monitoring-observability

Integrate metrics, logs, and traces into unified observability dashboards.

Updated Jun 20, 2025
One-click install
npx skills add https://github.com/Thethetrader/thethetrader --skill monitoring-observability-thethetrader
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monitoring-observability
Source: https://github.com/Thethetrader/thethetrader/tree/main/.cursor/skills/monitoring-observability
Command: npx skills add https://github.com/Thethetrader/thethetrader --skill monitoring-observability-thethetrader

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Production monitoring and observability across metrics, logs, and traces to detect and debug incidents faster.

Core Features & Use Cases

  • Three-pillar observability: metrics, logs, and traces combined for end-to-end visibility.
  • OpenTelemetry + Prometheus + Grafana: instrumentation, collection, and visualization for cloud-native apps.
  • SLOs and runbooks: define service level objectives and automated incident response workflows.

Quick Start

Enable basic monitoring by configuring metrics, logs, and traces collection for your service and start a Grafana dashboard.

Frequently Asked Questions about monitoring-observability

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

FAQPage Schema
How do I set up OpenTelemetry instrumentation for cloud-native application monitoring?

OpenTelemetry instrumentation enables cloud-native application monitoring by collecting metrics, logs, and traces into a unified visibility layer. It integrates with Prometheus for metric collection and Grafana for real-time dashboard visualization and incident response.

What is the best way to combine metrics, logs, and distributed tracing for end-to-end observability?

The best way to achieve end-to-end observability is combining metrics, logs, and distributed traces as three unified pillars. This approach integrates OpenTelemetry, Prometheus, and Grafana to detect and debug production incidents faster across multi-service architectures.

How do I define SLOs and create automated runbooks for incident response?

Defining SLOs and automated runbooks establishes service level objectives and triggers automated incident response workflows. This enables real-time SLA tracking and performance optimization by formalizing reliability thresholds and remediation steps within your monitoring stack.

Can I use Prometheus and Grafana dashboards for real-time SLA tracking in multi-service architectures?

Prometheus and Grafana dashboards support real-time SLA tracking in multi-service architectures by collecting and visualizing metrics. They enable incident detection and performance optimization across cloud-native stacks through unified visibility and alerting.

Why do I need distributed tracing alongside metrics and logs for production observability?

Distributed tracing is required for production observability because it tracks requests across multi-service architectures, pinpointing latency bottlenecks that metrics and logs alone cannot reveal. Combined, they form a three-pillar visibility layer to debug incidents faster.

What are the limitations of monitoring without unified metrics, logs, and traces in cloud-native stacks?

Monitoring without unified metrics, logs, and traces in cloud-native stacks limits visibility into multi-service request flows, slowing incident response. Fragmented data prevents automated runbooks from correlating root causes across distributed services for effective SLA tracking.