monitoring-observability

Define structured logging, metrics, tracing, and alerting patterns for distributed systems.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/ps-carvalho/cortex-agents --skill monitoring-observability-ps-carvalho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monitoring-observability
Source: https://github.com/ps-carvalho/cortex-agents/tree/main/.opencode/skills/monitoring-observability
Command: npx skills add https://github.com/ps-carvalho/cortex-agents --skill monitoring-observability-ps-carvalho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structured observability patterns help teams debug production issues, improve reliability, and optimize performance by providing consistent logging, metrics, and tracing across services.

Core Features & Use Cases

  • Structured Logging: emit JSON logs with contextual fields (correlation IDs, request IDs, user context) to enable fast debugging and traceability.
  • Metrics & Health Checks: instrument key endpoints, collect latency and error-rate data, and expose health endpoints for readiness checks and dashboards.
  • Distributed Tracing & Alerts: propagate traces across services to map end-to-end requests and define alerting strategies (SLOs, thresholds) for proactive remediation.
  • Use Case: A distributed backend can surface bottlenecks and failures by correlating logs, metrics, and traces to identify root causes quickly.

Quick Start

Configure your service to emit structured JSON logs, integrate metrics for key endpoints, instrument traces across services, expose a health check endpoint, and set up alerting based on defined SLOs.

Frequently Asked Questions about monitoring-observability

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

FAQPage Schema
How do I implement structured logging with correlation IDs for microservices?

Implement structured logging by emitting JSON logs with contextual fields like correlation IDs, request IDs, and user context. This enables fast debugging and traceability across distributed systems by standardizing log formats for consistent observability.

What is distributed tracing and how does it map end-to-end requests?

Distributed tracing propagates traces across services to map end-to-end requests in distributed systems. It correlates logs, metrics, and traces to surface bottlenecks and failures, helping identify root causes quickly by providing full request visibility.

How do I set up health check endpoints and metrics for backend services?

Set up health check endpoints by exposing readiness checks and instrumenting key endpoints to collect latency and error-rate metrics. This exposes service health for dashboards and enables proactive monitoring of backend service reliability.

What's the best way to define alerting strategies and SLOs for production monitoring?

Define alerting strategies by establishing SLOs and thresholds for proactive remediation. Standardized observability patterns with metrics collection and health monitoring allow teams to set meaningful alerts that catch production issues before they impact users.

Can I use these observability patterns for distributed systems needing end-to-end instrumentation?

Yes, these observability patterns apply to distributed systems needing end-to-end instrumentation. They provide standardized logging, metrics, and tracing for microservices and backend services, defining requirements for structured logging, tracing instrumentation, and health monitoring.