Integrating Loadster with VictorOps (now Splunk On-Call)
VictorOps, also known as Splunk On-Call, simplifies your approach to incident response. Whenever one of your Speedway monitors fails or recovers, it will automatically create or update an incident in VictorOps. You can then set your own alert policies, route or escalate the issue automatically to whoever’s on call, and track of time to issue resolution across your entire organization.
It’s easy to integrate Loadster/Speedway with VictorOps!
The VictorOps integration is mainly of interest if you’re using Speedway, powered by Loadster, for site and API monitoring. You can enable and configure the VictorOps integration in either Loadster or Speedway, but it is mainly your Speedway monitors that trigger the integration to create incidents in VictorOps.
Enabling the VictorOps Integration
Go to the Integrations page of your Loadster or Speedway dashboard. Click the Enable VictorOps button in the VictorOps section.
You’ll be prompted for two things: a required Service API Key and an optional Routing Key. You’ll need to get these from your VictorOps account. To get a Service API Key that Loadster can use to communicate with VictorOps on your behalf, follow these steps:
- Log in to your VictorOps portal.
- Visit the Integrations tab.
- Find Loadster in the 3rd Party Integrations. If it’s not showing up, you can use the generic REST integration.
- Enable the Loadster integration.
- VictorOps will generate a Service API Key or Service API Endpoint that Loadster can use to communicate with the VictorOps API. If it’s a Service API Key, copy the key and paste it into Loadster. If it’s a Service API Endpoint, extract only the UUID portion of the URL near the end, and copy and paste it into Loadster.
You can also enter a Routing Key if you want incidents created by Loadster/Speedway to follow specific routing rules when they are sent to VictorOps. If you don’t have a Routing Key in mind, or don’t know what this is for, simply leave it blank or enter everyone.
Testing the VictorOps Integration
Now that the integration is enabled, each time one of your Speedway monitors fails, it will create an incident in VictorOps. Incidents usually show up in VictorOps within seconds. When the same monitor recovers, it will mark the incident resolved in VictorOps.
You can test the integration by creating a Speedway monitor that points to an invalid location, submits invalid data, or is otherwise broken, and confirm that it creates an incident in VictorOps.
We’re happy to assist you if you have any trouble with the Loadster integration with VictorOps. If you encounter a problem that’s not covered on this page, get in touch at firstname.lastname@example.org and we’ll work through it with you.