Skip to main content
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 use the integration for Splunk On-Call. For configuration instructions, see Splunk On-Call. For instructions on connecting Splunk On-Call to entities, see Connecting entities to Splunk On-Call.

Viewing incident data

Incident list

See every imported incident and the entities it’s linked to in one place. To access the incident list:
  1. From the main sidebar, expand Integrations, then select Data.
  2. Select the Incidents tab.

Incidents on an entity’s details page

View incidents in the following places on an entity’s details page:
  • On the Overview tab, where active incidents appear at the top of the page
  • In the left details sidebar, under Connections > Incidents, on the Splunk On-Call tab

Incident assignees

Splunk On-Call doesn’t assign incidents, so Cortex treats the first person who acknowledged an incident as its assignee. If nobody acknowledged it, the person who resolved it is the assignee. An incident that Splunk On-Call resolved automatically has no assignee.

Mapping Splunk On-Call users to Cortex users

Cortex imports the users in your Splunk On-Call organization when you save the configuration, and again every night. It matches each one to the Cortex user with the same email address, and saves the match under their Splunk On-Call username. Users without a username aren’t imported. To review the matches or map users by hand:
  1. From the main sidebar, click your avatar in the bottom-left corner.
  2. Select Settings.
  3. Under Identity mappings, select Splunk On-Call.
See Configuring identity mappings for more detail.

Incident metrics in Eng Intelligence and OpEx Review

Splunk On-Call incidents count toward incident metrics in Eng Intelligence and OpEx Review, including:
  • Incident frequency
  • Mean time to resolution (MTTR)
To group these metrics by Incident assignee or Team, each assignee needs a mapping to a Cortex user. See Mapping Splunk On-Call users to Cortex users.

Viewing on-call information

Once an entity names its Splunk On-Call team, the user or team who is on call appears in the Current On-call block on that entity’s details page. You can also find on-call information on the On-call & incidents page in the entity’s sidebar.

Creating Scorecard rules with Splunk On-Call data

You can write Scorecard rules and CQL queries based on Splunk On-Call schedules. See more examples in the CQL Explorer in Cortex.
Definition: oncall (==/!=) null
This rule passes if an entity has a service, schedule, or escalation policy set.
Definition: oncall.numOfEscalations()
This rule checks that an entity’s escalation policy has at least two tiers, so there is a backup if the first on-call doesn’t acknowledge.
Definition: oncall.details()
This query finds every entity that the Splunk On-Call team sample-team1234 is on call for.

Viewing Splunk On-Call integration logs

This feature is available in Cortex cloud.
While viewing an integration’s settings page, select the Error logs tab to view errors from the last 7 days. You can filter the logs list by configuration and by operation (for example, you could filter to view errors surfaced only via Scorecards).
The 'Logs' tab on an integration's settings page shows error information over the past 7 days.
Click into a row to get more information, including time stamp, status code, full error, and request path.
Last modified on November 17, 2026