Metrics & monitoring

Send SolarWinds Orion alerts to on-call with CallHeim.

Orion/Observability alert action POST (Critical/Serious/Warning). CallHeim maps the payload, attaches repeats to the incident that is already open, and pages whoever is on call for the service it belongs to.

solarwindssource names also accepted: solar-winds, orion, swo

Set the payload template first

SolarWinds Orion posts to your CallHeim URL, but it only sends the fields you put in its payload template. Without one it sends an empty or differently shaped body that CallHeim cannot map, so set the template described in the setup steps before you point an alert at this integration.

Setting it up

Add a "Send a GET or POST request to a web server" alert action and template a JSON body.

Create an Integration in CallHeim and choose SolarWinds Orion from the Catalog. You get an ingest URL for that integration, which you paste into SolarWinds Orion’s webhook configuration. CallHeim’s ingest URL takes a JSON request body. The snippet beside this is the shape it expects, with {{WEBHOOK_URL}} replaced by your real URL.

SolarWinds Orion cannot sign its requests in a format CallHeim verifies, so the integration URL is the credential. Keep it secret, and if it is exposed, disable the integration and create a new one. Do not set a signing secret unless a signing proxy you run signs each request. With a secret set, every unsigned delivery is rejected.

CallHeim includes a payload mapping for SolarWinds Orion’s webhook format.

SolarWinds Orion documentation →

Setup snippetsolarwinds
# SolarWinds → Alerts → Manage Alerts → Trigger Actions → Add Action
# "Send a GET or POST request to a web server"   URL: {{WEBHOOK_URL}}
# Body: {"AlertName":"${N=Alerting;M=AlertName}","Severity":"...","AlertActive":true}
Check SolarWinds Orion’s current documentation for the exact fields.

After it arrives

What CallHeim does with SolarWinds Orion alerts.

Threshold alerts flap at the boundary. Where a source sends a recovery event CallHeim recognizes, a series that changes state four times inside ten minutes is grouped instead of re-paging, and the underlying incident stays open and visible.

CallHeim maps SolarWinds Orion’s severity or priority field to a P1 to P5 level where the source sends one, and shows a separate, explainable severity suggestion that a person can apply. How severity is suggested →

Each alert source is bound to a service, and the service’s escalation policy (or its team’s) sets who is paged. Alerting and escalation →

The thresholds it passes through

Repeat, sender-supplied dedup key
attaches, any age
Repeat, title or subject only
attaches, incident under 24 h old
Flap threshold
4 transitions / 600s
Title correlation
similarity ≥ 0.6, same source and service
Group window default
600s

All defaults are published. You can turn title correlation off or change its threshold, and set the window on your own noise rules; the dedup rule and the flap settings are fixed. A P1 or P2 repeat on an open P3 to P5 incident opens a new incident and pages. How alerts are processed →

CallHeim

Point SolarWinds Orion at CallHeim and see what it does with your alerts.

Start on the free trial, connect SolarWinds Orion and send a test alert to see the incident it opens.