observability-setup

Set up logging, metrics, health checks, and alerting for production services.

Updated Nov 22, 2025
One-click install
npx skills add https://github.com/Khamel83/oneshot --skill observability-setup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: observability-setup
Source: https://github.com/Khamel83/oneshot/tree/main/archive/v9/skills/observability-setup
Command: npx skills add https://github.com/Khamel83/oneshot --skill observability-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Set up observability infrastructure for production systems, including logging, metrics, health checks, and alerting.

Core Features & Use Cases

  • Structured logging to enable reliable incident analysis and troubleshooting
  • Health check endpoints (e.g., /health, /ready) to signal service readiness
  • Prometheus-compatible metrics and dashboards guidance for actionable insights
  • Clear runbooks and alerting configurations to reduce MTTR

Quick Start

Provide your production service details and ask me to set up logging, metrics, health checks, and alerting.

Frequently Asked Questions about observability-setup

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

FAQPage Schema
How do I set up observability for microservices in production?

Setting up observability for microservices requires structured logging, health check endpoints like /health and /ready, Prometheus-compatible metrics exposition, and clear alerting configurations to monitor readiness and incidents.

What's the best way to configure Prometheus metrics and alerting for web services?

The best way to configure Prometheus metrics and alerting is to implement metric exposition in your web services alongside structured logging and health endpoints to generate actionable insights and reduce mean time to resolution.

Why do I need health check endpoints like /health and /ready in production?

Health check endpoints like /health and /ready are needed in production to signal service readiness to orchestration platforms, enabling reliable incident analysis and preventing traffic from routing to unavailable instances.

Can I use this observability setup for typical web services without extra dependencies?

Yes, you can use this observability setup for typical web services without extra dependencies, as it focuses on standard health routes, basic logging formats, and metric exposition across common service architectures.

When do I need structured logging for incident analysis and troubleshooting?

You need structured logging for incident analysis and troubleshooting when operating production systems that require reliable event tracking to reduce mean time to resolution during outages or performance degradation.