article Why am I still receiving alerts when my host check is down?

When a host check goes into a failure state (WARN, CRIT), the other service monitors on the target element will have their alerts and/or actions suppressed and enter an UNKN state until the host check recovers.  There are a number of scenarios in which you may still notice alerts being sent for the non-host check monitors:

  • The host check hasn't failed all rechecks.  If the host check is still in its rechecking loop and hasn't started alerting, other monitors will still register outages and potentially send alerts.
  • The element in question doesn't have a proper host check defined.  Check to ensure that the Host Check for the system exists and is the correct monitor.
  • When a non-host check monitor runs, it will not force a run of the host check before sending an alert.  For example, if your host check runs once every 15 minutes but you have a monitor set up to run every minute, the once per minute monitor may fail and alert well before the host check has registered the outage.

As a general rule of thumb, your host check should check as often as the most frequently checked service on the element and have a recheck interval / max rechecks that is shorter than the most frequently checked service.

Related Articles


Why am I not receiving email alerts?

RatingViews
article

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

  4179

Still receiving alerts when topological dependency has failed

RatingViews
article

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...

By: uptime Support | Date Created: 7-7-2011 | Last Modified: 8-11-2011 | Index: 533

  1894

Changing the default host check

RatingViews
article

At times it may be required to change the default up.time host check from PING to UPTIME. Unfortunately there is no way to automatically make this update, up.time will always add the 2 default...

By: uptime Support | Date Created: 10-8-2009 | Last Modified: 8-13-2011 | Index: 396

  2475

Finding and updating hosts without a host check

RatingViews
article

Run the following query to generate a list of hosts (including their groups) without a defined host check: select e.name, eg.name from entity e, entity_group eg where e.entity_group_id =...

By: uptime Support | Date Created: 7-12-2011 | Last Modified: 8-11-2011 | Index: 547

  2563

Process Check monitor does not check the full Solaris path

RatingViews
article

Problem: At times the Check for a Process (Process Check) monitor may not check against a processes full path on Solaris systems. The up.time agent uses the "ps" command to match running processes....

By: uptime Support | Date Created: 12-31-1969 | Last Modified: 9-9-2011 | Index: 236

  4482

User Comments



No comments have been posted.

Copyright © 2021 IDERA, Inc.   Legal   Privacy Statement