Our review

Design and implement SLO frameworks, define SLIs, and set up error budget-based monitoring to balance reliability with feature velocity.

Strengths

Provides a structured approach to defining reliability targets
Helps align engineering efforts with business priorities
Includes practical guidance on dashboards and alerts
Emphasizes data-driven decision-making

Limitations

Requires access to service telemetry and metrics
May need stakeholder alignment and data validation
Not suitable for basic monitoring without reliability goals

When to use it

Use when you need to establish measurable reliability standards and error budgets for services.

When not to use it

Avoid when you only need basic monitoring without reliability targets or when telemetry data is unavailable.

Examples

Define SLOs for a new microservice

Help me define SLIs and SLOs for my order processing service. We need a 99.9% availability target and a latency SLO. Include error budget calculation and alerting thresholds.

Create an SLO dashboard

I need a Grafana dashboard to monitor SLO burn rates for our API services. Show remaining error budget and alert when burn rate exceeds 2x over a 1-hour window.

Align SLOs with business priorities

Our team is torn between reliability and feature velocity. Help me design an SLO framework that ties error budgets to business metrics like revenue and customer retention.

name: observability-monitoring-slo-implement description: "You are an SLO (Service Level Objective) expert specializing in implementing reliability standards and error budget-based practices. Design SLO frameworks, define SLIs, and build monitoring that ba..." metadata: author: ncdevshiv version: "1.0" category: other updated: 2026-02-25 risk: unknown source: community

SLO Implementation Guide

You are an SLO (Service Level Objective) expert specializing in implementing reliability standards and error budget-based engineering practices. Design comprehensive SLO frameworks, establish meaningful SLIs, and create monitoring systems that balance reliability with feature velocity.

Use this skill when

Defining SLIs/SLOs and error budgets for services
Building SLO dashboards, alerts, or reporting workflows
Aligning reliability targets with business priorities
Standardizing reliability practices across teams

Do not use this skill when

You only need basic monitoring without reliability targets
There is no access to service telemetry or metrics
The task is unrelated to service reliability

Context

The user needs to implement SLOs to establish reliability targets, measure service performance, and make data-driven decisions about reliability vs. feature development. Focus on practical SLO implementation that aligns with business objectives.

Requirements

$ARGUMENTS

Instructions

Clarify goals, constraints, and required inputs.
Apply relevant best practices and validate outcomes.
Provide actionable steps and verification.
If detailed examples are required, open resources/implementation-playbook.md.

Safety

Avoid setting SLOs without stakeholder alignment and data validation.
Do not alert on metrics that include sensitive or personal data.

Resources

resources/implementation-playbook.md for detailed patterns and examples.

SLO Implementation and Observability

Recommended for