We posted a couple of new articles in our technical resources section. The first covers how to control the default time that event monitors are allowed to run before they time out. If you have event monitors that are doing big scans of directory structures or searching through large event logs, just adding a setting in the config.ini file might be enough to let the monitoring tasks run to completion. For those really, really long monitoring tasks we have a second article that shows how to run big tasks outside of FrameFlow but still use FrameFlow to check the results. That lets the monitoring task run out-of-band but you still get the great alerting and notification from FrameFlow. It’s a technique we use ourselves as a part of our infrastructure monitoring and it works really well.