Debug production issues by instrumenting projects with Traceway and using the CLI to query logs, exceptions, metrics, and traces to root cause. Supports backends via OpenTelemetry and frontends/mobile via Traceway SDKs.
Traceway is an OpenTelemetry-native observability platform that combines logs, traces, metrics, session replay/RUM, exceptions, and AI tracing together. Point an OTLP exporter at it and you're in business. No Collector, no glue code, no per-language vendor SDK.
MIT licensed. No BSL. No "open core." Every feature is in the box. Self-host it for free, or run it on Traceway Cloud if you'd rather not babysit infra.
Session Replay — Watch what the user did right before the error. Available for web (any JS framework) and Flutter.
AI Observability — LLM cost, tokens, latency, and full conversations across providers (OpenRouter and any OTel-compatible AI gateway).
Plus: configurable alerts (Slack / GitHub / email / webhook / Pushover / Telegram), Apdex + Impact-Score endpoint ranking, multi-tenant orgs with role-based access, and a per-endpoint slow-threshold override.
AI-First
Your agent sets up Traceway, queries production telemetry, and finds the root cause:
npx skills add tracewayapp/traceway
One command installs two skills into Claude Code, Cursor, Codex, or any agent that reads SKILL.md:
/traceway-setup reads your repo and wires it up: OTel for backends, Traceway SDKs for web and mobile. Then it verifies data actually arrives.
/traceway installs the traceway CLI and uses it to query exceptions, logs, endpoints, and metrics, from bug report to root cause.
The CLI is designed for agents first: JSON when piped, tables on a TTY, stable error identifiers and exit codes, --fields to trim responses. It is read-only apart from archiving exceptions, which requires an explicit --yes, so nothing hangs and nothing gets damaged.
The skills are plain Markdown in skills/, in the same MIT-licensed repo. No marketplace, no lock-in. Learn more →
JavaScript Symbolication
app.min.js:1:63 tells you nothing. Traceway resolves minified production errors back to the original file, line, and function the moment they arrive.
The symbolicator is pure Go and built to keep up with ingest. Each source map compiles once into a binary .tw file and is memory-mapped from disk: under a microsecond to open a compiled map, p99 lookup under a millisecond on a cold cache, zero maps re-parsed after a restart. The corpus is a disk budget, not a RAM budget.
Skills, agents, and workflows for Honeycomb observability — query patterns, production investigations, SLOs, OpenTelemetry instrumentation, and Beeline migration. Designed to complement the Honeycomb MCP server.
OpenTelemetry
