Getting started
Sign in, then point your OpenTelemetry at your workspace and watch the first spans land. The whole path from landing page to your own data in atrim.ai.
atrim.ai docs
Point your existing OpenTelemetry at atrim.ai and the analysis starts on its own — topology, ranked critical paths, and incident detection, with nothing to install in your cluster.
Connect your app
The endpoint, the auth header, and the per-language wiring — plus what to check when nothing shows up.
Try the OTel Demo
No app to instrument yet? Run the OpenTelemetry Demo against atrim.ai and get a realistic microservice graph in a few minutes.
What atrim.ai does
A tour of every surface — Intelligence, Exploration, Incidents, and your workspace controls.
The surfaces
Section titled “The surfaces”Critical Paths
The flagship lens: request paths ranked by where time and errors actually accumulate, with the evidence one click away.
Metric Signals
Metrics that moved, ranked statistically against each service’s own history, with the arithmetic behind every rank on screen.
Service Topology
The full-system map — every service a node, every call an edge, with rate, error and duration read straight off the graph.
Traces, Logs & Metrics
The three raw-data explorers behind the findings — one natural-language-first query shell over traces, logs and metric series.
Incidents
A complete detect → notify → resolve loop: a condition opens an incident, a message goes out, and it closes itself when the condition clears.