observability-and-instrumentation

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

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/udsy19/.claude --skill observability-and-instrumentation-udsy19
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: observability-and-instrumentation
Source: https://github.com/udsy19/.claude/tree/main/skills/observability-and-instrumentation
Command: npx skills add https://github.com/udsy19/.claude --skill observability-and-instrumentation-udsy19

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the challenge of maintaining visibility into production code, enabling accurate diagnosis and resolution of issues.

Core Features & Use Cases

  • In-depth Code Instrumentation: Facilitates the addition of logging, metrics, tracing, and alerting to production code.
  • Use Case: When a feature is deployed in production, this Skill ensures that the necessary data is available to diagnose any potential issues that may arise.

Quick Start

Run the observability-and-instrumentation skill to set up monitoring for a new production feature.

Frequently Asked Questions about observability-and-instrumentation

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

FAQPage Schema
What is code instrumentation for production observability?

Code instrumentation for production observability is the process of adding structured logging, metrics, tracing, and alerting to diagnose issues in running features.

How do I add structured logging and distributed tracing to my production code?

You add structured logging and distributed tracing by instrumenting production code with telemetry data, ensuring features generate diagnostic logs and trace spans for issue resolution.

What's the best way to set up RED metrics and alerting for a new production feature?

The best way to set up RED metrics and alerting is to instrument the feature with actionable symptoms, configuring rate, error, and duration metrics to trigger alerts during production issues.

Does this observability approach work for any feature running in production?

Yes, this observability approach applies to any feature running in production that requires diagnostic data, applying structured logging, RED metrics, and distributed tracing without specific dependencies.

Why do I need distributed tracing and telemetry data for production monitoring?

You need distributed tracing and telemetry data for production monitoring to maintain visibility into running code, enabling accurate diagnosis and resolution of issues that arise after deployment.

What are the limitations of relying on basic logging for production diagnosis?

Relying on basic logging limits production diagnosis because it lacks the RED metrics and distributed tracing necessary to pinpoint actionable symptoms across complex deployed features.