amazonq: reported customization telemetry can be wrong
Opened this issue · 0 comments
ege0zcan commented
Problem
See: #5362 (comment). The current way of recording telemetry events that contain customization field can lead to wrong telemetry being recorded.
The current logic seems to be getting the active customization at the time of an event (e.g interact with message) and as explained in the linked comment, this can lead to wrong metrics when a customer selects a customization after a message has been received and goes back to interact with that message
System details (run AWS: About and/or Amazon Q: About)
n/a