File Trigger polling interval minimum - 5 or 30 seconds?

YetAnotherOpsGrp (1 post)
February 1, 2021 07:47 AM
Accepted Answer

Love the product!

We have a job where we actually want a fairly small polling interval.  According to the documentation, we can set a polling interval of 5 seconds, but there appears to be a hard limit in the UI for 30 seconds.

From the docs...

"suppose you are monitoring a log file for changes. The first time adTempus detects a change to the file, it will trigger your job. If the application that is writing to the log file continues to write to it, adTempus will continue to trigger your job each time it detects a change, so it will continue to trigger each time the Polling Interval elapses. If your polling interval is 5 seconds, adTempus will fire the job every 5 seconds."

 

If we actually WANTED a polling interval of 5, is that possible?

CM

Bill Staff (599 posts)
February 1, 2021 09:43 AM
Accepted Answer

I guess we need to reword the example :)

There is a minimum interval of 30 seconds for, I think, performance reasons, which may be less necessary now as we've made various performance improvements to the file monitoring over the years. If you'd like to try a shorter polling interval and you're on a maintenance subscription, open a support case referencing this discussion and we can make a change to allow it. You'll need to be on the latest version (4.7) and be able to deploy updates to both the adTempus server and the Console.

Replies are disabled for this topic.