Search Exchange
Search All Sites
Nagios Live Webinars
Let our experts show you how Nagios can help your organization.Login
New ListingsDirectory Tree
check_mssql_sp
Current Version
0
Last Release Date
2014-12-12
Owner
Hits
14507
Files:
| File | Description |
|---|---|
| check_mssql_sp_filter | the plugin |
Meet The New Nagios Core Services Platform
Built on over 25 years of monitoring experience, the Nagios Core Services Platform provides insightful monitoring dashboards, time-saving monitoring wizards, and unmatched ease of use. Use it for free indefinitely.
Monitoring Made Magically Better
- Nagios Core on Overdrive
- Powerful Monitoring Dashboards
- Time-Saving Configuration Wizards
- Open Source Powered Monitoring On Steroids
- And So Much More!
Allow you to run a stored procedure on an MSSQL server. Loosely based on the check_mssql plugin. Loops and output the data of all returned rows. Checks warnings, criticals and also allows to use columns fields as filters to the value name field. See example.
Syntax for the procedure name:
'
* it does no param initialization so might run into issue if you use params. I am using one parameter at the moment without any issue.
Syntax for warning / critical check is as follow (no spaces and case sensitive):
name_of_the_column=warning_or_critical_value;*
Syntax for filters / ignores check is as follow (no spaces and case sensitive):
name_of_the_column;*
Syntax
check_mssql_sp -H -U -P -s -d -w -c -f -i
An example:
check_mssql_sp -H 10.100.101.63 -U sa -P xxxXXXxxx -s 's_monitoring_queue_adv' -d itrans_igs_async -w 'queue=40;' -c 'queue=50;' -f 'queue_code'
when using the -i arg, you can actually get the system to ignore some columns returned by the stored procedure
Use at your own risks and please use stored procedure that don't do locks as much as possible :)
A concrete example with the following dataset :
header | network_code | throughput_in
1 | Telus B | 79
2 | Telus A | 39
3 | Others | 19
4 | NULL | 137
command:
./check_mssql_sp -H hostname -U user -P password -s storedproc -d database -f network_code
result:
OK - throughput_in_Telus_B=79,throughput_in_Telus_A=39,throughput_in_Others=19,throughput_in=137
|throughput_in_Telus_B=79,throughput_in_Telus_A=39,throughput_in_Others=19,throughput_in=137
Syntax for the procedure name:
'
Syntax for warning / critical check is as follow (no spaces and case sensitive):
name_of_the_column=warning_or_critical_value;*
Syntax for filters / ignores check is as follow (no spaces and case sensitive):
name_of_the_column;*
Syntax
check_mssql_sp -H
An example:
check_mssql_sp -H 10.100.101.63 -U sa -P xxxXXXxxx -s 's_monitoring_queue_adv' -d itrans_igs_async -w 'queue=40;' -c 'queue=50;' -f 'queue_code'
when using the -i arg, you can actually get the system to ignore some columns returned by the stored procedure
Use at your own risks and please use stored procedure that don't do locks as much as possible :)
A concrete example with the following dataset :
header | network_code | throughput_in
1 | Telus B | 79
2 | Telus A | 39
3 | Others | 19
4 | NULL | 137
command:
./check_mssql_sp -H hostname -U user -P password -s storedproc -d database -f network_code
result:
OK - throughput_in_Telus_B=79,throughput_in_Telus_A=39,throughput_in_Others=19,throughput_in=137
|throughput_in_Telus_B=79,throughput_in_Telus_A=39,throughput_in_Others=19,throughput_in=137
Reviews (0)
Be the first to review this listing!
