Bug 1423014 - Hawkular Metrics is missing the date in its timestamps
Summary: Hawkular Metrics is missing the date in its timestamps
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Hawkular
Version: 3.5.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Matt Wringe
QA Contact: Peng Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-16 21:04 UTC by Matt Wringe
Modified: 2018-04-26 01:37 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-12 19:13:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0884 0 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.5 RPM Release Advisory 2017-04-12 22:50:07 UTC

Description Matt Wringe 2017-02-16 21:04:04 UTC
The Hawkular Metrics logs are missing the date field in its timestamp.

Comment 1 Matt Wringe 2017-02-17 17:35:29 UTC
This is now fixed.

Entries in the log should now include the date as part of the timestamp.

eg: 2017-02-17 17:33:12,837 INFO  [org.hawkular.metrics.c....

Comment 2 Peng Li 2017-02-20 06:50:37 UTC
verified, logs contain date as part of timestamps.

version:
metrics-hawkular-metrics   3.5.0   b50862a32dd6   3 days ago   1.508 GB

# oc logs hawkular-metrics-1rxz2
2017-02-20 06:08:45,616 INFO  [org.hawkular.metrics.core.util.GCGraceSecondsManager] (metricsservice-lifecycle-thread) Checking tables in hawkular_metrics to see if gc_grace_seconds needs to be updated
2017-02-20 06:08:45,619 INFO  [org.hawkular.metrics.api.jaxrs.MetricsServiceLifecycle] (metricsservice-lifecycle-thread) HAWKMETRICS200005: Metrics service started
2017-02-20 06:08:45,631 INFO  [org.hawkular.metrics.core.util.GCGraceSecondsManager] (RxComputationScheduler-2) gc_grace_seconds for active_time_slices is set to 864000. Resetting to 0

Comment 4 errata-xmlrpc 2017-04-12 19:13:13 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-2017:0884

Comment 5 Matt Wringe 2017-05-23 20:25:59 UTC
@wsun: the test case is listed https://bugzilla.redhat.com/show_bug.cgi?id=1423014#c1 and verified here https://bugzilla.redhat.com/show_bug.cgi?id=1423014#c2

Is there something else that needs to be documented? Is this something that QA needs to do, or something the engineering side needs to complete?

Comment 6 Wei Sun 2017-05-24 06:05:50 UTC
(In reply to Matt Wringe from comment #5)
> @wsun: the test case is listed
> https://bugzilla.redhat.com/show_bug.cgi?id=1423014#c1 and verified here
> https://bugzilla.redhat.com/show_bug.cgi?id=1423014#c2
> 
> Is there something else that needs to be documented? Is this something that
> QA needs to do, or something the engineering side needs to complete?

Hi Matt,sorry for confusing you. Next time I'll put the comment on here for the keyword.
I added this keyword just to remind QE to add case/checkpoint in our test case,no any action from the developer.
Once we add the case/checkpoint for the bug,we will link the test case to the bug and will remove the keyword from the bug.


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