{"version":"2.1.268","anchor":"datadog-model-sanitization-now-runs-on-any-defined-model-val","canonical_anchor":"datadog-model-sanitization-now-runs-on-any-defined-model-val","heading":"Datadog model-sanitization now runs on any defined model value, not just strings","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/datadog-model-sanitization-now-runs-on-any-defined-model-val","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Datadog model-sanitization now runs on any defined model value, not just strings\n\nDatadog telemetry now sanitizes any defined model value, not just string ones, dropping events it can't sanitize\n\n**What**\n\nIn the internal Datadog telemetry pipeline, the step that checks and cleans up the `model` field before sending an event used to only run if the model value was a text string. Now it runs whenever the model value is defined at all, including cases where it is something else, like a number or `null`. If the value can't be recognized as a known model, the entire telemetry event is now dropped rather than being sent with an unrecognized or malformed model field.\n\n**Why**\n\nThis prevents malformed or unexpected model values from being forwarded in telemetry data, at the cost of silently dropping the whole event when the model field isn't a recognizable string.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}