What is the difference between SLIs, SLOs, and SLAs in this skill?

SLIs are specific metrics (like latency), SLOs are the target goals for those metrics (e.g., 99.9% success), and SLAs are the formal commitments made to customers based on those objectives.

Is this skill suitable for non-web services?

Absolutely. Any service that has measurable performance outcomes, such as batch processing jobs or database clusters, can benefit from these tracking patterns.

How does this skill help manage error budgets?

The skill helps calculate the remaining 'unreliability' permitted within your SLOs, allowing your team to decide if it is safe to deploy new features or if you need to focus on stability.

Can I integrate this with existing monitoring tools?

Yes, the skill provides a structured approach that can be used to configure or interact with external monitoring and alerting systems via Claude's terminal capabilities.

Service Reliability & SLA Tracker

Name: Service Reliability & SLA Tracker
Author: jeremylongshore

byjeremylongshore

•

883

분석 및 모니터링

Defines and tracks critical service reliability metrics including SLAs, SLIs, and SLOs to ensure peak system performance.

소개

This skill empowers Claude to act as a Site Reliability Engineering (SRE) assistant by establishing a structured framework for monitoring service health. It helps users define measurable indicators (SLIs), set realistic objective targets (SLOs), and formalize customer-facing agreements (SLAs), while also managing error budgets to balance innovation with stability. This is particularly useful for DevOps teams and system architects who need to maintain high availability and performance standards across distributed systems and microservices.

주요 기능

Customer-facing SLA formalization based on internal metrics
Visualization support for tracking performance against reliability targets
Automated error budget calculation based on service objectives
SLO target setting and performance tracking workflows
Guided definition of SLIs such as availability, latency, and error rates
883 GitHub stars

사용 사례

Establishing reliability benchmarks and performance targets for a new microservice
Calculating error budgets to determine the safety of new production deployments
Monitoring database availability and visualizing uptime against defined SLOs

소개

주요 기능

Customer-facing SLA formalization based on internal metrics
Visualization support for tracking performance against reliability targets
Automated error budget calculation based on service objectives
SLO target setting and performance tracking workflows
Guided definition of SLIs such as availability, latency, and error rates
883 GitHub stars

사용 사례

Establishing reliability benchmarks and performance targets for a new microservice
Calculating error budgets to determine the safety of new production deployments
Monitoring database availability and visualizing uptime against defined SLOs