turning off event deduplication ?

[mapzenoss]

mapzenoss [http://community.zenoss.org/people/mapzenoss] created the discussion

"Re: turning off event deduplication ?"

To view the discussion, visit: http://community.zenoss.org/message/74866#74866

--------------------------------------------------------------
hello,

I am recent user of zenoss and interested too about how to disable the deduplication completely for all messages. So.. anybody know how to do it?

thanks

I use zenoss 4.2.4
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/74866#74866]

Start a new discussion in zenoss-users at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[jcurry]

jcurry [http://community.zenoss.org/people/jcurry] created the discussion

"Re: turning off event deduplication ?"

To view the discussion, visit: http://community.zenoss.org/message/74892#74892

--------------------------------------------------------------
You can apply an event transform to an event class - you do not have to create an event class mapping.  Event Class transforms are rather hidden - drill to the event class and use the Action (gear) icon at the bottom of the left hand menu to show the link to create a transform.

Class transforms cascade.  So, you can, if you want, have a class transform at the root (/) event class.  Under that, you may have an App class - again with a transform.  This App class will have the / transform applied first and then its own App transform - and so on down the event class hierarchy.  If you do have an event class MAPPING transform for a class then that is applied AFTER any class transforms.

This may or may not help you - depends on whether your events that you want to dedup fit nicely into the event class hierarchy.

The point of the reference that jmp242 pointed you at is fundamentally that eventKey is one of the fields used to determine the duplicate "fingerprint" (provided it exists).

If you haven't already seen it, you may find the Zenoss Event Management paper that I wrote helpful - http://www.skills-1st.co.uk/papers/jane/zenoss4-events/ http://www.skills-1st.co.uk/papers/jane/zenoss4-events/ .

Cheers,
Jane
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/74892#74892]

Start a new discussion in zenoss-users at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]