Align attribute name and semantics with the OpenTelemetry spec (which was finalized yesterday 2023/9/11 - see open-telemetry/semantic-conventions#205) -- http.error.reason attribute has been standardized under name error.type. We need to:
- Rename
http.error.reason to error.type.
- Report
error.type also for valid responses where the HTTP status code indicates an error (4xx and 5xx) -- in such case, the value should be the string representation of the HTTP status code.
- Note: Currently we report
http.error.reason only when the underlying handler fails to fetch a response.
See error.type in the spec for more details.
For context: We introduced the attribute http.error.reason in PR #89809 (on 2023/8/3) based on the in-progress draft of the OTel spec (open-telemetry/semantic-conventions#205).
Given that this is new 8.0 feature, we should adapt to the spec in 8.0 to avoid breaking changes with 9.0.
Align attribute name and semantics with the OpenTelemetry spec (which was finalized yesterday 2023/9/11 - see open-telemetry/semantic-conventions#205) --
http.error.reasonattribute has been standardized under nameerror.type. We need to:http.error.reasontoerror.type.error.typealso for valid responses where the HTTP status code indicates an error (4xx and 5xx) -- in such case, the value should be the string representation of the HTTP status code.http.error.reasononly when the underlying handler fails to fetch a response.See
error.typein the spec for more details.For context: We introduced the attribute
http.error.reasonin PR #89809 (on 2023/8/3) based on the in-progress draft of the OTel spec (open-telemetry/semantic-conventions#205).Given that this is new 8.0 feature, we should adapt to the spec in 8.0 to avoid breaking changes with 9.0.