Change all refs from service to systemctl (#10703)
Joel Hans committed
Mar 3, 2021 at 11:14 UTC
1d003fa0d5111066e1459997c18bb115a036eb94
32 files changed
+108
-85
collectors/QUICKSTART.md
+2
-2
@@ -104,8 +104,8 @@ parameters as a reference, to configure the collector.
104
Most collectors are enabled and will auto-detect their app/service without manual configuration. However, you need to
105
restart Netdata to trigger the auto-detection process.
106
107
-To restart Netdata on most systems, use `service netdata restart`. For other systems, see the [other restart
108
-methods](/docs/getting-started.md#start-stop-and-restart-netdata).
107
+To restart Netdata on most systems, use `sudo systemctl restart netdata`, or the [appropriate
108
+method](/docs/configure/start-stop-restart.md) for your system.
109
110
Open Netdata's dashboard in your browser, or refresh the page if you already have it open. You should now see a new
111
entry in the menu and new interactive charts!
collectors/python.d.plugin/README.md
+6
-1
@@ -84,7 +84,12 @@ If you plan to submit the module in a PR, make sure and go through the [PR check
84
For a quick start, you can look at the [example
85
plugin](https://raw.githubusercontent.com/netdata/netdata/master/collectors/python.d.plugin/example/example.chart.py).
86
87
-**Note**: If you are working 'locally' on a new collector and would like to run it in an already installed and running Netdata (as opposed to having to install Netdata from source again with your new changes) to can copy over the relevant file to where Netdata expects it and then either `sudo service netdata restart` to have it be picked up and used by Netdata or you can just run the updated collector in debug mode by following a process like below (this assumes you have [installed Netdata from a GitHub fork](https://learn.netdata.cloud/docs/agent/packaging/installer/methods/manual) you have made to do your development on).
87
+**Note**: If you are working 'locally' on a new collector and would like to run it in an already installed and running
88
+Netdata (as opposed to having to install Netdata from source again with your new changes) to can copy over the relevant
89
+file to where Netdata expects it and then either `sudo systemctl restart netdata` to have it be picked up and used by
90
+Netdata or you can just run the updated collector in debug mode by following a process like below (this assumes you have
91
+[installed Netdata from a GitHub fork](https://learn.netdata.cloud/docs/agent/packaging/installer/methods/manual) you
92
+have made to do your development on).
93
94
```bash
95
# clone your fork (done once at the start but shown here for clarity)
collectors/python.d.plugin/adaptec_raid/README.md
+2
-2
@@ -60,8 +60,8 @@ cd /etc/netdata # Replace this path with your Netdata config directory, if dif
60
sudo ./edit-config python.d.conf
61
```
62
63
-Change the value of the `adaptec_raid` setting to `yes`. Save the file and restart the Netdata Agent
64
-with `sudo systemctl restart netdata`, or the appropriate method for your system.
63
+Change the value of the `adaptec_raid` setting to `yes`. Save the file and restart the Netdata Agent with `sudo
64
+systemctl restart netdata`, or the [appropriate method](/docs/configure/start-stop-restart.md) for your system.
65
66
## Configuration
67
collectors/python.d.plugin/alarms/README.md
+1
-1
@@ -23,7 +23,7 @@ Below is an example of the chart produced when running `stress-ng --all 2` for a
23
24
## Configuration
25
26
-Enable the collector and restart Netdata.
26
+Enable the collector and [restart Netdata](/docs/configure/start-stop-restart.md).
27
28
```bash
29
cd /etc/netdata/
collectors/python.d.plugin/anomalies/README.md
+2
-1
@@ -45,7 +45,8 @@ pip3 install --user netdata-pandas==0.0.32 numba==0.50.1 scikit-learn==0.23.2 py
45
46
## Configuration
47
48
-Install the Python requirements above, enable the collector and restart Netdata.
48
+Install the Python requirements above, enable the collector and [restart
49
+Netdata](/docs/configure/start-stop-restart.md).
50
51
```bash
52
cd /etc/netdata/
collectors/python.d.plugin/chrony/README.md
+2
-2
@@ -55,7 +55,7 @@ local:
55
command: 'chronyc -n tracking'
56
```
57
58
-Save the file and restart the Netdata Agent with `sudo systemctl restart netdata`, or the appropriate method for your
59
-system, to finish configuring the `chrony` collector.
58
+Save the file and restart the Netdata Agent with `sudo systemctl restart netdata`, or the [appropriate
59
+method](/docs/configure/start-stop-restart.md) for your system, to finish configuring the `chrony` collector.
60
61
[](<>)
collectors/python.d.plugin/hpssa/README.md
+5
-2
@@ -59,8 +59,8 @@ cd /etc/netdata # Replace this path with your Netdata config directory, if dif
59
sudo ./edit-config python.d.conf
60
```
61
62
-Change the value of the `hpssa` setting to `yes`. Save the file and restart the Netdata Agent
63
-with `sudo systemctl restart netdata`, or the appropriate method for your system.
62
+Change the value of the `hpssa` setting to `yes`. Save the file and restart the Netdata Agent with `sudo systemctl
63
+restart netdata`, or the [appropriate method](/docs/configure/start-stop-restart.md) for your system.
64
65
## Configuration
66
@@ -78,4 +78,7 @@ If `ssacli` cannot be found in the `PATH`, configure it in `hpssa.conf`.
78
ssacli_path: /usr/sbin/ssacli
79
```
80
81
+Save the file and restart the Netdata Agent with `sudo systemctl restart netdata`, or the [appropriate
82
+method](/docs/configure/start-stop-restart.md) for your system.
83
+
84
[]()
collectors/python.d.plugin/megacli/README.md
+2
-1
@@ -80,6 +80,7 @@ Battery stats disabled by default. To enable them, modify `megacli.conf`.
80
do_battery: yes
81
```
82
83
----
83
+Save the file and restart the Netdata Agent with `sudo systemctl restart netdata`, or the [appropriate
84
+method](/docs/configure/start-stop-restart.md) for your system.
85
86
[](<>)
collectors/python.d.plugin/samba/README.md
+2
-2
@@ -103,8 +103,8 @@ cd /etc/netdata # Replace this path with your Netdata config directory, if dif
103
sudo ./edit-config python.d.conf
104
```
105
106
-Change the value of the `samba` setting to `yes`. Save the file and restart the Netdata Agent
107
-with `sudo systemctl restart netdata`, or the appropriate method for your system.
106
+Change the value of the `samba` setting to `yes`. Save the file and restart the Netdata Agent with `sudo systemctl
107
+restart netdata`, or the [appropriate method](/docs/configure/start-stop-restart.md) for your system.
108
109
## Configuration
110
daemon/README.md
+2
-2
@@ -395,10 +395,10 @@ all programs), edit `netdata.conf` and set:
395
process nice level = -1
396
```
397
398
-then execute this to restart netdata:
398
+then execute this to [restart Netdata](/docs/configure/start-stop-restart.md):
399
400
```sh
401
-sudo service netdata restart
401
+sudo systemctl restart netdata
402
```
403
404
#### Example 2: Netdata with nice -1 on systemd systems
daemon/config/README.md
+3
-2
@@ -28,10 +28,11 @@ The configuration file is a `name = value` dictionary. Netdata will not complain
28
29
## Applying changes
30
31
-After `netdata.conf` has been modified, Netdata needs to be restarted for changes to apply:
31
+After `netdata.conf` has been modified, Netdata needs to be [restarted](/docs/configure/start-stop-restart.md) for
32
+changes to apply:
33
34
```bash
34
-sudo service netdata restart
35
+sudo systemctl restart netdata
36
```
37
38
If the above does not work, try the following:
docs/Running-behind-apache.md
+1
-2
@@ -255,10 +255,9 @@ errors while accessing the dashboard.
255
DOSPageCount 30
256
```
257
258
-Restart Apache with `sudo service apache2 restart`, or the appropriate method to restart services on your system, to
258
+Restart Apache with `sudo systemctl restart apache2`, or the appropriate method to restart services on your system, to
259
reload its configuration with your new values.
260
261
-
261
### Virtual host
262
263
To adjust the `DOSPageCount` for a specific virtual host, open your virtual host config, which can be found at
docs/collect/enable-configure.md
+4
-2
@@ -32,7 +32,8 @@ Within this file, you can either disable the orchestrator entirely (`enabled: ye
32
enable/disable it with `yes` and `no` settings. Uncomment any line you change to ensure the Netdata daemon reads it on
33
start.
34
35
-After you make your changes, restart the Agent with `service netdata restart`.
35
+After you make your changes, restart the Agent with `sudo systemctl restart netdata`, or the [appropriate
36
+method](/docs/configure/start-stop-restart.md) for your system.
37
38
## Configure a collector
39
@@ -51,7 +52,8 @@ according to your needs. In addition, every collector's documentation shows the
52
configure that collector. Uncomment any line you change to ensure the collector's orchestrator or the Netdata daemon
53
read it on start.
54
54
-After you make your changes, restart the Agent with `service netdata restart`.
55
+After you make your changes, restart the Agent with `sudo systemctl restart netdata`, or the [appropriate
56
+method](/docs/configure/start-stop-restart.md) for your system.
57
58
## What's next?
59
docs/collect/system-metrics.md
+3
-2
@@ -48,8 +48,9 @@ windows_exporter-0.14.0-amd64.exe --collectors.enabled="cpu,memory,net,logical_d
48
49
Next, [configure the WMI
50
collector](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/wmi#configuration) to point to the URL
51
-and port of your exposed endpoint. Restart Netdata with `service netdata restart` and you'll start seeing Windows system
52
-metrics, such as CPU utilization, memory, bandwidth per NIC, number of processes, and much more.
51
+and port of your exposed endpoint. Restart Netdata with `sudo systemctl restart netdata`, or the [appropriate
52
+method](/docs/configure/start-stop-restart.md) for your system. You'll start seeing Windows system metrics, such as CPU
53
+utilization, memory, bandwidth per NIC, number of processes, and much more.
54
55
For information about collecting metrics from applications _running on Windows systems_, see the [application metrics
56
doc](/docs/collect/application-metrics.md#collect-metrics-from-applications-running-on-windows).
docs/export/enable-connector.md
+8
-6
@@ -47,9 +47,10 @@ Use the following configuration as a starting point. Copy and paste it into `exp
47
Replace `my_opentsdb_http_instance` with an instance name of your choice, and change the `destination` setting to the IP
48
address or hostname of your OpenTSDB database.
49
50
-Restart your Agent with `sudo systemctl restart netdata` to begin exporting to your OpenTSDB database. The Netdata Agent
51
-exports metrics _beginning from the time the process starts_, and because it exports as metrics are collected, you
52
-should start seeing data in your external database after only a few seconds.
50
+Restart your Agent with `sudo systemctl restart netdata`, or the [appropriate
51
+method](/docs/configure/start-stop-restart.md) for your system, to begin exporting to your OpenTSDB database. The
52
+Netdata Agent exports metrics _beginning from the time the process starts_, and because it exports as metrics are
53
+collected, you should start seeing data in your external database after only a few seconds.
54
55
Any further configuration is optional, based on your needs and the configuration of your OpenTSDB database. See the
56
[OpenTSDB connector doc](/exporting/opentsdb/README.md) and [exporting engine
@@ -68,9 +69,10 @@ Use the following configuration as a starting point. Copy and paste it into `exp
69
Replace `my_graphite_instance` with an instance name of your choice, and change the `destination` setting to the IP
70
address or hostname of your Graphite-supported database.
71
71
-Restart your Agent with `sudo systemctl restart netdata` to begin exporting to your Graphite-supported database. Because
72
-the Agent exports metrics as they're collected, you should start seeing data in your external database after only a few
73
-seconds.
72
+Restart your Agent with `sudo systemctl restart netdata`, or the [appropriate
73
+method](/docs/configure/start-stop-restart.md) for your system, to begin exporting to your Graphite-supported database.
74
+Because the Agent exports metrics as they're collected, you should start seeing data in your external database after
75
+only a few seconds.
76
77
Any further configuration is optional, based on your needs and the configuration of your Graphite-supported database.
78
See [exporting engine reference](/exporting/README.md#configuration) for details.
docs/getting-started.md
+5
-9
@@ -211,16 +211,12 @@ You can use these features together or separately—the decision is up to yo
211
When you install Netdata, it's configured to start at boot, and stop and restart/shutdown. You shouldn't need to start
212
or stop Netdata manually, but you will probably need to restart Netdata at some point.
213
214
-- To **start** Netdata, open a terminal and run `service netdata start`.
215
-- To **stop** Netdata, run `service netdata stop`.
216
-- To **restart** Netdata, run `service netdata restart`.
214
+- To **start** Netdata, open a terminal and run `sudo systemctl start netdata`.
215
+- To **stop** Netdata, run `sudo systemctl stop netdata`.
216
+- To **restart** Netdata, run `sudo systemctl restart netdata`.
217
218
-The `service` command is a wrapper script that tries to use your system's preferred method of starting or stopping
219
-Netdata based on your system. But, if either of those commands fails, try using the equivalent commands for `systemd`
220
-and `init.d`:
221
-
222
-- **systemd**: `systemctl start netdata`, `systemctl stop netdata`, `systemctl restart netdata`
223
-- **init.d**: `/etc/init.d/netdata start`, `/etc/init.d/netdata stop`, `/etc/init.d/netdata restart`
218
+See our doc on [starting, stopping, and restarting](/docs/configure/start-stop-restart.md) the Netdata Agent for
219
+details.
220
221
## What's next?
222
docs/guides/collect-apache-nginx-web-logs.md
+5
-4
@@ -52,8 +52,8 @@ Find the `web_log` line, uncomment it, and set it to `web_log: no`. Next, open t
52
53
Find the `web_log` line again, uncomment it, and set it to `web_log: yes`.
54
55
-Finally, restart Netdata with `service netdata restart`, or the appropriate method for your system. You should see
56
-metrics in your Netdata dashboard!
55
+Finally, restart Netdata with `sudo systemctl restart netdata`, or the [appropriate
56
+method](/docs/configure/start-stop-restart.md) for your system. You should see metrics in your Netdata dashboard!
57
58
@@ -120,8 +120,9 @@ jobs:
120
log_type: auto
121
```
122
123
-Restart Netdata with `service netdata restart` or the appropriate method for your system. Netdata should pick up your
124
-web server's access log and begin showing real-time charts!
123
+Restart Netdata with `sudo systemctl restart netdata`, or the [appropriate
124
+method](/docs/configure/start-stop-restart.md) for your system. Netdata should pick up your web server's access log and
125
+begin showing real-time charts!
126
127
### Custom log formats and fields
128
docs/guides/collect-unbound-metrics.md
+5
-3
@@ -54,8 +54,9 @@ configuring the collector.
54
You may not need to do any more configuration to have Netdata collect your Unbound metrics.
55
56
If you followed the steps above to enable `remote-control` and make your Unbound files readable by Netdata, that should
57
-be enough. Restart Netdata with `service netdata restart`, or the appropriate method for your system. You should see
58
-Unbound metrics in your Netdata dashboard!
57
+be enough. Restart Netdata with `sudo systemctl restart netdata`, or the [appropriate
58
+method](/docs/configure/start-stop-restart.md) for your system. You should see Unbound metrics in your Netdata
59
+dashboard!
60
61
62
@@ -98,7 +99,8 @@ jobs:
99
Netdata will attempt to read `unbound.conf` to get the appropriate `address`, `cumulative`, `use_tls`, `tls_cert`, and
100
`tls_key` parameters.
101
101
-Restart Netdata with `service netdata restart`, or the appropriate method for your system.
102
+Restart Netdata with `sudo systemctl restart netdata`, or the [appropriate
103
+method](/docs/configure/start-stop-restart.md) for your system.
104
105
### Manual setup for a remote Unbound server
106
docs/guides/export/export-netdata-metrics-graphite.md
+2
-2
@@ -115,8 +115,8 @@ the port accordingly.
115
...
116
```
117
118
-We'll not worry about the rest of the settings for now. Restart the Agent using `sudo service netdata restart`, or the
119
-appropriate method for your system, to spin up the exporting engine.
118
+We'll not worry about the rest of the settings for now. Restart the Agent using `sudo systemctl restart netdata`, or the
119
+[appropriate method](/docs/configure/start-stop-restart.md) for your system, to spin up the exporting engine.
120
121
## See and organize Netdata metrics in Graphite
122
docs/guides/monitor-cockroachdb.md
+3
-3
@@ -30,9 +30,9 @@ configuring CockroachDB. Netdata only needs to regularly query the database's `_
30
display them on the dashboard.
31
32
If your CockroachDB instance is accessible through `http://localhost:8080/` or `http://127.0.0.1:8080`, your setup is
33
-complete. Restart Netdata with `service netdata restart`, or use the [appropriate
34
-method](../getting-started.md#start-stop-and-restart-netdata) for your system, and refresh your browser. You should see
35
-CockroachDB metrics in your Netdata dashboard!
33
+complete. Restart Netdata with `sudo systemctl restart netdata`, or the [appropriate
34
+method](/docs/configure/start-stop-restart.md) for your system, and refresh your browser. You should see CockroachDB
35
+metrics in your Netdata dashboard!
36
37
<figure>
38
<img src="https://user-images.githubusercontent.com/1153921/73564467-d7e36b00-441c-11ea-9ec9-b5d5ea7277d4.png" alt="CPU utilization charts from a CockroachDB database monitored by Netdata" />
docs/guides/monitor-hadoop-cluster.md
+2
-2
@@ -161,10 +161,10 @@ jobs:
161
address : 203.0.113.10:2182
162
```
163
164
-Finally, restart Netdata.
164
+Finally, [restart Netdata](/docs/configure/start-stop-restart.md).
165
166
```sh
167
-sudo service restart netdata
167
+sudo systemctl restart netdata
168
```
169
170
Upon restart, Netdata should recognize your HDFS/Zookeeper servers, enable the HDFS and Zookeeper modules, and begin
docs/guides/monitor/anomaly-detection.md
+4
-3
@@ -79,9 +79,10 @@ yourself if it doesn't already exist. Either way, the final result should look l
79
anomalies: yes
80
```
81
82
-[Restart the Agent](/docs/configure/start-stop-restart.md) with `sudo systemctl restart netdata` to start up the
83
-anomalies collector. By default, the model training process runs every 30 minutes, and uses the previous 4 hours of
84
-metrics to establish a baseline for health and performance across the default included charts.
82
+[Restart the Agent](/docs/configure/start-stop-restart.md) with `sudo systemctl restart netdata`, or the [appropriate
83
+method](/docs/configure/start-stop-restart.md) for your system, to start up the anomalies collector. By default, the
84
+model training process runs every 30 minutes, and uses the previous 4 hours of metrics to establish a baseline for
85
+health and performance across the default included charts.
86
87
> 💡 The anomaly collector may need 30-60 seconds to finish its initial training and have enough data to start
88
> generating anomaly scores. You may need to refresh your browser tab for the **Anomalies** section to appear in menus
docs/guides/monitor/pi-hole-raspberry-pi.md
+4
-4
@@ -83,9 +83,9 @@ As far as configuring Netdata to monitor Pi-hole metrics, there's nothing you ac
83
collector](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/pihole) will autodetect the new service
84
running on your Raspberry Pi and immediately start collecting metrics every second.
85
86
-Restart Netdata with `sudo service netdata restart` to start Netdata, which will then recognize that Pi-hole is running
87
-and start a per-second collection job. When you refresh your Netdata dashboard or load it up again in a new tab, you'll
88
-see a new entry in the menu for **Pi-hole** metrics.
86
+Restart Netdata with `sudo systemctl restart netdata`, which will then recognize that Pi-hole is running and start a
87
+per-second collection job. When you refresh your Netdata dashboard or load it up again in a new tab, you'll see a new
88
+entry in the menu for **Pi-hole** metrics.
89
90
## Use Netdata to explore and monitor your Raspberry Pi and Pi-hole
91
@@ -119,7 +119,7 @@ cd /etc/netdata
119
sudo ./edit-config charts.d.conf
120
```
121
122
-Uncomment the `sensors=force` line and save the file. Restart Netdata with `sudo service netdata restart` to enable
122
+Uncomment the `sensors=force` line and save the file. Restart Netdata with `sudo systemctl restart netdata` to enable
123
Raspberry Pi temperature sensor monitoring.
124
125
### Storing historical metrics on your Raspberry Pi
docs/guides/monitor/process.md
+6
-4
@@ -169,8 +169,9 @@ postgres: postgres*
169
sql: mariad* postmaster* oracle_* ora_* sqlservr
170
```
171
172
-Restart Netdata with `service netdata restart`, or the appropriate method for your system, to start collecting
173
-utilization metrics from your application. Time to [visualize your process metrics](#visualize-process-metrics).
172
+Restart Netdata with `sudo systemctl restart netdata`, or the [appropriate
173
+method](/docs/configure/start-stop-restart.md) for your system, to start collecting utilization metrics from your
174
+application. Time to [visualize your process metrics](#visualize-process-metrics).
175
176
### Custom applications
177
@@ -194,8 +195,9 @@ custom-app: custom-app
195
...
196
```
197
197
-Restart Netdata with `service netdata restart`, or the appropriate method for your system, to start collecting
198
-utilization metrics from your application.
198
+Restart Netdata with `sudo systemctl restart netdata`, or the [appropriate
199
+method](/docs/configure/start-stop-restart.md) for your system, to start collecting utilization metrics from your
200
+application.
201
202
## Visualize process metrics
203
docs/guides/step-by-step/step-04.md
+2
-2
@@ -95,8 +95,8 @@ section and give it the value of `1`.
95
test = 1
96
```
97
98
-Restart Netdata with `service restart netdata` or the [appropriate
99
-alternative](/docs/getting-started.md#start-stop-and-restart-netdata) for your system.
98
+Restart Netdata with `sudo systemctl restart netdata`, or the [appropriate
99
+method](/docs/configure/start-stop-restart.md) for your system.
100
101
Now, open up your browser and navigate to `http://HOST:19999/netdata.conf`. You'll see that Netdata has recognized
102
that our fake option isn't valid and added a notice that Netdata will ignore it.
docs/guides/step-by-step/step-05.md
+2
-2
@@ -69,8 +69,8 @@ the `warn` and `crit` lines to the values of your choosing. For example:
69
crit: $this > (($status == $CRITICAL) ? (75) : (85))
70
```
71
72
-You _can_ [restart Netdata](/docs/getting-started.md#start-stop-and-restart-netdata) to enable your tune, but you can
73
-also reload _only_ the health monitoring component using one of the available [methods](/health/QUICKSTART.md#reload-health-configuration).
72
+You _can_ restart Netdata with `sudo systemctl restart netdata`, to enable your tune, but you can also reload _only_ the
73
+health monitoring component using one of the available [methods](/health/QUICKSTART.md#reload-health-configuration).
74
75
You can also tune any other aspect of the default alarms. To better understand how each line in a health entity works,
76
read our [health documentation](/health/README.md).
docs/guides/step-by-step/step-06.md
+5
-5
@@ -7,8 +7,8 @@ custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/guides/step
7
8
When Netdata _starts_, it auto-detects dozens of **data sources**, such as database servers, web servers, and more.
9
10
-To auto-detect and collect metrics from a source you just installed, you need to [restart
11
-Netdata](/docs/getting-started.md#start-stop-and-restart-netdata).
10
+To auto-detect and collect metrics from a source you just installed, you need to restart Netdata using `sudo systemctl
11
+restart netdata`, or the [appropriate method](/docs/configure/start-stop-restart.md) for your system.
12
13
However, auto-detection only works if you installed the source using its standard installation
14
procedure. If Netdata isn't collecting metrics after a restart, your source probably isn't configured
@@ -99,9 +99,9 @@ Next, edit your `/etc/nginx/sites-enabled/default` file to include a `location`
99
}
100
```
101
102
-Restart Netdata using `service netdata restart` or the [correct
103
-alternative](/docs/getting-started.md#start-stop-and-restart-netdata) for your system, and Netdata will auto-detect
104
-metrics from your Nginx web server!
102
+Restart Netdata using `sudo systemctl restart netdata`, or the [appropriate
103
+method](/docs/configure/start-stop-restart.md) for your system, and Netdata will auto-detect metrics from your Nginx web
104
+server!
105
106
While not necessary for most auto-detection and collection purposes, you can also configure the Nginx collector itself
107
by editing its configuration file:
docs/guides/step-by-step/step-09.md
+6
-4
@@ -62,7 +62,8 @@ metrics your Agent collects, and more.
62
dbengine disk space = 512
63
```
64
65
-After you've made your changes, [restart Netdata](/docs/getting-started.md#start-stop-and-restart-netdata).
65
+After you've made your changes, restart Netdata using `sudo systemctl restart netdata`, or the [appropriate
66
+method](/docs/configure/start-stop-restart.md) for your system.
67
68
To confirm the database engine is working, go to your Netdata dashboard and click on the **Netdata Monitoring** menu on
69
the right-hand side. You can find `dbengine` metrics after `queries`.
@@ -142,9 +143,10 @@ Add the following section to the file:
143
collection = netdata_metrics
144
```
145
145
-[Restart](/docs/getting-started.md#start-stop-and-restart-netdata) Netdata to enable the MongoDB exporting connector.
146
-Click on the **Netdata Monitoring** menu and check out the **exporting my mongo instance** sub-menu. You should start
147
-seeing these charts fill up with data about the exporting process!
146
+Restart Netdata using `sudo systemctl restart netdata`, or the [appropriate
147
+method](/docs/configure/start-stop-restart.md) for your system, to enable the MongoDB exporting connector. Click on the
148
+**Netdata Monitoring** menu and check out the **exporting my mongo instance** sub-menu. You should start seeing these
149
+charts fill up with data about the exporting process!
150
151
152
docs/guides/troubleshoot/monitor-debug-applications-ebpf.md
+5
-3
@@ -57,8 +57,9 @@ dev: custom-app
57
...
58
```
59
60
-Restart Netdata with `sudo service netdata restart` or the appropriate method for your system to begin seeing metrics
61
-for this particular group+process. You can also add additional processes to the same group.
60
+Restart Netdata with `sudo systemctl restart netdata`, or the [appropriate
61
+method](/docs/configure/start-stop-restart.md) for your system, to begin seeing metrics for this particular
62
+group+process. You can also add additional processes to the same group.
63
64
You can set up `apps_groups.conf` to more show more precise eBPF metrics for any application or service running on your
65
system, even if it's a standard package like Redis, Apache, or any other [application/service Netdata collects
@@ -105,7 +106,8 @@ Replace `entry` with `return`:
106
network viewer = yes
107
```
108
108
-Restart Netdata with `sudo service netdata restart` or the appropriate method for your system.
109
+Restart Netdata with `sudo systemctl restart netdata`, or the [appropriate
110
+method](/docs/configure/start-stop-restart.md) for your system.
111
112
## Get familiar with per-application eBPF metrics and charts
113
docs/store/change-metrics-storage.md
+2
-1
@@ -54,7 +54,8 @@ multihost disk space` setting. Change it to the value recommended above. For exa
54
dbengine multihost disk space = 1024
55
```
56
57
-Save the file and restart the Agent with `service netdata restart` to change the database engine's size.
57
+Save the file and restart the Agent with `sudo systemctl restart netdata`, or the [appropriate
58
+method](/docs/configure/start-stop-restart.md) for your system, to change the database engine's size.
59
60
## What's next?
61
health/notifications/stackpulse/README.md
+3
-2
@@ -39,8 +39,9 @@ SEND_STACKPULSE="YES"
39
STACKPULSE_WEBHOOK="https://hooks.stackpulse.io/v1/webhooks/YOUR_UNIQUE_ID"
40
```
41
42
-4. Now [restart Netdata](/docs/getting-started.md#start-stop-and-restart-netdata). When your node creates an alarm, you
43
- can see the associated notification on your StackPulse Administration Portal
42
+4. Now restart Netdata using `sudo systemctl restart netdata`, or the [appropriate
43
+ method](/docs/configure/start-stop-restart.md) for your system. When your node creates an alarm, you can see the
44
+ associated notification on your StackPulse Administration Portal
45
46
## React to alarms with playbooks
47
packaging/installer/README.md
+2
-2
@@ -232,8 +232,8 @@ the lines to match the output from `ls -la` above and uncomment them if necessar
232
web files group = netdata
233
```
234
235
-Save the file, [restart the Netdata Agent](/docs/getting-started.md#start-stop-and-restart-netdata), and try accessing
236
-the dashboard again.
235
+Save the file, restart Netdata using `sudo systemctl restart netdata`, or the [appropriate
236
+method](/docs/configure/start-stop-restart.md) for your system, and try accessing the dashboard again.
237
238
### Multiple versions of OpenSSL
239