Skip to content
semconv.com
↑↓ move↵ openUse with your agent →

messaging.batch.message_count

Developmentintas of v1.44.0

The number of messages sent, received, or processed in the scope of the batching operation.

Instrumentations SHOULD NOT set messaging.batch.message_count on spans that operate with a single message. When a messaging client library supports both batch and single-message API for the same operation, instrumentations SHOULD use messaging.batch.message_count for batching APIs and SHOULD NOT use it for single-message APIs.

Examples

Used by

spans (7)

  • messaging.eventhubs.generic.client
  • messaging.process.consumer
  • messaging.receive.client
  • messaging.send.client
  • messaging.send.producer
  • messaging.servicebus.generic.client
  • messaging.settle.client

* required on that signal.

History

  1. v1.44.0

    No longer referenced by messaging.attributes, messaging.eventhubs and 4 others.

  2. v1.44.0

    Now referenced by messaging.attributes.consumer, messaging.eventhubs.generic.client and 6 others (conditionally required).

  3. v1.31.0

    No longer referenced by span.messaging.

  4. v1.31.0

    Now referenced by messaging.attributes (conditionally required).

  5. v1.31.0

    Stability label respelled from experimental to development.

  6. v1.30.0

    Already present at v1.30.0, the oldest release tracked here (experimental).

Definition sourceRegistry docsJSONUse with your agent →