Observability & Monitoring

Implements structured logging, metrics, distributed tracing, and alerting for production systems.

1|Updated Mar 5, 2026

Search Tags:#monitoring #logging #metrics #observability #alerting #opentelemetry #distributed tracing

Ready to run

npx skills add https://github.com/fabioc-aloha/AlexAgent --skill observability-monitoring-fabioc-aloha

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Observability & Monitoring
Source: https://github.com/fabioc-aloha/AlexAgent/tree/main/plugin/skills/observability-monitoring
Command: npx skills add https://github.com/fabioc-aloha/AlexAgent --skill observability-monitoring-fabioc-aloha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Production systems fail in ways that are hard to reproduce locally, and without logs, metrics, and traces, teams cannot see what is happening or debug issues at scale. ## Core Features & Use Cases - Three Pillars Guidance: Covers structured logging with correlation IDs, metrics using RED/USE methods and golden signals, and distributed tracing with context propagation. - OpenTelemetry Setup: Provides quick-start instrumentation for Node.js and .NET, plus cloud integrations with Azure Application Insights, AWS CloudWatch/X-Ray, and GCP tools. - Alerting & Dashboards: Defines alert severity hierarchies, anti-patterns to avoid, Prometheus alert rules with runbooks, and dashboard layout principles. - Use Case: When a checkout service shows elevated P99 latency, use trace-driven debugging to find the slow span, then add a Prometheus alert with a runbook so the issue is caught before users report it. ## Quick Start Ask the AI to set up OpenTelemetry tracing and structured logging with correlation IDs for your Node.js service.

Frequently Asked Questions about Observability & Monitoring

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

FAQPage Schema

How do I set up OpenTelemetry in Node.js?▼

OpenTelemetry setup in Node.js uses the NodeSDK with auto-instrumentations and an OTLP trace exporter pointing to your collector endpoint. Load the tracing module first before other imports so instrumentation hooks apply correctly.

What is the difference between logs, metrics, and traces?▼

Logs record discrete events for debugging and auditing, metrics aggregate measurements for alerting and dashboards, and traces show request flow across services. OpenTelemetry unifies all three pillars in one instrumentation framework.

How do I track requests across microservices with correlation IDs?▼

Correlation IDs propagate via middleware that reads or generates an x-trace-id header and includes it in every log entry. OpenTelemetry context propagation handles this automatically by extracting and injecting trace context into request headers.

What metrics should I monitor for a web service?▼

Use the RED method for services: request rate, error rate, and duration. For infrastructure resources, apply the USE method: utilization, saturation, and errors, covering the four SRE golden signals of latency, traffic, errors, and saturation.

Why does alert fatigue happen and how do I avoid it?▼

Alert fatigue happens when teams receive too many non-actionable alerts without runbooks or owners. Avoid it by using severity tiers, alerting on trends rather than static thresholds, and attaching runbook and dashboard links to every alert.

Does this observability approach work with Azure Application Insights?▼

Yes, Azure Application Insights integrates through the @azure/monitor-opentelemetry package using a connection string. Equivalent integrations exist for AWS CloudWatch with X-Ray and GCP Cloud Monitoring with Cloud Trace.