Thold and bandwidthgraphs?

[kyosanim]

Hello guys,
i'am using cacti for about 6 month with serveral plugins. most times i can solve my cacti-problems with help of the forum or docu-page. but this time i couldn'd find a post that match with my problem.

I want to monitor the internetconnection to our ISP. i have a cisco router with an 155mbit connection. and i want to get an alert if the usage of the bandwidth went above 130mbit.
I am using the cacti template/data query 'SNMP - Interface Statistics' to gather the data from the router.
Gathering data an graphing works fine (i am using a cdef-function to convert from bytes into bits).
now my problem. the 'current' value in thold is completly different to the value in the graph. and it's is not just a wrong convertion of bytes into bits. i tried serveral cdef-functions without success.
anybody an idea?
is thold able to handle 'counters' or just 'gauge' values?

Using - Cacti 0.8.6j on SLES 10
- cactid
- PluginArch 1.1
- 1Minute Polling
- Thold 3.4
- Syslog-Plugin

[Howie]

Hello guys,
i'am using cacti for about 6 month with serveral plugins. most times i can solve my cacti-problems with help of the forum or docu-page. but this time i couldn'd find a post that match with my problem.

I want to monitor the internetconnection to our ISP. i have a cisco router with an 155mbit connection. and i want to get an alert if the usage of the bandwidth went above 130mbit.
I am using the cacti template/data query 'SNMP - Interface Statistics' to gather the data from the router.
Gathering data an graphing works fine (i am using a cdef-function to convert from bytes into bits).
now my problem. the 'current' value in thold is completly different to the value in the graph. and it's is not just a wrong convertion of bytes into bits. i tried serveral cdef-functions without success.
anybody an idea?
is thold able to handle 'counters' or just 'gauge' values?

Using - Cacti 0.8.6j on SLES 10
- cactid
- PluginArch 1.1
- 1Minute Polling
- Thold 3.4
- Syslog-Plugin

Last time I looked, Thold assumes you have a 5 minute polling cycle. It doesn't use the data from the RRD files but directly from the poller, so it's certainly possible for there to be differences (it effectively does the same calculations internally that rrdtool would have done to figure out the rate).

[yep - in 0.3.4's setup.php, there are several hard-coded '/300' references. Possibly changing those to /60 would resolve it? Are the values out by a factor of 5-ish? ]

Howie
(not actually a thold expert)

[kyosanim]

that's it.
now it's working!
i created a cdef-function that make '$wrong-value * 5'...
thanks a lot!

@feature request: make thold working with 1MinutePolling Patch

[elpiako]

Hi, i currently have the same problem.
But i have some questions : even if I multiply the "wrong" value by 5, it's still wrong :/

Can someone help me ?

edit : after studying the current value of my traffic_in thrshold, it corresponds to nothing !!! What's the hell is this value ?

I actually have 12944042.0933 for traffic_out instead of 104,14 Mbits/second (on the graph)
and 19702522.06 for traffic_in instead of 158,36 Mbits/second (on the graph)

[elpiako]

I've found my response

http://forums.cacti.net/viewtopic.php?t=20155