Bug 1627944

Summary:	support for endmsg.regex
Product:	[Fedora] Fedora	Reporter:	Rich Megginson <rmeggins>
Component:	rsyslog	Assignee:	Jiří Vymazal <jvymazal>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	28	CC:	dapospis, dkopecek, jlieskov, jvymazal, lkundrak, mah.darade, qe-baseos-security, rmeggins, rsroka, tosykora
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rsyslog-8.38.0-1.fc28 rsyslog-8.38.0-1.fc27 rsyslog-8.38.0-1.fc29	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1627943	Environment:
Last Closed:	2018-10-16 11:38:49 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1627941, 1627943

Description Rich Megginson 2018-09-11 23:35:39 UTC

+++ This bug was initially created as a clone of Bug #1627943 +++

+++ This bug was initially created as a clone of Bug #1627941 +++

Description of problem:
rsyslog imfile has support for startmsg.regex for parsing multiline logs.  This is primarily for the purpose of parsing multiline stacktraces in the form:

firstmessage
    secondline
    thirdline
    ...
secondmessage

That is, the first segment of the message is an unindented line, and all subsequent lines that follow that are indented are segments of the same message.

However, for the docker json-file and crio log file case, the marker which denotes the complete message comes at the end e.g. with crio

date stdout P start of message
date stdout P  middle of message
date stdout F  end of message

The F means this is the line which contains the final part of
the message. The fully assembled message should be
start of message middle of message end of message.
endmsg.regex="^[^ ]+ stdout F " will match.  startmsg.regex does not help in this case.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Rich Megginson 2018-09-19 20:42:27 UTC

The fix is in rsyslog 8.38.0 - this bz will be fixed when rsyslog is rebased

Comment 2 Jiří Vymazal 2018-10-10 11:26:51 UTC

Commit:
=======
https://src.fedoraproject.org/rpms/rsyslog/c/f2ed0514cf09a92e466841e236bcb1f72d501796?branch=f28

Comment 3 Fedora Update System 2018-10-10 11:36:18 UTC

rsyslog-8.38.0-1.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-81c473ed78

Comment 4 Fedora Update System 2018-10-10 11:36:35 UTC

rsyslog-8.38.0-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-3b32e6c84d

Comment 5 Fedora Update System 2018-10-10 11:36:53 UTC

rsyslog-8.38.0-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-4e4c9fcfcd

Comment 6 Fedora Update System 2018-10-10 15:50:35 UTC

rsyslog-8.38.0-1.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-81c473ed78

Comment 7 Fedora Update System 2018-10-10 23:20:01 UTC

rsyslog-8.38.0-1.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-3b32e6c84d

Comment 8 Fedora Update System 2018-10-10 23:26:57 UTC

rsyslog-8.38.0-1.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-4e4c9fcfcd

Comment 9 Fedora Update System 2018-10-16 11:38:49 UTC

rsyslog-8.38.0-1.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.

Comment 10 Fedora Update System 2018-10-19 15:49:44 UTC

rsyslog-8.38.0-1.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.

Comment 11 Fedora Update System 2018-10-30 17:23:41 UTC

rsyslog-8.38.0-1.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.