Skip to main content
Version: 0.4 · current

NinjaOne checks

OverviewReviewed October 11, 2026
Applies to:Excubius 0.4Roles: Entity admin, Editor
PlansFree · Core · Pro · EnterpriseDeploymentSelf-hosted

The NinjaOne module tells you when a device stops talking to NinjaOne. It measures the minutes since each Windows, Linux and macOS device last contacted NinjaOne, from the device inventory the NinjaOne source already reads. Pending patches and NinjaOne's own alerts arrive through the same source.

What it monitors​

AreaChecksWhy it matters
Device contactMinutes since the device last contacted NinjaOne, for Windows, Linux and macOS hosts: warning after 15 minutes, critical after 60The NinjaOne agent checks in every minute. An hour without contact on a server is an outage or a broken agent

The NinjaOne source also feeds:

WhatWhere it appears
Pending operating system and software patches, approved and not installedThe Updates module and the Updates & advisories page
NinjaOne alerts, with the condition as the ruleThe Alert inbox, as alerts of their own kind

Workstations that sleep are not servers: switch the contact check off on them, or raise its thresholds on their entity. Every check, with its rule, cause and action, is in the reference for NinjaOne checks.

Before you begin​

  • The NinjaOne source, with an API client that has the Monitoring scope only. See Connect NinjaOne.
  • The source kind is on. The feature sources.ninjaone covers the source and this module.

Add a resource​

You do not add these resources by hand. The NinjaOne source adds each Windows, Linux and macOS device as a host under its entity, tagged client with its organization, and matches it with the same server from other sources. The contact check appears the first time the source reports the device.

Next steps​