Overdue devices

A device is classified as overdue if it has not uploaded data to the All Devices view within the specified time period and we have not received a graceful shutdown message. The handling of these overdue devices depends on whether the Agent on the device was installed in server mode or workstation mode.

An overdue device may indicate an issue with the device, which could be a connectivity issue, a problem with the Advanced Monitoring Agent, or something else.

For more articles about overdue devices to help you troubleshoot and investigate unexpected overdue devices, see: Troubleshooting: Overdue Device search results

If you suspect a connectivity issue, ensure the device meets the Network Connectivity Requirements.

Server

To highlight that data was not received, overdue servers display in the All Devices view and Wall Chart with a red background Last Response time. In addition to this visual indicator, a notification email or SMS Alert is sent when the device fails to report in and a recovery message is sent when the server subsequently reports back. This server alerting behavior is enabled by default, but may be configured to meet your requirements.

The overdue status for servers is only available if 24x7 Checks are configured on the device. If the Agent is installed with only Daily Safety Checks or in Asset Tracking only (no Checks) the device does not report as overdue.

As some devices may require a longer, or shorter, time-period to report in, you can set how long a server fails to report back before it is marked as overdue.

  1. In the All Devices view, right-click the device in the North-pane and select Edit Server.
  2. Go to General Settings.
  3. For Send an overdue alert if the server has not reported in after n minute(s), use the drop-down menu to enter the target time.

    The period of inactivity is configurable from 1 minute to 6 hours, with overdue alerting of less than 15 minutes only available on servers with 5 minute monitoring.

    For example, if you use 5-minute monitoring and select 2 minutes, if the server reports into N-sight RMM at 12:00:00, we would expect it to check back in at around 12:05:00. If no communication is received from the server by 12:07:00, an overdue Alert is sent.

  4. To send an SMS alert when the Server goes overdue, enable Also send SMS alert (optional).
  5. Select OK to save and apply.

    6. Due to overdue alert processing and verification, it may take between 10 to 30 seconds before the alert is sent.

    Enhanced overdue reporting utilizes the technology incorporated in our faster monitoring improvements and please ensure all Agent URLs are reachable from the device to take advantage of this feature.

Workstation

If a workstations fails to communicate back to N-sight RMM within 1.5 times the monitoring interval (non-configurable) its Last Response Time is highlighted in yellow in the All Devices view and Wall Chart.

The workstation overdue mechanism is different to the technology used for server reporting. It does not support the generation of data overdue or received alerting and is not tied to the 24x7 Checks. For example if there are no Checks configured (for example Asset Tracking Only (no template) or only Daily Safety Checks enabled the workstation will display as overdue.

Agent check-in behavior after server or workstation restart

When a workstation or server powers on, the Agent reports back to N-sight RMM shortly after startup. This ensures the Last Response column in the All Devices view more accurately reflects the computer's actual state.