 |
 |
These are excellent ideas. Centralized IT status pages have been implemented at other universities. One of my favorite examples is Penn State. Check out these URLs: http://www.its.psu.edu/ (look at the right column with Alerts) http://status.cac.psu.edu/statpage/status.html (status of major services) http://clc.cets.psu.edu/pals/labuse.exe (find out how busy a microlab is before you visit it) I think the PSU model is really great but obviously it would take serious thinking, co-ordination, and allocation of resources to make a single, reliable, comprehensive IT status service. /rich >LeTourneau, John wrote: > >>What could be even better is if 1) all the MSU critical systems are defined, >>e.g., SIS, email, the network, Advance 2) A status site is created for ALL >>MSU critical systems (not just computer lab systems) 3) Information is >>posted to the site whenever there is an incident, outage, denial of service >>involving one of the systems 4) A message is sent to the NAG whenever >>something is added to the status site. >> >>Something of this nature would be very helpful for us. It may not be able to >>get a status out in real time, especially if you can't get to the site. But >>after the network, or whatever, comes back on line we would have some real >>information instead of word-of-mouth like what is being passed around on the >>denial of service attack yesterday morning.