I know the sensor is in beta. That said, I noticed that when a device does not report data for a channel in the sensor PRTG records the value as 0 instead of null. This greatly affect number averaging. In the HTTP PUSH DATA ADVANCE sensor, it does handle lack of data in this manner.

Thanks. Dwight.

Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

Dear antinymldyls9e

The historic database of PRTG has no data value of null. If a sensor scan fails, the datapoint is not written at all, implying a null for the according scan. It is not possible to just set individual channels to null. Instead, zero is used.


Oct, 2016 - Permalink

I understand that this is how it currently works. That's why I titled this as a feature request. The sensor factory sensor handles compiling null data in this matter, but I presume it has significantly different underlying process.


Oct, 2016 - Permalink

Allow me to be honest: Due to the architecture of the PRTG database, this feature request has no chance of getting implemented in the foreseeable future.

PRTG cannot write a partial sensor result into the data base. The sensor factory has no historic data of its own, the aggregated data is generated on demand.


Oct, 2016 - Permalink