Define SLO/SLI/SLA
技能 已验证 活跃Establish Service Level Objectives (SLO), Service Level Indicators (SLI), and Service Level Agreements (SLA) with error budget tracking, burn rate alerts, and automated reporting using Prometheus and tools like Sloth or Pyrra. Use when defining reliability targets for customer-facing services, balancing feature velocity against system reliability through error budgets, migrating from arbitrary uptime goals to data-driven metrics, or implementing Site Reliability Engineering practices.
Define and manage service reliability targets, balancing feature development with system stability through data-driven metrics and error budgets.
功能
- Define SLO, SLI, and SLA hierarchy
- Select and measure key SLIs (Four Golden Signals)
- Set realistic SLO targets and calculate error budgets
- Implement SLO monitoring with Sloth and Prometheus
- Visualize compliance and budget with Grafana dashboards
- Establish error budget policies and automate enforcement
使用场景
- Defining reliability targets for customer-facing services
- Balancing feature velocity against system reliability
- Migrating from arbitrary uptime goals to data-driven metrics
- Implementing Site Reliability Engineering (SRE) practices
非目标
- Providing a fully automated SLO generation tool
- Replacing general monitoring or alerting systems
- Defining specific SLIs for every possible service type
工作流
- Understand SLI, SLO, and SLA Hierarchy
- Select Appropriate SLIs
- Set SLO Targets and Time Windows
- Implement SLO Monitoring with Sloth
- Build Error Budget Dashboards
- Establish Error Budget Policy
实践
- Service Level Management
- Observability
- Site Reliability Engineering
先决条件
- Prometheus for metrics collection
- Tools like Sloth or Pyrra for SLO generation
- Grafana for dashboarding
安装
/plugin install agent-almanac@pjt222-agent-almanac质量评分
已验证类似扩展
Slo Architect
99Use when defining, reviewing, or operating SLOs/SLIs/error budgets. Triggers on "define an SLO", "what should our SLO be", "error budget", "burn rate", "SLI", "service level objective", "Google SRE workbook", "multi-window burn-rate alert", or any reliability-target question. Ships SLO designer, error-budget calculator with multi-window burn-rate thresholds, and SLO reviewer that catches the common bugs (target too aggressive, window too short, conflicting SLOs, no SLI definition). 4 references on SLO principles + SLI design + error budget math + composition with feature-flags-architect/chaos-engineering/kubernetes-operator. NOT a generic observability skill — specifically the SLO discipline.
Observability Designer
100Observability Designer (POWERFUL)
SRE Engineer
98Defines service level objectives, creates error budget policies, designs incident response procedures, develops capacity models, and produces monitoring configurations and automation scripts for production systems. Use when defining SLIs/SLOs, managing error budgets, building reliable systems at scale, incident management, chaos engineering, toil reduction, or capacity planning.
Grafana Dashboards
99Create and manage production Grafana dashboards for real-time visualization of system and application metrics. Use when building monitoring dashboards, visualizing metrics, or creating operational observability interfaces.
Plan Capacity
99Perform capacity planning using historical metrics and growth models. Use predict_linear for forecasting, identify resource constraints, calculate headroom, and recommend scaling actions before saturation. Use before seasonal traffic spikes or product launches, during quarterly capacity reviews, when resource utilization trends upward, or before budget planning cycles.
Chaos Engineering
99Use when planning, running, or learning from chaos engineering experiments. Triggers on "chaos experiment", "fault injection", "gameday", "resilience test", "blast radius", "steady state", "abort criteria", "Chaos Toolkit", "Chaos Mesh", "Litmus", "Gremlin", "AWS FIS", or any deliberate failure-injection question. Ships experiment designer, blast-radius calculator, and postmortem generator (all stdlib Python), 4 references on chaos principles + experiment design + attack taxonomy + tooling landscape, and a /chaos-experiment slash command. Composes with feature-flags-architect (kill switches as abort triggers) and kubernetes-operator (common chaos targets).