install

Additional install commands

macOS

Homebrewverified · 100%

brew install grafana-alloy

local Homebrew formula metadata

Linux

Nixverified · 92%

nix profile install nixpkgs#grafana-alloy

nixpkgs package indexes · pkgs/by-name/gr/grafana-alloy/package.nix · source: api.github.com

Arch Linux pacmanverified · 92%

sudo pacman -S grafana-alloy

Arch Linux sync databases · grafana-alloy · source: geo.mirror.pkgbuild.com

Windows

Chocolateyverified · 92%

choco install grafana-alloy

Chocolatey community package catalog · grafana-alloy · source: community.chocolatey.org

overview

Package summary

OpenTelemetry Collector distribution with programmable pipelines

Project links

Commands and aliases

No executable aliases were found in the local package database.

history

Project history and usage

Grafana Alloy is Grafana Labs' open source distribution of the OpenTelemetry Collector, designed to run telemetry pipelines for metrics, logs, traces, and profiles while retaining first-class Prometheus-oriented pipeline support.

Project history

Alloy grew out of Grafana Agent and Grafana Agent Flow. Grafana Labs described Grafana Agent as a broad OSS telemetry agent introduced in 2020 for Prometheus-era collection problems, then positioned Alloy in 2024 as the successor that uses Agent Flow concepts while aligning with the OpenTelemetry Collector.

The launch announcement emphasized compatibility with OTLP, OpenTelemetry Collector, and Prometheus Agent workflows. That made Alloy both a migration target for Grafana Agent users and a standalone collector for mixed observability environments.

Adoption history

Grafana Labs tied Alloy adoption to its recommendation that Grafana Agent users plan migrations before the Agent end-of-life date. Official migration documentation covers moving Agent Flow state directories and pipelines into Alloy layouts on Linux, macOS, Windows, and containers.

The package became important in Homebrew-style environments because it packages a production telemetry collector as a single serviceable CLI/daemon with documented platform-specific configuration paths.

How it is used

Operators use Alloy to receive, transform, scrape, relabel, and export telemetry. Common package-manager usage is installing the binary, editing config.alloy, and running Alloy as a long-lived service that forwards data to Grafana Cloud, an LGTM stack, or other compatible backends.

Why package nerds care

Alloy matters to package maintainers because it sits at the convergence point of Prometheus scraping, OpenTelemetry Collector components, service management, and cross-platform config conventions. It replaced several collector choices with one packaged executable for many Grafana observability setups.

Timeline

2020: Grafana Agent rolled out as Grafana Labs' OSS telemetry agent.
2024-04-09: Grafana Agent and Grafana Agent Operator entered long-term support in favor of Alloy.
2024-04-10: Grafana Labs announced Grafana Alloy as an OpenTelemetry Collector distribution with Prometheus pipelines.
2025-11-01: Grafana Agent was expected to reach end of life, making Alloy the migration target.

Related projects

Grafana Agent and Grafana Agent Flow are Alloy's direct predecessors.
OpenTelemetry Collector, Prometheus Agent, Grafana, Loki, Tempo, and Mimir are adjacent projects in the same collector and backend ecosystem.

Sources

security posture

Risk level: orange

formula declares a Homebrew service.

Risk classifier

orange risk · medium confidence · infrastructure

Why

formula declares a Homebrew service

Signals

metadata:service

Install behavior

No Homebrew post-install hook is recorded in formula metadata.
Formula metadata declares a service or daemon block.
Homebrew bottle metadata is available for 6 platform targets.
Build metadata lists 2 build dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Linux: /etc/alloy/config.alloy
macOS: $(brew --prefix)/etc/alloy/config.alloy
Windows: %ProgramFiles%\GrafanaLabs\Alloy\config.alloy

executables

Installed executables

Command	Kind	Exposure	Note
No executable data was present.

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-08

manager version1.17.1

manager updated2026-06-30

local dataok

upstreamcurrent

latest detectedv1.17.1

https://github.com/grafana/alloy

okNo freshness warnings were generated.

install metadata

Package metadata

Package key	brew:grafana-alloy
Version	1.17.1
Package manager	Homebrew
Package manager page	https://formulae.brew.sh/formula/grafana-alloy
Homepage	https://grafana.com/oss/alloy-opentelemetry-collector/
Repository	https://github.com/grafana/alloy
Upstream docs	https://grafana.com/docs/alloy/latest
License	Apache-2.0
Source archive	https://github.com/grafana/alloy/archive/refs/tags/v1.17.1.tar.gz
Last updated	2026-06-30T00:08:53Z
Pulse	updated
Build dependencies	go, node
Bottle	available (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-install	not defined
Service	declared
Caveats	Alloy configuration directory is $HOMEBREW_PREFIX/etc/grafana-alloy

registry facts

Source database details

Source Database	Homebrew formula API
Tap	homebrew/core
Full Name	grafana-alloy
Version Scheme	0
Revision	0
Head Version	HEAD
Conflicts With	alloy-analyzer
Bottle Stable Root URL	https://ghcr.io/v2/homebrew/core
Deprecated	no
Disabled	no
Keg Only	no
URL Keys	head stable

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

Nix95%

grafana-alloy

nix profile install nixpkgs#grafana-alloy

normalized package name match
Matched by: Grafana Alloy

nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/gr/grafana-alloy/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

pacman95%

grafana-alloy 1.13.2-1

OpenTelemetry Collector distribution with programmable pipelines

https://grafana.com/oss/alloy-opentelemetry-collector/

sudo pacman -S grafana-alloy

License: Apache-2.0
Architecture: x86_64
1 dependencies
normalized package name match
Matched by: Grafana Alloy

Arch Linux sync databases · geo.mirror.pkgbuild.com · Arch Linux sync databases: grafana-alloy from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz

Chocolatey95%

grafana-alloy

choco install grafana-alloy

normalized package name match
Matched by: Grafana Alloy

Chocolatey community package catalog · community.chocolatey.org · Chocolatey community package catalog: grafana-alloy from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='11','gpg4win-vanilla'

package graph

Links come from deterministic package relationships, av.db category and tag curation, ecosystem matches, and package hub membership.

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Combined YAML source

View the package source record on GitHub.

combined/grafana-alloy.yml

Used sources

Geiger risk classifier
Nucleus package database
av.db category and tag curation
cross-ecosystem install command graph
curated configuration and credential file locations
curated package history
external package-manager database matches
package relationship graph
package version freshness
package-page enrichment

Install grafana-alloy with Homebrew, chocolatey, Nix, pacman