Skip to main content
Obsy acts as a central alert hub. Alerts from your monitoring platforms arrive via webhook, get normalized into a common format, trigger RCA, and optionally create incidents — all without you having to log in to three different tools.

​
How alert routing works

Datadog / Grafana / New Relic
         ↓ webhook
  Obsy (per-org URL)
         ↓
  Normalized Alert entity
         ↓
  ┌──────┴──────┐
  │             │
RCA          Auto-create
triggered    incident rule
             check

​
Alert fields

FieldDescription
NameTitle of the alert from the source platform
Sourcedatadog, grafana, or newrelic
Severitycritical, warning, or info
Signal typeerrors, latency, traffic, or saturation (inferred)
ServiceExtracted from alert tags or labels
EnvironmentExtracted from env / environment tags
Statusfiring or resolved
Linked incidentSet when an incident is created from this alert

​
Viewing alerts

Go to Alerts in the sidebar. Use the filters at the top to narrow by status, severity, source, or service. Click any alert to see the raw payload, labels, and linked incident or RCA.

​
Alert status lifecycle

(Alert fires)
     ↓
  firing
     ↓
  acknowledged  ← manual or from incident assignment
     ↓
  resolved  ← when platform sends recovery

​
Getting started with alert routing

Datadog

Set up the @webhook-obsy handle in Datadog monitors.

Grafana

Add Obsy as a Grafana Alerting contact point.

New Relic

Configure a New Relic Workflow to POST to Obsy.