elastic / elastic/apm

APM span error is not highlighted when otel.status_code = "ERROR"

Open
#504 1 comment 1 reaction 0 assignees View on GitHub
design
Dominant language
Gherkin
Stars
427
Forks
125
PR merge metrics
No merged PRs in 30d

Description

**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)

![image](https://user-images.githubusercontent.com/54806834/133000026-44f8dffb-f3fa-4cd3-b1ec-1887a8e0c04a.png)

![image](https://user-images.githubusercontent.com/54806834/133000042-e10ed141-579b-4437-9bb5-fdc1b7edc0fa.png)

![image](https://user-images.githubusercontent.com/54806834/133000319-1f50fa00-1069-4353-a1b9-3e9aaa27c396.png)


**This is same data interpreted by `Zipkin` and Equal is visible in `Jaeger`:**


![image](https://user-images.githubusercontent.com/54806834/133001109-8e271511-e072-40fb-b343-aa64f90af0b5.png)

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.