| Keyword | Definition |
|---|---|
| Alert | A monitoring rule is triggered when a system metric crosses a defined threshold. Users create alerts in Pulse to monitor critical cluster resources, including CPU, memory, database health, HDFS, and Hadoop service level metrics. Alerts notify users when thresholds are exceeded, allowing them to take timely action. |
| Alert Notification | A message is sent to a configured person or team when an alert is triggered. Pulse allows users to configure notifications to individuals or teams through multiple channels. This ensures the right stakeholders are informed immediately when an issue arises. |
| Alert Action | An automated playbook is executed when an alert is triggered to restore normal operation. Pulse executes alert actions automatically to remediate issues, reducing manual intervention and minimizing downtime. Users can configure these actions based on their requirements. |
| Incident | An Incident is created when an alert occurs repeatedly over a defined threshold or duration. In Pulse, incidents track repeated alerts over time. Users can view all details, including occurrence count, timestamps, severity, and triggering alert, to understand and resolve problems efficiently. Incidents are categorized as Critical, High-Priority, Medium, and Low based on the impact they make. |
| Forecasting Alert | Predicts future metric behavior using trained models and triggers alerts in advance when forecasted values exceed defined thresholds. |
Was this page helpful?