monitoring-observability

Name: monitoring-observability
Availability: InStock
Author: shakudo

Map SLIs to Four Golden Signals and identify monitoring coverage gaps.

Updated Feb 14, 2026

Search Tags:#monitoring #logging #metrics #observability #tracing #alerts #slo

Ready to run

npx skills add https://github.com/Shakudo-io/opencode-skills --skill monitoring-observability-shakudo-io

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: monitoring-observability
Source: https://github.com/Shakudo-io/opencode-skills/tree/main/monitoring-observability
Command: npx skills add https://github.com/Shakudo-io/opencode-skills --skill monitoring-observability-shakudo-io

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Monitoring and observability are essential for reliable software systems, enabling proactive detection, troubleshooting, and optimization across metrics, logs, and traces.

Core Features & Use Cases

Four Golden Signals based metrics design
OpenTelemetry instrumentation guidance and alerting patterns
Log aggregation, dashboarding, and SLO management
Cost optimization and tool comparison for open-source vs cloud observability

Quick Start

Enable end-to-end observability by instrumenting services, collecting metrics, logs, and traces, and wiring dashboards and alerts.

Frequently Asked Questions about monitoring-observability

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

FAQPage Schema

How do I map SLIs to the Four Golden Signals across my services?▼

To map SLIs to the Four Golden Signals, you identify gaps in monitoring coverage and align latency, traffic, errors, and saturation metrics across your specific services and environments to generate tailored dashboards and alerts.

What's the best way to design log aggregation and tracing strategies for end-to-end observability?▼

Designing log aggregation and tracing strategies involves using OpenTelemetry instrumentation guidance to collect metrics, logs, and traces, enabling proactive detection and troubleshooting across your software stacks.

How do I generate tailored dashboards, alerts, and runbooks for my environments?▼

You generate tailored dashboards, alerts, and runbooks by providing concrete inputs such as your specific services, environments, and thresholds to map out metric design and alerting patterns.

How does SLO management work with cost optimization for cloud observability?▼

SLO management with cost optimization works by comparing open-source versus cloud observability tools, allowing you to balance reliable alerting and dashboarding against the operational costs of collecting metrics and logs.

Do I need OpenTelemetry instrumentation to implement end-to-end observability?▼

You need OpenTelemetry instrumentation to implement end-to-end observability because it provides the necessary guidance to wire metrics, logs, and traces together for proactive detection and troubleshooting.

What are the limitations of using open-source vs cloud observability tools for alerting?▼

Limitations of open-source versus cloud observability tools involve trade-offs in cost optimization, operational overhead for dashboarding, and the complexity of managing log aggregation and alerting patterns across environments.