MSU Listserv


MSUNAG Archives

MSUNAG Archives


MSUNAG@LIST.MSU.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV at MSU

LISTSERV at MSU

MSUNAG Home

MSUNAG Home

MSUNAG  November 2003

MSUNAG November 2003

Subject:

Re: Reporting ongoing outages vs resolved ones

From:

jason justman <[log in to unmask]>

Reply-To:

jason justman <[log in to unmask]>

Date:

Sat, 8 Nov 2003 01:30:05 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (138 lines)

I personally prefer the merit style of the 'status' page containing a
snapshot of not only current but relevant information for the past few
days.  its not as verbose, but presents a better overview of UP/DOWN.

http://www.merit.edu/mail.archives/mn-network-events/

Even netmon has this in its alerts:
http://netmon.cl.msu.edu/netmon/msu/allbbdown.html (Recently Down.. Back
Up).

Why does it show scheduled outages if its not going to show resolved
outages? Maybe it should say "UP - MSU5 router" under outages to let
people know an explict change has occured - rather than dissapearing.

The other possibility is that an 'archived status history' event might
still have relevance to a current problem a user is experiencing.  Why
should there be a separate link to let people get an idea of change that
might have occurred?  The possibility of providing the illusion that
there was not a recent problem is somewhat high.  If just the past 7
days were added below the "Systems Scheduled for Maintenance", it would
be a welcome addition.   Then the archived status link can be placed in
a section which is relevant to its content which is displayed.


BTW - either the joins or updates to the db seem really weird:
https://contact.cl.msu.edu/status/status_history.php?id=000000000000212

same body copy 4 times..

J

Rich Wiggins wrote:

>Folks,
>
>Hmmm, I think this is an example of rising expectations.  :-) Six months
>ago, we didn't have a mechanism for folks to check on current outages.
>When we set up help/status we heard that computer support people needed
>to know not only about outages right now, but also outages that had
>been resolved.  So we added that functionality.
>
>The theory is this:  Your dean says "Was there a network problem
>this morning?" or "Is there a problem with ANGEL today?"
>
>You go to help.msu.edu/status.  You scan for current outages.  You
>see none.  You then click on the link for archived (ie resolved,
>it isn't down any more) outage reports.
>
>In a couple of clicks, you know about all the outages that are
>ongoing now, and all those within the last week.  It seems to me
>that this will answer the questions that we heard at the last face to
>face NAG meeting are asked by your faculty, staff, and management.
>
>We don't want the CURRENT outages page to list RESOLVED outages;
>that page is so people can know what is down now or is scheduled
>to be down soon.  As Doug indicates, it should be easy enough
>for folks to click on one more link to find out about recent outages.
>
>If you are interested in more detailed archive information, you
>can click to open the time window to:
>
>Last 30 days   Last 90 days   Last 365 days
>
>You can sort by the system that failed and you can filter by
>whether past outages where scheduled or not.
>
>We are continuing to refine out help/status works.  The entries you
>see from September are still there because they are STILL ongoing
>problems.  We're working on splitting off a new category so that
>the first page of help.msu.edu/status will show three main items:
>
>-- System outages (ie a major system is down right now)
>
>-- Bulletins (ie something significant of campus-wide interest
>w/r/t IT, e.g. a new major virus threat.  A number of the items
>now listed as Outages would be filed as Bulletins; eg AOL blocking
>Pilot mail.)
>
>-- Scheduled maintenance (ie planned service on a production system.
>Usually these items will be scheduled for off hours.)
>
>We're certainly open to suggestions as we evolve these tools to meet
>the information needs we've heard from customers.  Maybe after we
>have Bulletins implemented would be near the time of the next NAG
>meeting -- where we can go over help/status face to face.
>
>Keep those expectations rising.  :-)  If you know of examples from
>other institutions whose Web-based IT outages reporting systems are
>worth emulating, please let us know the specifics.
>
>Thanks,
>
>/rich
>
>
>
>>I am requesting that outage reports be left up on the main page for at least a
>>week before being archived then.
>>
>>There is information on the status page from September and October. To have
>>archived an outage report this quickly doesn't serve the needs of those who
>>have to answer questions from patrons and faculty.
>>
>>Don Bosman
>>Information Technologist
>>Michigan State University Libraries
>>517-432-6123  ext 233
>>[log in to unmask]
>>
>>
>>
>>
>>
>>-----Original Message-----
>>From: Doug Nelson [mailto:[log in to unmask]]
>>Sent: Friday, November 07, 2003 12:32 PM
>>To: [log in to unmask]
>>Subject: Re: dialup DNS problems
>>
>>
>>
>>
>>>I thought that campus-wide outages were going to be posted on the Computer
>>>Lab Status page? http://help.msu.edu/status/  There is nothing about an
>>>outage posted, therefore it never happened(?)
>>>
>>>
>>Go to that page, then click on "archived status history".  Look for an
>>entry entitled "Off campus network connections down" and dated 10/30/2003
>>11:51 pm.
>>
>>
>>Doug Nelson                     [log in to unmask]
>>Network Manager                 Ph: (517) 353-2980
>>Computer Laboratory             http://www.msu.edu/~nelson/
>>Michigan State University
>>
>>

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

December 2023
June 2023
May 2022
April 2022
March 2022
February 2022
December 2021
January 2019
August 2018
June 2018
May 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001

ATOM RSS1 RSS2



LIST.MSU.EDU

CataList Email List Search Powered by the LISTSERV Email List Manager