AI Alert sensitivity is controlled by the alert persistence and the number of cumulative impacted unique devices. All sensitivity factors must be met before the AI alert fires. Each AI alert is assigned an alert severity (Info, Warning, Critical) that can help you determine the impact of alert condition. By default, all alerts fire with the Info severity until the thresholds for Warning or Critical severity are met.
- Persistence: The interval between when the issue starts and the time the alert is fired for the issue. If an issue continues for more than the Persistence interval, then the alert is fired if the other sensitivity settings are met. A Warning or Critical severity level can be assigned to the alert based on the number of minutes the alert exceeds the persistence interval.
- Cumulative Impacted Unique Devices: This control limits AI alert firing so an AI alert fires only after an issue impacts the specified cumulative number and percentage of unique devices within the root cause group. The root cause group is limited to the unique devices impacted by the alert.
Sensitivity Control Access
After selecting a metric, the sensitivity controls enable you to configure the sensitivity settings to optimize alerting to meet your delivery network performance standards and user experience levels.
Note: Only Admin users can update the AI alert sensitivity settings.
-
To navigate to the Sensitivity page, click Alert Config in the AI Alert dashboard.
-
If you want to monitor the custom metrics, click Metrics, select the specific custom metrics, and click Apply. By default, monitor the out-of-box metrics:
-
Avg Page Load Time
-
Avg Screen Load Time
-
Avg Network Request Duration
-
Network Request Failure
-
Avg Perceived Page Load Time
-
-
Configure Persistence and Cumulative Impacted Unique Devices.
- Persistence: The interval between when the issue starts and the time the alert is fired for the issue. If an issue continues for more than the Persistence interval, then the alert is fired if the other sensitivity settings are also met. Use the Persistence slider to set this sensitivity level. The higher the Persistence time, the less frequently AI alerts will fire.
Set the number of minutes required to exceed the Persistence interval for an alert to be labeled with a Warning or Critical severity level. The minimum number is 3 minutes.
- Cumulative Impacted Unique Devices: This control limits AI alert firing so an AI alert fires only after an issue impacts the specified cumulative number of unique devices and the percentage of devices within the dimensions of the root cause. The minimum number of devices is 5, while the percentage can be between 0% and 100%.
You can adjust the sensitivity of this control to prevent plays from the same device or a small number of devices from generating multiple AI alerts. For example, a unique device can generate multiple sessions, which could cause multiple AI alert conditions for the same device.
Setting a higher sensitivity level throttles the AI alert firing until more unique devices and a higher percentage are impacted. Setting extremely high settings can effectively disable AI alerting. Admins should try different sensitivity levels for each metric to determine which level works best for their system based on how granular the firing of the AI alert should be.
Set the number and percentage of Cumulative Impacted Unique Devices required within the root cause group for an alert to be labeled with a Warning or Critical severity.
- Persistence: The interval between when the issue starts and the time the alert is fired for the issue. If an issue continues for more than the Persistence interval, then the alert is fired if the other sensitivity settings are also met. Use the Persistence slider to set this sensitivity level. The higher the Persistence time, the less frequently AI alerts will fire.
-
(Optional) Restore default settings.
When the AI alerts feature is enabled for the first time, the sensitivity controls are set to default values. Users may want to reset the parameters back to their default values after trying out different settings for a while. The Restore Default button allows a user to do that easily.
-
To apply the sensitivity controls and severity levels, click Save.
Sensitivity Change Logs
To display all the "saved" sensitivity updates, click Sensitivity Change Logs.
The Sensitivity Logs page displays the information for each change:
- Email address of the user who changed the sensitivity parameters
- Time when the updated parameters were saved
- Metric for which sensitivity was adjusted
- Changes to Persistence and Cumulative Impacted Unique Devices settings