This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
In V5.1.1 we had a rare problem where NV received a trap but appeared not to be
forwarded to T/EC. With V6.0.1 implemented we want to set the T/EC forwarding
rule to log all events being processed.
This introduced a delay of several minutes in processing events and some events
being lost all together. When the rule is removed there's a flood of bankedup
events.
The rule is:
Event Stream ---> Query SmartSet ---> Action ---> Forward
Check if events Echo event Forward to T/EC
from this node variables
should go to T/EC to a file
The production rule set is:
Event Stream ---> Query SmarSet ---> Forward
We're running NV 6.0.1, Solaris 2.6 and Framework 3.6.2. T/EC is on a different
TMR to NV. The rule is NOT defined in ESE.automation. I do realise this rule
will process all events not just the ones we want sent to T/EC.
Is anyone else trying to log events before they're forwarded to T/EC?
Thanks
Graeme Nelson
Macquarie Bank Ltd
Sydney, Australia
In V5.1.1 we had a rare problem where NV received a trap but appeared not to be forwarded to T/EC. With V6.0.1 implemented we want to set the T/EC forwarding rule to log all events being processed.
This introduced a delay of several minutes in processing events and some events being lost all together. When the rule is removed there's a flood of bankedup events.
The rule is:
Event Stream ---> Query SmartSet ---> Action ---> Forward
Check if events Echo event Forward to T/EC
from this node variables
should go to T/EC to a file
The production rule set is:
Event Stream ---> Query SmarSet ---> Forward
We're running NV 6.0.1, Solaris 2.6 and Framework 3.6.2. T/EC is on a different TMR to NV. The rule is NOT defined in ESE.automation. I do realise this rule will process all events not just the ones we want sent to T/EC.
Is anyone else trying to log events before they're forwarded to T/EC?
Thanks
Graeme Nelson
Macquarie Bank Ltd
Sydney, Australia
|