Systemd is a suite of basic building blocks for a Linux system.
This module monitors
Systemd units state.
- Works only on linux systems.
- Disabled by default. Should be explicitly enabled in the
It produces the following charts:
- Service Unit State in
- Socket Unit State in
- Target Unit State in
- Path Unit State in
- Device Unit State in
- Mount Unit State in
- Automount Unit State in
- Swap Unit State in
- Timer Unit State in
- Scope Unit State in
- Slice Unit State in
|1||started, bound, plugged in, ..., depending on the unit type|
|2||stopped, unbound, unplugged, ..., depending on the unit type|
|3||in the process of being activated|
|4||in the process of being deactivated|
|5||the service failed in some way (process returned error code on exit, or crashed, an operation timed out, or after too many restarts)|
go.d/systemdunits.conf configuration file using
edit-config from the
Netdata config directory, which is typically at
cd /etc/netdata # Replace this path with your Netdata config directory
sudo ./edit-config go.d/systemdunits.conf
include option. Syntax is shell file name pattern.
Here are some examples:
- name: my-specific-service-unit
- name: service-units
- name: socket-units
For all available options, see the Systemdunits collector's configuration file.
To troubleshoot issues with the
systemdunits collector, run the
go.d.plugin with the debug option enabled. The
output should give you clues as to why the collector isn't working.
First, navigate to your plugins directory, usually at
/usr/libexec/netdata/plugins.d/. If that's not the case on your
netdata.conf and look for the setting
plugins directory. Once you're in the plugin's directory, switch
sudo -u netdata -s
You can now run the
go.d.plugin to debug the collector:
./go.d.plugin -d -m systemdunits