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
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 underx-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}.
How SLOs link to entities
Cortex links each SLO to an entity in this order:- By ID: An entity lists the SLO’s
idunderx-cortex-slos.signalfx. - By service: The SLO’s SignalFlow program filters on exactly one service, through
sf_service,service.name, orservice. 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.