Como chegar a Kbits/s pela tabela raw? Quero importar da tabela raw o consumo de banda de um dispositivo e quando importo ela vem com uma configuração em Raw.
Article Comments
Dear Stephan,
Simply dividing "Traffic In (Speed)(RAW)" by 1024 we do not find the figure "Traffic In (Speed) kbit/s". First, we need to know what unit is in the column "Traffic In (Speed)(RAW)" in order to apply a constant to reach kbit/s.
As we were in a hurry to build some reports to our customers, we copied many speed columns to an Excel worksheet and calculated an average constant 124.95 resulted from Speed (RAW) / Speed.
So, basically, our question is: What is the unity reflected in "Traffic In (Speed)(RAW)" ???
Feb, 2019 - Permalink
There seems to be some confusion - let's see if we can clean this up a bit:
lower case b normally indicates bit
upper case B normally indicates Byte
- 8 bit = 1 Byte
- Kilo
- kilo means factor 1000 - in theory - with but's
- 1 kilo bit => 1000 bit (https://www.gbmb.org/kbit-to-bit)
- 1 kilo Byte => 1024 Byte (binary) (https://www.gbmb.org/kb-to-bytes)
It is very easy to confuse all those numbers...
Traffic speed is often defined in BIT - now your math goes more straight forward..
What is it now that you really want to know? I understand you exported data from various sensors to a report and you see an average speed of 124.95 (bit / kilo bit / ... ???) What exactly do you want to know?
Regards
Florian Rossmark
Feb, 2019 - Permalink
Florian,
What exactly I want to know:
Col 13) Output Traffic (Speed) = 69 kbit/s Col 14) Output Traffic (Speed) (RAW) = 8614.8261
What is the unity of the value 8614.8261 in Col 14?
Which calculation led to Col 13 = 69 kbit/s ?
Regards,
Thiago Ferreira Patricio www.netcenter.com.br
Feb, 2019 - Permalink
Dear Thiago,
the raw data is included in the output, but not intended to be used by the customer. (Some, but not all API calls support the parameter &noraw=1 to only include readable output.)
The factor you mention earlier is in fact 125, because kilo = 1000, Bit to Byte = 8.
1000 / 8 = 125.
Feb, 2019 - Permalink
The raw table should always be bits, so dividing it by 1024 should get you the kbit/s. Is that what you're after? That's what I got from the translation :)
PRTG Scheduler | PRTGapi | Feature Requests |WMI Issues | SNMP Issues
Kind regards,
Stephan Linke, Tech Support Team
Feb, 2019 - Permalink