[OpenTelemetry] Map OpenTelemetry messaging.* semantic conventions to Elastic Common Schema

[cyrille-leclerc]

Issue reported by https://github.com/gbanasiak on open-telemetry/opentelemetry-collector-contrib#3093

Is your feature request related to a problem? Please describe.

open-telemetry/opentelemetry-collector-contrib#671 introduced translation of http.* and db.* semantic conventions into Elastic equivalent, i.e. span.destination.* fields. The missing bit are messaging.* conventions which make service map presentation of services using components such as Kafka or RabbitMQ incomplete.

Describe the solution you'd like

Expand existing translation to include messaging.* conventions.

Describe alternatives you've considered

The alternative would be to use semantic convention for which translation exists (e.g. db.*) while manually instrumenting messaging spans, but that's hacky.

[cyrille-leclerc]

@axw was it fixed in 7.14 or 7.15?

[axw]

@cyrille-leclerc #5334 was merged into 7.14.

[tiny-dancer]

@axw minor note: this is still appearing in the limitations documentation: https://www.elastic.co/guide/en/apm/guide/current/open-telemetry.html#open-telemetry-known-limitations

[axw]

@tiny-dancer thanks for the heads up. There's still an issue remaining, which I'll write up and link from the docs soon. The gist is that OTel doesn't provide enough information for us to always correctly classify an OTel span as an Elastic APM transaction/span.

[axw]

@tiny-dancer FYI I've opened #7001, which is the only remaining limitation for messaging spans that I'm aware of. Docs should be updated in the not too distant future.