Repository navigation
Capture frontend framework failures and navigation health - #119
Merged
Merged
Conversation
mzupan
enabled auto-merge
November 15, 2026 22:23
mzupan
disabled auto-merge
November 15, 2026 22:24
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.
Vue-handled errors and failed lazy routes currently have no explicit application-health measurements. Register framework/bootstrap error capture before mounting and router measurement before authentication guards, then emit bounded error-source/stage and route-name navigation outcome/duration summaries. Deduplicate repeated reports of the same exception object and hand browser-global error capture to the existing SDK after initialization. No messages, stack traces, component props, URLs or route parameters are recorded.
Uses the identical bounded aggregate helper shared with #118; the PR is standalone against main. Standard released-image telemetry enablement is provided separately by #117.
Validation: 15 focused tests and production build/typecheck. Tests exercise real router success/duplicate/lazy-load rejection paths, production Vue error codes, exception deduplication, early-hook handoff, and preservation through the RUM privacy 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.