observability-and-instrumentation

Implement structured logging, metrics, distributed tracing, and alerting with OpenTelemetry and Prometheus.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/tgmarinho/agent-super-powers-matt-pocock-skills-comparasions --skill observability-and-instrumentation-tgmarinho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: observability-and-instrumentation
Source: https://github.com/tgmarinho/agent-super-powers-matt-pocock-skills-comparasions/tree/main/upstream-snapshots/agent-skills/skills/observability-and-instrumentation
Command: npx skills add https://github.com/tgmarinho/agent-super-powers-matt-pocock-skills-comparasions --skill observability-and-instrumentation-tgmarinho

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @opentelemetry/sdk-node, prom-client, winston, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that production code is instrumented to provide visibility and diagnostic capabilities, aiding in quick resolution of issues and efficient feature launches.

Core Features & Use Cases

  • Code Instrumentation: Facilitates logging, metrics, tracing, and alerting to enhance observability.
  • Structured Logging: Implements JSON-structured logs for better queryability and consistency.
  • Metrics: Utilizes RED (Rate, Errors, Duration) and USE (Utilization, Saturation, Errors) metrics for endpoint and resource monitoring.
  • Distributed Tracing: Integrates OpenTelemetry for tracking cross-service latency and request flow.
  • Alerting: Configures symptom-based alerts to notify on actionable issues.
  • Use Case: Before deploying a new feature, use this Skill to set up monitoring and alerting that will help identify and resolve any issues post-launch.

Quick Start

Run the 'instrument_feature' script with the feature name as an argument to add observability to your new feature.

Frequently Asked Questions about observability-and-instrumentation

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

FAQPage Schema
How do I add structured logging and metrics to a new feature before deployment?

To add observability to a new feature, run the 'instrument_feature' script with the feature name as an argument. This automatically implements JSON-structured logging and metrics to provide production visibility and diagnostic capabilities.

What is the best way to implement distributed tracing for cross-service latency tracking?

Distributed tracing is best implemented by integrating the OpenTelemetry SDK to track cross-service latency and request flow. This provides end-to-end visibility into how requests propagate through your microservices architecture.

Does this observability setup support RED and USE metrics for endpoint monitoring?

Yes, this observability setup supports RED (Rate, Errors, Duration) metrics for endpoint monitoring and USE (Utilization, Saturation, Errors) metrics for resource monitoring, utilizing prom-client to expose the data.

Can I configure symptom-based alerting alongside structured logging in a Node.js application?

Yes, you can configure symptom-based alerting alongside structured logging in a Node.js application. By using Winston for JSON-structured logs and setting up alerts, you get notified on actionable issues post-launch.

Do I need OpenTelemetry and Prometheus to set up tracing and metrics for my production code?

Yes, you need the OpenTelemetry SDK for distributed tracing and prom-client for metrics collection. These dependencies are required to instrument production code for effective monitoring and performance analysis.

Why should I use JSON-structured logs instead of plain text for application observability?

You should use JSON-structured logs because they provide better queryability and consistency than plain text. This structured format is essential for efficient feature launches and quick resolution of production issues.