Application Status Monitoring
What is Application Status Monitoring?
The Application Status Monitor monitors the status of your application. If the application reported failure reaches a threshold the virtual instance which the application resides is restarted. The application, assuming it has a startup script, will be restarted as well. The monitoring is done by calling a watchdog script that you write which checks your application state and returns a status of '0' (application is running), or a non zero value (application has failed).
The script must be set to executable and reside in the opt/app_status_monitor/watchdogs/ directory of your build source. The script must be given the name W<##><name>[APPLICATIONEXTENSIONPLATFORM:.ext] . The <##> represents the startup order of 01 to 99. The <name> is whatever you want to call your script and the [APPLICATIONEXTENSIONPLATFORM:.ext] is the optional suffix.
The default monitoring interval is 12. Since each interval is equivalent to 5 seconds, this would mean that the watch dog script would be called every 60 seconds (12 * 5 = 60 seconds). The default recovery threshold is 5. Therefore if five times in a row the system receives a non zero or no value each time it checks the application status, it will then request a restart of the virtual instance in which the application resides. If a zero value is received, then the threshold count starts over.
Yes they are. Valid values are 1 to 99. You can configure these attributes by creating a file called 'config' and placing it in the opt/app_status_monitor/config directory of your build source directory. Below is an example of how to set the application to be monitored every 30 seconds, (6 * 5 seconds = 30), and cause the virtual instance which contains your application to be restarted if a failure occurs 3 consecutive times.
Yes they are. Valid values are 1 to 99. Below is an example of how to set the application to be monitored every 30 seconds, (6 * 5 seconds = 30), and cause the virtual instance which contains your application to be restarted if a failure occurs 3 consecutive times.
No package dependency is required.
No additional configuration is required.