monitoring-observability

Design and operate observability stacks with OpenTelemetry, Prometheus, Loki, and Tempo.

1|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/allthingslinux/atl.services --skill monitoring-observability-allthingslinux
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monitoring-observability
Source: https://github.com/allthingslinux/atl.services/tree/main/.agents/skills/monitoring-observability
Command: npx skills add https://github.com/allthingslinux/atl.services --skill monitoring-observability-allthingslinux

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, boto3, PyYAML, tabulate, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This skill helps teams design and operate robust observability stacks for modern services. It addresses the challenge of fragmented metrics, logs, and traces across distributed architectures, aiming to provide a unified view of service health.

Core Features & Use Cases

  • End-to-end design of metrics, logs, traces, dashboards, and SLO governance.
  • Automation templates and scripts to instrument applications, generate dashboards, and migrate from vendor-centric tools.
  • Use Case: A microservices platform can implement a unified observability stack (Prometheus, Grafana, Loki, Tempo) and migrate from vendor tools to an OSS-first approach.

Quick Start

  • Install and configure a basic OSS stack (Prometheus, Grafana, Loki, Tempo) using the provided scripts.
  • Run the analysis tools to audit metrics and alerts (python3 scripts/analyze_metrics.py) and generate dashboards.
  • Example: instrument a sample service with OpenTelemetry and export to Tempo.

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 a Prometheus, Grafana, Loki, and Tempo observability stack?

Set up a Prometheus, Grafana, Loki, and Tempo observability stack using provided automation scripts and templates. You install and configure the OSS stack, instrument services with OpenTelemetry, and export traces to Tempo for a unified service health view.

How do I migrate from vendor-centric observability tools to an OSS-first approach?

Migrate from vendor-centric observability tools to an OSS-first approach using provided migration workflows and templates. The process helps teams transition fragmented metrics, logs, and traces into a unified open-source stack without losing visibility.

What is the best way to audit metrics and alerts for cloud-native architectures?

Audit metrics and alerts for cloud-native architectures by running dedicated analysis scripts like analyze_metrics.py. This evaluates your existing observability setup and helps generate optimized dashboards for distributed services.

Can I manage SLO governance and OpenTelemetry instrumentation across microservices?

Manage SLO governance and OpenTelemetry instrumentation across microservices using end-to-end design capabilities. It covers SLO management and provides templates to instrument applications for unified metrics, logs, and traces.

Does this observability stack require OpenTelemetry for distributed tracing?

Yes, this observability stack requires OpenTelemetry for distributed tracing. It uses OpenTelemetry instrumentation to collect traces and export them to Tempo, ensuring unified visibility across distributed architectures.