Loading full navigation.

Autonomous IT is here. The alert loop ends now. LEARN MORE

Partners

Docs

LM Academy

LM Community

Pricing

Platform
Solution
Industry
Role
There is no result.
Try it free

14-day access to the full LogicMonitor platform

HostStatus DataSource

Last updated – 13 October, 2026

The HostStatus DataSource is a critical component for effectively monitoring your infrastructure. It is preconfigured to associate with all resources added to your portal and is used to determine whether the resource is responsive. A datapoint within the HostStatus DataSource measures the amount of time in seconds since the LogicMonitor Collector was able to collect data from your host through built-in collection methods (for example SNMP, Ping, or WMI).

When the associated Collector cannot contact your host for a period of six minutes or more, LogicMonitor suppresses all alert notifications from that host (the six minute period is not configurable). This alert notification suppression will not auto-trigger an alert indicating that the host has been declared down. That is the job of the HostStatus DataSource. The HostStatus DataSource triggers a critical alert declaring the host down following the period designated in the idleInterval datapoint’s alert threshold.

When a host goes down, it does not generate a new alert (except HostStatus). All other existing alert notifications generated by the host are suppressed. This means they will not trigger notifications to their respective escalation chains. This reduces the noise caused by the cascading effects of the host being down.

Notes:

  • If a newly-added device has resided in the portal for less than 30 minutes and fails host status checks, it will not be declared down after six minutes. Instead, it will require at least 30 minutes of inaccessibility before being declared down.
  • You should not customize the HostStatus DataSource. Changes such as increasing the idleInterval datapoint’s alert threshold or renaming the datasource may result in critical alerts being suppressed or missed entirely, without any visible notification or warning.

Monitoring Response to Host Downtime

When a host goes down, LogicMonitor does not generate a new alert (except HostStatus.) All other existing alert notifications from the host are suppressed. This means they will not trigger notifications to their respective escalation chains. This reduces the noise caused by the cascading effects of your host being down.

Example of HostStatus DataSource

The absence of all data is important in order to formally declare a host as down. For example, data collection failures for individual protocols can result from credential errors such as an updated SNMP community string or a new WMI username and password. The device may still be available to ping, and thus not actually be down. Data collected by script DataSources does not affect the value of the idleInterval datapoint.

HostStatus DataSource example