New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

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

Free PRTG
Download >>

 

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

 

Top Tags


View all Tags


Factory Sensor results incorrect when adding two SNMP traffic sensors

Votes:

0

Your Vote:

Up

Down

I'm trying to create a single graph that shows the aggregate of all of our internet feeds on one chart. I've set up a standard sensor factory sensor with the following definition:

#1:Traffic in [mb]
((Channel(2693,0) +  Channel(2799,1)))

#2:Traffic Out [mb]
((Channel(2693,1) + Channel(2799,1)))

However, the numbers produced by the summs do not match the numbers I get when I manually add the individual channels. The problem seems to be that the standard sensor works both in bytes (total traffic) and bits (traffic per second) but only reports bytes total to the factory sensor. This means that no matter what kind of arithmetic gymnastics I perform, on of the summed numbers (either total or bps) will be incorrect by a factor of 8.

Is there a way to add traffic sensors properly so both numbers are accurate?

sensor-factory snmp sum

Created on Jun 7, 2010 2:09:11 PM by  Jim Kirby (181) 2 1



Best Answer

Accepted Answer

Votes:

1

Your Vote:

Up

Down

Remove the [mb] from your definition then the settings from the source sensors will be used with Byte for volume and bits for speed.

Created on Jul 12, 2010 10:46:16 AM by  Jens Rupp [Paessler Support]

Last change on Nov 4, 2010 11:51:24 AM by  Daniel Zobel [Paessler Support]



4 Replies

Votes:

0

Your Vote:

Up

Down

Sorry, there was a typo in my definition above but not in my actual configs. For each sensor I'm trying to add, there are indeed two channels: channel 0 for in and channel 1 for out. In my factory sensor, channel 1 is in and channel 2 is out.

The problem arises on the bottom of the overview page (as well as a few other places). There, each channel reports a "Last Value (volume)" and a "Last Value (speed)". The volume is in bytes while the speed is in bits. However, I cannot manipulate each value individually so one of them will always be off by a factor of 8. For instance, if I apply no divisor or multiplier to my formula (as above) then my Volume count is correct but my bps count is 8 times too small. If I multiply the formula by 8 to get the bps correct, the volume is 8 times too great. This is true even if I only put one source channel in the factory channel definition (ie, no math). Ostensibly if I only have on channel as part of a factory channel definition then both sensors (the original and the factory on) should report nearly identical #'s for both values. Unfortunately the factory channel does not match the source channel and one of the two values is always off by */ 8.

Is there a way to make it so that both the volume and speed values are correct?

Created on Jun 8, 2010 5:41:31 PM by  Jim Kirby (181) 2 1



Votes:

0

Your Vote:

Up

Down

Could you provide us with a screenshot, please?

Created on Jun 21, 2010 12:49:06 PM by  Patrick Hutter [Paessler Support] (7,164) 3 3



Accepted Answer

Votes:

1

Your Vote:

Up

Down

Remove the [mb] from your definition then the settings from the source sensors will be used with Byte for volume and bits for speed.

Created on Jul 12, 2010 10:46:16 AM by  Jens Rupp [Paessler Support]

Last change on Nov 4, 2010 11:51:24 AM by  Daniel Zobel [Paessler Support]



Votes:

0

Your Vote:

Up

Down

That works, thanks. I think the documentation should highlight the differences in placing a unit in the channel definition versus not using one. The docs make it seem like the units are mandatory whereas the difference is having or not having it is quite significant.

Created on Jul 13, 2010 7:59:27 PM by  Jim Kirby (181) 2 1



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.