v2 - Allow client-side rate limiting for logs

[kittydoor]

I would like to collect pod (and other) logs from my multiple k8s clusters and push them to a singular lgtm stack. In doing so, there is a risk that in more experimental clusters due to an issue, a ton of logs are generated that I do not actually wish to keep all of them.

For this, I would like to be able to rate limit on alloy on some basis such as maximum logs per month, or even something such as better maximum logs per custom time span.

Is there a way to set this up in the current state of the chart?

Even if so, is it possible for a convenience helm value to be exposed by the pod-logs feature + some simple documentation on how to use it?

---

Additionally, though out of scope for the initial ask, it would be great to be able to set this up with more granularity on both a global basis, and a per-feature basis (pod-logs vs node-logs, pod-logs per namespace, otel logs, etc).