[Shinken-devel] What is the right term for "criticity"? [Re: 0.4 is out, go prod, and look at the 0.5 :D]

[Christian S. <chr...@in...>]

>> Perhaps we could call it severity instead of "criticity"?
>> http://www.dict.org/bin/Dict?Form=Dict2&Database=*&Query=severity
>>
> It's quite a good name indeed. Thanks to let us know before we code it :)
> Do you know what other tools use for this word?
>

Many tools uses priority and/or severity. Trac[1] chose to keep priority
only and introduce ticket type instead of severity, as people tended to
mix the two concepts priority and severity, and probably because most trac
users did not need the extra distinction. Other projects seem to define
more accurately how priority and severity should be interpreted[2].

I haven't used much time to consider one term vs another, however I do
believe that it is beneficial to discuss and decide on a good name before
coding. This serves two purposes:
 + avoid later confusion when reading code and documentation
 + have an understanding of the concept before programming

OK, WARNING, CRITICAL reminded me about the level in syslog. However
looking more into it, this actually seems to be severity, whereas the
"criticity" probably should be termed priority. This is also in line with
the definitions by tptp[2].

However, using priority one often speaks of my first priority (as the most
important. So by convension priority 1 is more important than priority
with a higher number[3].

References:
[1] http://trac.edgewall.org/wiki/TracTickets
[2]
http://www.eclipse.org/tptp/home/documents/process/development/bugzilla.html
[3] http://en.wikipedia.org/wiki/Priority_level

--
Christian