Host-Specific Configuration and Monitoring

Each host can be configured by clicking the gear in the Host Actions column for that host.

When you select the gear icon, the Host Setting dialog appears with two tabs, Services and Configuration, enabling you to specify the services running on each host and configure host monitoring.

Services

The Services tab lets you toggle to enable or disable the services running on a specific host. Many of these services can be managed through the UI. The one exception is the Request service, which cannot be fully shut down.

When a service is shut down, the host still processes requests that have been specifically targeted to that host, but does not pick up generic, or untargeted, requests.

Monitoring Service

The Monitoring service captures and saves the latest statistics, promotes any statistics-related extended attributes to the Server object, and prunes any statistics that have outlived the configured retention period. The Monitoring service populates the task threads, request threads, and cpu usage statistics as well as statistics for memory usage, memory usage percentage, and database response time.

Reanimator Service

The Reanimator service helps manage "hung" tasks, or tasks that appear to be running even though they have stopped. An un-partitioned task can sometimes fail without properly updating the state of the TaskResult. This can leave the task in a hung state. The most common causes for this kind of issue are a temporary loss of connection to the database or a brief database server failure. Regardless of the underlying reason, the Reanimator service performs the task of resetting requests or tasks so they can resume.

The service can also help with terminating a task or request that is not configured to resume upon being orphaned or failing. If the task or request is not configured to resume, then when the service detects a task in a hung state, it automatically marks it as terminated.

Note: If you are using Email Task Alerts in any of your task definitions, be aware that when a task hangs and is restarted by the reanimator service, email task alert notifications may not be sent.

The Reanimator service runs by default on all hosts. Although it is unlikely that you would need to switch it off, it is possible to do so. For example, if you have a dedicated UI host, you might not need this service running there.

To disable the Reanimator service on a specific host:

  1. On the Hosts tab, select the gear icon beside the specific host on which you want to disable the service.

  2. On the Services tab of the Host Configuration dialog, use the slider to switch off the Reanimator service.

Configuration

The Configuration tab lets you set up host-specific monitoring configuration. What you set here overrides the global defaults for Polling Interval, Statistics Retention, and to enable and disable given retained statistics, such as CPU or task threads.

The Configuration tab also lets you select applications to monitor. Any applications you select for monitoring are contacted each time the monitoring service runs and a health check status is recorded.

The Use Default Settings button at the bottom of the Configuration tab clears your Monitoring Configuration for this host and reverts this host to the global defaults. See Monitoring Applications.

Note: When you restore default settings, any applications you have selected for Application Monitoring are retained; restoring default settings does not remove any applications you have selected for monitoring.

Note: Administrators can assign a given host to handle specific types of requests. See Specifying Hosts to Handle Requests.