Date: Fri, 29 Mar 2024 12:47:35 +0000 (UTC) Message-ID: <1521040197.5757.1711716455987@ip-10-0-1-161.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_5756_129678358.1711716455982" ------=_Part_5756_129678358.1711716455982 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
When the host check for a topological host enters a failure stat= e (i.e. WARN or CRIT), the service monitors for hosts that depend on that e= lement will have their alerts / actions suppressed and enter an UNKN state = until the host check on the topological host recovers. However, there= are a few scenarios where you may still notice alerts being sent when it a= ppears that the topological host has failed:
As a general rule, your topological parent's host check should check as = often as the most checked service on any of the child elements and have a r= e-check interval / max re-checks value that is shorter than the most checke= d service.