observability

Design logging, metrics, and tracing patterns across distributed services.

2|Updated Jan 16, 2026

Search Tags:#logging #metrics #observability #tracing #alerting #sre #health-checks

Ready to run

npx skills add https://github.com/MysMon/Spec-Workflow-Toolkit --skill observability-mysmon

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: observability
Source: https://github.com/MysMon/Spec-Workflow-Toolkit/tree/main/skills/workflows/observability
Command: npx skills add https://github.com/MysMon/Spec-Workflow-Toolkit --skill observability-mysmon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Observability patterns help teams design observable systems by standardizing logging, metrics, and tracing across services, enabling faster debugging and reliable operations.

Core Features & Use Cases

Pattern-agnostic guidance for structured logging, metrics collection, and distributed tracing
Guidance to discover and align with project tooling and conventions
Health checks design and alerting strategies for reliable service delivery

Quick Start

Describe your project stack and I will generate an observability plan.

Frequently Asked Questions about observability

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

FAQPage Schema

How do I design consistent logging, metrics, and tracing across microservices?▼

Consistent logging, metrics, and tracing across microservices require standardizing observable patterns across services. This approach provides concept-first guidance to align conventions independent of specific libraries, enabling faster debugging and reliable operations in distributed systems.

What is the best way to structure distributed tracing and health checks for reliable service delivery?▼

Distributed tracing and health checks for reliable service delivery are structured by designing aligned observable patterns. This provides concept-first guidance and convention alignment to establish consistent tracing and health check strategies across your project stack.

Can I use this observability guidance without committing to a specific metrics or logging library?▼

Yes, you can use this observability guidance without specific metrics or logging libraries. It offers pattern-agnostic guidance for structured logging and metrics collection, helping you discover and align with your project's existing tooling and conventions independently.

How do I create an observability plan for my distributed system stack?▼

To create an observability plan for your distributed system stack, describe your project stack to generate tailored guidance. This produces a comprehensive plan covering logging, metrics, distributed tracing, health checks, and alerting strategies specific to your environment.

Why do I need to standardize alerting strategies and observable patterns across services?▼

Standardizing alerting strategies and observable patterns across services is needed to enable faster debugging and reliable operations. By aligning logging, metrics, and tracing conventions, teams can quickly identify issues and maintain consistent service delivery in distributed systems.

Does this approach support discovering and aligning with existing project tooling for SRE operations?▼

Yes, this approach supports discovering and aligning with existing project tooling for SRE operations. It provides research prompts and convention alignment guidance to integrate health checks, alerting, and observability patterns directly within your current tool ecosystem.