[evla-sw-discuss] Terminology

[Bruce Rowen]

My thoughts tend to agree with everyone 8^)

Barry's scheme of a mapping between various alert enums into something 
that the user can organize into what suits their purpose along with 
James' notion of using OS built in functionality makes it very flexible 
and adaptable.
For the purpose of the CMIB, errors or any other logable event gets an 
appropriate enum tag that is filterable (think Xpath searching on a log 
file of XML messages).
This also serves up what Kevin and Sonja have stated as part of the 
requirement, only the notion of "error" or "problem" can be 
search/group criteria on whatever is looking at those messages.
Fatal stuff usually is unmaskable as with kernel panics and such where 
the system screams out just before it dies off...
The Unix crowd has defined a range of enums for system/software faults 
that seems to have stabilized over a number of years, we may just have 
to extend it to cover hardware specific items.

$0.02

-Bruce

On Monday, October 27, 2003, at 03:51 PM, James Robnett wrote:

>
>   Is there a reason not to use the priority philosophy inherent in
> syslog ?   It pretty much covers the options and has the added bonus
> that (at a later date) you can use the syslog functionality if you want
> to ....
>
>    From 'man 2 syslog'
>
>        #define KERN_EMERG    "<0>"  /* system is unusable              
>  */
>        #define KERN_ALERT    "<1>"  /* action must be taken 
> immediately */
>        #define KERN_CRIT     "<2>"  /* critical conditions             
>  */
>        #define KERN_ERR      "<3>"  /* error conditions                
>  */
>        #define KERN_WARNING  "<4>"  /* warning conditions              
>  */
>        #define KERN_NOTICE   "<5>"  /* normal but significant 
> condition */
>        #define KERN_INFO     "<6>"  /* informational                   
>  */
>        #define KERN_DEBUG    "<7>"  /* debug-level messages            
>  */
>
> James
>
> On Monday 27 October 2003 03:01 pm, Boyd Waters wrote:
>> "information" - requires no action
>> "warning"     - potential down-stream problems, but proceeding
>> "failure"     - problems, can't continue
>>
>> "warning" and "failure", as listed above, seem both to be "errors":
>>
>> "error"       - something unexpected
>
> _______________________________________________
> evla-sw-discuss mailing list
> evla-sw-discuss at listmgr.cv.nrao.edu
> http://listmgr.cv.nrao.edu/mailman/listinfo/evla-sw-discuss