-
Notifications
You must be signed in to change notification settings - Fork 59
AXON-1710 add replay analytics #1449
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Co-authored-by: atlassian[bot] <40802693+atlassian[bot]@users.noreply.github.com>
Co-authored-by: atlassian[bot] <40802693+atlassian[bot]@users.noreply.github.com>
4edb5c9 to
000ccaf
Compare
…tlassian/atlascode into no-ticket-add-replay-analytics
|
The issue is ready for review. The below acceptance criteria have not been met:
|
|
The issue is ready for review. The below acceptance criteria have not been met:
Code Reviewer could not determine whether the following acceptance criteria have been met:
|
| } | ||
|
|
||
| // Emit analytics for replay completion | ||
| this._telemetryProvider.fireTelemetryEvent({ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔥 Code Bugs
The telemetry event is emitted before processing the replay response, which may not accurately reflect completion status if processRovoDevReplayResponse fails.
Details
📖 Explanation: Moving the telemetry emission after the replay processing would ensure the event only fires when the replay actually completes successfully, providing more accurate health monitoring data.
What Is This Change?
Problem statement: Sometimes, the replay behaves unusually. Ideally, we would see this quickly through our metrics vs waiting for users to report it.