Re: [SAGE] Color identifiers and products like Nagios ...

[Fuat Baran <fuat@columbia.edu>]

On Nov 22, 2005, at 6:58 PM, Jennifer Davis wrote:

>
> So reading about the planned changes with Firefox, Opera, Konqueror, 
> and IE7 (reference 
> http://blogs.msdn.com/ie/archive/2005/11/21/495507.aspx).. especially 
> the idea of color coded address bar to report phishing and other 
> possible negative aspects to a potential website, and then reading 
> some of the comments about color-blindness, and poor color choices, I 
> wondered about the use in monitoring tools like nagios.
>
> Is the standard "red" - critical state, "yellow" - warning state, and 
> "green" - good/normal state good indicators for monitoring.  I 
> understand that there is an associated value with those colors, but is 
> that American-centric?
>
> If you were designing a brand new, from scratch tool/application for 
> system administrators .. would you follow the standard red, yellow, 
> green rules?  If not, why not?
>
> In part, I'm wondering about the information one would want to convey 
> to the rest of the people in an organization outside of the IT 
> department, who don't necessarily want to understand the technical 
> aspects but want to understand how/if they are affected.  (not wanting 
> people to attribute their possible experience with an announced 
> problem, but also not wanting to have to repeat multiple times with 
> updates to different people)
>
> Jennifer
>
>
For network management there is the ITU-T X.733 document (Information 
technology-Open Systems Interconnection-Systems Management: Alarm 
reporting function).

They define the states as indeterminate, critical, major, minor, and 
warning.  I think (but can't confirm since I don't have a copy of the 
document handy) they define corresponding colors purple, red, orange, 
yellow and blue respectively.

							--Fuat