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
- Soooooooooo many teams have specific latency metric fields and many
are asking to add them for re-invent
## Solution
- De-dup a lot of them e.g. amazonqGenerateApproachLatency,
amazonqGenerateCodeResponseLatency, amazonqEndOfTheConversationLatency,
etc
## Other notes
- amazonq_approachInvoke would then have perfServerLatency instead of an
individual amazonqGenerateApproachLatency field
- amazonq_codeGenerationInvoke would then have perfServerLatency instead
of an individual amazonqGenerateCodeResponseLatency field
- amazonq_endChat would then have perfE2ELatency instead of an
individual amazonqEndOfTheConversationLatency field
- In the future we can re-use the perfClientLatency metric for tracking
the duration of different events that only happen in the client side
(e.g. how long the client latency takes in the amazon q chat flow)
0 commit comments