Features of Service Monitoring

Service monitoring has the following additional features. Some of these features are explained in detail in the later sections:

Note: Ensure that the Client service account has the permission to start and stop remaining services.

• Service monitoring can be disabled or enabled depending on the configuration. If the configuration file is not present, then the monitoring is disabled. If the configuration file has some invalid syntax and if there are any errors in the configuration file, then too the service monitoring will be disabled.

• The Client service has the ability to disable or enable monitoring types. In other words, the maintenance monitoring can be disabled and the remaining monitoring can be enabled. By default, the Critical Memory Monitoring option is enabled and the Warning Memory and Maintenance Monitoring options are disabled.

• The Client service has the ability to enable and disable monitoring feature for a specific AVEVA Work Tasks service. For example, Monitoring only the Communication service can be enabled or disabled.

• Whenever the Client service is started, all AVEVA Work Tasks Windows services are also started. Similarly, whenever the Client service is stopped, all AVEVA Work Tasks Windows services are also stopped.

• If any AVEVA Work Tasks Windows service is stopped, it is restarted by the Client service.

• The Client service can also monitor service specific conditions, such as the Workflow engine thread hanging behavior. This is always enabled. To know more about Workflow Engine thread hanging behavior, see Workflow Engine.

• The Client service automatically restarts during its failure. Suppose a memory leakage in the client service stops the client service, then the client service is restarted after 5 minutes. However, it will not be restarted if it is stopped manually or from other applications.

• By default, the Client service sends alert emails when the services are restarted. However, you can configure whether the alert emails must be sent or not.

• If a service is not installed, it will not be monitored even if its configuration section values are present in the configuration file.

• If the Workflow Engine service is unable to acquire the required license, then the service does not get started. In this scenario, the Client service monitoring is disabled.

• If the load balancing feature is not enabled on a server, then the Advance Server Service will not be monitored by the Client service. 

• In a load balanced environment, if the Workflow Engine service or the Advance Server Service is unable to acquire the required license, then the service does not get started. In this scenario, the client service monitoring is disabled.