Windows
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
| Area | Checks | Why it matters |
|---|---|---|
| CPU and memory | CPU utilization, available memory | A host short of CPU or memory slows everything it runs |
| Disks | Free space per volume, read and write latency | A full volume stops databases and logs; slow disks are the usual cause of slow SQL Server data files |
| Services | The listed services running, by default MSSQLSERVER, SQLSERVERAGENT, SQLBrowser and ReportServer | A stopped service is an outage even when the host is up |
| Updates | Pending reboot, pending Windows updates found by a search, operating system version and edition | Feeds the Track updates and advisories page; Excubius never installs an update |
| Security | Security 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 administrators | Early 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
| Source | Feeds |
|---|---|
| New Relic | CPU, memory and disk free space of the hosts its infrastructure agent reports |
| NinjaOne | Minutes since the device last contacted NinjaOne, pending patches and NinjaOne alerts, in the NinjaOne module |
| Azure Monitor | Azure VMs: power state, CPU and pending updates from Azure Update Manager, in the Azure module |
| Native collector over WinRM | Every 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.
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
authset tonegotiateorntlm. 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.hostscovers 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
- Open Resources › Add resource and choose Windows host.
- Name it with the host's DNS name, or set its
ip. The collector connects toipwhen it is set, otherwise to the resource name. - 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.