The Driver Health job evaluates the conditions for the health states and assigns the driver the appropriate state. The job also executes any actions associated with the assigned state.
As with all driver jobs, there are several Driver Health job settings that you can modify to optimize health monitoring performance for your environment, including settings for how often the job runs, which drivers use the job, and how much data the job maintains to support transaction history.
To modify the job settings:
Open the Driver Health Configuration page for a driver that uses the Driver Health job you want to modify.
Click the Driver Health job.
Change the desired settings on the following tabs:
Schedule: The Driver Health job is a continuously running job, meaning that it does not stop unless a health state action shuts it down or it is shut down manually. The job must run continuously to be able to support transaction data collection for use in Transactions History conditions.
If the job does stop, it is restarted based on the schedule. The default schedule checks every minute to see if the job is running. If the job is not running, it is started.
Scope: By default, the job applies to all drivers in the driver set. This means that you only need one Driver Health job per driver set. However, you can create multiple Driver Health jobs for different drivers within the same driver set. For example, you might have some drivers whose health you want updated more frequently than other drivers, in which case you would need at least two Driver Health jobs.
Parameters: You can change any of the following parameters:
Login ID: This defaults to the login ID that was used when creating the driver job. You should only change this if you want the driver to authenticate with different credentials.
IMPORTANT:The Login ID should have subtree read rights on the driver set object for monitoring the health of the drivers under it.
Login password: This is the password required for the login ID that you supplied in the Login ID field.
Subscriber Heartbeat: Controls whether the Driver Health job does a heartbeat query on a driver’s Subscriber channel before performing a health check on the driver.
Polling interval: Determines how often the job evaluates the conditions for the health states, assigns the driver the appropriate state, executes any actions associated with the assigned state, and stores the driver’s transaction data. The default polling interval is one minute.
Polling interval units: Specifies the time unit (minutes, hours, days, weeks) for the number specified in thesetting.
Duration sampling data is kept: Specifies how long a driver’s transaction data is kept. The default, two weeks, causes a transaction to be retained for two weeks before being deleted. A longer duration provides a greater time period that can be used in Transactions History conditions, but requires more memory. For example, to use a Transactions History condition that evaluates of the number of publisher reported events for the last 10 days, you need to keep transaction data for at least 10 days.
Duration units: Specifies the time unit (minutes, hours, days, weeks) for the number specified in thesetting.
Clickto save your changes.