{"version":"2.1.280","anchor":"plugin-load-telemetry-now-also-reports-disabled-plugin-names","canonical_anchor":"plugin-load-telemetry-now-also-reports-disabled-plugin-names","heading":"Plugin-load telemetry now also reports disabled plugin names","tier":"internal","area":"Telemetry","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/plugin-load-telemetry-now-also-reports-disabled-plugin-names","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Plugin-load telemetry now also reports disabled plugin names\n\nPlugin-load telemetry now reports disabled plugin names alongside the already-reported enabled ones\n\n**What**\n\nThe telemetry event that fires when plugins load (`tengu_plugins_loaded`) previously only reported which plugins were enabled, as `enabled_names` (sourced from `ant_enabled_names`). It now also reports `disabled_names`, sourced from a new `ant_disabled_names` field on the loaded-plugins data. In at least one failure path this new field can be empty (`void 0`).\n\n**Why**\n\nThis gives a fuller picture of plugin state at load time, not just which plugins were active but which were explicitly turned off, which is useful for diagnosing plugin-related issues.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}