{"version":"2.1.261","anchor":"immediate-command-telemetry-now-redacts-custom-command-names","canonical_anchor":"immediate-command-telemetry-now-redacts-custom-command-names","heading":"Immediate-command telemetry now redacts custom command names","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261\/e\/immediate-command-telemetry-now-redacts-custom-command-names","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261","markdown":"### Immediate-command telemetry now redacts custom command names\n\nCustom slash-command names are now hidden from telemetry, replaced with 'custom'.\n\nThe `tengu_immediate_command_executed` telemetry event no longer sends the raw slash-command name. Shipped commands now have their name hashed, and user-defined commands are replaced with the literal string `custom` before the event is sent.\n\n- Area: Telemetry\n- Names: `tengu_immediate_command_executed`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}