Support Migration Notice: To update migrated JIRA cases click here to open a new case use www.vmware.com/go/sr | vFabric Hyperic 5.7.0 is Now Available

Hyperic HQ

DataPoints on MetricChart are mis-plotted by 1 minute

Details

  • Case Links:
    none
  • Regression:
    Yes
  • Tags:

Description

When viewing the current health data for a resource's metric chart the data points are shifted by 1 minute.

If Metric has 5 minute itv. It should only be plotted at even 5 minute intervals (:05, :10, :15, etc) however, it is actually plotted 1 minute early (:04, :09, :14, etc) (see screenshot)

This has a significant impact on quality of the product as metric values are not accurate when viewed in the ui.

Issue Links

Activity

Hide
Wes Schlichter added a comment -

In screenshot those metrics should be shown at 6:05.

The data exported to CSV appears to suffer the same issue.

Show
Wes Schlichter added a comment - In screenshot those metrics should be shown at 6:05. The data exported to CSV appears to suffer the same issue.
Hide
Mayan Weiss added a comment -

actually this if the measurement represent the whole 5 minute it should be reflected in the UI. showing it in the rounded time slot is also misleading.

and BTW do we know (from the actual measurement) if the offset here is for 1 minute or 4?

Show
Mayan Weiss added a comment - actually this if the measurement represent the whole 5 minute it should be reflected in the UI. showing it in the rounded time slot is also misleading. and BTW do we know (from the actual measurement) if the offset here is for 1 minute or 4?
Hide
Wes Schlichter added a comment -

I don't understand your first comment.

It doesn't matter what the itv is. Any dp plotted on the graph is shifted to one spot to the left. This applies to Availability data also. The data in the db will have the expected timestamp (:05 instead of :04) and agent log will show when it was collected as being correct. CSV export of the data also shows the correct timestamp.

Show
Wes Schlichter added a comment - I don't understand your first comment. It doesn't matter what the itv is. Any dp plotted on the graph is shifted to one spot to the left. This applies to Availability data also. The data in the db will have the expected timestamp (:05 instead of :04) and agent log will show when it was collected as being correct. CSV export of the data also shows the correct timestamp.
Hide
Wes Schlichter added a comment -

Determined this to be caused by improper rounding of begin and end times for datapoint gathering. This would also appear to be the same issue causing https://jira.hyperic.com/browse/HHQ-4297

Show
Wes Schlichter added a comment - Determined this to be caused by improper rounding of begin and end times for datapoint gathering. This would also appear to be the same issue causing https://jira.hyperic.com/browse/HHQ-4297
Hide
Wes Schlichter added a comment -

DataManager was improved in 4.5 and a couple errors in logic were introduced which created this regression. The begin/end ranges were not properly rounded to exclude seconds and the placeholder for empty metrics (a 5 minute itv with a 60 minute display range would have 48 empty metrics) weren't being populated properly.

Show
Wes Schlichter added a comment - DataManager was improved in 4.5 and a couple errors in logic were introduced which created this regression. The begin/end ranges were not properly rounded to exclude seconds and the placeholder for empty metrics (a 5 minute itv with a 60 minute display range would have 48 empty metrics) weren't being populated properly.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
    Last comment:
    2 years, 20 weeks, 5 days ago