-
Notifications
You must be signed in to change notification settings - Fork 27
Mute error occurrences #130
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
Conversation
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.
Looks good to me! I added some comments but all of them minor.
My only worry is that I don't know if it is better to avoid sending telemetry events, or send them with a muted: true
information.
Aside from the occurrence itself, the new occurrence telemetry event now also includes the error and the muted flag so users can choose wether the occurrence should be reported or not.
This makes sense. I've updated the code so the I've also updated the documentation to reflect this changes. |
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.
🚀 🤌
This pull request adds a new
muted
field to errors. Noisy errors can be muted in the UI so integrations and notifications can ignore them as well.In the end I decided to use the mute instead of silence as I think that mute and unmute are fairly commonly understood terms.
This is an addition to the capability of ignoring errors that we already have, and enables the possibility of tracking error occurrences but don't notify them. Closes #117
New mute action in the error detail page:

Mute and unmute actions in the dashboard page
