Skip to content
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

Tracing: Native crashes don't have trace-id #1842

Open
bruno-garcia opened this issue Oct 13, 2024 · 0 comments
Open

Tracing: Native crashes don't have trace-id #1842

bruno-garcia opened this issue Oct 13, 2024 · 0 comments

Comments

@bruno-garcia
Copy link
Member

Using the sample in Sentry Defenses I was able to capture lots of examples (try/catch, log/ etc) and all those in the C# layer are connected via a trace:

https://sentry.sentry.io/issues/5987941966/?project=5905698&query=is%3Aunresolved%20issue.priority%3A%5Bhigh%2C%20medium%5D&referrer=issue-stream&sort=date&statsPeriod=1h&stream_index=1

Image

Except events captured by the native SDK. It has the breadcrumbs (scope sync) but no trace-id:

https://sentry.sentry.io/issues/5987942166/?project=5905698&query=is%3Aunresolved%20issue.priority%3A%5Bhigh%2C%20medium%5D&referrer=issue-stream&sort=date&statsPeriod=1h&stream_index=4

We need to set the trace-id via the bridge anytime we create/update the trace id.
This way, all the telemetry data is connected via the trace. Even user feedback, events on the backend, spans, and native crashes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Todo
Development

No branches or pull requests

1 participant