[GitHub] incubator-metron pull request #276: METRON-363 Fix Cisco ASA Parser

Github user kylerichardson closed the pull request at: https://github.com/apache/incubator-metron/pull/276 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if

[GitHub] incubator-metron pull request #276: METRON-363 Fix Cisco ASA Parser

GitHub user kylerichardson reopened a pull request: https://github.com/apache/incubator-metron/pull/276 METRON-363 Fix Cisco ASA Parser I've rewritten the ASA parser which can be extended, as needed, to new ASA message types by editing the bundled asa patterns file and the static

Re: [DISCUSS] Improving quick-dev

Really looking forward to dockerized Metron. Thanks ahead. On Wednesday, 19 October 2016, Kyle Richardson wrote: > Sorry, I'm a bit late to the party on this one :). > > +1 on the four builds Nick described. Each would be useful and purpose > built. > > I like the

[GitHub] incubator-metron issue #308: Metron-498 Grok patterns are now read from zook...

Github user merrimanr commented on the issue: https://github.com/apache/incubator-metron/pull/308 Can't argue with you there, that is a better name. Thanks for all the great suggestions @mattf-horton. --- If your project is set up for it, you can reply to this email and have your

Re: [DISCUSS] Improving quick-dev

Sorry, I'm a bit late to the party on this one :). +1 on the four builds Nick described. Each would be useful and purpose built. I like the idea of using Docker, especially for local development and quick testing. Has anyone explored this? I'm envisioning very specific containers so you could

Re: [MENTORS] Release Maturity

I'm +1 on a meeting to discuss the backlog and would suggest, to be considered, each JIRA should have a clear description. I think that 72 hours is good for final adds to an upcoming release. I personally like the idea of having more visibility on which JIRAs are "up next" to help me figure out

Re: [MENTORS] Release Maturity

IMO, such a meeting is not necessary. Care must also be taken to make no decisions in these meetings where the entire community doesn't have a say - even if they are allowed to attend. Timezones and other priorities make such meetings difficult for many. Options can be discussed and presented to

[GitHub] incubator-metron issue #310: METRON-495: Upgrade Storm to 1.0.x

Github user ottobackwards commented on the issue: https://github.com/apache/incubator-metron/pull/310 I spent some time on this yesterday. I do not have a lot of Kafka/ZK/Storm experience - but I was hoping for something to stand out Unfortunately that was not the case. Can

[GitHub] incubator-metron issue #276: METRON-363 Fix Cisco ASA Parser

Github user kylerichardson commented on the issue: https://github.com/apache/incubator-metron/pull/276 Whew, got the CI build to finally pass. All integration and unit tests are passing. I've also re-testing in the single node vm environment I described above. --- If your project

[DISCUSS] Build Log Usability

The Metron build logs contain a great deal of information, including a large number of warnings / exceptions that do not result in test failures but still fill the log.  This makes troubleshooting test/build issues difficult.  For example - the travis ci log for PR #276’s recent failure doesn’t

[GitHub] incubator-metron pull request #315: METRON-464: Force co-location of all Met...

GitHub user dlyle65535 opened a pull request: https://github.com/apache/incubator-metron/pull/315 METRON-464: Force co-location of all Metron components Now the Ambari Add Service will show an error in the case that: a) The Metron Parsers service is not deployed with the

[GitHub] incubator-metron issue #308: Metron-498 Grok patterns are now read from zook...

Github user mattf-horton commented on the issue: https://github.com/apache/incubator-metron/pull/308 Ah, that makes sense -- although I would have called it "timestampFieldName" :-) +1. I think it's ready to go, and a great piece of work! Thanks for all your patience

[GitHub] incubator-metron pull request #308: Metron-498 Grok patterns are now read fr...

Github user mattf-horton commented on a diff in the pull request: https://github.com/apache/incubator-metron/pull/308#discussion_r84110876 --- Diff: metron-platform/metron-parsers/src/main/java/org/apache/metron/parsers/bolt/ParserBolt.java --- @@ -181,7 +185,8 @@ public void

[GitHub] incubator-metron issue #305: METRON-403 Bro Elasticsearch index item fails w...

Github user james-sirota commented on the issue: https://github.com/apache/incubator-metron/pull/305 +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or

Re: [DISCUSS] Build Log Usability

Hi Otto, Good point. One of the practices I'd like to see is to suppress any exception/error output in tests when it's expected. Thanks! -D... On Wed, Oct 19, 2016 at 8:18 AM, Otto Fowler wrote: > The Metron build logs contain a great deal of information, including