observability-monitoring

Implement structured logging, metrics, tracing, and alerting patterns for production services.

7|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/Jonathan0823/opencode-config --skill observability-monitoring-jonathan0823
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: observability-monitoring
Source: https://github.com/Jonathan0823/opencode-config/tree/main/skills/observability-monitoring
Command: npx skills add https://github.com/Jonathan0823/opencode-config --skill observability-monitoring-jonathan0823

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps teams implement robust observability by providing patterns for logging, metrics, tracing, and alerting.

Core Features & Use Cases

  • Structured logging, metrics exposure, and distributed tracing to monitor and diagnose production systems.
  • Alerting strategies and dashboards with Prometheus, Grafana, and Jaeger.
  • Use Case: When debugging a production incident, instrument services and correlate logs, traces, and metrics to identify bottlenecks.

Quick Start

Follow the references to implement logging, metrics, and tracing patterns. Start by enabling structured logging and OpenTelemetry tracing as described in references/logging.md and references/tracing.md.

Frequently Asked Questions about observability-monitoring

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

FAQPage Schema
How do I implement structured logging and distributed tracing for microservices?

Implement structured logging and distributed tracing by following reference patterns for OpenTelemetry integration, enabling microservices instrumentation, log-trace correlation, and production incident diagnosis across services.

What is the best way to set up a monitoring stack with Prometheus and Grafana?

Set up a monitoring stack with Prometheus and Grafana by applying alerting strategies and dashboard validation patterns, providing metrics exposure and visualization capabilities to monitor production system health.

How do I debug a production incident using logs, metrics, and traces?

Debug a production incident by correlating logs, traces, and metrics to identify bottlenecks, using provided patterns to instrument services and validate dashboards for diagnosing root causes across microservices architectures.

Does this observability approach work for microservices architectures?

Yes, this observability approach applies to production services across microservices architectures, providing patterns for logging, metrics, tracing, and alerting specifically designed for distributed systems.

How do I configure alerting rules and validate dashboards for production monitoring?

Configure alerting rules and validate dashboards using provided patterns for Prometheus and Grafana, ensuring proper metrics exposure and alert configuration to maintain production system reliability.

Why do I need OpenTelemetry tracing in my observability setup?

OpenTelemetry tracing is needed to implement distributed tracing across microservices, enabling correlation between logs, traces, and metrics to identify performance bottlenecks during production incidents.