Roadmap — Telemetry Machine

Recently shipped

Live for everyone.

›

Connect this application to Telemetry Machine.

Instrumentation addedOTel

Dataset and key createdTM

Production data verifiedOK

Agent setup

One prompt and your agent does the setup.

Paste our prompt into your coding agent. It installs our skills, instruments your service with OpenTelemetry, creates a dataset and key, and keeps going until your first traces and logs arrive.

Read the quick start guide

$ tm-cli query checkout --type traces --since 15m \
    --where "status_code = 'ERROR'" \
    --description "Recent checkout errors"

POST /checkout1,204

POST /cart/items87

GET /payment-methods12

tm-cli

Telemetry your agents can actually use.

tm-cli gives coding agents the same access you have: read schemas, look up field values, and query traces, logs, and metrics from the terminal. Your agent can check its own work in production instead of asking you to.

Now

In active development. Some of it is already in early users' hands.

app.version 4.2.0 81% 12%

cloud.region eu-west-2 64% 23%

http.route /checkout 47% 19%

Surface

Get straight to the why.

Highlight the outliers on a heatmap and Surface shows what sets them apart from everything else. Pin a problem on the exact version, region, pod, or customer behind it, starting from any trace query. No hunches needed, and anyone on the team can read the answer.

checkout availability 99.9% · 7d

38%error budget left

Spending 2.9× faster than budget · out in ~2 days

SLOs

Catch what hurts customers before it escalates.

See at a glance which services are keeping their promises and which need work. Set a target, or let the SLO agent suggest one from your real traffic. Alerts fire on real budget burn instead of every blip, and they arrive with context: one click opens Surface on the spans that broke the SLO.

Dashboards

Dashboards as powerful as your queries.

Turn any query into a widget: time series, heatmaps, histograms, top values, and tables. Split by any field, even numeric ranges like payload size, then put them side by side for your team and your agents.

Soon

Next up once the work above lands.

Investigation agents

An investigation that starts before you open your laptop.

When an alert fires, an agent gets to work. It queries your traces, logs, and metrics, runs Surface on the failing spans, and checks what changed. You get a short write-up with the evidence linked, so you start from a hypothesis instead of a blank query.

SLO alert · checkout availability burning 14×

Compared failing spans in Surface24 fields

Checked deploys in the last 6 hours3 found

Read error logs from checkout214 lines

Likely cause: app.version 4.2.0 in eu-west-2 Rolled out 38 minutes before the burn began.

Missing something you need?

Tell us at [email protected].