{"version":"2.1.228","anchor":"datadog-flush-interval-read-from-a-second-variable-name","canonical_anchor":"datadog-flush-interval-read-from-a-second-variable-name","heading":"Datadog flush interval read from a second variable name","tier":"use","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/datadog-flush-interval-read-from-a-second-variable-name","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Datadog flush interval read from a second variable name\n\nA telemetry flush interval can now be set with either of two environment variable names.\n\n**What**\n\nOne flush-interval call site now reads `CLAUDE_CODE_DATADOG_FLUSH_INTERVAL_MS`. The older `CLAUDE_CODE_DD_ERROR_TRACKING_FLUSH_INTERVAL_MS` is still registered and still read elsewhere, so both names are live and set whichever the call site you care about uses.\n\n**Evidence**\n\n`CLAUDE_CODE_DATADOG_FLUSH_INTERVAL_MS`\n\n- Area: Telemetry\n- Names: `CLAUDE_CODE_DATADOG_FLUSH_INTERVAL_MS`, `CLAUDE_CODE_DD_ERROR_TRACKING_FLUSH_INTERVAL_MS`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 2\/5"}