Enable or disable anomaly alert settings

How to enable or disable anomaly alerts

Understanding alerts

In Site24x7, there are two different types of alerts in anomaly detection:
  1. Status change alert: Triggered when there is a change in the monitor status, such as Trouble, Critical, or Down.
  2. Anomaly alert: Triggered when irregular patterns are detected by our machine learning (ML) models in monitored data. 
Note
An anomaly alert is sent only when there is a Confirmed anomaly.
In Threshold Configurations, if you have configured your Threshold Type as Zia-based Threshold, Zia will change the status of a monitor based on the severity of the anomaly. 
For example, for the above configurations in a server monitor where the CPU utilization is typically around 35%, a sudden spike to 90% prompts Zia to evaluate the severity of the anomaly. 
  1. If the anomaly is classified as Info, then there is no status change. 
  2. If the anomaly is classified as Likely, then the status is changed to Trouble.
  3. If the anomaly is classified as Confirmed, then the status is changed to Critical.

Disabling anomaly alerts will stop the alert mails for anomaly detection. However, users will continue to receive alert mails for a monitor status change caused by anomalies. 

How to enable or disable anomaly alerts 

Enable or disable anomaly alerts to suit your monitoring needs by toggling Yes or No in the following path:‌  
Admin > Configuration Profile > Anomaly Settings > Yes/No.

Note
  1. Anomaly alert settings are enabled by default.
  1. When anomaly alerts are disabled, the users will no longer receive an anomaly alert. However, if there is a status change triggered by the anomaly alert, then they will continue to receive the alert notifications.



    • Related Articles

    • Troubleshooting steps for No anomaly triggered

      Why are anomaly alerts not triggered? If you are not receiving anomaly alerts, it means that the model was not able to recognize a behavior as an anomaly. Site24x7's AI-powered Zia framework is the underlying mechanism of anomaly detection. The ML ...
    • Different cases considered for domain scoring and severity benchmarking in Anomaly Dashboard.

      The following methodologies (in the same order specified below) are usually considered for the final score determination: 1. Another attribute of the same monitor detected as anomalous It facilitates the increase of the overall anomaly score if an ...
    • How to disable alerts for containers in bulk?

      Alerts for docker containers can be muted in bulk or via Configuration Rules.  Ensure to have Linux agent 17.5.7 and above to enable the bulk option. Using Bulk Actions: Log in to Site24x7 and go to Admin > Inventory > Bulk Action. Click on Suppress ...
    • How to configure alerts to be sent to different users for different servers

      Different server groups have different use cases and eventually, different directly responsible individuals (DRIs). An alert from a server should be directed to the proper DRI to ensure prompt action and minimized alert fatigue. With Site24x7, you ...
    • Disable alerts for a plugin if the parent server is down

      If a plugin monitor's parent server goes down, you can choose to exclude additional alerts from the plugin monitor. This way, you won’t receive alerts when the plugin monitor goes down as a result of the parent server being unavailable. To enable ...