Sla Sli Tracker
Define and track SLAs, SLIs, and SLOs for service reliability including availability targets, latency budgets, error rate thresholds, and error budget burn rates.
Overview
This skill provides a structured approach to defining and tracking SLAs, SLIs, and SLOs, which are essential for ensuring service reliability. It automates the process of setting performance targets and monitoring actual performance, enabling proactive identification and resolution of potential issues.
How It Works
- SLI Definition: The skill guides the user to define Service Level Indicators (SLIs) such as availability, latency, error rate, and throughput.
- SLO Target Setting: The skill assists in setting Service Level Objectives (SLOs) by establishing target values for the defined SLIs (e.g., 99.9% availability).
- SLA Establishment: The skill helps in formalizing Service Level Agreements (SLAs), which are customer-facing commitments based on the defined SLOs.
When to Use This Skill
This skill activates when you need to:
- Define SLAs, SLIs, and SLOs for a service.
- Track service performance against defined objectives.
- Calculate error budgets based on SLOs.
Examples
Example 1: Defining SLOs for a New Service
User request: "Create SLOs for our new payment processing service."
The skill will:
- Prompt the user to define SLIs (e.g., latency, error rate).
- Assist in setting target values for each SLI (e.g., p99 latency < 100ms, error rate < 0.01%).
Example 2: Tracking Availability
User request: "Track the availability SLI for the database service."
The skill will:
- Guide the user in setting up the tracking of the availability SLI.
- Visualize availability performance against the defined SLO.
Best Practices
- Granularity: Define SLIs that are specific and measurable.
- Realism: Set SLOs that are challenging but achievable.
- Alignment: Ensure SLAs align with the defined SLOs and business requirements.
Integration
This skill can be integrated with monitoring tools to automatically collect SLI data and track performance against SLOs. It can also be used in conjunction with alerting systems to trigger notifications when SLO violations occur.
Prerequisites
- SLI definitions stored in ${CLAUDE_SKILL_DIR}/slos/sli-definitions.yaml
- Access to monitoring and metrics systems
- Historical performance data for baseline
- Business requirements for service reliability
Instructions
- Define Service Level Indicators (availability, latency, error rate, throughput)
- Set Service Level Objectives with target values (e.g., 99.9% availability)
- Formalize Service Level Agreements with customer commitments
- Configure automated SLI data collection
- Calculate error budgets based on SLOs
- Track performance and alert on SLO violations
Output
- SLI/SLO/SLA definition documents
- Real-time SLI metric dashboards
- Error budget calculations and burn rate
- SLO compliance reports
- Alerting configurations for violations
Error Handling
If SLI/SLO tracking fails:
- Verify SLI definition completeness
- Check metric collection infrastructure
- Validate data accuracy and granularity
- Ensure alerting system connectivity
- Review error budget calculation logic
Resources
- Google SRE book on SLIs and SLOs
- Error budget implementation guides
- Service reliability engineering practices
- SLO definition templates and examples
1---2name: tracking-service-reliability3description: Define and track SLAs, SLIs, and SLOs for service reliability including availability, latency, and error rates. Use when establishing reliability targets or monitoring service health. Trigger with phrases like "define SLOs", "track SLI metrics", or "calculate error budget".4license: MIT5---6# Sla Sli Tracker78Define and track SLAs, SLIs, and SLOs for service reliability including availability targets, latency budgets, error rate thresholds, and error budget burn rates.910## Overview1112This skill provides a structured approach to defining and tracking SLAs, SLIs, and SLOs, which are essential for ensuring service reliability. It automates the process of setting performance targets and monitoring actual performance, enabling proactive identification and resolution of potential issues.1314## How It Works15161. **SLI Definition**: The skill guides the user to define Service Level Indicators (SLIs) such as availability, latency, error rate, and throughput.172. **SLO Target Setting**: The skill assists in setting Service Level Objectives (SLOs) by establishing target values for the defined SLIs (e.g., 99.9% availability).183. **SLA Establishment**: The skill helps in formalizing Service Level Agreements (SLAs), which are customer-facing commitments based on the defined SLOs.1920## When to Use This Skill2122This skill activates when you need to:23- Define SLAs, SLIs, and SLOs for a service.24- Track service performance against defined objectives.25- Calculate error budgets based on SLOs.2627## Examples2829### Example 1: Defining SLOs for a New Service3031User request: "Create SLOs for our new payment processing service."3233The skill will:341. Prompt the user to define SLIs (e.g., latency, error rate).352. Assist in setting target values for each SLI (e.g., p99 latency < 100ms, error rate < 0.01%).3637### Example 2: Tracking Availability3839User request: "Track the availability SLI for the database service."4041The skill will:421. Guide the user in setting up the tracking of the availability SLI.432. Visualize availability performance against the defined SLO.4445## Best Practices4647- **Granularity**: Define SLIs that are specific and measurable.48- **Realism**: Set SLOs that are challenging but achievable.49- **Alignment**: Ensure SLAs align with the defined SLOs and business requirements.5051## Integration5253This skill can be integrated with monitoring tools to automatically collect SLI data and track performance against SLOs. It can also be used in conjunction with alerting systems to trigger notifications when SLO violations occur.5455## Prerequisites5657- SLI definitions stored in ${CLAUDE_SKILL_DIR}/slos/sli-definitions.yaml58- Access to monitoring and metrics systems59- Historical performance data for baseline60- Business requirements for service reliability6162## Instructions63641. Define Service Level Indicators (availability, latency, error rate, throughput)652. Set Service Level Objectives with target values (e.g., 99.9% availability)663. Formalize Service Level Agreements with customer commitments674. Configure automated SLI data collection685. Calculate error budgets based on SLOs696. Track performance and alert on SLO violations7071## Output7273- SLI/SLO/SLA definition documents74- Real-time SLI metric dashboards75- Error budget calculations and burn rate76- SLO compliance reports77- Alerting configurations for violations7879## Error Handling8081If SLI/SLO tracking fails:82- Verify SLI definition completeness83- Check metric collection infrastructure84- Validate data accuracy and granularity85- Ensure alerting system connectivity86- Review error budget calculation logic8788## Resources8990- Google SRE book on SLIs and SLOs91- Error budget implementation guides92- Service reliability engineering practices93- SLO definition templates and examples
ComeOnOliver