Package Details: grafana-alloy 1.11.0-1

Git Clone URL: https://aur.archlinux.org/grafana-alloy.git (read-only, click to copy)
Package Base: grafana-alloy
Description: OpenTelemetry Collector distribution with programmable pipelines
Upstream URL: https://grafana.com/oss/alloy-opentelemetry-collector/
Licenses: Apache-2.0
Submitter: bschnei
Maintainer: bschnei
Last Packager: bschnei
Votes: 5
Popularity: 0.004684
First Submitted: 2024-05-07 21:25 (UTC)
Last Updated: 2025-09-30 17:37 (UTC)

Latest Comments

1 2 Next › Last »

bschnei commented on 2025-09-18 21:01 (UTC)

Hi @hexchain, thanks! As I indicated in my response to @bone below, it would be great if this were made clearer in upstream documentation. Their documentation does already make a distinction between which build-time dependencies are needed only in specific cases[0]. They may have other reasons for wanting it to always be installed even if it is not currently used by the "default" build instructions. If you can either confirm with upstream that it is intended to only be an optional dependency, or, even better, make their documentation clearer, I'd be happy to make the change. Thanks!

[0] https://github.com/grafana/alloy/blob/v1.8.1/docs/developer/contributing.md#compile-on-linux

hexchain commented on 2025-09-18 14:13 (UTC)

Building Alloy using the system-wide Go toolchain should not (and does not) require Docker. The Makefile uses Docker when invoked with USE_CONTAINER=1, or when building an image, neither of which is the case here.

bschnei commented on 2025-04-10 18:51 (UTC) (edited on 2025-04-10 18:52 (UTC) by bschnei)

Hi @bone, thanks for your note! I can confirm v1.8.1 appears to build without it on x86_64, but upstream documentation[0] explicitly lists docker as a build-time dependency. I do not know their reasoning, but unless/until they remove it from their guide (or clarify if it is architecture/OS specific), I'm inclined to keep it to avoid breaking some case I cannot test (e.g. aarch64). In other words, if you determine the issue is with the upstream contributor guide, I'd prefer that gets fixed first so that all distributions might benefit.

[0] https://github.com/grafana/alloy/blob/v1.8.1/docs/developer/contributing.md

bone commented on 2025-04-10 09:01 (UTC)

This package builds just fine without the docker make dependency. Would you mind removing it from the build dependencies?

bschnei commented on 2024-12-22 18:25 (UTC)

@TheTaktik added in 1.5.1-2

TheTaktik commented on 2024-12-22 14:08 (UTC)

Consider setting GO_TAGS=promtail_journal_enabled for the make command to allow use of loki.source.journal.

bschnei commented on 2024-10-23 03:05 (UTC)

Thanks for the feedback! I'll incorporate at next update.

hexchain commented on 2024-10-22 16:30 (UTC)

Please add a backup line so that modified config files are not overridden on an upgrade, e.g.:

backup=(etc/default/grafana-alloy etc/grafana-alloy/config.alloy)

chaoslama commented on 2024-09-25 18:34 (UTC)

Wit the upgrade to alloy 1.4.0 the issue with the go-version is fixed, the package can be built with the current version of go now.

bschnei commented on 2024-08-31 20:09 (UTC) (edited on 2024-09-25 16:32 (UTC) by bschnei)

Hi @kode54, per my previous comment, v1.3.1 must be built with go 1.22.5. Go is not a dependency in order to run this program. This means users can either 1) stick with v1.3.0, 2) ask the maintainer of https://aur.archlinux.org/packages/grafana-alloy-bin to bring their package up-to-date, 3) build the package with the required version of go and then upgrade it after the package has built successfully, or 4) download the binary from upstream and install/package it manually. Given the number of workarounds, and the fact that go is only needed for compilation, I figured it made sense for the AUR to reflect the current state of upstream so users would be aware and +1 the issue if they are affected. Cheers!

1 2 Next › Last »