Bug 1408193 – [RFE] Update timestamp format in engine log to timestamp with timezone

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1408193 - [RFE] Update timestamp format in engine log to timestamp with timezone

Summary:	[RFE] Update timestamp format in engine log to timestamp with timezone

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	ovirt-engine
Classification:	oVirt
Component:	RFEs (Show other bugs)
Sub Component:
Version:	4.1.0
Hardware:	Unspecified Unspecified

Priority	medium Severity medium (vote)
Target Milestone:	ovirt-4.1.1
Target Release:	4.1.1.2
Assigned To:	Martin Perina
QA Contact:	Aleksei Slaikovskii
Docs Contact:

URL:
Whiteboard:
Keywords:	FutureFeature

Depends On:
Blocks:	oVirt-Metrics-and-Logs
	Show dependency tree / graph

Reported:	2016-12-22 07:24 EST by Shirly Radco
Modified:	2017-04-21 05:35 EDT (History)
CC List:	10 users (show)

See Also:
Fixed In Version:
Doc Type:	Enhancement
Doc Text:	From now on, all timestamp records for the engine and engine tools logs will contain a time zone to ease correlation between logs on the Manager and hosts. Previously engine.log contained a timestamp without a time zone, for example: 2017-02-27 13:35:06,720 INFO [org.ovirt.engine.core.dal.dbbroker.DbFacade] (ServerService Thread Pool -- 51) [] Initializing the DbFacade From now on there will always be a timezone identifier at the end of the timestamp part, for example: 2017-02-27 13:35:06,720+01 INFO [org.ovirt.engine.core.dal.dbbroker.DbFacade] (ServerService Thread Pool -- 51) [] Initializing the DbFacade
Story Points:	---
Clone Of:
Environment:
Last Closed:	2017-04-21 05:35:03 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	Infra
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Flags:	rule-engine: ovirt‑4.1+ gklein: testing_plan_complete- ylavi: planning_ack+ mperina: devel_ack+ pstehlik: testing_ack+

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
oVirt gerrit	67161	master	MERGED	core: Introduce logutils module	2017-02-13 10:57 EST
oVirt gerrit	67162	master	MERGED	tools: Add time zone to log records	2017-02-13 10:57 EST
oVirt gerrit	70114	master	MERGED	packaging: pythonlib: service: Add time zone to log records	2017-01-24 10:59 EST
oVirt gerrit	71116	ovirt-engine-4.1	MERGED	packaging: pythonlib: service: Add time zone to log records	2017-02-07 13:34 EST
oVirt gerrit	72207	ovirt-engine-4.1	MERGED	core: Introduce logutils module	2017-02-14 09:41 EST
oVirt gerrit	72208	ovirt-engine-4.1	MERGED	tools: Add time zone to log records	2017-02-14 09:41 EST
oVirt gerrit	72478	master	MERGED	core: Fix installing logutils.jar	2017-02-17 04:07 EST
oVirt gerrit	72484	ovirt-engine-4.1	MERGED	core: Fix installing logutils.jar	2017-02-17 05:07 EST
oVirt gerrit	72846	master	MERGED	core: Fix installing logutils.jar	2017-02-22 07:12 EST
oVirt gerrit	72884	ovirt-engine-4.1	MERGED	core: Fix installing logutils.jar	2017-02-23 04:27 EST
oVirt gerrit	72885	ovirt-engine-4.1.1.z	MERGED	core: Fix installing logutils.jar	2017-02-23 04:30 EST

Groups: None (edit)

Description Shirly Radco 2016-12-22 07:24:41 EST

Description of problem:
In order to be able to push the engine logs to the new metrics store we require the logs to include the timestamp with timezone, so it can be properly stored and later correlated with other logs and metrics.

Comment 5 Aleksei Slaikovskii 2017-02-16 11:35:25 EST

Verified on ovirt-engine-4.1.1.3-0.0.master.20170216131226.git07c3326.el7.centos.noarch

Note You need to log in before you can comment on or make changes to this bug.