When investigating an issue, developers often examine issues that occur in parallel. Issues rarely occur in a vacuum, and you can often trace two or more issues back to the same root cause, or gain context for one issue by examining another. For example, you may have multiple issues that occur on the same page, result from the same server failure, or always occur one after the other. Furthermore, sometimes one issue is caused by another, and fixing one may fully or partially resolve the other.
To accommodate this flow, we’ve added the Correlated Issues tab. As the name suggests, this tab identifies issues with similar properties to the issue you’re examining. Good developers spend a lot of time working out whether two or more issues are related. The Correlated Issues tab eliminates this guesswork and gets your team that much closer to resolving the issue.
Noibu considers two issues correlated if they meet at least one of the following criteria:
- The issues occur on the same URL. This may indicate the two issues stem from the same faulty code.
- Users experience the issues at similar times. This may indicate the two issues stem from a problem in the same flow or process, or that one issue causes the other.
- The issues have similar error signatures. This may indicate the two issues are the same, but Noibu’s error signature algorithm falsely separated them.
Click on an error signature to open the issue in a new tab.
Learn more about other tabs in the Issue details page: Overview, User Impact, Developer, and Sessions.