Sort order of Service Problems (CRITICAL/UNKNOWN/WARNING)

Icinga Web
1

Since moving to Icinga DB Web I’m wondering why the sort order of “Service Problems” is:

  1. CRITICAL
  2. UNKNOWN
  3. WARNING

I’d expect:

  1. CRITICAL
  2. WARNING
  3. UNKNOWN

I’m not sure how it was within Icinga Web 2,. but it feels wrong :man_shrugging:
Can somebody tell something about this sort order and maybe how to change it to the order I’m expecting?

Thanks for any help!

Regards,
Alex R.

2

This is just my interpretation:

For SLA calculation OK and Warning are both Good and Critical and Unknown are both bad for your SLA.

So Critical and Unknown services should be viewed before something that is in a warning state which has no impact on your SLA

3

@moreamazingnick
I guess you’re right! I haven’t had this in mind :man_shrugging:
That helped me “sorting” it out😊

Regards,
Alex R.

4

My few cents: The argument for this order of severities is the following in my head:

  • CRITICAL is obviously very bad, something is burning!
  • UNKNOWN, you really don’t know what is happening, might be quite bad
  • WARNING, not ideal, not terrible. Should be a cause for concern, but not enough to ring someone out of the bed

That’s how I model it and I think that’s the though behind this sort order