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.
Before you start
To import incidents, the Splunk On-Call configuration must include the Incidents category:- In Cortex, open the Splunk On-Call settings page.
- Edit the configuration and select both On-call and Incidents under Category.
- Click Save.
Editing the entity descriptor
An entity’sx-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.
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.
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 listspolicyIds, 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.