Here's how to set up a webhook to receive Splunk On-Call (Formerly VictorOps) alerts in Transposit.
Once configured, you can:
Follow the steps below to integrate Splunk On-Call alerts with Transposit.
Go to Settings > Webhooks, and click Add webhook. Choose Splunk On-Call (Formerly VictorOps), as shown below.
Note: The optional Slack channel must already exist, create it before adding the webhook.
Click Add and then find the webhook you just added in the list. Click Click to copy to copy the URL to the clipboard or manually copy the endpoint URL.
In Splunk On-Call, navigate to Integrations > Outgoing Webhooks and click Add Webhook, as shown below.
Set the Event dropdown to Incident-Triggered, the To field to the Endpoint URL you copied from Transposit, as shown below, and click Save.
Splunk On-Call is now setup to call this webhook for new incidents. You can test the webhook by creating an incident, as shown below.
When you click Create incident above, you should see events appearing in Transposit and, optionally, in Slack.
With Splunk On-Call webhooks set up, you can do the following in Transposit.
When a Splunk On-Call incident is triggered, you should see alerts displayed as events in Transposit, as shown below.
In Slack, if you defined the webhook in Transposit to support Slack, you should see Splunk On-Call alerts displayed, too, as shown below.
When an alert is received in Transposit or Slack via the Splunk On-Call webhook, click the Create activity button to create a new activity, add runbooks, and follow the progress of work done by your team in response to Splunk On-Call alerts.
If you have added runbook triggers based on Splunk-On Call alerts, the runbook will start automatically when a Splunk On-Call alert is received.
Alternatively, you can specify that the runbook should start only when an activity is created from the webhook, as shown below.
If you have defined dynamic Splunk On-Call alert parameters while adding runbook actions, as shown below, their values will be populated by the Splunk On-Call alert's payload when the actions are executed during runbook runs.