PATROL for Linux agent configuration variables
The following table lists the configuration variables for PATROL for Linux. You can use the PATROL Configuration Manager or the pconfig utility to view variable settings or to deploy them to other computers. See the PATROL Configuration Manager User Guide or the online technical documentation for BMC PATROL Agent 9.6 for more information.
Configuration variable | Description |
|---|---|
/NUK/LibvirtSock | Changes the standard socket directory for the libvirtd process, /var/run/libvirt to any other directory. |
/NUK/configuredFromPconfig | Cleans old (corrupt) entries that include comma character in the file system name. Valid values:
|
/NUK/AnnotationInterval | Sets the interval (in seconds) between the annotations. If this variable is not configured the annotation appears
If this variable is configured the annotation appears
|
Configuration variables for local monitoring | |
/NUK/NUK_FileSystem_Container/regEx | Excludes filesystems by name, and removes them from monitoring. |
/NUK/NUK_FileSystem_Container/FS_PreDiscoveryExcList | Excludes container-related filesystems from monitoring. By default, the field contains a comma-separated list of regular expressions: /var/lib/docker.*,/var/lib/kubelet.*,/run/docker/netns.*,/run/docker/runtime.*,/app/docker.*,/var/lib/origin/openshift.* To protect your environment from corrupting, BMC recommends you to retain the list. Add additional regular expressions to identify such container-related filesystems that you want to exclude from monitoring. Do not leave this variable blank. |
/NUK/NUK_FileSystem_Container/CUSTTokens | Excludes custom filesystem types from monitoring. For example, ext4. Separate multiple entries with a space. |
/NUK_FileSystem_Container.excludeTypes | Excludes filesystems by type. Default value is 0000. Here are the values that you can enter for different filesystem types:
The position of 1 in the four-digit value determines if you want to exclude a particular filesystem type from monitoring or not. For example, the first digit in the value determines if you want to exclude NFS filesystem types or not. Here, 1 determines exclude from monitoring and 0 determines don't exclude. Similarly, the second digit determines if the CD filesystem types are excluded from monitoring or not. With this information, you can place either 0 or 1 in the four-digit value to determine which filesystem types are excluded from monitoring. |
/NUK/NUK_FileSystem_Container/FS_UnmountedExcList | Removes filesystems from monitoring when they become unmounted. Separate multiple regular expressions by comma (,). |
/FILESYSTEM_RecoveryDataInitialized | Created automatically. |
/NUK/NUK_Disk_Container/discovery | Created automatically. |
/NUK/NUK_FileSystem.persistentTypes | Removes unmounted filesystems by category. Default value is 1111. Here are the values that you can enter for different unmounted filesystem types:
The position of 0 in the four-digit value determines if you want to remove a particular unmounted filesystem type from monitoring or not. For example, the first digit in the value determines if you want to remove NFS unmounted filesystem types from monitoring or not. Here, 0 determines remove unmounted filesystems from monitoring and 1 determines don't remove. Similarly, the second digit determines if the CD unmounted filesystem types are removed from monitoring or not. With this information, you can place either 0 or 1 in the four-digit value to determine which unmounted filesystem types are removed from monitoring. |
/NUK/NUK_FileSystem_Container/CDFSTokens | Designates which filesystem types are considered CDFS filesystems. (Types include CDFS, HSFS, and ISO9660.) |
/NUK/NUK_FileSystem_Container/NFSTokens | Designates which filesystem types are considered NFS filesystems. (Types include NFS CACHEFS NFS3, NFSV3.) |
/NUK/NUK_FileSystem_Container/PROCTokens | Designates which filesystem types are considered PROC filesystems. (Types include PROC, USBDEVFS, and DEVPTS.) |
/NUK/NUK_FileSystem_Container/discovery | Created automatically. |
/NUK/NUK_FileSystem_Container/moniList | Removes the file system name from the variable. This option only applies to previously discovered file systems that are no longer available. |
/NUK/NUK_FileSystem_Container/nonPersistCUSTTokens | Removes custom filesystem types when they are unmounted. Separate multiple entries with a space. For example, ext4. |
/NUK/Process/Default/Created | Created automatically. |
/NUK/Process/automount/info | Defines individual processes to be monitored. |
/NUK/Process/bind/info | Created automatically. |
/NUK/Process/cron/info | Created automatically. |
/NUK/Process/daemonObjectList | Created automatically. If deleted, it will be automatically recreated |
/NUK/SudoMode | Configuration for Sudo utility to execute root privileged command. |
/NUK/VMGuestLib | Monitors VMware guest counters on a VMware guest machine The default value is /usr/lib/vmware-tools/lib/libvmGuestLib.so. |
/NUK/NUK_Network_Container/NetworkPreDiscoveryExclude | Excludes networks that you do not want to monitor. By default, the following regular expression is entered in the field - veth.*. Separate multiple regular expressions by a comma. If the networks entered in the variable are already discovered and are being monitored, the monitoring of such networks is stopped. Also, the alerts created for the Network Interface Status attribute are closed. |
Configuration variables for remote monitoring | |
REMOTE/HOSTS/<HOST_NAME>/NUK_FileSystem_Container/regEx | Excludes filesystems by name, and removes them from monitoring. |
/REMOTE/HOSTS/<HOST_NAME>/NUK_FileSystem_Container/FS_PreDiscoveryExcList | Excludes container-related filesystems from monitoring. By default, the field contains a comma-separated list of regular expressions: /var/lib/docker.*,/var/lib/kubelet.*,/run/docker/netns.*,/run/docker/runtime.*,/app/docker.*,/var/lib/origin/openshift.* To protect your environment from corrupting, BMC recommends you to retain the list. Add additional regular expressions to identify such container-related filesystems that you want to exclude from monitoring. Do not leave this variable blank. |
/REMOTE/HOSTS/<HOST_NAME>/NUK_FileSystem_Container/CUSTTokens | Excludes custom filesystem types from monitoring. For example, ext4. Separate multiple entries with a comma (,). |
/REMOTE/HOSTS/<HOST_NAME>/NUK_FileSystem_Container/excludeTypes | Excludes filesystems by type. Default value is 0000. Here are the values that you can enter for different filesystem types:
The position of 1 in the four-digit value determines if you want to exclude a particular filesystem type from monitoring or not. For example, the first digit in the value determines if you want to exclude NFS filesystem types or not. Here, 1 determines exclude from monitoring and 0 determines don't exclude. Similarly, the second digit determines if the CD filesystem types are excluded from monitoring or not. With this information, you can place either 0 or 1 in the four-digit value to determine which filesystem types are excluded from monitoring. |
/REMOTE/HOSTS/<HOST_NAME>/NUK_FileSystem_Container/nonPersistCUSTTokens | Removes custom filesystem types when they are unmounted. Separate multiple entries with a space. For example, ext4. |
/REMOTE/HOSTS/<HOST_NAME>/NUK_FileSystem_Container/persistentTypes | Removes unmounted filesystems by type. Default value is 1111. Here are the values that you can enter for different unmounted filesystem types.
The position of 0 in the four-digit value determines if you want to remove a particular unmounted filesystem type from monitoring or not. For example, the first digit in the value determines if you want to remove unmounted NFS filesystem types from monitoring or not. Here, 0 determines remove unmounted filesystems from monitoring and 1 determines don't remove. Similarly, the second digit determines if the CD unmounted filesystem types are removed from monitoring or not. With this information, you can place either 0 or 1 in the four-digit value to determine which unmounted filesystem types are removed from monitoring. |
/REMOTE/HOSTS/<HOST_NAME>/NUK_FileSystem_Container/FS_UnmountedExcList | Removes filesystems from monitoring when they become unmounted. Separate multiple regular expressions by comma (,). |
/REMOTE/HOSTS/<REMOTE_HOST>/NUK_Network_Container/NetworkPreDiscoveryExclude | Excludes networks that you do not want to monitor. By default, the following regular expression is entered in the field - veth.*. Separate multiple regular expressions by a comma. If the networks entered in the variable are already discovered and are being monitored, the monitoring of such networks is stopped. Also, the alerts created for the Network Interface Status attribute are closed. |
/NUK_LINUX_REMOTE_HOSTS/NUKREM_DBG_FILE | Location of the debug file. |
/NUK_LINUX_REMOTE_HOSTS/recon_minutes | Created automatically. |
"/REMOTE/HOSTS/NUK_FileSystem.persistentTypes | Denies filesystems by category. |
/REMOTE/HOSTS/Host_name/NUK_FileSystem_Container/CDFSTokens | Designates which filesystem types are considered CDFS filesystems. (Types include CDFS, HSFS, and ISO9660.) |
/REMOTE/HOSTS/Host_name/NUK_FileSystem_Container/discovery | Created automatically. |
/REMOTE/HOSTS/Host_name/NUK_FileSystem_Container/NFSTokens | Designates which filesystem types are considered NFS filesystems. (Types include NFS CACHEFS NFS3, NFSV3.) |
/REMOTE/HOSTS/Host_name/NUK_FileSystem_Container/PROCTokens | Designates which filesystem types are considered PROC filesystems. (Types include PROC, USBDEVFS, and DEVPTS.) |
REMOTE/HOSTS/Host_name/NUK_FileSystem_Container/moniList | Removes the file system name from the variable. This option only applies to previously discovered file systems that are no longer available. |
/REMOTE/HOSTS/Host_name/Process/Default/Created | Created automatically. |
/REMOTE/HOSTS/Host_name/Process/automount/info | Created automatically. |
"/REMOTE/HOSTS/Host_name/Process/bind/info | Created automatically. |
/REMOTE/HOSTS/Host_name/Process/cron/info | Created automatically. |
"REMOTE/HOSTS/Host_name/Process/daemonObjectList | Created automatically. If deleted, it will be automatically recreated |
/REMOTE/HOSTS/Host_name/hostInfo | Add a remote host in the PATROL Agent with the following template "/REMOTE/HOSTS/Host_name/hostInfo" = {REPLACE = "remoteHost<Ctrl+B>NONE<Ctrl+B>0<Ctrl+B>UserName"} |
/REMOTE/HOSTS/Host_name/lastExecuteSessionReturn | Created automatically. If deleted, it will be automatically recreated |
/REMOTE/HOSTS/Host_name/lastOpenSessionReturn | Created automatically. If deleted, it will be automatically recreated |
/REMOTE/NUK_FileSystem_Container/discovery | Created automatically. If deleted, it will be automatically recreated |