observability-setup

Automate observability configuration for production systems with monitoring, alerting, dashboards, and tracing.

1|Updated Mar 3, 2026

Search Tags:#monitoring #dashboards #observability #tracing #alerting #SLO #open-telemetry

Ready to run

npx skills add https://github.com/ribatshepo/Auto-Orchestrate --skill observability-setup-ribatshepo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: observability-setup
Source: https://github.com/ribatshepo/Auto-Orchestrate/tree/main/claude-code/skills/observability-setup
Command: npx skills add https://github.com/ribatshepo/Auto-Orchestrate --skill observability-setup-ribatshepo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configure monitoring, alerting, dashboards, and distributed tracing for production systems — ensuring SLO alignment and incident readiness.

Core Features & Use Cases

Detect Existing Observability Stack: Scan for Prometheus config, Grafana dashboards, Datadog agent, OpenTelemetry collector, and related files.
Define SLO-Based Monitoring: Establish SLIs and SLO targets for services, with clear error budgets.
Configure Alerting Rules: Create rule templates for 5xx errors, latency thresholds, and health checks with escalation paths.
Dashboard Configuration: Design USE-based dashboards (Utilization, Saturation, Errors) for services and infrastructure.
Distributed Tracing Setup: Ensure OpenTelemetry instrumentation, trace propagation, sampling policies, and log-trace correlation.
Observability Report Generation: Produce a comprehensive observability readiness report with gaps and runbooks.

Quick Start

Run the observability-setup workflow against your project to begin configuring metrics, logs, traces, and dashboards.

Frequently Asked Questions about observability-setup

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

FAQPage Schema

How do I configure monitoring, alerting, and dashboards for production microservices?▼

Configure monitoring, alerting, and dashboards for production microservices by defining SLO-based metrics, generating alert rule templates for error rates and latency, and building USE-based dashboards. This ensures complete observability and incident readiness across distributed services.

How do I set up distributed tracing with OpenTelemetry across microservices?▼

Set up distributed tracing with OpenTelemetry by configuring instrumentation, trace propagation, and sampling policies across microservices. Establish log-trace correlation to ensure end-to-end visibility into request flows and latency bottlenecks.

Does this observability setup work with Prometheus, Grafana, and Datadog integrations?▼

Yes, this observability setup works with Prometheus, Grafana, and Datadog integrations by scanning for existing agent configurations and applying multi-tool integration. It aligns alerting pipelines and dashboards across your existing observability stack.

What is the best way to define SLOs and error budgets for my services?▼

Define SLOs and error budgets for your services by establishing clear Service Level Indicators (SLIs) and target thresholds. This creates measurable reliability targets and guides alerting rules for error budget burn rates.

Can I generate an observability readiness report with runbooks for my release?▼

Yes, you can generate an observability readiness report with runbooks for your release. This report identifies configuration gaps, documents crash-recovery workflows, and verifies SLO alignment and incident readiness before launch.