Configuring local monitoring of Solaris OS

Select or clear these fields to exclude Services based on their status.

• Online - Select this checkbox to exclude services with Online state. An Online state indicates that the instance is enabled and running or available to run. The online state is the expected operating state for a correctly configured service instance with all dependencies satisfied.
  
• Legacy - Select this checkbox to exclude services with Legacy state. A Legacy state indicates the service is not directly managed by SMF, but it was started at some point. By default, all Services of Legacy type are excluded.
• Disabled - Select this checkbox to exclude services with Disabled state. A Disabled state indicates that the instance is not enabled and is not running or available to run. By default, all Services of Disabled type are excluded.
  
• Maintenance - Select this checkbox to exclude services with Maintenance state. A Maintenance state indicates that the instance is enabled but not able to run. The instance might be transitioning through the maintenance state because an administrative action has not yet completed. Otherwise, administrative action is required to resolve the problem.
  
• Offline - Select this checkbox to exclude services with Offline state. An Offline state indicates that the instance is enabled but not running or available to run. For example, if the dependencies of an enabled service are not satisfied, the service is kept in the offline state.

Enter the service name or a regular expression to include multiple services for monitoring. Multiple regular expressions can be separated by using a pipe separator. By default, all the services are included for monitoring.

Enter a display name (process label) for processes to be monitored. The display name cannot contain special characters ( . [ ! @ # $ % ? { } ^ \ \ / | + = & * ( ) ) ; ] ) and blank spaces. The label can contain a maximum of 100 characters.
For example: Display name can be sshd_proc, patrolagent_proc. 

If you want to monitor a process running inside a non-global zone from a global zone, the process label must be in the following format:
<Host name of the non-global zone>:<Process Label>

Enter a string that matches names of processes to be monitored. Input may also be a regular expression pattern.

For example:

• The string can be /usr/sbin/sshd, Patrol.*
• To monitor PATROL Agent process running on port 3282 enter the regular expression as PatrolAgent -p 3282$

Note: PATROL monitors all processes that match the string you type in this field. When you enter text in this field, you may end up monitoring multiple processes. For example, if you type vi in this field, PATROL monitors processes named vi, view, and previous.

See process configuration examples.

Select a value to set the maximum number of process instances that may be running on the local computer or in the host group. If the number of running process instances exceeds this value, PATROL issues an alert.

Note: The value in the Maximum Count field must be equal to or greater than the value in the Minimum Count field.

Enter the user IDs for the accounts that may own the process. Separate multiple user IDs with spaces. 

Regular expressions are supported.

Select this check box to filter processes based on the process owners.

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. Thereby, the Process ownership check (OwnerCheck) attribute is deactivated when the Use Process Owners for Filtering check box is selected.

Parent Process ID Must Be 1

Click the drop-down list button in the Alert State field and select the state change (ALARM or WARNING) that occurs when the minimum or maximum process count is exceeded and the alert delay count reaches 0. The state change applies to the following attributes:

• Process count check (CountCheck)
• Process ownership check (OwnerCheck)
• Parent PID is 1 (ParentPID1)

Note: The alert thresholds for Process count check (CountCheck) must not be modified in order for the product to work as designed. Alerts for process presence monitoring are generated based on the Process count check (CountCheck) attribute, which has the following thresholds defined:

• 0 for OK
• 1 for WARNING
• 2 for ALARM

Select this option if you want the KM to automatically restart a process when it detects that the process count is less than the set minimum.

No - Indicates that the process must be restarted manually if it stops.

Yes - Indicates that the process is restarted automatically if BMC PATROL detects it has stopped. If you select this option, the KM attempts 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 tries to restart a process.

Note: To restart a process automatically, you must provide a start command and a command execution account user name and password in the appropriate fields on this configuration screen. 

Enter the filesystem name or a regular expression to exclude filesystems from monitoring. To exclude multiple filesystems, enter a comma-separated list of regular expressions. To exclude the root filesystem use the ^/$ regular expression.

If the rules are equally specific (if you exclude a file, and include the same file) then exclude takes precedence over include.

Enter the filesystem name or a regular expression to include filesystems for monitoring. To include multiple filesystems, enter a comma-separated list of regular expressions. To include the root filesystem use the ^/$ regular expression.

Enter the FileSystem type that you want to filter.

FileSystem types are:

DEV, FD, DEVFS, PROC, LOFSPROCFS, CTFS, FIFOFS, FDFS, MNTFS, NAMEFS, OBJFS, SHAREFS, SPECFS, SWAPFS

Enter the FileSystem types for which persistence monitoring must be denied. The corresponding filesystem instances are destroyed from PATROL Agent. The Mount status (MountStatus) attribute is not set to alarm if the filesystem is unmounted. If such filesystems are mounted again, the instances are rediscovered.

Multiple FileSystems can be separated by using a space character.

Enter the Zpool name or a regular expression to exclude Zpools from monitoring. To exclude multiple Zpools, enter a comma-separated list of regular expressions.

Enter the Zpool name or a regular expression to include Zpools for monitoring. To include multiple Zpools, enter a comma-separated list of regular expressions. By default, all the discovered Zpools are included for monitoring.