Repository navigation
Measure browser observed API outages and recovery duration - #121
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The availability dialog currently detects browser/proxy outages without reporting their impact. Add low-volume probe outcome/duration summaries and one outage-duration summary after confirmed recovery. Keep only one bounded in-memory outage transition while ingest may be unreachable; do not emit an outage on a single transient failure. Offline browsers, network errors, timeouts, HTTP failures and invalid proxy responses use fixed reason values. 401/403/429 remain reachable, and hidden/stopped probes are not counted as failures.
Uses the identical bounded aggregate helper shared with #118; this is a standalone main-based PR. #117 enables collection in released images. Same-service self-monitoring still needs an external synthetic check for complete outages.
Validation: 26 focused availability/aggregation/privacy tests and production build/typecheck. Tests cover two-probe confirmation, recovery-only emission, offline duration, duplicate recovery suppression, stopped probes and preservation through the RUM sanitizer.
Combined validation: all six frontend health PRs merge together without conflicts. The integrated suite passes 645 tests in 107 files and the production build/typecheck. A production-bundle Chrome smoke verified runtime opt-in, actual package version/environment, API/body events, failed lazy-route navigation, investigation completion/malformed-event counts and browser offline/recovery duration. Eleven custom event types arrived through the SDK and production privacy scrubber without query text or user identifiers in their attributes.