When the host check for a topological host enters a failure state (i.e. WARN or CRIT), the service monitors for hosts that depend on that element 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 appears 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 re-check interval / max re-checks value that is shorter than the most checked service. |
Why am I not receiving email alerts? | Rating | Views | |
---|---|---|---|
Email alerts may not be properly sent for any of the following reasons - The SMTP server settings are incorrect. If you are receiving other email alerts or are able to send an emailed report to... By: uptime Support | Date Created: 12-31-1969 | Last Modified: 9-1-2011 | Index: 268 |
4502 |
Why am I still receiving alerts when my host check is down? | Rating | Views | |
---|---|---|---|
When a host check goes into a failure state (WARN,CRIT) the other service monitors on the target element will have their alerts/actions supressed and enter an UNKN state until the host check... By: uptime Support | Date Created: 8-27-2010 | Last Modified: 8-13-2011 | Index: 498 |
2152 |
monitor failed: software caused connection abort: recv failed | Rating | Views | |
---|---|---|---|
This error message indicates a general network connectivity error from the monitoring station to the monitored agent servers. It has only been seen on windows monitoring stations and is generally... By: uptime Support | Date Created: 12-31-1969 | Last Modified: 6-27-2013 | Index: 280 |
6560 |
Creating Topological Dependencies | Rating | Views | |
---|---|---|---|
In large deployments, a single system or node can act as the gateway to other entities or entity groups. For example, up.time might need to go through a router - configured as a node in up.time -... By: uptime Support | Date Created: 1-30-2009 | Last Modified: 8-25-2011 | Index: 354 |
3189 |
Receiving "Could not connect to database" from Oracle Monitor | Rating | Views | |
---|---|---|---|
This article suggests how to troubleshoot and resolve issues related to connecting to an Oracle database with any of the three up.time Oracle service monitors (Basic Check, Advanced Metrics or... By: uptime Support | Date Created: 8-10-2012 | Last Modified: 8-11-2012 | Index: 583 |
1880 |