Automated ClickHouse Capacity Alerts
Every hour, WebRun opens the ClickHouse Cloud console, checks disk usage and p99 query latency for every service against the threshold you set, posts a Teams alert naming any service near capacity, and schedules a maintenance window on Google Calendar for a breach.
How do I get alerted before a ClickHouse service runs out of disk space?
WebRun checks ClickHouse Cloud every hour, comparing disk usage and query latency for every service against the threshold you set. A breach posts a Microsoft Teams alert naming the service and how close it is to capacity, and schedules a maintenance window on Google Calendar, so a service never runs out of headroom without warning.
- Capacity issues get caught within the hour, not after an outage
- Every breach comes with a scheduled maintenance window, not just a ping
- Resolved services can have their maintenance window cancelled
Built for platform engineers · data engineering teams · site reliability engineers · database administrators
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
console.clickhouse.cloudin a real browser with your saved login - no setup, no API keys. -
1
ClickHouse - check query latency and disk usage
WebRun opens ClickHouse to check query latency and disk usage. - Open the ClickHouse Cloud console and check disk usage across services
- Check p99 query latency against baseline
- Note which service is closest to its capacity threshold
Done when Every service has been checked against its capacity threshold.
-
2
Microsoft Teams - alert on a threshold breach
WebRun posts to Microsoft Teams to alert on a threshold breach. - Post an alert to the platform channel naming the service and how close it is to threshold
- Include the current disk usage and query latency
Done when The team has a Teams alert for every service near threshold.
-
3
Google Calendar - schedule a maintenance window
WebRun opens Google Calendar to schedule a maintenance window. - Schedule a maintenance window once a service crosses its threshold
- Invite the platform engineer on call
Done when A maintenance window is scheduled for every service over threshold.
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
Will it resize the cluster or add storage on its own?
No. WebRun only reports usage against threshold. Resizing a service or adding storage is left to a human.
How does it decide a service needs attention?
It compares disk usage and p99 query latency against the threshold you set per service, so the alert reflects your own capacity plan, not a generic default.
What if usage drops back down before the maintenance window?
It reads live usage from ClickHouse Cloud every run, so a service that's back under threshold before the scheduled window can have the meeting cancelled.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.