Getting a notification after 2-3 times critical is already kind of the default
Notifications are only sent if a Hard State is reached. You can configure how many soft states are needed for a Hard State.
What @bberg wanted to tell you is, that this is alreday the case by default. Icinga2 will (by default) only trigger a notification if a Host or Service reaches a “hard state”, which is (again by default, can be configured) after three consecutive “failed” checks.
How many “failed” attempts are necessary for a ‘Host’ or ‘Service’ to reach a “hard state” (as opposed to the “sofft state”) is not part of the notification configuration but of the Host or Service.
Regarding your second question, what is a “client” in this case?
Ok, let’s see if I can explain it in a few words:
Notifications are attached or linked to Services or Hosts, one Notification object for each single Service or Host.
Meaning, they are independent of each other. If two Services trigger a notification you will get two emails (assuming the usage of emails, the same apply rule for the Notifications and so on).
If you configure something like a ServiceNotification which applies to every Service (Condition: service.name or just true or something like that) you will get Notifications independently for each Service.
Does this answer your question? If not, please elaborate a bit.
@lorenz Thank you for explanation, i get it. And then i can easly make new Apply Rule en assing to the host/services (Webconsole> Directory> notification> notification> Create new notification Apply Rule> )
i have CPu check with warning at 80% and critical at 90 % and ThresholdInterval 5 min.
So what want is that if the CPU above 90% after 3 checks (after 15 min) then its wil print RED in dahsboard not if when Critical 90% after 2 checks and next check is under 90%