8 Discovery of systemd services

The item to use in the discovery rule is the

This key is only supported in Zabbix agent 2.

  2.            "{#UNIT.NAME}": "mysqld.service",
  3.            "{#UNIT.DESCRIPTION}": "MySQL Server",
  4.            "{#UNIT.LOADSTATE}": "loaded",
  5.            "{#UNIT.ACTIVESTATE}": "active",
  6.            "{#UNIT.SUBSTATE}": "running",
  7.            "{#UNIT.PATH}": "/org/freedesktop/systemd1/unit/mysqld_2eservice",
  8.            "{#UNIT.JOBID}": 0,
  9.            "{#UNIT.JOBTYPE}": "",
  11.            "{#UNIT.UNITFILESTATE}": "enabled"
  12.        }, {
  13.            "{#UNIT.NAME}": "systemd-journald.socket",
  14.            "{#UNIT.DESCRIPTION}": "Journal Socket",
  15.            "{#UNIT.LOADSTATE}": "loaded",
  16.            "{#UNIT.ACTIVESTATE}": "active",
  17.            "{#UNIT.SUBSTATE}": "running",
  18.            "{#UNIT.PATH}": "/org/freedesktop/systemd1/unit/systemd_2djournald_2esocket",
  20.            "{#UNIT.JOBTYPE}": "",
  21.            "{#UNIT.JOBPATH}": "/",
  22.            "{#UNIT.UNITFILESTATE}": "enabled"
  23.        }]
Discovery of disabled systemd units

Since Zabbix 6.0.1 it is also possible to discover disabled systemd units. In this case three macros are returned in the resulting JSON:

  • {#UNIT.PATH}
  • {#UNIT.ACTIVESTATE}
  • {#UNIT.UNITFILESTATE}.

To have items and triggers created from prototypes for disabled systemd units, make sure to adjust (or remove) prohibiting LLD filters for {#UNIT.ACTIVESTATE} and {#UNIT.UNITFILESTATE}.

Item prototypes that can be created based on systemd service discovery include, for example:

  • Item name: {#UNIT.DESCRIPTION}; item key: systemd.unit.info["{#UNIT.NAME}"]
  • Item name: {#UNIT.DESCRIPTION}; item key: systemd.unit.info["{#UNIT.NAME}",LoadState]

systemd.unit.info are supported since Zabbix 4.4.