{"version":"2.1.274","anchor":"new-otel-log-managed-settings-telemetry-env-var","canonical_anchor":"new-otel-log-managed-settings-telemetry-env-var","heading":"Managed settings can now be reported to telemetry","tier":"use","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/new-otel-log-managed-settings-telemetry-env-var","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Managed settings can now be reported to telemetry\n\nA new OTEL_LOG_MANAGED_SETTINGS env var adds managed\/policy settings details to telemetry, with sensitive values redacted\n\n**Unclear.** What effect setting OTEL_LOG_MANAGED_SETTINGS has is not specified beyond it being a recognized telemetry-related variable.\n\n**What**\n\n- A new environment variable, `OTEL_LOG_MANAGED_SETTINGS`, is now recognized as an OpenTelemetry-related setting.\n\n- A new telemetry event, `managed_settings_resolved`, reports metadata about how managed (policy-controlled) settings were resolved: their source, behavior, helper state, whether a helper was applied, and the entry's key, path, and script hash.\n\n- If `OTEL_LOG_MANAGED_SETTINGS` is set, this event also includes the actual resolved settings content. Values are redacted to `[REDACTED]` unless they match the expected tool\/permission-rule\/value schema, are known tool names, or match an `mcp__` tool naming pattern.\n\n**Why**\n\nThis gives administrators visibility into how managed\/policy settings are being resolved across an organization's machines, useful for auditing and debugging configuration issues, while redaction keeps unexpected or sensitive values from leaking into telemetry unless explicitly opted in.\n\n- Area: Telemetry\n- Names: `OTEL_LOG_MANAGED_SETTINGS`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 1\/5"}