sre-slo

Define SLOs, calculate error budgets, and configure burn-rate alerts for Trigent services.

Updated Jul 22, 2026
One-click install
npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill sre-slo-trigent-software-pvt-ltd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sre-slo
Source: https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc/tree/main/plugins/ai-sre/skills/sre-slo
Command: npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill sre-slo-trigent-software-pvt-ltd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams lack a structured way to define service level objectives, track error budgets, and set burn-rate alerting thresholds across Trigent products, making reliability posture hard to measure and enforce. ## Core Features & Use Cases - SLO Definition: Generate SLI definitions with New Relic NRQL and Azure Monitor queries, SLO targets, and error budgets per service for products like Emergency Management, Training, Visitor Management, and SmartPass. - Error Budget & Burn-Rate Alerts: Calculate remaining error budget in minutes per month and produce 3-tier multi-window burn-rate alert thresholds with an error budget release policy. - Compliance Review: Audit current SLO compliance against live Azure Service Bus DLQ metrics and optionally document results as a Confluence page. - Use Case: Run the define mode for the Emergency Management product to get 99.9% availability targets for the emergency-management-api, NRQL alert queries, and a Confluence SLO page. ## Quick Start Ask the assistant to define SLOs for the Emergency Management product using the sre-slo skill.

Frequently Asked Questions about sre-slo

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

FAQPage Schema
How do I define SLOs and error budgets for a service?

Run the skill in define mode with a product slug, such as /ai-sre:sre-slo em define. It generates SLI definitions with New Relic NRQL or Azure Monitor queries, SLO targets, error budgets in minutes per month, and burn-rate alert thresholds.

How do I calculate error budget from an SLO target?

Error budget equals (1 - SLO) multiplied by the minutes in a 28-day month. For example, 99.9% availability yields about 40.3 minutes per month, 99.5% yields about 201.6 minutes, and 99% yields about 403.2 minutes.

What burn-rate alert thresholds should I use for SLO monitoring?

The skill recommends three tiers: a page alert when 1-hour and 5-minute burn rates exceed 14.4, a ticket alert when 6-hour and 30-minute rates exceed 6, and a warning when the 24-hour rate exceeds 3.

Which products does the sre-slo skill support?

It supports products registered in the sre-kb GitLab group, including Emergency Management, Training, Visitor Management, Volunteer Management, DismissalSafe, CPOMS StudentSafe and StaffSafe, SmartPass, SchoolPass, and PSW Canada.

Can I review current SLO compliance against live metrics?

Yes, review mode audits current compliance by querying Azure Service Bus DLQ counts via the Azure CLI and reports error budget consumed and budget status for the selected product.