Configuring service monitoring

By default, PATROL monitors the availability of all system services except for those where the start-up type is disabled. You can change the monitoring properties of the monitored services or add other services to monitor. The following table shows you how the KM monitors each start-up type by default.

Default service monitoring flags

To change the default settings for services, select the Configure Service Monitoring menu command from a Services application instance to perform the following tasks:

  • To add services to the list of monitored services, select the Configure Service Monitoring > Add Service menu command.
  • To remove services to the list of monitored services, select the Configure Service Monitoring > Remove Service menu command.
  • To configure monitored services, select Configure Service Monitoring > Configure Service menu command.

By default, the Windows KM monitors all services with startup type as 'automatic' or 'manual'.

  • If you want to monitor a disabled service, add the service by using the Configure Service Monitoring > Add Service menu command. The Monitor pconfig variable for the service is set to '1'.
  • If you add a disabled service and later remove the service by using the Configure Service Monitoring > Remove Service menu command, the Monitor pconfig variable is not set to '0'. However, the removedServiceList pconfig variable is updated to contain this particular service.

Thus, Windows KM monitors a service only if the Monitor pconfig variable for the service is set to '1' and the service is not included in the list of the removedServiceList pconfig variable.

Service monitoring options

When you select the Configure Service Monitoring > Configure Service menu command, after you select the service you want to configure, you are presented with the monitoring options. The following table provides you with names, descriptions, and default values for these options, and the configuration variable associated with each option.

 Service monitoring options

Ensuring that services are restarted as desired

If the services that you are monitoring are not restarted by PATROL as desired, determine the values of the agent configuration variables that affect whether a service is restarted when it goes down. The following table shows the possible combinations of values for these variables and how each combination causes PATROL to restart (yes) or not restart (no) a monitored service when it goes down.

Configuration variable and service restart: combinations

Service configuration variable

Possible values

DisableServiceRestart (global)

0

0

0

0

1

1

1

1

AutoRestart (local)

0

0

1

1

0

0

1

1

OverrideGlobalServiceRestart (local)

0

1

0

1

0

1

0

1

Service is restarted? (yes/no)

No

No

Yes

Yes

No

No

No

Yes

For detailed information about the various configuration tasks that you can perform, see:

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*