Column | Description |
Name | Alert Name. |
Runtime | Integration Server, Universal Messaging, or Terracotta. |
Action | The icon activates the configuration view for the alert. |
Field | Description |
Threshold | The KPI's boundary values. When the value of the KPI is outside the range that is specified by these boundary values, the alert is raised. You can configure the threshold values of critical alerts by adjusting the ends of the red line. You can configure the threshold values of warning alerts by adjusting the ends of the orange line. You can configure the threshold values of information alerts by adjusting the ends of the blue line. Note: The Threshold field is read-only for KPIs that monitor the availability of a runtime instance. |
Runtime | Integration Server, Universal Messaging, or Terracotta. |
Summary | Summary of the alert. |
Interval | The scrape interval. The scrape interval is the frequency at which the system collects the data. The scrape interval is 60 seconds for all rules. Read-only. Note: The alert does not appear immediately when the corresponding rule violation occurs. The time delay from the actual time of the rule violation to the system alert is the following: up to 70 seconds for run-time availability rules of critical severity up to 420 seconds for run-time availability rules of information severity up to 180 seconds for the rest of the rules The system will not send an alert if the rule violation condition is resolved during the corresponding delay period. |
Email on alert | Email of the user who will receive the alerts. Note: The email is used for all rules. In case there are alerts, the system sends emails once every 10 minutes. The email alerts always display UTC time. To configure more than one email, use comma-separated values. |