observability-engineer

Define SLIs and SLOs for user-facing APIs.

2|Updated Mar 15, 2025
One-click install
npx skills add https://github.com/dandudzi/dotfiles --skill observability-engineer-dandudzi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: observability-engineer
Source: https://github.com/dandudzi/dotfiles/tree/main/dot_claude/skills/observability-engineer
Command: npx skills add https://github.com/dandudzi/dotfiles --skill observability-engineer-dandudzi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you build and maintain robust observability systems, ensuring your applications are reliable, performant, and compliant.

Core Features & Use Cases

  • SLI/SLO Definition & Management: Define, track, and alert on service level objectives to manage reliability.
  • OpenTelemetry Integration: Guide migration and implementation of OpenTelemetry for unified tracing, metrics, and logs.
  • Distributed Tracing & Logging: Analyze complex system behavior and debug issues across microservices.
  • Chaos Engineering: Design and execute experiments to proactively identify weaknesses.
  • Use Case: You're tasked with improving the observability of a new microservice. Use this Skill to define appropriate SLIs/SLOs, instrument the service with OpenTelemetry, set up structured logging, and configure alerts based on error budgets.

Quick Start

Use the observability-engineer skill to define SLIs and SLOs for a user-facing API.

Frequently Asked Questions about observability-engineer

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

FAQPage Schema
How do I define SLIs and SLOs for a microservice API?

To define SLIs and SLOs for a microservice, identify key user-facing metrics like latency and availability, then set target objectives to manage reliability and configure alerts based on error budgets.

What is the best way to migrate to OpenTelemetry for distributed tracing?

Migrating to OpenTelemetry involves integrating its SDKs to unify tracing, metrics, and logs, enabling you to analyze complex system behavior and debug issues across microservices effectively.

How does chaos engineering improve system reliability?

Chaos engineering improves system reliability by designing and executing controlled experiments that proactively identify weaknesses in your system architecture before they cause actual outages.

How do I set up structured logging for compliance and performance monitoring?

Set up structured logging by standardizing log formats with contextual metadata, which ensures applications remain compliant and allows for efficient debugging of complex system behavior.

Can I use OpenTelemetry with existing alerting systems to track error budgets?

Yes, OpenTelemetry integration supports unified metrics collection that can feed into existing alerting systems to track error budgets and manage service level objectives effectively.

When do I need distributed tracing in an observability stack?

You need distributed tracing in an observability stack when analyzing complex system behavior across microservices, allowing you to pinpoint latency bottlenecks and debug issues accurately.