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

Log to a file from triage CLI #834

Open
shaycrk opened this issue Mar 19, 2021 · 0 comments
Open

Log to a file from triage CLI #834

shaycrk opened this issue Mar 19, 2021 · 0 comments
Labels
trivial Should be very easy to implement, in a couple lines or so

Comments

@shaycrk
Copy link
Contributor

shaycrk commented Mar 19, 2021

In addition to logging to stdout/stderr when using the triage CLI, we should make it easier to ensure logs get captured to a file as well (although users could do this by redirecting the output, logging to a file would be good default behavior generally and providing some arguments to control it might be easier for users unfamiliar with bash).

A few features that seem like they would be useful:

  • Log to a file in the project path by default, identified by the current timestamp (in addition to logging to the terminal)
  • Allow specifying a log file name/path via a CLI argument
  • Arguments to suppress logging to the terminal and/or file might be nice to have as well (e.g., --quiet)
@shaycrk shaycrk added the trivial Should be very easy to implement, in a couple lines or so label Mar 19, 2021
@shaycrk shaycrk added this to To be Prioritized in 2019 Triage Planning via automation Mar 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
trivial Should be very easy to implement, in a couple lines or so
Projects
2019 Triage Planning
  
To be Prioritized
Development

No branches or pull requests

1 participant