observability-engineer

Correlate metrics, logs, and traces to detect and diagnose production incidents.

1|Updated Jan 26, 2026

Search Tags:#monitoring #observability #alerts #SLO #SLI #runbooks #incident-response

Ready to run

npx skills add https://github.com/filipemotta/devopsai-templates --skill observability-engineer-filipemotta

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: observability-engineer
Source: https://github.com/filipemotta/devopsai-templates/tree/main/skills/observability
Command: npx skills add https://github.com/filipemotta/devopsai-templates --skill observability-engineer-filipemotta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Achieve reliable systems by unifying metrics, logs, and traces to detect, diagnose, and reduce MTTR for production incidents.

Core Features & Use Cases

Design end-to-end monitoring systems using metrics, logs, and traces.
Create effective alerts and dashboards for SLOs/SLIs, and guide incident response with runbooks.
Define, monitor, and improve SLOs/SLIs/SLAs to drive reliability and on-call efficiency.

Quick Start

Set up a baseline Prometheus + Grafana stack and implement an initial alert rule to validate the observability workflow.

Frequently Asked Questions about observability-engineer

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

FAQPage Schema

How do I design monitoring systems that unify metrics, logs, and traces to detect production incidents?▼

Designing monitoring systems to detect production incidents involves correlating metrics, logs, and traces to reduce mean time to resolution. You achieve reliable systems by unifying these signals to diagnose issues across scalable monitoring architectures.

What is the best way to define SLOs and SLIs for driving reliability and on-call efficiency?▼

Defining SLOs and SLIs requires establishing service level indicators and objectives to drive reliability and on-call efficiency. You define, monitor, and improve these metrics to create effective alerts and guide incident response workflows.

How do I create effective alerts and dashboards for incident response?▼

Creating effective alerts and dashboards for incident response means applying alerting best practices alongside structured runbooks. You guide incident response workflows by building dashboards that visualize SLOs and SLIs for quick diagnosis.

Can I set up a baseline Prometheus and Grafana stack to validate my observability workflow?▼

Yes, you can set up a baseline Prometheus and Grafana stack to validate your observability workflow. Implementing an initial alert rule within this stack establishes a working monitoring baseline to detect and diagnose production incidents.

When do I need structured runbooks for incident response workflows?▼

You need structured runbooks for incident response workflows when guiding teams through diagnosing production incidents. Structured runbooks satisfy alerting best practices by providing standardized steps to reduce mean time to resolution during outages.