During the operation of otelcol, errors are often reported, and the specific error content is as follows:
2024-04-22T07:17:12.488Z error exporterhelper/queue_sender.go:101 Exporting failed. Dropping data. {"kind": "exporter", "data_type": "traces", "nameermanent error: rpc error: code = ResourceExhausted desc = grpc: received message after decompression larger than max (4430579 vs. 4194304)", "dropped_items": 441}
go.opentelemetry.io/collector/exporter/exporterhelper.newQueueSender.func1
go.opentelemetry.io/collector/exporter@v0.97.0/exporterhelper/queue_s
From a quick search, it looks like a GRPC setting would need to be updated in the exporter helper code to handle the size of message that you're attempting to send.
Component(s)
No response
Describe the issue you're reporting
During the operation of otelcol, errors are often reported, and the specific error content is as follows: 2024-04-22T07:17:12.488Z error exporterhelper/queue_sender.go:101 Exporting failed. Dropping data. {"kind": "exporter", "data_type": "traces", "nameermanent error: rpc error: code = ResourceExhausted desc = grpc: received message after decompression larger than max (4430579 vs. 4194304)", "dropped_items": 441} go.opentelemetry.io/collector/exporter/exporterhelper.newQueueSender.func1 go.opentelemetry.io/collector/exporter@v0.97.0/exporterhelper/queue_s
Otelcol version: 0.97.0
CPU usage and memory usage:
Main configurations:
Meanwhile, how to modify the limitations of GRPC ` s 4M