Observability & Monitoring

Set up OpenTelemetry instrumentation for Node.js and .NET applications.

1|1|Updated Nov 20, 2025
One-click install
npx skills add https://github.com/fabioc-aloha/AIRS_Data_Analysis --skill observability-monitoring-fabioc-aloha
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Observability & Monitoring
Source: https://github.com/fabioc-aloha/AIRS_Data_Analysis/tree/main/.github/skills/observability-monitoring
Command: npx skills add https://github.com/fabioc-aloha/AIRS_Data_Analysis --skill observability-monitoring-fabioc-aloha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides comprehensive visibility into production systems, enabling developers and SREs to understand behavior, debug issues, and ensure reliability through logs, metrics, and traces.

Core Features & Use Cases

  • Three Pillars of Observability: Understand and implement logging, metrics, and distributed tracing.
  • Best Practices: Learn structured logging, correlation IDs, RED/USE methods, and span structure.
  • Tooling & Setup: Get quick starts for OpenTelemetry in Node.js and .NET, and cloud provider tools.
  • Alerting & Dashboards: Design effective alerting strategies and dashboard layouts.
  • Use Case: When a critical service experiences intermittent errors, use this Skill to analyze logs with correlation IDs, examine trace waterfalls for bottlenecks, and check key metrics like error rates and latency to pinpoint the root cause.

Quick Start

Use the observability monitoring skill to set up OpenTelemetry instrumentation in a Node.js application.

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 instrumentation in a Node.js application?

Set up OpenTelemetry in Node.js by configuring the SDK to export traces, metrics, and structured logs, establishing distributed tracing to debug production issues and understand system behavior at scale.

What is the best way to debug intermittent errors in microservices using distributed tracing?

Debug intermittent errors using distributed tracing by examining trace waterfalls for bottlenecks, analyzing structured logs with correlation IDs, and checking RED metrics like error rates and latency to pinpoint the root cause.

When do I need correlation IDs for structured logging?

You need correlation IDs for structured logging when tracking requests across distributed services, allowing you to link related log entries together to understand behavior and debug issues at scale.

Does this observability skill support .NET applications?

Yes, this observability skill supports .NET applications by providing quick starts for OpenTelemetry setup, enabling production visibility through metrics, logs, and distributed traces in .NET environments.

What is the difference between RED and USE metrics patterns?

The RED pattern tracks Rate, Errors, and Duration for request-driven services, while the USE pattern monitors Utilization, Saturation, and Errors for resources, helping design effective alerting strategies and dashboard layouts.