Skip to main content
Version: 0.4 · current

Windows

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

The Windows module watches Windows hosts: CPU, memory and disks, the services that must run, pending updates and reboots, security events and hardening. Its values come from the sources you already have, New Relic, NinjaOne and Azure Monitor, or from the native collector over WinRM, which is experimental in this release.

What it monitors​

AreaChecksWhy it matters
CPU and memoryCPU utilization, available memoryA host short of CPU or memory slows everything it runs
DisksFree space per volume, read and write latencyA full volume stops databases and logs; slow disks are the usual cause of slow SQL Server data files
ServicesThe listed services running, by default MSSQLSERVER, SQLSERVERAGENT, SQLBrowser and ReportServerA stopped service is an outage even when the host is up
UpdatesPending reboot, pending Windows updates found by a search, operating system version and editionFeeds the Track updates and advisories page; Excubius never installs an update
SecuritySecurity event log entries such as failed logons, privileged group changes, a cleared audit log and new services; hardening posture: antivirus, firewall, SMBv1, RDP and local administratorsEarly signs of an attack, and settings that make one easier

Every check, with its rule, cause and action, is in the reference for Windows checks.

Where the values come from​

SourceFeeds
New RelicCPU, memory and disk free space of the hosts its infrastructure agent reports
NinjaOneMinutes since the device last contacted NinjaOne, pending patches and NinjaOne alerts, in the NinjaOne module
Azure MonitorAzure VMs: power state, CPU and pending updates from Azure Update Manager, in the Azure module
Native collector over WinRMEvery check of the module, including services, updates, events and hardening

A host reported by several sources is one resource. A check the native collector already runs is never taken over by a source.

warning

Collection over WinRM is experimental: the transport exists and its checks are added to Windows hosts, but it has not been validated against real hosts yet. Use a source for the hosts that matter until a release marks WinRM as supported.

Before you begin​

For collection over WinRM:

  • A domain account, member of the local groups Performance Monitor Users, Event Log Readers and Remote Management Users on each host. Never a local administrator.
  • A WinRM HTTPS listener on TCP 5986, restricted to the IP address of the Excubius server.
  • A Windows account credential with the connection option auth set to negotiate or ntlm. The default, kerberos, needs a Kerberos configuration that the collector image does not include. See Store a credential for the collector.
  • The module is on. The feature monitoring.hosts covers Windows and Linux hosts.

For hosts that come from a source, set up the source instead; the Windows host appears by itself.

Add a host​

  1. Open Resources › Add resource and choose Windows host.
  2. Name it with the host's DNS name, or set its ip. The collector connects to ip when it is set, otherwise to the resource name.
  3. Choose the Windows account credential and select Create resource.

To check other services than the defaults, change the check's services parameter:

curl -s "${H[@]}" -X PATCH "$BASE/resources/$HOST/checks/windows.services" \
-d '{"params": {"services": ["MSSQLSERVER", "SQLSERVERAGENT", "W3SVC"]}}'

The full wizard: Add a resource.

Next steps​