Memory Limiter processor should be configurable to drop the data.

[Harnoor-se7en]

trafficstars

Is your feature request related to a problem? Please describe. We use Kong API gateway 2.8x and its Zipkin plugin to export traces. Unfortunately, this Zipkin plugin uses a batch queue with no max size limit (i.e. we can't specify the max number of batches that can be queued before the oldest batch is dropped when a new one is queued). So in case, Otel-collector is overloaded (the batch queue is full), the memory limiter would refuse the data and the source(sender: Zipkin plugin) would retry sending the same batch. This will put pressure on the source.

Describe the solution you'd like There should be a configurable option such that the memory limiter simply drops data instead of refusing it so that the sender does not receive backpressure.