skills.rest
MDLDev-site
MDLDev-siteOFFICIAL
Explore all skills by this author →
GitHub

observability-engineer

Create observability blueprints for logs, metrics, and traces in distributed systems.

Updated Aug 23, 2026
Search Tags:#debugging#logs#metrics#observability#alerting#traces#incident
One-click install
npx skills add https://github.com/MDLDev-site/mdl-brand-website --skill observability-engineer-mdldev-site
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: observability-engineer
Source: https://github.com/MDLDev-site/mdl-brand-website/tree/main/.claude/skills/observability-engineer
Command: npx skills add https://github.com/MDLDev-site/mdl-brand-website --skill observability-engineer-mdldev-site

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Observability is foundational to debugging and reliability; this skill defines a practical blueprint for turning complex systems into observable ones by integrating structured logs, metrics, and traces, setting correlation IDs, and establishing SLO-based alerting.

Core Features & Use Cases

  • Build comprehensive observability into distributed systems with unified logs, metrics, and traces.
  • Enable fast incident response through correlation IDs, dashboards, and guided debugging workflows.
  • Establish standardized instrumentation, SLOs, and cost-conscious data collection across services.

Quick Start

Configure your services to emit structured logs, metrics, and traces, and wire them into central dashboards and alerting.

Frequently Asked Questions about observability-engineer

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

FAQPage Schema
How do I set up observability for distributed systems like microservices and serverless?▼

Observability for distributed systems is achieved by configuring services to emit structured logs, metrics, and traces. This blueprint enables standardized instrumentation, correlation IDs, and central dashboards for end-to-end request visibility.

What is the best way to correlate logs and traces during an incident?▼

The best way to correlate logs and traces is by setting correlation IDs across service boundaries. This approach enables fast incident response by linking end-to-end request flows with structured log data for guided debugging workflows.

How do I establish SLO-based alerting rules for production services?▼

Establish SLO-based alerting by defining standardized instrumentation and cost-conscious data collection across services. This blueprint helps you set actionable alerts and SLOs that trigger reliable, guided debugging workflows during incidents.

Can I use this observability blueprint for event-driven architectures?▼

Yes, this observability blueprint applies to event-driven architectures. It provides standardized instrumentation and end-to-end request tracing to make modern distributed systems fully visible, debuggable, and reliable.

How do I implement cost-conscious data collection for metrics and logs?▼

Cost-conscious data collection is implemented by standardizing instrumentation and filtering telemetry data across services. This blueprint helps you establish efficient observability pipelines that collect actionable metrics and logs without excessive overhead.

Related Skills

Explore More Software Engineering Skills→
InfinityBowmanInfinityBowman
3

Observability Analysis

Audit production observability stacks for logging, tracing, metrics, alerting, and debuggability.

Community
Advanced
pluginagentmarketplacepluginagentmarketplace
1

monitoring

Integrate Prometheus, Grafana, Loki, and OpenTelemetry for Kubernetes observability.

Community
Advanced
thejordanleopoldthejordanleopold
4

observability

Collect logs, metrics, and traces with OpenTelemetry for service observability.

Community
Advanced
ajianazajianaz
4

observability-monitor

Orchestrate end-to-end observability and monitoring for complex applications.

Community
Advanced