From Fedora Project Wiki
Line 72: Line 72:


<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
Currently Fedora, RHEL and CentOS use RSYSLOG_TraditionalFileFormat for
In files like /var/log/messages, /var/log/cron and /var/log/secure, format known as at is used for timestamps:
Mar  3 20:01:36
This format has few disadvantages
1. Does not include year which sometimes may be needed, mostly when doing long term analysis or some investigation.
2. Does not include timezone which may be important piece when working with system scattered around the globe.
3. It is not standard format. Standards are ISO 8601 and more strict RFC 3339
I would propose to change this to defaults to standard format with timezone included.





Revision as of 08:17, 5 May 2017


Change Proposal Name

Summary

Currently Fedora uses non-standard formats for date and time in its logs. Mainly there is missing year and timezone. This proposal aims to change this by adopting ISO 8601 and RFC 3339 compliant timestamps e.g.: 1996-12-19T16:39:57-08:00

Owner


Current status

Detailed Description

Currently Fedora, RHEL and CentOS use RSYSLOG_TraditionalFileFormat for

In files like /var/log/messages, /var/log/cron and /var/log/secure, format known as at is used for timestamps:

Mar 3 20:01:36

This format has few disadvantages

1. Does not include year which sometimes may be needed, mostly when doing long term analysis or some investigation.

2. Does not include timezone which may be important piece when working with system scattered around the globe.

3. It is not standard format. Standards are ISO 8601 and more strict RFC 3339

I would propose to change this to defaults to standard format with timezone included.


Benefit to Fedora

Scope

  • Proposal owners:
  • Other developers: N/A (not a System Wide Change)
  • Policies and guidelines: N/A (not a System Wide Change)
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

N/A (not a System Wide Change)

How To Test

N/A (not a System Wide Change)

User Experience

N/A (not a System Wide Change)

Dependencies

N/A (not a System Wide Change)

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change), Yes/No
  • Blocks product? product

Documentation

N/A (not a System Wide Change)

Release Notes