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.

[alert-conditions]

ALL or ANY

When setting up an alert's conditions, your first step is to decide whether the alert should fire when ALL conditions are met, or when ANY conditions are met. An alert that only fires when ALL conditions are met describes a specific scenario, which may mean the alert fires infrequently. On the other hand, alerts that fire when ANY of the selected conditions are met should be used to cast a wide net to receive regular, high-level updates.

Conditions & Variations

You can set up an alert to consider any of the conditions below. Several conditions have multiple variations to highlight specific circumstances.

• State
  • An issue's state is X (select one or multiple states)
  • An issue's state is not X (select one or multiple states)
• Insight tags
  • An issue's insight tags include X (You can select multiple insight tags, and set the condition to look for issues with ALL or ANY of the tags selected.)
  • An issues insight tags do not include X
• Browser
  • The issue occurs on ALL or ANY of the selected browsers
  • The issue does not occur on ALL or ANY of the selected browsers
• Operating system
  • The issue occurs on ALL or ANY of the selected operating systems
  • The issue does not occur on ALL or ANY of the selected operating systems
• Created at
  • The issue was created with the past X days.
• Last seen
  • The issue was last seen by a user within the last X days
•  Occurrences
  • Occurrences are greater than X in the last 1, 7, 14, 30, or 90 days
  • Occurrences are less than X in the last 1, 7, 14, 30, or 90 days
• Sessions
  • Noibu has captured more than X sessions with the issue in the last 1, 7, 14, 30, or 90 days
  • Noibu has captured less than X sessions with the issue in the last 1, 7, 14, 30, or 90 days
• Annualized Revenue Loss
  • ARL is greater than $X in the last 1, 7, 14, 30, or 90 days
  • ARL is less than $X in the last 1, 7, 14, 30, or 90 days
• Error type
  • The error type Is ANY of the selected error types (JS, HTTP, GQL, Image)
  • The error type Is NOT ANY of the selected error types
• Error source
  • The error source Is ANY of the selected error sources 
  • The error type Is NOT ANY of the selected error sources
    • Learn more about Error Sources
• Page type
  • Page type(s) include ANY or ALL of the selected page types
  • Page type(s) DO NOT include ANY or ALL of the selected page types
    • Learn more about Page Types
• Http status code
  • HTTP code is ANY of the status codes entered (404, 503, etc.)
  • HTTP code is NOT ANY of the status codes entered

Examples

By mixing and matching conditions, you can create alerts that address countless issue variations. Consider the examples below:

• A new issue is created that includes the Stacktrace insight tag AND has more than 150 occurrences in the past day.
• An issue's state changes from In Progress to Closed-Ignore OR an issue's state changes from In Progress to Closed-Fixed.
• 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.

Learn more about How to Create an Alert.