- activemq 'classic' doc
- activemq 'artemis' : bonus, can be done as a follow-up: doc
Proposal
Use the activemq.* namespace for all metrics:
Reuse when possible messaging semconv definitions, for example messaging.destination.name, this implies a few expected changes in the future
Proposal
Use the
activemq.*namespace for all metrics:messaging.activemq.*namespace (Messaging: adopt system-specific naming practices similar to DB semantic-conventions#1892)Reuse when possible messaging semconv definitions, for example
messaging.destination.name, this implies a few expected changes in the futuremessaging.system=activemq, we expect it to be stabilized asmessaging.system.nameMessaging: adopt system-specific naming practices similar to DB semantic-conventions#1892activemq.destination.typemight be used to indicate if it's aqueueortopic, there is currently no semconv attribute to reflect this (Messaging: record queue vs topic behavior correctly semantic-conventions#1220), there was one in the past but it has been removed.