monitor-slo

Automate multi-cloud SLO monitoring and reliability reporting across AWS, Azure, GCP, and on-prem.

2|1|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/lloydchang/agentic-reconciliation-engine --skill monitor-slo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monitor-slo
Source: https://github.com/lloydchang/agentic-reconciliation-engine/tree/main/core/ai/skills/monitor-slo
Command: npx skills add https://github.com/lloydchang/agentic-reconciliation-engine --skill monitor-slo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires boto3, azure-sdk, google-cloud, kubernetes, terraform-python, ansible-python.

What problem does it solve?

Track and enforce Service Level Objectives (SLOs) across multi-cloud environments to improve reliability, governance, and incident preparedness.

Core Features & Use Cases

  • Multi-cloud SLO tracking across AWS, Azure, GCP, and on-prem environments
  • Automatic error-budget calculations, burn-rate alerts, and reliability reporting
  • Use cases include capacity planning, post-incident reviews, and SLA compliance across providers

Quick Start

Identify the services to monitor and enable SLO tracking with a single configuration command to bootstrap monitoring.

Frequently Asked Questions about monitor-slo

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track SLOs across AWS, Azure, and GCP environments?

You can calculate error budgets and burn rates automatically by configuring SLO tracking across AWS, Azure, and GCP, which calculates error budgets and generates burn-rate alerts using cloud SDK libraries.

Can I use Kubernetes and Terraform for multi-cloud SLO monitoring?

Multi-cloud SLO monitoring requires Python 3.8+, cloud SDKs including boto3, azure-sdk, google-cloud, Kubernetes client, and Terraform to implement end-to-end monitoring across providers.

Does SLO monitoring support error budget calculations and burn-rate alerts?

Automatic error-budget calculations and burn-rate alerts are supported natively, enabling service reliability governance, incident response, and capacity planning across AWS, Azure, and GCP.

What is the best way to start monitoring service reliability across multiple clouds?

Bootstrapping multi-cloud SLO monitoring involves identifying target services and running a single configuration command to enable tracking, applying reliability governance across AWS, Azure, and GCP.

How do I generate reliability reports for post-incident reviews?

Reliability reports for post-incident reviews are generated by monitoring SLOs across multi-cloud environments, tracking error budgets, and applying service reliability governance across AWS, Azure, and GCP.