Problem
While adding the unified cli_command telemetry event, the command runner also needs to keep sending the legacy per-command events such as cli_command_push and cli_command_datasets_ls during the migration period.
If the new unified event is awaited before the legacy event, a slow or failing send path can delay or prevent the legacy event from being attempted. That weakens backward compatibility for dashboards and Mixpanel custom events that still depend on the old event names.
Expected behavior
For every CLI command execution, attempt to send both events from the same payload:
cli_command- legacy
cli_command_<command>
The two sends should be independent so one failure does not prevent the other.
Notes
The concrete command should continue to be available in the event payload as commandString.
Problem
While adding the unified
cli_commandtelemetry event, the command runner also needs to keep sending the legacy per-command events such ascli_command_pushandcli_command_datasets_lsduring the migration period.If the new unified event is awaited before the legacy event, a slow or failing send path can delay or prevent the legacy event from being attempted. That weakens backward compatibility for dashboards and Mixpanel custom events that still depend on the old event names.
Expected behavior
For every CLI command execution, attempt to send both events from the same payload:
cli_commandcli_command_<command>The two sends should be independent so one failure does not prevent the other.
Notes
The concrete command should continue to be available in the event payload as
commandString.