2017-05-26 05:38 AM
Hi All!
I should create a new custom #netwitness log parsers for a database from syslog, but the format is like XML, so the #esi tool can not cope with the <> characters.
Log Sample:
May 25 07:21:32 db db: <ROW><DB_NAME>db045</DB_NAME><ACTION_NAME>LOGOFF</ACTION_NAME><RETURN_CODE>0</RETURN_CODE>
May 25 07:21:32 db db: <ROW><DB_NAME>db045</DB_NAME><ACTION_NAME>LOGON</ACTION_NAME><RETURN_CODE>0</RETURN_CODE>
I set to bold the variables we need to parse. The other part of the log is static. Is there a way to do this?
Thank You, Erika
2017-05-27 09:25 AM
2017-05-30 04:07 AM
Thank You Arthur,
in this case will the ESI tool parse the event?
I created a parser, which looks fine in the ESI tool, but the log events are not parsed. I put the xml and the data sample as well (I could not attache ). Maybe you could have a look at it.
Thank You, Erika
May 25 07:21:32 oracle oracle: <ROW><DB_NAME>db046</DB_NAME><ACTION_NAME>LOGON</ACTION_NAME><RETURN_CODE>0</RETURN_CODE>
May 25 07:21:32 oracle oracle: <ROW><DB_NAME>db046</DB_NAME><ACTION_NAME>LOGOFF</ACTION_NAME><RETURN_CODE>0</RETURN_CODE>
<!--SA=True-->
<HEADER
id1="HDR1"
id2="HDR1"
content="<hmonth><hday><htime> oracle oracle: <<ROW><<DB_NAME><db_name><<DB_NAME><<ACTION_NAME><messageid><<!payload:$START>"/>
<MESSAGE
id1="LOGON"
id2="LOGON"
eventcategory="1401040000"
content="<hmonth><hday><htime> oracle oracle: <<ROW><<DB_NAME><db_name><<DB_NAME><<ACTION_NAME><messageid><</ACTION_NAME><<RETURN_CODE><result><</RETURN_CODE>"/>
2017-05-31 05:28 AM
Hi all, now it is working. There was a < missing from the header. So the correct header is:
content="<hmonth><hday><htime> oracle oracle: <<ROW><<DB_NAME><db_name><<DB_NAME><<ACTION_NAME><messageid><<<!payload:$START>"/>
Thank You Arthur for the help.