Open tapuhi opened 6 years ago
Although the feature is possible, I think it is not enough general purpose. Scheduler is designed to do just one task: executes external executables. Its duty ends there.
These executables are normally scripts.
The most common use for these script is to monitor backends, and they normally connect back to ProxySQL's Admin to fetch some configuration (ex: list of servers), or to reconfigure ProxySQL based on configuration pulled from somewhere else.
As said, depending from the types of scripts, although not required they normally connect back to ProxySQL.
Because ProxySQL's Admin itself is a database, nothing stops you from creating one of more tables on disk
where the scrip itself can log whatever you want, from its total execution time (before exiting), to the execution time of various blocks of code, to any current status, etc etc
Thanks for the reply . I will definitely use the underlying dB and create my “own” monitoring table.
Unless I am missing something, there is no way to get statistics of scheduler tasks like successful/failed runs, the time it took, etc....
The script itself is throwing logs, but it would be useful to get the above info into proxysql stats tables.