Red Hat Bugzilla – Bug 535725
Logfile parser ignores lines where severity is not surrounded by spaces
Last modified: 2013-09-01 05:59:15 EDT
Suppose you have a log line like this:
[2009.08.27-09:46:34] (INFO ) Log4J Log Level
Our logfile reader allows to set the date format to '['yyyy.MM.dd-hh:mm:ss']' to match the date part, but matching will fail on '(INFO )', as the matcher expects that the severity is surounded by space.
Log4JLogEntryProcessor.REGEX == "(.*) (TRACE|DEBUG|INFO|WARN|ERROR|FATAL) (.*)"
We should perhaps allow (via some %x expressions for users to completely compose their entry format )
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-2391
Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs.
new = Tracking + FutureFeature + SubBug
making sure we're not missing any bugs in rhq_triage
master commit f9a99a4e1f83f3bc74b4fae5a8515914f69b15a5
I've updated our logEntry pattern handling to allow for bracket or paren
delimiters, with optional spacing, around the severity. So, the
following should all now match, for example:
2012-01-05 11:42:13,607 INFO [org.foo.Baz] my message
2012-01-05 11:42:13,607 [INFO] [org.foo.Baz] my message
2012-01-05 11:42:13,607 ( INFO ) [org.foo.Baz] my message
Bulk closing of items that are on_qa and in old RHQ releases, which are out for a long time and where the issue has not been re-opened since.