using filelog receiver output operator

[pankaj101A]

file exporter is buffering the content and writing the content into batches with one batch containing multiple lines.

To mitigate this problem removing the exporter completely and using file output operator at adds the nextLine character explicitly at the end of each log like fluentbit

[jagan2221]

Looks good!
Also Do we have any performance tests to see how fluentbit vs otel file output operator?
Like how are we planning to ensure there is no large scale performance degradation

[pankaj101A]

Looks good! Also Do we have any performance tests to see how fluentbit vs otel file output operator? Like how are we planning to ensure there is no large scale performance degradation

There are not performance tests for tailing-sidecar or sumologic kubernetes collection helm.

We can observe how this change behaves on our k8s deployment (zaidan) and check for any alert. This will provide good confidence about performance

[jagan2221]

Looks good! Also Do we have any performance tests to see how fluentbit vs otel file output operator? Like how are we planning to ensure there is no large scale performance degradation

There are not performance tests for tailing-sidecar or sumologic kubernetes collection helm.

We can observe how this change behaves on our k8s deployment (zaidan) and check for any alert. This will provide good confidence about performance

Okay, Let's compare log data lag before and after updating to otel based sidecar.