Monitor files exist option
Posted: Tue May 10, 2016 9:51 am
Hi,
I need to execute a project when files matching a pattern arrive on an FTP site. I have tried using both monitors and schedules, but neither quite solves my problem:
Monitors:
1. Only run when there's something there to act upon (which is exactly what I'm looking for)
2. Will never run again if they failed to run when an event happened. Example: if we restart the service or reboot the server, any files that have arrived on (or were already on) an FTP site will not trigger the monitor. This is a major problem.
Schedules:
1. Always run a project whether there is useful work to do or not.
2. Logs become filled with evaluations and it's like searching for a needle in a haystack to find an entry where meaningful work was done. This is a maintenance headache that I'm looking to avoid.
What would seem ideal for this situation is the ability to add a monitor event type for the existence of any files matching the pattern. This would run only when there is something to do and would be durable in the case of a service outage - it would pickup where it left off and handle any existing files on the site.
I need to execute a project when files matching a pattern arrive on an FTP site. I have tried using both monitors and schedules, but neither quite solves my problem:
Monitors:
1. Only run when there's something there to act upon (which is exactly what I'm looking for)
2. Will never run again if they failed to run when an event happened. Example: if we restart the service or reboot the server, any files that have arrived on (or were already on) an FTP site will not trigger the monitor. This is a major problem.
Schedules:
1. Always run a project whether there is useful work to do or not.
2. Logs become filled with evaluations and it's like searching for a needle in a haystack to find an entry where meaningful work was done. This is a maintenance headache that I'm looking to avoid.
What would seem ideal for this situation is the ability to add a monitor event type for the existence of any files matching the pattern. This would run only when there is something to do and would be durable in the case of a service outage - it would pickup where it left off and handle any existing files on the site.