no rfc compliance with log output

Bug #1484888 reported by Benedikt von St. Vieth
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
oslo.log
Won't Fix
Undecided
Unassigned

Bug Description

Hi,
we moved from Icehouse to Kilo and removed the "use-syslog-rfc-format" config setting (because it should have gone since Juno). Since the update, our Logstash is not parsing the logs in a correct way.

Log lines appear as follow (with both use_syslog enabled and disabled, for all services) in log files and on the remote logstash daemon:
2015-08-14 11:11:44.296 11642 INFO nova.osapi_compute.wsgi.server [-] (11642) wsgi starting up on http://127.0.0.1:8874/

I can't see RFC 5424 or RFC 3164 compliance, for example:
<158>Aug 14 09:54:40 HOST rsyncd[13079]: sent 31 bytes received 197 bytes total size 0
<134>Aug 14 11:15:18 zam979 account-server: no_change:44 ts_repl:0 diff:0 rsync:0 diff_capped:0 hashmatch:0 empty:0

can anybody confirm this?

Revision history for this message
Doug Hellmann (doug-hellmann) wrote :

The log line format can be controlled with configuration options. The default is not likely to be compliant with the standards you mention. If you work out formatting settings that support those standards, we would be happy to add that information to the documentation.

Changed in oslo.log:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.