Skip to content

Conversation

@teg-atlassian
Copy link
Contributor

@teg-atlassian teg-atlassian commented Feb 4, 2026

What Is This Change?

The volume of errors logged to Sentry is huge. To reduce that, in the is PR, we filter out certain exceptions not be sent to Sentry. These exceptions are thrown by the underlying VS Code instead of our own Atlascode.

The specific filters are taken by analyzing the data in an hour interval of reported errors

How Has This Been Tested?

Screenshot 2026-02-03 at 9 35 46 PM

Basic checks:

  • npm run lint
  • npm run test

Advanced checks:

  • If Atlassian employee & Bitbucket changes: did you test with DC in mind? See Instructions

Recommendations:

  • Update the CHANGELOG if making a user facing change

You don't have access to Rovo Dev Standard
Ask your organization admin to add you to Rovo Dev Standard.
More about code review errors

@teg-atlassian teg-atlassian changed the title add restriction to which exceptions to log to Sentry AXON-1856-Limiting-Error-Logging-Volume-To-Sentry Feb 4, 2026
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.

2 participants