observability-and-instrumentation

Name: observability-and-instrumentation
Availability: InStock
Author: Boris

Instrument production code with structured logs, metrics, traces, and alerts.

1|1|Updated Apr 11, 2026

Search Tags:#logging #metrics #observability #tracing #instrumentation #alerts #telemetry

Ready to run

npx skills add https://github.com/Borisserz/FoodTracker --skill observability-and-instrumentation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: observability-and-instrumentation
Source: https://github.com/Borisserz/FoodTracker/tree/main/.agents/skills/skills/observability-and-instrumentation
Command: npx skills add https://github.com/Borisserz/FoodTracker --skill observability-and-instrumentation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code that runs in production often runs unseen. This skill provides observability and instrumentation to make production behavior visible and diagnosable through telemetry such as logs, metrics, traces, and alerts.

Core Features & Use Cases

Structured logging: stable event names and fields to answer: what happened, where, and why.
Metrics and dashboards: RED/USE patterns to quantify latency, errors, and throughput with low-cardinality labels.
Distributed tracing: end-to-end request tracing to identify bottlenecks across services.
Alerts and runbooks: symptom-based alerts with actionable guidance and runbooks.

Quick Start

Instrument a new feature by adding structured logging, metrics, and traces to production code and validate telemetry in staging.

Frequently Asked Questions about observability-and-instrumentation

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

FAQPage Schema

What is observability and instrumentation in production code?▼

Structured logging uses stable event names and fields to answer what happened, where, and why, ensuring production events are consistently captured and queryable for incident diagnosis.

How do I instrument code with OpenTelemetry tracing for new services?▼

Apply OpenTelemetry distributed tracing to new services and endpoints to achieve end-to-end request visibility, identifying bottlenecks across services and diagnosing incidents effectively.

Why do metrics need low-cardinality labels for dashboards?▼

Metrics need low-cardinality labels to prevent unbounded dimensional growth, ensuring dashboards using RED/USE patterns to quantify latency, errors, and throughput remain performant and queryable.

What's the best way to set up alerts and runbooks for production incidents?▼

Configure symptom-based alerts with actionable guidance and runbooks so that production telemetry triggers meaningful notifications with clear, guided incident response steps.

Can I use this instrumentation for background jobs and external integrations?▼

Yes, the instrumentation applies to new services, endpoints, background jobs, and external integrations, ensuring all production code paths are monitored and diagnosable for reliability.

JCE-Joshhh77

observability

Wire traces, metrics, and logs across distributed systems using OpenTelemetry, Prometheus, and Grafana; instrument, dashboard, alert, and verify in dev to prod.

Community

Advanced