monitoring

Define unified observability strategies with metrics, logs, traces, and alerting.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/datorresb/vibecoding-starter --skill monitoring-datorresb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monitoring
Source: https://github.com/datorresb/vibecoding-starter/tree/main/.claude/skills/devops/monitoring
Command: npx skills add https://github.com/datorresb/vibecoding-starter --skill monitoring-datorresb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a cohesive observability strategy that unifies metrics, logs, and traces with alerting, enabling teams to understand system health, diagnose issues faster, and meet reliability targets.

Core Features & Use Cases

  • Unified observability pillars: metrics, logs, and traces with correlated data across services.
  • SRE best practices: Four Golden Signals, SLIs/SLOs, alerting strategies, runbooks, and dashboards.
  • Incident readiness and dashboards: prebuilt patterns for health, dependency health, and on-call readiness.
  • Integrations and tooling: Prometheus, Grafana, Loki, Jaeger/OpenTelemetry, Alertmanager, and cloud-native stacks.

Quick Start

Instrument services to emit metrics, logs, and traces, deploy a standard stack (Prometheus for metrics, Loki for logs, Jaeger/OpenTelemetry for traces, Grafana for dashboards), define SLIs/SLOs and alerts, and validate end-to-end observability with a sample request flow.

Frequently Asked Questions about monitoring

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

FAQPage Schema
How do I unify metrics, logs, and traces for cloud-native observability?

Unify metrics, logs, and traces by instrumenting services to emit correlated data and deploying a standard stack using Prometheus, Loki, and Jaeger for end-to-end visibility. This enables faster incident debugging and performance tuning across applications.

What are the four golden signals and how do I use them for SRE alerting?

The four golden signals—latency, traffic, errors, and saturation—are core metrics for monitoring system health. You use them to define SLIs/SLOs and configure Alertmanager strategies for on-call readiness and incident response.

How do I set up Grafana dashboards for incident debugging and capacity planning?

Set up Grafana dashboards by connecting Prometheus for metrics and Loki for logs, then applying prebuilt patterns for health, dependency health, and on-call readiness to visualize capacity planning and debug incidents effectively.

Can I use OpenTelemetry and Jaeger for distributed tracing in existing applications?

Yes, you can apply this observability strategy to existing cloud-native applications by integrating Jaeger and OpenTelemetry to collect traces, correlating them with metrics and logs for comprehensive incident debugging and performance analysis.

What's the best way to define SLIs and SLOs for on-call readiness?

Define SLIs and SLOs by establishing reliability targets based on the four golden signals, then configure alerting rules in Alertmanager and build runbooks to ensure on-call readiness and validate end-to-end observability for your services.