Parameter summary

BMC PATROL for Log Management has various parameters that provide statistical information about resources, operating status, and performance. The following table lists each application class and its associated parameters. The table also provides information that you can use when selecting or reviewing the appropriate parameters used in monitoring the PATROL KM. See Parameter defaults topic for the default values of each parameter.

 PATROL for Log Management parameter summary

Parameter

Description

LOG Application Class

LOGCollectionStatus

Displays the collection status for a remote host. The parameter goes into an alarm state when collection fails. The values for this parameter are:

  • 0 - No collection
  • 1 - OK 
  • 2 - Collection failed

This parameter is available only for log monitoring on remote hosts.

LOGMainColl

Is used internally by the PATROL KM for LOG Management application for normal priority scan. Has no icon. This parameter is available only for log monitoring on the local host.

LOGMainCollP2

Is used internally by the PATROL KM for LOG Management application for medium priority scan. Has no icon. This parameter is available only for log monitoring on the local host.

LOGMainCollP3

Used internally by the PATROL KM for LOG Management application for low priority scan. Has no icon. This parameter is available only for log monitoring on the local host.

LOGRemoteMainColl

Is used internally by the PATROL KM for LOG Management application for normal priority scan on remote hosts. Has no icon. This parameter is available only for log monitoring on remote hosts.

LogSCPColl

Is used to copy pmgreader to the remote host. This parameter also checks whether the pmgreader process is running on the remote host, and if the binary file is valid. If an invalid pmgreader binary file is found on the remote host, or if pmgreader has not been copied to the remote host, PATROL KM for LOG Management copies the required binary file to the remote host and any existing file is overwritten. The pmgreader binary is located in the*$HOME*/BMCPatrol/ directory on the remote host. This folder is created by the KM. This parameter is inactive by default. It becomes active when you configure a remote instance for the first time, or when a remote instance is discovered for the first time. This parameter is available only for log monitoring on remote hosts.

Note

Pmgreader cannot be copied to the remote host if it is already running, and an notification is displayed in this case.

RemotePipeColl

Executes the pmgreader binary with the pipe argument to monitor named pipe instances. This parameter is available only for log monitoring on remote hosts.

LOGCMACollector 

The LOGCMACollector collector parameter has no icon and is used internally by the PATROL KM for LOG Management application. The collector is used to synchronize Central Admin configurations for PATROL KM for LOG Management. This parameter is available only for log monitoring on the local host.
LOGConfiguration StatusThis parameter displays the configuration status of log monitoring over the Central Monitoring Administration. The parameter goes into an alarm state when Central Administration configuration fails. This parameter is available only for log monitoring via Central Monitoring Administration.

LOGMON Application Class

LOGErrorLvl

Is used to set OK, WARN, or ALARM status based on criteria specified for the log file definition. Threshold values are: 

  • 1 - OK
  • 2 - WARN
  •  3 - ALARM If the threshold of a search criterion is breached, this parameter displays the number of matches of that search criterion as annotated text. 

Warning

Do not change the default thresholds of this parameter. Doing so prevents the KM from functioning correctly.

LOGFileSize

Displays the file size of monitored files. The log file size limit is 2 GB.

Note

If this parameter is inactive, the value of the LOGGrowthRate parameter will be inaccurate.

LOGFileSize MB

Displays the size of the file you are monitoring in megabytes The LOGFileSize parameter displays the size of the file you are monitoring in bytes. When the number that represents the file size in bytes exceeds 10 digits, the number no longer displays correctly. If this is an issue in your environment, deactivate the LOGFileSize parameter, and activate the LOGFileSizeMB parameter.Note: The LOGFileSize MB parameter is inactive by default and should only be activated after you have inactivated the LOGFileSize parameter.

LOGFileSizeStatus

Displays the status of the monitored files. The parameter goes into an alarm state when the file size of the monitored file exceeds the specified threshold. 
The values for this parameter are: 

  • 0 - OK 
  • 1 - ALARM

Note

 This parameter is active only if the KM is configured for alarm based on the file size of the monitored file.

LOGFileTimestampStatus

Displays the status of the monitored files. The parameter goes into an alarm state when the time stamp of the monitored file changes. 
The values for this parameter are: 

  • 0 - OK 
  • 1 - ALARM 

Note

This parameter is active only if the KM is configured for alarm based on the time stamp of the monitored file.

LOGFilePermissionStatus

Displays the status of the monitored files. The parameter goes into an alarm state when the permissions of the monitored file change. 
The values for this parameter are: 

  • 0 - OK 
  • 1 - ALARM 

Note

This parameter is active only if the KM is configured for alarm based on the permissions of the monitored file.

LOGGrowthRate

Displays the growth rate of the log file to graph changes in the size of the log file over time, calculated by the change of the LOGFileSize parameter over time.

Note

If the LOGFileSize parameter is inactive, the value of LOGGrowthRate will be inaccurate.

LOGMatchString

Displays the string that matched the regular expression defined in the log search It also displays the summary of the number of matches found for all the search criteria.

LOGMONRecoveryColl

Used internally by the PATROL KM for LOG Management application.This parameter has no icon

LOGSearchString

Displays the total number of search string matches found for all the search criteria during the last scanning cycle. A value of 0 indicates that no matches were found.

LOGStatus

Displays the status of the monitored log file:

  • 0 - Missing or unknown
  • 1 - OK
  • 2 - Modified
  • 3 - Read Error
  • 4 - Inactivity/Error
  • 5 - Missing Message Error
  • 6 - File Growth Rate Exceeded
  • 7 - Invalid File

If the default account of the PATROL Agent does not have read access to a file, the LOGStatus parameter is set to a value of 3 (Read Error). If you configure a PATROL KM for LOG Management instance with theGenerate Alert if no Match Found at Scan Endcheck box selected in the Schedule Log Scan dialog, and no match string is found during the scheduled duration, the LOGStatus parameter is set to a value of 5(Missing Message Error). If there is an error while scanning the XML file because of reasons such as invalid XML syntax, the value of this parameter is set to7 (Invalid File). On UNIX systems, you can change the permission of the pmgreader binary file to the setuid root, which is owned by the root account with the 6755 permission. You can also change the permission of the file or add the default account of the PATROL Agent to a user account that has the permission to read the file.

LOGT Application Class The LOGT application class has no parameters.
Was this page helpful? Yes No Submitting... Thank you

Comments