William Dumont

> Once comments on PRs for design documents have slowed down, the PR is merged regardless of the current state of the proposal. More PRs to update the design document...

> Proposals are in one of the following states: The doc mentions a __Hold__ state which is not described there: >Proposals that break [backward compatibility] are moved to a "Hold"...

> Comments on PRs for design documents should be restricted to grammar, spelling, or proposal procedural errors related to the preparation of the design document itself. All other comments should...

> The acceptance cycle of most proposals is increased to take at least three weeks; one week to move to _Active_, one additional week to move to _Likely Accept_, and...

I like the idea of only merging the design docs for accepted proposals. When the code is not clear, it can be useful to search for a related design doc...

@ptodev @thampiotr thanks for your feedback! I made some changes to try to improve naming and readability. I also split the interface in two: DebugCallbackRegistry and DebugDataPublisher. I'm now using...

waiting for @clayton-cornell feedback on the doc before merging it

Hello, thanks for reporting the bug and sorry about that. I think that I have a fix for it: https://github.com/grafana/alloy/pull/875.

> Metric values are also fine if we send them directly to the NewRelic metrics API with Prometheus Server remote_write. if you send the metrics with [prometheus.remove_write](https://grafana.com/docs/alloy/latest/reference/components/prometheus/prometheus.remote_write/) with Alloy in...

Hi, I tried it in a docker container and it worked fine. When I used "apt-get remove --purge grafana-agent-flow", it did not remove the /var/lib/grafana-agent-flow dir. I tried installing again...