Automated Servers.com Resource Usage Alerts
Every hour, WebRun opens the Servers.com control panel, reads CPU, memory, and bandwidth usage across your servers, posts a warning to Microsoft Teams the moment one runs hot, and logs it on a Trello card so the follow up doesn't get lost.
How do I get warned before Servers.com resource usage affects customers?
WebRun checks CPU, memory, and bandwidth usage across your Servers.com fleet every hour against safe thresholds. It posts a warning to Microsoft Teams the moment any server runs hot and logs a Trello card to track the follow up, so resource strain gets caught and actually resolved instead of scrolling past in a chat channel.
- Resource strain gets a same hour Teams warning
- Every flagged server stays tracked on Trello until resolved
- Nothing on the server changes without a human deciding to act
Built for Infrastructure teams · hosting providers · enterprises running dedicated 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
www.servers.comin a real browser with your saved login - no setup, no API keys. -
1
Servers.com - check CPU, memory, and bandwidth usage
WebRun checks CPU, memory, and bandwidth usage in Servers.com. - Open the Servers.com control panel and read CPU, memory, and bandwidth usage for every server
- Compare each against a safe operating threshold
- Flag any that are running hot
Done when Every server's resource usage is checked for this hour.
-
2
Microsoft Teams - post a warning to the team
WebRun posts a warning to the team in Microsoft Teams. - Post a warning to the infrastructure channel for anything running hot
- Include the server name, figure, and threshold crossed
- Skip the post if everything is within normal range
Done when The team has a same hour Teams warning for any resource running hot.
-
3
Trello - log it for follow up
WebRun logs the issue for follow up in Trello. - Add a card for the flagged server if one doesn't already exist
- Update the existing card if the issue is ongoing
- Leave resizing or restarting the server to the team
Done when A Trello card tracks every flagged server until it's resolved.
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 resize or restart a server that's running hot?
No. WebRun only reads resource stats and reports them. Resizing, restarting, or reconfiguring a server stays a manual step your team takes.
Why track it on Trello as well as posting to Teams?
The Teams post gets the team's attention immediately. The Trello card makes sure the issue stays tracked until someone actually resolves it.
Will it alert me for normal traffic spikes?
No. It only posts when a resource crosses its threshold, so a brief, expected spike that stays within range doesn't trigger a warning.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.