Skip to main content

Possible statuses of a resource

Statuses show the availability of a host, and the availability or performance of a service. Each status has a precise meaning for the resource.

  • The statuses and states of a resource can be seen on page Resources Status. You can filter the page according to these statuses and to certain states.
  • Some statuses are determined according to user-defined thresholds.

Host status

The table below summarizes all the possible statuses for a host.

StatusDescription
UPThe host is available and reachable
DOWNThe host is unavailable
PENDINGThe host has just been created and has not been checked yet by the monitoring engine

Service status

The table below summarizes all the possible statuses for a service.

StatusDescription
OKThe service presents no problem
WARNINGThe service has reached the warning threshold
CRITICALThe service has reached the critical threshold
UNKNOWNThe status of the service cannot be checked (e.g.: SNMP agent down, etc.)
PENDINGThe service has just been created and has not been checked yet by the monitoring engine

States

In addition to their status, resources can be in several states:

  • Acknowledged: indicates that the incident on the service or on the host has been taken into account by a user. Acknowledged resources have a yellow background.
  • In downtime: indicates that notifications are temporarily stopped. Downtime can be planned in advance to avoid receiving alerts during maintenance periods, or can be set following an incident. Resources in downtime have a purple background.

Status types

The status of a resource can be one of these two types:

  • SOFT: Means that an incident has just been detected and that it has to be confirmed.
  • HARD: Means that the status of the incident is confirmed. Once the status is confirmed, the notification process is engaged (sending of an email, SMS, etc.).

You can filter the view on the Resources Status page according to the status type.

Explanation

An incident (Not-OK status) is confirmed as soon as the number of validation attempts has reached its end. As soon as the first incident is detected, the state is "SOFT" until its confirmation into "HARD", triggering the notification process.