What: New telemetry backend for event logging and monitoring Details:
- Sends logs to Datadog HTTP intake endpoint:
https://http-intake.logs.datadoghq.com/api/v2/logs - Controlled by feature gate
tengu_log_datadog_events(gate name at line 477899) - Batches events for efficiency (batch size threshold
KBI, flush intervalVBI = 15000msat line 477634) - Includes context tags: user type, version, model, session ID, platform details
- Automatic flush on process exit
- Evidence:
FBI constant at line 477632, gate checker2 at line 477899, batching logic inQB0() at line 477567andBB0() at line 477543
tengu_log_datadog_events On for this account, and not off by defaultThe flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.
This account: on · anonymous baseline: on · compiled default in v2.0.36: 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.
Read once, for one account on one subscription tier, against v2.0.36. It isn't a statement about your account. What a flag value here can and cannot tell you
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.