Configure

Servers & agents

The nodes DriftSense knows about — local (this box) and SSH agents (remote servers scanned over a restricted-key SSH connection). Add one at a time or bulk-import a list of hostnames sharing a single key.

Two flavors: Local = scanner runs on the same box as the file being watched (fast, zero-network). SSH agent = scanner SSHes into the target box using a restricted key; only footprint on that box is one authorized_keys entry. Great for stealth deployment where you don't want developers on the monitored box to see DriftSense installed. Paste a PEM key below to store it in the DB (encrypted). Test any row with the "Test" button.

Single-server form Bulk import

Add server

Pick local for the DriftSense host itself, or ssh_agent for anything remote.

Quick help

The three most common setup shapes.

Same server — pick local, skip all the SSH fields. This is the default install monitoring itself.

Remote via SSH — pick ssh_agent, fill ssh_host + ssh_user, and either paste the PEM key below (encrypted at rest with the master key) OR give a path to a keyfile on disk.

Test the connection — after saving, hit the "Test" button on the server row. Runs an SSH probe and reports back inline.

Bulk import 20 hosts at once — switch to the "Bulk import" tab. Paste hostnames, one shared key, one base scan config. DriftSense fans out and starts scanning within 5 minutes.

Registered servers

3 total.

Kind / status	Name	Reach	Key	Last scan	Actions
local active	local	@localhost:22	-	never	Edit
ssh_agent active	localhost-ssh-agent	root@127.0.0.1:22	/etc/drift_sense/keys/agent_key	Jul 12 07:15	Edit
ssh_agent active	WebSTLs (webstls.com)	root@webstls.com:22	/etc/drift_sense/keys/webstls_agent_key	Jul 12 07:15	Edit