docs edit (#18895)
Co-authored-by: Ilya Mashchenko <ilya@netdata.cloud>
Fotis Voutsas committed
Oct 30, 2024 at 12:39 UTC
b1c9385c707a88f0e911032e3736b1cff07f9f50
2 files changed
+10
-11
docs/netdata-agent/reload-health-configuration.md
deleted
-9
@@ -1,9 +0,0 @@
1
-# Reload health configuration
2
-
3
-## Unix systems
4
-
5
-No need to restart the Netdata Agent after modifying health configuration files (alerts). Use `netdatacli` to avoid metric collection gaps.
6
-
7
-```bash
8
-sudo netdatacli reload-health
9
-```
docs/netdata-agent/start-stop-restart.md
+10
-2
@@ -1,8 +1,8 @@
1
-# Start, stop, or restart the Netdata Agent
1
+# Service Control
2
3
The Netdata Agent automatically starts at boot after installation.
4
5
-> In most cases, you need to **restart the Netdata service** to apply changes to configuration files. [Health configuration](/docs/netdata-agent/reload-health-configuration.md) files, which define alerts, are an exception. They can be reloaded **without restarting** by using the `netdatacli` tool.
5
+> In most cases, you need to **restart the Netdata service** to apply changes to configuration files. Health configuration files, which define alerts, are an exception. They can be [reloaded](#reload-health) **without restarting**.
6
>
7
> Restarting the Netdata Agent will cause temporary gaps in your collected metrics. This occurs while the netdata process reinitializes its data collectors and database engine.
8
@@ -34,6 +34,14 @@ The Netdata Agent also comes with a [CLI tool](/src/cli/README.md) capable of pe
34
sudo netdatacli shutdown-agent
35
```
36
37
+### Reload health
38
+
39
+No need to restart the Netdata Agent after modifying health configuration files (alerts). Use `netdatacli` to avoid metric collection gaps.
40
+
41
+```bash
42
+sudo netdatacli reload-health
43
+```
44
+
45
## Windows systems
46
47
> **Note**