semantic-conventions/docs/messaging
Johannes Tax 4204c02ef0
BREAKING: Rename `messaging.client_id` to `messaging.client.id` (#948)
2024-05-03 06:59:02 -07:00
..
README.md [chore] Prepare v1.25.0 release (#878) 2024-04-04 09:45:17 -07:00
azure-messaging.md BREAKING: Rename `messaging.client_id` to `messaging.client.id` (#948) 2024-05-03 06:59:02 -07:00
gcp-pubsub.md Generate Attribute Registry using Weaver (#917) 2024-05-01 11:22:28 -07:00
kafka.md BREAKING: Rename `messaging.client_id` to `messaging.client.id` (#948) 2024-05-03 06:59:02 -07:00
messaging-metrics.md Generate Attribute Registry using Weaver (#917) 2024-05-01 11:22:28 -07:00
messaging-spans.md BREAKING: Rename `messaging.client_id` to `messaging.client.id` (#948) 2024-05-03 06:59:02 -07:00
rabbitmq.md Generate Attribute Registry using Weaver (#917) 2024-05-01 11:22:28 -07:00
rocketmq.md BREAKING: Rename `messaging.client_id` to `messaging.client.id` (#948) 2024-05-03 06:59:02 -07:00

README.md

Semantic Conventions for Messaging Systems

Status: Experimental

This document defines semantic conventions for messaging systems spans, metrics and logs.

Semantic conventions for messaging systems are defined for the following signals:

Technology specific semantic conventions are defined for the following messaging systems:

  • Kafka: Semantic Conventions for Apache Kafka.
  • RabbitMQ: Semantic Conventions for RabbitMQ.
  • RocketMQ: Semantic Conventions for Apache RocketMQ.
  • Google Cloud Pub/Sub: Semantic Conventions for Google Cloud Pub/Sub.