DevOps & SRE

Analyzes an alert from a monitoring system to suggest potential root causes and initial diagnostic steps for the on-call engineer.

Generates a starter CI/CD pipeline configuration file (e.g., for GitHub Actions) for a new service, automating a common and repetitive task.

Generates a monitoring and alerting plan for a new service based on Google's 'Four Golden Signals' of SRE.

SREs live by monitoring and instrumentation. However, writing queries for modern observability tools like Prometheus (using PromQL) is a specialized, complex skill.

When a system fails, SREs are on the hook. They face high "operational load" and cognitive "overload" from the high-stress, complex debugging required to restore service.

A slow or flaky CI/CD pipeline is a bottleneck for the entire engineering organization. Common problems include slow build times, serialized deployments that create queues, and a lack of visibility into failure points.

IaC (e.g., Terraform, Ansible) is the industry standard for managing cloud infrastructure. However, the domain-specific languages are complex, and debugging configuration errors or failed plans is notoriously difficult.

"Toil" is the set of manual, repetitive, non-strategic tasks that SREs are forced to do. The SRE mandate is to automate this toil away.

Facilitate effective incident post-mortems that drive learning and prevent recurrence.

Design comprehensive monitoring and alerting strategies that provide visibility without alert fatigue.

Review Infrastructure as Code (IaC) for best practices, security, and maintainability.