Skip to content
GitHub
Start a 14-day trial

Your first ten minutes

By the end of this guide you’ll have your own request on screen and a ranked critical path through your services, with Analyze one click away.

New here? Getting started covers signing in and the first-run welcome. This guide picks up once you’re in your workspace.

  1. Open Settings → App Onboarding. Under Admin & Governance, open Settings, then App Onboarding. Choosing Connect your app on the first-run welcome lands you here too.

  2. Generate a token. Press Generate token, keep Send telemetry as the purpose, and press Generate token in the dialog. Press Copy, then Done. The token is shown once, and it is already filled into the config on this page, so stay here for the next step. Leave, and you generate another.

  3. Send telemetry from your app. Under 2. Send telemetry from your app, pick your route:

    • My app already uses OpenTelemetry — copy the Environment Variables tab, or the OTel Collector tab to add an exporter beside the ones you already run.
    • Have my coding agent do it — a prompt for Claude Code, Cursor or any coding agent, in any language. Connect with a coding agent walks it.

    Every language, the Collector, Kubernetes and the endpoint details are on Connect your app.

  1. Start your app and make a request, so it produces a trace.

  2. Press I’ve started my app — check now under 3. Check that your telemetry arrived. The check walks your telemetry through Accepted, then Searchable with the services it saw, then Analysis ready.

  3. Press Open your trace. The request you just sent opens as a waterfall, with Analyze and Copy for agent in its header.

If nothing arrives, work down the troubleshooting list.

Critical paths are the routes requests take between your services. Send some traffic that crosses from one service to the next, and when the check reaches Analysis ready, Go to Critical Paths appears beside Open your trace. Running a single service? Your trace and Analyze already work on it, and See your services, in the same place, opens it in Service Topology.

  1. Press Go to Critical Paths once it appears, or open Intelligence → Critical Paths. I’ve already ranked the paths through your system by where the time and the errors go, so the one worth your attention is at the top.

  2. Select the top path. Its services are listed above the detail panel, and the Explore panel on the right keys to it.

  3. Press View Trace to open a real request that took this path.

  4. Press Analyze in the trace’s header. I read that request, show where its time went and, if it failed, name the service the failure started in, with the evidence beside it.