Robert
If the process creates a PID file, and cleans up when done, you could
monitor the age of that file, and alert when it's beyond a threshold.
One problem with this approach is that it requires a clientlocal.cfg entry
to collect the PID file's metadata, and it's only the last Xymon server's
clientlocal.cfg that gets used. (By "last" I mean which is listed last in
the client's XYMSRV setting.) If the third party happens to have added your
Xymon server last, then you might get this to work just fine, but that
situation might change in the future if the client is reconfigured to put
another Xymon server last.
Cheers
Jeremy
▸ quoted from Robert Herron
On Thu, 27 May 2021 at 05:53, Robert Herron <user-8b27ea4290da@xymon.invalid> wrote:
I need pointers to documentation or how-to for monitoring via the Client
Data server-side.
I have a server managed by a third-party. Fortunately, this vendor uses
Xymon to monitor it. I cannot add custom EXT scripts to it. The vendor did
add my Xymon server to the xymonclient.cfg?s XYMSERVERS parameter so I
can set custom thresholds in my analysis.cfg.
So, the server had a process that hung and started causing problems. I
would like to leverage a Client Data on my server to monitor and alert for
this process.
Thanks.
--
Robert Herron
user-8b27ea4290da@xymon.invalid