Create top-level views of your applications in a graphical editor. Rules express dependencies between existing hosts and services and let you alert on application level. Business processes are displayed in a tree or list overview.
We make extensive use of F5 load balancers or services that are in high availability (HA).
We want to provide the operators, who monitor day and night, with the ability to take the best actions based on the status.
Example
Example: Our two Icinga2 masters each have their own IcingaDB.
If both IcingaDB services are working, it is OK.
No action needed
If both IcingaDB services are down, it is CRITICAL (red color)
Urgent action must be taken, and possibly the on-call staff should be called to resolve this issue as soon as possible.
If one of the two IcingaDB services is down, it is WARNING (orange color)
This does not need to be resolved urgently outside office hours. It can wait until the next working day.
The next working day they can quickly see that some services ( all in WARNING) are not working and need to be resolved
DEGRADED
Actually, there is the DEGRADED option with the only difference that CRITICAL - CRITICAL does not result in WARNING, but is displayed as CRITICAL.
New DEGRADED CRITICAL table
I use this option in combination with the setting that WARNING/PENDING and UNKNOWN are overridden by CRITICAL.
then you can reduce the table/operator to :
Is there a possibility to provide the DEGRADED CRITICAL option in the future?
MIN x
Maybe it's also interesting to create a 3-level status for operator MIN:
Currently, it is:
MIN x OK: status is OK
Other: CRITICAL
It might be interesting to add more gradation:
ALL OK: OK
MIN x OK, but not everything is OK: status is WARNING
Less than MIN x: CRITICAL
Is it possible to provide the operator MIN with a 3-level status?
Hello,
We make extensive use of F5 load balancers or services that are in high availability (HA). We want to provide the operators, who monitor day and night, with the ability to take the best actions based on the status.
Example
Example: Our two Icinga2 masters each have their own IcingaDB.
If both IcingaDB services are working, it is OK.
If both IcingaDB services are down, it is CRITICAL (red color)
If one of the two IcingaDB services is down, it is WARNING (orange color)
DEGRADED
Actually, there is the DEGRADED option with the only difference that CRITICAL - CRITICAL does not result in WARNING, but is displayed as CRITICAL.
New DEGRADED CRITICAL table
I use this option in combination with the setting that WARNING/PENDING and UNKNOWN are overridden by CRITICAL.
then you can reduce the table/operator to :
Is there a possibility to provide the DEGRADED CRITICAL option in the future?
MIN x
Maybe it's also interesting to create a 3-level status for operator MIN:
Currently, it is:
MIN x OK: status is OK
Other: CRITICAL
It might be interesting to add more gradation:
ALL OK: OK
MIN x OK, but not everything is OK: status is WARNING
Less than MIN x: CRITICAL
Is it possible to provide the operator MIN with a 3-level status?
regards, Geert