Get alerted when a Couchbase cluster needs attention
Every hour, WebRun opens Couchbase Capella, checks memory usage and query latency for every bucket and node against the threshold you set, messages the on-call DBA on WhatsApp the moment one breaches, and schedules a maintenance window on Google Calendar.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I get alerted when a Couchbase cluster is under pressure?
WebRun checks Couchbase Capella every hour, comparing memory usage and query latency for every bucket and node against the threshold you set. A breach triggers a WhatsApp message to the on-call DBA naming the bucket or node, and schedules a maintenance window on Google Calendar, so cluster pressure gets a fix booked before it turns into downtime.
- Cluster pressure gets caught within the hour, not after downtime
- Every breach comes with a scheduled fix, not just a notification
- Recovered clusters can have their maintenance window cancelled
Built for database administrators · platform engineers · site reliability engineers · backend engineering 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.couchbase.comin a real browser with your saved login - no setup, no API keys. -
1
Couchbase - check bucket and cluster health
WebRun opens Couchbase to check bucket and cluster health. - Open Couchbase Capella and check cluster and bucket-level health metrics
- Compare memory usage and query latency to your threshold
- Note which bucket or node is closest to breaching
Done when Every cluster and bucket has been checked against its threshold.
- 2
- 3
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 rebalance the cluster or resize a bucket on its own?
No. WebRun only alerts and schedules time to fix it. Rebalancing, resizing, or restarting a node is left to a human.
How does it decide a threshold is breached?
It compares memory usage and query latency for each bucket and node against the threshold you set, so the alert reflects your own capacity plan.
What if the issue resolves before the maintenance window?
It reads live health metrics from Couchbase Capella every run, so a cluster that's recovered 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.