find-traces

To query OpenTelemetry traces, you search across trace datasets by trace_id, service, duration, and error status. This analyzes distributed traces to identify errors, latency hotspots, and potential root causes quickly.

You can search for a specific trace_id by invoking a trace search query. This surfaces related spans and timing data for that trace_id, allowing you to correlate the results with service maps and dashboards to diagnose slow transactions.

Yes, analyzing distributed traces requires an authenticated Axiom CLI session. This session provides the necessary access to query trace datasets containing OpenTelemetry field conventions like trace_id, span_id, and duration.

Trace discovery works across datasets containing OpenTelemetry traces, such as otel-*, traces, and spans. Querying these datasets by service, duration, and error status surfaces relevant traces to locate issues in distributed systems.

Yes, you can investigate slow transactions by running a trace search to surface related spans and timing. Analyzing these OpenTelemetry spans identifies latency hotspots and helps diagnose the root cause of slow distributed transactions.