Parse Grok after Multiline event capture truncates the multiline event. #10620
-
I have a Python Stacktrace that I am capturing from the log file using the 'file ' source.
The multi-line config looks like this. Basically says "to group all lines that don't start with a TIMESTAMP with the last line that did in a single event"
Using this, I am able to capture the event successfully, the event looks like this :
However when I pass it through another GROK layer (to extract to loglevel, date, exception type, etc..) I loose the date after the newline.
post which my event looks like
As you can see, the message filed is reduced to only the first line of the multi-line event. I guess this is something to do with escaping \n in the msg field but since the msg is generated internally in the pipeline, Vector should handle this ?? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 4 replies
-
could be avoided if we could treat message as a raw string. Either a config to ingest log lines as Raw string or a remap transform to convert a string to raw string. |
Beta Was this translation helpful? Give feedback.
-
Hi @atibdialpad ! It looks like you can use regex classes to enable multi-line matching behavior:
It looks like |
Beta Was this translation helpful? Give feedback.
Hi @atibdialpad !
It looks like you can use regex classes to enable multi-line matching behavior: