Database health
What the engine is doing right now — connections, running queries, slow queries and uptime — and a day of history.
Health, at the top right of the Databases screen, answers one question: is the database the reason the site is slow? It reads live counters from the engine, so it is current, not a cached summary.
One tab per engine
The buttons under the title are the engines installed on this server —
MySQL, MongoDB, PostgreSQL. Each has its own counters; switching
tabs reloads the numbers for that engine. The URL carries the choice
(?engine=postgresql), so a tab is linkable.
The verdict banner
The widest thing on the screen is a plain-English judgement — Healthy · Nothing needs your attention right now — with the engine's exact version string, whether the service is Running, and how long it has been up.
Read this first. If it says healthy, the slow page is not the database, and the application's logs are the next place to look.
The four cards
| Card | What it counts | What to watch for |
|---|---|---|
| Connections | Open connections, against the engine's configured limit — 2 of 151. | A bar creeping toward the limit. New connections fail outright once it is reached. |
| Running queries | Connections doing work right now. Idle ones are counted, not listed. | A number that stays high rather than spiking and settling. |
| Slow queries | Queries over the engine's slow threshold, with a per-hour rate. | Anything above zero that keeps climbing — that is a missing index, usually. |
| Uptime | Time since the engine last restarted. | A figure that keeps resetting. The engine is crashing, most likely on memory. |
Each card also labels itself Normal when the value is unremarkable, which saves you knowing what a reasonable connection count looks like.
Connections include the panel's own
OSS Panel polls the engine to draw this page, so a completely idle server still shows a connection or two. A baseline of two is not a leak.
Running queries
Underneath, the live list: every connection currently executing something. On a healthy idle server it reads Nothing is running right now.
This is where a stuck query shows itself — one statement sitting in the list for minutes while everything else waits behind it.
Last 24 hours
The chart plots queries per second, connections, and running threads, sampled every five minutes. Above it, three figures for queries per second — Current, Average and Peak — which together say whether right now is normal for this server.
Drag the handles below the chart, or scroll on it, to zoom into a time range. That is the quick way to answer "what was the database doing at 06:40, when the site went slow?"
History starts when the engine does
The samples are kept by the panel, not reconstructed from the engine, so a freshly installed engine — or one that has just restarted — has a short chart. Uptime on the card above tells you how much history to expect.