Skip to main content

Prerequisites

  • Your Splunk On-Call API key and API ID

Setup

Install the in Courier and enter your API key and API ID.
Splunk On-Call was formerly known as VictorOps. The API documentation at portal.victorops.com may redirect to Splunk’s current documentation.

Profile requirements

Splunk On-Call addresses the recipient by target type and slug, under splunk_on_call on the profile. Store it once with , which merges into the profile and creates it if it does not exist:
Then send to user_id and Courier resolves the address. For a one-off with no stored profile, pass it inline instead: "to": { "splunk_on_call": { "target": { "type": "User", "slug": "userSlug" } } }.

Send by user id

The call in every language, and the rest of the profile object.

Send to a recipient

Courier reads splunk_on_call off the saved profile, so preferences apply and the value can change without touching this code.

Template requirements

Provide a summary in the notification’s integration settings.

Overrides

covers the two levels and which one wins. You can override the API key, API ID, username, URL, and request body. This example overrides the API key and username through config:

Provider details

Courier recommends routing to the channel. Naming this key in routing.channels instead is supported, and sends through just this provider.

Send to a specific provider

When that is worth doing, and what you give up: failover, channel priority, and providers you add later.