Automated PhoenixNAP Server Uptime Alerts
Every hour, WebRun opens the PhoenixNAP client portal, reads server uptime and resource usage across your bare metal and cloud instances, logs the readings to a Google Sheet, and drafts a Gmail alert the moment a server crosses a safe threshold.
How do I get warned before a PhoenixNAP server issue turns into an outage?
WebRun checks every PhoenixNAP server's uptime and resource usage every hour, logging each reading to a Google Sheet so trends stay visible. The moment a server crosses a safe threshold, it drafts a Gmail alert naming the server and the figure that triggered it, so your team catches strain early instead of discovering an outage after it happens.
- Server strain gets caught within the hour it starts
- Every hourly reading is logged for trend analysis
- Restarting or resizing a server always stays a human decision
Built for Infrastructure teams · IT operations · enterprises running bare metal servers · DevOps engineers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
phoenixnap.comin a real browser with your saved login - no setup, no API keys. -
1
PhoenixNAP - check server uptime and resource usage
phoenixnap.com
WebRun checks server uptime and resource usage in PhoenixNAP. - Open the PhoenixNAP client portal and read uptime and resource usage for every server
- Compare each against a safe operating threshold
- Flag anything running hot or reporting downtime
Done when Every server's status is checked for this hour.
-
2
Google Sheets - log this hour's readings
google.com
WebRun logs this hour's readings in Google Sheets. - Log this hour's reading for every server
- Keep a running history so trends are visible
- Note which servers are flagged this hour
Done when This hour's readings are logged for every server.
-
3
Gmail - draft an alert for anything critical
gmail.com
WebRun drafts an alert in Gmail for anything critical. - Draft an alert for any server that's flagged
- Include the server name, the figure, and the threshold it crossed
- Leave restarting or resizing the server to the team
Done when A draft alert is waiting for any server that needs attention.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it restart or resize a server that's running hot?
No. WebRun only reads server status and drafts an alert. Restarting, resizing, or reconfiguring a server stays a manual step your team takes.
Why log to a sheet as well as sending an alert?
The sheet builds an hourly history so the team can see whether a server is trending toward trouble, not just react to a single reading.
Will it alert for a brief, normal spike?
No. It only flags a server once it actually crosses the safe threshold, so routine, short lived spikes don't trigger an alert.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.