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
      • Searching for traces and spans
      • Viewing and analyzing traces
      • Query language
      • Critical path analysis
      • Trace-to-log correlation
      • Trace archiving
      • Incomplete traces
    • Limitations
  • Access management
  • Pricing policy
  • Terraform reference
  • Release notes

In this article:

  • Gantt chart
  • Span details
  • Analysis strategies
  • Top-down
  • Bottom-up
  • Interface actions
  1. Traces
  2. Working with traces
  3. Viewing and analyzing traces

Viewing and analyzing traces

Written by
Yandex Cloud
Updated at March 24, 2026
  • Gantt chart
  • Span details
  • Analysis strategies
    • Top-down
    • Bottom-up
  • Interface actions

The trace view page displays the end-to-end request path: from the root span to final operations. To open a trace, use search or type in its trace_id.

Gantt chartGantt chart

The trace is visualized as a Gantt chart, where each horizontal bar represents a span and its length indicates the operation duration. Nested spans are positioned beneath their parents, forming a call tree. Any spans with errors are highlighted in color.

Span detailsSpan details

Click a span to open its details. The information is organized into tabs:

  • Attributes: Key-value pairs added during instrumentation: HTTP method, URL, database table name, etc.
  • Events: Timestamped data recorded within the span (e.g., an exception event).
  • Links: References to associated spans within the same or a different trace. They are used in asynchronous operations. If a span has links, they are displayed next to its name.

The following actions are available from the span details:

  • Share: Copies a link to the selected span to your clipboard.
  • Go to logs: Opens logs for with the span or entire trace. For more information, see Trace-to-log correlation.

Analysis strategiesAnalysis strategies

Top-downTop-down

Use this approach when you lack prior context, e.g., when you receive a trace_id from an alert or a user. Start at the root span and follow the request’s path through each service to pinpoint latency hotspots or the exact point of failure.

Bottom-upBottom-up

Use this when you are investigating a specific service or operation. Use the in-trace search bar to find relevant spans: matching spans will be highlighted.

Interface actionsInterface actions

  • Show only found results: Hides irrelevant spans, displaying only those that match your search.
  • Spans with errors: Filters the trace to show only spans with ERROR status.
  • Spans on critical path: Displays spans affecting the total request execution time. For more information, see Critical path analysis.
  • Share: Copies a link to the trace to your clipboard. If a specific span is open, the link will point directly to that span.

Was the article helpful?

Previous
Searching for traces and spans
Next
Query language
© 2026 Direct Cursus Technology L.L.C.