Bug 88075

Summary:	journalctl: MIssing priority label makes log messages hard to read.
Product:	systemd	Reporter:	Alec Leamas <leamas.alec>
Component:	general	Assignee:	systemd-bugs
Status:	RESOLVED INVALID	QA Contact:	systemd-bugs
Severity:	normal
Priority:	medium
Version:	unspecified
Hardware:	Other
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description Alec Leamas 2015-01-05 22:03:48 UTC

When running out existing code using plain syslog + 'cat messages.log' the lines of info were something like

INFO: Nothing special happened
ERROR: Bad things happened.

The error messages are really designed for being displayed in this context, where the first item clearöly indicates the severity of the condition causing the log entry.

Now, as of 208 it seems that journalctl does not display these labels. When users only sees the text they don't have the immediate classification from the label.

I would like a new switch or preferably configuration which makes journalctl display the label the same way as it existed in /var/log/messages etc.

Comment 1 Zbigniew Jedrzejewski-Szmek 2015-01-05 22:14:07 UTC

(In reply to Alec Leamas from comment #0)
> When running out existing code using plain syslog + 'cat messages.log' the
> lines of info were something like
> 
> INFO: Nothing special happened
> ERROR: Bad things happened.
Are you sure? My /var/log/messages looks like

an  5 17:08:45 host systemd: Starting Fingerprint Authentication Daemon...
Jan  5 17:08:45 host dbus[653]: [system] Successfully activated service 'net.reactivated.Fprint'
Jan  5 17:08:45 host systemd: Started Fingerprint Authentication Daemon.

and journalctl

Jan 05 17:08:45 host systemd[1]: Starting Fingerprint Authentication Daemon...
Jan 05 17:08:45 host dbus[653]: [system] Successfully activated service 'net.reactivated.Fprint'
Jan 05 17:08:45 host systemd[1]: Started Fingerprint Authentication Daemon.

journalctl output was designed to be similar to standard rsyslog format on Fedora.

Comment 2 Alec Leamas 2015-01-05 22:40:32 UTC

nope, I'm not sure... mixed memories from console output and, double-checking, some local configuration in rsyslog.conf.

I understand your question as you not are intending to do anything about this. This is really all I need right now, before updating the application code. Sorry for the noise, too tired it seems. Closing.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.