{"version":"2.0.36","anchor":"datadog-telemetry-integration","canonical_anchor":"datadog-telemetry-integration","heading":"Datadog Telemetry Integration","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.0.36\/e\/datadog-telemetry-integration","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.0.36","markdown":"### Datadog Telemetry Integration\n\n**What:** New telemetry backend for event logging and monitoring **Details:**\n\n- Sends logs to Datadog HTTP intake endpoint: `https:\/\/http-intake.logs.datadoghq.com\/api\/v2\/logs`\n- Controlled by feature gate `tengu_log_datadog_events` (gate name at line 477899)\n- Batches events for efficiency (batch size threshold `KBI`, flush interval `VBI = 15000ms` at line 477634)\n- Includes context tags: user type, version, model, session ID, platform details\n- Automatic flush on process exit\n- **Evidence**: `FBI constant at line 477632`, gate check `er2 at line 477899`, batching logic in `QB0() at line 477567` and `BB0() at line 477543`\n\n- Flag `tengu_log_datadog_events`: On for this account, and not off by default (read for one account on one subscription tier against v2.0.36; this account: on, anonymous baseline: on, compiled default: no gate table built for this version) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release."}