Client telemetry should provide better error identification
Open
feature-request
telemetry
- Dominant language
- Python
- Stars
- 4.6k
- Forks
- 3.5k
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 60
Description
### Description
When looking at our client telemetry at errors, we have a few values:
* Command executed (if parsed and known)
* Message text
* Stack trace
* Fault type
But these values make it impossible to collate down to a specific error condition. For example, identifying login errors or polling state failures can only be investigated via manual processes.
Is it possible to provide some invariant error names (FaultName)?
Contributor guide
Assessment
This issue has not been assessed yet.