Alarms allow you to monitor the status of your devices based on the metrics reported by drivers.

An alarm compares the received values with conditions defined by the user.

When a configured condition is reached, Zebrix Control:

• Triggers an alarm
• Changes the device status
• Displays the alarm in the interface

Alarms rely on three main elements:

• A driver
• One or more metrics
• One or more alarm conditions

The driver collects information from the device and sends metrics to Zebrix Control.

These metrics are then analyzed to determine whether an alarm should be triggered.

Example:

• The Ping driver reports the metric “alive”
• The received value is “false”
• An alarm rule specifies that “alive = false”
• The device status changes to Critical or Unreachable

To create an alarm:

1. Open the device configuration
2. Go to the Alarms tab
3. Click Configuration
4. Click the ➕ Add button

Two types of alarms are available:

• Measurement alarm – Based on the values reported by a metric
• No data alarm – Triggered when Zebrix Control no longer receives any data from a selected driver

This type of alarm detects when a driver no longer reports any data.

This usually means:

• The device is unreachable
• The network is unavailable
• Or the probe can no longer communicate with the device

Example:

• A Samsung display uses an MDC driver
• The driver no longer reports any information
• Zebrix Control triggers an alarm

It is not recommended to use this type of alarm with the Ping driver.

A failed Ping is still considered valid data.

When the device does not respond:

• The driver still returns a value
• The reported value is simply “false”

As long as the probe continues to receive metrics from the Ping driver, a No Data alarm will never be triggered.

The delay configured in a No Data alarm must always be:

• Greater than or equal to the minimum polling interval of the driver

Example:

• Driver minimum polling interval: 10 minutes
• No Data alarm delay: 5 minutes ❌

In this case, Zebrix Control will check for missing data before the driver has had enough time to send a new metric.

Result:

• False alarms will be triggered regularly

• Driver polling interval: 10 minutes
• No Data alarm delay: 10 minutes or more

This type of alarm compares a metric directly against a value or threshold.

It is the most commonly used alarm type.

For a given metric, you can define multiple thresholds corresponding to different severity levels.

An alarm is triggered when the value reported by the probe matches the configured criteria.

By default:

• If no condition matches → the device status remains OK
• If multiple conditions match → the highest severity level is applied

A device reports a “volume” metric.

You can configure:

• Info if volume = 0
• Warning if volume > 50
• Critical if volume > 80

The device status will automatically change according to the reported values.

The Ping driver reports a boolean value:

• “true”
• “false”

Recommended configuration:

• Level: Unreachable
• Condition: “=”
• Value: “false”

In this case:

• “true” → device reachable
• “false” → device unreachable