VictorOps (Splunk On-Call) integration
Route HowlOps incidents into VictorOps so your existing on-call schedules handle the paging.
What this brings you
If your on-call rotation already lives in VictorOps (Splunk On-Call), you don't need to rebuild it in HowlOps. Connect VictorOps as a notification channel and every HowlOps incident is sent straight into it, where your existing schedules, escalation policies, and paging rules take over. HowlOps stays the monitor and incident source of truth; VictorOps stays the paging layer your on-call engineers already know.
Setup
- In VictorOps: go to Integrations > REST Endpoint (or the equivalent Alert Ingestion URL in your org), and note your API key and routing key. These identify your VictorOps organization and the escalation policy the alert should route to.
- In HowlOps, go to Settings > Notification channels > Add channel > VictorOps (Splunk On-Call).
- Enter the API key and routing key from step 1.
- Save the channel, then trigger a test alert to confirm it lands in the right VictorOps escalation policy.
The routing key determines which VictorOps escalation policy receives the alert. If alerts aren't reaching the on-call engineer you expect, check that the routing key matches the policy you intended.
See also
- Integrations reference for the exact field table.
- On-call & schedules for how HowlOps' own on-call rotations work, in case you want to run escalation from HowlOps directly instead.
Was this page helpful?