System Health
System Health is a single screen that answers one question at a glance: is the whole system up? It runs a set of live probes against the parts WaDesk depends on — the database, cache, queue, the Node WhatsApp bridge, and media storage — and shows you an overall status plus the recent activity of the platform. This is a v1.2 feature.
Overview
Rather than logging into a server to check whether services are running, you open one page and read the result. System Health probes each critical dependency in real time and rolls the results into an overall status banner, so you can confirm everything is healthy — or immediately spot what is broken.
You will find it in the admin sidebar under Admin → System Health (URL /admin/health).
Core Probes
Each probe is independent and tolerant — one failing probe never takes down the page, it just reports that one part as unhealthy. The core probes are:
| Probe | What it checks |
|---|---|
| Database | That the database responds, reported with its ping time. |
| Cache | A live read/write round-trip against the cache. |
| Queue | The number of pending jobs and failed jobs waiting in the queue. |
| Node WhatsApp bridge | The bridge is pinged — any HTTP response means it is alive; a connection refused means it is down. |
| Media storage | A full write / read / delete round-trip against storage, reported with its timing. |
Tip: The Node WhatsApp bridge probe treats any HTTP reply as healthy — it is checking that the process is reachable, not that a particular response came back. So even an error response confirms the bridge is up; only a refused connection marks it down.
Overall Status & Activity
At the top of the page an overall status banner summarises every probe into one of three states:
- Operational — everything is healthy.
- Degraded — something is impaired but the platform is still running.
- Down — a critical dependency has failed.
Beneath the banner, last-24h activity counters show how busy the platform has been: messages, AI calls, conversations, and webhooks. Response-time bars visualise how quickly each probe responded, so a slow database or storage round-trip is easy to see.
Throughput & Engine Status
The page also shows operational detail about messaging:
- A 14-day message-throughput chart, so you can see the volume trend and whether sending has stalled.
- Per-engine connected-number cards for each messaging engine — Unofficial API, WhatsApp Cloud, and Twilio — each showing connected numbers versus the total configured. This is how you catch numbers that have silently disconnected.
Host Vitals
A host-vitals panel reports the environment the platform is running in, so you can spot a server-level problem such as a disk filling up:
- PHP version and Laravel version.
- Free disk space.
- Memory limit.
Auto-Refresh
The page auto-refreshes every 20 seconds, so you can leave it open during an incident or a deployment and watch the status update on its own without reloading.
When to Use It
Open System Health to instantly catch problems such as:
- a down Node WhatsApp bridge — the reason sends and inbound messages stop flowing;
- a backlog of failed jobs in the queue;
- a full disk, before it causes wider failures;
- numbers that have disconnected, shown in the per-engine cards.
Plan & Permission
System Health is platform admin only. It reports on the whole install — servers, queues, and every engine — so it is not available inside customer workspaces.
Related Pages
- AI Usage Dashboard — platform-wide AI token and cost analytics.
- Security & Audit Log — security posture and the record of sensitive actions.