On Dec 24, 2008, at 3:15 AM, nixinfo wrote: > Thanks for your response cluther. I could not comprehend what you > meant in your response. Could you please expand on it? > > Just to narrow down the problem a little more, the scenario is as > follows: > > Application: foo > Event ID: 25 > Message: The application has some erratic behaviour > > The script detects the message on event log and sends as a trap to > Zenoss server. Now if the application foo writes to event log again > as follows > > Event ID: 50 > Message: The application has crashed > > Another trap will be sent but instead of displaying it as a separate > new message in event console Zenoss will increase the count of > previous message. Regardless of different Event ID/Messages Zenoss > just increases the count if the event has been generated by same > application. > > I hope this has made the picture more clear. > > I forgot to mention the Zenoss version we are using is 2.1.3 and > upgrade is not an option just in case.
I was just trying to explain how the deduplication mechanism works so that you can make it work the way you want it to. The most important thing to understand is that if the following fields match between two events, the existing event's count will just be increased instead of creating a new event. device component (can be blank) eventClass severity eventKey (summary is used if eventKey is blank) So in the case of the SNMP traps that your script is sending, all of these fields are matching. This leads to the deduplication you're experiencing. The high-level answer to any question like this is that you need to make sure that at least one of these fields is different between your events if you want them to remain distinct events. The most common ones to alter are the eventKey or summary. My previous example suggested altering the summary because I was assuming that your events have a blank eventKey. _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
