Now telemetry reports very little about vscode command failures, to avoid sending user sensitive data. Single vscode command can use 0..many CLI commands during execution. Current reporting mechanism sends back only VsCommandError's telemetry message, which is very vague 'Unexpected error occurs'. It should also send info about what command/subcommand failed without actual option values. That should give us idea where exactly vscode command fails.
Now telemetry reports very little about vscode command failures, to avoid sending user sensitive data. Single vscode command can use 0..many CLI commands during execution. Current reporting mechanism sends back only VsCommandError's telemetry message, which is very vague 'Unexpected error occurs'. It should also send info about what command/subcommand failed without actual option values. That should give us idea where exactly vscode command fails.