All templates

Automated Time4VPS Resource Usage Alerts

Every hour, WebRun opens the Time4VPS control panel, reads disk, memory, and CPU usage against safe thresholds, posts a Slack warning the moment one runs hot, and logs the reading to a Google Drive doc so the team can see the trend.

Runs on WebRun · Strict Lockdown policy
Every hour, around the clock WebRunorchestrates each step
1 Time4VPS check disk, memory, and CPU usage
2 Google Drive log this hour's reading
3 Slack post a warning to the team
In short

How do I get warned before Time4VPS resource usage takes a site down?

WebRun checks your Time4VPS server's disk, memory, and CPU usage every hour against safe thresholds, logging each reading to Google Drive so trends stay visible. The moment a resource runs hot, it posts a Slack warning naming the figure and threshold crossed, so your team catches strain early, before a site goes down.

  • Resource strain gets a same hour Slack warning
  • Every hourly reading is logged for trend analysis
  • Nothing on the server changes without a human deciding to act

Built for Developers running Time4VPS · small dev teams · system administrators · agencies managing client servers

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens time4vps.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    Time4VPS - check disk, memory, and CPU usage
    time4vps.com
    WebRun in Time4VPS: check disk, memory, and CPU usage
    WebRun checks disk, memory, and CPU usage in Time4VPS.
    • Open the Time4VPS control panel and read disk, memory, and CPU usage
    • Compare each against a safe operating threshold
    • Flag any that are running hot

    Done when Every resource is checked against its threshold for this hour.

  3. 2
    Google Drive - log this hour's reading
    drive.google.com
    WebRun in Google Drive: log this hour's reading
    WebRun logs this hour's reading in Google Drive.
    • Log this hour's reading to the usage tracking doc
    • Keep a running history so trends are visible
    • Note which resources are flagged this hour

    Done when This hour's readings are logged.

  4. 3
    Slack - post a warning to the team
    slack.com
    WebRun in Slack: post a warning to the team
    WebRun posts a resource warning to the team in Slack.
    • Post a warning to the team channel for anything running hot
    • Include the current figure and the threshold it crossed
    • Skip the post if everything is within normal range

    Done when The team has a same hour Slack warning for any resource running hot.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
time4vps.com
ScheduleRuns automatically on this cadence
Every hour, around the clock
DeliveryHow each run's result reaches you
Resource alert · Slack
OutputWhat each run produces - A Slack warning for any Time4VPS resource running hot, with readings logged to Google Drive.
Alert
Setup & safety

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.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Does it upgrade the plan or free up resources automatically?

No. WebRun only reads resource stats and reports them. Upgrading a plan, clearing disk space, or restarting a service stays a manual step your team takes.

Why log to Google Drive as well as posting to Slack?

The Drive log builds an hourly history so the team can see whether a resource is trending toward trouble, not just react to one reading.

Will it alert me for a normal traffic spike?

No. It only posts when a resource actually crosses its threshold, so routine, short lived spikes don't trigger a warning.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.