Giving the ability to run secondary scripts in the background, which can monitor primary scripts and client states would allow for custom local monitoring/management.
This would be extremely valuable for custom metrics monitoring on a docker/Kubernetes deployment etc.
At it's core, the monitor would need to be able to collect client data such as script crash counts, uptime, login time values etc.
These statistics can then be easily used as external metric guides.
Alternatively the client could send events caused by those state changes and leave statistic processing to the plugin.
Giving the ability to run secondary scripts in the background, which can monitor primary scripts and client states would allow for custom local monitoring/management.
This would be extremely valuable for custom metrics monitoring on a docker/Kubernetes deployment etc.
At it's core, the monitor would need to be able to collect client data such as script crash counts, uptime, login time values etc.
These statistics can then be easily used as external metric guides.
Alternatively the client could send events caused by those state changes and leave statistic processing to the plugin.