You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem:
Adding a new telemetry : Client component latency for codewhisperer.
telemetry definition in:
aws/aws-toolkit-common@618a9fb
A client component latency metric is emitted only once for each complete
GenerationRecommendation pagination session if the suggestion is shown to the
user.
{
"name": "codewhispererFirstCompletionLatency",
"type": "double",
"description": "The time it takes for the response to be received after the plugin makes a first GenerateCompletions API call."
},
{
"name": "codewhispererEndToEndLatency",
"type": "double",
"description": "The time it takes for the first completion to be shown in the IDE after the user performs the CW trigger action."
},
{
"name": "codewhispererAllCompletionsLatency",
"type": "double",
"description": "The time it takes for the last GenerateCompletions response to be received after plugin makes a first call to GenerateCompletions API."
},
{
"name": "codewhispererPostprocessingLatency",
"type": "double",
"description": "The time it takes for the first completions to be displayed in the IDE after the plugin receives the initial Completions object."
},
{
"name": "codewhispererPreprocessingLatency",
"type": "double",
"description": "The time it takes for the plugin to make the first GenerateCompletions API call after the user performs the CW trigger action."
},
{
"name": "codewhispererCredentialFetchingLatency",
"type": "double",
"description": "The time it takes to get the Sono/SSO credential for the invocation."
},
Solution:
Record timestamp and compare the timestamp to build the Client component latency
metric and report it to service.
0 commit comments