Configuring Log Monitoring

The KM supports monitoring of PATROL Agent log files with predefined search criteria. To enable this monitoring, select the Monitor PATROL log files check box.

When this option is enabled, the KM creates two monitoring instances, PAgentLog_Alarm and PAgentLog_Warn to monitor the PATROL Agent log files with the predefined search criteria.

• PAgentLog_Alarm - This instance is configured to raise the alarm if one or more of the following strings are detected:

• • “found inconsistencies”
  • “PatrolAgent-W-EINTERNAL: PatrolAgent is running low on memory”
  • “PatrolAgent: "not superuser"
  • “Please check parameter history for corruption“
  • “runqSchedPolicy is now set to 9“
  • “Detected during operation readRec.fseek”
  • PAgentLog_Alarm

• PAgentLog_Warn - This instance is configured to raise a warning if one or more of the following strings are detected:

• • “remaining for PATROL license to expire”
  • “Not authorized connect agent”
  • “Please check parameter history for corruption”
  • “PatrolAgent-E-EFORK: Couldn't fork a new process”

The PAgentLog_Alarm and PAgentLog_Warn monitoring instances have a constant predefined search criteria that cannot be edited.

Select this check box if you want the KM to collect debug information for the pmgreader process in the log file.

The diagnostic output is written to the monitored system in the following location:

• on UNIX: $PATROL_HOME/../pmg/port_ int*/readerLog.txt*
• on Windows:%PATROL_HOME%\port_ int*\readerLog.txt*

where port is the port used by the agent and int is an integer (1, 2, or 3) that corresponds to the LOG KM collector's scan priority.

Note: Selecting this check box enables debug information collection for all supported file types - text, binary, script, XML, and named pipe.