Connect logs, traces, and metrics datasets so investigations can move from the first clue to the surrounding system state without manual query stitching.
Correlations are now available in Axiom.
Correlations connect the logs, traces, and metrics that describe the same system. Instead of treating each signal as a separate silo, Axiom lets you move from the first clue to the surrounding system state without manual query stitching.
Move from logs to traces#
In many incidents, the first clue is a log event: a timeout, an exception, a failed request, or some local detail that proves something went wrong.
With Correlations, a log event that includes trace context can open the matching trace in Axiom. No copying trace IDs. No switching datasets. No rebuilding the time range by hand.
Inspect related metrics#
A trace can show where one request slowed down. It cannot always show whether the service was already unhealthy.
With Correlations, Axiom can surface related workload metrics while you are inspecting the span. That context helps separate a single bad request from a broader service problem.
For more information, see Correlations.