Skip to main content

Install the Wakora agent on SUSE and openSUSE

Tested on openSUSE Leap 15.6 on amd64. SUSE Linux Enterprise shares the same tooling (zypper, systemd) and behaves the same way.

Install​

curl -fsSL https://get.wakora.io | bash -s -- --key <YOUR_TEAM_KEY>

curl and openssl are the prerequisites. The installer writes and enables wakora-agent.service, registers the host and starts the service; the unit is hardened the same way as on every systemd distribution (read-only system tree except the agent's own directories, a CPU quota, lowered priority, an OOM score that puts the agent first in line).

What the agent finds on a SUSE host​

  • the package inventory from rpm, pending updates from zypper list-updates and the count of patches in the security category from zypper list-patches;
  • whether /run/reboot-needed exists, the flag zypper itself sets when a patch needs a reboot, so the "host is waiting for a reboot" rule works out of the box here;
  • systemd units, failed units, OOM kills, SSH activity from the journal;
  • every recognised service from the catalog: Apache (httpd on SUSE), MariaDB, PHP-FPM, Postfix, Docker, and the rest;
  • host metrics: CPU, memory, swap, disks, load, network, top processes.

Verify​

wakora doctor
systemctl status wakora-agent
tail -f /var/log/wakora/agent.log

Notes​

  • A repository whose metadata is stale makes zypper list-updates print a warning; the probe tolerates that and still reports the counts it can read.
  • The agent runs zypper non-interactively in query mode only; it never applies a patch.
  • Apache metrics carry the svc.httpd.* prefix on SUSE, because the process is httpd. See Monitoring Apache.

Next: First start, Fleet deployment.