hi.

i'm uses prtg 8

PRTG Collecting snmp data...

I would like to know how it was calculated and bps byte.

                                                Input(Volume)    Input(Speed)
07/21/2014 00:00:00 - 01:00:00	
   59,230 GByte	133 gbit/s	50,509 GByte	114 gbit/s	0 %	100 %
07/21/2014 01:00:00 - 02:00:00	
   39,097 GByte	93 gbit/s	35,867 GByte	86 gbit/s	0 %	100 %
07/21/2014 02:00:00 - 03:00:00	
   26,342 GByte	63 gbit/s	25,598 GByte	61 gbit/s	0 %	100 %
07/21/2014 03:00:00 - 04:00:00	
   18,232 GByte	44 gbit/s	18,426 GByte	44 gbit/s	0 %	100 %


Article Comments

Dear user

Please allow me to ask you to clarify your question. What exactly do you want to know about SNMP traffic data?


Jul, 2014 - Permalink

Hi there

When after collecting the data bandwidth snmp, is expressed in bits per second (bps).

However, transformation is possible in byte how to express.

I want to know how they will be calculated when you want to convert to a byte from bps at this time.


Jul, 2014 - Permalink

Dear user

To convert from bit to byte, please divide by 8.

However we use the prefix "kilo" differently. When uses as prefix for bit, we evaluate 1 k = 1000. In conjunction with byte, we take 1 K = 1024.

The same applies for the Mega and Giga prefix.


Jul, 2014 - Permalink

I appreciate the answer.

Please look at the contents of the first question.

Is the monitoring of data traffic.

Time: 07/21/201400: 00:00 - 01:00:00 Input: 59,230 GByte133 gbit / s Output: 50,509 GByte114 gbit / s

If you convert to 59,230 Byte, or 133 gbit / s?


Jul, 2014 - Permalink

Dear

PRTG historic Data Report

Date Time Input (volume) Input (speed) Output (volume) Output (speed)

07/22/2014 7,743 GByte 128 gbit/s 6,505 GByte 108 gbit/s

8bit = 1Byte 1024 Byte = 1 Kbyte

But... PRTG differ Report 7,743 Gbyte = 8,314,000,000,000 Byte => 66,512,000,000,000 bit

Input (Speed) 128 gbit/s ????


Jul, 2014 - Permalink

Dear user

In this case, it looks like that either "G" uses the 1000 prefix or "g" the 1024. I asked a developer, but since PRTG is constantly developed further, we cannot look into the source code of PRTG 8 any more.

It could be a bug, which however is fixed with the current PRTG 14 version.


Jul, 2014 - Permalink