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

# Connecting entities to Splunk On-Call

PUBLIC BETA

> [!NOTE]
>
> Cortex connects to many third-party vendors whose system interfaces frequently change. As a result, integration behavior or configuration steps may shift without notice. If you encounter unexpected issues, check with your system administrator or refer to the vendor's documentation for the most current information. Additionally, integration sync times vary and are subject to scheduling overrides and timing variance.

This article explains how to connect Cortex entities to Splunk On-Call. For configuration instructions, see [Splunk On-Call](https://docs.cortex.io/ingesting-data-into-cortex/integrations/splunk-oncall). For information on how to use the integration, see [Using the integration for Splunk On-Call](https://docs.cortex.io/ingesting-data-into-cortex/integrations/splunk-oncall/using-the-integration-for-splunk-oncall.md).

## Before you start

To import incidents, the Splunk On-Call configuration must include the **Incidents** category:

1. In Cortex, open the [Splunk On-Call settings page](https://app.getcortexapp.com/admin/integrations/splunk-oncall).
2. Edit the configuration and select both **On-call** and **Incidents** under **Category**.
3. Click **Save**.

## Editing the entity descriptor

An entity's `x-cortex-oncall.victorops` block names the Splunk On-Call team that supports it. Cortex uses that team for the entity's on-call schedule and to link incidents to the entity. To narrow the link to specific escalation policies, add `policyIds`.

> [!NOTE]
>
> The YAML examples on this page show only the `x-cortex-*` block. When you add one to an entity descriptor, nest it inside the `info` section. Blocks at the root level of the file are ignored without an error. For a full example, see [Defining entities with YAML](https://docs.cortex.io/ingesting-data-into-cortex/entities-overview/entities/yaml#metadata-in-entity-descriptor-yaml-files).

```yaml theme={null}
x-cortex-oncall:
  victorops:
    type: SCHEDULE
    id: team-abcd12345
    policyIds:
      - 12345
      - 56789
```

| Field | Description | Required |
| - | - | :-: |
| `type` | Type of on-call data (in this case, `SCHEDULE`) | **✓** |
| `id` | ID of the Splunk On-Call team that supports the entity | **✓** |
| `policyIds` | Escalation policy IDs that limit which pages link to the entity | |

You can find the team ID in the Splunk On-Call portal on the teams page (e.g., `https://portal.victorops.com/dash/cortex-app#/team//users`).

## How incidents link to entities

An incident links to an entity when it paged the entity's team. If the entity lists `policyIds`, the incident must also have paged one of those policies on that team. An incident can link to more than one entity.

When you change an entity's team or policies, Cortex re-links the existing incidents that paged the old or the new team.


## Related topics

- [Using the integration for Splunk On-Call](https://docs.cortex.io/ingesting-data-into-cortex/integrations/splunk-oncall/using-the-integration-for-splunk-oncall.md)
- [Connecting entities to Datadog](https://docs.cortex.io/ingesting-data-into-cortex/integrations/datadog/connecting-entities-to-datadog.md)
- [Splunk On-Call (VictorOps)](https://docs.cortex.io/ingesting-data-into-cortex/integrations/splunk-oncall.md)
