Repository navigation
fix(promtail): disable Alloy usage-report telemetry - #1230
Merged
Merged
Conversation
Grafana Alloy (running under the legacy promtail.service unit) phones home anonymous usage stats to stats.grafana.org every ~4h. On offline/air-gapped clusters this call times out, spamming the journal with retry/failure noise. Pass --disable-reporting explicitly on the podman run command instead of relying on the image's default CMD, which stops the beacon without affecting the Loki log-shipping path. Assisted-by: Claude Code:claude-sonnet-5
DavidePrincipi
approved these changes
Jul 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Grafana Alloy (running under the legacy
promtail.serviceunit) sendsanonymous usage stats to
stats.grafana.orgevery ~4h. On offline /air-gapped clusters this call times out and spams the journal with
retry/failure noise.
Passes
--disable-reportingexplicitly on thepodman runcommand(instead of relying on the image's default CMD) to stop the beacon.
The internal Loki log-shipping path is unaffected.
Related issue
NethServer/dev#8088
How to test
promtail.serviceunit.systemctl daemon-reload && systemctl restart promtailpodman inspect promtail --format '{{json .Args}}'— confirm--disable-reportingis present.journalctl -u promtail -f— confirm no"reporting Alloy stats"/"usage report"lines appear (previously fired every ~4h).loki.write.defaultnode evaluates without error at startup;logcliquery returns fresh entries).Validated live on
rl1.leader.default.gs.nethserver.net.