Pulse streams your server's layer 4 and layer 7 traffic to live graphs. One command to install, nothing to open inbound, and a flood shows up the second it starts.
Raw transport volume and application behaviour are different questions. Pulse graphs them separately, so an HTTP flood and a bandwidth spike never hide inside one line.
Throughput, packets per second, live connection count, and a peak-preserved SYN rate that makes a volumetric flood visible the instant it lands — read straight from the kernel.
Request rate, the 2xx/4xx/5xx status mix, and latency — tailed from your web server's access log. A surge of 5xx or a slow-loris stall shows here long before bandwidth moves.
The agent reads its own host's counters and one log file. It never scans, never probes, never opens a port. Nothing on your server accepts an inbound connection from us.
Pick a scheme per monitor — try them on the live wall above. Shared status pages keep whichever you chose.
Create a monitor, run one command on your box, and the graphs fill in as the agent reports.
Create your first monitor