Splunk On-Call
Connect Splunk On-Call (VictorOps) so Sazabi can route issues to your on-call rotation.
About
Connecting Splunk On-Call (VictorOps) lets Sazabi route issues to your on-call rotation. Splunk On-Call is a shared notification channel.
Sazabi triggers and resolves Splunk On-Call incidents as an issue opens and closes, mapping issue severity to the Splunk On-Call message type.
Prerequisites
- A Splunk On-Call account.
- A REST integration endpoint URL and its API ID. The endpoint URL must be an HTTPS URL on a VictorOps or Splunk On-Call domain.
- Organization admin access in Sazabi.
Set up in the dashboard
Get your REST endpoint URL and API ID
In Splunk On-Call, enable the REST endpoint integration and copy its
endpoint URL (it looks like
https://alert.victorops.com/integrations/generic/...) and your API ID.
Open the Splunk On-Call integration
In the dashboard, go to Settings > Integrations > Splunk On-Call.
Enter the endpoint URL and API ID
Provide the Endpoint URL and API ID, then connect.
Add a delivery rule
On the project Settings > Notifications page, add a delivery rule that routes an event type to the Splunk On-Call destination. See Route notifications.
Set up with the CLI
You can also connect Splunk On-Call with the Sazabi CLI (installed and authenticated — see CLI reference).
Splunk On-Call is an API-key provider with two credential fields: the REST integration endpointUrl and its apiKey (the API ID). Read the API ID from an environment variable rather than pasting it inline:
export VICTOROPS_API_ID=... # your VictorOps API ID
sazabi integrations connect victorops \
--credentials "{\"endpointUrl\":\"https://alert.victorops.com/integrations/generic/...\",\"apiKey\":\"$VICTOROPS_API_ID\"}"Then add a delivery rule so issues reach Splunk On-Call — from the project Settings > Notifications page, or with the CLI (sazabi notifications delivery-rules create; see Route notifications). Run sazabi integrations list to confirm the connection, or sazabi integrations providers --json to see each provider's credential fields.
Notifications
Use Splunk On-Call as a delivery destination for issue and system events: on the project Settings > Notifications page, add a delivery rule that routes an event type to the Splunk On-Call destination. See Route notifications.
Verify
With a delivery rule pointing at the Splunk On-Call destination, trigger a test issue and confirm an incident appears in Splunk On-Call within a minute. Resolve the issue and confirm the Splunk On-Call incident resolves.
Troubleshooting
Endpoint URL rejected — The URL must be HTTPS on a VictorOps or Splunk On-Call domain. Copy it directly from the REST endpoint integration.
No incident in Splunk On-Call — Confirm the delivery rule names both the event type and the Splunk On-Call destination, and that no condition excludes the issue.