Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Info messages saved into stderr #510

Closed
arkadyb opened this issue Oct 22, 2020 · 3 comments
Closed

Info messages saved into stderr #510

arkadyb opened this issue Oct 22, 2020 · 3 comments
Assignees
Labels
type: question Request for information or clarification.

Comments

@arkadyb
Copy link

arkadyb commented Oct 22, 2020

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
@arkadyb arkadyb added the type: question Request for information or clarification. label Oct 22, 2020
@shubha-rajan
Copy link
Contributor

#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.

@arkadyb
Copy link
Author

arkadyb commented Oct 22, 2020

Thanks @shubha-rajan ! Is there any particular reason to not have that true by default?

@arkadyb arkadyb closed this as completed Oct 22, 2020
@kurtisvg
Copy link
Contributor

@arkadyb See the comments in the original PR: #150 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: question Request for information or clarification.
Projects
None yet
Development

No branches or pull requests

3 participants