Robert Fratto

This wouldn't be relevant anymore if we merge the UI prototype, since that could just replace the Graphviz dependency.

Personally, I'm comfortable adding more usage information as long as we: * Continue to document what we collect * Continue to document how to disable collection clearly in an obvious...

Thinking about this more, just setting it to `1` probably wouldn't work, since if your graph updates frequently enough it'll likely always be set to `1`. I guess what's more...

For #1820, we should update Loki to a weekly release which contains https://github.com/grafana/loki/pull/6135, since it's not in the latest tagged release and tagged releases are uncommon.

> We could provide a way for users to do that; I think a new flag on the agent-operator binary could be a decent option but I'm not sure if...

@Kovah Please be kinder to the maintainers. We're all humans and mistakes will be made. Obviously hammering your DNS server wasn't a deliberate design goal. That being said, I'm sorry...

Passing `-disable-reporting` or `--disable-reporting` as an argument should do it. I'm working on reproducing now and I'll get back to you soon. In the meantime, are there any log messages...

Something weird is going on here. I ran this: ``` $ docker run grafana/agent:latest -disable-reporting --config.file=/etc/agent/agent.yaml --metrics.wal-directory=/etc/agent/data ``` And I'm not seeing any log lines saying `running usage stats reporter`....

@Kovah here's what I tried: I ran the latest Agent Docker image with usage stats disabled, exposing its HTTP server to my host machine: ``` $ docker run -p 12345:12345...

> Is there a config that could lead to this? The agent has only the posted cli flags and the config file which contains the scrape settings. No, not at...