New test SystemEDGE log file monitor not working

book

Article ID: 76382

calendar_today

Updated On:

Products

CA Systems Performance for IM (SystemEdge) CA eHealth

Issue/Introduction

  1.  We have created a SystemEDGE log file watcher.
  2.  If we put a keyword like "test" then alarm is getting generated.
  3.  If we then add a match criteria such as "Database has crashed" to the same file, and create a new log file monitor the alarm is not getting generated. 

Environment

Release: SYSEDG99000-12.9-Stand Alone SystemEDGE Agent
Component:

Resolution

When testing new Log File monitor entries keep the following in mind:
  1. The first poll cycle will only stat the log for file size.
  2. Once the monitor goes active any new lines after the initial file stat are monitored. Lines present before the file stat are ignored.
  3. For the purposes of testing log file monitoring, create and initialize the log file monitor entry BEFORE populating the log with test data.
  4. You can view the sysedge.mon file for all defined monitors.
W2k8\12\16
C:\Users\Public\CA\SystemEDGE\port#\sysedge.mon

UNIX
/opt/CA/SystemEDGE/config/port#/sysedge.mon


       5. A monitor is not initialized until it reads as active:

logfilemon {
  1234
  ""
  "c:\test.txt"
  "error"
  ""
  0x1
  active
  1
  major
  45
}