Description of problem: Timestamp is missing timezone in the engine.log instead there is "Z", this means fluentd is unable to parse the log messages. Version-Release number of selected component (if applicable): 4.2.2.4-0.1.el7 How reproducible: Steps to Reproduce: 1.Have ovirt engine in utc 2.Check engine.log timestamp 3. Actual results: Timestamp example: 2018-03-29 06:53:33,581Z INFO ... Expected results: 2018-03-29 06:53:33,581+00 INFO ... Additional info:
Nothing is broken, engine logs comply with ISO 8601 [1] standard, where Z is correct identification for UTC time zone. We are using "X" [2] to identify that we want logs with ISO 8601 time zone, there's no option how to control that "+00:00" is used instead of "Z". And what's even more important "Z" is preferred over "+00:00" to identify UTC time zone. [1] https://en.wikipedia.org/wiki/ISO_8601#Coordinated_Universal_Time_(UTC) [2] file:///home/mperina/Documents/api-1.8.0/index.html
(In reply to Martin Perina from comment #1) > Nothing is broken, engine logs comply with ISO 8601 [1] standard, where Z is > correct identification for UTC time zone. > > We are using "X" [2] to identify that we want logs with ISO 8601 time zone, > there's no option how to control that "+00:00" is used instead of "Z". And > what's even more important "Z" is preferred over "+00:00" to identify UTC > time zone. > > [1] https://en.wikipedia.org/wiki/ISO_8601#Coordinated_Universal_Time_(UTC) > [2] file:///home/mperina/Documents/api-1.8.0/index.html Sorry here's correct public link: [2] https://docs.oracle.com/javase/8/docs/api/java/text/SimpleDateFormat.html
Reopenning on metrics, where we need to support this format from the fluentd side.
verified in ovirt-engine-metrics-1.1.4-1.el7ev.noarch Timestamp type: 2018-04-19 13:43:44,043Z
This bugzilla is included in oVirt 4.2.3 release, published on May 4th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.3 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.