Engineers at eCommerce companies need an easy way to correlate code deployments with new issues. If a code change results in one or more user-impacting issues that block conversion, engineers want to know about it as soon as possible so they can modify the code or revert the change altogether. Noibu collects enough issue and session data to filter for issues created after a deployment, but this is a highly manual process that requires a lot of guesswork and dot-connecting.
We understand the need for reliable release monitoring, and we’re excited to announce the addition of event logging, a new function that places releases and resulting issues on a simple timeline. This update introduces a new method of tracking and prioritizing issues, so to keep things organized, we’ve created a new page to house this functionality: Events.
Anatomy of the Events Page
The Events page keeps a running list of each release deployed, and whether the deployment succeeded or failed; each issue or cluster of issues created; and each time issue conditions triggered an alert email. The logs are organized by date and sorted by timestamp, which helps an engineer draw connections between code deployments and resulting issues. For example, if new code deploys at 9:45am, and three new issues appear at 9:47am, chances are the new issues are related to the release.
Sometimes, you’ll see two or more event logs for the same release back-to-back. This indicates when multiple updates are deployed at the same time. To group entries from the same release and keep release entries visually distinct, each release is assigned a random colour next to its version code.
The Events page serves as a high-level summary of activity in your domain, and you can click the View buttons in each log item to access more information about a specific release or issue.
Setting Up Release Tracking
By default, the Events page will only display issue and alert events. However, a client can set up a webhook with their CI/CD tool to pass release events to Noibu. Visit our guides on setting up Release Monitoring for more information on how to configure the webhook.