IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.

« SLOs Create a service-level objective (SLO) »

› ›

Configure service-level objective (SLO) access

edit

Configure service-level objective (SLO) access

edit

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, edit, and manage SLOs and their historical summaries.
SLO Read — See SLOs and their historical summaries.

To create a role:

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

Create an SLO All role

edit

Set the following privileges for the SLO All role:

Under Cluster privileges in the Elasticsearch section, add manage_transform.
Under Index privileges, add .slo-* to the Indices field and all to the Privileges field.
Click Add index privilege
Add indices you plan to create SLOs for to the Indices field, and add read and view_index_metadata to to the Privileges field.
In the Kibana section, click Add Kibana privilege.
From the Spaces dropdown, either select any specific spaces you want the role to apply to, or select All Spaces.
Set Observability → SLOs to All.

Create an SLO Read role

edit

Set the following privileges for the SLO Read role:

Under Index privileges in the Elasticsearch section, add .slo-* to the Indices field and read to the Privileges field.
In the Kibana section, click Add Kibana privilege.
From the Spaces dropdown, either select any specific spaces you want the role to apply to, or select All Spaces.
Set Observability → SLOs to Read.

« SLOs Create a service-level objective (SLO) »