Skip to content
GitHub
Start a 14-day trial

Getting started

atrim.ai turns your existing OpenTelemetry into topology, ranked critical paths, and automatic analysis — you point your data at it and the work starts on its own. This is the whole path from the landing page to your first spans arriving.

  1. Land and pick a route. Open atrim.ai. Two ways in, each one click:

    • Connect my app — you already emit OpenTelemetry and want your own services in.
    • Explore the demo — nothing to connect yet, so start on a live OpenTelemetry demo with incidents firing throughout the day and see what atrim.ai does with it.
  2. Sign in. A magic link to your email, or GitHub. Your workspace is ready as soon as you’re in. Until it has received anything, the app opens on a welcome that offers the same two choices — Connect your app or Explore the demo — or Skip for now.

  3. Generate a token and copy your config. On Settings → App Onboarding (the Connect my app route opens it for you), Generate token creates your ingest token and fills it, with the OTLP endpoint, into config that is ready to paste. The token is what routes your telemetry to your workspace; copy the config before you leave the page. The App route needs no code change; the Collector route adds an exporter beside the ones you already run. No OpenTelemetry in your app yet? Choose Have my coding agent do it for a prompt to hand your coding agent, in any language, or follow your language’s steps on Connect your app.

  4. Watch it arrive. Start your app, make a request, and press I’ve started my app — check now. The check shows your telemetry Accepted, then Searchable (with the services it saw), then Analysis ready, and Open your trace opens the trace you just sent. If nothing shows up, the same screen links to troubleshooting.

  5. Explore. Once data is arriving, start at Critical Paths — the ranked view of where time and errors actually accumulate — or open Service Topology for the map.

The App route needs no SDK and no code change — five standard OpenTelemetry environment variables:

OTEL_EXPORTER_OTLP_ENDPOINT=https://otlp.atrim.ai
OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf
OTEL_EXPORTER_OTLP_HEADERS=x-api-key=atrim_sat_YOUR_TOKEN_HERE
OTEL_EXPORTER_OTLP_COMPRESSION=gzip
OTEL_SERVICE_NAME=your-service-name

The Collector route adds an exporter rather than replacing one, so whatever you already send telemetry to keeps receiving it. Both snippets, and the full per-language reference, are on Connect your app.

atrim.ai groups its surfaces into four entry points. Once your first traces land:

  • Intelligence — start here. Critical Paths ranks the request paths through your system by where the time and the errors actually are. Metric Signals surfaces the metrics that moved.
  • Exploration — Service Topology for the map, and the Traces, Logs and Metric Explorer explorers for individual requests, lines and ad-hoc metric queries.
  • Incidents — automatic detection with a full lifecycle: an incident that opens on a real condition and resolves when the condition clears.
  • Admin & Governance — your ingest tokens, alerting webhooks, appearance, and account.