My webMethods Server 10.11 | My webMethods Server Webhelp | Administering My webMethods Server | Startup and Configuration | Using My webMethods Server with Docker | Monitoring My webMethods Server Containers
 
Monitoring My webMethods Server Containers
 
Implementing Custom Health Indicators
Monitoring My webMethods Server Containers with Prometheus
By default, the generated Dockerfile for My webMethods Server includes a HEALTHCHECK instruction that checks the status of each container by testing a number of health indicators such as database connectivity, disk space and memory status, directory service connectivity, and so on.
The container health check for My webMethods Server is configured to run 5 minutes after you start a container, to trigger each individual check 15 seconds after the previous check completes, and to fail if an individual check fails to complete within 30 seconds. You can modify these settings in the generated Dockerfile for your installation. For more information about modifying the HEALTHCHECK instruction, see the Docker documentation.
My webMethods Server containers include the following predefined health indicators:
*MemoryHealthIndicator - passes if the total amount of available memory in the system is larger than a predefined value. The predefined value is 20 (percent). Enabled by default.
*JettyThreadHealthIndicator - passes if the ratio of the number of the current Jetty threads to the number of the maximum available Jetty threads is larger than a predefined value. The predefined value is 20 (percent). Enabled by default.
*DiskspaceHealthIndicator - passes if the total amount of available disk space is larger than a predefined value. The predefined value is 20 (percent). Enabled by default.
*DatabaseConnectivityHealthIndicator - passes if the container can connect to the database and execute a simple query. Enabled by default.
*AXSRFTGenerationHealthIndicator - passes if My webMethods Server successfully generates an AXSRFT token. Enabled by default.
*CustomDataSourceHealthIndicator - passes if the container can connect to the external data sources, defined for My webMethods Server. Enabled by default.
*DirServiceConnectivityHealthIndicator - passes if the container can connect to the external data source(s), defined for My webMethods Server. Enabled by default.
*ProcessEngineConnectivityHealthIndicator - passes if the container can connect to the Integration Server that hosts Process Engine. Enabled by default for containers that include Task Engine.
*RulesEngineConnectivityHealthIndicator - passes if the container can connect to the Integration Server that hosts Business Rules. Enabled by default for containers that include Task Engine.
*UmConnectionHealthIndicator - passes if the container can connect to the Universal Messaging. Enabled by default when useDbJms=false.
My webMethods Server containers provide a dedicated endpoint at http://container_host:port/health, which exposes the current values, measured by all configured health indicators. Accessing the health endpoint requires basic authentication with an account that is a member of the Admin role.
You can configure the default indicator thresholds, and switch individual checks on or off using a healthCheck.json configuration file. For more information about the healthcheck configuration file, see Container Health Check Samples.
In addition to the default health indicators for containers, you can implement a custom indicator and register it with My webMethods Server, as described in Implementing Custom Health Indicators.