Capabilities · Databases
See what your databases are doing, and why.
PostgreSQL, MySQL, SQL Server and Redis, read through their own system views and server commands with a monitoring account. Never the data in your tables or keys.
The task
- See what is slow or blocked right now: sessions, waits and locks, sampled over a few seconds.
- Read the heaviest queries and their plans, estimated without running them.
- Find recent deadlocks with the statements involved, masked, where the database records them.
- Check replication and availability: PostgreSQL replicas, MySQL replication and Group Replication, SQL Server availability groups, failover clusters and log shipping.
- Tune settings to the machine’s memory and cores, then ask whether the change helped, with a before-and-after verdict.
- Turn a pasted permission error into the grant that should fix it, for you to check before applying.
- Review security settings, bloat and upkeep, and how long until the disk fills.
Who it helps
DBAs and SRE teams, developers chasing a slow query, QA and release managers checking health before a release, and security teams preparing an audit.
Supported sources
| Database | What Verbiqo reads | What it needs |
|---|---|---|
| PostgreSQL | Activity, locks, statements, replication, table statistics and settings from the catalog and statistics views. Plans of statements from PostgreSQL 16, without running them. | pg_monitor. A superuser is refused. Plans also need pg_read_all_data |
| MySQL 8.0 and later | Sessions, locks, replication, statement statistics and settings from performance_schema and sys. MySQL 5.7 is not supported. | PROCESS, REPLICATION CLIENT and reads on performance_schema and sys. An account that can write is refused |
| SQL Server 2016 to 2022 | Requests and blocking, waits, the heaviest queries, databases and logs, availability groups, backups and Agent jobs from the system views. Every statement is planned before it runs. | VIEW SERVER STATE, VIEW ANY DEFINITION, SHOWPLAN. A login that can write or administer is refused |
| Redis, Valkey | Memory and eviction, the slow log and latency, clients, persistence and replication, through commands on a read list. Never keys or values. | An ACL user without admin rights. One that can administer is refused |
Example
SQL Server 2022 · edited excerpt from a real transcript, lab server
Question
Orders are timing out in the shop database, what’s going on?
Checks Verbiqo ran
- Requests and blocking, sampled once a second for 10 seconds
- The heaviest statements and the indexes the optimizer asked for
- Deadlocks recorded by system_health, statements masked
Findings Measured
- Warning: the transaction log of shop is 65% full, with no log backup in the last day.
- Note: 2 deadlocks on
dbo.accountsin the last week.
Explanation Your model
Two deadlocks were recorded on dbo.accounts in the last week; these can abort transactions. The sample captured no active or blocked requests, so it does not establish the cause of the reported timeouts. The log is 65% full and its backup history needs review.
Limits stated
No requests were active or blocked during the sample, so a timeout happening at another moment would not show in it.
Limitations
- Verbiqo sees what the monitoring account can see, and says what it could not.
- It never runs your statements or applies a fix: it recommends a statement, with its risk and what to check first, for a person to decide on.
- Plans of application statements need an extra grant on PostgreSQL and MySQL.
- “Did the changes help?” compares readings kept on your computer, so it needs a reading from before the change and enough work after it.
Next step
Read how to connect each database, or try it on your own.