Fix BatchLogRecordProcessor default schedule_delay_millis to 1000ms per OTel spec

[Manvi2402]

…er OTel spec

Description

The BatchLogRecordProcessor._DEFAULT_SCHEDULE_DELAY_MILLIS was set to
5000ms, but the OTel specification defines OTEL_BLRP_SCHEDULE_DELAY
default as 1000ms.

Fixes #4991

Type of change

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Updated existing unit tests in opentelemetry-sdk/tests/logs/test_export.py
to reflect the corrected default value of 1000ms instead of 5000ms.

Does This PR Require a Contrib Repo Change?

• Yes. - Link to PR:
• [ x ] No.

Checklist:

• [ x ] Followed the style guidelines of this project
• [ x ] Changelogs have been updated
• [ x ] Unit tests have been added
• [ x ] Documentation has been updated

[pmcollins]

Thanks for the change. Can you also update the default value in the docstring for OTEL_BLRP_SCHEDULE_DELAY (in environment_variables/__init__.py)?

[Manvi2402]

Hi @pmcollins , I've made both the requested changes — updated the CHANGELOG wording and the OTEL_BLRP_SCHEDULE_DELAY docstring default to 1000ms. Please let me know if anything else is needed!

[Manvi2402]

Thank you for the detailed review @themavik . Agreed on the performance/rate-limit docs — that feels like a separate issue. Happy to open one if that would be helpful!