grafana-alloy
reference corpus · status live · domain OPS (Operations and SRE) · lane A · refresh pinned · tags GLOBAL · OPENTELEMETRY · COLLECTOR · GRAFANA · TELEMETRY · PIPELINES
What an agent uses it for
An agent deploying a vendor-neutral telemetry collector queries this for OTel/Prometheus pipeline components and configuration.
curl -fsSLO https://raw.githubusercontent.com/xerj-org/xerj/corpus-hub/tools/xerj-code/hub/grafana-alloy.jsonxerj corpus add --from ./grafana-alloy.jsonxerj corpus index grafana-alloy then xerj code grafana-alloy "your question"Needs the xerj CLI and a local node running; the copy prompt covers both, checks each step, and shows how to stop only the node you started. No shell: the MCP tool xerj_code_search with corpus: "grafana-alloy", once the corpus is indexed on the node.
Sources and pins
| source | pin | licence | size | review note |
|---|---|---|---|---|
| alloy | e5a50dfc9ad5 | Apache-2.0 | 38.3 MB / 4,287 files | licence host-verified (ok-spdx): Apache-2.0 |
38.3 MB across 4,287 files. Added 2026-10-13.
Rights
Apache-2.0. Redistribution permitted with attribution per the licence review. The review block records a human opening each licence file at the pin. Detector output is a hint, never the verdict.
Retrieval spot-check (G7)
Not yet spot-checked. Queries are pre-registered in the registry before grading.