Skip to content
This repository has been archived by the owner on Aug 14, 2024. It is now read-only.

Define how tracing and performance can be separated #885

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

smeubank
Copy link
Member

@smeubank smeubank commented Mar 22, 2023

Background

While much of distributed tracing was introduces in many places at Sentry with the perofrmance product. Tracing is not tied to performance, in any way "by design".

Meaning any products of sentry should be linkable by traces regardless of the usage of the Performance product.

This change proposed would define how SDKs should behave with existing options. This obeys our promise to users, and we only need to check how all SDKs behave in actuality of this situation.

Open point:
Tracing could be on by default for all sentry SDKs, and this option is then simply to turn it off.

https://develop-git-smeubank-tracing-sans-performance.sentry.dev/sdk/performance/#separation-of-sampling-transcations-and-trace-propagation

getsentry/sentry#45725

@vercel
Copy link

vercel bot commented Mar 22, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated
develop ✅ Ready (Inspect) Visit Preview Mar 22, 2023 at 1:13PM (UTC)

@smeubank smeubank changed the title Define how tracing and performance can be segregated Define how tracing and performance can be separated Mar 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant