-
Notifications
You must be signed in to change notification settings - Fork 436
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
refactor(telemetry): prepend the error code/name to the
reasonDesc
…
…field (#5557) ## Problem: In telemetry we sometimes add the error message to the `reasonDesc` field. Additionally when using `getTelemetryReasonDesc()` it will recurse through the causal chain of the error and return a value composed of all the error messages. Eg: `Reason A | Reason B | Reason C` The issue is that the nested errors may have useful context (in addition to the message) in their id (code or name). And currently this is lost. ## Solution: Prepend the code/name to the error messages when using `getTelemetryReasonDesc()` Eg: `CodeA: Reason A | CodeB: Reason B | NameC: Reason C` --- <!--- REMINDER: Ensure that your PR meets the guidelines in CONTRIBUTING.md --> License: I confirm that my contribution is made under the terms of the Apache 2.0 license. --------- Signed-off-by: Nikolas Komonen <[email protected]>
- Loading branch information
1 parent
4a88c9e
commit 4bb2fc1
Showing
4 changed files
with
69 additions
and
21 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters