having read that coroot now supports mysql i was happy to check it out - to see if i can get some better analysis of some of my databases. i could not get it to work though, the screenshot in the 1.3.0 release notes shows a mariadb database, but i could not get mariadb databases to show up - only mysql ones (see here: 1.3.0 release notes )
having a look at the code, it seemed like if the running process was identifies to be mysqld - a metric would be set which would then indicate the application type. so, adding the mariadbd to the process list to set the mysql label worked perfectly.
since they are protocol (and a lot of code) compatible, all features work fine, including the mysql tab, as well as profiling, io, etc...
having read that coroot now supports mysql i was happy to check it out - to see if i can get some better analysis of some of my databases. i could not get it to work though, the screenshot in the 1.3.0 release notes shows a mariadb database, but i could not get mariadb databases to show up - only mysql ones (see here: 1.3.0 release notes ) having a look at the code, it seemed like if the running process was identifies to be mysqld - a metric would be set which would then indicate the application type. so, adding the mariadbd to the process list to set the mysql label worked perfectly. since they are protocol (and a lot of code) compatible, all features work fine, including the mysql tab, as well as profiling, io, etc...