Plugins

A plugin is one kind of thing the agent can watch. You turn plugins on by listing them in the plugins array of client.config.json, and most take a config block of the same name. See Configuration for the file itself.

Most plugins run inside the agent on a host you control. Cloudflare is different. It runs as a Worker in your own Cloudflare account and pushes straight to daemonitor, so no agent is involved.

Hosts and processes

Plugin	Watches	Runs on
os	CPU, memory, disks, load, network, uptime	every host
pm2	Node processes managed by pm2	hosts running pm2
docker	Compose projects and their containers, health checks, restarts	hosts with Docker
lxc	LXD or Incus instances, one service each	LXD or Incus hosts
logwatch	nginx and Apache access logs for attack patterns	web servers
patroni	Postgres role, replication lag and cluster leader	Patroni nodes
mongodb	MongoDB connections and traffic. Not in the published plugin set	hosts with MongoDB

Websites

Plugin	Watches	Runs on
website	HTTP status, latency, origin behind a CDN, expected and forbidden content	any agent
wordpress	Admin accounts, mu-plugins, crontabs, trashed critical pages	the WordPress host

Office network

Reports from netscan, snmp and tplink that share an IP address merge into one device on the dashboard.

Plugin	Watches	Runs on
netscan	Reachability and latency of LAN devices	an agent on that LAN
snmp	Printers, NAS units and switches over SNMP	an agent on that LAN
tplink	TP-Link extenders, uplink, radios, clients	an agent on that LAN
3cx	3CX PBX and SBC services, SIP ports, tunnels	the 3CX host
ewelink	eWeLink smart plugs. Not in the published plugin set	any agent

Cloud services

Plugin	Watches	Runs on
cloudflare	Zones, WAF, cache, Workers errors, Pages deployments	a Worker in your Cloudflare account
supabase	Supabase Cloud project health, disk, connections. Not released yet	any agent
ga4	Google Analytics users, sessions and views per property	any agent
adsense	AdSense earnings, RPM and zero-earning days	any agent