check_xi_mssql_server returning innacurate values

This support forum board is for support questions relating to Nagios xi, our flagship commercial network monitoring solution.
codell
Posts: 2
Joined: Mon Jun 25, 2012 5:24 pm

check_xi_mssql_server returning innacurate values

Post by codell »

And I mean *wildy* inaccurate values... like 32996357.0ms for Average Wait. Some metrics are measured correctly, like Lock Waits / Sec and Connection Time. See the attached .png for the MSSQL service details & results.

Running Nagios xi 64 .vhd on Hyper-V, Centos 6.2. I believe I have all the pre-reqs for the mssql plugin installed. The server I'm trying to monitor is MSSQL 2005 Sp3, running on Server 2003.

Any help much appreciated!
Capture.PNG
You do not have the required permissions to view the files attached to this post.
User avatar
nscott
Posts: 1040
Joined: Wed May 11, 2011 8:54 am

Re: check_xi_mssql_server returning innacurate values

Post by nscott »

I'm going to change how this plugin is implemented. Currently its implemented in a way that would allow for bogus numbers like this to happen as it bases most 'per second' metrics off of how long tempdb has been alive. I'm working on reimplementing it right now and hope to have something later today for it. I would appreciate it if you wouldn't mind testing out the changes.
Nicholas Scott
Former Nagios employee
codell
Posts: 2
Joined: Mon Jun 25, 2012 5:24 pm

Re: check_xi_mssql_server returning innacurate values

Post by codell »

Sure, I'd be happy to test an update for you.
Nitpat
Posts: 10
Joined: Fri Aug 17, 2012 8:49 am

Re: check_xi_mssql_server returning innacurate values

Post by Nitpat »

Hello guys,

Any update on this issue. We are also facing the same issue.

Thanks,
Nitin P
JulianFDRacing
Posts: 51
Joined: Tue Oct 16, 2012 9:45 am

Re: check_xi_mssql_server returning innacurate values

Post by JulianFDRacing »

I am suffering the same issue too but thought it was a MS issue with the counters value being 93x what it should be, I could be wrong as this info was passed on to me but could explain why development seems so slow on this