Skip to content

Conversation

@bwieger-atlassian-com
Copy link
Collaborator

@bwieger-atlassian-com bwieger-atlassian-com commented Dec 30, 2025

What Is This Change?

  • Add a replay analtyic event so that we can monitor the health of the replay API in BBY mode

Problem statement: Sometimes, the replay behaves unusually. Ideally, we would see this quickly through our metrics vs waiting for users to report it.

Co-authored-by: atlassian[bot] <40802693+atlassian[bot]@users.noreply.github.com>
Co-authored-by: atlassian[bot] <40802693+atlassian[bot]@users.noreply.github.com>
@bhorai-atl bhorai-atl force-pushed the no-ticket-add-replay-analytics branch from 4edb5c9 to 000ccaf Compare December 31, 2025 11:09
@bwieger-atlassian-com bwieger-atlassian-com changed the title no-ticket add replay analytics AXON-1710 add replay analytics Jan 7, 2026
@atlassian
Copy link
Contributor

atlassian bot commented Jan 7, 2026

The issue is ready for review.

The below acceptance criteria have not been met:

  • ❌ Investigate the root cause of the blank screen issue in the chat session.
  • ❌ Resolve the blank screen issue to prevent it from occurring again.
  • ❌ Check the extension installation process as a potential cause.
  • ❌ Check workspace ID issues as a potential cause.

Check Jira issue

@atlassian
Copy link
Contributor

atlassian bot commented Jan 7, 2026

The issue is ready for review.

The below acceptance criteria have not been met:

  • ❌ Resolve the blank screen issue to prevent it from occurring again.

Code Reviewer could not determine whether the following acceptance criteria have been met:

  • Investigate the root cause of the blank screen issue in the chat session.
  • Check the extension installation process as a potential cause.
  • Check workspace ID issues as a potential cause.

Check Jira issue

}

// Emit analytics for replay completion
this._telemetryProvider.fireTelemetryEvent({
Copy link
Contributor

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.

Uses AI. Verify results. Give Feedback

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants