I've been working on parsing files with long (multi-line) entries. To process the file I've set up a Data Source that uses "year" as the line break. What I wanted to know is when working on the parsing patterns for the File Type, does it know to interpret the line break defined by the Data Source or does it assume the default line break?
The data type page does not use the the line break rule defined from the sources page. To deal with the multiline events clump the events together and remove any empty lines. Multiline events with which contain new line will need to be reformatted on the Data Types page. For example let's say you were using the following sample data on the Data Types page.
java.lang.RuntimeException: at com.liquidlabs.transport.proxy.PeerHandler.handleRemoteMethodInvocation(PeerHandler.java:282) at com.liquidlabs.transport.proxy.PeerHandler.receive(PeerHandler.java:128) at com.liquidlabs.transport.MultiReceiver.receive(MultiReceiver.java:36) ... 10 more Caused by: java.io.FileNotFoundException: ../../work/LogServer_SERVER_/neil@neilavery.com/_SERVER_/10.28.1.163 (Is a directory) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.(FileOutputStream.java:221) at com.liquidlabs.logserver.LogMessage.getOutputStream(LogMessage.java:121) at com.liquidlabs.logserver.LogMessage.write(LogMessage.java:84) ... 11 more
This would be broken up into two events. The second event starting where <Exception> begins . This would need to be reformatted to look like this:
2014-11-13 09:19:27,490 INFO long-runningMeterService-one-way-1-1869 (proxy.PeerHandler) Task Error:MeterService java.lang.RuntimeException: VScapeRemoteException[stcp://10.28.1.170:11104]=>target[MeterService].method[public abstract void com.logscape.meter.MeterService.handle(java.lang.String,java.lang.String,java.lang.String,java.lang.String)] IllegalArgument[null] ArgCount[ArgLength:4] Cause[java.lang.RuntimeException: java.lang.RuntimeException: at com.liquidlabs.transport.proxy.PeerHandler.handleRemoteMethodInvocation(PeerHandler.java:282) at com.liquidlabs.transport.proxy.PeerHandler.receive(PeerHandler.java:128) at com.liquidlabs.transport.MultiReceiver.receive(MultiReceiver.java:36) ... 10 more Caused by: java.io.FileNotFoundException: ../../work/LogServer_SERVER_/neil@neilavery.com/_SERVER_/10.28.1.163 (Is a directory) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.(FileOutputStream.java:221) at com.liquidlabs.logserver.LogMessage.getOutputStream(LogMessage.java:121) at com.liquidlabs.logserver.LogMessage.write(LogMessage.java:84) ... 11 more
This doesn't affect the File Ingestion in any way. The new line rules are not used on the Types page since multiple tags and explicit paths can be defined in the DirMask field.
__________________
Page 1 of 1 sorted by
Logscape Support -> logscape -> Parse testing of Data Type that uses Data Source with non-default Line Breaking
