One-click install
npx skills add https://github.com/framecastdev/framecast --skill observability-framecastdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: observability
Source: https://github.com/framecastdev/framecast/tree/main/.claude/skills/observability
Command: npx skills add https://github.com/framecastdev/framecast --skill observability-framecastdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams diagnose and fix production issues quickly by providing structured logging, traces, and metrics.

Core Features & Use Cases

  • Structured logging with correlation IDs to enable end-to-end traceability
  • Distributed tracing using OpenTelemetry to map request flows across services
  • Health checks and readiness endpoints to determine service readiness
  • Metrics collection and dashboards for real-time performance visibility

Quick Start

Instrument your services to emit logs, traces, and metrics for end-to-end visibility.

Frequently Asked Questions about observability

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

FAQPage Schema
How do I implement distributed tracing across microservices using OpenTelemetry?

Distributed tracing maps request flows across microservices by instrumenting services with OpenTelemetry to emit traces, enabling end-to-end visibility for issue diagnosis and performance optimization in distributed systems.

What is the best way to add correlation IDs to structured logging for production issues?

Adding correlation IDs to structured logging enables end-to-end traceability across services, allowing teams to quickly diagnose and fix production issues by tracking request flows through correlated log entries.

How do you set up health checks and readiness endpoints for microservices?

Health checks and readiness endpoints determine service readiness in distributed systems by collecting metrics and exposing endpoints, providing real-time performance visibility through dashboards to monitor system health.

Does this observability approach work for existing microservices without major code rewrites?

This observability approach applies to microservices and distributed systems by instrumenting existing services to emit logs, traces, and metrics without requiring complete rewrites, supporting end-to-end visibility.

Why do I need both distributed tracing and metrics collection for reliable services?

Distributed tracing maps request flows across services while metrics collection provides real-time performance visibility through dashboards; together they enable end-to-end visibility and quick issue diagnosis.

When should I not use OpenTelemetry for observability in my application?

OpenTelemetry for observability suits microservices and distributed systems needing end-to-end visibility; simpler monolithic applications with basic logging needs may not require distributed tracing and metrics collection overhead.