Tried doing it with a FileMaker Script but that get slow really fast. Problem seems to be the Process Logs. As I understand you use them to monitor the running of the FM services. But they generate about 300-500 Log entries a second with only 5 monitored servers. And deleting them from within filemaker is really slow. Truncating or deleting them from SQL is way faster. I think the deamon should only maintain 1 set of process info (the current one). Everything else is just too confusing and there is no way one can make use of the amount of data right now.
Attached, user pass both admin. Find Script searching for CURL in Script Workspace. Also did a few adaptions regarding notification frequency.
And regarding this probably a threshold for notification would be nice to avoid false positives. Sometimes the WB reports a server problem and the next minute it's gone. So a configurable threshold would be nice (e.g. if we set it two double the time of the frequency of the server side script it would avoid false positives - with the caveat of notifying a tad delayed)
It would also be nice if you could enter more than 1 Prowl account for a server and if those accounts (api Keys) could be on a server basis.
Additionally I'd love to have a HDD monitoring as well. To see if the HDD fills up and in the event be able to take action before everything crashes.
RAM as well probably.
You told us in Berlin but I forgot - what is the reason the deamon does not work with FM11? I also have problems with a FM14 Host of mine, 15+ is working fine.
Thanks for all this fantastic work btw!!