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] 541-902-5101
**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 http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [2]
Links:
[1] http://siuslawbroadband.com [2] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium