Webinar: Continuous Code Improvement Series | How to Improve with AI-Assisted Workflows Register Here Today!
September 22nd, 2020 • By Gabriella Papp
Chances are you have multiple incoming occurrences in your Rollbar projects, grouped into items, appearing in your Item list, one after another. You also start to receive notifications pouring in your inbox. Now, you might as well keep your incoming items organized and clean by Rollbar’s useful options of:
This way you can make sure your item list is transparent, you will not be spammed by irrelevant notifications, provide clear visibility for your teams who manage the same project by appropriately triaging your errors and setting up the relevant severity level and status, to speed up the process of debugging, making sure everyone focuses their attention on the relevant things!
At Rollbar, we offer the chance to assign 3 statuses for your items: Active, Resolved, Muted.
All items start as active. Active means that the error is present and on-going and it requires your attention. It could represent a bug that has not yet been fixed or an intermittent ongoing backend issue.
When you believe your item is fixed or if you want to be notified if the bug re-appears you can mark it as Resolved. If possible you should include the version in which the item is fixed for future reference, as it will prevent it from being reactivated fore you deploy the new code version. This way you can also prevent your items from being reactivated by clients that are still running the old code.
If you consider an item as a non-issue for the time or currently don’t want to work on it, you can set it to Muted. Errors that currently aren’t worth investigating can be set to Muted, making sure they stay out of sight. Muted items are still searchable and can be indexed.
Update your item statuses
There are many ways to update item statuses, you can:
All Rollbar Items have severity levels. Properly setting up your severity level can reduce the noise in your Items/Dashboard/Versions view and your notifications and also reduce alert fatigue. There are 5 levels:
The default severity level for all unhandled items is Error, which you can change based on your system of prioritization. You can easily change the severity levels in the UI manually. Severity levels can be used as criteria for notification rules. It is useful if you only want to receive notifications about a certain level of bugs. It can also be used as a filter in RQL or the Item/Dashboard/Versions view, so you can manage the visibility of your items.
Check out our Docs to get more details on how to change your item statuses!