node_exporter/examples/systemd
Nils K 715a2ed674
Gracefully handle absence of environment configuration file (#3062)
node_exporter has reasonable defaults so it is able to start without explicit config.
Such a setup is common in /usr/-only images where /etc/ is an empty tmpfs upon boot.

Signed-off-by: Nils K <24257556+septatrix@users.noreply.github.com>
2024-09-22 19:34:41 +02:00
..
node_exporter.service Gracefully handle absence of environment configuration file (#3062) 2024-09-22 19:34:41 +02:00
node_exporter.socket Add multiple listeners and systemd socket listener activation (#2393) 2022-10-23 12:45:29 +02:00
README.md Add multiple listeners and systemd socket listener activation (#2393) 2022-10-23 12:45:29 +02:00
sysconfig.node_exporter Switch to kingpin flags (#639) 2017-08-12 15:07:24 +02:00

Systemd Unit

If you are using distribution packages or the copr repository, you don't need to deal with these files!

The unit files (*.service and *.socket) in this directory are to be put into /etc/systemd/system. It needs a user named node_exporter, whose shell should be /sbin/nologin and should not have any special privileges. It needs a sysconfig file in /etc/sysconfig/node_exporter. It needs a directory named /var/lib/node_exporter/textfile_collector, whose owner should be node_exporter:node_exporter. A sample file can be found in sysconfig.node_exporter.