(→Scope) |
No edit summary |
||
| Line 127: | Line 127: | ||
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuid required? include a link to the releng issue. | <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuid required? include a link to the releng issue. | ||
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication --> | The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication --> | ||
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: Not affected <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | |||
<!-- Please check the list of Fedora release deliverables and list all the differences the feature brings --> | |||
* Policies and guidelines: Not affected <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | |||
<!-- Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. --> | |||
* Trademark approval: Not needed for this Change | |||
<!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://fedorahosted.org/council/ ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. --> | |||
== Upgrade/compatibility impact == | == Upgrade/compatibility impact == | ||
| Line 184: | Line 190: | ||
--> | --> | ||
[[Category: | [[Category:ChangeAnnounced]] | ||
<!-- When your change proposal page is completed and ready for review and announcement --> | <!-- When your change proposal page is completed and ready for review and announcement --> | ||
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | ||
Revision as of 13:23, 29 May 2017
Rsyslog log format change proposal
Summary
Currently Fedora uses RSYSLOG_TraditionalFileFormat as a default format for timestamps in its logs. There is missing year and timezone. This proposal aims to change this by adopting ISO 8601 and RFC 3339 compliant timestamp format known as RSYSLOG_FileFormat instead of current RSYSLOG_TraditionalFileFormat.
Owner
- Name: Radovan Sroka
- Email: rsroka@redhat.com
- Name: Roman Pavelka
- Email: rpavelka@redhat.com
- Release notes owner:
Current status
Detailed Description
Currently Fedora, RHEL and CentOS use RSYSLOG_TraditionalFileFormat for log’s timestamp, so timestamps in files like /var/log/messages, /var/log/cron and /var/log/secure looks like e.g.:
May 29 13:37:50 localhost systemd: Starting Fingerprint Authentication Daemon...
This format has few disadvantages
- Does not include year which sometimes may be needed, mostly when doing long term analysis or some investigation.
- Does not include timezone which may be important piece when working with system scattered around the globe.
- It is not standard format. Standards are ISO 8601 and more strict RFC 3339
We would propose to change this to defaults to standard format with timezone included.
We are suggesting new RSYSLOG_FileFormat that looks like e.g.:
2017-05-29T13:40:50.976409+02:00 localhost systemd: Stopping System Logging Service...
All necessary changes are here:
$ diff rsyslog.conf.orig rsyslog.conf -u --- rsyslog.conf.orig 2017-05-26 16:31:09.768671818 +0200 +++ rsyslog.conf 2017-05-26 16:30:36.093682748 +0200 @@ -30,7 +30,7 @@ global(workDirectory="/var/lib/rsyslog") # Use default timestamp format -module(load="builtin:omfile" Template="RSYSLOG_TraditionalFileFormat") +module(load="builtin:omfile" Template="RSYSLOG_FileFormat") # Include all config files in /etc/rsyslog.d/ $IncludeConfig /etc/rsyslog.d/*.conf
Benefit to Fedora
Compliance to international standard, more information available in logs.
Scope
- Proposal owners:
- commit necessary changes
- create rsyslog build
- Other developers: none
- Release engineering: Releng#6818
- List of deliverables: Not affected
- Policies and guidelines: Not affected
- Trademark approval: Not needed for this Change
Upgrade/compatibility impact
Someone parsing logs would need update his/her scripts or revert configuration to traditional one.
How To Test
Restart rsyslog by “systemctl restart rsyslog” and check “sudo tail /var/log/messages”, timestamp should be in ISO 8601 format, e.g.: 2017-05-26T16:25:47.125900+02:00
User Experience
Regular users should not experience any change. Administrators would benefit from more information provided, especially when maintaining a system scattered in more timezones or doing long-term analysis.
Dependencies
None
Contingency Plan
- Contingency mechanism: Rsyslog maintainer will either change the configuration or keep the original.
- Contingency deadline: Fedora 27 Beta freeze
- Blocks release? No
- Blocks product? No
Documentation
http://www.rsyslog.com/doc/v8-stable/configuration/templates.html