search

meerkat-dashboard / meerkat

Drag-and-drop dashboards for Icinga
https://meerkat.run
GNU Affero General Public License v3.0
18 stars 2 forks source link

Unknown states are treated as worse than critical #222

Closed sol1-matt closed 1 year ago

sol1-matt commented 1 year ago

For dashboard elements that return more than one Icinga object the "worst" state is returned. At the moment this appears to be numericly sorted eg: unknown (3), critical (2), warning (1), ok (0).

It also appears that Meerkat v2 also made things acknowledged if anything in the group was acknowledged, Meerkat v3 doesn't appear to treat acknowledged this way.

Icingaweb2's Severity sort uses the order (worst to best)

Nagvis used the order

Change the default order to match the Nagvis order Allow the order to be changed by users on a per dashboard basis

sol1-matt commented 1 year ago

The ability to have specify different sort behavior's may be useful here. The above is a sensible default.

sol1-matt commented 1 year ago

There is a bug in the sort order when you have both Critical and Critical (Ack) are present in the group and Critical (Ack) has the priority. The dashboard displays Critical instead of Critical (Ack).

Also fails on when the state is Warning vs Warning(Ack). Also fails on any Ack when a un Ack'd state exists.

sol1-matt commented 1 year ago

This isn't a meerkat bug, it is a problem with how Ack is handled in Icinga.

In Icinga when a host is acknowledged any service on that host becomes handled, the acknowledgment isn't visible on the service.

handled is only available as a api call, not in event streams.

Ref: https://community.icinga.com/t/handled-not-in-checkresult-event-stream/12545