observability-setup

Name: observability-setup
Availability: InStock
Author: oalansilva

Configure metrics, logs, and traces with correlation IDs and alert thresholds.

Updated Dec 28, 2025

Search Tags:#logs #metrics #observability #instrumentation #alerting #traces #correlation-id

Ready to run

npx skills add https://github.com/oalansilva/crypto --skill observability-setup-oalansilva

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: observability-setup
Source: https://github.com/oalansilva/crypto/tree/main/.codex/skills/infra/observability-setup
Command: npx skills add https://github.com/oalansilva/crypto --skill observability-setup-oalansilva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide essential observability for a service by configuring metrics, logs, and tracing to give developers visibility into performance and reliability.

Core Features & Use Cases

Instrument logs with correlation IDs to enable end-to-end tracing.
Define service indicators and error budgets to guide stability efforts.
Set up alerting for critical thresholds to prevent outages and SLA breaches.
Output a reproducible instrumentation checklist and alert plan.

Quick Start

Instrument your service with correlation IDs, define key indicators, and configure alerts to establish baseline observability.

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 a mid-sized service with logs, metrics, and traces?▼

To establish observability, you configure metrics, logs, and traces to gain visibility into uptime, latency, and error budgets. This process involves selecting key indicators, implementing log correlation IDs, and defining alert thresholds to produce a reproducible instrumentation checklist.

Why use correlation IDs for end-to-end tracing in my application logs?▼

Using correlation IDs in application logs enables end-to-end tracing across distributed services. Instrumenting logs with these unique identifiers allows developers to track a single request through multiple system components and quickly pinpoint performance bottlenecks or failures.

What's the best way to define service indicators and error budgets for stability?▼

Defining service indicators and error budgets involves selecting core metrics like uptime and latency to guide stability efforts. Establishing these indicators creates a clear baseline for service reliability and helps define acceptable performance thresholds for your application.

How do I configure alerting for critical service thresholds to prevent outages?▼

Configuring alerting for critical thresholds involves setting specific limits on metrics like uptime and latency to prevent outages and SLA breaches. You define these alert thresholds alongside your service indicators to create a reproducible alert plan for your service.

Can I use this observability setup for both frontend and backend components?▼

Yes, this observability setup is applicable to mid-sized services seeking core visibility across both frontend and backend components. It provides a reproducible instrumentation checklist that covers essential metrics, logs, and traces for comprehensive monitoring across your architecture.