Feature Request for nkview

Epp, Matthew Contractor PEO EIS AKO matthew.epp at us.army.mil
Wed Sep 6 23:23:40 CEST 2006


I love the new Critical Systems overview so far! I've been configuring every
single system/alert in the config file using vi, since I needed to do
roughly 500 servers at once. A few things occurred to me.

- It would be helpful to be able to use wildcards in the hostname and
service fields. Say you've decided that any CPU alerts are really not that
important and can all be PRIO 3. Right now you need to define that for every
system separately, since you can only point a server to another to get /all/
of it's PRIO settings. Then you could just have one line somewhere stating:
*|cpu||||3|||username 2006-07-27 15:34:05

Maybe have it at the bottom, then the code could first look for a hostname
match, and if it doesn't find one, then it'll match the wildcard at the end
of the config file.

- Have the nkview consider ALL active alerts, and for any that it can't find
a PRIO setting for, display it at the bottom in a section labeled UNKNOWN.
You could also add it to the Priority drop-down menu to filter them out. I
realize this may seem a little redundant, as there's always the bb2.html
view, but sometimes people are adding in new servers to the bb-hosts file,
but don't realize you also need to configure a PRIO in order for the alerts
to show at all on nkview.

- Not sure if this has already been addressed: How does nkview handle purple
events from dead clients?



More information about the Xymon mailing list