Documentation

Overview

A summary of the server — package count, running services, SSL certificates, and cron jobs. Resource gauges show current CPU, memory, and disk usage.

Packages

Every package installed via apt/dpkg with its version. Use the search box to find specific packages. Version comparison against latest known versions is shown for tracked packages.

Services

All systemd services with their current status (running, stopped, failed). Filter by status to quickly find failed services. Note: UFW firewall may show as stopped even when active — verify with sudo ufw status on the server.

SSL

SSL certificates detected from your Nginx config, with issuer, expiry date, and days remaining. A color-coded bar shows urgency — green is healthy, yellow is expiring soon, red is critical.

Cron

Scheduled cron jobs from crontab and /etc/cron.d/, showing the user, schedule, and command for each job. The Last Run column shows how long ago each job was last invoked, based on system journal logs from the last 24 hours. Note: Last Run shows when the job started, not whether it succeeded. A job that runs and fails silently will still show a recent Last Run time. Jobs showing — have not run in the last 24 hours or could not be matched to a journal entry.

Containers

Docker containers running on the server, showing image name, tag, status, and exposed ports. Containers using the latest tag are highlighted — pinning to a specific version is recommended for production. Note: Docker must be installed before running the agent installer for container detection to work automatically. If you install Docker after the agent, re-run the install command to enable container visibility.

History

A timeline of the last 50 scans for this server. Select any two scans and click Compare to see a diff of what changed between them — packages added or removed, services that changed status, SSL certs, and cron jobs.

Requirements

PM2 installed and running on the server. DriftHalt agent v1.2.3 or later.

Setup

SSH into your server and run the following commands. Replace YOUR_USERNAME with the Linux user that runs PM2 on your server (commonly ubuntu, deploy, or your personal username).

sudo bash -c 'cat > /usr/local/bin/drifthalt-pm2-info << '\''EOF'\''
          #!/bin/bash
          PM2_HOME=/home/YOUR_USERNAME/.pm2 pm2 jlist
          EOF'
          sudo chmod +x /usr/local/bin/drifthalt-pm2-info
          sudo chown YOUR_USERNAME:YOUR_USERNAME /usr/local/bin/drifthalt-pm2-info

echo "drifthalt ALL=(YOUR_USERNAME) NOPASSWD: /usr/local/bin/drifthalt-pm2-info" | sudo tee /etc/sudoers.d/drifthalt-pm2
          sudo chmod 440 /etc/sudoers.d/drifthalt-pm2

Once complete, PM2 data will appear in your next agent scan (within 15 minutes). No agent restart required.

What gets monitored

Process name and current status. Restart count — alerts when 3 or more restarts occur in a single scan cycle. Memory usage per process.

Alerts

When a PM2 process restarts 3 or more times between scans, DriftHalt sends an email and webhook notification with the process name, restart count, and a link to your dashboard.