Understanding Current Value vs Last Value

Support questions about the Threshold plugin

Moderators: Developers, Moderators

Post Reply
jko5
Posts: 10
Joined: Fri Oct 11, 2013 9:35 am

Understanding Current Value vs Last Value

Post by jko5 »

I am in Infrustrcture. This makes me very slow at certain things. :) I am sure I have read this answer or some variation of this answer on the forums but need more explaination.

What I am doing: I have a 10Mb pipe and want to receive a warning message at 8.55Mb and an alert message at 9.50. I figured out that the current value is equal to bytes. When I look at the current value, I also look at the Last value which is what I must enter to trigger a message.

8.55Mb = 1067331.0228 (current value) = 28912.44 (last value)
9.50Mb = 1187466.9487 (current value) = 32102.73 (last value)

So when I hit 8.55Mb I receive a warning message. When I hit 9.5Mb I receive an alert message. This is great and its working. For my own information what is the corraltion between current value and last value? And why not alert based on current value?

Please see example below.
cacti_current_to_last_value.PNG
cacti_current_to_last_value.PNG (78.63 KiB) Viewed 1432 times
Thank you for your time!
liet
Posts: 1
Joined: Wed Jul 31, 2013 7:11 am

Re: Understanding Current Value vs Last Value

Post by liet »

Hi jko5.

IMHO, current value is the bytes counters... transferred in your last poller check. If your poller frecuency is 5 minutes: your bytes*8/300 sec is the transfer average in bits/sec, quite similar to the last value.

Cheers
Liet
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest