Skip to main content
Version: 0.4 · current

Linux

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

The Linux module watches Linux hosts: load, memory and file systems, the systemd units that must run, pending package updates and reboots, authentication events and hardening. Its values come from the sources you already have, New Relic, NinjaOne and Azure Monitor, or from the native collector over SSH, which is experimental in this release.

What it monitors​

AreaChecksWhy it matters
CPU and memoryLoad average and CPU, available memoryA host short of CPU or memory slows everything it runs
File systemsFree space per mount pointA full file system stops databases, logs and containers
ServicesThe listed systemd units active, by default sshd, podman and chronydA stopped unit is an outage even when the host is up
UpdatesPending package updates found by a check-only dnf or apt run, reboot required after a new kernelFeeds the Track updates and advisories page; Excubius never installs a package
SecurityFailed SSH logins, sudo commands and new users from the journal; hardening posture: SSH root login and password authentication, SELinux, firewalld and listening portsEarly signs of an attack, and settings that make one easier

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

Where the values come from​

SourceFeeds
New RelicLoad and CPU, memory and file system free space of the hosts its infrastructure agent reports
NinjaOneMinutes since the device last contacted NinjaOne 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 SSHEvery check of the module

macOS hosts appear from New Relic and NinjaOne with their alerts and NinjaOne's last contact; the Linux checks do not apply to them.

warning

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

Before you begin​

For collection over SSH:

  • A dedicated, non-root user on each host that signs in with a key, in a dedicated group, without sudo to a shell. The checks run their commands as that user; they do not call sudo.
  • Read access to the system journal for the authentication events check, for example membership in the systemd-journal group. Without it the check sees no events.
  • An SSH key credential with the host keys pinned in the connection option known_hosts. Use one key per entity. See Store a credential for the collector.
  • Network. The Excubius server reaches the host on TCP 22, or on the port in the host's ssh_port.
  • The module is on. The feature monitoring.hosts covers Windows and Linux hosts.

Pending updates are read with dnf or apt; other package managers are not covered. The hardening check reads the effective SSH server settings with sshd -T, which on many distributions only root can run; review its first results before you rely on them.

Add a host​

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

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

curl -s "${H[@]}" -X PATCH "$BASE/resources/$HOST/checks/linux.services" \
-d '{"params": {"units": ["sshd", "postgresql", "chronyd"]}}'

The full wizard: Add a resource.

Next steps​