[prev in list] [next in list] [prev in thread] [next in thread] 

List:       opennms-discuss
Subject:    Re: [opennms-discuss] OpenNMS Auto acknowledge of Thresholds
From:       Are_Øhrn <are () fasthost ! no>
Date:       2009-01-27 23:23:37
Message-ID: 497F9779.8010305 () fasthost ! no
[Download RAW message or body]

Wiktor Wodecki wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi,
> 
> Are Øhrn wrote:
> > Hi,
> > I'm trying to configure auto acknowledgment of thresholds, but I seem to 
> > have some problems matching the threshold in notifd-configuration.xml
> > The threshold notifications does add up to a lot when not auto acknowledged.
> > 
> > The default node lost service in the notifd.configuration.xml seems 
> > straightforward:
> > 
> > <auto-acknowledge resolution-prefix="RESOLVED: "
> > uei="uei.opennms.org/nodes/nodeRegainedService" 
> > acknowledge="uei.opennms.org/nodes/nodeLostService">
> > <match xmlns="">nodeid</match>
> > <match xmlns="">interfaceid</match>
> > <match xmlns="">serviceid</match>
> > </auto-acknowledge>
> > 
> > But I see no way of matching the thresholds, as the reduction key is 
> > using some variable parameters: (from eventconf.xml)
> > 
> > clear-key="uei.opennms.org/threshold/highThresholdExceeded:%dpname%:%nodeid%:%interface%:%parm[ds]%:%parm[threshold]%:%parm[trigger]%:%parm[rearm]%:%parm[label]%" \
> >  auto-clean="false"/>
> > 
> > Have anyone configured auto acknowledge of thresholds? Or does anyone 
> > have any suggestions on workarounds.
> 
> I think you're mixing up two things here. The part from the
> notifd-configuration.xml is the place where you configure
> auto-acknowledgement of notifications. You can match notifications by
> either nodeid, interfaceid, serviceid or any combination of these.
> Eventparameters like the datasource (parm[ds]) cannot be accessed from
> within here.
> 
> The clear-key you found in the event definition relates to alarms, which
> are kind of aggregates of events. They are indeed used for
> auto-acknowledgement of those.
> 
> AFAIK the vacuumd is currently the only viable way to auto-acknowledge
> notifications based on the eventparameters since you're free to do your
> SQL there.
> I think I've read about some plans to create notification out of alarms
> in 1.7, but I'm not sure about this.
> 
> - --
> Regards,
> 
> Wiktor Wodecki
> 
> net mobile AG, Zollhof 17, 40221 Duesseldorf, Germany
> 923B DCF8 070C 9FDD 5E05  9AE3 E923 5A35 182C 9783
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> 
> iEYEARECAAYFAkl/T1oACgkQ6SNaNRgsl4NZIgCffIFXJTe8ZNyosR2RFSjDmowc
> NIMAoJQcXXnFQ32LUHm3Vg0VYVPAtgvW
> =Kovc
> -----END PGP SIGNATURE-----
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> Please read the OpenNMS Mailing List FAQ:
> http://www.opennms.org/index.php/Mailing_List_FAQ
> 
> opennms-discuss mailing list
> 
> To *unsubscribe* or change your subscription options, see the bottom of this page:
> https://lists.sourceforge.net/lists/listinfo/opennms-discuss

Hi,
I did mix things up, and got the auto acknowledgment working after 
reading it trough a few more times.
Thanks for the help.

-- 
Regards,
Are Øhrn


------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss


[prev in list] [next in list] [prev in thread] [next in thread]