Yandex Cloud
Search
Contact UsTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Monium
  • Getting started
  • Overview
    • Getting started
    • Basic terms
      • Auto-instrumentation
      • Manual instrumentation
      • HTTP communication
      • Working with databases
      • RPC calls
      • Asynchronous operations
      • Handling errors
      • Retries
    • Limitations
  • Access management
  • Pricing policy
  • Terraform reference
  • Release notes

In this article:

  • Naming convention
  • Attributes
  • Examples
  • Multiple producers, one consumer
  • One producer, multiple consumers
  1. Traces
  2. Application instrumentation
  3. Asynchronous operations

Asynchronous operations

Written by
Yandex Cloud
Updated at March 24, 2026
  • Naming convention
  • Attributes
  • Examples
    • Multiple producers, one consumer
    • One producer, multiple consumers

In asynchronous communication via message queues (Kafka, RabbitMQ, etc.), span relationships are not modeled as parent–child; instead, span links are used. They connect spans from different traces, e.g., when multiple producers send messages and a consumer processes them in a single batch.

Naming conventionNaming convention

The span name has the {messaging.operation.name} {destination} format, e.g., send orders or process orders. For a topic name with high cardinality, use a template (messaging.destination.template). If the topic is unknown, use unknown. For more information, see the messaging span naming specification.

AttributesAttributes

Attribute

Description

messaging.system

Messaging system: kafka, rabbitmq, etc.

messaging.destination.name

Topic or queue name: orders

messaging.operation.name

System operation name: send, poll, or process

messaging.operation.type

Standardized type: send, receive, process, create, or settle

messaging.message.id

Message ID

messaging.batch.message_count

Number of messages in the batch

For a full list of attributes, see the OpenTelemetry specification for messaging spans.

ExamplesExamples

Multiple producers, one consumerMultiple producers, one consumer

Producer A and Producer B each send a message to the orders Kafka topic. The consumer receives both messages in a single batch (poll orders span) and then creates an individual process orders span for each message. Span links are attached to the process spans, connecting each message back to its producer:

Attribute

Producer A

Producer B

Consumer: receive

Consumer: process A

Consumer: process B

Name

send orders

send orders

poll orders

process orders

process orders

Kind

PRODUCER

PRODUCER

CLIENT

CONSUMER

CONSUMER

Status

OK

OK

OK

OK

OK

Links

—

—

—

→ send orders (Producer A)

→ send orders (Producer B)

messaging.system

kafka

kafka

kafka

kafka

kafka

messaging.destination.name

orders

orders

orders

orders

orders

messaging.operation.name

send

send

poll

process

process

messaging.operation.type

send

send

receive

process

process

messaging.message.id

a1

a2

—

a1

a2

messaging.batch.message_count

—

—

2

—

—

One producer, multiple consumersOne producer, multiple consumers

A producer sends a message to the orders topic. Consumer X and Consumer Y from different consumer groups independently process this message. Each process span is connected to the producer's span via a span link:

Attribute

Producer

Consumer X

Consumer Y

Name

send orders

process orders

process orders

Kind

PRODUCER

CONSUMER

CONSUMER

Status

OK

OK

OK

Links

—

→ send orders (Producer)

→ send orders (Producer)

messaging.system

kafka

kafka

kafka

messaging.destination.name

orders

orders

orders

messaging.operation.name

send

process

process

messaging.operation.type

send

process

process

messaging.message.id

a1

a1

a1

Was the article helpful?

Previous
RPC calls
Next
Handling errors
© 2026 Direct Cursus Technology L.L.C.