This documentation contains work-in-progress information for future Elastic Stack and Cloud releases. Use the version selector to view supported release docs. It also contains some Elastic Cloud serverless information. Check out our serverless docs for more details.
Configure service-level objective (SLO) access
editConfigure service-level objective (SLO) access
editTo create and manage SLOs, you need an appropriate license.
You can create the following roles for your SLOs:
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
editSet the following privileges for the SLO All role:
-
Under Cluster privileges in the Elasticsearch section, add
manage_transform
andmanage_ingest_pipelines
. -
Under Index privileges, add
.slo-*
to the Indices field andall
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 the Privileges field. The following example shows
logs-*
, but you can specify any indices. - 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
editSet the following privileges for the SLO Read role:
-
Under Index privileges in the Elasticsearch section, add
.slo-*
to the Indices field andread
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
.