Owlpane docs
Everything you need to run observability in one workspace
Ingest OTLP telemetry, explore logs and traces, install dashboard packs, alert your on-call rotation, and connect IDE agents — documented to match the console you use every day.
Press ⌘K in the sidebar to search pages and integration names.
Common tasks
Start here
Follow these five steps in order — from first ingest key to on-call.
- 1WorkspaceCreate a workspace, ingest key, and open the console.
- 2IngestSend OTLP logs, metrics, or traces from your app or agent.
- 3ExploreSearch logs, filter traces, and inspect request sessions.
- 4VisualizeInstall dashboard packs from the library or import JSON.
- 5AlertWire alert rules and on-call schedules to your team.
Browse by section
What Owlpane is, architecture, workspace setup, and your first OTLP payloads.
What each signal and surface does — logs, metrics, traces, dashboards, alerting, RUM, AI, and Carbon.
OTLP HTTP/gRPC endpoints for logs, metrics, and traces with workspace ingest keys.
Logs, traces, alerts, session replay, dashboards, and on-call — aligned to console routes.
Pre-built dashboard and ingest guides for databases, cloud, Kubernetes, and apps.
Language SDKs, browser RUM, Helm agent, and host collectors.
Plans and billing, members and roles, SSO, API tokens, projects and ingest keys, quotas.
Environment variables, the OTLP contract, agent Helm values, and the control-plane API.
Investigation assistants, MCP tools, and API tokens for IDE agents.