TracePath

TracePath is a hosted, OpenTelemetry-native monitoring platform. It gives you real-time visibility into your application's health through exception tracking, endpoint latency, background tasks, logs, metrics and synthetic monitors.

Create an account at app.tracepath.dev/register (opens in a new tab), create a project, and copy its token from the Connection page. That token is all an integration needs.

First time here? Read Project Structure first: one project per backend system, per browser app, and per mobile app.

Send data with OpenTelemetry

OpenTelemetry over OTLP/HTTP is the integration path for TracePath. It is vendor-neutral, it exists for every language TracePath supports, and it needs nothing TracePath-specific in your application beyond an endpoint and a header.

Start at the OpenTelemetry guide. It carries per-framework walkthroughs for Node.js, NestJS, Next.js, Hono, Cloudflare Workers, Python, Django, Symfony and Laravel, and the generic setup covers everything else — Go, Java, .NET, Ruby, Rust, and anything with an OTLP exporter.

Send AI traces from OpenRouter

If your LLM calls go through OpenRouter (opens in a new tab), you can point its Observability broadcast at the same OTLP endpoint and get model, token, cost and conversation data in TracePath without touching your code. See the OpenRouter integration.

Browser and mobile SDKs

Each planned SDK still has a page describing what it will cover, what it will capture automatically, and which parts of it already exist on the server side — source map and symbol upload, for instance, work today and have nothing to resolve only because no client is sending frames yet.

Server-side code in a JavaScript, Python, PHP or Go project is not waiting on any of this — it instruments with OpenTelemetry today. Only the browser and mobile halves are pending.

Want to be told when one of them ships? Email [email protected].

Choose your framework

OpenTelemetryEvery backend, whatever the language: Go, Node.js, Python, PHP, Java, .NET, Ruby. Start here.OpenRouterAI observability for LLM calls routed through OpenRouter. Point its OTLP broadcast at TracePath; no code changes.ReactComing soonPlanned browser SDK for React apps. Server code in a Next.js or Remix project uses OpenTelemetry today.Vue.jsComing soonPlanned browser SDK for Vue 3, with a plugin and composables.SvelteComing soonPlanned browser SDK for Svelte and SvelteKit, using the context API.jQueryComing soonPlanned browser SDK for jQuery apps, including automatic AJAX error capture.JS GenericComing soonThe framework-agnostic browser SDK the packages above share. Planned.FlutterComing soonPlanned Flutter SDK with automatic error capture and screen recording.React NativeComing soonPlanned React Native and Expo SDK with exception, fetch / XHR and console capture.AndroidComing soonPlanned native Android (Kotlin/Java) SDK with exception, log, HTTP and navigation capture.iOSComing soonPlanned native iOS (Swift) SDK with automatic crash and exception capture.

Next steps

• OpenTelemetry: the integration path that works today
• Project Structure: how to split your systems into TracePath projects
• Monitors: synthetic uptime checks, which need no instrumentation at all