{"version":"2.1.242","anchor":"telemetry-for-plugin-test-mocks-and-refused-subscriptions","canonical_anchor":"telemetry-for-plugin-test-mocks-and-refused-subscriptions","heading":"Telemetry for plugin test mocks and refused subscriptions","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/telemetry-for-plugin-test-mocks-and-refused-subscriptions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Telemetry for plugin test mocks and refused subscriptions\n\nPlugin evaluation mock failures are reported by kind, and refused subscriptions get their own reason.\n\n**What**\n\nFailures setting up mocks during plugin evaluation are now reported under a single event, tagged by kind: registration, identity, missing tools, integrity, or aborted by the mock. Separately, the code that classifies subscription outcomes gained a forbidden-subscribe reason with a latched variant.\n\n**Evidence**\n\n`cli_plugin_eval_mocks`\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}