@cryptotaxi247 / netdata-1
Code Commits Issues Pulls Sessions CI/CD
master
master
md 161 lines 8.18 KB
Rendered Raw
1 # Alerts Tab
2
3 Netdata provides hundreds of pre-configured health alerts to notify you when an anomaly or performance issue affects your node or its applications.
4
5 ## Raised Alerts Tab
6
7 The **Raised Alerts** tab shows all current alerts in your Room that are in a **warning** or **critical** state.
8
9 ### Alert Table Overview
10
11 The table provides key details about each active alert:
12
13 | Column | Description |
14 |----------------------|----------------------------------------------------------------------|
15 | **Alert Name** | The name of the alert; click to view alert details. |
16 | **Status** | Current state: Warning or Critical. |
17 | **Class** | The alert's class (e.g., Latency, Utilization). |
18 | **Type & Component** | The system type and component involved. |
19 | **Role** | The notification role assigned to the alert. |
20 | **Node Name** | The node where the alert was triggered. |
21 | **Silencing Rule** | Whether silencing rules are applied. |
22 | **Actions** | Options to create silencing rules or ask Netdata Assistant for help. |
23
24 Use the **gear icon** (top right) to control which columns are visible. Sort alerts by clicking on column headers.
25
26 ## Filtering Alerts
27
28 Filter the alert list using the right-hand bar:
29
30 | Filter Option | Purpose |
31 |----------------------------|----------------------------------------------------------------------------------|
32 | **Alert Status** | Filter by status (Warning, Critical). |
33 | **Alert Class** | Filter by class (e.g., Latency, Utilization). |
34 | **Alert Type & Component** | Filter by alert type (e.g., System, Web Server) and component (e.g., CPU, Disk). |
35 | **Alert Role** | Filter by the notification role (e.g., Sysadmin, Webmaster). |
36 | **Host Labels** | Filter by host labels (e.g., `_cloud_instance_region=us-east-1`). |
37 | **Node Status** | Filter by node availability (Live, Offline). |
38 | **Netdata Version** | Filter by the Netdata version. |
39 | **Nodes** | Filter by specific nodes. |
40
41
42 ## Viewing Alert Details
43
44 Click on an alert name to open the **alert details page**, which provides:
45
46 | Section | Description |
47 |------------------------------|--------------------------------------------------------------|
48 | **Latest / Triggered Time** | Shows when the alert was last triggered. |
49 | **Description** | Includes a detailed explanation of the alert. |
50 | **Netdata Advisor Link** | Links to related Netdata Advisor guidance. |
51 | **Triggered Chart Snapshot** | Visualizes the chart at the alert’s trigger time. |
52 | **Alert Metadata** | Shows node name, chart instance, type, component, and class. |
53 | **Configuration** | Displays the alert's configuration parameters. |
54 | **Instance Values** | Provides node instance details. |
55
56 At the bottom of this page, click **View alert page** to open a dynamic view where you can:
57
58 - Run metric correlations.
59 - Navigate to the specific node’s chart that triggered the alert.
60
61 ## Silencing Alerts
62
63 In the **Raised Alerts** tab:
64
65 - The **Silencing column** shows whether a silencing rule exists for an alert.
66 - The **Actions column** allows you to:
67 - Create a new [silencing rule](/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/centralized-cloud-notifications-reference.md#alert-notification-silencing-rules).
68 - Ask AI to troubleshoot the alert.
69
70 :::note
71
72 Cloud alert silencing rules are available on Netdata Cloud for Community and Paid plans (anonymous access cannot create rules).
73
74 Users can also silence or disable alerts at the Agent level by editing alert configuration. For example, set `to: silent` in the alert's `health.d/*.conf` file and run `sudo netdatacli reload-health` to stop notifications, or use `enabled alarms = !alert_name *` in `netdata.conf` to exclude specific alerts entirely (requires restarting the Agent). See [manual configuration](/src/health/REFERENCE.md) for step-by-step instructions.
75
76 :::
77
78 ## Creating and Tuning Alerts
79
80 From the Alerts tab, you can create new alerts or tune existing ones:
81
82 - **[Alerts Automation](/docs/netdata-ai/alerts-automation/alerts-automation.md)** — Describe what you want in plain English and let AI generate the alert configuration, including thresholds and tuning parameters
83 - **[Alerts Configuration Manager](/docs/alerts-and-notifications/creating-alerts-with-netdata-alerts-configuration-manager.md)** — Visual UI wizard for manual alert creation and fine-tuning
84 - **[Manual configuration](/src/health/REFERENCE.md)** — Edit `health.d/*.conf` files directly for full control
85
86 :::note
87
88 **Alerts Automation** and the **Alerts Configuration Manager** require a Netdata Cloud paid plan.
89 See [Netdata OSS limitations and feature availability](/docs/netdata-oss-limitations.md) to confirm plan requirements.
90 Community plan users can still create and tune alerts using [manual configuration](/src/health/REFERENCE.md).
91
92 :::
93
94 ## Alert Configurations Tab
95
96 The **Alert Configurations** tab shows the configuration of all running alerts in your Room.
97
98 :::note
99
100 "Running alerts" are alerts attached to metrics that are actively being collected. Pre-configured alerts that do not match your setup may not appear here.
101
102 :::
103
104 ### Configuration Table Overview
105
106 | Column | Description |
107 |--------------------|-----------------------------------------------------|
108 | **Alert Name** | The name of the alert; click to view configuration. |
109 | **Node Name** | The node where this configuration applies. |
110 | **Status** | Whether the alert is active or silenced. |
111 | **Silencing Rule** | Indicates if silencing rules are applied. |
112 | **Actions** | Explore configuration or ask the Netdata Assistant. |
113
114 Use the **gear icon** to adjust which columns are displayed.
115
116 ## Viewing Alert Configuration
117
118 From the **Actions column**, click **Show Configuration** to:
119
120 | Action | Outcome |
121 |---------------------|--------------------------------------------------------------|
122 | **Explore by Node** | View configurations split by node. |
123 | **View Alert Page** | See full alert details, including configuration and history. |
124
125 This allows you to investigate:
126
127 - When the alert last triggered.
128 - All configuration parameters per node.
129
130 ## Alert Lifecycle Diagram
131
132 ```mermaid
133 flowchart TD
134 A("Metric Collection") --> B("Alert Evaluation")
135 B --> C("Condition Met?")
136 C -->|"Yes"| D("Trigger Alert")
137 C -->|"No"| J("No Alert Triggered")
138 D --> E("Alert in Raised Alerts Tab")
139 E --> F("Details and Chart Snapshot")
140 E --> G("Apply Silencing Rule")
141 F --> H("Explore Metrics<br/>Run Correlations")
142 G --> I("No Notification Sent")
143
144 %% Style definitions
145 classDef alert fill:#ffeb3b,stroke:#000000,stroke-width:3px,color:#000000,font-size:14px
146 classDef neutral fill:#f9f9f9,stroke:#000000,stroke-width:3px,color:#000000,font-size:14px
147 classDef complete fill:#4caf50,stroke:#000000,stroke-width:3px,color:#000000,font-size:14px
148 classDef database fill:#2196F3,stroke:#000000,stroke-width:3px,color:#000000,font-size:14px
149
150 %% Apply styles
151 class A,D alert
152 class B,C,E neutral
153 class F,H,J complete
154 class G,I database
155 ```
156
157 :::tip
158
159 The diagram above illustrates the flow of alert detection and management, from metric collection to alert evaluation, triggering, and optional silencing.
160
161 :::