NethServer Version: 8
Just want to know if it’s anyone else. Started about 22 hours ago. 2 nodes behind one gateway. Don’t see evidence of blocks.
2026-04-13T10:33:57-07:00 [1::promtail] ts=2026-04-13T17:33:57.015680552Z level=info msg=“failed to send usage report” retries=0 err=“Post “https://stats.grafana.org/alloy-usage-report\”: context deadline exceeded (Client.Timeout exceeded while awaiting headers)”
Hi Fasttech, sorry for the late reply. Have you already solved this?
I think you have a point: over time, we’re seeing many similar threads about stats.grafana.org:
https://community.nethserver.org/search?q=stats.grafana.org%20order%3Alatest
We should probably choose one of the following approaches:
stats.grafana.org as a system requirement: https://docs.nethserver.org/projects/ns8/en/latest/system_requirements.html#external-network-connectivityWe should either disable it or allow it to be turned off by the admin.
It should not be a system requirement.
I had disabled metrics, no change, I applied some updates and rebooted, no change, continued connections attempts. I was going to start researching how to completely kill the process permanently but it’s not a priority so I hadn’t gotten to it yet. I found the block, a Google subnet I had blocked incoming because of obnoxious, excessive probing and pausing that rule stops the fail logging and dns log filling.
Disabling the reporting seems still working:
IMHO, we should do nothing on the NethServer module.
Stats are useful for an Open Source project and that’ts the only way we are supporting Grafana.
Also, if you think Grafana as an issue for with sending stats, I’d just report the problem upstream.
Those log lines are harmless and probably depend on a network issue (IP / hostname banned?) or
temporary maintance of the remote server.