Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
Starting Nmap 5.51 ( http://nmap.org ) at 2013-04-15 10:28 CDT
Nmap scan report for 10.4.2.63
Host is up (0.0012s latency).
PORT STATE SERVICE
1433/tcp open ms-sql-s
MAC Address: 78:E7:D1:F8:D5:AC (Hewlett Packard)
Nmap done: 1 IP address (1 host up) scanned in 5.92 seconds
/usr/local/nagios/libexec/check_nt -H <MSSQL SERVER IP HERE> -s <MSSQL NSCLIENT PASSWORD HERE> -p 12489 -v COUNTER -l "\\MSSQL\$<INSTANCE NAME HERE>:Buffer Manager\Page Life expectancy","Page Life expectancy is %.fsec" -w 100: -c 50:
Lets verify that we can connect to the database from the Nagios server.
Check the working command against the one you have configured in XI.
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
COMMAND: /usr/local/nagios/libexec/check_nt -H 10.4.2.63 -s "password" -p 12489 -v COUNTER -l [b]"\\\\MSSQL\\\$LIVE:Buffer Manager\\Page Life expectancy"[/b],"Page Life expectancy is %.fsec" -w 100: -c 50
OUTPUT: Page Life expectancy is 0sec | 'Page Life expectancy is %.fsec'=0.000000%;100.000000;50.000000;
But the original issue was to do with issues with check_mssql_database.py command your example is check_NT? Are you saying find the performance counter and use that instead?