Hi there, Is there any way to change channel unit in sensor factory sensors?


Article Comments

Hello there,

It's possible to define units in the "Channel Definition" of a Factory Sensor the following way:

#<id>:<name>[<unit>]
<formula>

Here an Example:

#1:Traffic[kbit]
channel(1234,1)

[<unit>] is an optional unit description for the factory sensor's channel (for example, bytes). If you do not provide a unit, the sensor factory selects a suitable unit string automatically (recommended).

For further information, please take a look at this manual.


Kind regards,
Birk Guttmann, Tech Support Team


Jan, 2019 - Permalink

Dear Support Team, It was very very helpful and was great! Thanks a lot for your kind advice.


Jan, 2019 - Permalink

Dear Support Team, Unfortunately it doesn't work correctly. The sensor factory sensors don't inherit channel unit configuration. So regardless of their parents always show traffic speed in Gbit/s. (for example X Gbit/s) After your advise i add a Mbit at the end of channel name as you describe. But it shows a very large and incorrect value after that (for example Y). I expected it to be multiplied by 1000. In addition regardless of unit that i edit in channel definition, that value does not change at all. I mean if i set Mbit or Kbit or any other unit, The result is still the same big wrong number. (Same Y)


Jan, 2019 - Permalink

Hi there,

Please note that the factory sensor gathers raw data with the default unit of the source sensor and so also works with the these results. E.g. the raw data of a traffic Sensor is given in kbit/second.


Kind regards,
Birk Guttmann, Tech Support Team


Jan, 2019 - Permalink

Hi there, But it is not as you say in my PRTG. Each sensor factory has its own attitude regardless of its source channels. I mean some sensor factories's units are in Mbit/s and the others are in Gbit/s! And non of them are in bit/s or any other units!


Feb, 2019 - Permalink

Hi,

I'm sorry, my last statement was not correct and a bit misleading. I corrected it.


Kind regards,
Birk Guttmann, Tech Support Team


Feb, 2019 - Permalink