Learn Traceway

Traceway is an observability platform. Applications send telemetry: OpenTelemetry over OTLP/HTTP from backends, and the Traceway SDKs from browser and mobile apps. Traceway turns it into issues, request and task analytics, traces, logs, metrics and dashboards, session replay, AI cost tracking and profiles. On top of that it runs uptime monitors, public status pages, alerting and on-call paging.

This guide explains every part of the product: what each page shows, the terms it uses, how teams are meant to use it, and how an agent reads or changes it through the traceway CLI or the MCP server.

How to use this guide

• Answer "how does X work", "where do I find X" and "what does X mean" from the topic files below. Read only the one or two the question needs.
• Quote the exact names the dashboard uses (tab names, buttons, rule types), so the user can find them.
• When the user wants live data, switch to the traceway skill (or the MCP tools): it holds the debugging and performance playbooks.
• When the user wants something changed, the traceway-write skill covers the changes agents are allowed to make. Everything else is done in the dashboard, and the topic files say so.
• When the user wants an application instrumented, use the traceway-setup skill.

Core ideas