Kubernetes alerts tell you what is broken right now; SLOs tell you how much reliability budget the incident is consuming. This package helps SRE and platform teams move from replica-count symptoms to workload-level error-budget tracking using the same OpenTelemetry metrics they already collect with Elastic’s Kubernetes OpenTelemetry Assets integration.
What is included
- Deployment Replica Availability 99.5% rolling 30-day SLO template.
- StatefulSet Replica Availability 99.5% rolling 30-day SLO template.
- DaemonSet Scheduling Availability 99.0% rolling 30-day SLO template.
- Job Completion Success Rate 99.0% rolling 30-day SLO template.
- Package manifest, changelog, and Elastic License 2.0 file.
Who it helps
Use this package when Deployment, StatefulSet, DaemonSet, or Job failures need more context than a single alert can provide. The templates help teams see whether a rollout, node-level agent gap, or failed batch job is a small transient issue or a meaningful burn against the monthly reliability target. This makes the package useful for on-call triage, reliability reviews, incident follow-up, and prioritizing fixes across many Kubernetes workloads.
Compatibility
The current kubernetes_otel package manifest declares Kibana ^9.4.0 and basic subscription. The Labs article refers to kubernetes_otel 2.3.0; the current source package is newer.
Source and license
Source is from elastic/integrations. Files use Elastic License 2.0 unless otherwise noted in the repository.
| Tested versions | |
| ECS compliant |
You must log in to submit a review.
