Description
Is your feature request related to a problem? Please describe.
In this solution used for logs collection in Kubernetes cluster it is visible that Otel collectors for logs collection (otlphttp exporter is used to send logs) keep persistent connection with Otel collectors for metadata enrichment (otlp receiver is used to get logs) what makes that adding more instances of Otel collectors for metadata enrichment does not help in handling higher amount of logs (using hpa does not make sense in this situation).
The problem was observed in production clusters.
In single node k8s cluster, which was used only for tests, it is visible that only one instance of Otel collectors for metadata enrichment is used despite the fact that there are 3 instances in the cluster.
In the same single node cluster when modified version of Otel collector with disabled HTTP keep-alives is used it is visible that all 3 instances of Otelcol collectors for metadata enrichment are working:
Describe the solution you'd like
Add option to disable HTTP keep-alives in OTLP/HTTP Exporter (it will require changes in HTTPClientSettings)
Additional context
I'd like to prepare pull request with changes to add option to disable HTTP keep-alives.