Once your investigation is complete, you should understand the WHY and HOW of the error, and have a potential solution lined up. The process of actioning and deploying a fix varies depending on whether you're dealing with a first- or third-party error.
- First-party: Implement the fix yourself, or assign the task to a team member.
- Third-party: Submit a bug report to the vendor, and reach out for support.
Once a fix has been actioned and deployed, use Noibu to monitor changes and confirm that the fix has been effective.
- Review the Annualized Revenue Loss and Occurrences charts on the User Impact tab to verify that ARL and occurrences have tapered since the fix was implemented. Be sure to adjust the time period dropdown to pull data for an appropriate length of time.
- Monitor the Sessions tab to see if new sessions with the error appear after the fix is implemented.
Now that you've been through the four steps of the error-solving workflow, check our our Appendices for a list of tips on replicating errors.