Bug 1627944 - support for endmsg.regex
Summary: support for endmsg.regex
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: rsyslog
Version: 28
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jiří Vymazal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1627941 1627943
TreeView+ depends on / blocked
 
Reported: 2018-09-11 23:35 UTC by Rich Megginson
Modified: 2018-11-20 07:43 UTC (History)
10 users (show)

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:
Clone Of: 1627943
Environment:
Last Closed: 2018-10-16 11:38:49 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github rsyslog rsyslog pull 3014 0 None None None 2018-09-11 23:35:38 UTC

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 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.


Note You need to log in before you can comment on or make changes to this bug.