OwlpaneDOCS
Features

Features

Owlpane is a hosted observability platform. You reach every capability through the web console at console.owlpane.com, send telemetry to ingest.owlpane.com, and manage workspace configuration through api.owlpane.com. This section is the concept layer of the documentation: each page explains what a surface is, the capabilities it exposes, the exact console routes it occupies, and how telemetry reaches it.

Task-oriented walkthroughs live in the user guide. Wire-level ingest detail lives under ingestion and the integration library.

How each page is organised

Every feature page follows the same shape so you can jump straight to what you need:

  1. What it is — the surface in one paragraph, and why it matters.
  2. Key capabilities — the things you can do without leaving the console.
  3. Where it lives — the exact console routes, as console.owlpane.com paths.
  4. How data gets in — the SDK, collector, agent, or integration that feeds it.
  5. Related — deeper concept and task pages.

Surface map

Every console surface, its route, and what it does. Routes are shown relative to console.owlpane.com.

SurfaceConsole routeWhat it does
Logs explorer/observability/logsFull-text and structured search over log records, with a volume histogram, facets, and trace correlation.
Log settings/observability/log-settingsRetention, volume, storage layout, and the masking/rewrite rules applied before lines are shown or exported.
Search jobs/observability/search-jobsRun long-range Logs SQL queries in the background, download the rows, and schedule recurring searches.
Metrics explorer/observability/explorerChart any metric with an aggregation, a group by, and filters; the whole view lives in the address bar.
PromQL/observability/promqlWrite and run a PromQL subset with live validation.
Profiler/observability/profilerProcess CPU, memory, heap, event loop, and GC for Node APIs, plus browser page performance.
GPU profiler/observability/profiler/gpuGPU-oriented profiling alongside the standard profiler.
Traces hub/observability/tracesEntry point for trace search, opening onto Requests, Spans, and Service map.
Traces → Requests/observability/traces/requestsHTTP/RPC request list for API services, with a span waterfall per request.
Traces → Spans/observability/traces/spansBroader span search when you already hold a trace or span ID.
Traces → Service map/observability/traces/service-mapTopology graph of service-to-service edges with error and latency signals.
Request detail/observability/requests/:traceIdOne request's waterfall, service graph, and correlated logs.
Dashboards/observability/dashboardsWorkspace hub for creating, browsing, and organising dashboards.
Dashboard library/observability/dashboards/libraryCurated integration dashboard packs installed with one click.
Built-in templates/observability/dashboards/templatesStarter golden-signal, Kubernetes, database, and LLM templates.
Dashboard import/observability/dashboards/importPaste or upload a JSON dashboard definition.
Dashboard view/observability/dashboards/:idRender an individual dashboard with its variables and time range.
Alerts/observability/alertsThreshold, log-pattern, job, and error rules evaluated every minute, with history and notification volume.
Alert channels/observability/alert-channelsDestinations for alerts, SLO burn, and uptime incidents, plus workspace notification defaults.
Workflows/observability/workflowsNotification and ticketing steps that run when an alert fires or resolves, or an incident is declared.
SLOs/observability/slosReliability targets with error budgets and multi-window burn-rate alerts.
Escalation policies/observability/escalation-policiesWho is notified, and after which delay, when an alert keeps firing.
Incidents/observability/incidentsExternal Jira and ServiceNow issues opened from alerts, with acknowledgment sync.
Declared incidents/observability/declared-incidentsIncidents declared by you, as opposed to ones opened automatically.
Incident timeline/observability/timelineChronological view of incident events across the workspace.
Scheduled reports/observability/reportsEmail a dashboard snapshot on a cadence.
Browser (RUM)/observability/browserCore Web Vitals, navigation timing, pages, JavaScript errors, and fetch/XHR from real users.
Session replay (Beta)/observability/browser/replayReplay masked DOM events for a browser session.
Journeys/observability/journeysTrack how many real visitors complete a multi-page flow and whether linked checks pass.
Synthetics/observability/syntheticsOutside-in API, TLS, TCP, SSH, DNS, and browser checks that open incidents on repeated failure.
Private locations/observability/synthetics/locationsManage private probe locations.
Infrastructure overview/observability/infrastructureFleet health across Kubernetes, data platforms, hosts, and cloud scrapes.
Infrastructure → Hosts/observability/infrastructure/hosts (/hosts/:name)Node and VM metrics, aggregated and per host.
Infrastructure → Databases/observability/infrastructure/databases (/databases/:instanceId)PostgreSQL, MySQL, and MongoDB metrics with instance detail.
Infrastructure → Data stores/observability/infrastructure/data-storesRedis and in-memory cache metrics.
Infrastructure → Messaging/observability/infrastructure/messagingKafka and RabbitMQ integration views.
Infrastructure → Network devices/observability/infrastructure/network-devices (/topology, /flows)Interface inventory, device topology, and flow views.
Infrastructure → Cloud/observability/infrastructure/cloud (/aws, /gcp, /azure)Scraped cloud provider resources, per provider.
Infrastructure → Maintenance/observability/infrastructure/maintenanceMaintenance windows that suppress infrastructure noise.
Kubernetes 360/observability/infrastructure/kubernetesCluster hub for logs, metrics, traces, and incidents.
Kubernetes/observability/kubernetes (/explorer, /nodes/:node, /pods/:namespace/:pod, /workloads/:kind/:namespace/:name, /services/:namespace/:name, /ingresses/..., /certificates/...)Cluster detail and explorers for nodes, pods, workloads, services, ingresses, and certificates.
Applications overview/observabilityApplications hub (APM): API traffic and front-end RUM side by side.
Applications/observability/applicationsApplication inventory with per-app focus.
Services/observability/servicesService health and per-service drill-down.
Errors/observability/errorsExceptions grouped by failure — unhandled versus handled — plus browser JavaScript errors.
Jobs/observability/jobsBackground job health.
Releases/observability/releasesRelease markers and delivery activity.
User activity/observability/usersReal-user and account activity views.
Runtimes/observability/runtimes/:runtimeRuntime-specific telemetry boards.
Serverless/observability/serverlessServerless function telemetry.
Database queries/observability/database-queriesQuery-level database performance.
AI assistant/observability/agent (chat /observability/agent/chat, filters, automations, auto-tune)Chat, filter building, rule runs, and hot-path analysis.
AI Teammates/observability/ai-teammatesRole-based teammates with human-in-the-loop briefings and an approval queue.
LLM observability/observability/llm (/sessions, /evals)Latency, errors, tokens, and cost across LLM and agent traffic, with session and quality views.
Carbon/observability/carbon (/detail, /nodes, /namespaces, /hosts, /jobs, /gpu, /billing, /compare, /budget, /recommendations, /regressions, /diet, /factors)SCI-based energy, operational and embodied CO₂e, water, and cost attribution.
Security findings/observability/catalog/findingsSecurity and posture findings.
SIEM detection rules/observability/siemDetection rules over security telemetry.
Delivery → CI/observability/catalog/ciContinuous-integration pipeline telemetry.
Usage / cost/observability/costWorkspace usage and cost views.
Pipelines/observability/pipelinesIngest pipelines that transform telemetry before it is stored.
Redaction (signal control)/observability/signal-controlControls that decide what is kept, hidden, or rewritten.
Export (as-code)/observability/as-codeManage dashboards, monitors, and configuration as code.
Device fleets (Beta)/observability/device-fleets/*Register edge devices, run the observability scorecard, and review the fleet risk inbox.
Catalog/observability/catalog/:pageLong-tail catalog pages such as notebooks, events, work items, agent samples, governance, storage, and autoscaling.

Beta surfaces

Two surfaces are marked Beta in the console. Treat them as suitable for evaluation, not as settled contracts:

  • Device fleets (/observability/device-fleets/*) — OTLP telemetry plus a Postgres inventory, a scorecard, and a risk inbox. See Device fleets.
  • Session replay (/observability/browser/replay) — masked DOM replay for a browser session, subject to the replay retention caps below.

Plans and limits

Feature gates are set per plan. The console reads them from the plan entitlements, so what you see depends on your workspace plan.

CapabilityPlans
Every alert channel kind, the Slack app, importing on-call schedules, Kubernetes cluster count, on-call schedule count, Carbon attribution and Carbon report exportAll plans
Per-project ingest controls (keep ratio, bytes-per-minute cap, dropped signals); sending snapshots to your own object-storage bucketTeam and above
SSO routing and enforcement, audit-log export, dedicated ingest endpoints, restricting a member to specific Kubernetes namespacesScale and Enterprise
Session replay retentionStarter 7 days · Team 30 days · Scale/Enterprise 90 days
Audit retentionStarter 30 days · Team 365 days · Scale/Enterprise unlimited (≤ 3650)
Carbon query windowStarter 7 days · Team and above 30 days

See Plan and billing and Quotas and limits for the full picture.

How data gets in

Every surface is fed by the same ingest path. Send OpenTelemetry traffic — logs, metrics, and traces — to ingest.owlpane.com with a workspace-scoped owl_ing_* key, or use a published Owlpane SDK or integration.

Last updated

On this page