Describe the feature
Add the ability to control the log level written to the system journal as well as the local log file.
Add the ability to disable the local log file (as that info is already written to the system journal).
Currently INFO is written to the system journal and DEBUG is written to a local file.
Use Case
This is causing significant unnecessary disk usage and churn.
In our situation we want all logging written to journald which is then shipped to a central logging point. Managing local log files is not desired. DEBUG logging, when not troubleshooting, is also not desired.
Alternatives considered
I have searched for and been unable to find any settings, env variables, or command line opts that control this.
How important is this for you?
Would improve my workflow
Checklist
Describe the feature
Add the ability to control the log level written to the system journal as well as the local log file.
Add the ability to disable the local log file (as that info is already written to the system journal).
Currently INFO is written to the system journal and DEBUG is written to a local file.
Use Case
This is causing significant unnecessary disk usage and churn.
In our situation we want all logging written to journald which is then shipped to a central logging point. Managing local log files is not desired. DEBUG logging, when not troubleshooting, is also not desired.
Alternatives considered
I have searched for and been unable to find any settings, env variables, or command line opts that control this.
How important is this for you?
Would improve my workflow
Checklist