Integrate Postman with Splunk On-Call
Integrate Postman with Splunk On-Call
Splunk On-Call (formerly VictorOps) is a real-time incident management platform that handles incidents as they occur and prepares for the next one.
This integration enables you to configure Postman Monitors to trigger incidents on Splunk On-Call whenever it fails.
Get the Splunk On-Call API key
- Sign in to your Splunk On-Call account and click the Integrations tab.
- On the Integrations page, search and select the REST Generic Integration.
- If the integration isn’t already enabled, click Enable Integration. When the integration is enabled, the page displays a URL containing the API Key.
- Copy the API Key and save it for later.
Route alerts to specific teams
If you are using teams in Splunk On-Call, you can route alerts to specific teams by pairing routing keys with escalation policies.
- Click the Settings tab, then click Routing Keys.
- Click Add Key.
- Enter the API key you copied from the Integrations page and select an escalation policy.
Configure Postman Monitors
- On the Home page, click Integrations.
- Search for and select Splunk On-Call.
- Click Add Integration and enter the following:
- Nickname - A nickname for your integration.
- Choose workspace - The workspace that contains your monitor.
- Choose Monitor - Send this monitor’s results to Splunk On-Call.
- API Key - The API key from the Splunk On-Call Integrations page.
- Click Advanced Options if you want to add a Splunk On-Call routing key. This enables you to direct incidents to a specific team, so they get notified about a particular failure.
You can send the multiple monitors’ results to the same Splunk On-Call collection.
- Click Add Integration.
- Select the name of the integration you added to view the monitoring results.
You can view your configured integrations on the Integrations page. Configured integrations have a green dot in the upper right corner of the tile.
Incidents on Splunk On-Call
An incident on Splunk On-Call consists of basic information from a monitor that has failed, including the number of errors and failed tests. It also provides a direct link to the failing monitor. This integration automatically acknowledges a triggered incident if the next run succeeds.