search

getsentry / sentry

Developer-first error tracking and performance monitoring
https://sentry.io
Other
39.28k stars 4.21k forks source link

Identify what parts of the product use `event.contexts.trace` #69504

Open AbhiPrasad opened 7 months ago

AbhiPrasad commented 7 months ago

While revamping the JS SDK for v8, we've been taking another look at what we send in event.contexts.trace.

https://develop.sentry.dev/sdk/event-payloads/contexts/#trace-context

To help with this it would be great to identify what exact fields the product uses in event.contexts.trace so the SDK can send as minimal of a payload as possible.

So far we've identified three fields:

  1. event.contexts.trace.trace_id: Main correlation identifier for trace
  2. event.contexts.trace.span_id: Main correlation identifier for span
  3. event.contexts.trace.data: Used by transactions as a key-value bag for attributes, same function as span.data
### Tasks
- [ ] Audit Sentry
- [ ] Audit Snuba
- [ ] Audit Relay
getsantry[bot] commented 7 months ago

Routing to @getsentry/product-owners-performance for triage ⏲️