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

refactor logging #24

Closed
giuseppe opened this issue Mar 16, 2019 · 10 comments
Closed

refactor logging #24

giuseppe opened this issue Mar 16, 2019 · 10 comments

Comments

@giuseppe
Copy link
Member

the logging (src/libcrun/error.c) is currently a mess, it needs to be simplified and polished

@dmolik
Copy link
Contributor

dmolik commented Mar 27, 2019

would this be a good time to bring up logging to syslog?

@giuseppe
Copy link
Member Author

giuseppe commented Mar 27, 2019

@dmolik if you need that, I can try to add it in the current mess :-)

Is it anything runc already does and we need to keep some CLI compatibility? If not, would something like --log=syslog:IDENTITY be good for you?

@giuseppe
Copy link
Member Author

@dmolik I've opened https://github.com/giuseppe/crun/pull/28

It is still work in progress, but you can start using syslog, like crun --log=syslog: and journald as crun --log=journald:. If not specified, they both use the container name as the identifier, otherwise they use whatever is specified after :. So for example if you want to override an identifier in the logging, you can do: crun --log=syslog:FOO.

What do you think?

@dmolik
Copy link
Contributor

dmolik commented Apr 4, 2019

Setting the facility name would be cool.

@giuseppe
Copy link
Member Author

giuseppe commented Apr 4, 2019

I've implemented that functionality in the PR.

You can use --log=syslog:IDENTITY to override the identifier, otherwise it defaults to the container name. Similarly for --log=journald:

@giuseppe
Copy link
Member Author

giuseppe commented Apr 4, 2019

is that enough for you? :-) Can I merge the PR?

@dmolik
Copy link
Contributor

dmolik commented Apr 13, 2019

LGTM. Thanks! Sorry for the slow response.

@rhatdan
Copy link
Member

rhatdan commented Aug 19, 2019

@giuseppe Should this issue be closed?

@rhatdan
Copy link
Member

rhatdan commented Sep 11, 2019

@giuseppe Can we close?

@giuseppe
Copy link
Member Author

yes, let's close it as there is no work going on and it is not really a specific issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants