Setup
1
Get your REST endpoint API key and routing key
- In Splunk On-Call, go to Settings → Integrations → REST Endpoint
- Enable the integration and copy the API key from the endpoint URL
- Go to Settings → Routing Keys and copy an existing key — or create a new one (e.g.
devhelm) mapped to the team that should receive alerts
2
Create the alert channel in DevHelm
3
Test the channel
Configuration
Lifecycle behavior
Splunk On-Call uses a trigger-resolve lifecycle keyed on the incident, so state stays in sync with DevHelm:Troubleshooting
Alerts not creating (HTTP 4xx)
Alerts not creating (HTTP 4xx)
Confirm you used the REST endpoint API key, not a personal API token from Settings → API. The two are different credentials — only the REST endpoint key works with this integration. Then run
devhelm alert-channels test <channel-id>.Incidents created but no one is paged
Incidents created but no one is paged
The routing key must be mapped to a team with an active escalation policy. In Settings → Routing Keys, verify the key points to the right team, then check that team has an on-call schedule.