observability

Automate observability setup with OpenTelemetry, structured logging, and Prometheus/Grafana metrics.

9|1|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/calcosmic/Aether --skill observability-calcosmic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: observability
Source: https://github.com/calcosmic/Aether/tree/main/.aether/skills-codex/domain/observability
Command: npx skills add https://github.com/calcosmic/Aether --skill observability-calcosmic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Logging, metrics, and tracing infrastructure are often fragmented, making it hard to diagnose failures and optimize performance. This Skill standardizes and guides the implementation of observability practices across projects to provide unified visibility.

Core Features & Use Cases

  • OpenTelemetry integration for automatic trace collection and contextual propagation across services.
  • Centralized logging standards with structured logs, trace IDs, and consistent log levels for faster incident response.
  • Metrics strategy using Prometheus/Grafana for latency, throughput, and error tracking, plus dashboards for golden signals.
  • Distributed tracing and alerting to detect bottlenecks, enable root-cause analysis, and enforce SLOs.
  • Use Case: Deploy in a microservices architecture to monitor service health, trace requests, and alert on SLA breaches.

Quick Start

Instrument services with OpenTelemetry, standardize structured logging, and expose metrics and traces for centralized monitoring.

Frequently Asked Questions about observability

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

FAQPage Schema
How do I set up OpenTelemetry tracing and structured logging in a microservices architecture?

Set up OpenTelemetry tracing and structured logging by instrumenting services to automatically collect traces and propagate context across services. Standardize logs with consistent levels and trace IDs for centralized monitoring and faster incident response.

What is the best way to standardize Prometheus and Grafana metrics for golden signal dashboards?

Standardize Prometheus and Grafana metrics by implementing a consistent metrics strategy for latency, throughput, and error tracking. This approach creates dashboards for golden signals, enabling reliable performance insight and bottleneck detection.

Why do I need distributed tracing and centralized logging for incident response?

You need distributed tracing and centralized logging for incident response because fragmented infrastructure makes diagnosing failures difficult. Unified visibility with trace IDs enables root-cause analysis and detects service bottlenecks.

Can I enforce SLOs and alerting using OpenTelemetry and Prometheus integration?

You can enforce SLOs and alerting using OpenTelemetry and Prometheus integration. This combination standardizes observability practices, enabling automatic trace collection, error tracking, and automated alerts on SLA breaches for reliable monitoring.

How do I turn observability data into reliability for application monitoring?

Turn observability data into reliability by standardizing logging, tracing, and metrics across applications. Applying OpenTelemetry integration and SLO enforcement provides unified visibility to diagnose failures, optimize performance, and maintain service health.