Noibu offers a set of basic notifications that users can opt-in or -out of through their user profile in the Teammates module. These notifications are based on high-level conditions–when the checkout is down, when issues are assigned to the user, a weekly status update, etc. While these notifications are useful, they’re reliant on a predetermined set of factors and may not capture the needs of each company or individual using the Noibu platform.
Every eCommerce company prioritizes different metrics and needs notifications that accommodate these nuances, and we’re happy to announce the launch of a brand new module in the Noibu platform to meet this need: Alerts! Through the Alerts module, you can create custom alerts with nuanced conditions, descriptive names, and a curated list of recipients.
Note: The old notifications will be active until mid-October, at which time they'll be removed and all email notifications must be configured through the Alerts module. Visit our guide to Recommended Alerts to find out how to configure custom alerts that fill these roles.
Anatomy of an Alert
An alert has three main components: Conditions, Recipients, and Settings. To review the process of configuring an alert in detail, visit our guide to Creating an Alert.
Noibu triggers alerts based on changes in issue data, and you can customize each alert to fire based on a set of conditions. An alert can have as little as one condition–perhaps you want a notification every time an issue is created, regardless of the circumstance–but the real value of a custom alert comes into play when you combine several conditions to create a nuanced alert that describes a specific situation. When setting an alert’s conditions you can decide whether the alert should fire when ALL conditions are met or when ANY conditions are met, depending on how wide of a net you want to cast.
An alert can consider any combination of the conditions below:
- Issue states
- Insight tags
- Operating system
- Created at date
- Last seen date
- Occurrence rates
- Sessions captured
- Annualized Revenue Loss (ARL)
- Error type
- Error source
- Page type
- HTTP status code
Several conditions have multiple variations to highlight specific circumstances. For example, you can configure an alert to fire when an issues state is X, or when an issue’s state is not X. For a complete breakdown of conditions and their variations, visit our guide to Alert Conditions.
By mixing and matching conditions, you can create alerts that address countless issue variations. Consider the examples below:
- An issue includes the Stacktrace insight tag AND has more than 150 occurrences in the past day.
- An issue's state occurs on the Chrome browser but does not occur on Android OS.
- An issue's state is In Progress AND has more than 100 sessions in the past 7 days AND ARL is greater than $10,000.
*Please note that while you can combine conditions however you like, each alert can only have one of each condition. For example, you can’t set an alert to fire when ARL is greater than $1000 in the last day and when ARL is greater than $10,000 in the last day.
When configuring a new alert, you can select users to receive the alert by selecting names from the dropdown provided. Selected users will receive the alert via email at the address associated to their Noibu account.
You can also set your alert to post updates to a designated Slack channel. If you’ve already configured your Slack webhook, this will happen by default. If not, the form will prompt you to set up the integration. This, of course, is optional.
Finally, you must configure each alerts settings. Here, you’ll give the alert a descriptive name and assign it one of three urgency markers: Low: Notice alert, Medium: Warning alert, or High: Critical alert. The alert’s urgency affects how it appears in your email inbox and on Slack, and helps you to know if an issue needs your immediate attention, or if the problem can wait.
The Alerts Dashboard
Opening the Alerts module brings you to the alerts dashboard, where you’ll see a list of your active alerts. From here, you can see each alert’s urgency–signified by the colour of the bug icon–its name, and when it was last triggered. There’s no limit to the number of alerts you can create, and you can toggle the index to show 10, 20, or 50 alerts per page.
You can also access a host of actions for each alert. At any time, you can Edit an Alert to change its conditions, recipients, or settings. If you’re creating a new alert that’s similar to an existing alert, Duplicate the Alert and make changes from there. Finally, if an alert goes out of commission, you can Delete the Alert to remove it from the Noibu console.
The Alert Profile
Click on an alert’s name to open its profile. Here, you’ll see a list of issues that have met the alerts conditions, with links to investigate each issue further. The profile also lists the alert’s conditions and a collection of high-level details, including when the issue was last triggered and last modified.