-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
feat: add isolateTrace option to Sentry.withMonitor() #18079
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
naaa760
wants to merge
4
commits into
getsentry:develop
Choose a base branch
from
naaa760:feat/monitor-trace
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
2b4f7c1
feat(core): Add isolateTrace option to MonitorConfig
naaa760 382fdc6
feat(core): Implement isolateTrace in withMonitor function
naaa760 4dfa0af
test(core): Add tests for isolateTrace functionality
naaa760 4b663d6
Merge branch 'develop' into feat/monitor-trace
naaa760 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bug: Isolated Trace Creation Failing in Monitored Spans
withMonitor(..., { isolateTrace: true }) does not actually start a new trace when an active span exists. It calls startSpan({ forceTransaction: true }) without resetting the propagation context or explicitly nulling the parent, so startSpan continues the existing traceId if a parent span is present (per createChildOrRootSpan’s parentSpan && forceTransaction branch). This contradicts the intent to create a separate trace per monitor execution. To truly isolate, start a new trace (e.g., via startNewTrace) before creating the monitor span (or set a new propagation context/parentSpan: null with a new traceId).