Availability Monitoring

On this page

Availability Monitoring checks whether your computers and hardware devices answer on the network. When a device keeps failing to answer, it creates an Incident or sends an e-mail notification, as you configure it. For Incidents in general, see Tickets.

Nothing about the integration is compiled into the product: its two scheduled tasks, its parameters, and the messages it logs come with the supplied workflow configuration. This page describes them as they are in a new 2026.1 database created with the Default Workflow; see Default Workflow Configuration. An upgraded database need not have this content, and an administrator may have changed it.

How it works

Availability Monitoring consists of two scheduled tasks:

  • Availability Monitoring Device Checking pings each eligible device that is not yet recorded as failed, once per run, and records every device that does not answer as a first failure.
  • Availability Monitoring Failed Devices re-pings only the recorded devices. When the Failed Attempt Threshold is reached for a device, the task takes the action set in Failed Threshold Action and clears the device's failure record.

Each task runs on its own schedule; for the schedules a new database starts with, see Supplied configuration. No parameter switches the integration on or off. You enable the two tasks and change their schedules on the Scheduled Tasks pages; see Enable the scheduled tasks.

Which devices are checked

You do not pick devices one by one. A device is checked when all of these apply:

  • It is an active computer or hardware item.
  • It has a primary IP address, and that address does not start with 169.
  • Its primary IP address is on a Network that is linked to the organization set in Organization.
  • Its category is in one of the two monitored-category parameters, one for computer categories and one for hardware categories.

The monitored-category parameters hold category names as text, matched against your own categories. When you rename a category or add a new one, it is not monitored until you update the parameter too.

Each device is checked by its primary IP address, with one ping per run. When two devices share an address, each device is pinged, and when the address does not answer, each device is recorded as failed.

What happens when a device fails

When the threshold is reached, the task does what Failed Threshold Action says:

  • Create Incident creates an Incident configured by the seven Incident parameters and by the role set in Assignee / E-mail Recipient.
  • Send E-mail Notification sends an e-mail notification to the role set in Assignee / E-mail Recipient.

While an Incident for the same device and service is not Resolved or Closed, a repeated failure does not create a second Incident, but it does send the notification again.

Network requirements

Availability Monitoring uses ICMP echo (ping), so no port has to be opened for devices on the same network. Private addresses cannot be reached from outside unless routes are added.

Availability Monitoring is available on-premises and in Alloy Navigator Cloud. Whether a Cloud system can ping devices on your private network is a question of network connectivity.

Workflow parameters

The parameters are on the integration's own settings page in Workflow Configuration, Integrations > Availability Monitoring. The integration has no Safe Mode parameter.

Parameter Description
Organization The organization whose Networks hold the devices to check. If it is blank, the session aborts.
Failed Attempt Threshold The number of failed attempts at which the action is taken. If it is blank, the session aborts.
Failed Threshold Action Create Incident or Send E-mail Notification. If it is blank, the session aborts.
The two monitored-category parameters (computer categories and hardware categories) Lists of category names, matched as text. If no category to monitor is listed, the session aborts.
The seven Incident parameters: Medium, Type, Category, Status, Service, Impact, and Urgency (Incident Service is a lookup) The values of the Incident that the task creates. A blank value does not stop the session: it logs a warning that the Incident may get blank values. For a blank Service, Impact, or Urgency, the Incident's Response and Due Dates may also be blank.
Assignee / E-mail Recipient The role for the Incident, or the role the e-mail notification is sent to: Device Owner, Organization Manager, Network Owner, or Service Manager.
Debug Logging Status The only On/Off parameter.

Supplied configuration

In a new 2026.1 database created with the Default Workflow, Availability Monitoring starts with the settings below; see Default Workflow Configuration.

  • The two scheduled tasks are in the group Integrations, and both are disabled.
  • Availability Monitoring Device Checking is scheduled to run every 10 minutes, and Availability Monitoring Failed Devices every minute, both all day.
  • Failed Attempt Threshold is set to 5.
  • Failed Threshold Action is set to Create Incident.
  • Assignee / E-mail Recipient is set to Service Manager.
  • Incident Service is empty. The supplied services include a Service named Availability Monitoring, and Incident Service is not set to it.

Set the parameters

To change the parameters, you need, in the Settings App, the administrative right that allows managing Workflow Configuration, and in the Admin Center, the Workflow Configuration permission; see Permissions Reference.

In the Settings App

  1. Under Workflow and Business Logic, open Workflow Configuration.
  2. In the category tree, select Integrations > Availability Monitoring. The right pane shows one control per parameter, with its description.
  3. Enter the values and save your changes. Only the changed values of the selected category are saved.

In the Admin Center

  1. Under Workflow and Business Logic, open Workflow Configuration.
  2. Open Integrations > Availability Monitoring. The page shows one control per parameter.
  3. Enter the values, and then click Save. Save and Cancel appear once you change a field. If you leave the page with unsaved changes, the Admin Center asks: "You should save you changes before leaving this page. Do you want to leave this page?"

The Admin Center's Workflow Configuration form does not check the values you enter against the parameter's type or declared validation rules.

Enable the scheduled tasks

Enabling, running, and scheduling tasks is described in Scheduled Tasks. The two tasks to enable are Availability Monitoring Device Checking and Availability Monitoring Failed Devices.

  • In the Settings App, the tasks are on the Services > Scheduled Tasks > Tasks page, which has the Enable, Disable, Run, and Terminate commands. The Scheduled Task window of a task has a Settings tab with Enabled and a Schedule group, whose Change... opens the Schedule window.
  • In the Admin Center, the tasks are on the Tasks tab of Scheduled Tasks. A task opens with a Settings tab and a Sessions tab.

The Scheduled Tasks pages have a right of their own in the Settings App and a permission of their own in the Admin Center; see Scheduled Tasks. While no Automation Server is running, the Scheduled Task window in the Settings App and the opened task in the Admin Center show "Warning. For this job to be executed, the Automation Server must be set up and running."

Under an Alloy Navigator Cloud license, the Settings App refuses a schedule interval shorter than 60 minutes, or shorter than 1 hour when the interval is in hours, and the Admin Center raises an interval in minutes that is shorter than 60 to 60 minutes. On-premises, the Settings App accepts an interval of 1 minute or more.

Troubleshooting

A session is aborted, with a log line that starts with "ERROR." and ends with "Session is aborting.", when:

  • Organization is blank.
  • Failed Attempt Threshold is blank.
  • Failed Threshold Action is blank.
  • No category to monitor is listed.
  • The selected organization has no IP addresses.
  • "The number of IP addresses for the selected organization exceeds 10,000".

A blank Incident parameter only logs a WARNING and does not stop the session.

The ERROR and WARNING lines are written to the session log of the task's run. The Automation Server records an aborted session as a failed run.

You read the tasks' sessions on the Scheduled Tasks pages of the Settings App and the Admin Center; see Scheduled Tasks and Logs.

  • In the Settings App, the Sessions tab of the Scheduled Task window lists the task's runs. The Scheduled Tasks log is also under Services > Scheduled Tasks > Logs and under Logs > Scheduled Tasks, where View Log shows the text of the selected session.
  • In the Admin Center, the Sessions tab of the task lists its sessions, and a session opens its log. The Logs tab of Scheduled Tasks shows the Scheduled Tasks log, and the Logs area of the Admin Center shows the same log.

The integration's messages point you to its settings page: "See Workflow Configuration > Integrations > Availability Monitoring to provide settings".