# Integrating Loadster with VictorOps (now Splunk On-Call)

> How to integrate Loadster with VictorOps (now Splunk On-Call) for fast incident routing and resolution.

Source: https://loadster.com/manual/integration-with-victorops/

[VictorOps](https://victorops.com), also known as Splunk On-Call, simplifies your approach to incident response.
You can set your own alert policies, route or escalate the issue automatically to whoever is on call, and track of
time to issue resolution across your entire organization.

If you're using Loadster for [Site & API Monitoring](https://loadster.com/manual/monitoring/), whenever one of your monitors fails or
recovers it will automatically create or update an incident in VictorOps.

It's easy to integrate Loadster with VictorOps!

## Enabling the VictorOps Integration

Go to the <a href="https://loadster.com/dashboard/integrations">Integrations</a> page of your Loadster 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:

1. Log in to your VictorOps portal.
2. Visit the **Integrations** tab.
3. Find Loadster in the **3rd Party Integrations**. If it's not showing up, you can use the generic REST integration.
4. Enable the Loadster integration.
5. 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 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 Loadster 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 Loadster monitor that points to an invalid location, submits invalid data,
or is otherwise broken, and confirm that it creates an incident in VictorOps.

## Getting Help With the VictorOps Integration

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 [help@loadster.com](mailto:help@loadster.com) and we'll work through it with you.