OBSERVABILITY / Grafana Labs
Grafana Alloy
Write a Grafana Alloy pipeline, validate it before running it, and treat an unhealthy component on the local UI as the failure.
“OpenTelemetry-compatible collector — one binary for metrics + logs + traces + profiles.”
01 / THE REASONING
Why this made the selection.
- The file runs alloy fmt and alloy validate before alloy run, then reads the local component API for any health state other than healthy.
- The OTLP example listens on 0.0.0.0, and the remote-write password is read from an environment variable rather than written as a literal.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- skills/grafana-core/alloy/SKILL.md
- LICENSE at the same commit
- skills/grafana-core/alloy/references/config-syntax.md
- vercel-labs/skills@48dc9e8eb8aa19040e91cb90ba0b642c9cbad57e:README.md
- LICENSE
Our findings
- The Apache appendix at this commit says Copyright 2026 Grafana Labs.
- A missing span is traced to refused or failed exporter counters, not to a guessed network fault.
- The configuration-syntax reference explains component arguments versus exports and re-evaluation when referenced values change, including secret-file wiring.
- Log shipping tells the reader to confirm the file exists and is readable by the alloy user before blaming the pipeline.
- The OTLP receiver example binds its gRPC and HTTP listeners to all IPv4 interfaces and forwards traces to the Tempo exporter; troubleshooting distinguishes refused receiver spans from exporter failures.
Not established by this review
- Alloy was not installed or run.
- The component catalogue and collection patterns were not read.
- Not executed: it was not installed or run.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Add a skill to your workflow.
DOCUMENTED COMMAND
npx skills add grafana/skills/skills/grafana-core/alloy Run in your terminal to choose your AI tools, project or global scope, and installation method. This short command follows the current upstream version; the review covers the revision shown above.
Optional: install the reviewed revision
Keeps the original source and installer version where recorded, while leaving your AI tools and installation scope for you to choose.
npx skills add https://github.com/grafana/skills/tree/1ccacf29049fde66637fe01ab93a83a772da323b/skills/grafana-core/alloy - The command pins only the Alloy skill at the reviewed commit. The installer was not executed.
- Do not point the installer at a parent directory if you only want this skill.
Before you start
- Node.js and npm
- An Alloy binary and a telemetry endpoint you are allowed to send to, if you follow the workflow
04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
- Skill definition ↗Checked
https://github.com/grafana/skills/blob/1ccacf29049fde66637fe01ab93a83a772da323b/skills/grafana-core/alloy/SKILL.md
Supports: summary, whySelected
- Apache-2.0 licence ↗Checked
https://github.com/grafana/skills/blob/1ccacf29049fde66637fe01ab93a83a772da323b/LICENSE
Supports: Redistribution terms, Copyright 2026 Grafana Labs
https://github.com/grafana/skills/blob/1ccacf29049fde66637fe01ab93a83a772da323b/skills/grafana-core/alloy/references/config-syntax.md
Supports: review, limitations, access, install
https://raw.githubusercontent.com/grafana/skills/1ccacf29049fde66637fe01ab93a83a772da323b/skills/grafana-core/alloy/SKILL.md
Supports: review.findings, bestFor, limitations