observability-and-instrumentation

Instrument code with logging, metrics, tracing, and alerting using OpenTelemetry and Prometheus.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires opentelemetry, prom-client, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps engineers instrument their code for production, ensuring that system behavior is visible and diagnosable, crucial for post-launch monitoring and incident response.

Core Features & Use Cases

  • Code Instrumentation: Adds logging, metrics, tracing, and alerting to code.
  • On-Call Questions: Defines clear questions that on-call engineers will ask about a feature.
  • Structured Logging: Implements structured logging for better log analysis.
  • Metrics: Tracks RED (Rate, Errors, Duration) metrics for services and resources.
  • Distributed Tracing: Implements OpenTelemetry for cross-service request tracing.
  • Alerting: Sets up symptom-based alerts for actionable events.

Quick Start

Run the observability-and-instrumentation skill to instrument your codebase for production readiness.

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 code for production monitoring and incident response?

Instrument code for production monitoring by adding structured logging, metrics, tracing, and alerting to ensure system behavior is visible and diagnosable for post-launch incident response.

What are RED metrics and how do I track them for my services?

RED metrics track Rate, Errors, and Duration for services and resources. You track them using Prometheus to measure request throughput, failure rates, and latency for production visibility.

How do I implement distributed tracing with OpenTelemetry for cross-service requests?

Implement distributed tracing with OpenTelemetry to trace cross-service requests, allowing on-call engineers to diagnose system behavior and pinpoint failures across production services.

What is the best way to set up alerting for on-call engineers?

The best way to set up alerting for on-call engineers is configuring symptom-based alerts for actionable events, ensuring notifications trigger only for significant production issues requiring intervention.

Can I use Prometheus with OpenTelemetry for logging and metrics?

Yes, you can use Prometheus with OpenTelemetry to implement metrics tracking and distributed tracing, covering production monitoring requirements for structured logging and cross-service request diagnosis.

Why do I need structured logging for better log analysis?

Structured logging formats log entries as parseable data, enabling better log analysis tools to filter, search, and correlate production events during post-launch monitoring and incident response.