Activating verbose mode in terminal MySQL is very useful while working with a production deployment, especially when it helps to resolve any issue right away. At Bobcares, with our MySQL Support Services, we offer solutions to your questions.

Activating verbose mode in terminal MySQL

Logging

We can use the --log-level option to start MySQL Shell with a verbose logging level:

$> mysqlsh --log-level=DEBUG3

The suggested level is DEBUG3. The SQL queries that are executed as part of each AdminAPI call can be found in lines like Debug: execute_sql( ... ) in the MySQL Shell log file when DEBUG3 is enabled. On Unix-based systems, the MySQL Shell log file can be found in ~/.mysqlsh/mysqlsh.log. And for MS Windows systems, it can be found in %APPDATA%\MySQL\mysqlsh\mysqlsh.log.

We can control the output AdminAPI provides in MySQL Shell after executing each command in addition to enabling the MySQL Shell log level. Issue the following command in MySQL Shell to enable AdminAPI output volume:

mysql-js> dba.verbose=2

This enables the maximum output from AdminAPI calls. In order to turn the “–Verbose” option on in MySQL, we can use any of the below codes:

mysql -u user -p -v

mysql -u user -p -vvv (more verbose)

Output

As of MySQL 8.0.17, you can send logging data from MySQL Shell to the console to aid in debugging. The verbose: prefix is used in console logging messages. Logging data is still sent to the app log file even when it is sent to the console. We can select any of the following options to send logging information to the console as verbose output.

1. While starting MySQL Shell, we can use the --verbose command-line option.
2. We can use the MySQL Shell \option command to set the verbose MySQL Shell configuration option.
3. We can use the shell.options object to set the verbose MySQL Shell configuration option.

The verbose option’s settings cause messages to be displayed at the following levels of detail:

0: No messages – Equivalent to a logging level of 1 for the app log.

1: Internal error, error, warning, and informational messages – Equivalent to a logging level of 5 for the app log.

2: Adds debug messages – Equivalent to a logging level of 6 for the app log.

3: Adds debug2 messages – Equivalent to a logging level of 7 for the app log.

4: Adds debug3 messages, the highest level of detail – Equivalent to a logging level of 8 for the app log.

Verbose output to the console is disabled if the verbose option is not set on the command line, in the configuration file, or if we specify a setting of 0. The level of detail for messages sent to the console is set by the other values, which enable verbose output. Setting 1 is used we specify the option without a value, which is allowed as a command-line option when starting MySQL Shell (–verbose) but not with other methods of setting the option.

[Searching for a solution to another query? We’re available 24/7.]

Conclusion

To conclude, the article details the method from our Support team for activating verbose mode in terminal MySQL.