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.
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.
In order to pull and display release information on the Events page, you must configure a post-release webhook in your deployment pipeline to notify Noibu when you are shipping code. This can work for most CI/CD tools, provided it can send an HTTP request and retrieve release data. For assistance, consult our guides on configuring webhooks through the methods below:
All methods require you to Retrieve your Domain ID.