<div>Hello Harper,</div> <div> </div> <div>Just my 2 cents.. :-)</div> <div> </div> <div>I am not sure who I can contact but If you guys need help with QA or Dev, I can give a hand because I used to work on Unicenter... :-)</div> <div> </div> <div>Thanks,</div> <div>Tom Tran</div> <div>eesimed.com Harper Mann <hmann@groundworkopensource.org> wrote:</div> <BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">Hi Tom, Good thought. I think the meta-issue is what features go into a dashboard. Propagation and drill-down are good ones to consider. A dashboard should present actionable information at a glance. There have been status map improvement discussions and I believe work is in progress on it. You might check the archives to see who is working it. Cheers, - Harper Tom Tran wrote: > Dear Harper and All, > > Thank you very much for you explanation. I am totally clear and I > have no problem with that at all. > > However, don't you think it's better this way. > > Supposed you are the network admin, sitting in front of huge monitor > and managing a status map of your entire network which has about 200 > critical servers... if all the servers are up and running.. So, they > are all green. How do you know which one has a problem like Running > out of disk space or exchange process has just stopped? If you can > propagate, when the exchange process stopped, it goes to critical > status.. this child service will propagrate to the parent node... and > the network admin will see.. Oh.. something is wrong with node xyz. > because it's RED.. so let me drill down that node to see what's going on? > > Best regards, > Tom Tran, > PS: The statements above is CONSTRUCTIVE suggestion. I am not trying > to compare Nagios to any product. It is just my thought to help us to > have a better Nagios if you guys think my suggestion is useful. > > > > */Harper Mann <HMANN@GROUNDWORKOPENSOURCE.ORG>/* wrote: > > Hi Tom, > Nagios has two top-level types of check, host checks and service > checks. Host checks are a check that verifies the host is up. It's > generally defined as a ping check. Service checks check services like > disk, cpu, swap, etc. are running on the host. By default, Nagios > checks a service and if it is in alarm, it runs the host check. If > the host check fails, Nagios sends host notification and doesn't send > service notification. If the host is up, it sends the service > notification. > > Nagios, only runs the host checks if the service fails. So if the > disk is bad, it's set critical, but the host check ping still works so > the host is not set down. This is intentional because if the disk > fails, and the host check fails, disk notifications are suppressed as > well as the other services being checked, and you get one alarm that > the host is down and not one alarm each for each service. Feature.... > > Nagios doesn't have propagation like Unicenter. It has a host check > so it can suppress alarm storms. > > Hope this helps. > Regards, > - Harper > Harper Mann > Groundwork Open Source > 510-599-2075 (cell) > > Tom Tran wrote: >> Dear All, > >> I am a newbie with Nagios but long time user of Enterprise >> Management (CA Unicenter in particular)... > >> Here is my suggestion (not sure If i implemented correctly...) or it >> has been designed this way. > >> Suppose I am monitoring a Server.... which I am trying to monitoring >> the following: >> Ping, disk space, Load....... > >> And i set the threshold for my disk space.. and the disk space >> exceeds my critical threshold; therefore, the status for my Disk >> Space Watcher is Red (Critical)... > >> According to what i see right now.. the status for the whole server >> is GREEN.. I am not sure it is supposed to be green? Isn't it >> supposed to be RED.... because of the propagation from a child level? > >> Hope my explanation is clear enough. > >> Best regards, >> Tom Tran >> EESImed. > > >> */Deborah Martin <DEBORAH.MARTIN@KOGNITIO.COM>/* wrote: > >> Hi, > >> I'm running Suse 9.1 with Nagios 2.0b4 > >> I have a service alerting as Critical which I then acknowledged. >> Notifications were then supressed. >> However, I had to restart Nagios sometime later after adding >> some further >> services/hosts and it seems that the acknowledgement still >> remains across >> the restart but the notifications have started again. > >> Is this expected behaviour ? I've trawled through the docs and >> archives but >> cannot find a definitive >> answer so any advice would be appreciated. > >> thanks, >> deborah > > > ************************************************************************ >> This email and any files transmitted with it are confidential and >> intended solely for the use of the individual or entity to whom > they >> are addressed. Any unauthorised distribution or copying is strictly >> prohibited. > >> Whilst Kognitio Limited takes steps to prevent the transmission of >> viruses via e-mail, we can not guarantee that any email or >> attachment is free from computer viruses and you are strongly >> advised to undertake your own anti-virus precautions. > >> Kognitio grants no warranties regarding performance, >> use or quality of any e-mail or attachment and undertakes no >> liability for loss or damage, howsoever caused. > > *********************************************************************** > > > > ------------------------------------------------------------------------- >> Take Surveys. Earn Cash. Influence the Future of IT >> Join SourceForge.net's Techsay panel and you'll get the chance >> to share your >> opinions on IT & business topics through brief surveys -- and >> earn cash > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >> _______________________________________________ >> Nagios-users mailing list >> Nagios-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/nagios-users >> ::: Please include Nagios version, plugin version (-v) and OS >> when reporting any issue. >> ::: Messages without supporting info will risk being sent to >> /dev/null > > >> ---------------------------------------------------------------------- >> Do you Yahoo!? >> Everyone is raving about the all-new Yahoo! Mail Beta. >> <HTTP: evt="42297/*http://advision.webevents.yahoo.com/handraisers" us.rd.yahoo.com> > > >> ---------------------------------------------------------------------- > >> ------------------------------------------------------------------------- >> Take Surveys. Earn Cash. Influence the Future of IT >> Join SourceForge.net's Techsay panel and you'll get the chance to > share your >> opinions on IT & business topics through brief surveys -- and earn cash >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > >> ---------------------------------------------------------------------- > >> _______________________________________________ >> Nagios-users mailing list >> Nagios-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/nagios-users >> ::: Please include Nagios version, plugin version (-v) and OS when > reporting any issue. >> ::: Messages without supporting info will risk being sent to /dev/null > ------------------------------------------------------------------------ > Do you Yahoo!? > Next-gen email? Have it all with the all-new Yahoo! Mail Beta. > <HTTP: evt="42241/*http://advision.webevents.yahoo.com/handraisers" us.rd.yahoo.com> </BLOCKQUOTE> <hr size=1>Do you Yahoo!? Everyone is raving about the <a href="http://us.rd.yahoo.com/evt=42297/*http://advision.webevents.yahoo.com/handraisers"> all-new Yahoo! Mail Beta.</a>