Page tree
Skip to end of metadata
Go to start of metadata

This task describes how to modify the configuration of a monitored process.

  1. Double-click the NUK_Process_Container application class.
  2. Access the NUK_Process application menu.
  3. Select Manage List of Monitored Processes from the pop-up menu.
    The Manage List of Monitored Processes dialog box is displayed.
  4. In the Process List group box, select the process you want to modify.
  5. In the Actions group box, select Modify Selected Process, and click OK.
    The Modify Selected Process dialog box is displayed.
    Use the instructions in step 6 through step 21 to modify the monitoring attributes you would like to change.
  6. In the Process Instance Label field, type a name for the monitored process icon (maximum 100 characters).
  7. In the Monitored Process String field, type the command or a unique command string for the process that is being monitored.

    Note

    • BMC PATROL monitors all processes that match the string you type in this field. When you enter text in this field, you might end up monitoring multiple processes. For example, if you type vi in this field, BMC PATROL will monitor processes named vi, view, and previous.
    • You must specify a single process if you want to use the BMC PATROL feature that allows you to restart a process automatically.
  8. In the Minimum Count field, type a value to set the minimum number of process instances that must be running on the local computer or in the host group. For example, if you want at least three instances of the process to run at all times, type 3 in this field. If the number of running process instances falls below this value, BMC PATROL will issue an alert.
  9. In the Maximum Count field, type a value to set the maximum number of process instances that might be running on the local computer or in the host group. If the number of running process instances exceeds this value, BMC PATROL will issue an alert. The value of the Maximum Count field must be greater than the value of the Minimum Count field.
  10. In the Acceptable Process Owners field, type the user IDs for the accounts that might own the process. Separate multiple user IDs with spaces.
  11. Select the Use Process Owners for Filteringcheck box.

    Note

    Because the process filtering for the processes is based on owners, the owner of the processes is always a subset of the provided owner set. Therefore, the ProcessOwnerCheckk parameter is deactivated when the Use Process Owners for Filtering check box is selected.

  12. Select the Parent Process ID Must Be 1 option if the parent process ID (PPID) is 1. A process with a PPID of 1 is owned by init, or the UNIX scheduler.
  13. Select the Filter Processes with Parent Process ID 1check box if you want to filter the processes by Parent Process ID 1.

    Note

    • If you select the Filter Processes with Parent Process ID 1 check box, only the processes having parent process ID 1 are filtered.
    • If you do not select the Filter Processes with Parent Process ID 1 check box, the processes are filtered irrespective of their parent process ID.
    • If you select Yes for the Parent Process ID Must Be 1 field, and if you filter processes with parent process ID 1, the ProcessParentPID1 parameter will be deactivated.
    • If you select No for the Parent Process ID Must Be 1 field, the processes are not filtered by parent process ID 1.
  14. Select the Restart Automatically option if you want the KM to automatically restart a process when it detects that the process count is less than the set minimum.
    If you select this option, the KM will attempt to restart the process when it detects that the process instance count has fallen below the specified minimum threshold. The KM uses the value in the Command Execution Attempts field to determine how many times it will try to restart a process.

    Note

    You must specify a start command and a command execution user name in the appropriate fields on this dialog box if you want BMC PATROL to automatically restart a process.

  15. In the Command Execution Attempts field, type a value set the number of times the host will attempt to run a Start Process or Stop Process command before it stops trying to run the command.
  16. In the Start Commandfield, type the command string that will start the process instance.

    Note

    You must specify a command execution user account and password if you want to use the Start command.

  17. In the Stop Commandfield, type the command string that will stop the process instance.

    Note

    You must specify a command execution user account and password if you want to use the Start command.

  18. In the Command Execution User Name field, type the user ID under which the command will be executed.

    Note

    You must specify a command execution user account and password if you want to use the Start and Stop commands.

  19. In the Command Execution Password field, type the password for the user ID under which the command will be executed. You can leave this field blank. The KM will accept a NULL value.

    Note

    You must specify a command execution user account and password if you want to use the Start and Stop commands.

  20. In the Alert Delay Count field, type a value to set the number of collection intervals that this host will defer an alert while it waits for the process count to be reestablished on a host or across a group of hosts.
    If you delay the alert, the system has time to detect that a process has died and restart it automatically before BMC PATROL issues an alarm.
  21. Click the drop-down list button in the Alert Statefield and select the state change that will occur when the process count either falls below the minimum threshold or exceeds the maximum threshold and the alert delay count reaches 0. The state change will apply to the following parameters:
    • PROCPPCountCheck
    • PROCPPOwnerCheck
    • PROCPPParentID1

      Note

      The alert thresholds for ProcessCountCheck must not be modified in order for the product to work as designed. Alerts for process presence monitoring are generated based on the ProcessCountCheck parameter, which has the following thresholds defined:

      • 0 for OK
      • 1 for WARNING
      • 2 for ALARM
  22. From the Monitoring Scope drop-down list, select whether you want BMC PATROL to monitor the process on one host computer or across a group of hosts:

    Option

    Description

    Only On This Host

    BMC PATROL will only monitor the process on the selected local host computer.

    Across Host Group

    BMC PATROL will monitor the process across a group of host computers. Select this option if you want to monitor a process in a clustered environment.

  23. In the Blackout Period fields, enter a beginning and ending blackout time (use 24-hour clock).
  24. Click OK.
    The dialog box closes, and the Manage List of Monitored Processes dialog box is displayed. The process that you just added to the monitored queue is listed in the Process List group box.
  • No labels