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:

  • Markup pattern
  • Attributes
  • Example
  1. Traces
  2. Application instrumentation
  3. Retries

Retries

Written by
Yandex Cloud
Updated at March 24, 2026
  • Markup pattern
  • Attributes
  • Example

Each retry attempt is recorded as an individual child span. This means a trace will show how many attempts were taken, which of them failed with an error, and which one was successful.

Markup patternMarkup pattern

The parent span covers the entire operation. Each attempt is a separate child span with the same name. Unsuccessful attempts get the ERROR status, and successful ones, OK. The http.resend_count attribute indicates the sequence number of the retry, starting with 1 for the first retry.

AttributesAttributes

Attribute

Description

http.resend_count

Sequence number of the retry attempt. The initial request has no sequence number; 1 is for the first retry, 2 for the second one, etc.

Populate request attributes (HTTP, RPC, etc.) in alignment with the conventions for each operation type; see HTTP communication, RPC calls.

ExampleExample

payment-service processes the payment and requests the exchange rate from an external service. The initial request fails, but the second attempt succeeds:

Attribute

process_payment

GET (attempt 1)

GET (attempt 2)

Kind

SERVER

CLIENT

CLIENT

Status

OK

ERROR

OK

http.resend_count

—

—

1

Was the article helpful?

Previous
Handling errors
Next
Searching for traces and spans
© 2026 Direct Cursus Technology L.L.C.