Automated Elastic Cluster Capacity Tracking
Every night, WebRun signs into Elastic Cloud, opens each deployment, records storage used against storage allocated plus the cluster health state, writes a dated row per deployment into Airtable, works out the growth rate from the last 14 days, and pings Telegram when a cluster is on track to fill within your warning window.
How do I know before an Elasticsearch cluster runs out of storage?
WebRun signs into Elastic Cloud every night, reads storage used against storage allocated plus the health state of each deployment, and writes a dated row into Airtable. It calculates growth from the last 14 nights and pings Telegram when a cluster is on track to fill within two weeks.
- A filling cluster is flagged two weeks out, not at 100 percent
- Nightly readings build a growth record you can plan capacity from
- Healthy weeks stay silent so the alert keeps its meaning
Built for platform engineers · SRE teams · data engineers · DevOps teams
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
cloud.elastic.coin a real browser with your saved login - no setup, no API keys. -
1
Elastic - read storage and health per deployment
WebRun opens Elastic to read storage and health per deployment. - Sign into Elastic Cloud and open the list of deployments
- For each deployment, record storage used against storage allocated, and the current health state
- Note the deployment name, region, and version
- Flag any deployment showing a health state other than healthy
Done when Every deployment has tonight's storage figures and health state.
-
2
Airtable - log a dated row per cluster
WebRun opens Airtable to log a dated row per cluster. - Open your Airtable infrastructure base
- Add a dated row per deployment with storage used, storage allocated, percentage full, and health
- Calculate the average daily growth from the last 14 rows for that deployment
- Estimate the days remaining until the deployment reaches its allocated storage
Done when Tonight's rows are written and each deployment has a days-remaining estimate.
-
3
Telegram - ping when a cluster will fill
WebRun opens Telegram to ping when a cluster will fill. - Send a short ping naming any deployment estimated to fill within 14 days
- Include current percentage full, average daily growth, and days remaining
- Also ping when a deployment reports a health state other than healthy
- Send nothing when every cluster is healthy and has room
Done when You have been pinged about at-risk clusters, or nothing needed sending.
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 or restart a deployment?
No. WebRun reads deployment storage and health and writes only to your Airtable base. Resizing, scaling, and restarting stay manual decisions your team makes in Elastic Cloud.
How does it know a cluster is about to fill?
It compares tonight's storage against the last 14 nightly readings in Airtable, takes the average daily growth, and estimates days remaining against the allocated storage.
Will it ping me every night?
No. The Airtable log is written silently every night. Telegram only fires when a cluster is estimated to fill within 14 days or reports an unhealthy state.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.