Hi Gabriel,  in short : - you mention that you have eventCode uniquely identifying the event, so, if you have a translation table in your ASL code, you will have for ex: eventCode => eventName eventCode1 => "Name of Event #1" eventCode2 => "Name of Event #2" so using this translationTable you now have a unique eventName which has a meaning for the end user, not just a code. (EventName should be "CPU load", not "CPU load x%" BTW)  - now, for the eventDisplayName, you don't really have the choice : by default, this is not a supported feature in the trap receiver, so you can hack the trap receiver ASL script to add this feature (not that difficult, clean, but not supported) or use a DXA to add this information. This is just cosmetic information (not use as a key) so you can add the eventDisplayName in SAM, not in OI. To do this, with a DXA, you have to test for your notification "source" (to apply this feature only to the right notifications), and then set the eventDisplayName (in SAM) with a value that the script will take from any attribute coming from OI.  --Fred
I need help.  My INCHARGE-OI repository is growing too fast and crashes after 2 days.  This happens because INCHARGE-OI receives lots of traps from several different managers and when the number of ICS_Notifications is bigger than 750.000,00 it goes down.  Some of you may ask about this number of events. Unfortunately, some intermitent traps have different values at its varbinds and Smarts creates a diferent object for the same event in OI repo. (Blame the other NMS)  But the real number of valid ICS_Notifications is only 5.000,00 ( Active and Inactive). The another ICS_Notifications (700.000,00) are with Unitialized Status.  My workaround solution is an ASL/SH scripts to archive this type of Notification, but I'm not happy with it. 1. What is the "unitialized" state?  2. Why Smarts isn't clearing those Notifications?  3. What can I do?  Tks  Gabriel
ICS_Notification Status: Unitialized