Monitor a UPS Zen-X with a .txt file

[openmindz (Thomas Karatzoglou)]

Hi @Obeylife10

@Obeylife10

Should I remove the agent and reinstall it ? When I tried the @r.sander’s method (plugin) maybe it caused a conflict with local checks?

No, I don’t think so, but the plugin looks for me as if it is for Checkmk 1.6 and not for 2.0. Anyway, that shouldn’t interfere with local checks.

@Obeylife10

Stupid question, when I put the script in the directory, checkmk should execute it automatically ?

Yes, if it’s executable. From your output I see, that it is being executed.

@Obeylife10

And as my checkmk server and agent are on the same machine, I don’t really need to use Piggyback mechanism right ?

In theory, no. But the services your local check creates, will be associated with your “main” host. If you can live with that, and just “know” that those two services refer to your UPS, that’s fine. If you want to have your UPS as a separate host in Checkmk, I’d personally use the piggyback method.

Back to the issue: the script mylocalcheck is being executed, but as I see, the <<<<otherhost>>>> identifier is not present, so I believe that’s the reason why no piggyback data is present.

Can you try two things:

• remove the line with echo <<<local>>> from mylocalcheck. Wait three minutes or so, and recheck your host in “Setup”: Theoretically, your host should discover two new services. This would “fulfill” the scenario of having services which refer to the UPS, associated with your “main host”.

• add both lines with echo <<<<otherhost>>>> and the line with echo <<<local>>> to mylocalcheck. Again, wait three minutes or so. Theoretically piggyback data should exist now, your host should “lose” the two services it discovered before, and if you discover services for “otherhost” it should find them. This would result in having two hosts in Checkmk: your main host, and the piggybacked one.

I hope all my explanations are not too convoluted…

Thomas