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-reliability
3description: 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".
4version: 1.0.0
5allowed-tools: "Read, Write, Edit, Grep, Glob, Bash(monitoring:*), Bash(metrics:*)"
6license: MIT
7author: Jeremy Longshore <jeremy@intentsolutions.io>
8compatible-with: claude-code, codex, openclaw
9metadata:
10 source: https://skillmd.com/skills/micsapp/tracking-service-reliability
11---
12
13# Sla Sli Tracker
14
15Define and track SLAs, SLIs, and SLOs for service reliability including availability targets, latency budgets, error rate thresholds, and error budget burn rates.
16
17## Overview
18
19This 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.
20
21## How It Works
22
231. **SLI Definition**: The skill guides the user to define Service Level Indicators (SLIs) such as availability, latency, error rate, and throughput.
242. **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).
253. **SLA Establishment**: The skill helps in formalizing Service Level Agreements (SLAs), which are customer-facing commitments based on the defined SLOs.
26
27## When to Use This Skill
28
29This skill activates when you need to:
30- Define SLAs, SLIs, and SLOs for a service.
31- Track service performance against defined objectives.
32- Calculate error budgets based on SLOs.
33
34## Examples
35
36### Example 1: Defining SLOs for a New Service
37
38User request: "Create SLOs for our new payment processing service."
39
40The skill will:
411. Prompt the user to define SLIs (e.g., latency, error rate).
422. Assist in setting target values for each SLI (e.g., p99 latency < 100ms, error rate < 0.01%).
43
44### Example 2: Tracking Availability
45
46User request: "Track the availability SLI for the database service."
47
48The skill will:
491. Guide the user in setting up the tracking of the availability SLI.
502. Visualize availability performance against the defined SLO.
51
52## Best Practices
53
54- **Granularity**: Define SLIs that are specific and measurable.
55- **Realism**: Set SLOs that are challenging but achievable.
56- **Alignment**: Ensure SLAs align with the defined SLOs and business requirements.
57
58## Integration
59
60This 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.
61
62## Prerequisites
63
64- SLI definitions stored in ${CLAUDE_SKILL_DIR}/slos/sli-definitions.yaml
65- Access to monitoring and metrics systems
66- Historical performance data for baseline
67- Business requirements for service reliability
68
69## Instructions
70
711. Define Service Level Indicators (availability, latency, error rate, throughput)
722. Set Service Level Objectives with target values (e.g., 99.9% availability)
733. Formalize Service Level Agreements with customer commitments
744. Configure automated SLI data collection
755. Calculate error budgets based on SLOs
766. Track performance and alert on SLO violations
77
78## Output
79
80- SLI/SLO/SLA definition documents
81- Real-time SLI metric dashboards
82- Error budget calculations and burn rate
83- SLO compliance reports
84- Alerting configurations for violations
85
86## Error Handling
87
88If SLI/SLO tracking fails:
89- Verify SLI definition completeness
90- Check metric collection infrastructure
91- Validate data accuracy and granularity
92- Ensure alerting system connectivity
93- Review error budget calculation logic
94
95## Resources
96
97- Google SRE book on SLIs and SLOs
98- Error budget implementation guides
99- Service reliability engineering practices
100- SLO definition templates and examples