Linux
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
| Area | Checks | Why it matters |
|---|---|---|
| CPU and memory | Load average and CPU, available memory | A host short of CPU or memory slows everything it runs |
| File systems | Free space per mount point | A full file system stops databases, logs and containers |
| Services | The listed systemd units active, by default sshd, podman and chronyd | A stopped unit is an outage even when the host is up |
| Updates | Pending package updates found by a check-only dnf or apt run, reboot required after a new kernel | Feeds the Track updates and advisories page; Excubius never installs a package |
| Security | Failed SSH logins, sudo commands and new users from the journal; hardening posture: SSH root login and password authentication, SELinux, firewalld and listening ports | Early 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
| Source | Feeds |
|---|---|
| New Relic | Load and CPU, memory and file system free space of the hosts its infrastructure agent reports |
| NinjaOne | Minutes since the device last contacted NinjaOne 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 SSH | Every 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.
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
sudoto a shell. The checks run their commands as that user; they do not callsudo. - Read access to the system journal for the authentication events check, for example membership in the
systemd-journalgroup. 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.hostscovers 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
- Open Resources › Add resource and choose Linux host.
- Name it with the host's DNS name, or set its
ip, andssh_portif it is not 22. The collector connects toipwhen it is set, otherwise to the resource name. - 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.