Descripción
Query Monitor is the developer tools panel for WordPress and WooCommerce. It enables debugging of database queries, PHP errors, hooks and actions, block editor blocks, enqueued scripts and stylesheets, HTTP API calls, and more.
It includes some advanced features such as debugging of Ajax calls, REST API calls, user capability checks, and full support for block themes and full site editing. It includes the ability to narrow down much of its output by plugin or theme, allowing you to quickly determine poorly performing plugins, themes, or functions.
Query Monitor focuses heavily on presenting its information in a useful manner, for example by showing aggregate database queries grouped by the plugins, themes, or functions that are responsible for them. It adds an admin toolbar menu showing an overview of the current page, with complete debugging information shown in panels once you select a menu item.
Query Monitor es compatible con versiones de WordPress de hasta tres años de antigüedad, y con la versión 7.4 o superior de PHP.
For complete information, please see the Query Monitor website.
Here’s an overview of what’s shown for each page load:
- Database queries, including notifications for slow, duplicate, or erroneous queries. Allows filtering by query type (
SELECT,UPDATE,DELETE, etc), responsible component (plugin, theme, WordPress core), and calling function, and provides separate aggregate views for each. - El nombre del archivo de plantilla, la jerarquía de plantilla completa y los nombres de todas las partes de la plantilla que se cargaron o no (para temas de bloques y temas clásicos).
- PHP errors presented nicely along with their responsible component and call stack, and a visible warning in the admin toolbar.
- Usage of «Doing it Wrong» or «Deprecated» functionality in the code on your site.
- Bloques y propiedades asociadas dentro del contenido de la entrada y dentro de la edición completa del sitio (FSE).
- Matched rewrite rules, associated query strings, and query vars.
- Enqueued scripts and stylesheets, along with their dependencies, dependents, and alerts for broken dependencies.
- Language settings and loaded translation files (MO files and JSON files) for each text domain.
- HTTP API requests, with response code, responsible component, and time taken, with alerts for failed or erroneous requests.
- User capability checks, along with the result and any parameters passed to the capability check.
- Environment information, including detailed information about PHP, the database, WordPress, and the web server.
- The values of all WordPress conditional functions such as
is_single(),is_home(), etc. - Transients that were updated.
- Usage of
switch_to_blog()andrestore_current_blog()on Multisite installations.
In addition:
- Whenever a redirect occurs, Query Monitor adds an HTTP header containing the call stack, so you can use your favourite HTTP inspector or browser developer tools to trace what triggered the redirect.
- The response from any jQuery-initiated Ajax request on the page will contain various debugging information in its headers. PHP errors also get output to the browser’s developer console.
- The response from an authenticated WordPress REST API request will contain an overview of performance information and PHP errors in its headers, as long as the authenticated user has permission to view Query Monitor’s output. An an enveloped REST API request will include even more debugging information in the
qmproperty of the response.
By default, Query Monitor’s output is only shown to Administrators on single-site installations, and Super Admins on Multisite installations.
In addition to this, you can set an authentication cookie which allows you to view Query Monitor output when you’re not logged in (or if you’re logged in as a non-Administrator). See the Settings panel for details.
Otros plugins
Mantengo varios otros plugins para desarrolladores. Échales un vistazo:
- User Switching ofrece cambio instantáneo entre cuentas de usuario en WordPress.
- WP Crontrol te permite ver y controlar lo que sucede en el sistema WP-Cron
Gracias
El tiempo que dedico a mantener este plugin y otros está patrocinado en parte por:
Privacy Statement
Query Monitor es privado por defecto y siempre lo será. No almacena de forma persistente ninguno de los datos que recoge. No envía datos a terceros, ni incluye recursos de terceros. Aquí se puede encontrar la declaración de privacidad completa de Query Monitor.
Declaración de accesibilidad
Query Monitor pretende ser totalmente accesible para todos sus usuarios. Aquí se puede encontrar la declaración de accesibilidad completa de Query Monitor.
Capturas
FAQ
-
¿Funciona este plugin con PHP 8?
-
Sí, se ha probado activamente y funciona hasta PHP 8.5.
-
Who can see Query Monitor’s output?
-
By default, Query Monitor’s output is only shown to Administrators on single-site installations, and Super Admins on Multisite installations.
In addition to this, you can set an authentication cookie which allows you to view Query Monitor output when you’re not logged in, or when you’re logged in as a user who cannot usually see Query Monitor’s output. See the Settings panel for details.
-
Does Query Monitor itself impact the page generation time or memory usage?
-
Short answer: Yes, but only a little.
Long answer: Query Monitor has a small impact on page generation time because it hooks into a few places in WordPress in the same way that other plugins do. The impact is negligible.
On pages that have an especially high number of database queries (in the hundreds), Query Monitor currently uses more memory than I would like it to. This is due to the amount of data that is captured in the stack trace for each query. I have been and will be working to continually reduce this.
-
¿Puedo evitar que Query Monitor recopile datos durante solicitudes de larga duración?
-
Sí, puedes llamar a
do_action( 'qm/cease' )para indicar a Query Monitor que deje de funcionar durante el resto de la generación de la página. Se desvinculará de cualquier otra recopilación de datos posterior, descartará los datos recopilados hasta el momento y omitirá la salida de su información.Esto es útil para operaciones de larga duración que realizan un número muy elevado de consultas a la base de datos, consumen mucha memoria o que, de otro modo, no interesan a Query Monitor, por ejemplo:
- Copia de seguridad o restauración de tu sitio
- Importar o exportar una gran cantidad de datos
- Running security scans
-
Are there any add-on plugins for Query Monitor?
-
Aquí encontrarás una lista de extensiones para Query Monitor.
In addition, Query Monitor transparently supports add-ons for the Debug Bar plugin. If you have any Debug Bar add-ons installed, deactivate Debug Bar and the add-ons will show up in Query Monitor’s menu.
-
Where can I suggest a new feature or report a bug?
-
Please use the issue tracker on Query Monitor’s GitHub repo as it’s easier to keep track of issues there, rather than on the wordpress.org support forums.
-
¿Viene Query Monitor ya incluido en mi alojamiento?
-
Algunos proveedores de alojamiento web incluyen Query Monitor como parte de su plataforma de hosting, lo que significa que no necesitas instalarlo tú mismo. Aquí tienes algunos de los que tengo constancia:
- Altis Cloud.
- WordPress VIP, aunque a los usuarios se les debe otorgar la capacidad
view_query_monitorincluso si son administradores. Consulta la documentación de WordPress VIP para obtener más detalles.
-
¿Puedo hacer clic en las trazas de la pila para abrir el archivo en mi editor?
-
Yes. You can enable this on the Settings panel.
-
¿Cómo puedo informar de un fallo de seguridad?
-
Puedes enviar un informe privado de vulnerabilidad de seguridad a Query Monitor a través de la pestaña de Seguridad en el repositorio de GitHub. El proceso de avisos de seguridad de GitHub facilita la colaboración privada en problemas de seguridad. Recibirás reconocimiento por un informe válido y un CVE si fuera necesario.
No informes sobre problemas de seguridad en los foros de soporte de WordPress.org ni por correo electrónico. Gracias.
-
Do you accept donations?
-
Acepto patrocinios a través del programa GitHub Sponsors. Si trabajas en una agencia que desarrolla con WordPress, pide a tu empresa que proporcione patrocinio para invertir en su cadena de suministro. Las herramientas que mantengo probablemente ahorren tiempo y dinero a tu empresa, y el patrocinio de GitHub ahora se puede realizar a nivel de organización.
In addition, if you like the plugin then I’d love for you to leave a review. Tell all your friends about it too!
Reseñas
Colaboradores y desarrolladores
«Query Monitor» es un software de código abierto. Las siguientes personas han colaborado con este plugin.
Colaboradores«Query Monitor» está traducido en 26 idiomas. Gracias a los traductores por sus contribuciones.
Traduce «Query Monitor» a tu idioma.
¿Interesado en el desarrollo?
Revisa el código , echa un vistazo al repositorio SVN o suscríbete al registro de desarrollo por RSS.
Registro de cambios
4.0.6 (11 April 2026)
Version 4 of Query Monitor adds a new timeline view, and switches from rendering its panels server-side in PHP to efficiently rendering them client-side in Preact.
Version 4.0.6 fixes a compatibility issue with the GeneratePress theme.
More information at querymonitor.com/4.
4.0.5 (10 April 2026)
Version 4 of Query Monitor adds a new timeline view, and switches from rendering its panels server-side in PHP to efficiently rendering them client-side in Preact.
Version 4.0.5 fixes the following:
- Ensures closing script tags within data don’t break the output
- Adds «Doing it Wrong» data to the timeline view
More information at querymonitor.com/4.
4.0.4 (10 April 2026)
Version 4 of Query Monitor adds a new timeline view, and switches from rendering its panels server-side in PHP to efficiently rendering them client-side in Preact.
Version 4.0.4 fixes the following:
- Ensures the Scripts panel remains visible when no scripts are enqueued in the header
- Corrects the display of number formatting in some locales
More information at querymonitor.com/4.
4.0.3 (9 April 2026)
Version 4 of Query Monitor adds a new timeline view, and switches from rendering its panels server-side in PHP to efficiently rendering them client-side in Preact.
Version 4.0.3 fixes the following:
- Improves compatibility with plugins that perform non-UTF8 queries or make other use of non-UTF8 data
- Avoids a PHP warning for undefined file and line number in some stack trace frames
- Simplifies and standardises the format of names used for closure callbacks
- Improves styling and layout of the timeline view
More information at querymonitor.com/4.
4.0.2 (9 April 2026)
Version 4 of Query Monitor adds a new timeline view, and switches from rendering its panels server-side in PHP to efficiently rendering them client-side in Preact.
Version 4.0.2 fixes the following:
- Adds further backwards compatibility for third-party plugins that read from the QM data collectors and output their own panels
- Adds transient updates to the timeline view
More information at querymonitor.com/4.
4.0.1 (7 April 2026)
Version 4 of Query Monitor adds a new timeline view, and switches from rendering its panels server-side in PHP to efficiently rendering them client-side in Preact.
- Version 4.0.1 fixes a backwards compatibility issue with plugins that register their own menus or sub-menus in Query Monitor.
More information at querymonitor.com/4.
4.0.0 (7 April 2026)
Version 4 of Query Monitor adds a new timeline view, and switches from rendering its panels server-side in PHP to efficiently rendering them client-side in Preact. This new approach provides several benefits:
- Performance is greatly increased, particularly on sites where a large number of queries are performed, a large number of PHP errors are triggered, or a large amount of data is collected in one of the other panels.
- Further future enhancements are facilitated, such as displaying client-side metrics, lazy-loading data, showing data from different requests, and more remixing of data into different views.
- The raw data collected by Query Monitor has been reduced in size and memory usage, and is now exposed to the page as JSON. Take a look at the
QueryMonitorDataobject in your browser console to play around with it.
More information at querymonitor.com/4.
3.20.4 (19 March 2026)
- This is a security release which fixes a reflected XSS vulnerability in the Request panel. Full details in the security advisory.
3.20.3 (17 March 2026)
- Clicking QM in the the admin toolbar a second time will now close the panel
- Improvements to accessibility of the toggle buttons
- Failed HTTP API GET requests now show a clickable link
3.20.2 (11 December 2025)
- Prevents a PHP error being triggered under certain conditions and when no database queries are performed.
Earlier versions
For the changelog of earlier versions, refer to the releases page on GitHub.







