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

Output logs in stdout instead of file #337

Open
jchanam opened this issue Sep 20, 2024 · 0 comments
Open

Output logs in stdout instead of file #337

jchanam opened this issue Sep 20, 2024 · 0 comments

Comments

@jchanam
Copy link
Contributor

jchanam commented Sep 20, 2024




Is your feature request related to a problem? Please describe.
When running as a cronjob in a kubernetes cluster, there's no way to see if the execution was successful or not as there's no output, and the log file is lost.

Describe the solution you'd like
A new flag to be added, such as --log-stdout that enables this feature. I've assumed that this would only be possible if the --save option is used, so the outputs don't collide with each other.

Describe alternatives you've considered
Add a fluentd to as a sidecar to tail the file and send the logs, but I think it's a little bit overkill.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant