observe

Instrument services with Prometheus metrics, structured JSON logs, and OpenTelemetry traces.

26|8|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/arbazkhan971/godmode --skill observe-arbazkhan971
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: observe
Source: https://github.com/arbazkhan971/godmode/tree/main/skills/observe
Command: npx skills add https://github.com/arbazkhan971/godmode --skill observe-arbazkhan971

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams and services that lack reliable monitoring, structured logs, and distributed traces struggle to detect, diagnose, and measure incidents; this Skill implements end-to-end observability so engineering teams can rapidly find and fix production issues and verify reliability improvements.

Core Features & Use Cases

  • Metrics & Instrumentation: Define RED/USE and business metrics, recommend low-cardinality Prometheus metrics and cardinality limits.
  • Structured Logging: Enforce JSON logs, include request_id and trace_id, and exclude PII and secrets.
  • Distributed Tracing: Auto-instrument with OpenTelemetry, propagate trace IDs, and recommend sampling strategies.
  • SLOs, Alerts & Dashboards: Create SLIs/SLOs, error-budget aware alerts with proper for durations, and dashboards covering the Four Golden Signals.
  • Use Case: Add monitoring and alerting to an API service to detect p99 latency regressions, capture traces for slow requests, and notify on error budget burn.

Quick Start

Add Prometheus metrics, structured JSON logs with request_id, and OpenTelemetry traces, then define an SLO and a critical alert for high error rate.

Frequently Asked Questions about observe

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

FAQPage Schema
How do I add distributed tracing and structured logging to a web service?

To add distributed tracing and structured logging, instrument services with OpenTelemetry to propagate trace IDs and enforce JSON logs that include request IDs while excluding PII, enabling fast incident diagnosis.

What is the best way to define SLOs and error budget alerts for an API?

Defining SLOs and error budget alerts involves creating SLIs, setting error-budget aware alerts with proper for durations, and building dashboards to track the Four Golden Signals for API reliability.

How do I prevent high cardinality when instrumenting Prometheus metrics?

Prevent high cardinality in Prometheus metrics by defining low-cardinality RED and USE metrics, enforcing cardinality limits, and avoiding unbounded labels like user IDs in your monitoring instrumentation.

Can I use this observability approach for debugging slow requests in distributed systems?

Yes, you can use this observability approach for debugging slow requests in distributed systems by capturing propagated trace IDs across services to pinpoint latency bottlenecks during incident response.

Why should structured logs exclude PII and secrets during application monitoring?

Structured logs should exclude PII and secrets during application monitoring to maintain security compliance, prevent sensitive data exposure in dashboards, and ensure safe diagnostic access across engineering teams.