Re: [hobbit] Usefulness for xymonconfigsync?

["W.J.M. Nelis" <nelis (at) nlr.nl>]

Hello,

> I've seen this link:
>
> http://sourceforge.net/projects/xymonconfigsync/
>
> Could some of you please share what are some of the ways in which you are using this?
>   
That module is used quite frequently over here. That is not really 
surprising, as I am the author of that perl module.

The module is written to be able to synchronize the Xymon configuration 
file bb-hosts with a configuration database. That database contains the 
devices to be monitored, some comment and above all the administrators 
of each device. Those administrators will receive an e-mail if there is 
a yellow or red condition for a test of "their" server. The database 
does *not* contain information about the tests to be performed. When 
regenerating the bb-hosts configuration file, information is taken as 
much as possible from the configuration database, and the rest of the 
information, especially the network tests, is taken from the old version 
of the bb-hosts configuration file.

As a result, a server becomes monitored (although with only one test 
"conn") as soon as it is defined in the configuration database, en it 
disappears from Xymon once it is removed from the database. Thus the 
administrators have a bit of control of what is being monitored, and who 
receives the alerts, as they are allowed to modify the configuration 
database.

To illustrate the benefits of this approach: bb-hosts is divided into 
about a dozen subfiles, glued together with "include" directives. One of 
them contains for each administrator a list of devices (s)he 
administers. There is a notes-file for each monitored device, which 
contains a link to that entry in the configuration database. In 2009, 
the configuration synchronization has (re)written more than 2700 times 
one of those configuration files.

A way of using the xymonconfigsync module is described in the POD within 
the module.

Regards,
 Wim Nelis.



*******************************************************************************************************
The NLR disclaimer (http://www.nlr.nl/emaildisclaimer) is valid for NLR e-mail messages.
*******************************************************************************************************