OTLP status.message is dropped by APM Server

Open Beginner friendly
#614 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
76/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
go
Domain
observability-sre

Research direction

Start in traces.go and follow the status.Code() handling for event.outcome and transaction.result. Check nearby tests for trace status mapping; done means the OTLP Status Description from status.Message() is preserved in the corresponding APM data while the existing derived fields remain correct.

Written by the indexing model from the issue text.

Description

traces.go calls status.Code() to derive event.outcome and transaction.result, but never calls status.Message().

Per the OTel spec, Description is a defined property of Status (setStatus(ERROR, description)).

Users setting an error description via the OTel API expect it to be mapped.

https://opentelemetry.io/docs/specs/otel/trace/api/#set-status

Dominant language
Go
Stars
12
Forks
31
Avg merge
8h 55m
Merged PRs (30d)
2

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from elastic/apm-data

All issues in elastic/apm-data

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.