We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
every time the file logger is started, it creates 2 files. one that's only relevant to quickly see errors and one full log
the error.log file should only be created if there was an error logged
5.1.0
The text was updated successfully, but these errors were encountered:
#1045: remove -error.log file on exit if there was no error
2c40b7b
Merge pull request #1046 from Accenture/bugfix/1045-logger-creates-er…
1cb3771
…rorlog-files-even-if-no-errors-occured #1045: remove -error.log file on exit if there was no error
Closed by #1046.
Sorry, something went wrong.
#1045: remove empty error log files during log rotation
d705672
when commands are executed on multiple BUs using the * sign, logs are rotated before switching BUs
Revert "#1045: remove empty error log files"
63d6ea9
This reverts commits d705672 and 2c40b7b
#1045: use new lazy flag in winston 3.10.0 to ensure error.log files …
fed0939
…are only created when needed
JoernBerkefeld
Successfully merging a pull request may close this issue.
Is there an existing issue for this?
Current Behavior
every time the file logger is started, it creates 2 files. one that's only relevant to quickly see errors and one full log
Expected Behavior
the error.log file should only be created if there was an error logged
Version
5.1.0
Participation
The text was updated successfully, but these errors were encountered: