- Observability: other versions:
- What is Elastic Observability?
- What’s new in 8.10
- Get started
- Observability AI Assistant
- Application performance monitoring (APM)
- Logs
- Infrastructure monitoring
- AWS monitoring
- 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
- 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
- Uptime monitoring
- Real user monitoring
- Universal Profiling
- Alerting
- Service-level objectives (SLOs) (beta)
- Cases
- CI/CD observability
- Troubleshooting
- Fields reference
- Tutorials
- Monitor Amazon Web Services (AWS) with Elastic Agent
- Monitor Amazon Web Services (AWS) with Beats
- Monitor Google Cloud Platform
- Monitor a Java application
- Monitor Kubernetes
- Monitor Microsoft Azure with Elastic Agent
- Monitor Microsoft Azure with the Azure Native ISV Service
- Monitor Microsoft Azure with Beats
Configure service-level objective (SLO) access
editConfigure service-level objective (SLO) access
editThis 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:
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
. -
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 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
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
.
On this page