i have an application that has an bug in the logging, but i need to workaround it.
Dec 10 13:21:09 abc: request: Session: ****** User-Agent: ******** Content-Length: **** Content-Type: ********* positionDec 10 13:22:09 abc: reply: Session: ******** Date: 2014-12-09T14:33:09Z Range: ***** Scale: **** Content-Type: **** Content-Length: *** position: ******
this are two events. in the request event it writes at the and in the beginning of the replay message "position:"
i tried already with seed to remove the "position:" - but it is valid in the replay event and it would remove this one as well.
i guess i need to do it via transforms.conf as it needs to be done before we check for the timestamp, otherwise the full line will be used to the event to detect the timestamp.
i tried to add via transforms a line break, but did not work.
[position-fix] REGEX = (?m)^(.*)position.* FORMAT = $1\n position1$2 DEST_KEY = _raw
thanks a lot for any advice.
The following should remove the stray "position"
REGEX = (.*)position(?=[^:])(.*) FORMAT = $1\n$2 DEST_KEY = _raw
your suggestion doesn't work 😞
[abc_xyzprovider] BREAK_ONLY_BEFORE = abc: MAX_TIMESTAMP_LOOKAHEAD = 15 NO_BINARY_CHECK = 1 TIME_FORMAT = %b %d %H:%M:%S TRANSFORMS-positionfix = position-fix TZ = UTC pulldown_type = 1
[position-fix] REGEX = (.)position(?=[^:])(.) FORMAT = $1\n$2 DEST_KEY = _raw
Still the "position" element (which belongs to the last event) is shown in the next event.
Your REGEX line is not the same as mine. The asterisks are critical. If you want "position" to remain with the first event, try this regex:
Sorry, copy & paste must have missed something. But also with correct regex the result is:
\nDec 9 14:33:09 abc: reply:
Sideeffect is also that everything that comes after this first line from the event is somehow deleted.