sre-engineer

To define and track SLI and SLO metrics for production system reliability, you establish Service Level Indicators and Objectives that balance reliability with feature velocity. This framework guides engineering trade-offs using error budget policies.

The best way to automate operational toil and repetitive incident response tasks is by identifying repetitive manual actions and implementing Python-based self-healing and runbook automation patterns to reduce manual intervention.

Chaos engineering helps manage incident response and ensure system resilience by executing controlled failure experiments and managing incident response workflows, which validates system behavior under failure conditions.

Yes, you can use Python and numpy to monitor golden signals and error budgets. The skill implements quantitative monitoring of golden signals and error budget policies using Python-based automation patterns.

You need to implement error budget policies for your services when you must balance reliability with feature velocity. These policies guide engineering trade-offs by quantifying acceptable levels of unreliability.

Yes, the sre-engineer skill supports setting a 30-day measurement window for a 99.9 percent availability target. You can define specific SLOs for individual services like a payment-api with these exact parameters.