[CLOSED] Problem: restoral mail & Time Based Treshld

Support questions about the Threshold plugin

Moderators: Developers, Moderators

User avatar
TheWitness
Developer
Posts: 17047
Joined: Tue May 14, 2002 5:08 pm
Location: MI, USA
Contact:

Re: Problem: restoral mail & Time Based Treshld

Post by TheWitness »

If you only have two values, don't set a WARNING. You can leave it blank. Also, if you are using time based at a 1 minute poller interval and require 10 intervals to generate an alert over 10 minutes, why just not use Hi/Low?

Both the time interval/trigger count issue and the same level for Warning and Alarm are what are referred to as negative tests. The User Interface should block both from happening. This is why I asked you if you knew what 'Reductio ad Absurdum' meant. Cause you are 'reducing to the absurb'. Although, the dev's should take part of the blame as they allowed it to happen.

TheWitness
True understanding begins only when we realize how little we truly understand...

Life is an adventure, let yours begin with Cacti!

Author of dozens of Cacti plugins and customization's. Advocate of LAMP, MariaDB, IBM Spectrum LSF and the world of batch. Creator of IBM Spectrum RTM, author of quite a bit of unpublished work and most of Cacti's bugs.
_________________
Official Cacti Documentation
GitHub Repository with Supported Plugins
Percona Device Packages (no support)
Interesting Device Packages


For those wondering, I'm still here, but lost in the shadows. Yearning for less bugs. Who want's a Cacti 1.3/2.0? Streams anyone?
uhtred
Cacti User
Posts: 121
Joined: Fri Oct 09, 2009 8:59 am
Location: Germany

Re: Problem: restoral mail & Time Based Treshld

Post by uhtred »

TheWitness wrote:If you only have two values, don't set a WARNING. You can leave it blank.
if i do this, i get restored messages "restored to warning threshold with value 1" :o
Also, if you are using time based at a 1 minute poller interval and require 10 intervals to generate an alert over 10 minutes, why just not use Hi/Low?
i had have problems with Hi/Lo threshold in older versions of thold. I don't clearly remember...in the forum someone recommended the time based threshold.
Both the time interval/trigger count issue and the same level for Warning and Alarm are what are referred to as negative tests. The User Interface should block both from happening. This is why I asked you if you knew what 'Reductio ad Absurdum' meant. Cause you are 'reducing to the absurb'. Although, the dev's should take part of the blame as they allowed it to happen.
now, i understand :D

with Hi/Lo it looks good, now
System: Ubuntu 10.04lts@64bit, 2*X5650, 12GB, Cacti 0.8.7g, Spine 0.8.7g, PA2.9, Weathermap 0.97a, CAMM 1.6.75, monitor 1.3.1, realtime 0.43, thold 0.4.9.3, manage 0.6.2, mactrack 2.9(.1) ---- 508 devices, 6741 items, 4263 ds, time 7.01s, intervall 60, proc. 12, threads 14, php server 8
Post Reply

Who is online

Users browsing this forum: No registered users and 5 guests