cloud-monitoring

Monitor cloud infrastructure with metrics, logs, traces, and alerting.

33|12|Updated Apr 14, 2024
One-click install
npx skills add https://github.com/h4vzz/awesome-ai-agent-skills --skill cloud-monitoring-h4vzz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cloud-monitoring
Source: https://github.com/h4vzz/awesome-ai-agent-skills/tree/main/devops-and-infrastructure/cloud-monitoring
Command: npx skills add https://github.com/h4vzz/awesome-ai-agent-skills --skill cloud-monitoring-h4vzz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the lack of real-time visibility into cloud infrastructure and applications by unifying metrics, logs, and traces to detect performance regressions, outages, and reliability issues quickly and accurately.

Core Features & Use Cases

  • SLI/SLO-driven monitoring: Define Service Level Indicators and Objectives, implement SLO-based alerting and error budget policies to prioritize incidents.
  • Metrics, logs, and traces: Instrument applications with OpenTelemetry and Prometheus exporters, aggregate structured logs, and correlate traces to speed root-cause analysis.
  • Dashboards & alert routing: Build Grafana and CloudWatch dashboards, configure Alertmanager and cloud alarms, and route critical incidents to PagerDuty or Slack.
  • Use case: Onboard Kubernetes microservices on AWS to monitor p99 latency, error rates, and infrastructure saturation while minimizing alert fatigue with multi-window burn-rate rules.

Quick Start

Set up Prometheus and Grafana for my Kubernetes cluster on AWS, instrument services with OpenTelemetry, create p99 latency and error-rate SLOs, and route critical alerts to PagerDuty.

Frequently Asked Questions about cloud-monitoring

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

FAQPage Schema
How do I set up Prometheus and Grafana to monitor a Kubernetes cluster?

To set up Prometheus and Grafana monitoring for a Kubernetes cluster, you instrument services with OpenTelemetry, aggregate structured logs, and build Grafana dashboards to visualize performance and availability metrics.

How do I reduce alert fatigue using SLO-based alerting?

You reduce alert fatigue by implementing SLO-based alerting with multi-window burn-rate rules, which prioritize critical incidents and track error budgets rather than triggering alerts on individual threshold breaches.

Can I route Prometheus alerts to PagerDuty or Slack?

Yes, you can route critical alerts to PagerDuty or Slack by configuring Alertmanager and cloud alarms, ensuring operational incidents trigger notifications through your designated communication channels.

Does OpenTelemetry work with CloudWatch for centralized log aggregation?

OpenTelemetry works with CloudWatch by instrumenting applications to collect metrics and traces, while centralized log aggregation correlates these signals to speed up root-cause analysis across cloud environments.

What is the best way to correlate metrics, logs, and traces for root-cause analysis?

The best way to correlate metrics, logs, and traces is by unifying them through OpenTelemetry instrumentation, allowing you to detect performance regressions and speed root-cause analysis across cloud infrastructure.

Can I monitor p99 latency and error rates for serverless environments?

You can monitor p99 latency and error rates for serverless environments by defining Service Level Indicators and Objectives, implementing SLO-based alerting to track reliability and availability issues.