Systemd service discovery not working

[fleurpot]

We are using check_mk raw 1.6.0 p5.

I am trying to set up a check to monitor the state of wildfly, we are managing it via systemd so I thought rather than use the process monitor I would try and monitor the state of the service as we have had issues when people start it manually.

my unit file is called “wildfly.service” confirmed by the following command..

systemctl show wildfly -p Names

Names=wildfly.service

I have created a Systemd service discovery rules as follows:

I have set it on an explicit host, saved the rule, activated pending changes, and then run a service discovery on the host and fails to detect any new services. I am not sure if its related but I have also had no luck using the systemd services option under APPLICATIONS, PROCESSES & SERVICES.

Am I using the wrong rule, or are we missing a plugin? I can’t seem to find a command line equivalent to check locally on the box I am trying to monitor.

[fleurpot]

I have just added this as a manual check, and its now picking it up as “unknown” the check MK server is reporting:

WARN - [agent] Version: 1.4.0p30, OS: linux, Missing agent sections: systemd_units

So I am now assuming that I am missing a plugin on the agent end?

[lkoenig (Lorenz Koenig)]

The agent will automatically output the systemd-sections (no need for a plugin), but this feature is only present in agent-versions 1.6 and newer. As per your last comment your host is running the agent in version 1.4.0p30, so the systemd-section is missing there. As your site is in version 1.6.0p5 i would recommend pulling the current agent from your site and updating the agent on your host, then the systemd-services should be discovered.

[fleurpot]

Thank you, I did think it was odd our agent was so far behind, I will get on to our infrastructure team and find out why the agent hasn’t been updated when we pushed out the new version.