Integrating the check-in URLĪfter adding the monitor it will have a “Started” status. Leaving the other options as default, we can click “Save”. Our plan here is to get notified if and when the scheduled FileMaker script does not run in a timeframe of 65 minutes. Accounting for some delays and runtime, it makes sense to define a custom check-in interval of 65 minutes. Let’s say our script is scheduled to run every 60 minutes. We can give the monitor a name for reference and then set a check-in interval. Once you have registered on allgood.systems you can navigate to the “Job Monitors” tab to create a new monitor for the FileMaker script you would like to get notifications for. I will be using allgood.systems, a monitoring platform I recently built. In this tutorial I want to describe how you can setup immediate notifications whenever your scheduled FileMaker scripts stop running – for example due to a crashed FileMaker scripting engine, an error in your script or just general server downtime.
0 Comments
Leave a Reply. |