The MySQL and MariaDB Databases page lists databases discovered on a monitored server. Use it for inventory review and database-level context.
Workflow
- Open Databases.
- Review database names and status information where available.
- Use Queries, I/O, Permissions, and Health Checks for follow-up.
How To Use MySQL And MariaDB Database Inventory
The Databases page gives inventory context for a monitored MySQL or MariaDB server. Use it to confirm which databases Mini DBA discovered, which environment you are viewing, and which database should be investigated during a performance or availability issue.
Inventory context is especially important on shared servers where multiple applications use the same instance. If an alert or expensive query references a database name, this page helps you confirm the affected workload before opening Queries, Activity, or Health Checks.
If an expected database is missing, check the connection target, account privileges, and whether the database has been excluded or is hidden by permissions. Cloud-hosted MySQL and MariaDB services may also expose metadata differently from self-managed servers.
MySQL And MariaDB Databases FAQ
Is this page for performance tuning?
It is mainly inventory context. Use Queries, Activity, InnoDB, I/O, and Health Checks for tuning evidence.
Why is a database missing?
The monitoring account may not have visibility, the connection may target a different server, or collection may not have completed.
Can this page help with audits?
Yes. It can support estate inventory checks when combined with Reports and Enterprise View.
Next Steps From Inventory
After confirming the MySQL or MariaDB database list, choose the page that matches the symptom. Use Activity for live sessions, Queries for SQL workload, InnoDB for locks and transactions, I/O for storage pressure, and Health Checks for operational risks. If inventory is incomplete, review connection target, grants, and collection status.