Can someone please give me an hand with this? I have spent a few days trying to get this to work with no luck.
Any assistance is great appreciated. Alhagie Puye - Network Engineer Datawave Group of Companies (604)295-1817 > >-----Original Message----- > >From: [EMAIL PROTECTED] > >[mailto:[EMAIL PROTECTED] On Behalf > >Of Alhagie Puye > >Sent: December 12, 2005 12:40 PM > >To: jffnms-users@lists.sourceforge.net > >Subject: RE: [jffnms-users] Event or Alarm when setting up SLA's > > > >OK, I have read the consolidation process and gained some > >insight into how this works. > > > >I have found the sla-creation-example.txt that Christian > >Zimmerman has written. I think it is a little old for 0.8.2 > >though since some of the menu items have changed. I > >processed in modifying it for what I need. > > > >I am not getting any emails though. > > > >Could someone take a look and let me know if I'm missing something? > > > >Greatly appreciated. > > > >Alhagie Puye - Network Engineer > >Datawave Group of Companies > >(604)295-1817 > > > >> >-----Original Message----- > >> >From: [EMAIL PROTECTED] > >> >[mailto:[EMAIL PROTECTED] On > >Behalf Of Javier > >> >Szyszlican > >> >Sent: December 11, 2005 9:30 AM > >> >Cc: jffnms-users@lists.sourceforge.net > >> >Subject: Re: [jffnms-users] Event or Alarm when setting up SLA's > >> > > >> >Its easy, Match events matches events, and match alarms matches > >> >alarms. > >> > > >> >An Event is something that happened once. > >> > > >> >And alarm is an outage with 1 start event and 1 stop > >event (like a > >> >protocol down event, and then a protocol up event for the same > >> >interface). > >> > > >> >The manual describes the Consolidation process better. > >> > > >> >Javier > >> > > >> >Alhagie Puye wrote: > >> >> Hello all, > >> >> > >> >> I'm having an issue in getting SLA triggers sending emails. > >> >> > >> >> First question is am I supposed to use "Match Events" or > >> >"Match Alarms"? > >> >> Can some explain the difference between the two to me. I > >> >couldn't find > >> >> the difference reading through the documentation. > >> >> > >> >> > >> >> > >> >> Alhagie Puye - Network Engineer > >> >> Datawave Group of Companies > >> >> (604)295-1817 > >> >> > >> >> > >> >> This message (including any attachments) is confidential, > >> >may be privileged and is only intended for the person to > >whom it is > >> >addressed. If you have received it by mistake please notify the > >> >sender by return e-mail and delete this message from your > >system. > >> >Any unauthorized use or dissemination of this message in > >whole or in > >> >part is strictly prohibited. E-mail communications are > >inherently > >> >vulnerable to interception by unauthorized parties and are > >> >susceptible to change. We will use alternate communication means > >> >upon request. > >> >> > >> >> > >> >> ------------------------------------------------------- > >> >> This SF.net email is sponsored by: Splunk Inc. Do you grep > >> >through log > >> >> files for problems? Stop! Download the new AJAX search > >> >engine that > >> >> makes searching your log files as easy as surfing the > >> >web. DOWNLOAD SPLUNK! > >> >> http://ads.osdn.com/?ad_idv37&alloc_id865&op=click > >> >> _______________________________________________ > >> >> jffnms-users mailing list > >> >> jffnms-users@lists.sourceforge.net > >> >> https://lists.sourceforge.net/lists/listinfo/jffnms-users > >> > > >> >-- > >> >=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > >> >Javier Szyszlican, Project Leader, JFFNMS [EMAIL PROTECTED] > >> > > >> >I hope JFFNMS or I were helpful to you, if you can, > >please donate at > >> >http://jffnms.org/donate > >> > > >> > > >> > > >> >------------------------------------------------------- > >> >This SF.net email is sponsored by: Splunk Inc. Do you > >grep through > >> >log files for problems? Stop! Download the new AJAX > >search engine > >> >that makes searching your log files as easy as surfing the web. > >> >DOWNLOAD SPLUNK! > >> >http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > >> >_______________________________________________ > >> >jffnms-users mailing list > >> >jffnms-users@lists.sourceforge.net > >> >https://lists.sourceforge.net/lists/listinfo/jffnms-users > >> > > > > > > >This message (including any attachments) is confidential, > >may be privileged and is only intended for the person to > >whom it is addressed. If you have received it by mistake > >please notify the sender by return e-mail and delete this > >message from your system. Any unauthorized use or > >dissemination of this message in whole or in part is > >strictly prohibited. E-mail communications are inherently > >vulnerable to interception by unauthorized parties and are > >susceptible to change. We will use alternate communication > >means upon request. > > This message (including any attachments) is confidential, may be privileged and is only intended for the person to whom it is addressed. If you have received it by mistake please notify the sender by return e-mail and delete this message from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited. E-mail communications are inherently vulnerable to interception by unauthorized parties and are susceptible to change. We will use alternate communication means upon request.
We want to monitor disk space on the server and be notified when : disk space used is > 30% of the total disk space. Things we need to do: 1. Create a new Event Type 2. Create a new SLA Conditions Individual Definition 3. Create a new SLA group 4. Associate the newly created condition with the new SLA Group 5. Create a new Trigger (allows for notification if needed) 6. Add a rule for the trigger Step One: ========= Goto Administration > Internal Configuration > Event Analyzer > Event Types You should see a list of all event types. Click the ADD link to create a new Event. Now we need to input a description, severity, and event text. Enter the following: Description -> Disk Full-SLA Severity -> select Critical Event Text -> Disk <interface>: <info> Next put a check in the next two boxes: Show in Event Viewer? and Event Generates an Alarm? Once this is completed click the submit button and now you should see this new event in the list with all the other events. Step Two: ========= Goto Administration > Internal Configuration > SLA definitions > SLA Conditions Individual Definition Again we will need to add the condition that we will want to test for so lets create a new condition. Click the ADD link to begin creating a new condition. You will need to fill in the following fields Description, Show Info, Condition, Show Expression, and Show Unit. Here are the values: Description -> Used Storage > 30% Show Info -> Used > 30% Condition -> ( <storage_used_blocks> > ((<storage_block_count>*30)/100)) Show Expression -> ((<storage_used_blocks> * 100)/<storage_block_count>) Show Unit -> % Once you've entered the information in, click submit and your new condition is created. Steps Three and Four: ===================== Goto Administration > Internal Configuration > SLA definitions > Conditions Groups Here we will need to create a new SLA group. Click the ADD button and lets create a new group. Here is a list of fields that we need to fill in: Description, Interface Type, Event Type, Alarm State, Event Text, Threshold % (for Reports). Here's the values: Description -> Storage Full Interface Type -> Storage Event Type -> Disk Full-SLA Alarm State -> Alert Event Text -> Storage Threshold % -> 100 Notice the value for the Event type is the one we created. This is where we link the Event Type to the SLA. When the SLA is met or not met depending on how you setup the triggers, an event will be generated. Click Save and your new SLA group is created. You should see your new event group now with a view link right next to it. This view link is where we associate the condition to check for, if the condition is met an event is generated. So click the view button and a second frame opens up right below the SLA groups. Click the ADD link and a new box appears. Under the "Condition" option select -> Used Storage > 30% and then click the SHOW option. Click Save. We have now created a new SLA option on which will test whether or not our Server disk space usage is above 30% ( meaning its full or almost full). If the SLA is met then an event type will be generated. Step Five: ========== Goto Administration > Internal Configuration >Triggers & Filters > Triggers Configuration Now that our SLA is setup we need to setup a trigger for notification. (Note: You don't have to setup a trigger, but you might as well as you can turn them off later if needed without any hassle.) Click the ADD link and fill in the Description and Type fields: Description -> Disk over 30% Full Type -> Match Events Click Save and your done. Step Six: ========= The trigger has been created, but we haven't told the trigger what action to perform to lets do this now. Click on View Rules for the Trigger "Disk Full". A Triggers Rules Administration window shows below the Triggers. Click the ADD link. We need to edit these options: Field, Operator, Value, Action, Action Parameters. Set them to this: Field -> Type Operator-> IN Value -> Disk Full-SLA Action -> Send Mail Action Parameters subject -> Disk <interface-interface> comment -> <alarm-type_description> <interface-description> Click Save and your done. This trigger will now send an email to the email configured in your profile when the SLA has been met. You should also see an event as well. Step Seven: =========== Go to Triggers Users and click on Add. Under Username, select "Alhagie Puye" and under Trigger, select "Disk over 30% Full" Click on Save.
