Currently, Sentry SDKs (and instrumentation) can add a span status message to spans via
span.setStatus({code: SpanStatus.ERROR, message: 'Connection Refused'});
Our current span v2 serialization logic discards the message property, following our push to have as simple span statuses as possible (ok and error only).
Suggested solution:
We reuse the sentry.status.message attribute that we already use for the exact same case in our OTLP ingestion endpoint. This is essentially the same use case.
Currently, Sentry SDKs (and instrumentation) can add a span status message to spans via
Our current span v2 serialization logic discards the
messageproperty, following our push to have as simple span statuses as possible (okanderroronly).Suggested solution:
We reuse the
sentry.status.messageattribute that we already use for the exact same case in our OTLP ingestion endpoint. This is essentially the same use case.