A target's database, asked on its server with the database's own client: its size, its collections (or tables), the connections, the server's uptime and version, the operations running for too long -- mongosh for MongoDB, mysql for MySQL / MariaDB.
class MMO\admin\monitoring\probes\DatabaseProbe extends MMO\admin\monitoring\aProbe
Only targets with a `database` (deploy.json) are asked. How to reach it is [`$uri`](https://mmoframework.fr/en/documentation/mmo.admin/php/monitoring/probes/DatabaseProbe.md#databaseprobe-uri): `mongodb://127.0.0.1:27017`
by default, a target's own `databaseUri` in the hub's credentials file when it needs a user and a password
(`hub.credentials.json`, never `hub.json`). MySQL reads its user from the server's `~/.my.cnf`, as `mysqldump` does
for mmo.admin's backups.
Cumulative numbers (operations, queries since the server started) are counters: the hub makes them per second.
Metrics: `db.dataMb`, `db.storageMb`, `db.indexMb`, `db.objects`, `db.collections`, `db.connections.current`,
`db.connections.usedPercent`, `db.uptimeDays`, `db.slowOps`, and the rates `db.opsPerSec` / `db.queriesPerSec`,
`db.slowQueriesPerSec`. Facts: `engine`, `database`, `dbVersion`. Details: `collections` (the largest, with their counts and sizes).