Open Telemetry Source GRPC Max Message Size Configuration

[mjesperson]

Hi Team,
We use vector to send logs to storage. I recently saw some errors from our client showing:

Error, message length too large: found 4327818 bytes, the limit is: 4194304 bytes

After doing some research, it seems that 4194304 bytes is the default value. The recommended workarounds were either to reduce the batch size on the client (however there are still chances we could get batches with larger values than default) or to increase the max message size on the server.

I went through the Vector Opentelemetry Source documentation and see nothing about configuring a max message size in the grpc source config. Am I missing something or is this currently not possible to set from Vector's side.

Thanks!

[mjesperson]

We worked around this issue by using the HTTP endpoint for the open telemetry vector source. However it would be nice if the vector GRPC open telemetry server were configurable to accept a larger message size than default. Some of the things we send are pretty large, and even with a batch size of 64 on the client we go past this threshold

[Myzel394]

How did you configure the http endpoint?

[pront]

However it would be nice if the vector GRPC open telemetry server were configurable to accept a larger message size than default. Some of the things we send are pretty large, and even with a batch size of 64 on the client we go past this threshold

Agreed, it would be nice to capture this in a new feature request.