Skip to content

oss_23_logrecord_attribute_limit_env_vars #47

Description

@ocelotl

Support OTEL_LOGRECORD_ATTRIBUTE_COUNT_LIMIT / OTEL_LOGRECORD_ATTRIBUTE_VALUE_LENGTH_LIMIT so log attribute limits can be tuned independently of spans (Linear OSS-23, finding L4).

Branch / worktree: oss_23_logrecord_attribute_limit_env_vars
Stacked on: oss_21_logger_provider_log_record_limits (PR #42) — depends on the L2 programmatic path.

Linear issue: https://linear.app/dash0/issue/OSS-23/l4-otel-logrecord-attribute-count-limit-value-length-limit-unsupported

Activity

  1. ocelotl commented on Jul 22, 2026

    @ocelotl
    OwnerAuthor

    🔒 Internal (dash0) — not for upstream.

    Closing as already resolved upstream — no action needed.

    The finding (Linear OSS-23 / L4) said the dedicated OTEL_LOGRECORD_ATTRIBUTE_COUNT_LIMIT / OTEL_LOGRECORD_ATTRIBUTE_VALUE_LENGTH_LIMIT env vars were unsupported. On current upstream/main both constants are already declared (opentelemetry-sdk/.../environment_variables/__init__.py) and read by LogRecordLimits with correct precedence (dedicated OTEL_LOGRECORD_* > generic OTEL_ATTRIBUTE_* > default), and the covering unit tests already exist and pass (opentelemetry-sdk/tests/logs/test_log_limits.py, 16 passed). Verified via git show upstream/main:....

    Note: this is distinct from OSS-21/L2 (the programmatic LoggerProvider(limits=...) path), which was genuinely missing and is addressed by PR #42. Only the env-var path (L4) was already upstream.

    Linear issue: https://linear.app/dash0/issue/OSS-23/l4-otel-logrecord-attribute-count-limit-value-length-limit-unsupported

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions