-
Notifications
You must be signed in to change notification settings - Fork 3k
journald event logging #2850
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
journald event logging #2850
Conversation
1ea235e to
40047f9
Compare
3efd98a to
3493894
Compare
|
/test images |
1 similar comment
|
/test images |
libpod/events.go
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why run this every time? We can store it in the runtime (c.runtime.eventer)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We initialize once during NewRuntime, and after that we can use c.runtime.eventer.Write()
|
/test images |
17264e0 to
d1ca2cf
Compare
|
☔ The latest upstream changes (presumably #2948) made this pull request unmergeable. Please resolve the merge conflicts. |
|
ping folks to review or merge this |
|
I will wait for @mheon OK. |
|
I got one small thing, LGTM once that's fixed |
add the ability for podman to read and write events to journald instead of just a logfile. This can be controlled in libpod.conf with the `events_logger` attribute of `journald` or `file`. The default will be set to `journald`. Signed-off-by: baude <[email protected]>
|
fixed |
|
LGTM, Lets merge when it passes tests. |
|
Agree |
|
LGTM assuming happy tests |
|
/lgtm |
add the ability for podman to read and write events to journald instead
of just a logfile. This can be controlled in libpod.conf with the
events_loggerattribute ofjournaldorfile. The default will beset to
journald.Signed-off-by: baude [email protected]