Repository navigation
Observe investigation stream completion latency and client limits - #120
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.
An investigation can return HTTP 200 and later stall, disconnect, exceed client limits or emit unusable events. Record exactly one terminal stream outcome per attempt, time to first evidence/report separately from thinking, and bounded malformed/unknown/truncated/limit discard totals. Existing stream contents, questions, model output and session identifiers never enter telemetry.
Uses the identical bounded aggregate helper shared with #118; this is a standalone main-based PR. #117 enables collection in standard released images.
Validation: 19 focused stream-state/aggregation/privacy tests and production build/typecheck. Tests cover successful completion, each failure/cancellation outcome, cleanup deduplication, first useful response timing 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.