Repository navigation
Measure frontend API outcomes retries and body failures - #118
Merged
Merged
Conversation
This was referenced Nov 15, 2026
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.
HTTP 200 and successful retries currently hide malformed responses, failed body reads and additional transport work. Record bounded ten-second summaries for final logical JSON request outcomes, individual attempts, retries and response-body lifecycles. Logical request duration includes reading and decoding the body. Expected cancellation is a separate outcome; resource identifiers, URLs, queries and error messages are never attributes. RUM ingest is excluded.
Includes a small bounded operational aggregate sink that buffers before RUM initialization without running a timer when collection is disabled. The same helper commit is included unchanged in the other standalone operational-health PRs, so these PRs share no merge-order dependency. Runtime enablement in #117 is needed for standard released images to send telemetry.
Validation: 27 focused transport/cache/health tests, 10 final health/privacy tests, production build and typecheck. Tests cover retry recovery, deferred bodies, HTTP-200 decode failures, mid-body failures, finite labels and preservation through the production 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.