observability

Implement structured logging, error tracking, and health checks for web services.

Updated Apr 5, 2023
One-click install
npx skills add https://github.com/fcalell/dotfiles --skill observability-fcalell
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: observability
Source: https://github.com/fcalell/dotfiles/tree/main/dot_claude/skills/observability
Command: npx skills add https://github.com/fcalell/dotfiles --skill observability-fcalell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Observability gaps in systems slow debugging and degrade reliability; this skill provides structured logging, error tracking, and production monitoring patterns to improve observability.

Core Features & Use Cases

  • Structured Logging: define consistent JSON logs with request IDs and context.
  • Error Tracking: integrate providers and capture exceptions with context and tags.
  • Health Monitoring: implement health checks and performance metrics to maintain uptime.
  • Use Case: For a web service, enable end-to-end visibility from request receipt to response with correlated logs.

Quick Start

Run the observability templates to initialize structured logging, error tracking, and monitoring in your project.

Frequently Asked Questions about observability

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

FAQPage Schema
How do I implement structured logging for web services?

Structured logging for web services is implemented using consistent JSON formats with request IDs and contextual data. This enables end-to-end visibility across the request lifecycle from receipt to response.

What is the best way to set up error tracking in production applications?

Error tracking in production applications is set up by integrating error tracking providers to capture exceptions with context and tags. This captures exceptions with relevant contextual data and tags for debugging.

How do I add health checks to a backend system?

Health checks are added to backend systems by implementing performance metrics and uptime monitoring. This maintains system reliability and provides production-readiness checklists for deployment.

Can I use this observability setup for microservices and backend systems?

This observability setup applies to microservices and backend systems. It provides templates and guardrails for log formatting, error-tracking integration, and health checks across modern web services.

Why do I need correlated logs for end-to-end observability?

Correlated logs are needed for end-to-end observability to trace requests across the entire lifecycle. Structured JSON logs with request IDs enable visibility from request receipt to response generation.

What is included in a production-readiness checklist for monitoring?

A production-readiness checklist for monitoring includes structured log formatting, error-tracking integration, and health check implementation. These components ensure uptime and performance metrics are maintained.