Paulin Todev

@BarunKGP - The rebase must have gone wrong, because there are lots of changes in the PR now.

This is the way I normally rebase my feature branches: ``` git fetch git rebase origin/main ``` If you'd like to clean up your branch in a more step-by-step basis,...

@clayton-cornell I fixed it, no worries. Thank you for the review! @BarunKGP Thank you for your contribution, and apologies for the delay with the review! I also opened a [PR](https://github.com/grafana/alloy/pull/1043)...

Hello, thank you for submitting a bug report! Did the Agent run successfully with this configuration on the domain controller before? Or did it stop sending logs only recently? In...

It seems like this issue, along with grafana/alloy#432 and grafana/alloy#433 might be caused by too many messages coming in from the event log. Would it be possible to limit the...

> How can this problem be diagnosed? If you are using the Flow mode, you could use [loki.echo](https://grafana.com/docs/agent/latest/flow/reference/components/loki.echo/) after the loki processing stage so that you can see the logs...

Yes, I think you could use the `metrics` stage in this case. It would be useful to have a counter metric for the log lines which you believe are missing....

`loki.source.kubernetes_events` also uses a positions file. I am not sure if there is a need for it to go in scope for this migration path doc as well.

Looks like `loki.source.docker` also uses a positions file.

Note that there is also an [open PR](https://github.com/grafana/agent/pull/5905) for the Agent to add a Prometheus feature which is not available in Prometheus 2.48. Maybe we could upgrade the Agent straight...