Server Monitoring

Install the PulseBeacon agent and stream host metrics every minute.

Server monitoring is agent-based. Each server sends metric payloads to PulseBeacon every minute, then PulseBeacon evaluates offline state and high resource thresholds.

Install Flow

Add a server in PulseBeacon, copy its server code, run the installer command, then confirm the server shows recent heartbeat data.

Install the Agent

Interactive install

curl -s https://pulsebeacon.io/agent/pulsebeacon-agent.sh | sudo bash -s --

Non-interactive install

curl -s https://pulsebeacon.io/agent/pulsebeacon-agent.sh | sudo bash -s -- --code=YOUR_SERVER_CODE

Agent operations

# upgrade / refresh script + cron
curl -s https://pulsebeacon.io/agent/pulsebeacon-agent.sh | sudo bash -s -- --upgrade --code=YOUR_SERVER_CODE

# status + server-code validation
curl -s https://pulsebeacon.io/agent/pulsebeacon-agent.sh | sudo bash -s -- --status --code=YOUR_SERVER_CODE

# uninstall
curl -s https://pulsebeacon.io/agent/pulsebeacon-agent.sh | sudo bash -s -- --uninstall

What Gets Collected

CPU usage and load
Memory and swap usage
Disk utilization
Network activity
Uptime and process counts

Default Server Alert Signals

Signal	Threshold	Event
Offline	No recent metrics received	`server_offline` / `server_online`
High CPU	Resource usage crosses threshold	`server_high_cpu`
High memory	Resource usage crosses threshold	`server_high_mem`
High disk	Resource usage crosses threshold	`server_high_disk`

Use notification rules to route these events to the right teams.

Troubleshooting

If server stays offline, verify outbound access to your PulseBeacon app domain on 80/443.
Check logs: sudo tail -n 50 /var/log/pulsebeacon-agent.log
Validate server code by running installer status mode.
Ensure host scheduler runs every minute (cron entry for pulsebeacon-agent.sh).