[GitHub] metron issue #586: METRON-508 Expand Elasticsearch templates to support the ...

Github user nickwallen commented on the issue: https://github.com/apache/metron/pull/586 Actually, I meant the integration tests. The stuff under `metron-platform/metron-integration-test/src/main/sample/data/bro`. --- If your project is set up for it, you can reply to this email and

[GitHub] metron issue #531: METRON-854 create dhcp dump parser

Github user nickwallen commented on the issue: https://github.com/apache/metron/pull/531 I am a -1 on merging this PR. It relies on a forked version of the original sensor which limits its general usefulness. I have concerns about maintaining and supporting that fork long-term.

[GitHub] metron issue #586: METRON-508 Expand Elasticsearch templates to support the ...

Github user simonellistonball commented on the issue: https://github.com/apache/metron/pull/586 Looks like there are some good unit tests, though maybe not for every new type you mention, or that could come in. Seems like decent coverage though. I wonder, is it worth adding something

Remember remember the 29th of April — Matt’s instructions for handling the github rename

Resending this, so that will land on top and be more findable for folks. ——— A brief guide to changing our github remotes from “apache/metron-incubating” to “apache/metron”  [also applies to “incubator-metron-bro-plugin-kafka” → “metron-bro-plugin-kafka” ]  Hey all, as a result of

[GitHub] metron issue #586: METRON-508 Expand Elasticsearch templates to support the ...

Github user JonZeolla commented on the issue: https://github.com/apache/metron/pull/586 Didn't I do that? --- 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,

[GitHub] metron issue #586: METRON-508 Expand Elasticsearch templates to support the ...

Github user nickwallen commented on the issue: https://github.com/apache/metron/pull/586 Still need to review, but this is a great addition Jon. What pairs nicely with this is to expand the unit tests for the Bro parser to test the other log types that you include in this PR

[GitHub] metron issue #558: METRON-811: Enforce Maven Version in Top Level POM

Github user ottobackwards commented on the issue: https://github.com/apache/metron/pull/558 +1 by inspection, thanks for the contribution --- 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

[GitHub] metron issue #550: METRON-890: Intermittent unit test errors in shutting dow...

Github user ottobackwards commented on the issue: https://github.com/apache/metron/pull/550 What is the status of this PR? --- 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

[GitHub] metron issue #531: METRON-854 create dhcp dump parser

Github user ottobackwards commented on the issue: https://github.com/apache/metron/pull/531 @JonZeolla does this relate to your latest PR (#586)? What is the status of this pr? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[GitHub] metron issue #528: METRON-838 Incorrect set of ts in FireEye parser

Github user ottobackwards commented on the issue: https://github.com/apache/metron/pull/528 Hi, What is the status of this PR? --- 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 ena

[GitHub] metron issue #526: Metron-846: Add E2E tests for metron management ui

Github user ottobackwards commented on the issue: https://github.com/apache/metron/pull/526 What is the status of this PR? --- 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

[GitHub] metron issue #481: METRON-322 Global Batching and Flushing

Github user ottobackwards commented on the issue: https://github.com/apache/metron/pull/481 What is the status of this PR? --- 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

[GitHub] metron issue #439: METRON-571 add stellar external functions feature - code ...

Github user ottobackwards commented on the issue: https://github.com/apache/metron/pull/439 Hi, is there any update to the status of this PR? --- 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 t

[GitHub] metron issue #425: METRON-609 Enhance Mpack to handle single-node and small-...

Github user ottobackwards commented on the issue: https://github.com/apache/metron/pull/425 What is the status of this? How is it related to METRON-608? --- 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 doe

[GitHub] metron issue #408: METRON-608 Mpack to install a single-node test cluster

Github user ottobackwards commented on the issue: https://github.com/apache/metron/pull/408 What is the status of this PR? --- 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

integration testing framework

Hi All, I have been looking for an easy way to test metron in the development environment. Using "full-dev-environment" is a bit painful because you each time need to copy artifacts etc. I tried to understand integration testing framework but it a little complex for a newbie. Would you guys descri