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:

  • Searching for traces by logs
  • Searching for logs by traces
  1. Traces
  2. Working with traces
  3. Trace-to-log correlation

Trace-to-log correlation

Written by
Yandex Cloud
Updated at March 24, 2026
  • Searching for traces by logs
  • Searching for logs by traces

Traces and logs describe the same application from different perspectives: traces show the request's path through services and operations, whereas logs capture events and messages in each component. In Monium, logs and traces are linked: from a log, you can navigate to a trace or span, and from a trace or span to related logs. This gives you the full context of the request from the same place to help you diagnose the problem faster.

Most OpenTelemetry instrumentation libraries automatically add trace IDs to log entries:

  • trace_id: Trace ID.
  • span_id: Span ID.

Here is an example of a log entry in JSON format with tracing context:

{
  "level": "INFO",
  "time": "2026-02-18T13:58:22.200Z",
  "project": "folder__b1g86q4m5vej********",
  "cluster": "default",
  "service": "frontend-proxy",
  "host": "frontend-proxy-f55dc9f55-ktxwv",
  "message": "Request successfuly served",
  "span_id": "a4df8085ed748a6b",
  "trace_id": "7d069c8223d982cd72e549860de9d210",
  "labels": {
    "k8s.deployment.name": "frontend-proxy",
    "k8s.namespace.name": "default",
    "k8s.node.name": "cl1c63baqn6458a167ec-omor"
  }
}

Field names in logs may vary depending on the delivery format, e.g., trace.id and span.id instead of trace_id and span_id. To navigate to a trace, use the ID value.

Searching for traces by logsSearching for traces by logs

To open a trace or span by log and view the full request execution context:

  1. Open the logs page and locate the entry you need. For more information on viewing logs, see Viewing logs.
  2. In the entry, find the field with the trace ID (trace_id or trace.id) or span ID (span_id or span.id) and click its value.

This will open the trace view page with the selected span or the root span of the trace.

Searching for logs by tracesSearching for logs by traces

To find all logs related to a trace or particular span:

  1. Open the trace you need in the trace search and select the span on the trace view page.
  2. In the right-hand span details panel, click Go to logs and select Trace logs or Span logs.

This will open the Viewing logs page with a filter by trace_id or trace_id and span_id already set.

Was the article helpful?

Previous
Critical path analysis
Next
Trace archiving
© 2026 Direct Cursus Technology L.L.C.