What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
300.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

Difference between "speednet" and "bytesbandwith" unit types

Votes:

0

Your Vote:

Up

Down

Hi, I have created a python script to return data to PRTG. The scripts reads a json string containing upload and download bandwith values. In my Python script I use the following settings to send them to PRTG: ... csr.add_primary_channel(name="Download", value=d_b, unit=ValueUnit.SPEEDNET, speed_size=ValueSize.MEGABIT, is_float=False) csr.add_channel(name="Upload", value=u_b, unit=ValueUnit.SPEEDNET, speed_size=ValueSize.MEGABIT, is_float=False) ...

When I use the above code, the values in PRTG always show as "nnn /s" although I set the ValuSize in my script to MEGABIT. Also on the sensor Channel settings in PRTG I have no option to change that to Mbps.

When I use the ValueUnit.BYTESBANDWITH, with the same ValueSize.MEGABIT, the values show up as Kbit/s in PRTG, but I do have the option in PRTG to change them to Mbit/s

1) is this a bug in the Python PRTG module that it doesn't use the correct ValueSize?
2) What's the difference between SpeedNet and BytesBandwith unit options?
3) What is best used to keep track of up- and downloadspeeds of a connection?

Thanks a lot for your input.

bandwidth-speed custom-sensor python

Created on Apr 19, 2021 7:22:34 PM by  Mickeybyte (0) 1

Last change on Apr 20, 2021 7:58:01 AM by  Felix Wiesneth [Paessler Support]



15 Replies

Votes:

0

Your Vote:

Up

Down

What's the actual output of your script when run manually? SpeedNet and BytesBandwidth are measuring speed and throughput. The latter also allows for reporting on throughput over a certain timespan. The first one is best for what you're intending to do. iirc, the right value to use would be bytes for this in order for PRTG to calculate correctly :)

Created on Apr 27, 2021 11:38:23 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Stephan,

When I use SpeedNet as ValueUnit, it always shows up in bytes and I can't use the ValueSize option (actually I can but it doesn't change anything). I can also not change it using the PRTG channel settings When I use BytesBandwidth as ValueUnit, I can also set the ValueSize option and the values show as MBit/s in PRTG in stead of in bytes/s.

I'm actually running the speedtest.net cli program and parse the output in the python script to get an (hourly) update of my internet connection speed. That's why I also thought SpeedNet was the one to use, but then I only get values in bytes/s and I actually wont the see it in a more human-readable format (the times of 56k modem connections are long behind us already, we're measuring in Mbps now :-))

Created on Apr 27, 2021 12:00:13 PM by  Mickeybyte (0) 1



Votes:

0

Your Vote:

Up

Down

Well speednet would work for that, you can configure the channel unit configuration in the device settings, have you tried that one? :)

Created on May 3, 2021 7:52:09 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

On the device settings, it says: No configurable channels...

Created on May 3, 2021 8:05:45 AM by  Mickeybyte (0) 1



Votes:

0

Your Vote:

Up

Down

But your sensor clearly has channels, right? Could you post a screenshot of the device settings, at the very bottom where it states that? I have yet to see this message :)

Created on May 3, 2021 8:08:32 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

See screenshot. Sensor is currently paused, so no live data visible. Channels Download en Upload are setup with SpeedNet unit.

Created on May 3, 2021 8:15:39 AM by  Mickeybyte (0) 1



Votes:

0

Your Vote:

Up

Down

Still the same when resuming it?

Created on May 3, 2021 12:14:07 PM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Yes. Just started the sensor again, values are updated correctly, but only showing in bits /s and no way to change it to Mbps.

Created on May 3, 2021 12:29:54 PM by  Mickeybyte (0) 1



Votes:

0

Your Vote:

Up

Down

When you're in the Sensor, open up its settings tab. At the bottom, there should be a section "Channel Unit Configuration" where you can set this - is that not the case here?

Created on May 3, 2021 1:00:14 PM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

No. It says: no configurable channels. On the other senor, using the BytesBandwidth as Unit, I do have an option to change it to Kbps/Mbps/...

Created on May 3, 2021 1:03:10 PM by  Mickeybyte (0) 1



Votes:

0

Your Vote:

Up

Down

What happens if you click in the gear icon of the Channels? Can you send me a screenshot of that?

Created on May 7, 2021 2:02:23 PM by  Miguel Aikens [Paessler Technical Support]



Votes:

0

Your Vote:

Up

Down

Created on May 7, 2021 3:38:59 PM by  Mickeybyte (0) 1



Votes:

0

Your Vote:

Up

Down

Hi,

Have you tried changing the Channel Unit directly from the device? Please review the following document: https://www.paessler.com/manuals/prtg/device_settings#channel

Another option is to change the script so that it reports BytesBandwidth (unit) without a customunit, SpeedSize or VolumeSize.

Hope this helps.

Created on May 11, 2021 8:54:44 PM by  Miguel Aikens [Paessler Technical Support]



Votes:

0

Your Vote:

Up

Down

Hi,

When using the BytesBandwidth type I can change it to KB/MB/GB without any problem. It's when using SpeedNet as unit that I always get it in bytes/s and there's no way to change it to mega- or gigabytes/s. I just created a new sensor with the script only specifying SPEEDNET as Unit and no other options, but in PRTG I have no way to change it to MB/GB/... Not in the settings, nor in the channel configuration.

Created on May 12, 2021 12:05:51 PM by  Mickeybyte (0) 1



Votes:

0

Your Vote:

Up

Down

Hi,

I believe the best option is to open up a ticket with us and if needed gather logs for analysis. To open up a ticket you can do it directly from the Contact Support option in the Core Server web interface.

Created on May 17, 2021 6:01:42 PM by  Miguel Aikens [Paessler Technical Support]



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.