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
Currently, if you use events_logger = "journald" (the default) and have many containers, you'll end up with a journal spammed of (most times) irrelevant podman events. Here's a proof: https://gist.githubusercontent.com/Edu4rdSHL/7484cb674db93fee5905270c1d1df7b1/raw/340bd5d8d26f8dcbecf3d37f1f740df6cc404698/gistfile0.txt
events_logger = "journald"
The workaround is to use file or none as events_logger, but you'll lose the ability to podman container logs -f.
file
none
events_logger
podman container logs -f
Having a way to control what's reported to the journal using a events_logger_level = debug/info/warn/err/crit variable, would be awesome.
events_logger_level = debug/info/warn/err/crit
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Feature request description
Currently, if you use
events_logger = "journald"
(the default) and have many containers, you'll end up with a journal spammed of (most times) irrelevant podman events. Here's a proof: https://gist.githubusercontent.com/Edu4rdSHL/7484cb674db93fee5905270c1d1df7b1/raw/340bd5d8d26f8dcbecf3d37f1f740df6cc404698/gistfile0.txtThe workaround is to use
file
ornone
asevents_logger
, but you'll lose the ability topodman container logs -f
.Suggest potential solution
Having a way to control what's reported to the journal using a
events_logger_level = debug/info/warn/err/crit
variable, would be awesome.Have you considered any alternatives?
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: