Closed kahest closed 1 year ago
We'll look into the code base and check if anything has to be done and check off the platform if nothing is needed.
@antonpirker this doc is related to this issue right? We just need to be sure what the schema is, so we can double-check in our implementation.
https://develop.sentry.dev/sdk/performance/span-operations/ does not tell where http.status
should go.
https://github.com/getsentry/rfcs/pull/89 is a draft and it links to OTel which is a huge breaking change.
https://github.com/getsentry/develop/pull/940 is the spec, I believe SDKs don't set that yet, so we have to.
@antonpirker this doc is related to this issue right? We just need to be sure what the schema is, so we can double-check in our implementation.
Maybe too late, but for the record: Yes. this doc is "where are all the SDKs storing the http status code right now". In the future we want all the SDKs store the http status code in the same place, making it easier of ingest to act on it.
It changed to http.response.status_code
https://develop.sentry.dev/sdk/performance/span-data-conventions/
React Native SDK doesn't set status_code
. If there will be any changes RN gets it from JS SDK.
Background:
http.status
is set in different places in different SDKs which creates some problems in processing for metrics extraction and thenhttps://www.notion.so/sentry/Expand-Metrics-for-Alerts-cdfa32d7624e498b8246c3f131f753f1#17480955e2fb4407b619b9236bc2723a
Requirements:
Note: .NET and Java are handled in https://github.com/getsentry/team-sdks/issues/9.