monitoring

Validate and troubleshoot K3s monitoring stack health with kubectl and helm.

1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/villadalmine/infra --skill monitoring-villadalmine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monitoring
Source: https://github.com/villadalmine/infra/tree/main/.agents/skills/monitoring
Command: npx skills add https://github.com/villadalmine/infra --skill monitoring-villadalmine

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires kubectl, helm, python3, and includes scripts (resource) components.

What problem does it solve?

This Skill helps you install, validate, and troubleshoot the full monitoring and observability stack for an ARM64 K3s cluster so you can quickly confirm that metrics, logs, traces, and alerting are working end to end.

Core Features & Use Cases

  • Stack validation: Check the health of Prometheus, Grafana, Alertmanager, Tempo, Loki, Alloy, and supporting services in the monitoring namespace.
  • Observability troubleshooting: Diagnose readiness issues, missing logs, failed traces, broken HTTP routes, and Helm upgrade problems with practical cluster checks.
  • Operational guidance: Verify routing, storage, datasources, and pipeline wiring for Gateway API, Loki multi-tenancy, Tempo metrics generation, and Alloy log collection.
  • Use case: Use this Skill when a Grafana dashboard is empty, Loki is not receiving logs, Tempo is crashing after an upgrade, or you need a reliable health report before and after a rollout.

Quick Start

Ask for a concise health check of the monitoring stack and summarize any failing pods, Helm releases, routes, or datasources.

Frequently Asked Questions about monitoring

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

FAQPage Schema
How do I troubleshoot a Grafana dashboard that is empty or missing data?

To troubleshoot an empty Grafana dashboard, validate the monitoring stack health. This Skill checks Prometheus, Tempo, and Loki datasources, pipeline wiring, and Helm release readiness to diagnose missing metrics or logs.

Why is Loki not receiving logs in my Kubernetes cluster?

Loki might not be receiving logs due to readiness issues or broken pipeline wiring. This Skill inspects namespace-aware cluster health, verifies Alloy log collection, and checks Loki multi-tenancy auth headers to resolve log ingestion failures.

How do I check the health of a Prometheus and Alertmanager monitoring stack?

Check the health of a Prometheus and Alertmanager stack by running python3-based health verification. This Skill validates pod readiness, Helm releases, and Gateway API routing to ensure metrics and alerting work end to end.

Do I need kubectl and helm to validate a K3s observability stack?

Yes, you need kubectl and helm to validate a K3s observability stack. This Skill requires these command-line tools alongside python3 to perform namespace-aware cluster inspection and health verification.

How do I fix Tempo crashes after a Helm upgrade on ARM64 K3s?

To fix Tempo crashes after a Helm upgrade on ARM64 K3s, diagnose readiness issues and storage configuration. This Skill checks Helm releases and validates Tempo metrics generation to restore distributed tracing functionality.