-
-
Notifications
You must be signed in to change notification settings - Fork 54
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
feat: Propagate traceId
on platforms supported by sentry-native
#2089
Conversation
Instructions and example for changelogPlease add an entry to Example: ## Unreleased
- Propagate `traceId` on platforms supported by `sentry-native` ([#2089](https://github.com/getsentry/sentry-unity/pull/2089)) If none of the above apply, you can opt out of this check by adding |
f961bec
to
6265ac0
Compare
CHANGELOG.md
Outdated
@@ -4,6 +4,7 @@ | |||
|
|||
### Features | |||
|
|||
- When running on Windows or Linux, the SDK now links errors and events originating on different layers (managed, native errors) via `trace ID` ([#2089](https://github.com/getsentry/sentry-unity/pull/2089)) |
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.
question: Could we merge both entries into a single entry linking both PRs, or do we prefer to have one entry per PR?
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.
True, we could just append the links to the PRs to the entry!
Propagating the
traceId
when running on platforms supported bysentry-native
.