What log level reveals OAuth redirect_uri mismatches without leaking secrets?

An administrator needs to pinpoint why an OAuth token request fails due to a mismatched or missing redirect_uri by examining deployment logs from the client library and the authorization server.

The challenge is determining the lowest log level that includes the redirect_uri value in the error message while avoiding the accidental logging of client secrets, given that verbosity and redaction policies differ across libraries and server implementations.

What log level captures the full redirect_uri in OAuth validation error messages for typical client libraries?
How can administrators confirm that enabling this level does not expose client secrets in the logs?
Which configuration options control whether the authorization server redacts the redirect_uri or other parameters in its audit logs?