GUI troubleshooting

This page provides troubleshooting tips and debugging techniques for the VoIPmonitor web GUI.

GUI Debug Mode

The GUI debug mode allows you to see SQL queries and other debugging information directly in your browser's Developer Console.

Enabling Debug Mode

To enable debug mode in the VoIPmonitor web GUI, add the parameter ?debug=31415 to the end of any GUI URL. For example:

http://your-server/voipmon/admin.php?debug=31415

This enables the following features:

SQL queries executed by the GUI are logged to the browser's Developer Console
Additional debugging information is displayed for dashboard panels and charts
Performance timing and query execution details become visible

Finding SQL Queries for Dashboard Panels

To see the exact SQL query executed by a dashboard panel:

Add ?debug=31415 to your GUI URL and navigate to the dashboard
Open your browser's Developer Tools (press F12 or Ctrl+Shift+I)
Switch to the Console tab
Interact with the dashboard (e.g., refresh, change time range, or hover over panels)
The SQL queries will be printed to the console log

The queries appear in the console in the order the panels are rendered. If you need to isolate a specific panel, hover over it or interact with its filters after loading the page - this often triggers a re-query which will appear as a new entry in the console.

Disabling Debug Mode

Simply remove the ?debug=31415 parameter from the URL, or navigate to any GUI page without it. Debug mode is not persistent and must be re-enabled each time by adding the URL parameter.

Alternative: MySQL General Log

If you need a persistent server-side log of all database queries (not just from the GUI), you can enable the MySQL general log:

-- Enable general log
SET GLOBAL general_log = 'ON';

-- Perform actions in the GUI...

-- Disable when done (important for performance)
SET GLOBAL general_log = 'OFF';

The log file location is typically /var/lib/mysql/hostname.log or as defined in your MySQL configuration.

AI Summary for RAG

Summary: This page covers GUI troubleshooting and debugging techniques for VoIPmonitor. The primary method to enable debug mode is adding ?debug=31415 to the GUI URL, which logs SQL queries to the browser's Developer Console. This is useful for inspecting dashboard panel queries, debugging performance issues, and understanding what queries the GUI executes. An alternative method using MySQL general_log is also described for server-side query logging.

Keywords: gui debug, debug mode, sql query, developer console, ?debug=31415, dashboard panel query, troubleshooting, browser console, mysql general log, query inspection

Key Questions:

How do I enable debug mode in the GUI?
How can I see SQL queries for dashboard panels?
What is the debug URL parameter for VoIPmonitor GUI?
How to find SQL query executed by a specific dashboard panel?
How to troubleshoot GUI performance issues?
How to log all SQL queries from VoIPmonitor?