Default notifications
When configuring Continuous testing, you can define notifications for the conducted measurements. These notifications serve to alert you if actions or measurements deviate from expected behavior. There are four default notifications:
- Login Failure: This notification triggers when a virtual user is unable to log in to the configured environment (not applicable to the "desktop" connector).
- Login Time: This notification checks if the login time exceeds the configured threshold. If this occurs, an event is generated, and depending on the configuration, an email may be sent.
- Latency: This notification checks if the measured latency exceeds the configured threshold. If so, an event is generated, and based on configurations, an email may be dispatched.
- Application Failure: This notification triggers an event whenever an application fails to start.
Application notifications
You can manually add application notifications and select the specific applications or measurements to monitor. You can then define the threshold manually. Whenever a measurement exceeds the defined threshold, an event is generated. As illustrated in the screenshot, you can configure email notifications to be sent when a measurement exceeds a specific number of occurrences within a specified time frame.
Email notifications
Starting from Login Enterprise 5.9, email notifications for Continuous Tests are enhanced. By default, we now include the last 5 measurements when thresholds are exceeded.
If there are fewer than 5 measurements available, the email will indicate the actual number present. If there are no previous measurements (for example, because the test run had only started), this section will not be displayed.
To configure email notifications, you need to enable the email option for the measurements you want to stay up-to-date with. You can add email notifications to each measurement individually by selecting the 'letter' icon.
This will present you with two text fields and a switch.
You can define when you want to receive emails. This feature is designed to prevent you from being spammed whenever a spike occurs, giving you the ability to decide whether behavior is a fluke or a consistent issue. In the example provided, it is stated that when the measurement crosses the defined thresholds more than five times in one hour, it will send you an email.
An email typically looks like this:
In the title, it states which environment and which measurement or application went over the threshold. In the email, you can find details about the threshold it exceeded (as configured). It also includes information about the environment, the threshold time measured, and the last five measurements, along with a remark indicating the percentage over the threshold.
Global notifications
Global notifications can notify you of such scenarios as disabled accounts or launchers going offline. To configure global notifications:
1. In the Login Enterprise sidebar menu, navigate to Other > External notifications.
2. In External notifications, look for Global notifications.
In Global notifications, you can configure the following settings:
- Account is disabled: This notification triggers when a user account is used but fails to become active. If this occurs a specified number of times within a specified timeframe, an email notification will be sent containing the name(s) of the affected user account(s).
- Launcher went offline: This notification activates when a launcher fails to report and is marked as offline. If this happens more than a specified number of times within a specified timeframe, an email notification will be sent containing the name(s) of the affected launcher(s).
- Database connection error: This notification activates when the database connection fails a specified number of times within a specified timeframe. In this case, an email notification will be sent.
Email cool-down
After sending each email, there is a cool-down period in place to prevent excessive email notifications.
The cool-down period is as follows:
- It is identical to the timeframe configured, as demonstrated by the 60-minute example in the previous image.
- The minimum cool-down period is 10 minutes.
- The maximum cool-down period is 1 hour.