When odo command fails, the exception message includes user sensetive information like:
- local filesystem path
- user name for login command
- cluster URL
- login token
In current implementation those error are not reported because of implementation error, but when error reporting fixed that information should not get into telemetry events.
Extension should send error messages without user sensitive information. That is possible for VsCommandExeptions instances because it contains two messages:
- message - to show to user with user sensitive information
- telemetryMessage - to send with telemetry event, w/o user sensitive information
For instance if 'message' for login failure would have full path to odo command, cluster url and user name and odo stderr output, 'telemetryMessage' would have only 'Failed to login to cluster'.
Other exceptions might have sensitive information, that's why we cannot just send exeption.message in telemetry event.
When odo command fails, the exception message includes user sensetive information like:
In current implementation those error are not reported because of implementation error, but when error reporting fixed that information should not get into telemetry events.
Extension should send error messages without user sensitive information. That is possible for VsCommandExeptions instances because it contains two messages:
For instance if 'message' for login failure would have full path to odo command, cluster url and user name and odo stderr output, 'telemetryMessage' would have only 'Failed to login to cluster'.
Other exceptions might have sensitive information, that's why we cannot just send exeption.message in telemetry event.