summaryrefslogtreecommitdiffstats
path: root/docs/monitor/view-active-alerts.md
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2023-10-17 09:30:23 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2023-10-17 09:30:23 +0000
commit517a443636daa1e8085cb4e5325524a54e8a8fd7 (patch)
tree5352109cc7cd5122274ab0cfc1f887b685f04edf /docs/monitor/view-active-alerts.md
parentReleasing debian version 1.42.4-1. (diff)
downloadnetdata-517a443636daa1e8085cb4e5325524a54e8a8fd7.tar.xz
netdata-517a443636daa1e8085cb4e5325524a54e8a8fd7.zip
Merging upstream version 1.43.0.
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to '')
-rw-r--r--docs/monitor/view-active-alerts.md (renamed from docs/monitor/view-active-alarms.md)22
1 files changed, 11 insertions, 11 deletions
diff --git a/docs/monitor/view-active-alarms.md b/docs/monitor/view-active-alerts.md
index cc6a2d3a1..14b1663d6 100644
--- a/docs/monitor/view-active-alarms.md
+++ b/docs/monitor/view-active-alerts.md
@@ -43,28 +43,28 @@ At the bottom of the panel you can click the green button "View dedicated alert
<!--
## Local Netdata Agent dashboard
-Find the alarms icon ![Alarms
+Find the alerts icon ![Alerts
icon](https://raw.githubusercontent.com/netdata/netdata-ui/98e31799c1ec0983f433537ff16d2ac2b0d994aa/src/components/icon/assets/alarm.svg)
-in the top navigation to bring up a modal that shows currently raised alarms, all running alarms, and the alarms log.
-Here is an example of a raised `system.cpu` alarm, followed by the full list and alarm log:
+in the top navigation to bring up a modal that shows currently raised alerts, all running alerts, and the alerts log.
+Here is an example of a raised `system.cpu` alert, followed by the full list and alert log:
-![Animated GIF of looking at raised alarms and the alarm
+![Animated GIF of looking at raised alerts and the alert
log](https://user-images.githubusercontent.com/1153921/80842482-8c289500-8bb6-11ea-9791-600cfdbe82ce.gif)
-And a static screenshot of the raised CPU alarm:
+And a static screenshot of the raised CPU alert:
![Screenshot of a raised system CPU
-alarm](https://user-images.githubusercontent.com/1153921/80842330-2dfbb200-8bb6-11ea-8147-3cd366eb0f37.png)
+alert](https://user-images.githubusercontent.com/1153921/80842330-2dfbb200-8bb6-11ea-8147-3cd366eb0f37.png)
-The alarm itself is named **system - cpu**, and its context is `system.cpu`. Beneath that is an auto-updating badge that
-shows the latest value of the chart that triggered the alarm.
+The alert itself is named **system - cpu**, and its context is `system.cpu`. Beneath that is an auto-updating badge that
+shows the latest value of the chart that triggered the alert.
With the three icons beneath that and the **role** designation, you can:
-1. Scroll to the chart associated with this raised alarm.
+1. Scroll to the chart associated with this raised alert.
2. Copy a link to the badge to your clipboard.
3. Copy the code to embed the badge onto another web page using an `<embed>` element.
-The table on the right-hand side displays information about the health entity that triggered the alarm, which you can
-use as a reference to [configure alarms](https://github.com/netdata/netdata/blob/master/health/REFERENCE.md).
+The table on the right-hand side displays information about the health entity that triggered the alert, which you can
+use as a reference to [configure alerts](https://github.com/netdata/netdata/blob/master/health/REFERENCE.md).
-->