IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
Elastic Docs ›Elastic Observability [8.8] ›SLOs
« SLOs Create a service-level objective (SLO) »

Configure service-level objective (SLO) accessedit

This functionality is in beta and is subject to change. The design and code is less mature than official GA features and is being provided as-is with no warranties. Beta features are not subject to the support SLA of official GA features.

You can create the following roles for your SLOs:

  • SLO All — Create, delete, and see SLOs and their historical summaries.
  • SLO Read — See SLOs and their historical summaries.

To create a role:

  1. From the left navigation in Kibana, under Management select Stack Management.
  2. Under Security, select Roles.
  3. Click Create role in the upper-right corner of the page.

Create an SLO All roleedit

Set the following privileges for the SLO All role:

  1. Under Cluster privileges in the Elasticsearch section, add manage_index_template, manage_ilm, manage_pipeline, and manage_transform to the Cluster Privileges field.

  2. Under Index privileges, add .slo-* to the Indices field and all to the Privileges field.

    slo es priv all
  3. In the Kibana section, click Add Kibana privilege.

  4. Set Observability → SLOs to All.

    slo kibana priv all

Create an SLO Read roleedit

Set the following privileges for the SLO Read role:

  1. Under Index privileges in the Elasticsearch section, add .slo-* to the Indices field and read to the Privileges field.

    slo es priv read
  2. In the Kibana section, click Add Kibana privilege.

  3. Set Observability → SLOs to Read.

    slo kibana priv read
« SLOs Create a service-level objective (SLO) »