-
Type:
Change Request
-
Resolution: Unresolved
-
Priority:
Trivial
-
None
-
Affects Version/s: 8.0.0rc1
-
Component/s: API (A), Frontend (F), Server (S)
After introduction of Complex event processing it has become possible to clone events processed by the CEP windows. After cloning, these clones are also processed by the same actions as original events in the same way.
From trigger Actions perspective, Users might want to react to such cloned events differently from the operations executed for the original event.
A condition, that would filter out cloned or original events, will allow them to do so.
If such condition is introduced on Action level, it would allow to execute separate actions for cloned or original events, but if it is introduced on action operation level, it would allow to separate the operations for cloned and original events within the same action.
From CEP rule perspective, such condition is already introduced on operation level, but it is missing for CEP rule conditions. As result, to avoid processing the clone by the same CEP rule that originated it, the user will need to specify an "Event is clone = No" condition for every operation. It would be much more convenient if such condition could be defined on CEP rule level.
- related to
-
ZBXNEXT-10353 Complex Event Processing (CEP)
-
- IN DOCUMENTING
-