We're monitoring PhEDEx now. The result, in Cnagios is... well... too wide to fit this blog. Trust me. It's in there. Try the web interface.
We're monitoring port 2811 on the new GridFTP doors (whatever they are?!)
Some recent discussion on the Nagios mailing list reminded me that I've announced my super nifty full-screen terminal interface for Nagios...
http://noc.hep.wisc.edu/cnagios.html
Cnagios and nagiosr make a darn nice replacement for the Nagios web GUI--in fact I almost never use the web gui anymore!
If you know Nagios, then you probably know that that some of it's monitoring scripts (aka "plugins") suck. And that's why I wrote nifty scripts to monitor sendmail mail queue size over snmp today...
ftp://noc.hep.wisc.edu/pub/src/nagios/
Adaptec bought a company called DPT a number of years ago. I
have a long and good history of using the RAID controllers
from DPT. A few months ago, I was disappointed to find out
that Adaptec had stopped making DPT-based RAIDs. I emailed one
of the DPT guys at Adaptec and he sent my a very friendly reply
with the skinny. Adaptec no longer makes DPT-based RAID controllers,
but they have folded a lot of the DPT technology into their latest
("aacraid") controllers and software. So we're now standardizing
on the aacraid controllers--which I'm comfortable with because
not-so-little vendors like Dell and Sun integrate aacraid controllers
into their products. And thus I just finished writing a Nagios plugin
to monitor our new aacraid (2130/2230S) controllers...
ftp://noc.hep.wisc.edu/pub/src/nagios/
There was a thread about report generation on the Nagios mailing list last week, so I posted asking about a simple CLI report generator. There wasn't one. But one kind fellow asked exactly what sort of output I was looking for. Well, back in 1995, I had written a report generator for the NOCOL monitoring package, so I just posted a snippet of old output from that. Lo and behold, the next day this guy has written the code!
The result is Nagiosr and the output is sweeet! I tried posting sample output here, but it overwrites the right hand column, but you can see some sample output by clicking here.
At first there was a typo in the config which caused it to not work, but now the UWMadisonCMS WAN_Traffic shows up in the DiSUN MonALISA...
http://www.disun.org:8888/display?page=wan_traffic_histogram
Our "monitor the monitoring" system at FermiLab is up. You can see it in all it's glory (?) at
http://noc2.hep.wisc.edu/nagios/
At the request of Dan Bradley, UW-HEP now has an iperf service available at iperf.hep.wisc.edu. The system (SL304) has reasonable (perhaps not the best?) kernel tuning, and the iperf daemon has a 16 MB TCP window. Internally, we're seeing around 942 Mbps of throughput. Enjoy.
Harvey Newman from CalTech quickly pointed out that this service is of dubious utility. And I certainly agree. But I also believe that our iperf service provides ball-park estimates that are useful, for example, as a "reality check". If you believe your site has 1 Gbps connectivity, ane you only realize, say, 155 Mbps, then you should probably revise your notion of reality!
Given the recent UW<->ESnet peering outage and our responsibilities as a CMS Tier2 Data Center, I've written a little Nagios plug-in script to monitoring IP routing via the "mtr" command. The results can be seen here...
http://noc.hep.wisc.edu/nagios/cgi-bin/status.cgi?hostgroup=internet
You can find the plug-in (called check_ip_routing_with_mtr) here...
ftp://noc.hep.wisc.edu/pub/src/nagios/