Visual tour
This page walks through the Owlpane console area by area so you know what each surface is for before you sign in. The rendered diagrams below are the static views that ship with these docs; live screenshots are always available in the console itself at console.owlpane.com.
Platform context
The System Context diagram shows how applications, Owlpane SDKs, OpenTelemetry collectors, and Kubernetes agents reach the platform, and how queries return through the console.
Home
Home (/home) is your workspace-wide snapshot: firing and acknowledged alerts, service health cards ordered by severity, stacked log volume, recent alert events, and What changed. The Assistant tab hosts natural-language queries and guided workflows. This is the first screen after sign-in and the fastest place to notice that something is off.
Applications → Overview
Applications → Overview (/observability) is where application and frontend performance live: request throughput, 5xx/4xx rates, p50/p95/p99 latency by route, and Core Web Vitals for front-end apps instrumented with the browser SDK.
Setup and ingest
Setup (/observability/setup) is where you create ingest keys and copy the ingest endpoint. The Ingest & Query Dataflow diagram shows what happens after a collector posts to /v1/traces, /v1/metrics, or /v1/logs — authentication, partitioning, compaction, and query.
Logs, Metrics, and Traces explorers
The three telemetry explorers share one query bar and one time range:
| Area | What you do |
|---|---|
| Logs explorer | Full-text and field search over log streams. |
| Metrics explorer | PromQL-style metric expressions and instant/range views. |
| Traces & requests | Distributed trace search, waterfall views, and per-request detail. |
Dashboards hub
Dashboards (/observability/dashboards) is a single hub for custom dashboards, one-click installs from Library, Built-in templates, and JSON import/export. The Dashboard Lifecycle diagram shows how library packs, templates, and importers feed the hub.
Alerts and On-call
Alerts, monitors, and SLOs live alongside On-call schedules and escalations. When a monitor fires, the event lands on the incident timeline and routes to your configured destinations — Slack, PagerDuty, webhooks, and the mobile/desktop apps.
Infrastructure and the Kubernetes agent
Infrastructure surfaces Kubernetes, hosts, and integrations. Once the Helm agent is running, its cluster, node, and pod telemetry appear here under your cluster.name. The Deployment Topology diagram gives the shape of how the pieces fit together.
Status pages
Uptime monitors can publish a public status page from the console. A published status page is reachable at /status/:slug on the console host, so you can share service health outside your workspace.
AI assistants
The in-console assistants answer questions over your own telemetry, summarise incidents, and drive guided workflows. They are documented under the user guide, with their own privacy notes.
Related
Last updated