monitoring

Instrument software systems with OpenTelemetry logs, metrics, and traces.

3|Updated May 28, 2026
One-click install
npx skills add https://github.com/mahg-es/araya --skill monitoring-mahg-es
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monitoring
Source: https://github.com/mahg-es/araya/tree/main/skills/monitoring
Command: npx skills add https://github.com/mahg-es/araya --skill monitoring-mahg-es

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design and implement observability — logs, metrics, traces, and alerts — that tell you what's happening in your system right now, what happened yesterday, and what will happen if nothing changes.

Core Features & Use Cases

  • Instrument services with metrics, logs, and traces using OpenTelemetry
  • Define SLOs and alerting policies to detect issues early
  • Build dashboards and provisioning for service health and performance
  • Use cases: production monitoring, troubleshooting, and capacity planning

Quick Start

Instrument your services with metrics, logs, and traces, then deploy a basic dashboard and alert to validate observability.

Frequently Asked Questions about monitoring

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

FAQPage Schema
How do I instrument services with logs, metrics, and traces using OpenTelemetry?

To instrument services with logs, metrics, and traces using OpenTelemetry, you deploy observability configurations that capture real-time system health, performance data, and bottlenecks across production architectures. This provides actionable visibility into outages and latency.

What is the best way to design observability for production services?

Designing observability for production services involves implementing logs, metrics, traces, and alerts to reveal real-time health and performance bottlenecks. This approach helps engineers diagnose outages, latency issues, and capacity problems effectively.

How do I set up SLOs and alerting policies to detect system issues early?

Setting up SLOs and alerting policies requires defining thresholds and provisioning dashboards that monitor service health. These alerting policies detect issues early, helping engineers troubleshoot and maintain system performance before outages escalate.

Can I use dashboards and alerts for capacity planning and troubleshooting?

Yes, dashboards and alerts support capacity planning and troubleshooting by visualizing real-time metrics and historical logs. Engineers use these observability tools to diagnose bottlenecks, analyze performance trends, and plan infrastructure capacity accurately.

Does observability instrumentation work across different software architectures?

Observability instrumentation applies to production services across various architectures, using OpenTelemetry to collect logs, metrics, and traces. This cross-architecture support helps diagnose outages and capacity problems regardless of underlying system design.