slo-implementation

Name: slo-implementation
Availability: InStock
Author: drgaciw

Implement SLIs, SLOs, and error budgets with Prometheus alerting rules.

Updated Dec 23, 2025

Search Tags:#monitoring #reliability #alerting #sre #error budget #slo #sli

Ready to run

npx skills add https://github.com/drgaciw/academic-compliance-hub-glm --skill slo-implementation-drgaciw

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: slo-implementation
Source: https://github.com/drgaciw/academic-compliance-hub-glm/tree/main/agents/plugins/observability-monitoring/skills/slo-implementation
Command: npx skills add https://github.com/drgaciw/academic-compliance-hub-glm --skill slo-implementation-drgaciw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides a framework for defining and implementing Service Level Indicators (SLIs), Service Level Objectives (SLOs), and error budgets to manage service reliability and innovation velocity.

Core Features & Use Cases

SLI/SLO Definition: Define measurable indicators and targets for service reliability.
Error Budget Management: Calculate and track error budgets to balance reliability with feature development.
Alerting: Implement alerts for error budget burn rates and SLO violations.
Use Case: When establishing reliability targets for a new API, use this Skill to define availability and latency SLOs, set up error budgets, and configure alerts to notify the team when the error budget is being consumed too quickly.

Quick Start

Use the slo-implementation skill to define an availability SLI for the API and set a 99.9% SLO with a 28-day window.

Frequently Asked Questions about slo-implementation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I define SLI and SLO targets for service reliability?▼

To define SLI and SLO targets, you establish measurable Service Level Indicators like availability and latency, then set target objectives such as a 99.9% success rate over a 28-day window to manage service reliability.

How do I calculate and track error budgets for SRE?▼

Error budgets are calculated by measuring the gap between your SLO target and 100% reliability, allowing you to track the remaining tolerance for failures and balance feature development velocity with service stability.

How do I configure Prometheus alerting rules for error budget burn rate?▼

You can configure Prometheus alerting rules to monitor error budget burn rates by implementing specific recording and alerting configurations that notify your team when SLOs are violated or budgets are consumed too quickly.

What is the difference between SLI and SLO in monitoring?▼

SLIs are the actual metrics measuring service performance like availability and latency, while SLOs are the specific reliability targets set for those indicators, such as requiring 99.9% availability over a 28-day window.

Can I implement latency and availability SLOs for a new API?▼

Yes, you can implement latency and availability SLOs for a new API by defining the specific SLIs for those metrics, setting your desired target objectives, and calculating the corresponding error budgets to establish proactive monitoring.

Why do I need error budgets when setting reliability targets?▼

Error budgets provide a quantitative framework to balance reliability with innovation, indicating how much unreliability is tolerable before focusing on stability rather than shipping new features.