[Xymon] Feature request: add description in hosts.cfg for conn multiple IP entry

White, Bruce bewhite at fellowes.com
Wed Apr 10 17:49:14 CEST 2013


Use the COMMENT keyword in your hosts.cfg entry and it will display on
the web page.


 
Bruce White
Senior Enterprise Systems Engineer | Phone: 1-630-671-5169 | Fax: 630-893-1648  | bewhite at fellowes.com | http://www.fellowes.com/
 
 
 
Disclaimer: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Fellowes, Inc.
 
-----Original Message-----
From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf
Of Deiss, Mark
Sent: Wednesday, April 10, 2013 7:46 AM
To: xymon
Subject: [Xymon] Feature request: add description in hosts.cfg for conn
multiple IP entry

Maybe this is supported(?) or someone has a hack available: Would like
to see support for a displayed description field for the hosts.cfg conn
declaration for cases where there are multiple IPs.

When there are a multiple IPs being tested on a given host, it can be a
bit confusing figuring out what a particular failing IP is associated
with. Ideally the description would show up in the status report to help
identify the IP's purpose. 

For example in the hosts.cfg file:

1.2.3.1 main-host1 # conn=worst,1.2.4.10 (ILO address), 1.2.5.20
(PA-RISC Console port), 1.2.3.2 (Web Server Business Portal), 1.2.3.3
(Web Server https Business Portal), 1.2.3.4 (Oracle Listener/databases
connections)......

In web status page:

1.2.3.1 is alive (1ms) 		
1.2.4.10 is alive (3 ms) 	ILO address
1.2.5.20 is alive (3 ms) 	PA-RISC Console port
1.2.3.2 is alive (1 ms) 	Web Server Business Portal
1.2.3.3 is  unreachable 	Web Server https Business Portal
1.2.3.4 is alive (1 ms) 	Oracle Listener/databases connections

The secondary IPs can be declared as separate entries in the hosts.cfg
but that can lead to display "bloat". Even using the separate entries,
there is still no user-friendly detail in the status messages on what is
being tested.

group-compress <B>Operations</B>
1.2.3.1	main-host1 # conn ....
...

Group-compress <B>ILO ports</B>
1.2.4.10	main-host1 # conn
....

Group-compress <B>Console ports</B>
1.2.5.20	main-host1 # conn
....

Group-compress <B>Web Servers ports</B>
1.2.3.2	main-host1 # conn=worst,1.2.3.3		(so if the .3 address ip
is unreachable, you don't know what the business impact is from just
looking at the web status display)	
....




_______________________________________________
Xymon mailing list
Xymon at xymon.com
http://lists.xymon.com/mailman/listinfo/xymon



More information about the Xymon mailing list