{"version":"2.1.219","anchor":"telemetry-ids-validated-before-sending","canonical_anchor":"telemetry-ids-validated-before-sending","heading":"Telemetry ids validated before sending","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219\/e\/telemetry-ids-validated-before-sending","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219","markdown":"### Telemetry ids validated before sending\n\nAnalytics ids are now filtered to safe characters before being sent, with no change you'll see.\n\n**What**\n\nA large set of analytics call sites now run ids through a validator, bounding what can reach the analytics pipeline.\n\n**Details**\n\n- The validator allows only `[A-Za-z0-9_-]` up to 128 characters and otherwise reports the literal \"nonconforming\".\n- Applied to background job ids and attach shorts, `session_id` on `tengu_remote_attach_session`, `appearance_id` on feedback\/survey and transcript-share events, `requestId` and `previousMessageId`, and `trigger_ids` which are now joined through the same validator.\n- Numeric fields such as `http_status` and bug-report `status_code` moved from `String(...)` to the string-coercing sanitizer.\n- No user-visible behaviour change.\n\n**Evidence**\n\n`nonconforming`\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}