Re: [rules-users] Fusion: Insert passed events
Use the "true" time of the event for the event's @imestamp attribute
and do not rely on the automatic timestamp added by the engine.
Of course, if some event is delayed on the wire, rules checking the
absence of an event will still fire incorrectly.
-W
On 14/03/2012, javadude <sven(a)bighugesystems.com> wrote:
Hi !
scenario: Event A then Event B. If there is no Event B after 5 min of A then
trigger rule.
*when
time1:(Event) from entry-point xxx
not (Event(this after[ 0,5m ] time1)) from entry-point xxx
then
...
end*
For realtime event that works fine, but in real life you have the event
coming in delayed, eg. from an interface.
Example:
Event A time: 01:00 (mm:ss) but received at 02:00
Above rule will trigger at 07:00, but the business logic would require it to
be triggered at 06:00
How do I handle this kind of requirement ?
Thanks
Sven
--
View this message in context:
http://drools.46999.n3.nabble.com/Fusion-Insert-passed-events-tp3824630p3...
Sent from the Drools: User forum mailing list archive at Nabble.com.