- Observability: other versions:
- Get started
- What is Elastic Observability?
- What’s new in 8.17
- Quickstart: Monitor hosts with Elastic Agent
- Quickstart: Monitor your Kubernetes cluster with Elastic Agent
- Quickstart: Monitor hosts with OpenTelemetry
- Quickstart: Unified Kubernetes Observability with Elastic Distributions of OpenTelemetry (EDOT)
- Quickstart: Collect data with AWS Firehose
- Add data from Splunk
- Applications and services
- Application performance monitoring (APM)
- Get started
- Learn about data types
- Collect application data
- View and analyze data
- Act on data
- Use APM securely
- Manage storage
- Configure APM Server
- Monitor APM Server
- APM APIs
- Troubleshooting
- Upgrade
- Release notes
- Known issues
- Synthetic monitoring
- Get started
- Scripting browser monitors
- Configure lightweight monitors
- Manage monitors
- Work with params and secrets
- Analyze monitor data
- Monitor resources on private networks
- Use the CLI
- Configure projects
- Multi-factor Authentication
- Configure Synthetics settings
- Grant users access to secured resources
- Manage data retention
- Use Synthetics with traffic filters
- Migrate from the Elastic Synthetics integration
- Scale and architect a deployment
- Synthetics support matrix
- Synthetics Encryption and Security
- Troubleshooting
- Real user monitoring
- Uptime monitoring (deprecated)
- Tutorial: Monitor a Java application
- Application performance monitoring (APM)
- CI/CD
- Cloud
- Infrastructure and hosts
- Logs
- Troubleshooting
- Incident management
- Data set quality
- Observability AI Assistant
- Reference
Configure service-level objective (SLO) access
editConfigure service-level objective (SLO) access
editTo create and manage SLOs, you need an appropriate license and an Elasticsearch cluster with both transform
and ingest
node roles present.
You can enable access to SLOs in two different ways:
-
Creating the following roles, depending on the type of access needed:
- SLO Editor — Create, edit, and manage SLOs and their historical summaries.
- SLO Viewer — Check SLOs and their historical summaries.
-
Using the
editor
built-in role. This role grants full access to all features in Kibana (including the Observability solution) and read-only access to data indices. Users assigned to this role can create, edit, and manage SLOs.The
editor
built-in role grants write access to all Kibana apps. If you want to limit access to the SLOs only, you have to manually create and assign the mentioned roles.
To create a role:
- To open Roles, find Stack Management in the main menu or use the global search field.
- On the Roles page, click Create role.
Create an SLO Editor role
editSet the following privileges for the SLO Editor role:
-
Under Index privileges in the Elasticsearch section, add
.slo-observability-*
to the Indices field andread
,view_index_metadata
,write
, andmanage
to the Privileges field. - Click Add index privilege.
-
In the Indices field, add the indices for which you plan to create SLOs. Then, add
read
andview_index_metadata
to the Privileges field. The following example showslogs-*
, 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
. - Click Create Role at the bottom of the page and assign the role to the relevant users.
Create an SLO Viewer role
editSet the following privileges for the SLO Read role:
-
Under Index privileges in the Elasticsearch section, add
.slo-observability-*
to the Indices field andread
andview_index_metadata
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
. - Click Create Role at the bottom of the page and assign the role to the relevant users.