Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1591231

Summary:	Data from engine with UTC is parsed and saved correctly by Elasticsearch
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Francisco Garcia <fgarciad>
Component:	ovirt-engine-metrics	Assignee:	Shirly Radco <sradco>
Status:	CLOSED ERRATA	QA Contact:	Ivana Saranova <isaranov>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	dcadzow, eedri, lleistne, mperina, sradco
Target Milestone:	ovirt-4.3.4	Keywords:	ZStream
Target Release:	4.3.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-20 14:48:27 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Metrics	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Francisco Garcia 2018-06-14 10:48:44 UTC

Description of problem:

Currently the RHV Metrics Store documentation regarding Engine logs config is unclear :

https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html-single/metrics_store_installation_guide/#Prerequisites

Currently it reads:


"""
Manager Machine Prerequisites

Ensure that the time stamp in the /var/log/ovirt-engine/engine.log file contains a UTC offset suffix, rather than a letter such as Z or A. For example: 2018-03-27 13:35:06,720+01
"""

Expected results:

The document should describe what to change to achieve the expected logging, or point to a KCS describing the how to.

Comment 3 Sandro Bonazzola 2019-01-28 09:41:24 UTC

This bug has not been marked as blocker for oVirt 4.3.0.
Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.

Comment 5 Shirly Radco 2019-02-25 07:33:55 UTC

Please test this after the move to Rsyslog this may not be an issue anymore.

Comment 6 Lucie Leistnerova 2019-02-26 07:26:08 UTC

What exactly should be tested here? Shouldn't just the documentation be changed?

Comment 7 Shirly Radco 2019-02-26 07:54:10 UTC

When engine machine is configured in utc the the engine.lod dates will have a Z instead of +00:00 for timezone.
Please check that this is the case. Then configure metrics on the hosts 
and check that the logs are being parsed and saved currectly to elasticsearch, by inspecting the logs in Kibana.

Comment 9 Eyal Edri 2019-05-16 08:19:18 UTC

the bot didn't ack the bug, might be due to missing z-stream KeyWord. adding.

Comment 10 Ivana Saranova 2019-06-12 11:56:35 UTC

If I understand this bug correctly, then the purpose of it is to test that engine with UTC will have its logs parsed correctly to Kibana with metrics. The line about ensuring the timestamping in engine.log is not longer present in the official documentation and the parsing should work correctly with both offset and Z timestamps, therefore I'm changing the summary for this bug.

Steps:
1) Set engine timezone to UTC

timedatectl set-timezone UTC

2) Connect engine to metrics store (full guide is in the official documentation)

/usr/share/ovirt-engine-metrics/setup/ansible/configure_ovirt_machines_for_metrics.sh

3) See engine.log and check that it has Z timestamps
4) Check that data is sent to Kibana and parsed correctly

Result:
Engine log has correct timestamp and data is showing correctly in Kibana.

Verified in:
ovirt-engine-4.3.4.3-0.1.el7.noarch
ovirt-engine-metrics-1.3.1.1-1.el7ev.noarch

Comment 12 errata-xmlrpc 2019-06-20 14:48:27 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:1565