check_mssql query_perf and Graphs
Posted: Wed Feb 18, 2015 10:11 pm
Hi,
We are running Nagios XI 2014R2.0 VMware image 64bit / CentOS 6.5 with no special configurations.
I am using MSSQL Query check to graph a single value returned from the SQL query and am having problems with the resultant graph.
An example of the Performance Data as viewed in the Advanced tab of the service check is:
Performance Data: query_duration=0.788114s;300;900 query_perf=3;;
The query_perf value is what the SQL query returns and is what I want to graph. Only whole number are ever returned. However the performance graph never plots these numbers. What it does plot is a fraction of the number.
Eg. query_perf = 5, plot = 4.687
The plotted numbers are usually a little below the actual query_perf value, however there was one time where it was a little more. I was initially thinking that maybe the query_duration was being taken off the query_result however this doesn't seem to be the case as the numbers don't add up correctly.
Any help with this would be appreciated.
Cheers,
Simon
We are running Nagios XI 2014R2.0 VMware image 64bit / CentOS 6.5 with no special configurations.
I am using MSSQL Query check to graph a single value returned from the SQL query and am having problems with the resultant graph.
An example of the Performance Data as viewed in the Advanced tab of the service check is:
Performance Data: query_duration=0.788114s;300;900 query_perf=3;;
The query_perf value is what the SQL query returns and is what I want to graph. Only whole number are ever returned. However the performance graph never plots these numbers. What it does plot is a fraction of the number.
Eg. query_perf = 5, plot = 4.687
The plotted numbers are usually a little below the actual query_perf value, however there was one time where it was a little more. I was initially thinking that maybe the query_duration was being taken off the query_result however this doesn't seem to be the case as the numbers don't add up correctly.
Any help with this would be appreciated.
Cheers,
Simon