Owlpane / Solutions / Developers
Teams · built on OpenTelemetryDebug your own code in production — down to the query and the release.
Add one SDK line or point any OpenTelemetry exporter at Owlpane. Follow a slow request from the route handler to the SQL that caused it, see which release introduced an error, and debug per customer.
The problem
Why this is hard today
“Works on my machine”
Production behaviour is a black box without asking someone with dashboard access.
Proprietary agents
Vendor tracers and DSLs you have to learn and later rip out.
Customer tickets
A bug report for one account cannot be matched to that account’s requests.
What you use
Built from features that ship today
Requests and spans
The full waterfall — route handler, database queries, outgoing calls and background work.
APM & tracing →
Database queries
Database calls per service, one click from the request that issued them.
APM & tracing →
User activity
Accounts seen on requests via owlpane.setUser(), so you can debug per customer.
APM & tracing →
Errors tied to releases
Error groups with the release that introduced them and a sample trace.
APM & tracing →How it works
Three steps
Install
npm install @owlpane/node, or keep your OpenTelemetry SDK and change the exporter URL.
Ship
Set the release to your commit SHA so every deploy is comparable.
Debug
Open any request, error or customer and follow it to the line that matters.
import { owlpane } from "@owlpane/node";
owlpane.start({
service: "payments-api",
release: process.env.GIT_SHA,
});
owlpane.setUser(account.id);Questions
Which languages are supported?
Where Owlpane is narrower
- Owlpane wrappers for Python, Go, Java and Ruby are still in progress; plain OpenTelemetry works today.
Send a copy of your telemetry. Change nothing else.
Standard OpenTelemetry in, so you can try Owlpane beside what you run today.
Every new workspace starts with a 14-day Team trial: 50 GB of ingest a month and 30-day retention. No card to start. Documentation · Pricing · Pricing questions