-
Notifications
You must be signed in to change notification settings - Fork 87
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(protocol): Add origin to trace context and span #1984
Conversation
Adds origin to both trace context and the span. The origin of the span indicates what created the span.
7c96fc6
to
5939cf9
Compare
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.
We could enforce alphanumeric characters: a-z , A-Z , and 0-9 and underscores: _ as pointed out in the develop docs.
Let's do this. It can easily be done by adding allow_chars
to the metastructure of the property, see example. Blocking the PR for this.
relay-general/src/protocol/mod.rs
Outdated
/// Origin type such as `auto.http`. | ||
/// Follows the pattern described in the [develop docs](https://develop.sentry.dev/sdk/performance/trace-origin/). | ||
pub type OriginType = String; |
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.
Sorry I missed this earlier, but let's move this to relay-general/protocol/contexts/mod.rs
, like OperationType
.
With getsentry/relay#1984, Relay officially accepts a new property on the span called origin. The origin property indicates what precisely created the span. This PR sends origin for opening span details to investigate that data in Amplitude.
With getsentry/relay#1984, Relay officially accepts a new property on the span called `origin`. The origin property indicates what precisely created the span. This PR sends origin for opening span details to investigate that data in Amplitude. The Amplitude event is [`Performance Views: Event Details span details opened`](https://data.amplitude.com/sentry/sentry.io/events/main/latest/Performance%20Views%3A%20Event%20Details%20span%20details%20opened?view=All&tab=DETAILS&propertyValidityFilter=All%2520Properties). For more information on trace origin, visit the [develop docs](https://develop.sentry.dev/sdk/performance/trace-origin/).
With getsentry/relay#1984, Relay officially accepts a new property on the span called `origin`. The origin property indicates what precisely created the span. This PR sends origin for opening span details to investigate that data in Amplitude. The Amplitude event is [`Performance Views: Event Details span details opened`](https://data.amplitude.com/sentry/sentry.io/events/main/latest/Performance%20Views%3A%20Event%20Details%20span%20details%20opened?view=All&tab=DETAILS&propertyValidityFilter=All%2520Properties). For more information on trace origin, visit the [develop docs](https://develop.sentry.dev/sdk/performance/trace-origin/).
With getsentry/relay#1984, Relay officially accepts a new property on the span called origin. The origin property indicates what precisely created the span. This PR adds this property in the span details view.
Adds origin to both trace context and the span. The origin of the span indicates what created the span.
Related RFC getsentry/rfcs#73 and develop docs PR getsentry/develop#887