Telemetry built for agents.
Give your coding agent a prompt, an API key, and skill.md. It can instrument structured logs fast, while humans stay aligned with dashboards, charts, tables, and alerts.
Works well with Claude, Codex, Cursor, and custom agents.
Agent-native workflow
Give the agent the setup. Keep the humans on the signal.
Telemetry is built for the handoff. Agents can instrument real workflows fast, and your team gets dashboards, tables, and alerts that make the output legible.
Agent Prompt
Point your agent at skill.md, hand it an API key, and let it wire the first structured events without a long setup doc.
Structured Events
Capture clean snake_case fields for status, latency, identifiers, costs, and errors so the resulting tables stay easy to query.
Readable Dashboards
Turn agent-written logs into charts and tables that operators, founders, and teammates can scan in seconds.
Alerts
Track the metrics your agents add and notify the team when latency, failures, or costs move out of bounds.
Query API
Agents and humans can run SQL on the same data when dashboards need deeper investigation or custom reports.
Shared Workspace
Saved dashboards, queries, and tables give automation and operators one source of truth instead of fragmented scripts.
Start with a prompt, not a setup doc
Copy this into Claude, Codex, Cursor, or your own coding agent. The prompt points to skill.md, asks the agent to instrument the project with structured logs, and asks it to create a high-level dashboard with charts and tables.
Paste this into your coding agent
Instrument this project with structured logs using /skill.md.
Use this Telemetry API key: YOUR_API_KEY
Please:
1. Find the most important user-facing flows, background jobs, and AI/tooling workflows.
2. Add structured logging with pragmatic snake_case tables and fields.
3. Capture the key signals for each workflow, including status, latency, identifiers, and error context when relevant.
4. Send test events to Telemetry and verify that ingestion works.
5. Create a high-level dashboard with charts and tables that summarize the most important signals in this project.
6. Tell me what you instrumented, which tables you created, and which dashboard views I should review first.
Prefer small, composable events over giant payloads, and optimize for dashboards that humans can scan quickly.YOUR_API_KEY after signup and let the agent do the first pass.Humans can come back to refine the schema, add alerts, or expand the dashboard once the first workflows are visible.
Trusted by builders
Teams use Telemetry to turn raw structured events into something humans can actually understand.
“Telemetry makes it super easy to track, analyze, and visualize what's going on in my business. It's the perfect mix of simple and powerful.”
Namu Kang
Founder, Browserflow
“Telemetry is one of the easiest ways to go from dumping in your data to actually understanding it.”
Shayan Taslim
Founder, LogSnag
“Telemetry is my go-to for dumping logs and tracking events. It's straightforward, the SQL workbench is fast, and I don't have to worry about the schema upfront. Running SQL over a REST API lets me fetch data and dump reports straight to Slack. It's the essentials of what Sentry did for me.”
Prem Viswanathan
Founder, SwiftCX
Give the agent the prompt. Give the team the dashboard.
Telemetry is the handoff layer between automated instrumentation and human-readable operations.