Please make sure you have searched for information in the following guides.

• Search the issues already opened: https://github.com/GoogleCloudPlatform/google-cloud-node/issues
• Search StackOverflow: http://stackoverflow.com/questions/tagged/google-cloud-platform+node.js
• Check our Troubleshooting guide: https://github.com/googleapis/google-cloud-node/blob/main/docs/troubleshooting.md
• Check our FAQ: https://github.com/googleapis/google-cloud-node/blob/main/docs/faq.md
• Check our libraries HOW-TO: https://github.com/googleapis/gax-nodejs/blob/main/client-libraries.md
• Check out our authentication guide: https://github.com/googleapis/google-auth-library-nodejs
• Check out handwritten samples for many of our APIs: https://github.com/GoogleCloudPlatform/nodejs-docs-samples

A screenshot that you have tested with "Try this API".

N/A

Link to the code that reproduces this issue. A link to a public Github Repository or gist with a minimal reproduction.

https://github.com/googleapis/nodejs-spanner/pull/2455/files

A step-by-step description of how to reproduce the issue, based on the linked reproduction.

Just initialize a new client.

A clear and concise description of what the bug is, and what you expected to happen.

Upon initialization, the client uses console.log to write debug-level logs. This cannot be configured.

A clear and concise description WHY you expect this behavior, i.e., was it a recent change, there is documentation that points to this behavior, etc. **

Please revert #2455.
Using console.log in a package prevents any kind of consistent logging for users. It also interferes with the standard output, which can be used by CLIs as a way to return results. It is also not clear why everybody would need such logs all the time, including in production. The default should be not to produce any logs and have the package user explicitly ask for them.