Building hobbit-nkview.cfg from cmdb (Critical systems view) 🔗 link

Hi all,

I'm trying to generate the hobbit-nkview.cfg file from an external
source (our CMDB) and not using the Critical systems editor,
hobbit-nkedit.sh .

As I've being unable to find docs on the format for the
hobbit-nkview.cfg file, I'm just hoping you help me to gather the
relevant into. The requirements are:

- All monitored hosts are subject to appear in the Critical systems view.
- All hosts are applied Prio3 by default.
- Some checks (columns) may have higher priority than host's default.
ie: load-balanced host is prio3 but http check in that host is prio2.


Playing around with the editor, I've being able to produce this :

# fake host definition that all unix hosts inherit
dummy_unix_template|content||||2|Group in charge||
dummy_unix_template|cpu||||2|Group in charge||
dummy_unix_template|disk||||2|Group in charge||
dummy_unix_template|files||||2|Group in charge||
dummy_unix_template|fullduplex||||2|Group in charge||
dummy_unix_template|hardware||||2|Group in charge||
dummy_unix_template|http||||2|Group in charge||
dummy_unix_template|info||||2|Group in charge||
dummy_unix_template|memory||||2|Group in charge||
dummy_unix_template|meta||||2|Group in charge||
dummy_unix_template|msgs||||2|Group in charge||
dummy_unix_template|network||||2|Group in charge||
dummy_unix_template|ntp||||2|Group in charge||
dummy_unix_template|ping||||2|Group in charge||
dummy_unix_template|ports||||2|Group in charge||
dummy_unix_template|procs||||2|Group in charge||
dummy_unix_template|raid||||2|Group in charge||
dummy_unix_template|ssh||||2|Group in charge||
dummy_unix_template|sslcert||||2|Group in charge||
dummy_unix_template|temp||||2|Group in charge||
dummy_unix_template|timediff||||2|Group in charge||
dummy_unix_template|updates||||2|Group in charge||
# real servers
actual_unix_host1|=dummy_unix_template
actual_unix_host2|=dummy_unix_template
...etc

However this has a number of drawbacks :

- I've being unable to find a regexp to match all columns. Then it
makes necessary to know in advance all the columns that all hosts can
have (and involve the development team each time a new column is
required).
- It's also a problem since most of our HTTP checks are named
content_* , ie: content_InternalURL , content_APP1, etc).

any ideas?

best regards

;))


Le 22 déc. 2009 à 19:25, Fran Garcia <user-a22f64c5936d@xymon.invalid> a  
écrit :