Previously, the graph for cluster utilization did not display values in percentage on the Y-axis. This happened because the plugin used the default template where the scale value of the graph was not fixed. With this fix, a specific template is implemented for the Nagios plugin.
Description of problem:
The graph for cluster utilization should show values in percentage on the Y-axis. The scale of the graph changes based on the utilization. That should not happen. Warning and critical lines does not appear on the graph when the utilization does not cross critical or warning levels.
Version-Release number of selected component (if applicable):
gluster-nagios-addons-0.1.8-1.el6rhs.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Add a cluster as a service on one of the hosts being monitored.
2. Create data on the volume in that cluster.
3. Check the cluster utilization graph.
Actual results:
The values on the Y-axis do not have a unit associated.
The scale on the Y-axis changes as the brick utilization changes.
Lines for warning and critical levels are not being displayed on the graph.
Expected results:
Show the Y-axis values in percentage.
The scale on the Y-axis should not change with utilization.
warning and critical lines should be displayed on the graph even if the utilization is zero.
Additional info:
verified and works fine with build nagios-server-addons-0.1.9-1.el6rhs.noarch.
With the fix in this build, cluster utilization graph Y-axis does not change with utilization.
scale on the y-axis is shown as % Usage.
warning and critical lines should be displayed on the graph when utilization is zero.
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://rhn.redhat.com/errata/RHBA-2015-0039.html
Comment 12Red Hat Bugzilla
2023-09-14 02:11:27 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days