JBoss ON metric graph is missing all values if min, max, and avg values are all the same within a selected time range that includes 60 or more collected values

Environment

• Red Hat JBoss Operations Network (ON) 3.2, 3.3
• Resource metrics monitoring page displays a graph that:
  • has the same minimum, maximum, and average values for all time values along the x axis;
  • displays 60 data point metric values as 0 or with a graph bar having a height of 1 pixel;
  • has no values defined or displayed on its y axis;

Issue

• Graph representation Free Swap Space not correct
• Graph shows 0 at some intervals
• Graph is empty
• No values on graph

Resolution

This issue has been captured in This content is not included.Red Hat Bugzilla 1146266 and will be addressed in a future release of JBoss ON.

Although the graph does not render correctly, the minimum, maximum, and average values displayed at the top of the graph are correct.

Root Cause

When a time range is selected that includes 60 or more collected metric values that all have the exact same minimum, maximum, and average values, the graph fails to render its data points. This is due to a bug in how the value range is being determined for plotting the graphs data points. See This content is not included.Red Hat Bugzilla 1146266 for more information.

Diagnostic Steps

• View the browser's web console or log for the affected metric graph's data:

    { "x":1411497374906, "barDuration": "24.0 m",  "high":92, "highFormatted":"92 %", "low":92, "lowFormatted":"92 %", "avg":92, "avgFormatted":"92 %"},
    { "x":1411498814906, "barDuration": "24.0 m",  "high":92, "highFormatted":"92 %", "low":92, "lowFormatted":"92 %", "avg":92, "avgFormatted":"92 %"},
    { "x":1411500254906, "barDuration": "24.0 m",  "high":92, "highFormatted":"92 %", "low":92, "lowFormatted":"92 %", "avg":92, "avgFormatted":"92 %"},
    { "x":1411501694906, "barDuration": "24.0 m",  "high":92, "highFormatted":"92 %", "low":92, "lowFormatted":"92 %", "avg":92, "avgFormatted":"92 %"},
    ...
    { "x":1411578014906, "barDuration": "24.0 m",  "high":92, "highFormatted":"92 %", "low":92, "lowFormatted":"92 %", "avg":92, "avgFormatted":"92 %"},
    { "x":1411579454906, "barDuration": "24.0 m",  "high":92, "highFormatted":"92 %", "low":92, "lowFormatted":"92 %", "avg":92, "avgFormatted":"92 %"},
    { "x":1411580894906, "barDuration": "24.0 m",  "high":92, "highFormatted":"92 %", "low":92, "lowFormatted":"92 %", "avg":92, "avgFormatted":"92 %"},
    { "x":1411582334906, "barDuration": "24.0 m",  "high":92, "highFormatted":"92 %", "low":92, "lowFormatted":"92 %", "avg":92, "avgFormatted":"92 %"}
  

  In the above output, all 60 values have the value 92 for high, low, and avg during a 24 hour period. If this is the case, this issue applies.

  If any of the 60 values had a value other then 92 this issue most likely does not apply.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.