skills.rest
monang404
monang404COMMUNITY
Explore all skills by this author →
GitHub

observability-engineer

Design monitoring, logging, tracing, and SLO systems for production services.

2|Updated Jun 16, 2026
Search Tags:#monitoring#observability#incident response#prometheus#opentelemetry#distributed tracing#slo
One-click install
npx skills add https://github.com/monang404/lunawave --skill observability-engineer-monang404
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: observability-engineer
Source: https://github.com/monang404/lunawave/tree/main/.agent/skills/observability-engineer
Command: npx skills add https://github.com/monang404/lunawave --skill observability-engineer-monang404

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Production systems fail silently without proper telemetry, and teams struggle to detect, diagnose, and resolve incidents before users are impacted. This Skill provides expert guidance for building comprehensive observability systems covering metrics, logs, traces, alerting, and reliability targets. ## Core Features & Use Cases - Monitoring & Metrics Design: Architect Prometheus, Grafana, DataDog, or CloudWatch monitoring with recording rules, dashboards, and high-cardinality handling. - Distributed Tracing & Logging: Implement OpenTelemetry instrumentation, Jaeger tracing, and ELK/Loki log aggregation for root cause analysis. - SLI/SLO & Incident Response: Define service level objectives, error budgets, alert routing with PagerDuty, and blameless postmortem workflows. - Use Case: A platform team running 50 microservices needs to meet a 99.9% availability target. Use this Skill to design the SLI/SLO framework, deploy OpenTelemetry tracing, build Grafana dashboards, and configure noise-reduced alerting with escalation policies. ## Quick Start Ask the assistant to design a monitoring and alerting strategy with SLOs for your microservices architecture.

Frequently Asked Questions about observability-engineer

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

FAQPage Schema
How do I set up SLI/SLO monitoring for microservices?▼

Define SLIs from request latency, error rate, and availability metrics, then set SLO targets like 99.9% availability. Track error budgets with burn rate alerts in Prometheus or Grafana, and align alert thresholds to SLO violations rather than raw metric spikes.

What is the best way to implement distributed tracing with OpenTelemetry?▼

Deploy the OpenTelemetry Collector as a central pipeline, then add auto-instrumentation agents for your languages. Export traces to Jaeger or Zipkin, apply tail-based sampling to control costs, and correlate trace IDs with logs and metrics for root cause analysis.

Prometheus vs DataDog for infrastructure monitoring?▼

Prometheus is open-source, Kubernetes-native, and cost-effective with PromQL flexibility, but requires managing storage and scaling. DataDog offers managed APM, synthetic monitoring, and easier setup at higher cost. Choose based on team size, budget, and existing cloud commitments.

How do I reduce alert fatigue and noise in production alerting?▼

Alert on symptoms tied to SLO burn rates instead of every metric anomaly. Use alert correlation, grouping, and deduplication in PagerDuty, tune thresholds from historical data, and route only actionable pages to on-call while sending informational alerts to chat channels.

Can OpenTelemetry export to multiple observability backends?▼

Yes, the OpenTelemetry Collector supports multi-backend export, sending the same telemetry to Prometheus, Jaeger, and DataDog simultaneously. Configure exporters in the collector pipeline and use processors for sampling, filtering, and enrichment before export.

When should I not invest in a full observability stack?▼

Skip full observability architecture for single ad-hoc dashboards, prototypes without production traffic, or systems where you cannot access metrics, logs, or traces. Start with basic health checks and add structured telemetry only when reliability targets justify the operational cost.

Related Skills

Explore More Software Engineering Skills→
tylern91tylern91

opentelemetry

Instrument services to export traces, metrics, and logs to an OpenTelemetry collector.

Community
Advanced
allthingslinuxallthingslinux
1

monitoring-guidelines

Define monitoring requirements for metrics, alerting, SLOs, dashboards, and incident response.

Official
Basic
farmountainfarmountain
1

Reliability Tester

Execute chaos engineering and fault injection tests to validate system resilience.

Community
Advanced
pauljbernardpauljbernard
5

Monitoring and Observability Tools Expertise

Guide monitoring, observability, and APM tool implementation for distributed systems.

Community
Advanced