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.

Sign up for GitHub

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

Jump to bottom

Add --help message documentation to README #709

Open
FezVrasta opened this issue Sep 30, 2024 · 5 comments
Open

Add --help message documentation to README #709

FezVrasta opened this issue Sep 30, 2024 · 5 comments
Assignees
@enocom
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: cleanup An internal cleanup or hygiene concern. type: docs Improvement to the documentation for an API.

Comments

@FezVrasta
Copy link

Question

Hi, we are using gcr.io/alloydb-connectors/alloydb-auth-proxy and we are observing a huge amount of logs being generated by the container.

2024-09-30 13:35:38.160 CEST
2024/09/30 11:35:38 [.us-central1.default.default] accepted connection from 127.0.0.1:60560
2024-09-30 13:35:38.258 CEST
2024/09/30 11:35:38 [.us-central1.default.default] client closed the connection
2024-09-30 13:35:43.135 CEST
2024/09/30 11:35:43 [.us-central1.default.default] accepted connection from 127.0.0.1:60574
2024-09-30 13:35:43.281 CEST
2024/09/30 11:35:43 [.us-central1.default.default] client closed the connection
2024-09-30 13:35:48.135 CEST
2024/09/30 11:35:48 [.us-central1.default.default] accepted connection from 127.0.0.1:59438
2024-09-30 13:35:48.204 CEST
2024/09/30 11:35:48 [.us-central1.default.default] client closed the connection
2024-09-30 13:35:53.129 CEST
2024/09/30 11:35:53 [.us-central1.default.default] accepted connection from 127.0.0.1:59452
2024-09-30 13:35:53.199 CEST
2024/09/30 11:35:53 [.us-central1.default.default] client closed the connection

We reached over 1 million log entries over the past month. Is there any way to set the log level to "warn" so that these info messages are not logged to the console?

Code

No response

Additional Details

No response
@FezVrasta FezVrasta added the type: question Request for information or clarification. label Sep 30, 2024
@enocom
Copy link
Member

enocom commented Sep 30, 2024

You're looking for the --quiet flag which will only log error messages.

@FezVrasta
Copy link
Author

Thanks, I don't think that's documented though?

@enocom
Copy link
Member

enocom commented Sep 30, 2024

If you run ./alloydb-auth-proxy --help, it does appear in the list of flags.

We could reproduce that help message here in the repository if that would help. WDYT?

@FezVrasta
Copy link
Author

Yes that would be extremely helpful, having ran this project exclusively through kubernetes and its container I never had a chance to play with the CLI tool.

@enocom enocom added type: docs Improvement to the documentation for an API. type: cleanup An internal cleanup or hygiene concern. priority: p2 Moderately-important priority. Fix may not be included in next release. and removed type: question Request for information or clarification. labels Sep 30, 2024
@enocom
Copy link
Member

enocom commented Sep 30, 2024

Sounds good. I'll make this an issue for doing that. Thanks again for the report.

@enocom enocom changed the title Container is extremely noisy Add --help message documentation to README Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@enocom enocom

Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: cleanup An internal cleanup or hygiene concern. type: docs Improvement to the documentation for an API.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@enocom @FezVrasta