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

// , Send SystemD Logs to a separate file #11

Open
v6 opened this Issue Dec 3, 2018 · 2 comments

Comments

Projects
None yet
1 participant
@v6
Owner

v6 commented Dec 3, 2018

// , Currently both Vault and Consul logs are going into /var/log/messages, but for easier external consumption, either by the ELK stack or by Splunk, it would be more convenient if they had separate vault.log and consul.log files.

@v6 v6 added the enhancement label Dec 3, 2018

@v6

This comment has been minimized.

Owner

v6 commented Dec 3, 2018

// , @mrodriguezio, would you please have a go at this one?

@v6 v6 added the good first issue label Dec 3, 2018

@v6

This comment has been minimized.

Owner

v6 commented Dec 4, 2018

// , Something like this might work:

ExecStart=/bin/bash -c '/usr/bin/journalctl --no-tail -f -o json > /var/journald_file'

Splunk and others can't handle the binary format of SystemD journals:

https://www.freedesktop.org/wiki/Software/systemd/journal-files/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment