Getting Started
TracePath is a hosted, OpenTelemetry-native observability platform: traces, logs, metrics, exceptions, profiles, AI/LLM tracing, synthetic monitors, status pages and on-call paging, in one workspace, operated by us. Session replay is built but waits on the browser SDK, which has not shipped — see Sessions.
There is nothing to install and nothing to run. You create an account, create a project, and point an OpenTelemetry exporter at the ingest endpoint.
The three hosts
TracePath is split across three hostnames, and which one you use depends on what you are doing. Mixing them up is the most common first-day mistake.
| Host | What it serves |
|---|---|
https://app.tracepath.dev | The dashboard, the HTTP API, sign-up and sign-in, source-map and symbol uploads |
https://ingest.tracepath.dev | Telemetry only — the OTLP endpoints your exporters write to |
https://docs.tracepath.dev | These docs |
Your exporter talks to the ingest host with a project token. Everything else — the dashboard, the API, the CLI — talks to the app host with your own credentials. The two kinds of credential are not interchangeable.
One integration path
TracePath speaks vendor-neutral OpenTelemetry over OTLP/HTTP, and that is the whole integration surface:
POST https://ingest.tracepath.dev/api/otel/v1/traces
POST https://ingest.tracepath.dev/api/otel/v1/metrics
POST https://ingest.tracepath.dev/api/otel/v1/logs
Authorization: Bearer <project token>Any OpenTelemetry SDK, any auto-instrumentation agent, or an OpenTelemetry Collector in front of them can send to those paths. TracePath publishes no SDK of its own, no CDN script and no installer, so an application that already exports OTel needs no new dependency at all — just a different endpoint and one header.
OTLP over gRPC is not supported. Set your exporter's protocol explicitly to
http/protobuf (or http/json); several SDKs default to gRPC and fail silently
when the variable is unset.
Where to go next
- TracePath Cloud — sign up, create a project, and get your first trace on screen. Start here.
- OpenTelemetry Integration — the full configuration reference, plus per-language guides for Node.js, Python, Go, Java, PHP and .NET.
- Architecture Overview — how spans become endpoints, tasks, issues and AI traces, and what the dashboard is actually showing you.
- Billing and plans — plan limits, how the ingest quota is metered, and exactly what happens when you reach it.
- Security — the controls that protect your data, and the ones we do not have.
- API reference — personal access tokens and the HTTP API behind the dashboard.
Getting help
Email [email protected] for anything about your account, your data or a broken integration. Security reports go to [email protected] — see Reporting a vulnerability.