Proposed scenarios and roadmap for messaging semantic conventions for tracing

[pyohannes]

Semantic conventions for messaging systems for tracing are available, but are in an experimental state. A workgroup focusing on messaging semantic conventions will work on bringing the existing semantic conventions for messaging to a stable state. The workgroup meets on Thursdays at 8AM PST.

This documents proposes a scope for an initial stable version of messaging semantic conventions, as well as a roadmap. It should serve as a starting point for initial discussions in the workgroup and, once agreed on, define the further agenda of the workgroup.

[Oberon00]

Consider moving this PR out of the draft state ("Ready for Review"). If it's in draft state, that signals that you don't need feedback on it yet except from people you explicitly requested it from. Maybe that is the case here since you asked for feedback in the Messaging Conventions WG, but if you also want feedback from outside the WG, I'd mark it as "ready for review". Unless there are some changes you plan to do before.

[pyohannes]

Consider moving this PR out of the draft state ("Ready for Review").

Done. I think the first workgroup meeting showed enough alignment on the document so we can have a wider discussion.

Examples are still missing and will be added once we discussed the scenarios.

[pyohannes]

@open-telemetry/specs-approvers @open-telemetry/specs-trace-approvers

Please have a look. This document captures a consensus we reached in the messaging workgroup.

[pyohannes]

It would be useful to list the popular messaging systems which can be correctly modelled within the constraints of the scenarios that the OTEP suggests to support. The examples mention RabbitMQ and Kafka, if there are others that will be supported by this proposal please list somewhere.

Added a sentence with a (non-exhaustive) list of systems that we aim to target:

Popular messaging systems that should be supported include Kafka, RabbitMQ, Apache RocketMQ, Azure Event Hubs and Service Bus, Amazon SQS, SNS, and Kinesis.

[pyohannes]

@open-telemetry/specs-approvers @open-telemetry/specs-trace-approvers

Thanks for reviewing. Can anybody with the necessary permissions please merge this PR?

[tedsuo]

I believe @open-telemetry/technical-committee needs to merge, not approvers.

[tigrannajaryan]

Thanks @pyohannes !