It there a way around having show_compatibility_56 set in MySQL for DPA

Question

We are exploring the possibility of using DPA for MySQL but this seems like a problem based on other SA/DBA not wishing to revert to deprecated features.  Is there a way around setting this variable or do we just need to wait for a releases where this is no longer required?

Thanks -- Jeff

jschafer1 · Answer

My concern is that the things it says are missing are the most important things you measure, basic CRUD operations.

From the doc you mentioned, these are missing metrics:

All metrics except the following:

* Selects
* Inserts
* Updates
* Deletes

This doesn't leave much except resource monitoring.

If I am misunderstanding what is meant by the document, please let me know.

Thanks -- Jeff

bmrad · Answer

Jeff, dug in with our engineers, here is the detail;

DPA can monitor MySQL 5.6.10+, 5.7.9+.

* MySQL 5.6 is monitored through information_schema.global_status
* MySQL5.7 is monitored through performance_schema.global_status

There are a couple of metrics which are not present in performance schema at all, but were supported for older MySQL (metrics loaded from information_schema which is disabled in MySQL 5.7).  It depends on the configuration of MySQL server, so if the DBA doesn’t allow compatibility mode, we are not able to monitor these particular metrics.

See KB for more details:

* https://support.solarwinds.com/Success_Center/Database_Performance_Analyzer_(DPA)/No_metric_data_for_MySQL
* https://support.solarwinds.com/Success_Center/Database_Performance_Analyzer_(DPA)/DPA_Installation_Guide/0030-DPA_requirements/0060-MySQL_requirements