This topic provides information about configuring services by using Central Monitoring Administration.
On the Add Monitor Types dialog, with the Monitoring Profile set to Services or Operating System, and the Monitor Type set to Windows Services, provide the following details:
Field | Description |
|---|---|
| Service Host Configuration | |
| Host Name |
|
| Disable automatic restart | Select this check box to disable automatic restart of the services configured. |
| Disable Alert For Paused Services | Select this check box to disable alerts for paused services. |
| List of Services | |
| Service Details | |
| Service Name | Specify a Display Name or Service Name to add the service for monitoring. Regular expressions are supported only for Display Name. |
| Use Display Name | Select this option to add services by using Display Name or clear this option to add services using Service Name. |
| Service Startup Type (This feature is available in 4.8.10 and later versions of the KM) | |
| Automatic | Select this check box to monitor the services with Startup Type as Automatic, Automatic (Trigger Start) Automatic (Delayed Start). This checkbox is enabled by default. |
| Manual | Select this check box to monitor the services with Startup Type as Manual, Manual (Trigger Start). This checkbox is enabled by default. |
| Disabled | Select this check box to monitor the services with Startup Type as Disabled. |
| Generate an Alarm/Warning when service is stopped | Select this check box to generate a PATROL alarm or warning when the service stops. |
| Alert State | Select one of the following options to define the type of alert you want to raise when the service stops:
|
| Restart service when stopped | Select this check box to enable re-starting the service when it stops. |
| Enable process monitoring for the service(s) | Select this check box to enable process monitoring for the services. |
| Use command line for non-responsive service(s) | Select this check box to use the command line for non-responsive services. Specify the command line that must be used in the Command line field. |
| Command line | Specify the command line that must be used for non-responsive services. |
| Add to List | Click this option for confirming the configuration information that you provided and adding the service name specified to the list of services. Select the services that you want to finally configure and click this option so that the host name appears in the list of service hosts configured. |
| Modify Selection | Select one of the items that you added to the list in the preceding step, and click this option to modify details. |
| Remove from List | Select the items added earlier and click this option to delete that item from the list of configured objects and the clear the details provided in the earlier fields. |
| Add | Click this option to add this monitoring configuration. This information is displayed on the Monitor Configuration page. After you click this option, you can continue to add more objects for monitoring. |
| Reset | Click this option to clear off your configuration details and revert to default settings. |
| Close | Click this option to exit without saving any changes. |
Related topics
Configuring in a BMC ProactiveNet Performance Management environment
Overview
Content Tools
Apps
Reporter Replacement
com.bmc.atlassian.bmc-util-plugin-2.section.label
Tasks
2 Comments
Daric Smith
I had to open a ticket because the section "Service Startup Type might lead someone to think having those boxes check will monitor ALL services in an Automatic or Manual state.
The fact is, if you configure individual service monitor, the boxes must be checked or they won't get monitored.
I am trying to understand the use-case where you would ever uncheck the boxes.
Edoardo Spelta
Startup type is NOT available in CMA policies based on 4.8, the startup type section doesn't even appear in the CMA GUI.
It's only available from 4.8.10 and greater.
Without this section available, what is the agent supposed to monitor ? It seems to me that it will go on and monitor all configured services regardless of startup type ? Including disabled ones ?
4.8.10 monitoring profile has also changed name to something different from Microsoft WIndows Servers, which luckily was mantained in 4.9, and is inconsistent with 4.8, resulting in the 4.8.10 policies not to inherit global thresholds set for 4.8