Our latest version of our JS SDKs (@sentry/browser >= 5.2, @sentry/node >= 5.2) and sentry-python >= 0.7.13 now come with a Tracing integration. What is tracing? Our first version of tracing is there to correlate errors between different platforms. So for example you are using our JS SDK in the f…

I don’t quite get the Tracing feature. From your screenshot it just looks like two integrations using the same DSN. At least from your screenshot I can‘t see an automatic correlation between the frontend/backend errors. Could you please give some in depth details on the Tracing feature? Thanks in…

You are right they use the same DSN but note the filter on the right hand side. The issues also have the same trace ID. The sdks automatically correlate the events.

Sorry if this wasn’t clear enough. So on the screenshot you can see multiple issues that all have the same trace (see content of the search field). When using the tracing integration we emit a “trace” tag which can be used to search for issues that belong to the same trace (across different projec…

Thanks for the clarification @HazAT @bruno-garcia ! I was so focused on the highlighted area that I missed the search filter. Looks promising and with some UI iterations this could give significant insight into errors trails.

Does / will this feature support– Accessing the tracing id used by Sentry for inclusion in one’s own (non-Sentry) logs, and Setting your own tracing id instead of using one generated by Sentry?

Hey, So regarding 1. This depends on your setup, if you log all incoming headers you will see the trace_id but we are not logging anything anywhere by default. Regarding 2. Yes, you can do it now like (this may change in the future, that’s why it’s not documented yet): import * as Sentry from '…

Okay, thanks! So we can grab the trace information from the headers (assuming those header names remain the same). Also, what is the difference between the span_id and the trace_id? How should they each be thought of / which should be of interest to users?

The header might change very soon :expressionless: to it’s final form. So please be aware of that. trace_id can be seen as something similar to a session_id, all spans that are in a trace have the same trace_id. A span_id uniquely identifies a span which can be seen as an action during a trace.

Do you mean to set the trace id or the span id? The trace id could have been defined already by the caller in which case you can’t control. Could you please describe a bit your scenario, besides logging Sentry’s trace/span ids? And what format would you be expecting to have for your ids?

Sorry, I meant to reply to this earlier. [image] bruno-garcia: Do you mean to set the trace id or the span id? I guess just the trace id. [image] bruno-garcia: Could you please describe a bit your scenario, besides logging Sentry’s trace/span ids? And what format would you be expecting …

Sentry + Tracing

SDKs

HazAT January 14, 2020, 11:54am 17

Hey, yes it still works.
Please see this post for the latest info on how to use APM

Topic		Replies	Views
[PHP, React] Distributed Tracing SDKs	7	2845	December 17, 2020
JS transactions not linked to backend using JS/PHP SDK SDKs	1	1231	January 19, 2021
Sentry's APM Docs [Alpha] SDKs	6	4363	June 19, 2020
Performance Monitoring "head-based"	4	2761	October 1, 2020
Sentry Tracing Node appears to work but noting logged, how to debug? SDKs	2	2835	January 11, 2022

Sentry + Tracing

Related topics