elastic / elastic/opentelemetry-lib
[enrichments] Destination service resource derivation for messaging systems
Open
- Dominant language
- Go
- Stars
- 5
- Forks
- 18
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 7
Description
Currently, the code in apm-data (as well as the ported code in this repository for enrichments) prioritizes `peer.service` for destination service resource enrichment. For the messaging system, the destination service resource is derived by suffixing the messaging destination name to the peer service. Is this valid or do we need to reconsider this?
Relevant discussion: https://github.com/elastic/opentelemetry-lib/pull/72#discussion_r1710193570
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.