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

[FEATURE]: Multi-location file logging. #79

Closed
SeedyROM opened this issue Oct 20, 2022 · 2 comments · Fixed by #80
Closed

[FEATURE]: Multi-location file logging. #79

SeedyROM opened this issue Oct 20, 2022 · 2 comments · Fixed by #80
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@SeedyROM
Copy link
Collaborator

SeedyROM commented Oct 20, 2022

Problem

Right now we only log the error reason in the ~/.croncatd/logs, what we really want is to pipe the tracing messages from warn and error into that same log file as well.

Ideas

@SeedyROM SeedyROM added the enhancement New feature or request label Oct 20, 2022
@SeedyROM SeedyROM self-assigned this Oct 20, 2022
@TrevorJTClarke
Copy link
Member

@SeedyROM I am hoping for a split actually!
Logs for info/warn in 1 file, errors in another turned on by debug flag

@TrevorJTClarke TrevorJTClarke added this to the 🚲 Alpha milestone Oct 20, 2022
@SeedyROM
Copy link
Collaborator Author

@TrevorJTClarke So I was thinking we have the debug flag set it shows the traceback in the terminal itself.

How about we keep that, but also always store a info/warn log and an error log. (eg. uni-5.log and uni-5.error.log).

Using the log rotation from that crate puts the current date at the end like this uni-5.log.2022.10.20

@SeedyROM SeedyROM changed the title [FEATURE]: Log to console and to a file for WARN/ERROR. [FEATURE]: Multi-location file logging. Oct 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants