Proposed title of this feature request
Implement throttling in Vector

What is the nature and description of the request?

Customers want to limit log limits to avoid problems at the cluster level.

Why does the customer need this? (List the business requirements)

Avoid cluster issues and losing huge number of logs

List any affected packages or components.

Logging component.

This is the point for the client:

Summary: Rate limits for log sources that are possibly chatty to address the use-case of the noisy neighbor.
Details: Openshift as a multi-tenant environment that shares the log system between different projects. Offend, a human error or a bug, could lead to excessive logging on one pod creating a noisy neighbor scenario.
Impact: Log system get temporally saturated by chatty pods, genuine logs are delayed hours.
Suggestions: Implement some kind of rate limit per project, so the problem get confined at project level only.

In Vector official documentation exists a throttle option --> https://vector.dev/docs/reference/configuration/transforms/throttle/

And previously for fluentd, this option was evaluated --> https://issues.redhat.com/browse/LOG-1139