[
https://issues.apache.org/jira/browse/METRON-647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15798449#comment-15798449
]
Kyle Richardson commented on METRON-647:
----------------------------------------
[~justinleet] If you have time today, please feel free. Unfortunately, I won't
be able to get to it until tonight or maybe tomorrow.
When I looked into it a bit this morning it seems like, for
GrokWebSphereParserTest, it isn't going to be a quick fix. It turns out that
the grok pattern being used only expects the month and day in the timestamp of
the syslog messages. We may be able to make it year safe by reusing some of the
code from the BasicAsaParser and SyslogUtils.
Of course, I'm happy to be corrected if there's a quick fix out there that I'm
just not seeing, too.
> Parser unit test failures due to assumed year values
> ----------------------------------------------------
>
> Key: METRON-647
> URL: https://issues.apache.org/jira/browse/METRON-647
> Project: Metron
> Issue Type: Bug
> Reporter: Kyle Richardson
> Priority: Blocker
>
> Unit Tests Failing:
> * BasicAsaParserTest.testIp6Addr:151
> * GrokWebSphereParserTest.testParseLoginLine:60
> * GrokWebSphereParserTest.testParseMalformedLoginLine:151
> * GrokWebSphereParserTest.tetsParseLogoutLine:84
> * GrokWebSphereParserTest.tetsParseMalformedLogoutLine:175
> * GrokWebSphereParserTest.tetsParseMalformedOtherLine:220
> * GrokWebSphereParserTest.tetsParseMalformedRBMLine:198
> * GrokWebSphereParserTest.tetsParseOtherLine:129
> * GrokWebSphereParserTest.tetsParseRBMLine:107
> The issue appears to be the same for all. The original syslog message did not
> include a year (fairly common); however, we have hard coded an assertion
> based on the year the code was written (in our case 2016).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
