observability

Guide observability design with structured logging, tracing, metrics, health checks, alerting, and error tracking.

2|Updated Feb 15, 2026

Search Tags:#monitoring #logging #metrics #observability #tracing #alerting

Ready to run

npx skills add https://github.com/nakano1122/dotfiles --skill observability-nakano1122

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: observability
Source: https://github.com/nakano1122/dotfiles/tree/main/dot_agents/skills/observability
Command: npx skills add https://github.com/nakano1122/dotfiles --skill observability-nakano1122

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive guide to designing and implementing observability in applications, ensuring you can effectively monitor, troubleshoot, and understand system behavior.

Core Features & Use Cases

Structured Logging: Design effective, machine-readable logs with clear levels and essential fields.
Request Tracing: Implement correlation IDs and distributed tracing to follow requests across services.
Metrics Design: Utilize RED and USE methods for robust performance and resource monitoring.
Health Checks & Alerting: Define health endpoints and set up actionable alerts.
Error Tracking: Establish best practices for capturing and analyzing errors.
Use Case: When building a new microservice, use this Skill to define its logging format, set up Prometheus metrics for request rates and durations, and configure basic health checks.

Quick Start

Use the observability skill to design a structured logging format for your application.

Frequently Asked Questions about observability

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

FAQPage Schema

What is observability and how does it help troubleshoot distributed systems?▼

Yes, the observability guide is framework-agnostic and applies to any application. It is essential for building maintainable and debuggable distributed systems, regardless of the specific technology stack or platform used.

How do I design structured logging for application observability?▼

Structured logging creates machine-readable logs with clear levels and essential fields. This format enables effective troubleshooting and system analysis by making log data easily parsable and queryable during application monitoring.

How do I implement request tracing across microservices?▼

Implement request tracing using correlation IDs and distributed tracing to follow requests across services. This allows you to track a request's full path through microservices, identifying bottlenecks and failures in distributed systems.

What is the best way to monitor application performance with metrics?▼

RED and USE methods are frameworks for robust performance and resource monitoring. RED tracks Rate, Errors, and Duration for services, while USE monitors Utilization, Saturation, and Errors for resources, enabling comprehensive metrics design.

How do I set up health checks and actionable alerting?▼

Set up health checks by defining health endpoints and establishing actionable alerts. Combine this with error tracking best practices to capture and analyze failures, ensuring you receive meaningful notifications about system state.

Can I use this observability guide for any framework or platform?▼