Skip to main content
ZICQ

Skills ZICQ category:DevOps & Cloud infrastructure

Infrastructure

Ship Kubernetes, host, container, and cloud-provider telemetry into Grafana Cloud — `k8s-monitoring` Helm chart for K8s clusters (metrics + logs + traces + events + cost), Alloy `prometheus.exporter.unix` for Linux hosts, cAdvisor + Docker discovery for containers, and CloudWatch / Azure Monitor / Google Cloud Monitoring datasource setup. Use when onboarding a new cluster or VM fleet to Grafana Cloud, picking the right Helm values for K8s scraping, wiring kube-state-metrics + node-exporter + cAdvisor, alerting on `PodCrashLooping` / node memory / PVC capacity, or pulling AWS / Azure / GCP cloud metrics — even when the user says "monitor my cluster", "send K8s metrics to Grafana", "scrape EC2 metrics", "cluster pod logs", or "install the monitoring helm chart" without naming `k8s-monitoring

4657 installs

Official URL:skills.sh

What this skill does

Intro in this page language first. The official description stays in its original wording; we do not rewrite SKILL.md.

What it does

Ship Kubernetes, host, container, and cloud-provider telemetry into Grafana Cloud — `k8s-monitoring` Helm chart for K8s clusters (metrics + logs + traces + events + cost), Alloy `prometheus.exporter.unix` for Linux hosts, cAdvisor + Docker discovery for containers, and CloudWatch / Azure Monitor / Google Cloud Monitoring datasource setup

When to use it

onboarding a new cluster or VM fleet to Grafana Cloud, picking the right Helm values for K8s scraping, wiring kube-state-metrics + node-exporter + cAdvisor, alerting on `PodCrashLooping` / node memory / PVC capacity, or pulling AWS / Azure / GCP cloud metrics — even when the user

How agents load it

Per Agent Skills progressive disclosure: name and description load at startup (~100 tokens); the full SKILL.md body loads when the skill activates; scripts/, references/, and assets/ load only as needed. This file's sections: Grafana Cloud Infrastructure Monitoring; Prerequisites; Common Workflows; 1. Onboard a Kubernetes cluster (k8s-monitoring chart); 1. Create the namespace + secret; 2. Install — values.yaml in references/k8s-monitoring-values.md. It includes spec-recommended sections: step-by-step instructions.

File analysis

File analysis: besides SKILL.md, the body references references/k8s-monitoring-values.md, references/clouds-and-hosts.md. Those resources load on demand.

Official description (original)

Ship Kubernetes, host, container, and cloud-provider telemetry into Grafana Cloud — `k8s-monitoring` Helm chart for K8s clusters (metrics + logs + traces + events + cost), Alloy `prometheus.exporter.unix` for Linux hosts, cAdvisor + Docker discovery for containers, and CloudWatch / Azure Monitor / Google Cloud Monitoring datasource setup. Use when onboarding a new cluster or VM fleet to Grafana Cloud, picking the right Helm values for K8s scraping, wiring kube-state-metrics + node-exporter + cAdvisor, alerting on `PodCrashLooping` / node memory / PVC capacity, or pulling AWS / Azure / GCP cloud metrics — even when the user says "monitor my cluster", "send K8s metrics to Grafana", "scrape EC2 metrics", "cluster pod logs", or "install the monitoring helm chart" without naming `k8s-monitoring` or Alloy.

Grafana Cloud Infrastructure MonitoringPrerequisitesCommon Workflows1. Onboard a Kubernetes cluster (k8s-monitoring chart)1. Create the namespace + secret2. Install — values.yaml in references/k8s-monitoring-values.md3. Verify every pod is RunningExpect alloy-*, kube-state-metrics-*, node-exporter-*, etc. all Ready.4. Verify no error logs in the metrics/logs/traces Alloys5. Verify telemetry landed in Grafana CloudPromQL on the metrics datasource (should be > 0):sum(up{cluster="production-us-east"})

· License:Apache-2.0

Source category:skills.sh agent-skill

SKILL.md & Agent activation

Official spec ↗
name
infrastructure
description
Ship Kubernetes, host, container, and cloud-provider telemetry into Grafana Cloud — `k8s-monitoring` Helm chart for K8s clusters (metrics + logs + traces + events + cost), Alloy `prometheus.exporter.unix` for Linux hosts, cAdvisor + Docker discovery for containers, and CloudWatch / Azure Monitor / Google Cloud Monitoring datasource setup. Use when onboarding a new cluster or VM fleet to Grafana Cloud, picking the right Helm values for K8s scraping, wiring kube-state-metrics + node-exporter + cAdvisor, alerting on `PodCrashLooping` / node memory / PVC capacity, or pulling AWS / Azure / GCP cloud metrics — even when the user says "monitor my cluster", "send K8s metrics to Grafana", "scrape EC2 metrics", "cluster pod logs", or "install the monitoring helm chart" without naming `k8s-monitoring` or Alloy.
License
Apache-2.0
  1. DiscoverThe client exposes names and descriptions to the agent.
  2. ActivateYour request or the task context selects the skill and loads its instructions.
  3. Load resourcesReferenced scripts, documentation and assets are used when needed.
Files referenced by the instructions · 2
  • references/k8s-monitoring-values.md
  • references/clouds-and-hosts.md

These paths are extracted from the text. Check the upstream package to verify the files exist.

Invocation syntax and available tools depend on your Agent client. Client integration guide ↗

Install this skill

Skills CLI ↗

Choose the target agent and installation scope, keep referenced package files, then verify the skill appears in the client's catalog.

This skill references supporting files. Retrieve the complete directory from the source; copying SKILL.md alone may leave missing dependencies.

Ask your Agent to install

Copy these instructions to a compatible agent and confirm the target directory matches your client.

Install the agent skill "infrastructure" into my project. The full SKILL.md and official description are at https://zicq.com/en/skills/skl-194fa957e5056f1d-Infrastructure.html
Save it as .cursor/skills/infrastructure/SKILL.md or .claude/skills/infrastructure/SKILL.md and keep the frontmatter name and description exactly as-is.
This skill also ships scripts/, references/, or assets/ — fetch the whole folder from https://github.com/grafana/skills instead of creating only a SKILL.md.

Full package on GitHub ↗

Install from the terminal · Skills CLI

Requires Node.js and npx. First inspect the repository's skill list to confirm the name.

npx skills add 'https://github.com/grafana/skills' --list

npx skills add 'https://github.com/grafana/skills' --skill 'infrastructure'

The CLI lets you choose the agent interactively. The default scope is the project; use -g for user scope. Confirm package availability with the discovery command, then use npx skills list to inspect installed skills.

Readable layout
--- name: infrastructure license: Apache-2.0 description: Ship Kubernetes, host, container, and cloud-provider telemetry into Grafana Cloud — `k8s-monitoring` Helm chart for K8s clusters (metrics + logs + traces + events + cost), Alloy `prometheus.exporter.unix` for Linux hosts, cAdvisor + Docker discovery for containers, and CloudWatch / Azure Monitor / Google Cloud Monitoring datasource setup. Use when onboarding a new cluster or VM fleet to Grafana Cloud, picking the right Helm values for K8s scraping, wiring kube-state-metrics + node-exporter + cAdvisor, alerting on `PodCrashLooping` / node memory / PVC capacity, or pulling AWS / Azure / GCP cloud metrics — even when the user says "monitor my cluster", "send K8s metrics to Grafana", "scrape EC2 metrics", "cluster pod logs", or "install the monitoring helm chart" without naming `k8s-monitoring` or Alloy. --- # Grafana Cloud Infrastructure Monitoring > **Docs**: https://grafana.com/docs/grafana-cloud/monitor-infrastructure/ K8s + host + container + cloud-provider telemetry, mostly via the `grafana/k8s-monitoring` Helm chart or Alloy. ## Prerequisites - Grafana Cloud stack with Prometheus / Loki / Tempo endpoints + API key (`metrics:write`, `logs:write`, `traces:write`) - For Kubernetes: a cluster + `helm` 3.x + `kubectl` context pointing at it - For hosts / Docker: Alloy installed on the node ## Common Workflows ### 1. Onboard a Kubernetes cluster (k8s-monitoring chart) ```bash # 1. Create the namespace + secret kubectl create namespace monitoring kubectl create secret generic grafana-cloud-secret \ -n monitoring --from-literal=api-key= # 2. Install — values.yaml in references/k8s-monitoring-values.md helm repo add grafana https://grafana.github.io/helm-charts && helm repo update helm install k8s-monitoring grafana/k8s-monitoring \ --version 4.1.4 -n monitoring -f values.yaml # 3. Verify every pod is Running kubectl get pods -n monitoring # Expect alloy-*, kube-state-metrics-*, node-exporter-*, etc. all Ready. # 4. Verify no error logs in the metrics/logs/traces Alloys kubectl -n monitoring logs deploy/k8s-monitoring-alloy-metrics --tail=50 | grep -iE 'error|level=err' || echo "clean" # 5. Verify telemetry landed in Grafana Cloud # PromQL on the metrics datasource (should be > 0): # sum(up{cluster="production-us-east"}) # LogQL on Loki: # sum(count_over_time({cluster="production-us-east"}[5m])) ``` Full `values.yaml`, key PromQL, dashboard IDs (15520, 1860, 14282…), and alert rules: [`references/k8s-monitoring-values.md`](references/k8s-monitoring-values.md). ### 2. Monitor a Linux host ```alloy # 1. /etc/alloy/config.alloy — see references/clouds-and-hosts.md for the full block prometheus.exporter.unix "host" { rootfs_path = "/" } prometheus.scrape "node" { targets = prometheus.exporter.unix.host.targets forward_to = [prometheus.remote_write.cloud.receiver] } ``` ```bash # 2. Reload Alloy and verify the unix exporter is up systemctl reload alloy curl -s http://localhost:12345/api/v0/web/components | jq '.[] | select(.id|contains("prometheus.exporter.unix"))' # 3. Verify in Grafana Cloud — open the "Node Exporter Full" dashboard (ID 1860) # and pick your host from the `instance` dropdown. ``` ### 3. Pull AWS / Azure / GCP metrics Provision the datasource (full YAML in [`references/clouds-and-hosts.md`](references/clouds-and-hosts.md)), then: ```bash # 1. After provisioning, restart Grafana to pick up the file # 2. Verify the datasource — Grafana → Connections → Data sources → "Test" # Expect "Successfully queried the CloudWatch metrics API" (or equivalent). # 3. Confirm a query — Explore → datasource → metric e.g. # CloudWatch namespace AWS/EC2 metric CPUUtilization, last 1h. ``` ## Troubleshooting - chart installed but no metrics in Cloud → check the `grafana-cloud-secret` `api-key` value; check Alloy logs for `401` - `kube-state-metrics` pod Pending → likely RBAC; reapply the chart's CRDs/CRBs - Node-exporter pod CrashLoopBackOff → typically `hostNetwork: true` collision with the host's :9100; change the port - CloudWatch "Access denied" → IAM role missing `cloudwatch:GetMetricData`, `cloudwatch:ListMetrics` ## Resources - [`grafana/k8s-monitoring` chart](https://github.com/grafana/k8s-monitoring-helm) - [Monitor Infrastructure docs](https://grafana.com/docs/grafana-cloud/monitor-infrastructure/) - [CloudWatch datasource](https://grafana.com/docs/grafana/latest/datasources/aws-cloudwatch/) - [Azure Monitor datasource](https://grafana.com/docs/grafana/latest/datasources/azure-monitor/) - [Google Cloud Monitoring datasource](https://grafana.com/docs/grafana/latest/datasources/google-cloud-monitoring/)

Related skills

DevOps & Cloud

Docker Essentials

Essential Docker commands and workflows for container management, image operations, and debugging.

DevOps & Cloud

Find Skills

Discover and install skills from the open agent skills ecosystem. Use when: (1) user asks "how do I do X" where X might have an existing ski…

DevOps & Cloud

Microsoft Foundry

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end. USE FOR: foundry, azd a…

DevOps & Cloud

Azure Deploy

Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT us…