NodeJS: Replace SimpleLogRecordProcessor by BatchLogRecordProcessor

[rndD]

Fixes #1798

SimpleLogRecordProcessor has a concurrency limit of 30 simultaneous export promises. After hitting this limit, the Processor throws the error Error: Concurrent export limit reached.

To avoid the error during heavy logging, we can use BatchLogRecordProcessor.

BatchLogRecordProcessor can already be configured via env vars, which is good for lambda layer:

• OTEL_BLRP_MAX_EXPORT_BATCH_SIZE
• OTEL_BLRP_MAX_QUEUE_SIZE
• OTEL_BLRP_SCHEDULE_DELAY
• OTEL_BLRP_EXPORT_TIMEOUT

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: rndD / name: Alexey Kalmakov (4029b1f, ab5c8cb, 4f5b8df)

[rndD]

cc @serkan-ozal

[serkan-ozal]

Thanks @rndD,
That's fast :)
I have added one minor comment.

[serkan-ozal]

@rndD PR look good, but there is lint issue. Can you fix that by npm run lint:fix

[rndD]

That's fast :)

Had it ready. I was testing if the batchProcessor solves the problem. I might say that the publishing layer took a while to do manually. I appreciate all the infrastructure you built to make layers publicly available.

Any chance you can trigger nodejs layer publish after merging this one?

[serkan-ozal]

Hi @rndD,

I think we should wait this PR (#1789) got approved and merged for the next release, but not sure what @tylerbenson thinks

[tylerbenson]

LGTM.