Skip to content

Sending Logs to Support

When you report a problem that you can repeat, debug logs help support find the cause. DbVisualizer writes its logs to the .dbvis/logs folder in your home directory, and you open them using Tools → Debug Window.

The Debug Window

Collecting debug logs

  1. Select File → Clear Cache → Clear All, and click Clear.
  2. Restart DbVisualizer.
  3. Select Tools → Debug Window, and select Debug DbVisualizer. If support asks for logs from the database driver too, also select Debug JDBC Drivers. It writes a lot of entries, so only select it if you are asked to.
  4. Do what causes the problem.
  5. In the Debug Window, clear Debug DbVisualizer and Debug JDBC Drivers.
  6. Select Help → Contact Support. Describe step by step what you did, and if you are answering a support ticket, mention its number. Screenshots or a screen recording of the problem help a lot: drop the files on the form, or click Attach File.
  7. Check that Attach Logs is selected, and click Send.

Recording a performance problem

If DbVisualizer is slow or stops responding, a recording shows support what it is doing.

  1. Select Tools → Debug Window, and click Start Java Flight Recording.
  2. Do what is slow.
  3. Click Stop Java Flight Recording. DbVisualizer offers to open Contact Support with the recording attached.

If DbVisualizer is slow when it starts, click Configure Java Flight Recording instead. Set how long to record, and click Restart. DbVisualizer restarts and records the startup.

Finding errors

When an error is written to the log, a red icon is shown in the status bar. Click it to see the error in the Error Log tab of the Debug Window. To open the folder with the log files, click Open Logs Directory.