[Xymon] Can client extension scripts use client-local.cfg data passed back to client?

Henrik Størner henrik at hswn.dk
Fri Jul 11 12:51:16 CEST 2014


 

Den 2014-07-11 8:49, Richard Hamilton skrev: 

> I'm gathering that
said data ends up in $XYMONCLIENTHOME/tmp/logfetch.$MACHINEDOTS.cfg. 
>

> Would it hurt anything to put (on the server) data in addition to the
lines defined in the man page? Would it make it back to the above file?

> 
> And if so, can a naming convention be recommended for user-defined
lines that should avoid conflict with any future official lines? (maybe
names that begin with site_ or something like that?)

You can add extra
lines to the client-local.cfg definition for a host, and they will end
up in the client logfetch.<hostname>.cfg file. It may take a bit of time
- the Xymon daemon has to reload the client-local.cfg file (by default,
it checks for updates every 10 minutes - if you do a "kill -HUP" on the
xymond process, it will reload the configuration immediately), and the
client has to run one cycle before the new configuration is passed to
the client. So it may take up to 15 minutes for a change to show up on
the client. 

A naming convention would be ok, I think "site_" is too
long to type, but something like 'X-' (as is used in many other text
protocols, e.g. http) would be fine with me. 

> And if that's not all
crazy...it would be cool if the library module to fetch the
client-local.cfg for a host could check the timestamp on the file, and
if changed, reload it (freeing all the old data structures first, so as
not to leak memory, of course!) 
> 
> That way, without restarting the
server, one could replace the client-local.cfg file on the server and
have client log, file, and extension script behavior altered
accordingly.

See above, this should happen already. 

Having used Big
Brother for many years, the ability of Xymon to pass update

> or
whatever), sounds like it could make life _much_ simpler in terms of
centralizing the control of clients and server alike. So naturally I
want to take that to its logical extreme. :-) But so far, I haven't read
enough of the code to really have a good handle on just what might be
possible, let alone normal enough not to be too fragile. 
> 
> For
larger configuration files, you can use the 'xymon IP "config FILENAME"'
or 'xymon IP "download FILENAME"' commands on the client. See the
xymon(1) and xymond(8) manpages.
rds,
Henrik 

 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xymon.com/pipermail/xymon/attachments/20140711/683daaca/attachment.html>


More information about the Xymon mailing list