DBSnoop’s main function is to monitor databases, so we poured all of our experience in it. It comes to show on how our MySQL monitor works.
Currently, we support:
- MySQL 5.5~5.7
- MariaDB 5.5~10.3
- PerconaDB 5.5~5.7
If your database suddenly restarts, it’ll throw an alert just to make sure it doesn’t go by unnoticed. This helps a lot for further investigation on why it restarted.
By monitoring the processlist, we can establish a range of very important metrics. This includes the number and state of connected threads, query statistics and, especially, gather info for our Query Catalog.
With this info and the alerts that they generate, it’ll be quite easy to find room for improvements in your operation.
As a byproduct of processlist monitoring, we build a comprehensive report of who is acessing what in your database, ready for any auditing that should take place. And if someone access something that he wasn’t suposed to, we’ll throw an alert for you.
Disk Consumption Growth
By gathering info about how indexes, tables and schemas are stored in your disk, we can estimate how long it’ll take to fill up the current disk. And also by much do we need to expand it to keep it safe for the next few days, months or even years. It’s up to you.
Get alerts whenever replication stops working, or whenever the replication slave gets further from the master.
Transactions and Locks
We monitor every transaction and lock in your system, so we can trace any situation that occurs from it. From forgotten transactions to long running ones with a lock, you’ll get real knowledge on how your database runs, and we’ll provide info to help you find out why it runs like that.
Buffers, Status and QPS
We can establish a pretty good health check, since we do collect info about your QPS, your buffers and the general status of your database. You can use to judge if you need to make any adjustments to its settings, software or hardware wise.