A hosting account that runs out of disk or bandwidth takes the site down just as surely as a server crash, but it usually gives you warning first. Connect your WHM server to TLDTrack and we watch the resource usage on every cPanel account for you, and shout while there is still time to act, not after the site has already stopped.
What it is
Read more
Why it matters
Read more
What gets checked, and when it alerts
A scheduled job checks every connected account and raises an alert when any of these thresholds is crossed:
- Disk usage. A warning at 75% full (
whm_disk_warning), and a critical at 90% full (whm_disk_critical), where the site may stop working. - Bandwidth usage. A warning at 75% used (
whm_bandwidth_warning) and a critical at 90% (whm_bandwidth_critical), noting that monthly bandwidth resets on the 1st. - Projected bandwidth (
whm_bandwidth_projected). Based on usage so far this month, if the account is on track to reach 85% or more by month end it warns early, and if it is projected to exceed 100% it is treated as critical, so you see an overage coming before it arrives. - Account suspended (
whm_account_suspended). A critical alert if a cPanel account has been suspended.
You will not be spammed with the same warning
How the alerts reach you
WHM alerts use the same notification plumbing as the rest of TLDTrack. They are batched per organisation into a single message so ten accounts crossing a limit do not mean ten separate emails, and sent to your notification contacts who have WHM alerts switched on, by email and, if you have SMS credits and a contact opted in, by text. Every account's usage is also visible in the dashboard whenever you want to check it, alert or no alert.
Connecting a server
You will need a WHM API token from your server (created in WHM under API tokens). Then:
-
1
In TLDTrack, open the WHM servers page and choose to add a server.
-
2
Enter a label, the hostname, the port (usually 2087), the username (usually
root), and paste the API token. Leave SSL on unless you have a reason not to. -
3
Use Test connection to confirm the credentials work before saving. TLDTrack reports back the WHM version on success.
-
4
Save. You are taken to a preview of the accounts on the server, showing which already match domains in your portfolio and which are new.
-
5
Select the accounts you want to import as domains. From then on they are watched, and the limit checks run automatically.
-
6
Optionally, record the price of each hosting package.
Read-only, and your token is encrypted
Keeping it current
Once a server is connected, its accounts are re-synced automatically so usage figures stay fresh for the limit checks, and you can trigger a manual re-sync at any time from the server's page. If an account shows up that you do not want tracked, you can dismiss it, which tombstones it so a future sync never re-imports it.
Where to set this up
Good to know
- The connection is strictly read-only. TLDTrack reads usage; it never changes anything on your server.
- Disk and bandwidth both warn at 75% and go critical at 90%; bandwidth also projects the month-end position and warns early.
- Alerts are batched per organisation and only re-fire as usage climbs past each new 5% step, so they stay useful rather than noisy.
- You can connect several servers, import their accounts as monitored domains, and record package pricing.