skills.rest
lookatitude
lookatitudeCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

devops-observability-setup

Instrument services with SLIs, SLOs, traces, dashboards, and alerts.

6|Updated Apr 24, 2026
Search Tags:#logs#metrics#dashboard#observability#tracing#alerting#slo
One-click install
npx skills add https://github.com/lookatitude/guild --skill devops-observability-setup
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: devops-observability-setup
Source: https://github.com/lookatitude/guild/tree/main/skills/specialists/devops-observability-setup
Command: npx skills add https://github.com/lookatitude/guild --skill devops-observability-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Service health and performance are often opaque, making incidents longer and harder to diagnose. This skill provides a standardized approach to instrumenting a service with metrics, logs, tracing, SLOs, dashboards, and alerts so on-call can answer "is it healthy?" in minutes.

Core Features & Use Cases

  • Instrument a service with 3–5 SLIs and convert them into SLOs with error budgets.
  • Emit structured logs with a correlation identifier to enable end-to-end tracing.
  • Wire distributed tracing across service boundaries and export dashboard-as-code artifacts.
  • Define alert rules from SLO burn rates and route them through a single paging mechanism.
  • Maintain dashboard-as-code alongside the service for reproducibility and audits.

Quick Start

Configure observability for your service by wiring SLIs, SLOs, alerts, and traces and commit a dashboard-as-code file alongside the service.

Frequently Asked Questions about devops-observability-setup

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

FAQPage Schema
How do I set up observability for a microservice with metrics, logs, and tracing?▼

You set up observability by defining SLIs and SLOs, emitting structured logs with correlation IDs, wiring distributed tracing across service boundaries, and exporting dashboard-as-code artifacts for health monitoring.

What is the best way to define SLOs and alert rules for distributed systems?▼

The best way to define SLOs is to convert SLIs into SLOs with error budgets, then define alert rules from SLO burn rates and route them through a single paging mechanism for efficient incident response.

How does structured logging with correlation IDs improve incident diagnosis?▼

Structured logging with correlation IDs enables end-to-end tracing across distributed systems, allowing on-call teams to diagnose service health and pinpoint performance bottlenecks during incidents in minutes.

Can I maintain dashboards as code alongside my service for reproducibility?▼

Yes, you can maintain dashboard-as-code files committed alongside your service to ensure reproducibility and audits, standardizing service health monitoring across deployment environments.

Does this observability setup apply to both new and existing services?▼

Yes, this observability setup applies to both new and existing services, enabling teams to instrument new microservices and monitor existing ones across deployment environments with standardized SLIs and SLOs.

Related Skills

Explore More Software Engineering Skills→
julianobarbosajulianobarbosa
7

opentelemetry

Automates OpenTelemetry collector deployment and pipeline configuration in Kubernetes environments.

Community
Advanced
1k-off1k-off
1

alerting-irm

Provision Grafana alert rules, contact points, and notification policies via YAML.

Community
Intermediate
majiayu000majiayu000
104

observability-architecture

Configure Prometheus metrics, OpenTelemetry traces, and JSON logs for LiteLLM gateway.

Community
Advanced
ricardorochericardoroche
2

monitoring-alerting

Automate Prometheus/Grafana monitoring, alerting, and SLO/SLI definitions.

Community
Intermediate