Commit 608571e
authored
feat: add general latency metrics (#913)
## 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)1 parent f851093 commit 608571e
1 file changed
+17
-2
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1145 | 1145 | | |
1146 | 1146 | | |
1147 | 1147 | | |
1148 | | - | |
| 1148 | + | |
1149 | 1149 | | |
1150 | 1150 | | |
1151 | 1151 | | |
| |||
1488 | 1488 | | |
1489 | 1489 | | |
1490 | 1490 | | |
| 1491 | + | |
| 1492 | + | |
| 1493 | + | |
| 1494 | + | |
| 1495 | + | |
| 1496 | + | |
| 1497 | + | |
| 1498 | + | |
| 1499 | + | |
| 1500 | + | |
| 1501 | + | |
| 1502 | + | |
| 1503 | + | |
| 1504 | + | |
| 1505 | + | |
1491 | 1506 | | |
1492 | 1507 | | |
1493 | 1508 | | |
| |||
7069 | 7084 | | |
7070 | 7085 | | |
7071 | 7086 | | |
7072 | | - | |
| 7087 | + | |
0 commit comments