I've been working on generating reports for multiple sensors as part of automated reporting.

I am wondering what units are used for the Downtime(RAW) value. Should I interpret it as a percentage that needs to be divided by 10000?

I've compared the historic data report with the raw data obtained via the csvexport tool:

csvexport -pu=YOURLOGIN -pp=PASSWORD -ps=YOUR.PRTG.INSTANCE -s=16171 -to=90 -av=3600 -sd=2015-02-28-15-00-00 -ed=2015-03-02-15-00-00 -co -fc="Date T ime,Downtime(RAW),Downtime"

16171 1-3-2015 21:00:00 - 22:00:00 0.0000 16171 1-3-2015 22:00:00 - 23:00:00 236.300 16171 1-3-2015 23:00:00 - 0:00:00 513.500 16171 2-3-2015 0:00:00 - 1:00:00 0.0000

From the historic report ran via https://YOUR.PRTG.INSTANCE/historicdata_html.htm?id=16171&sdate=2015-02-28-15-00-00&edate=2015-03-02-15-00-00&avg=3600&pctavg=300&pctshow=false&pct=95&pctmode=false&hide=2,3,4,5,6,7,8,9,10

I see the following values during this period: Interval Downtime 1-3-2015 22:00:00 - 23:00:00 24% 1-3-2015 23:00:00 - 00:00:00 51%

Downtime for PRTG is the time between at least two "DOWN"-Conditions. So if the next scan after the "first Down-Scan" results in an UP-State of a sensor, then this will not be accounted as downtime. Furthermore, the log only shows status-changes, but probably there were more requests being made. You could check the Historic Data (with RAW Data), to see how many requests exactly failed and how long the sensor was down.

Article Comments

Dear Sander

We usually recommend to use the user-friedly formatted version, not the raw format. Depending on the API call and node, down / coverage raw data can be shown in different formats. Internally, it is a fixpoint number with 4 decimal places. You are correct, if you extract the number as raw integer, please divide it by 10000.


Mar, 2015 - Permalink