You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Summary of the problem
The APM trace view does not highlight errored span in trace view in case error is reported over Opentelemetry protocol. (otel.status_code = "ERROR"). This is related to trace SPAN error !
Telemetry data flow: NetCore > OpentelemtryCollector > ElasticAPM server all over otel-protocol.
State:
Some span is errored
Span contains otel.status_code = "ERROR"
The error is visible only on span detail not in Trace view
Error is never highlighted and in span view it has only gray color.
This span also contain error log from logging system that is visible but also not highlited
Requirement:
Span errors must be in trace view visible for errored Span similar as status code errors or system exceptions errors...
Stack verisons
7.14.0
Example failed and not highlighted span member:
(The last span has error)
This is same data interpreted by Zipkin and Equal is visible in Jaeger:
The text was updated successfully, but these errors were encountered:
Summary of the problem
The APM trace view does not highlight errored span in trace view in case error is reported over Opentelemetry protocol. (
otel.status_code = "ERROR"
). This is related to trace SPAN error !Telemetry data flow:
NetCore > OpentelemtryCollector > ElasticAPM server
all overotel-protocol
.State:
otel.status_code = "ERROR"
Requirement:
Span errors must be in trace view visible for errored Span similar as status code errors or system exceptions errors...
Stack verisons
7.14.0
Example failed and not highlighted span member:
(The last span has error)
This is same data interpreted by
Zipkin
and Equal is visible inJaeger
:The text was updated successfully, but these errors were encountered: