This table lists identifiers of alerts raised by the UNIX/Linux Resource Monitor.
Alert Identifier | Description |
_CPU <cpu-resource-name> | ULRM raises an alert when CPU utilization exceeds the threshold for a period of time. The first time ULRM polls and finds utilization exceeds the threshold, ULRM shortens the polling interval to check utilization more frequently and starts counting the violations. ULRM raises an alert after the fifth consecutive violation. Then the polling interval is reset to polling interval from resource policy and the violation count is set to zero. If during shortened polling interval CPU utilization falls below the threshold, ULRM resets the polling interval to value set in the resource policy and resets the violation count to zero. |
_CriticalProcess <critical process resource name> | The indicated process is not in the expected state. The critical process resource name is the name of the process. |
_FileSystems <file systems resource name> | The amount of free space on the indicated file system has fallen below the threshold defined in the resource policy. The file systems resource name is the name of the file system on the monitored system. |
_MemoryUsage | ULRM raises an alert when memory utilization exceeds the threshold for a period of time. The first time ULRM polls and finds utilization exceeds the threshold, ULRM shortens the polling interval to check utilization more frequently and starts counting the violations. ULRM raises an alert after the fifth consecutive violation. Then the polling interval is reset to polling interval from resource policy and the violation count is set to zero. If during shortened polling interval memory utilization falls below the threshold, ULRM resets the polling interval to value set in the resource policy and resets the violation count to zero. |
_LongProcessUsage | A long running process has accumulated more CPU time than the threshold defined in the resource policy. The process is identified in the alert text and the alert qualifier. |
_LogFile <log file resource name> | A message was written to the identified log file that matched the pattern defined in the resource policy. The log file resource name is the name of the log file that contains the message. |
_ULRM_CustomAction_failed | The UNIX/Linux Resource Monitor cannot execute a custom action. The script or program file may not exist or may not have execute permission. |
_ULRM_LogFile_access_error | The UNIX/Linux Resource Monitor cannot monitor a log file specified by the resource policy because the UNIX/Linux Resource Monitor could not read the log file. |
_ULRM_LogFile_filter_error | The UNIX/Linux Resource Monitor cannot monitor a log file specified by the resource policy because the UNIX/Linux Resource Monitor could not save the message filter definition. |
_ULRM_Memory_policy_error | The resource policy contains memory resource monitoring and the policy is used on a SOLARIS system. Memory monitoring is not possible on SOLARIS systems. |
_ULRM_policy_read_error | Operations Sentinel distributed a policy to the UNIX/Linux Resource Monitor and the UNIX/Linux Resource Monitor could not process the policy. If a policy was active prior to the distribution of the new policy, the UNIX/Linux Resource Monitor continues to use the old policy. |
_ULRM_policy_update_error | Operations Sentinel distributed a policy to the UNIX/Linux Resource Monitor and the UNIX/Linux Resource Monitor could not update the current policy with information from the new policy. The UNIX/Linux Resource Monitor continues to use the old policy without updates from the distributed policy. |
_ULRM_PolicySave_failed | Operations Sentinel distributed a resource policy to the UNIX/Linux Resource Monitor and the UNIX/Linux Resource Monitor could not save the resource policy on the monitored system. |