Monitoring doesn’t seem to work

Thanks for reporting this defect!

You’re quite right, monitoring collected no data. (I guess I should fix the ridiculous-time bug and just say “no data captured”, shouldn’t I?)

Would you be kind enough to visit the plugin’s About tab and upload your metadata? From there I may be able to figure out what’s wrong.

Sure thing: eBdekkQ6

Thanks!

Thanks for the upload. I was looking for a plugin that might use its own drop-in db.php module, like the ones Query Monitor or WP Total Cache use. But I don’t see any such. (This plugin’s monitor capture works fine with Query Monitor and W3TC).

Try purging your Redis Object Cache. Sometimes that makes a difference.

To monitor, the plugin sets SAVEQUERIES to true, then hooks the shutdown action and looks at $wpdb->queries. It seems like something is interfering with the shutdown hook on your system. It’s hard to know exactly what.

Thanks for your patience with this.

I tried it out on a staging site with redis disabled, same effect.

I do have SAVEQUERIES set to false in wp-config, I wonder if that is the issue.

Query Monitor logging seems to work fine, though I do need to manually enable SAVEQUERIES to get that to work.

Thanks!

• This reply was modified 3 years, 1 month ago by Marty.

I was able to get this working by manually setting

define('SAVEQUERIES', true);

in wp-config

Thanks for that feedback. The plugin attempts to set SAVEQUERIES to true while monitoring, and takes care to set it back to false when done. (SAVEQUERIES adds significant overhead to WordPress’s processing, so it’s best to disable it when not in use.)

I guess, for some reason, the plugin isn’t able to set it to true in your environment.