semantic-conventions/docs/messaging
Joao Grassi 8d6f12bd82
Clarify fully-qualified name should be used for `error.type` (#945)
Co-authored-by: Liudmila Molkova <limolkova@microsoft.com>
2024-04-23 08:30:22 -07:00
..
README.md [chore] Prepare v1.25.0 release (#878) 2024-04-04 09:45:17 -07:00
azure-messaging.md Fix the linkTitle for Azure Messaging (#944) 2024-04-22 11:14:04 +02:00
gcp-pubsub.md BREAKING: Rename `messaging.operation` to `messaging.operation.name` (#913) 2024-04-16 14:12:31 -07:00
kafka.md BREAKING: Rename `messaging.operation` to `messaging.operation.name` (#913) 2024-04-16 14:12:31 -07:00
messaging-metrics.md Clarify fully-qualified name should be used for `error.type` (#945) 2024-04-23 08:30:22 -07:00
messaging-spans.md Clarify fully-qualified name should be used for `error.type` (#945) 2024-04-23 08:30:22 -07:00
rabbitmq.md [chore] Prepare v1.25.0 release (#878) 2024-04-04 09:45:17 -07:00
rocketmq.md [chore] Prepare v1.25.0 release (#878) 2024-04-04 09:45:17 -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.