sre-canary

Verify production deployments and canary releases for health and performance regressions.

2|1|Updated Jul 25, 2026
One-click install
npx skills add https://github.com/CODE-SAURABH/OpenSkills --skill sre-canary
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sre-canary
Source: https://github.com/CODE-SAURABH/OpenSkills/tree/main/sre-canary
Command: npx skills add https://github.com/CODE-SAURABH/OpenSkills --skill sre-canary

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers determine whether a production deployment is healthy and safe to promote, catching regressions before a canary becomes a wider outage.

Core Features & Use Cases

  • Post-Deploy Monitoring: Establish baselines and monitor error rates, latency, resource usage, logs, queues, caches, dependencies, and health checks across immediate, stabilization, and confidence windows.
  • Canary Verification: Compare canary and stable cohorts through staged traffic gates, SLO compliance, error budgets, Apdex, database performance, and downstream health.
  • Rollback Readiness: Define hard and soft rollback triggers and provide operational patterns for aborting, undoing, and verifying Argo Rollouts deployments.
  • Frontend Observability: Track Core Web Vitals, browser console errors, failed resources, client-side API failures, and real-user monitoring data by deployment version.

Quick Start

Use the SRE Canary skill to monitor the newly deployed service, compare it with the stable version, and determine whether to promote or roll back the canary.

Frequently Asked Questions about sre-canary

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

FAQPage Schema
How do I verify a canary deployment before promoting it in Kubernetes?

Canary deployment verification compares canary and stable cohorts through staged traffic gates, SLO compliance, and error budgets to detect regressions before broader Kubernetes rollout.

What metrics are needed for post-deploy monitoring of a production release?

Post-deploy monitoring requires baseline metrics, error rates, latency, resource usage, structured logs, health probes, and Prometheus-style telemetry to validate reliability across stabilization and confidence windows.

How do I set up rollback triggers for Argo Rollouts?

Rollback triggers for Argo Rollouts are set by defining explicit hard and soft thresholds based on SLO validation, error budgets, and incident-sensitive health checks to automate deployment aborts.

Can I track Core Web Vitals and frontend observability by deployment version?

Frontend observability tracks Core Web Vitals, browser console errors, failed resources, and real-user monitoring data by deployment version to catch user-experience regressions during release.

When should I abort a canary release instead of promoting it?

Abort a canary release when automated or human rollback thresholds are breached, indicating health, reliability, performance, or user-experience regressions compared to the stable baseline metrics.

Does canary verification work without baseline metrics and structured logs?

No, canary verification requires baseline metrics, health probes, structured logs, Prometheus-style telemetry, and deployment annotations to accurately compare cohorts and validate SLO compliance.