Overview
Watchman Tower’s server agent is a lightweight Go-based collector that sends basic server telemetry to the platform. Today, it is best understood as a practical infrastructure signal source for:- CPU usage
- memory usage
- disk usage
- network transfer
- load averages
- uptime
- swap usage
- top resource-consuming processes
The current server agent is functional, but still intentionally simple. It is
useful for basic server visibility today, while richer server intelligence can
evolve later without overpromising in docs now.
How It Fits Into Watchman Tower
The server agent complements Watchman Tower’s broader monitoring workflow by adding host-side telemetry. That means teams can combine:- external uptime and status checks
- domain and SSL visibility
- internal WordPress signals when needed
- server-side telemetry from the agent
Current Delivery Model
The current agent:- runs as a standalone Go binary
- collects metrics directly from the host
- sends metrics to Watchman Tower over HTTPS
- uses a server-specific API key
- follows the interval returned by the Watchman Tower API
What the Platform Stores Today
On the backend side, Watchman Tower currently stores and surfaces:- the latest server version reported by the agent
- current server status snapshots through Redis-backed cached data
- recent server stat entries for historical views
- alerting structures tied to server resources
Current Limitations
This docs section intentionally reflects the current implementation. It does not claim support for:- custom user-defined metrics
- deep service autodiscovery
- advanced process inventory beyond the sampled top processes
- Noema-based server interpretation today