{"version":"2.1.273","anchor":"new-telemetry-event-names-addedremoved","canonical_anchor":"new-telemetry-event-names-addedremoved","heading":"New telemetry event names added\/removed","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/new-telemetry-event-names-addedremoved","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### New telemetry event names added\/removed\n\nSeveral new internal telemetry event names added; the old model_catalog_flag_rows event removed\n\n**Unclear.** What specific behaviors these new telemetry events measure is not stated beyond their names.\n\n**What**\n\nThe list of recognized telemetry event names gained several new entries: `upgrade_relay_fork_direct`, `refusal_same_model_retry`, `rc_repl_fork_conversation`, `mcp_serve_file_call`, and `publish_settling`. The `model_catalog_flag_rows` event was removed.\n\n**Why**\n\nThese are internal telemetry changes with no direct user-facing effect, though the new names hint at tracking for things like relay-based upgrades, same-model refusal retries, REPL conversation forking, MCP file-serving calls, and publish settling.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}