OOM error caused by AzureMonitorLogRecordExporter

[rafalp88]

Below line cause OOM error. When DEBUG level is on, there will be some kind of recursive invocation.
LogRecords logging causes more log entries which causes sending more and more LogRecords.

azure-sdk-for-java/sdk/monitor/azure-monitor-opentelemetry-exporter/src/main/java/com/azure/monitor/opentelemetry/exporter/AzureMonitorLogRecordExporter.java

Line 57 in 1740413

LOGGER.verbose("exporting log: {}", log);

[github-actions]

Thank you for your feedback. Tagging and routing to the team member best able to assist.

[lmolkova]

@rafalp88

Thank you for reporting this!
As a mitigation step, could you please disable verbose logs from com.azure.monitor.opentelemetry.exporter? If you haven't done it already.

@heyams @trask could you please take a look?

it seems exporter logs with ClientLogger from core which, when such debug logs are enabled, produces enormous amount of logs.

We might need to figure out how to disable all logs from the exporter http pipeline completely or prevent the exporter from consuming its own logs in some other way. LMK if you need any help with ClientLogger.