observability-and-instrumentation

Instrument code with structured logging, metrics, tracing, and alerting.

63|14|Updated Jun 6, 2026
One-click install
npx skills add https://github.com/HsienW/chat-gun-react-agent --skill observability-and-instrumentation-hsienw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: observability-and-instrumentation
Source: https://github.com/HsienW/chat-gun-react-agent/tree/main/.agents/skills/observability-and-instrumentation
Command: npx skills add https://github.com/HsienW/chat-gun-react-agent --skill observability-and-instrumentation-hsienw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you instrument your code to make production behavior visible and diagnosable, crucial for effective logging, metrics, tracing, and alerting.

Core Features & Use Cases

  • Logging: Structured logging for better queryability and consistency.
  • Metrics: Instrumentation for RED (Rate, Errors, Duration) and USE (Utilization, Saturation, Errors) for resources.
  • Tracing: Distributed tracing with OpenTelemetry for service-to-service latency insights.
  • Alerting: Symptom-based alerting to notify on actionable issues.

Quick Start

Use the observability-and-instrumentation skill to instrument your service for monitoring and alerting.

Frequently Asked Questions about observability-and-instrumentation

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

FAQPage Schema
How do I instrument production code for logging, metrics, and tracing?

Instrument production code by adding structured logging, RED and USE metrics, and OpenTelemetry distributed tracing to make system behavior visible and diagnosable post-deployment.

What is structured logging and how does it improve queryability?

Structured logging formats log data into consistent, queryable fields, enabling better searchability and analysis when diagnosing production system behavior and actionable alerting.

Does distributed tracing with OpenTelemetry work for diagnosing service-to-service latency?

Yes, distributed tracing with OpenTelemetry provides service-to-service latency insights, helping you diagnose performance bottlenecks and monitor production system behavior effectively.

What's the best way to set up alerting for production systems?

The best way to set up alerting is using symptom-based alerts that notify on actionable issues, ensuring production code remains observable and diagnosable without alert fatigue.

When do I need RED and USE metrics for observability?

You need RED metrics for service rate, errors, and duration, and USE metrics for resource utilization and saturation, to comprehensively monitor production system health and performance.