|
From: <bla...@pa...> - 2004-07-30 20:53:51
|
Ok sorry i think i need to clarify this.. if i have and oid that i want to monitor for changes how do i go about implementing this within the xml files.. I'm not familiar with how opennms sets this up and which xml files to modify. so if i want to monitor OID .1.3.6.1.4.1.9.9.132.1.1.1.1.7 (cds3TraceAlarm) for changes and set thresholds on it so if it changes from say 5 to 6 i want an event then when it changes back to 5 i want a clear event. how would i accomplish this? At 03:50 PM 7/30/2004, you wrote: >On Fri, 2004-07-30 at 18:47, bla...@pa... wrote: > > Ok so where is cpu_Utilization_OID_Alias defined? > >look in /etc/opennms/eventconf.xml, there are the variables defined >OpenNMS can collect per default > > > > > and is there a way to tell opennms not to generate an alarm/event unless > > the threshold has been violated 4 times in the last 15 mins. > >no idea > > > > > > > At 12:12 PM 7/30/2004, you wrote: > > >open /etc/opennms/thresholds.xml > > > > > >insert the following line: > > > > > ><threshold type="high" ds-name="cpu_Utilization_OID_Alias" > > >ds-type="node" value="80" rearm="70" trigger="3"/> > > > > > >which will trigger the specified event three times > > > > > > > > >plounty > > > > > > > > >On Fri, 2004-07-30 at 17:37, bla...@pa... wrote: > > > > How does one go about setting up a threshold on specific oid variables? > > > > > > > > for instance if i wanted to (threshold cpu utilization) to say > generate an > > > > alarm at 80% and clear it at 70%. > > > > > > > > how would i do that? > > > > > > > > what xml files do i need to change? > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > This SF.Net email is sponsored by OSTG. Have you noticed the changes on > > > > Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, > > > > one more big change to announce. We are now OSTG- Open Source > Technology > > > > Group. Come see the changes on the new OSTG site. www.ostg.com > > > > _______________________________________________ > > > > opennms-discuss mailing list > > > > ope...@li... > > > > https://lists.sourceforge.net/lists/listinfo/opennms-discuss > > > > > > > > > > > > > > > >------------------------------------------------------- > > >This SF.Net email is sponsored by OSTG. Have you noticed the changes on > > >Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, > > >one more big change to announce. We are now OSTG- Open Source Technology > > >Group. Come see the changes on the new OSTG site. www.ostg.com > > >_______________________________________________ > > >opennms-discuss mailing list > > >ope...@li... > > >https://lists.sourceforge.net/lists/listinfo/opennms-discuss > > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by OSTG. Have you noticed the changes on > > Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, > > one more big change to announce. We are now OSTG- Open Source Technology > > Group. Come see the changes on the new OSTG site. www.ostg.com > > _______________________________________________ > > opennms-discuss mailing list > > ope...@li... > > https://lists.sourceforge.net/lists/listinfo/opennms-discuss > > > > > >------------------------------------------------------- >This SF.Net email is sponsored by OSTG. Have you noticed the changes on >Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, >one more big change to announce. We are now OSTG- Open Source Technology >Group. Come see the changes on the new OSTG site. www.ostg.com >_______________________________________________ >opennms-discuss mailing list >ope...@li... >https://lists.sourceforge.net/lists/listinfo/opennms-discuss |