There are two ways the alert thresholds will be set :
a) From a manufacturer-supplied value, as with Cisco
b) Based on the first measurement +/- a %age which varies based on unit (we allow temperature to vary more than voltage, for example)
The only way you'd have a sensor with a range of 2.0 - 2.5 when the measured value is ~23 is if :
a) The manufacturer supplied this range in the MIB
b) The value at initial poll was ~2.3
c) The value passed at initial poll was an order of magnitude wrong, possible due to a bug in our code
There's no way for something to get a threshold an entire order of magnitude wrong without someone having broken something somewhere, either us or the manufacturer. If it's on our side, it's a bug that needs fixed, rather than something which needs worked around via more features.
adam.
On 2014-01-27 17:36, Robbie Wright wrote:
Cisco may have been a poor example. The problematic ones (withSiuslaw Broadband [3]
unsupported mibs) have been Mikrotik and the Ubiquiti wireless stuff.
Ubiquiti's EdgeMax router is basically Vyatta so it picked up most
things on its own, but not all.
Robbie Wright541-902-5101 [1]
541-902-5101
**For support issues, please email support@siuslawbroadband.com.**
On Mon, Jan 27, 2014 at 3:25 PM, Adam Armstrong <adama@memetic.org> wrote:
On Cisco kit, the limits are provided by IOS as part of CISCO-ENTITY-SENSOR-MIB. If they're wrong, you should open a bug with Cisco.
As a workaround, we allow you to manually set the limits when Cisco fail.
adam.
On 2014-01-27 17:08, Robbie Wright wrote:
Agreed as well, I can see the complexity around templates as well. The
only real complication was just bogus alerts and as Tom just
mentioned, smarter auto-limits could be an easy way to fix that. They
end user could then customize them individually if they needed
something more, ie a switch in a non climate controlled cabinent on a
telephone pole that ran hot.
Robbie Wright
Siuslaw Broadband [1]
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [2] [2]
**For support issues, please email support@siuslawbroadband.com.**
On Mon, Jan 27, 2014 at 2:57 PM, Tom Laermans
<tom.laermans@powersource.cx> wrote:
On 27/01/2014 22:51, Adam Armstrong wrote:
On 2014-01-27 15:08, Tom Laermans wrote:
Sure, but those are changed one on one, not with a template for all
devices of a certain type as asked ;-)
I'm not even sure how you'd template these things, probably something like the alerting matching code, but i suspect it'd be little used, as it'd be really complex.
Agreed.
I would prefer smarter auto-limits. Like, for values surrounding 3.3v,
use a static set of 3.0-3.5 or whatever, etc.
Tom
_______________________________________________
observium mailing list
observium@observium.org
Links:
------
[1] http://siuslawbroadband.com [3]
[2] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [2][1] tel:541-902-5101
_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [2]
_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [2]
Links:
------
[2] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
[3] http://siuslawbroadband.com
_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium