The alerts module is a powerful feature that allows users to create custom rules on single or multiple metrics, helping to detect anomalies or potential issues within their application environment. By defining thresholds for specific metrics whether critical, major, or warning, users can ensure their systems operate within expected performance parameters. The alert module continuously monitors these metrics during a specified alert interval and triggers an alert if the values cross predefined thresholds. When an alert is triggered, the system can perform a variety of predefined actions, such as executing scripts, generating thread dumps or TCP dumps, and sending notifications to stakeholders. The alerts module also leverages algorithms like outlier detection, forecasting, and anomaly detection to predict or identify abnormal behaviors in the system. This enables proactive management and ensures timely responses to issues, ultimately minimizing downtime and helping maintain optimal application performance.

Alert

The Alert homepage contains the following details:

Search: Use the search option to filter down to a particular alert by entering a string. The entered string searches for its corresponding match in all the columns present in the alert table.

Alert Category: Using this dropdown, you can view all the current and past alerts. Following options are available:

• Active: Select this to view all the alerts that are currently active. These alerts display the alert rules that have been triggered because the metric values are not within the expected range
• History: Select this to view those alerts that were generated in the past and are now not active i.e. the metric value is back within the expected range.

Grouping: Group the generated alerts based on their subject, such as by tier, server, instance, or specific identifiers like Incident ID. The grouping is hierarchical: at level 1, you typically see Tiers, at level 2, Servers, and at level 3, Instances. This structure allows you to check the frequency and number of alerts for each entity, helping you quickly identify which entities need your immediate attention. Grouping is also done on the basis of incident ID <need to see how this is done in the UI and add the correlation with AIOps>

Status: Select the status from All, Critical, Major, or Minor to filter the alerts accordingly.

The alerts table has the following fields that provides in depth details about the generated alerts:

• Node: The monitored entity (for e.g. server, process or instance) on which the alert is generated. 
• Severity: Intensity of the alert - Critical/Major/Minor.
• Ack: Indicates whether this alert is seen and acknowledged by the user.
• Rule Name: Name of the alert rule. You can view the rule by clicking the link.
• Alert Start Time: Time when the alert was started.
• Last Seen Ago: It is the last generated alert time.
• Alert Message: Alert message associated with the alert.
• Subject: The subject at which the alert is generated.
• Alert Value: The value at which the alert is generated. You can view the details in tabular format by clicking the link.
• Active id: All the generated alerts will be allocated and a unique id will be shown in Active id.

User can also perform additional operation by clicking on the following tab :

• Refresh Events: While you click the Refresh Event button , the newly generated alerts will be updated and displayed on the Alert window. It also changes the values in the Time Ago field according to the current time.
• Add Event Type: This option is used to filter overlays based on custom event types, which can be configured through the dashboard widget's overlay settings. Note that this option is only applicable when viewing historical alerts.
• Open AIOPS: This button will display the AIOps dashboard. "Group by ID" will only generate records for incidents created by AIOps. For example, users can see the AIOPS visualization of the generated alerts.
• Acknowledge: This feature allows you to confirm that you have seen the alert. You can acknowledge an alert by selecting the relevant records and clicking the Acknowledge button. This acknowledgment acts as an indicator that the generated alerts have been viewed by the relevant stakeholder.
  Note: This option is not applicable for historical data.
• Force Clear Event: The Force Clear Event feature is used to delete an event forcefully. To do this, the user must select the corresponding checkbox and then click on the Force Clear Event option.
  Note: This option is only applicable for Active Alerts.
• Open Graph: This option is used to open the corresponding graph for the particular alert on the dashboard. The user has to select the corresponding severity checkbox and then click on the Open Graph option.
• Download: You can download the alert events in Word, Excel, and PDF formats. Select a record and click the Download option.
• Column Filter: You can apply filters on each column by using the Column Filter button.
• Toggle Columns: You can show/hide the columns based on your requirements by using the Toggle Columns option.
• Setting: It has following settings in the window:
  1. Alert Configurations: Alert configuration involves the following subsections - Global Basic Configurations, Policy Configurations, Action Events (Action will be taken when the selected criteria are satisfied), and REST API Triggered Event Configurations.
  2. Alert Maintenance: Alert maintenance window configuration is required to disable alert generation at the time of the maintenance period or a scheduled downtime
• Rules list: Users can see all the alert rules.
• Action list: Users can check all the actions.

Note: By default, the UI displays all active sessions. To view the history of alerts, users need to select the "History" option from the drop-down menu.