KBI 310617 Issue Addressed: User Data Does Not Save Properly If File Log Entries Span Multiple Lines
Issue Addressed in Argent for Compliance 3.1A-1308-A and above
Monday, 29 Jul 2013
Argent for Compliance engine only parsed the first line for user data field. All following lines were treated as part of description field
Some log file puts date/time at one line and put some other information on separate lines. For example,
In order to parse this type of log, the keyword ‘NewLineAfterTimeStamp = Yes‘ is used. The sample also uses ‘CombineLeftRightText = Yes‘ because the timestamp column is in the middle of log line.
Note: Column ‘USER_DATA_5‘, ‘USER_DATA_6‘, ‘USER_DATA_7‘ and ‘USER_DATA_8‘ does not come from the line having the timestamp.
In Argent Advanced Technology 3.1A-1308-A or above, these USER_DATA columns won’t be parsed as all the lines after line of timestamp are simply cascaded into the description field.
As a result, any criteria using any of these USER_DATA columns won’t be correctly calculated.
Upgrade to Argent Advanced Technology 3.1A-1308-A and above.