fix(sdk): add validation for export_timeout_millis <= 0 in BatchSpanP…

[Dotify71]

Description

Fixes #5648

Currently, BatchSpanProcessor validates max_queue_size, schedule_delay_millis, and max_export_batch_size during initialization to ensure they are positive integers. However, export_timeout_millis was omitted from argument validation, allowing non-positive or negative values (0 or negative integers) to be passed without error.

This PR adds validation for export_timeout_millis in BatchSpanProcessor._validate_arguments(), raising a ValueError if export_timeout_millis <= 0.

Type of change

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

How Has This Been Tested?

• Unit tests in opentelemetry-sdk/tests/trace/export/test_export.py (test_invalid_export_timeout_millis)

Does This PR Require a Contrib Repo Change?

• Yes. - Link to PR:
• No.

Checklist:

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

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: Dotify71 / name: Dushyant Acharya (9b5daa0)

[opentelemetry-pr-dashboard]

Pull request dashboard status

Waiting on reviewers · refreshed 2026-09-17 08:34 UTC

Review the latest changes.

Status above doesn't look right?

• Just replied or pushed? Anything around or after the refresh time above may not be picked up yet — give it a few minutes.
• Anything look wrong? Report it with what you expected; it helps us improve the dashboard.

[henry3260]

Do we actually need to validate this? export_timeout_millis is stored in BatchProcessor but never read, and the log processor even has a comment saying "Not used. No way currently to pass timeout to export." So a non-positive value has no runtime effect today.

[Dotify71]

Thanks for taking a look @henry3260

I added validation mainly for consistency with schedule_delay_millis and max_queue_size, so users don't pass invalid negative values for OTEL_BSP_EXPORT_TIMEOUT.

That said, if we prefer not validating it until export timeouts are enforced in the export loop, happy to follow your lead!

[henry3260]

cc @emdneto @xrmx

[henry3260]

If we want to add validation here, we should add this too :)

opentelemetry-python/opentelemetry-sdk/src/opentelemetry/sdk/_logs/_internal/export/__init__.py

Line 286 in ab22674

BatchLogRecordProcessor._validate_arguments(max_queue_size, schedule_delay_millis, max_export_batch_size)

[Dotify71]

Added validation to BatchLogRecordProcessor as well and updated unit tests :))