Alerts overview

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

Field	Description
Name	Title of the alert from the source platform
Source	datadog, grafana, or newrelic
Severity	critical, warning, or info
Signal type	errors, latency, traffic, or saturation (inferred)
Service	Extracted from alert tags or labels
Environment	Extracted from `env` / `environment` tags
Status	firing or resolved
Linked incident	Set 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.

Get Started

Incidents

Alerts

Root Cause Analysis

Postmortems

OpenTelemetry

Integrations

Platform

Status Page

Alerts overview

How alert routing works

Alert fields

Viewing alerts

Alert status lifecycle

Getting started with alert routing

Datadog

Grafana

New Relic

​How alert routing works

​Alert fields

​Viewing alerts

​Alert status lifecycle

​Getting started with alert routing

Datadog

Grafana

New Relic

How alert routing works

Alert fields

Viewing alerts

Alert status lifecycle

Getting started with alert routing