> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sazabi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Splunk On-Call

> Connect Splunk On-Call (VictorOps) so Sazabi can route issues to your on-call rotation.

## Supported capabilities

Core integration

* **Core integration**: [Splunk On-Call](https://docs.sazabi.com/catalogs/integrations/victorops.md#core-integration) — Connect Splunk On-Call (VictorOps) so Sazabi can route issues to your on-call rotation.

Each connection method has its own setup and permissions. Connecting one method does not enable the others.

## Core integration

## About

Connecting Splunk On-Call (VictorOps) lets Sazabi route issues to your on-call rotation. Splunk On-Call is a shared [notification channel](https://docs.sazabi.com/guides/detect/notifications.md).

Sazabi triggers and resolves Splunk On-Call incidents as an issue opens and closes, mapping issue severity to the Splunk On-Call message type.

## Prerequisites

* A Splunk On-Call account.
* A REST integration **endpoint URL** and its **API ID**. The endpoint URL must be an HTTPS URL on a VictorOps or Splunk On-Call domain.
* Organization admin access in Sazabi.

## Set up in the dashboard

**Step 1**

### Get your REST endpoint URL and API ID

In Splunk On-Call, enable the REST endpoint integration and copy its
endpoint URL (it looks like
`https://alert.victorops.com/integrations/generic/...`) and your API ID.

**Step 2**

### Open the Splunk On-Call integration

In the dashboard, go to [**Settings > Integrations > Splunk On-Call**](https://app.sazabi.com/settings/integrations/victorops).

**Step 3**

### Enter the endpoint URL and API ID

Provide the **Endpoint URL** and **API ID**, then connect.

**Step 4**

### Add a delivery rule

On the project [**Settings > Notifications**](https://app.sazabi.com/settings/project-notifications) page, add a delivery rule that
routes an event type to the Splunk On-Call destination. See
[Route notifications](https://docs.sazabi.com/guides/detect/notifications.md).

## Set up with the CLI

You can also connect Splunk On-Call with the [Sazabi CLI](https://docs.sazabi.com/reference/cli.md) (installed and authenticated — see [CLI reference](https://docs.sazabi.com/reference/cli/integrations.md)).

Splunk On-Call is an API-key provider with two credential fields: the REST integration `endpointUrl` and its `apiKey` (the API ID). Read the API ID from an environment variable rather than pasting it inline:

```bash theme={"system"}
export VICTOROPS_API_ID=...   # your VictorOps API ID
sazabi integrations connect victorops \
  --credentials "{\"endpointUrl\":\"https://alert.victorops.com/integrations/generic/...\",\"apiKey\":\"$VICTOROPS_API_ID\"}"
```

Then add a delivery rule so issues reach Splunk On-Call — from the project [**Settings > Notifications**](https://app.sazabi.com/settings/project-notifications) page, or with the CLI (`sazabi notifications delivery-rules create`; see [Route notifications](https://docs.sazabi.com/guides/detect/notifications.md#delivery-rules)). Run `sazabi integrations list` to confirm the connection, or `sazabi integrations providers --json` to see each provider's credential fields.

## Notifications

Use Splunk On-Call as a delivery destination for issue and system events: on the project [**Settings > Notifications**](https://app.sazabi.com/settings/project-notifications) page, add a delivery rule that routes an event type to the Splunk On-Call destination. See [Route notifications](https://docs.sazabi.com/guides/detect/notifications.md).

## Verify

With a delivery rule pointing at the Splunk On-Call destination, trigger a test issue and confirm an incident appears in Splunk On-Call within a minute. Resolve the issue and confirm the Splunk On-Call incident resolves.

## Troubleshooting

**Endpoint URL rejected** — The URL must be HTTPS on a VictorOps or Splunk On-Call domain. Copy it directly from the REST endpoint integration.

**No incident in Splunk On-Call** — Confirm the delivery rule names both the event type and the Splunk On-Call destination, and that no condition excludes the issue.

## Further reading

> [card] [Route notifications](https://docs.sazabi.com/guides/detect/notifications.md)
>
> Route issues to Splunk On-Call with delivery rules.

> [card] [PagerDuty](https://docs.sazabi.com/catalogs/integrations/pagerduty.md)
>
> Another incident routing destination.

> [card] [Integrations](https://docs.sazabi.com/catalogs/integrations.md)
>
> Browse the full integration catalog.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.