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

Add a SyslogIdentifier section in .service #4

Open
CedricLevasseur opened this issue Apr 27, 2022 · 1 comment
Open

Add a SyslogIdentifier section in .service #4

CedricLevasseur opened this issue Apr 27, 2022 · 1 comment

Comments

@CedricLevasseur
Copy link

Proposed feature

Adding a syslog identifier make the journal clearable and filterable

Rationale

It's actually unclear. For example, i'm using tomcat, and it's hard to identify it in journalctl

Apr 27 05:36:02 myhost bash[88952]: java.io.FileNotFoundException: /somewhere/logs/localhost.2022-04-27.log (Permission denied)
Apr 27 05:36:02 myhost bash[88952]: at java.io.FileOutputStream.open0(Native Method)
Apr 27 05:36:02 myhost bash[88952]: at java.io.FileOutputStream.open(FileOutputStream.java:270)
Apr 27 05:36:02 myhost bash[88952]: at java.io.FileOutputStream.<init>(FileOutputStream.java:213)

It would be clearer if it were :
Apr 27 05:36:02 myhost tomcat: java.io.FileNotFoundException: /somewhere/logs/localhost.2022-04-27.log (Permission denied)
And also i could use
journalctl -t tomcat

Additional context

Here is the source of the tip for SyslogIdentifier in systemd:
https://stackoverflow.com/a/43830129/1654749

Thank you

@CedricLevasseur
Copy link
Author

I'm working on a Pull Request

This was referenced Apr 27, 2022
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

1 participant