{"version":"2.1.267","anchor":"tengu-feature-bad-tengu-feature-sad-now-sanitize-the-error","canonical_anchor":"tengu-feature-bad-tengu-feature-sad-now-sanitize-the-error","heading":"tengu_feature_bad \/ tengu_feature_sad now sanitize the error_code field before sending","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/tengu-feature-bad-tengu-feature-sad-now-sanitize-the-error","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### tengu_feature_bad \/ tengu_feature_sad now sanitize the error_code field before sending\n\nFeature-bad\/feature-sad telemetry now sanitizes the error_code field before sending it\n\n**What**\n\nThe internal telemetry events `tengu_feature_bad` and `tengu_feature_sad` now validate the `error_code` value they record. If the value doesn't match an expected pattern, it gets replaced with a placeholder value of `nonconforming` before being sent.\n\n**Why**\n\nThis keeps malformed or unexpected error codes from being recorded verbatim in telemetry, making the data more consistent and predictable to analyze.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}