oss_21_logger_provider_log_record_limits

[ocelotl]

Closes #37

LoggerProvider now accepts a programmatic limits (LogRecordLimits, analogous to TracerProvider's SpanLimits); threaded into Logger and _from_api_log_record so attribute count/length limits apply to emitted log records (Linear OSS-21, finding L2). Backward compatible (defaults unchanged).

Validation: scope contained to opentelemetry-sdk + changelog; logs suite 115 passed.

Linear issue: https://linear.app/dash0/issue/OSS-21/l2-loggerprovider-cannot-configure-logrecordlimits-programmatically

[ocelotl]

🔒 Internal (dash0) — not for upstream.

• Linear: https://linear.app/dash0/issue/OSS-21/l2-loggerprovider-cannot-configure-logrecordlimits-programmatically (finding L2)
• Closes: oss_21_logger_provider_log_record_limits #37 · Branch: oss_21_logger_provider_log_record_limits · Commit: 88b7449a7
• Validation: logs suite 115 passed; scope sdk + changelog. Note: same-file overlap with OSS-22/PR oss_22_logger_enabled #26 (merge sequentially); complements OSS-26/PR oss_26_declarative_config_env_substitution #36 attribute_limits limitation.

[ocelotl]

📣 Public-facing draft — to be used for the upstream PR in open-telemetry/opentelemetry-python. No internal references; copy verbatim.

Title: Add programmatic LogRecordLimits support to LoggerProvider

What

LoggerProvider.__init__ now accepts a keyword-only limits argument of type LogRecordLimits. The provider stores it, passes it to each Logger it creates, and threads it into ReadWriteLogRecord._from_api_log_record, so attribute-count and attribute-value-length limits are enforced on emitted log records.

Why

TracerProvider already accepts SpanLimits programmatically, but the logs SDK only exposed LogRecordLimits through environment variables — _from_api_log_record always used default limits, so there was no way to set log-record limits in code. This aligns the logs SDK with the tracing SDK and the spec's "LogRecord Limits" section (mirrors Java's SdkLoggerProviderBuilder.setLogLimits / LogLimits).

Spec

specification/logs/sdk.md — "LogRecord Limits".

Compatibility

Fully backward compatible: when limits is omitted, the provider constructs a default LogRecordLimits(), preserving the previous env-var/default behavior.

Tests

New TestLoggerProviderLimits emits records through a real LoggerProvider(limits=...) + SimpleLogRecordProcessor + in-memory exporter and asserts: default provider applies the default attribute-count limit and reports dropped attributes; programmatic max_log_record_attributes bounds attribute count; max_log_record_attribute_length truncates values; and the global max_attributes/max_attribute_length act as fallbacks. Full logs suite passes (115).

[github-actions]

This PR has been automatically marked as stale because it has not had any activity for 14 days. It will be closed if no further activity occurs within 14 days of this comment.
If you're still working on this, please add a comment or push new commits.