Đỗ Trọng Hải

It seems the similar CRD created in [Loki](https://github.com/grafana/loki/blob/main/production/helm/loki/values.yaml#L3300) chart is the culprit for the conflict here. We probably have to switch Loki's self-monitoring from Agent to Alloy in the long...

I intend to put some sleep like 5 seconds after executing `sc stop` in the NSIS installer. Do you think it'll resolve the perceived root cause?

Hi there, the proposed change wasn't merged into `grafana/agent` codebase actually (see https://github.com/grafana/agent/pull/6018). For the rationale behind, you can check in the PR's discussion. Thanks for checking by!

This is controversial take but I think we shouldn't have global options as it would make debugging regarding to component-level option harder as we always have to take global options...

I think its a good enhancement to add into Alloy's AWS components. I'll draft up something this weekend 🥸

Thanks Matt! I'll implement the poller and fix whatever makes the tests failed. Maybe in the long run, we can have a reusable implementation. But that's for another day, I...

I wonder if we still need to implement an equivalent otelcol-to-Alloy converter, similar to [these](https://github.com/grafana/alloy/tree/main/internal/converter/internal/otelcolconvert)? 🤔

hi @mrashad10, are you still working on this PR? If anything's troubling you, feel free to raise it here!

Oops, `git rebase` sheenanigan 🤦

Hi folks, cross-post my discovery here. https://github.com/grafana/alloy/issues/464