{"version":"2.1.280","anchor":"model-list-telemetry-now-tracks-a-served-overflow-and-base","canonical_anchor":"model-list-telemetry-now-tracks-a-served-overflow-and-base","heading":"Model-list telemetry now tracks a 'served overflow' and base\/main picker mismatch separately","tier":"internal","area":"Telemetry","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/model-list-telemetry-now-tracks-a-served-overflow-and-base","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Model-list telemetry now tracks a 'served overflow' and base\/main picker mismatch separately\n\nModel-list telemetry now separately tracks 'served overflow' counts and full picker-set mismatches\n\n**What**\n\nInternal telemetry that compares model capability lists now reports `picker_set_match`, `picker_added`, and `picker_removed` from a richer underlying object, and adds two new fields: `picker_full_match` and `served_overflow_count`. The detailed before\/after picker payloads (`picker_old`\/`picker_new`) are now only included when either the base or the full picker set doesn't match.\n\n**Why**\n\nThis gives more precise internal visibility into when the list of models shown to users diverges from what's expected, and avoids sending the full payload for comparisons that already match, trimming unnecessary telemetry data.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}