Datadog telemetry now sanitizes any defined model value, not just string ones, dropping events it can't sanitize
In 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.
This 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.