You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! The sidecar logs seem to be going into sdrerr and therefore displayed as part of Errors pipe on GCP. Is that a know issue or are there known workaround?
A tons of messages i am talking about are like:
New connection for "<sqlinstanceid>"
Client closed local connection on 127.0.0.1:5432
Instance <sqlinstanceid> closed connection
The text was updated successfully, but these errors were encountered:
#150 implements a flag to override this and log non-error output to Stdout, but it is defaulted to false, as to not break users who are dependent on the existing error logging behavior. If you don't want connection-related messages to log as errors, you can run the proxy with the CLI flag --log_debug_stdout set to true.
Hi! The sidecar logs seem to be going into sdrerr and therefore displayed as part of Errors pipe on GCP. Is that a know issue or are there known workaround?
A tons of messages i am talking about are like:
The text was updated successfully, but these errors were encountered: