
Observability Manage Slos
- 2.2k installs
- 546 repo stars
- Updated July 22, 2026
- elastic/agent-skills
observability-manage-slos creates and manages Elastic Observability SLOs through the Kibana API.
About
The observability-manage-slos Elastic skill documents SLO lifecycle through Kibana API calls with ApiKey or basic auth and required kbn-xsrf headers. SLI types include custom KQL, custom and timeslice metrics, histogram metrics, APM latency and availability, and Synthetics availability with budgeting method rules. Guidelines cover objective targets as decimals, transform role requirements, reset after mapping changes, group-by cardinality cautions, and separate burn-rate alert setup. Agents reference official Elastic docs for create, update, delete, enable, disable, and reset endpoints. Use when defining SLIs, error budgets, or managing SLO lifecycle in Elastic Observability stacks.
- Documents Kibana SLO API auth with ApiKey or basic credentials.
- Lists SLI types from KQL logs to APM and Synthetics indicators.
- Explains objective.target decimals and timeslice budgeting rules.
- Warns on high-cardinality group-by and transform node requirements.
- Notes burn-rate alerts are configured separately from SLO API.
Observability Manage Slos by the numbers
- 2,183 all-time installs (skills.sh)
- +160 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #96 of 1,435 DevOps & CI/CD skills by installs in the Skillselion catalog
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
observability-manage-slos capabilities & compatibility
- Capabilities
- slo api operations · sli type selection · error budget configuration
- Use cases
- devops
npx skills add https://github.com/elastic/agent-skills --skill observability-manage-slosAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2.2k |
|---|---|
| repo stars | ★ 546 |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 22, 2026 |
| Repository | elastic/agent-skills ↗ |
How do I define or update SLOs and SLIs in Elastic Observability?
Create and manage Elastic Observability SLOs via Kibana API across KQL, metric, APM, and Synthetics SLI types.
Who is it for?
Elastic stacks using Kibana Observability SLO features.
Skip if: Non-Elastic monitoring or alert-only setups without SLO objects.
When should I use this skill?
User manages Elastic SLOs, SLIs, or error budgets.
What you get
Correctly formed SLO API payloads with appropriate SLI type and budgeting method.
- Kibana API SLO definitions and updates
- SLI and error-budget configuration aligned to Elasticsearch data
By the numbers
- Elastic agent-skills metadata lists observability-manage-slos at version 0.2.0
Files
Service-Level Objectives (SLOs)
Create and manage SLOs in Elastic Observability. SLOs track service performance against measurable targets using service-level indicators (SLIs) computed from Elasticsearch data.
Authentication
SLO operations go through the Kibana API. Authenticate with either an API key or basic auth:
# API key
curl -H "Authorization: ApiKey <base64-encoded-key>" -H "kbn-xsrf: true" <KIBANA_URL>/api/observability/slos
# Basic auth
curl -u "$KIBANA_USER:$KIBANA_PASSWORD" -H "kbn-xsrf: true" <KIBANA_URL>/api/observability/slosFor non-default spaces, prefix the path: /s/<space_id>/api/observability/slos.
Include kbn-xsrf: true on all POST, PUT, and DELETE requests.
SLI Types
| Type | API value | Use case |
|---|---|---|
| Custom KQL | sli.kql.custom | Raw logs — good/total using KQL queries |
| Custom metric | sli.metric.custom | Metric fields — equations with aggregations |
| Timeslice metric | sli.metric.timeslice | Metric fields — per-slice threshold check |
| Histogram metric | sli.histogram.custom | Histogram fields — range/value_count |
| APM latency | sli.apm.transactionDuration | APM — latency threshold |
| APM availability | sli.apm.transactionErrorRate | APM — success rate |
| Synthetics availability | sli.synthetics.availability | Synthetics monitors — uptime percentage |
Guidelines
objective.targetis a decimal between 0 and 1 (for example0.995for 99.5%).- Timeslice metric indicators require
budgetingMethod: "timeslices". - Updating an SLO resets the underlying transform — historical data is recomputed.
- The cluster needs nodes with both
transformandingestroles. - Use
POST .../slos/{id}/_resetwhen an SLO is stuck or after index mapping changes. - Group-by SLOs create one instance per unique value — avoid high-cardinality fields.
- Synthetics SLOs are auto-grouped by monitor and location; do not set
groupBymanually. - Burn rate alert rules are not auto-created using the API — set them up separately.
Additional references
For official documentation, refer to the following resources:
SLO documentation
— concepts, SLI types, budgeting methods, and dashboard panels.
- Create an SLO — step-by-step
guide for creating SLOs in the Kibana UI.
searching, filtering, and managing existing SLOs.
Kibana SLO API
- Create an SLO — full request body schema
with all SLI type payloads.
- Enable |
Troubleshooting and access
Related skills
Forks & variants (1)
Observability Manage Slos has 1 known copy in the catalog totaling 2 installs. They canonicalize to this original listing.
- elastic - 2 installs
How it compares
Pick observability-manage-slos when SLOs must live inside Elastic Observability instead of a separate incident or uptime SaaS.
FAQ
How is objective.target formatted?
As a decimal between 0 and 1, such as 0.995 for 99.5%.
What SLI types exist?
Custom KQL, metric, timeslice, histogram, APM latency, APM error rate, and Synthetics availability.
Do API calls create burn alerts automatically?
No. Burn rate alert rules must be configured separately.
Is Observability Manage Slos safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.