@cryptotaxi247 / netdata
Code Commits Issues Pulls Sessions CI/CD
master
master
md 113 lines 5.14 KB
Rendered Raw
1 # Creating Alerts with Netdata Alerts Configuration Manager
2
3 The **Netdata Alerts Configuration Manager** lets you create and fine-tune alerts directly from the Netdata Cloud Dashboard using a visual UI wizard.
4
5 :::tip
6
7 **Want AI to handle the configuration for you?** [Alerts Automation](/docs/netdata-ai/alerts-automation/alerts-automation.md) uses AI to suggest alerts, generate the configuration, and test it against historical data — so you can validate thresholds before deployment without writing any configuration manually.
8
9 :::
10
11 :::info
12
13 To use this feature, you'll need a Netdata Cloud paid plan. [View subscription plans](https://www.netdata.cloud/pricing/)
14
15 :::
16
17 ## Creating Alerts: Quick Guide
18
19 ```mermaid
20 flowchart LR
21 A("Navigate to Metrics") -->|"Find Chart"| B("Click Alert Icon")
22 B -->|"Select Add Alert"| C("Set Thresholds")
23 C -->|"Configure Options"| D("Submit to Nodes")
24
25 %% Style definitions
26 classDef alert fill:#ffeb3b,stroke:#000000,stroke-width:3px,color:#000000,font-size:18px
27 classDef neutral fill:#f9f9f9,stroke:#000000,stroke-width:3px,color:#000000,font-size:18px
28 classDef complete fill:#4caf50,stroke:#000000,stroke-width:3px,color:#000000,font-size:18px
29 classDef database fill:#2196F3,stroke:#000000,stroke-width:3px,color:#000000,font-size:18px
30
31 %% Apply styles
32 class A neutral
33 class B alert
34 class C database
35 class D complete
36 ```
37
38 ## Alert Detection Types
39
40 You can choose from different ways to trigger alerts based on your monitoring needs:
41
42 | Type | Description |
43 |---------------------|---------------------------------------------------------------------|
44 | **Standard** | Fires when a metric crosses a set value |
45 | **Metric Variance** | Fires based on variation in values over time |
46 | **Anomaly Rate** | Fires when Netdata's ML-derived anomaly rate exceeds a set threshold |
47
48 For **Anomaly Rate** alerts, the threshold is the ML anomaly rate on a `0`-`100` scale, where higher values indicate more anomalous behavior. See [ML-powered anomaly detection](/docs/ml-ai/ml-anomaly-detection/ml-anomaly-detection.md#creating-anomaly-based-health-alerts) and the [health reference](/src/health/REFERENCE.md) for more details on configuring anomaly-rate checks.
49
50 Choose the type that best suits the behavior you want to monitor.
51
52 ## Metrics Lookup & Filters
53
54 Click **Show advanced** in the Alert Configuration Manager to access these options.
55
56 ### Metrics Lookup
57
58 You can define how Netdata should query the data before triggering an alert:
59
60 | Parameter | Description |
61 |--------------|----------------------------------------------------------------------|
62 | `method` | How values are aggregated (`avg`, `min`, `max`, etc.) |
63 | `duration` | Time window used for the check |
64 | `dimensions` | Which metric dimensions to include |
65 | `options` | Modify how values are interpreted (e.g., `percentage`, `absolute`) |
66
67 ### Filtering Targets
68
69 You can limit your alert to specific infrastructure components:
70
71 - Hosts
72 - Nodes
73 - Instances
74 - Operating systems
75 - Chart labels
76
77 ### Formulas
78
79 You can use a custom formula to manipulate values before comparing against thresholds.
80
81 Example:
82
83 ```txt
84 (metric1 - metric2) / 100
85 ```
86
87 ## Defining Alert Conditions
88
89 You control how and when alerts are triggered, escalated, or resolved:
90
91 | Setting | Purpose |
92 |------------------------------|------------------------------------------------------------------|
93 | **Thresholds** | Define values for `warning` and `critical` states |
94 | **Recovery thresholds** | Set when the alert should downgrade or clear |
95 | **Check interval** | How often the alert check runs (e.g., every 10 seconds) |
96 | **Notification delay** | Delay before sending notifications for state changes |
97 | **Repeat notifications** | How often to resend an alert if the issue persists (Agent only) |
98 | **Notification recipients** | Define who gets alerted (Agent only) |
99 | **Custom exec script** | Run a custom shell script when an alert triggers |
100
101 ## Naming and Documentation
102
103 | Field | Description |
104 |-----------------|------------------------------------------------------|
105 | **Alert Name** | A unique name for the alert |
106 | **Description** | What the alert does, in one or two sentences |
107 | **Summary** | Optional: a short summary for display in dashboards |
108
109 ## Final Notes
110
111 - You can apply alert definitions to **Parent Agents** or **Standalone Child Agents**
112 - If you need help writing custom alerts, check the [full alert reference](/src/health/REFERENCE.md)
113 - To create alerts using natural language instead of this manual wizard, see [Alerts Automation](/docs/netdata-ai/alerts-automation/alerts-automation.md)