How to disable telemetry in config file?

[deadnews]

#1777

This is release v0.25.0 of the Grafana Agent.
* As of this release, the Grafana Agent will send anonymous, but uniquely-identifiable information around enabled feature flags to stats.grafana.org. Statistics help us better understand how Grafana Agent is used. This helps us prioritize features and documentation. If you would like to disable the reporting, Grafana Agent provides the flag -disable-reporting
to stop the reporting.

How to disable telemetry via --config.file, in /etc/grafana-agent/grafana-agent.yml?

[rfratto]

Hi, there is currently no way to disable reporting in the config file and it must be done via the -disable-reporting command line flag mentioned above.

[mvtab]

I'll just drop this here for now

https://github.com/cilium/cilium/security/advisories/GHSA-mxv3-27mh-wcfj
cilium/cilium@ceed392

[ocontant]

Your link return a 404, maybe the url is incomplete?

New discussion started in Tempo repo: grafana/tempo#5001

[Sommerwiesel]

@ocontant Good luck with that (and I mean that). I already tried to convince them to change this practise, here: grafana/alloy#317

[ocontant]

Thanks for the reference https://github.com/Sommerwiesel

I read the topic and Grafana is wrong all the way. Anonymized data is never anonymous when aggregated, and this narrative is just the same argument used by the Advertiser to defend an unethical and immoral position.

From the moment it is enabled by default this is straight malicious and goes against Nettiquette that existed before mass-surveillance.

There is just no justification whatsoever to collect data without explicit authorization of users, and any attempt to hide it or obfuscate it, and it is automatic obfuscation when you don't provide a splash screen to warn the user that their data is being sent out.

For me, this is just a reason to fork Grafana and respin it under another name. Sad, but if founder and developers are acting malevolently, this is what will happen in the end. And the only reason, this hasn't happened yet, it's because barely anyone knows about it, as it is obfuscated well enough.

If the only reference is the last part of a documentation page, you can be sure no one ever read it. No one read documentation end to end in details. We scan and surf for what we are looking for.

There is no reference in the yaml config file, which would be the ONLY place where anyone deploying Grafana is very likely to check and see. SystemD config file, no lambda user ever check there. If you are not a savvy Linux administrator, you will not even know it exist.

In my honest opinion, the whole argument is bullshit and dishonest.

[ocontant]

I'm opening an issue on the grafana/grafana repo, seems to me it seems the right place to raise this properly, as grafana/grafana is logically the central focal point.

[ocontant]

I opened an issue on grafana/grafana : grafana/grafana#104077

Feel free to bring your support and feedback!