SSH Script Advanced History

Hey Patrik,

you missed a setting ;). Go to your PRTG-Website => Configuration => System => Web Interface

There on the bottom is a setting box with values for graphs. Set up this, for your choice. but be sure, that any changes has an result to the performance of your PRTG. Especially the RAM should be used more if you got a lot of sensors.

Best

Sascha

Jan, 2015 - Permalink

I think I was not clear enough.

History, "2-365 days" are working on all other sensors except this one. For example, the traffic sensor on my wireless bridge shows kbit/s in all graphs.

See link below for a visual description

http://imgur.com/a/Fuj3l

1. The sensor I'm seeing this error.
2. "Live Data" - correct values in Celsius
3. "2 days"-History - Showing non existent %-values.

/P

Jan, 2015 - Permalink

Hey Patrik,

now it is more clear. I see you use an SSH Script Sensor, what is the "unit" in your script?

Please refer on "Channel Unit Types" on this page https://www.paessler.com/manuals/prtg/exe_script_advanced_sensor

Maybe this could be the problem. Furthermore % in the graph is ok, because the error is in %, but for the values from your script, this means a funny mistake.

Could you post an example of your xml code? Run the script in shell and post the result - please blank information from your company.

Best

Sascha

Jan, 2015 - Permalink

Dear Patrik

Are you using a lookup table for this sensor? In this case, the live graph will show the actual value. The other graphs however use averages (because there are more data points than pixels to draw.) Since lookup entries cannot be really averaged, PRTG shows the per cent of the defined range instead.

Actual values cannot be shown because there are way more data points than pixels.

Jan, 2015 - Permalink

This is the script I'm running.

#!/bin/bash
#
array=( da1 da2 da3 da4 da5 da6 da7 da8 da9 da10 da11 da12 da13 da14 )

function disk_temperature {
Temp=$(smartctl -A /dev/$1 | grep "194 T" | cut -d: -f3 | awk '{print $10}')
echo "$Temp"
}

echo "<prtg>"

# <-- Start
for i in "${array[@]}"
do

echo -n "   <result>
       <channel>Disk: $i</channel>
         <value>"
disk_temperature $i
echo "</value>
         <ValueLookup>linux.ssh</ValueLookup>
   </result>"
done
# End -->
echo "</prtg>"
exit

Output is as follow

[root@nas] /var/prtg/scriptsxml# ./array.sh
<prtg>
   <result>
       <channel>Disk: da1</channel>
         <value>28
</value>
         <ValueLookup>linux.ssh</ValueLookup>
   </result>
   <result>
       <channel>Disk: da2</channel>
         <value>29
</value>
         <ValueLookup>linux.ssh</ValueLookup>
   </result>
   <result>
       <channel>Disk: da3</channel>
         <value>28
</value>
         <ValueLookup>linux.ssh</ValueLookup>
   </result>
   <result>
       <channel>Disk: da4</channel>
         <value>28
</value>
         <ValueLookup>linux.ssh</ValueLookup>
   </result>
   <result>
       <channel>Disk: da5</channel>
         <value>27
</value>
         <ValueLookup>linux.ssh</ValueLookup>
   </result>
   <result>
       <channel>Disk: da6</channel>
         <value>28
</value>
         <ValueLookup>linux.ssh</ValueLookup>
   </result>
   <result>
       <channel>Disk: da7</channel>
         <value>28
</value>
         <ValueLookup>linux.ssh</ValueLookup>
   </result>
   <result>
       <channel>Disk: da8</channel>
         <value>26
</value>
         <ValueLookup>linux.ssh</ValueLookup>
   </result>
   <result>
       <channel>Disk: da9</channel>
         <value>26
</value>
         <ValueLookup>linux.ssh</ValueLookup>
   </result>
   <result>
       <channel>Disk: da10</channel>
         <value>26
</value>
         <ValueLookup>linux.ssh</ValueLookup>
   </result>
   <result>
       <channel>Disk: da11</channel>
         <value>27
</value>
         <ValueLookup>linux.ssh</ValueLookup>
   </result>
   <result>
       <channel>Disk: da12</channel>
         <value>28
</value>
         <ValueLookup>linux.ssh</ValueLookup>
   </result>
   <result>
       <channel>Disk: da13</channel>
         <value>26
</value>
         <ValueLookup>linux.ssh</ValueLookup>
   </result>
   <result>
       <channel>Disk: da14</channel>
         <value>28
</value>
         <ValueLookup>linux.ssh</ValueLookup>
   </result>
</prtg>

Do I have to change anything in my script to add units? I thought I could just set custom unit in PRTG channel-properties?

Best Regards Patrik

Jan, 2015 - Permalink

Dear Patrik

If you use a lookup for your sensor, the aggregated data cannot be shown as unit. While it is acceptable to use averages of unit values, lookup values normally represent a pointer to a string. It normally makes no sense to compute averages of pointers.

To always see the unit, please use no lookup tables.

The custom unit definition is documented within the PRTG webinterface, menu Setup / PRTG API, tab Custom Sensors, section "Advanced Exe/Script sensor, Advanced SSH Script sensor, and Advanced HTTP Push data sensor".

Jan, 2015 - Permalink

Thanks you very much Arne!

Jan, 2015 - Permalink