ObsrvHQ fits into the stack you already run
One YAML config block connects ObsrvHQ to your metrics source. Your existing alertmanager, Grafana dashboards, PagerDuty policies: unchanged. ObsrvHQ is not a replacement for your observability stack. It is the filter layer that sits in front of it.
Connect your metrics source and incident routing
Reads your alerting rules via the Prometheus HTTP API. Observes metric time-series from your existing scrape targets. No changes to prometheus.yml or recording rules required.
Reads your Grafana unified alerting rule groups via the Grafana HTTP API. Requires Grafana 9+ with unified alerting enabled. Works alongside your existing Grafana contact points and notification policies.
Connects via Datadog API key. Reads your monitor definitions and metric time-series. Suppression decisions wrap around your existing monitors without modifying thresholds, notification channels, or monitor states.
Connects to your PagerDuty service routing. Suppressed decisions never create PagerDuty incidents. Only paged decisions flow through to your existing escalation policies and on-call schedules.
Connects to your Opsgenie team routing via API integration. Only paged decisions create Opsgenie alerts. Your team routing rules, responder assignments, and escalation schedules remain in place and unchanged.
New Relic NRQL alert condition support is in active development. Join the waitlist.
Splunk On-Call (formerly VictorOps) incident routing integration planned for Q3 2026.
Native Prometheus Alertmanager webhook receiver for direct integration without Prometheus source setup.
Prometheus integration walkthrough
The most common path. Prometheus with alerting rules is the default setup for most platform teams running Kubernetes. This walkthrough covers the full connection from Prometheus endpoint to first baseline.
Sign up and create a workspace
Sign up at obsrvhq.com and create a workspace for your organization or environment. Your API key is generated during workspace creation. Takes under 60 seconds.
Add one YAML block
Add the ObsrvHQ config block to a new obsrvhq.yaml file. Point it at your Prometheus HTTP API endpoint. ObsrvHQ reads your alerting rules and begins observing metric time-series immediately on startup.
obsrvhq: source: prometheus endpoint: http://prometheus:9090 api_key: ${OBSRVHQ_API_KEY}
Baselines build automatically
ObsrvHQ watches every metric series and builds per-hour, per-weekday baseline envelopes during the learning window. All alerts pass through unchanged until the window completes. After 48 hours, suppression begins. No further configuration from you.
Running a different stack?
Email [email protected] with your metrics source and incident routing tools. New Relic NRQL conditions and Alertmanager native webhook are in active development. We prioritize by demand.