[Orca-users] Orca graph's y-axis for counter values

[Guilherme Chehab]

Joshua,

Complementing Blair's response, the rate function in procallator code calculates 
the difference between two values and divides the result by the time interval. 
That way the counter approximates the measurements to the rate in seconds.

The default interval is, indeed, 5 minutes, but the logged rate counters already 
takes that in consideration. 


If you sense that this behavior, for some reason, it is not working as 
described, send some more information so we can check it out.

It is possible to change this interval, but to graph it in Orca should require 
some tweaking in the Orca's perl modules. I think I have tried it once when I 
needed to do some troubleshooting data to be logged and graphed. 


regards,
Guilherme





________________________________
From: Blair Zajac <blair at orcaware.com>
To: Joshua Miller <joshuamiller01 at gmail.com>
Cc: orca-users at orcaware.com
Sent: Tue, April 19, 2011 7:49:49 PM
Subject: Re: [Orca-users] Orca graph's y-axis for counter values


On Apr 19, 2011, at 1:29 PM, Joshua Miller wrote:

> I use procallator to gather network interface statistics.  The 'Interface Input 
>Packets Per Second' graph (among others) shows packets per second, but 
>procallator seems to collect the packet counters once every five minutes and 
>report the difference (a counter).  If I understand this correctly the data 
>that's being collected is along the lines of "Packets per five minutes", rather 
>than per second.
> 
> The data I see on the orca graphs seems to fit with what I'm observing.  Am I 
>missing something?  And if not, is there a reason for having the graph y axis 
>report Packets/s rather than Packets/5min?

It looks correct to me, as packets/s.  It's recording a count every 5 minutes 
and then dividing the difference by 300.

I have a system with 101.287 Mbit/sec and 16,088 packets/sec, if you assume 
roughly 1000 bytes per packet, then

16088*1000*8/1024/1024 = 122.7 Mbit/sec, which is in the right ballpark.

Finally, if you look at the procalltor implements:

            put_output(
                "if_in_b_$if_name[$i][$r]",
                rate( $if_in_b[$i][$r], $if_in_b[$i][ 1 - $r ] ),
                "if_in_p_$if_name[$i][$r]",
                rate( $if_in_p[$i][$r], $if_in_p[$i][ 1 - $r ] ),

then the bits/sec and the packets/sec are using the same algorithm.

Why do you think it's packets/5 min?

Blair

_______________________________________________
Orca-users mailing list
Orca-users at orcaware.com
http://www.orcaware.com/mailman/listinfo/orca-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/orca-users/attachments/20110420/510e08fc/attachment.html>