[RUM-11993] Add trace context and graphql fields to error event schema#370
Open
[RUM-11993] Add trace context and graphql fields to error event schema#370
Conversation
mormubis
requested changes
Mar 23, 2026
mormubis
reviewed
Mar 23, 2026
mormubis
approved these changes
Mar 23, 2026
c9ed97a to
4385e2f
Compare
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.
Motivation
When a network resource fails (timeout, no connectivity), the SDK emits a 'RUMErrorEvent'
Currently the error event schema has no trace context fields ('trace_id', 'span_id', 'parent_span_id', 'rule_psr')
and no 'graphql' struct on 'error.resource', unlike the success path ('RUMResourceEvent') which already has both.
This means cross-platform SDKs (React Native, Flutter) silently lose trace and GraphQL attributes on the error path.
Changes