IPSLA -- To monitor more than one probes

[sreinhardt]

This plugin also seems to have some issues with the flags as well and seems like it has several issues throughout the plugin, solely based on the output you sent us. In addition to that, the data with -i ALL is not properly formatted for nagios to interpret as check returns or performance data. The check return being multi-lines is fine, however the performance data doing so and the entire message having multiple | characters is not. Per the Plugin Development Guidelines it actually needs to be one | and space separated names and values after that. I would suggest speaking with the developer of the plugin if you wish to keep using it. Otherwise the one scottwilkerson listed earlier does in fact have checks for jitter and ping, it is just not listed in the help for it.

[Kif]

yes i have used which scott mentioned earlier but it is not showing me the graph, using -ALL argument

[slansing]

How long have you allowed for the performance data to be graphed? If the plugin does indeed function correctly and report that data I would give the plugin about 30 minutes to fill the data and plot two data-points "at least." Though if it is still not plotting the data, you should try to contact the developer of the plugin as has been previously suggested.

[Kif]

Hi guys,

Now I am using the pluggin which is in Nagios Exchange and i am still having some issues with it. When i run it as a service i can see all the statistics and also all the performance graphs but when i run it as host i can see all the statistics but in term of performance graph i can only see graph for just 1 IPSLA out of 3. I am pretty sure i am missing something minor here.

Thanks

Kif

[scottwilkerson]

can you run this plugin from the command line and show the output...

thanks

[Kif]

[root@c1ecn-nagios1 libexec]# ./check_csco_ipsla.pl -H 1.1.1.1 -c XXXXXX -i ALL
IP SLA status: OK | Total-Time=471
IP SLA 10 # HTTP ( http ) status: OK
IP SLA 100 # ping ( echo ) status: OK
IP SLA 15 # jitter ( udp-jitter ) status: OK | HTTP=410
ping=16
jitter=45

Please disregard the name of the pluggin as i had to change for some testing, its the same pluggin as in Nagios Exchange (check_cisco_ipsla.pl)

[scottwilkerson]

It looks like the plugin isn't returning the performance data in the correct format when you run it with -i ALL

According to Nagios plug-in development guidelines

Performance data is defined by Nagios as "everything after the | of the plugin output" - please refer to Nagios documentation for information on capturing this data to logfiles. However, it is the responsibility of the plugin writer to ensure the performance data is in a "Nagios plugins" format. This is the expected format:

'label'=value[UOM];[warn];[crit];[min];[max]

Notes:

space separated list of label/value pairs

label can contain any characters except the equals sign or single quote (')

the single quotes for the label are optional. Required if spaces are in the label

label length is arbitrary, but ideally the first 19 characters are unique (due to a limitation in RRD). Be aware of a limitation in the amount of data that NRPE returns to Nagios

to specify a quote character, use two single quotes

warn, crit, min or max may be null (for example, if the threshold is not defined or min and max do not apply). Trailing unfilled semicolons can be dropped

min and max are not required if UOM=%

value, min and max in class [-0-9.]. Must all be the same UOM

warn and crit are in the range format (see Section 2.5). Must be the same UOM

UOM (unit of measurement) is one of:

no unit specified - assume a number (int or float) of things (eg, users, processes, load averages)

s - seconds (also us, ms)

% - percentage

B - bytes (also KB, MB, TB)

c - a continous counter (such as bytes transmitted on an interface)

It is up to third party programs to convert the Nagios plugins performance data into graphs.