telemetry(amazonq): deprecate codewhisperer_userDecision
metric
#6702
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
the
codewhisperer_userDecision
metric isn't used by the codewhisperer/Q team. And it is very noisy (5x more emits than second most frequent metric, 20x more emits than the third).Solution
Stop emitting this metric from vsCode
Note
The user decision events are still kept since they are used to calculate
userTriggerDecision
. De-noising it would be the next TODOfeature/x
branches will not be squash-merged at release time.