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 connect Cortex entities to the SLOs you’ve defined in Splunk Observability Cloud. For configuration instructions, see Splunk Observability Cloud. For information on how to use the integration, see Using the integration for Splunk Observability Cloud.

Before you start

The access token in your Splunk Observability configuration needs read access to SLOs and to SignalFlow. Cortex reads each SLO’s definition, then runs its SignalFlow program to compute the SLO’s status.

Editing the entity descriptor

To link an entity to an SLO, add the SLO’s ID under x-cortex-slos.signalfx in the entity descriptor. You can list more than one SLO.
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 an SLO’s ID at the end of its URL in Splunk Observability Cloud: https://app.{REALM}.signalfx.com/#/slo/{ID}. Cortex links each SLO to an entity in this order:
  1. By ID: An entity lists the SLO’s id under x-cortex-slos.signalfx.
  2. By service: The SLO’s SignalFlow program filters on exactly one service, through sf_service, service.name, or service. Cortex links the SLO to the entity whose tag matches that service, ignoring case. An entity that lists SLO IDs isn’t linked this way.
An SLO that matches neither way is still reported, without an entity.
Last modified on November 17, 2026