{"version":"2.1.280","anchor":"plugin-installupdate-telemetry-now-records-git-commit-sha","canonical_anchor":"plugin-installupdate-telemetry-now-records-git-commit-sha","heading":"Plugin install\/update telemetry now records git commit SHA","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/plugin-installupdate-telemetry-now-records-git-commit-sha","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Plugin install\/update telemetry now records git commit SHA\n\nPlugin install\/update telemetry now also records the plugin's install location and, for updates, its git commit SHA\n\n**What**\n\nThe `tengu_plugin_installed_cli` and `tengu_plugin_updated_cli` telemetry events (sent when a plugin is installed or updated from the command line) now include extra fields:\n\n- a set of fields keyed off the plugin's install location, sent with both events\n\n- the plugin's git commit SHA, sent with the update event only\n\nThis builds on the marketplace-catalog verification step added earlier, which confirms a plugin exists in the marketplace before logging it and otherwise falls back to a redacted, third-party record.\n\n**Why**\n\nRecording the install location and commit SHA gives more precise identification of exactly which plugin version was installed or updated, on top of the existing marketplace verification.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}