tombenner

MySQL Profiler displays debugging information about SQL queries to admin WordPress users. For each query, the profiler displays the time, syntax-highlighted SQL, and a trace of the functions (as well as the file and line number that the functions were called from) that were called.
The list can be sorted by any of its columns, so you can, for example:
<ul>
<li>Order the list by ID to see the chronological order of the queries</li>
<li>Order the list by time to see the slowest queries</li>
<li>Order the list by query to group the queries by type (SELECT, UPDATE, etc)</li>
<li>Order the list by trace to group the queries by similar origins</li>
</ul>
The list can also filtered by typing in the search box, so you can, for example:
<ul>
<li>View all queries that use the wp_posts table</li>
<li>View all queries that are related to the use of a function in taxonomy.php</li>
<li>View all queries that are related to the use of a specific function or class</li>
<li>View all queries that call a specific MySQL function</li>
</ul>
To turn off syntax highlighting, put the following in wp-config.php:
<pre><code>define('MP_HIGHLIGHT_SYNTAX', false);
</code></pre>
To omit the file and line number from the function trace and display the functions as a comma-separated list (to save vertical space), define the following in wp-config.php:
<pre><code>define('MP_DISPLAY_FILES', false);
</code></pre>
This plugin was loosely based on <a href="http://bueltge.de/" rel="nofollow ugc">Frank Bueltge</a>‘s <a href="https://wordpress.org/extend/plugins/debug-queries/" rel="ugc">Debug Queries</a> plugin, so a hearty thanks to him for the development of that.
If you’d like to grab development releases, see what new features are being added, or browse the source code please visit/follow the <a href="http://github.com/tombenner/mysql-profiler" rel="nofollow ugc">GitHub repo</a>.

MySQL Profiler

Displays a list of each page's SQL queries and the functions calling them that can be searched and sorted by time, type, etc.

Modern Tribe, Inc.

Jonathan Brinley

Peter Chester

You can use this plugin to manually log data or to capture logging on WordPress actions. You can capture load time, memory, backrace, data dumps, urls, and server IPs.
This is designed to either be managed using wp-config.php and logging OR using the admin and debugbar plugin ( https://wordpress.org/extend/plugins/debug-bar/ ). Most of the following documentation applies equally to the settings panel or the wp-config.php vars. Either one works fine. The only exception is the DEBUG_LOG configuration which is only supported as a wp-config var.
Firstly, you can manually log things using the following function:
<pre><code>do_action( 'log', $message, $group, $data );
</code></pre>
The $group allows you to selectively output logging based on groups of log messages. The $message is the string you want to see in the log. $data is an optional parameter for the data that you want to display in the log (objects, arrays, or any other sort of data really).
To render messages to the log, you must configure wp-config.php as follows:
Run debug on only these groups. Use ‘ALL’ to debug everything. The group ‘ACTIONS’ is reserved for WordPress actions.
<pre><code>define( 'DEBUG_GROUPS', 'ACTIONS,default,myspecialgroup' );
</code></pre>
Display these outputs in the log for each log message.
<pre><code>define( 'DEBUG_PARAMS', 'time,timedelta,memory,memorydelta,data,backtrace,url,server' );
</code></pre>
WordPress actions that you wish to log.
<pre><code>define( 'DEBUG_ACTIONS', 'wp_head,switch_theme,wp_footer' );
</code></pre>
Optional restriction by URL (useful on MU installs).
<pre><code>define( 'DEBUG_URLS', 'myurl.com' );
</code></pre>
Minimum time in milliseconds required to register a log entry as being slow. Default 0 for no minumum.
<pre><code>define( 'DEBUG_MIN_TIME', 500 );
</code></pre>
Minimum memory in killobytes required to register a log entry as being heavy. Default 0 for no minumum.
<pre><code>define( 'DEBUG_MIN_MEM', 1024 );
</code></pre>
Path to log file or set to TRUE to use php error log. Default FALSE for no logging.
<pre><code>define( 'DEBUG_LOG', '/path/to/writable/log/file' );
</code></pre>
or
<pre><code>define( 'DEBUG_LOG', TRUE );
</code></pre>
<h4>Todo</h4>
<ul>
<li>Add variable for sample rate so that this could run randomly on production installs</li>
<li>Admin panel per site</li>
<li>Admin panel globally</li>
<li>WordPress error logging</li>
<li>Mysql query logging</li>
<li>WP_Error integration</li>
<li>Alerts ex: if this takes more than this much memory then log it…</li>
</ul>

Debugger

You can use this plugin to manually log data or to capture logging on WordPress actions. You can capture load time, memory, backrace, data dumps, urls …

MySQL Profiler vs Debugger