god-observability

Guide DevOps engineers in setting up observability with OpenTelemetry, Prometheus, Grafana, and ELK Stack.

1|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/ArdurAI/god-skill-suite --skill god-observability-ardurai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: god-observability
Source: https://github.com/ArdurAI/god-skill-suite/tree/main/skills/god-observability
Command: npx skills add https://github.com/ArdurAI/god-skill-suite --skill god-observability-ardurai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of observability in complex software systems, providing a comprehensive approach to monitoring, logging, and tracing.

Core Features & Use Cases

  • Comprehensive Observability: Covers metrics, logs, and traces, including OpenTelemetry, Prometheus, Grafana, ELK Stack, and more.
  • In-depth Engineering Practices: Includes best practices for observability engineering, including anti-hallucination rules and SLO-based alerting.
  • Use Case: For a DevOps engineer tasked with setting up a monitoring system for a microservices architecture, this Skill offers guidelines and tools to achieve a full observability setup.

Quick Start

Load the god-observability skill to learn best practices for observability engineering.

Frequently Asked Questions about god-observability

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

FAQPage Schema
How do I set up distributed tracing and metrics collection for a microservices architecture?

Observability in complex software systems requires integrating metrics, logs, and traces to monitor internal states effectively. This Skill provides engineering practices to implement comprehensive observability, ensuring you can detect, debug, and resolve issues across distributed microservices architectures.

Does this observability engineering approach work with the ELK Stack and OpenSearch?

Yes, this observability approach explicitly supports the ELK Stack and OpenSearch for log management. It provides best practices for integrating these platforms alongside Prometheus and Grafana to achieve full system visibility.

What is the best way to implement SLO-based alerting with Prometheus and Grafana?

The best way to implement SLO-based alerting is by applying observability engineering best practices to configure Prometheus metrics and Grafana dashboards. This Skill outlines specific guidelines to establish reliable SLO alerting without overwhelming operators with noise.

Do I need prior knowledge of OpenTelemetry to use these observability guidelines?

Yes, you need prior knowledge of monitoring, logging, and tracing principles to effectively apply these observability guidelines. The Skill is designed for DevOps engineers and assumes familiarity with OpenTelemetry, Prometheus, and the ELK Stack.

How do I prevent alert fatigue when configuring comprehensive observability metrics?

Preventing alert fatigue requires implementing SLO-based alerting practices derived from robust observability engineering. This Skill includes anti-hallucination rules and best practices to ensure your metrics collection generates actionable, high-signal alerts rather than noise.