Hello,
On Apr 29, 2013, at 7:35 AM, vivek nalla <nalla.g...@gmail.com> wrote:
> In the class Mib2Events.java of opennms-tools. reduction key is set like
> this. Is there any wrong with this?
Yes, there is. I didn't wrote mib2events but I wrote the new Vaadin app for the
MIB Compiler and Event/DataCollection editor on 1.12. The problem with the
reduction key is that there is no way to set that variable automatically
because that is a human decision, not a decision based on what we read from the
trap.
The reduction key you're suggesting is so generic, that basically all traps
with the same UEI, the same node and the same interface are going to be reduced
to one, no matter if all the event parameters are different. That's why
handling AlarmData is something that the user itself must configure manually in
my opinion. That's why I'm not setting this on my Vaadin app, and I believe
that's why getTrapEventAlarmData() is not used on mib2events.
http://www.opennms.org/wiki/Configuring_alarms#Reduction_Keys
Alejandro.
------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ
opennms-devel mailing list
To *unsubscribe* or change your subscription options, see the bottom of this
page:
https://lists.sourceforge.net/lists/listinfo/opennms-devel
