Skip to content

feat(sentry): Add sentry.description attribute#135

Merged
loewenheim merged 1 commit intomainfrom
sebastian/sentry-description
Sep 11, 2025
Merged

feat(sentry): Add sentry.description attribute#135
loewenheim merged 1 commit intomainfrom
sebastian/sentry-description

Conversation

@loewenheim
Copy link
Contributor

@loewenheim loewenheim commented Sep 11, 2025

This attribute roughly corresponds to the description field on SpanV1, which is marked as Pii::Maybe. If this attribute is not defined in this repo, Relay assumes Pii::True.

Implements INGEST-571.

@linear
Copy link

linear bot commented Sep 11, 2025

This attribute roughly corresponds to the description field on SpanV1,
which is marked as `Pii::Maybe`. If this attribute is not defined in
this repo, Relay assumes `Pii::True`.
@loewenheim loewenheim force-pushed the sebastian/sentry-description branch from f67d527 to 91f3a2e Compare September 11, 2025 10:39
@cleptric
Copy link
Member

Are we aligned on the naming here? Aka, is this already used in Relay?

@AbhiPrasad
Copy link
Contributor

Should we use sentry.span.description instead?

@loewenheim
Copy link
Contributor Author

Should we use sentry.span.description instead?

I would leave it as it is analogously to sentry.op, which also only applies to spans.

Are we aligned on the naming here? Aka, is this already used in Relay?

It's used in the span v2 -> span v1 conversion to populate the description field on span v1. This behavior was inherited from the old OTEL -> span v1 conversion.

@loewenheim loewenheim merged commit 74d6eea into main Sep 11, 2025
5 checks passed
@loewenheim loewenheim deleted the sebastian/sentry-description branch September 11, 2025 12:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants