Re: [DISCUSS] Build broken due to transitive dependencies

Hmm, 0.4.1 built fine for me. Jon On Mon, Oct 2, 2017 at 10:44 AM Casey Stella wrote: > Ok, the build is broken in metron-config due to some transitive changes > that happened in npm-land: > > [INFO] > > /Users/cstella/Documents/workspace/metron/fork/incubator-metron/metron-interface/metron-con

Re: SUM aggregator not working?

You're right, with ES 5 we can use periods directly instead of transforming them in indexing to colons (actually, this feature was reintroduced sin 2.4 ). I outlined this as a benefit in the original JIRA

Re: Quick Dev

I say we kill it and repoint the site. That will give us one less thing to upgrade to centos 7 as well. Jon On Fri, Oct 6, 2017, 08:27 Justin Leet wrote: > So what are we going to do with Quick Dev? I'm pretty sure everybody's > been using full dev for awhile now (and quick dev is probably br

Re: who is having problems installing?

To generalize a bit, I think it would be helpful to have a single or series of recordings, write-ups, or even just pointers to some good high-level docs to introduce people to each component used in Metron, and then a description of how it's used in the Metron environment. I know I spend a lot of

Re: who is having problems installing?

hem more consumable. The problem > with videos is that they become out of date very quickly and it's a lot of > effort to re-record them. > > Thanks, > James > > 06.10.2017, 11:05, "zeo...@gmail.com" : > > To generalize a bit, I think it would be hel

Re: Metron 0.4.2 release date

As of right now I'm not aware of any discussions regarding a next release, and I believe the METRON-777 features are at least a few months out from being reviewed and merged in (There is a fair amount of work in chunking it up to be reviewed, then work to review and merge it in). ES 5.x is also in

Re: Metron 0.4.2 release date

Elasticsearch, I am looking for the support from the client side > rather than a full Metron mpack that includes ES 5.x. As long as Metron > Alert-UI and indexing can support ES 5, I am fine. Is that the scope of > Metron-939? > > Cheers, > Ali > > On Mon, Oct 9, 2017 at 1

Re: Suricata parser

I would love to see one, and if it doesn't exist in the next few weeks I'm going to take a stab at it. Jon On Mon, Sep 25, 2017, 09:49 Carolyn Duby wrote: > > Is anyone working on a Suricata parser? > > https://suricata-ids.org/ > > > I was not able to find an enhancement request for it. > > Th

Re: new committer: Raghu Mitra

Congratulations, Raghu! Jon On Fri, Oct 20, 2017, 12:11 Simon Elliston Ball wrote: > Congratulations Raghu. Well deserved with all that awesome UI work that’s > coming in. > > Simon > > > On 20 Oct 2017, at 17:10, James Sirota wrote: > > > > > > > > The Project Management Committee (PMC) for A

[DISCUSS] Release Process Update

Today I was poking around the Metron site and documentation, and I noticed that the site-book's travis build status image is pointing to master for all of our releases. We should probably update the release process to pin this to

Re: [DISCUSS] Release Process Update

MEs to > make > > them > > suitable for site-book. At that point it's just gone entirely. from > > the > > next release. > > > > Doesn't solve the problem of prior releases (assuming we care enough > > to do > > anything). >

Re: [DISCUSS] Release Process Update

5 > Rational in > https://issues.apache.org/jira/browse/METRON-1278 > > Thanks, > --Matt > > On 10/24/17, 5:37 AM, "zeo...@gmail.com" wrote: > > Hmm, I kind of like it as a historical validation/confirmation of build > success, but I c

Re: [DISCUSS] - Remove Kibana

I'm probably okay with marking it as deprecated in two releases (after moving to 5.x, thus not really helping with the migration), but it depends a lot on increased functionality for the metron alerts UI IMO. Jon On Wed, Nov 1, 2017 at 12:51 PM Otto Fowler wrote: > I don’t think we should remov

Re: [DISCUSS] Upcoming Release

I agree, I think it's very reasonable to move in line with Nick's proposal. I would also suggest that we outline what the target versions would be to add in the METRON-777 components, since it has been functional for a very long time but not reviewed and has some really rockstar improvements. Jon

Re: Committing to the metron-bro-plugin-kafka repo

b.com/JonZeolla/metron-bro-plugin-kafka/pull/1>. Jon On Mon, Sep 18, 2017 at 11:52 AM Nick Allen wrote: > Nice! Looks good to me. > > > > > > > On Mon, Sep 18, 2017 at 11:35 AM zeo...@gmail.com > wrote: > > > Okay, I took a stab at it this morning, ca

Re: Committing to the metron-bro-plugin-kafka repo

ed to do before we start accepting enhancements? > > Thanks for the update and all the hard work, Jon. > > On Mon, Nov 6, 2017 at 10:02 PM, zeo...@gmail.com > wrote: > > > Sorry for the delay here - I pushed this out tonight (link > > <https://github.com/apache/met

Re: Committing to the metron-bro-plugin-kafka repo

Add a sub-module pointing to the repo and ensure that the Ansible > deployment to Full Dev can deploy Bro with the Kafka plugin > > > > > > On Tue, Nov 7, 2017 at 9:19 AM, zeo...@gmail.com wrote: > > > So here's an update on this, and I'm looking for any suggest

Re: Committing to the metron-bro-plugin-kafka repo

ugin to Full Dev from the new repository > > What do you think? > > > > On Wed, Nov 8, 2017 at 11:00 AM zeo...@gmail.com wrote: > > > So, here's my argument against the sub-module approach: > > - If we add a sub-module into apache/metron then the way you clone fro

Re: Committing to the metron-bro-plugin-kafka repo

afka. Jon On Wed, Nov 8, 2017 at 2:57 PM zeo...@gmail.com wrote: > I'm not strongly against it, but my biggest interest was not wasting time > doing something that will get ripped out fairly quickly. That said, > discussing this is taking more time than doing the work, and I should h

<    1   2   3