Re: [DISCUSS] Moving GeoIP management away from MySQL

Re: extensibility - I am one of those enterprise users who plan to do enrichment using their IPAM data in the next couple of months. However, since the information that I have is a much different format compared to maxmind, my approach was going to make a completely separate HBase enricher. That

Re: Pittsburgh PA Meetup

he evening starting around 7pm. Jon On Fri, Nov 4, 2016 at 1:16 PM James Sirota wrote: > Excellent. Thanks for setting that up, John. There are additional metron > Meetups that will be announced soon. > > 04.11.2016, 03:50, "zeo...@gmail.com" : > > Hi everyone, ju

Re: [VOTE] Reporting Issues Wiki

gt; -Kyle > >>> > > >>> > > On Jan 6, 2017, at 7:53 AM, JJ Meyer wrote: > >>> > > > >>> > > +1 (non-binding) > >>> > > > >>> > > What do you think about changing `*DO NOT FILE A JIRA, DO NOT

Re: [PROPOSAL] up-to-date versioned documentation

s. > > > > I fiddled with trying to do a POC, and unfortunately concluded > (again) > > that I don’t really know maven very well :-) > > Are there any maven experts out there who would be willing to give me > some > > pointers (offline) on how to

Build failing

The build has been showing as failing for a little while now. I know we recently updated the language around Merge Requirements , but if I recall properly our current issue is si

Re: [VOTE] Release Process Documentation

-1 (non-binding). There appears to be a minor oversight where it goes from Step 9 to Step 14. Jon On Fri, Jan 20, 2017 at 11:56 AM James Sirota wrote: > The document is available here: > https://cwiki.apache.org/confluence/display/METRON/Release+Process > > and is also pasted in this email for

Re: [DISCUSS] Error Indexing

As someone who currently fills the platform engineer role, I can give this idea a huge +1. My thoughts: 1. I think it depends on exactly what data is pushed into the index (#3). However, assuming the errors you proposed recording, I can't see huge benefits to having more than one dashboard. I w

Re: Build failing

ry.java:165) at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75) Jon On Thu, Jan

Re: [DISCUSS] Error Indexing

ailures are messages that explicitly failed stellar validation/schema enforcement. There should be relatively few of the second type. With respect to 3, why do you want the error hashed? Why not just search for the error text? Thanks, James 20.01.2017, 14:01, "zeo...@gmail.com" : &

Re: [DISCUSS] Error Indexing

failed validation" > hashing this error string will always result in the same hash. Why not > just use the actual error string? Can you provide an example where you > would use it? > > Thanks, > James > > 23.01.2017, 16:29, "zeo...@gmail.com" : > > For

Re: [DISCUSS] Error Indexing

t; > >4. Write a completely new topology with multiple spouts (1 for each > > >error type listed above) that all feed into a single > > BulkMessageWriterBolt. > > > 1. Good because the current topologies would not need to change > > > 2

Mailing Lists on Website

Is there a reason why we don't have any Metron-specific mailing lists advertised on the Metron apache page under Mailing Lists ? I would have expected to see them there, but since I don't I'm wondering if there was an explicit decision to not include

Reporting Issues Wiki

ng list, as shown below: Hi! This is the ezmlm program. I'm managing the iss...@metron.incubator.apache.org mailing list. Acknowledgment: I have added the address zeo...@gmail.com to the issues mailing list. Welcome to iss...@metron.incubator.apache.org! Am I missing something here? T

Re: [DISCUSS] Error Indexing

assed along with no error thrown (only logged). Everywhere > else I'm having trouble identifying specific fields that should be hashed. > Would hashing the message in every case be acceptable? Do you know of a > place where we could hash a field instead? On the topic of excepti

Re: Reporting Issues Wiki

> > James or David, has issues@ for the metron project been set up > > differently than the Apache norm, so it is in fact an appropriate place > for > > non-committer users to report problems with Jira? > > > > Thanks, > > --Matt > > > >

Re: [DISCUSS] Error Indexing

nge things. Any opinion on a hashing algorithm? On Wed, Jan 25, 2017 at 9:37 PM, zeo...@gmail.com wrote: > Although hashing the whole message is better than nothing, it misses a lot > of the benefits we could get. > > While I'd love to have consistency for this field across all o

Re: Reporting Issues Wiki

; instead of issues@. David, we have the ability to administer a few > permissions for the Metron JIRA, so people should email us first before > trying INFRA. > > On Thu, Jan 26, 2017 at 7:43 AM, zeo...@gmail.com > wrote: > > > Okay. Since that wiki page has been voted

Cannot close JIRAs I didn't originally request

I assigned a JIRA (METRON-354 ) to me that was reported by someone else, and it appears that I don't have the permissions to close it. For clarity, I didn't have access to close it before I assigned it to myself either. Would someone be willing to

Re: [DISCUSS] Next Release (0.3.1) Content

I haven't had a chance to look through the unresolved JIRAs but I did want to mention a few quick things. First, when we released 0.3.0 and dropped the BETA flag, one of the things that was discussed was putting together a method of documenting upgrades from one version to the next. As one of the

Re: [DISCUSS] Next Release (0.3.1) Content

gt; > > So, I agree with the Upgrading.md and I was going to submit a PR at least > > to describe the the changes to indexing configurations that I made during > > the 3.0.1 release. > > > > > > On Thu, Jan 26, 2017 at 10:50 PM, zeo...@gmail.com > > wrote:

Re: [DISCUSS] Gratuating to Apache Top Level Project

I agree On Fri, Jan 27, 2017 at 3:37 PM Otto Fowler wrote: > +1 > > > On January 23, 2017 at 19:09:13, James Sirota (jsir...@apache.org) wrote: > > I think the Apache Incubation was very valuable learning experience for us, > but it seems like we are ready to become a top-level project. We have

Re: [MENTORS] ICLA for non-committer contributions

What Ryan has suggested has happened twice before from memory. We should probably make that clear in the development guide if it isn't already. Jon On Fri, Jan 27, 2017, 5:08 PM Casey Stella wrote: > I should add, each of them should have the same PR title, just different > authors. > > On Fri

Re: [DISCUSS] Contributions with multiple authors and requisite modifications to the development guide

I thought the idea would be to maintain the commit mapping to individuals so things like the GitHub statistics are accurate regarding # of commits, # of lines affected +/-, # of contributors, etc. Jon On Tue, Jan 31, 2017, 12:20 AM Otto Fowler wrote: > I mean multi-author of course > > > On Jan

Re: [DISCUSS] Contributions with multiple authors and requisite modifications to the development guide

gt;> > # Commands: > >> > # p, pick = use commit > >> > # r, reword = use commit, but edit the commit message > >> > # e, edit = use commit, but stop for amending > >> > # s, squash = use commit, but meld into previous commit > >> &

Re: [DISCUSS] Metron Management UI

First off - this is an awesome first take at a management UI and I'm looking forward to messing around with it. Other than skimming some of the dialogue as it comes in I have not been keeping up with the API PR. Should I be able to assume that the UI PR is broken until the API is merged and the U

Re: [DISCUSS] Error Indexing

think sticking with FIPS 140-2 is a solid choice. Jon On Thu, Jan 26, 2017, 11:23 AM zeo...@gmail.com wrote: So one more thing regarding why I think we should throw an exception on a failed enrichment. If we do make something like username a constant field, in cases where that is used to calc

Re: [DISCUSS] Metron Management UI

Ok great, thanks for the feedback Ryan. I'm going to try and get around to playing with this next week if I can. Currently my productivity machine is "in the shop" getting the battery replaced, so I'm playing man down right now. So if we ignore the current API restrictions, here are my MUST have

Re: [Discuss] Improve Alerting

Otto, I think you're thinking of the "Enrich enrichment" dev mailing list thread that Dima started. In that case we chatted about passing through enrichment multiple times while decrementing a TTL field to prevent infinite loops (and drop a message to the error queue if TTL == 0) would work just f

Re: [DISCUSS] Error Indexing

is hash > and how? > > - Dima > > On 02/01/2017 06:23 AM, zeo...@gmail.com wrote: > > After thinking on this for a few days I recant my previous suggestion of > > TupleHash256. It's still a bit early for SHA-3 - no good reference > > implementations/libra

Re: [GitHub] incubator-metron issue #429: METRON-660 [Umbrella] up-to-date versioned docu...

Agreed, sounds good to me. I'm good with it getting merged. Jon On Fri, Feb 3, 2017, 6:31 PM mattf-horton wrote: > Github user mattf-horton commented on the issue: > > https://github.com/apache/incubator-metron/pull/429 > > Hi @JonZeolla , you have good eyes! I missed those cases, whi

Re: Cannot close JIRAs I didn't originally request

ted state for issues. The workflow may > also be why there is no way to specify the reason for the resolution of the > ticket. If we want to make any adjustments to the permissions or workflow, > that will require an INFRA ticket. > > On Thu, Jan 26, 2017 at 8:30 AM, zeo...@gmail.co

Re: [DISCUSS] Metron Management UI

it with Ambari Mpack where new topologies will be monitored? Last thing, should metron-parsers*.jar be split into separate parsers jar in case if among 50 parsers we need to update just one and we want to do that from Metron UI? - Dima On 02/01/2017 11:16 PM, zeo...@gmail.com wrote: > Ok great, thanks

Re: Debuging storm 1.0 article

Thanks, I haven't read it yet, but I added it to my reading list. Do you think it would be a good addition to just below this , this

Unable to build Ansible 2.0.0.2 on macOS using our instructions

Has anybody attempted to set up ansible 2.0.0.2 recently on a fresh mac using brew and the steps we outline here ? I received a new laptop this week, so I ran through some of our setup documenta

Rev additional metron components?

So I was spinning up the 0.3.1-RC3 candidate on my bare metal cluster today and I noticed that when I generated the mpack it still had a version of 1.0.0.0. I double checked and made sure that the mpack existed in the 0.3.0 release

Re: Rev additional metron components?

support the following: > > > > Declare it "not ready" and leave it at 1.0.0.0-SNAPSHOT > > Decide 0.3.0 actually did contain MPack 1.0.0.0 and increment this to > > 1.0.1.0. > > (I'm sure there are other ways as well) > > > > My (weak) prefere

Re: [VOTE] Releasing Apache Metron (incubating) 0.3.1-RC3

-1 (non-binding) due to mpack revision number On Thu, Feb 9, 2017, 2:42 PM Casey Stella wrote: > -1, we didn't rev the mpack. Discussion going on currently as to what > version it should be and Justin volunteered to do the work. I vote we wait > for that and cut another RC. > > On Thu, Feb 9,

Re: [VOTE] Releasing Apache Metron (incubating) 0.3.1-RC3

Would someone mind taking a glance at METRON-708? If possible I would like to get that merged to clean up the documentation a bit before RC4. Jon On Thu, Feb 9, 2017, 2:57 PM zeo...@gmail.com wrote: > -1 (non-binding) due to mpack revision number > > On Thu, Feb 9, 2017, 2:42 PM Cas

Re: Unable to build Ansible 2.0.0.2 on macOS using our instructions

gt; > On Fri, Feb 10, 2017 at 9:26 AM, Casey Stella > > wrote: > > > > > > > Hmm, that's disconcerting. I certainly don't mind documenting the > > > > workaround that you've proposed in METRON-708 > > > > > > > > On

Re: [ANNOUNCE] Metron Apache Community Demo for Metron_0.3.1

Was this recorded like the previous ones ? Unfortunately I had a conflict and wasn't able to make it. Jon On Wed, Feb 8, 2017 at 10:14 AM Casey Stella wrote: > I'd like to show the modifications/enhancements to the flat file loader > >

[DISCUSS] Wiki use and migration of docs

This morning I had an opportunity to watch the video from yesterday's community demo, and there was some really good discussion towards the end about documentation of examples that I wanted to follow up with. For future reference, here is the recording

Re: Unable to build Ansible 2.0.0.2 on macOS using our instructions

> Ansible's 'register' seems to have a length limitation now- that's causing > a problem in ansible_gather_facts ln 133. I'm fixing that with a > combination of curl and grep. > > I'll give it a bit more and see if I can roll through it. > > -D...

Re: Unable to build Ansible 2.0.0.2 on macOS using our instructions

ttable state prior to next week. > > I didn't find anything but the issues I've already mentioned. > > -D... > > On Mon, Feb 13, 2017 at 08:58 zeo...@gmail.com wrote: > > > Are you handling this one under METRON-196? I'd be happy to lend a hand > if >

Re: [GitHub] incubator-metron issue #400: METRON-636: Capture memory and cpu details as a...

To clarify, I'm giving permission to merge and squash everything into a commit from @anandsubbu without attributing anything to me. On Tue, Feb 14, 2017, 1:53 AM anandsubbu wrote: > Github user anandsubbu commented on the issue: > > https://github.com/apache/incubator-metron/pull/400 > >

[DISCUSS] Update Metron Release Documentation

As a follow-up to METRON-716, I would like to suggest that we update our Metron Release documentation to account for the site-book. Specifically, I think that Step 4 and Step 9 need a bit of a refresher. In the most recent build

Re: Cannot close JIRAs I didn't originally request

Thoughts? Just want to put this one to rest, one way or another. Jon On Fri, Feb 3, 2017 at 8:03 PM zeo...@gmail.com wrote: > Has anybody had a chance to look into this and decide whether a change > should be made? This specific incident is no longer an issue but I'd like >

Re: [DISCUSS] Management of Elastic and other index schemas

I think this is a good direction to move things toward - moving indexing templates to be packaged with parsers (using multiple tiered options) that are then merged with the possible enrich fields before getting added to the indexing technology in use. Now, to read the proposal thread... Jon On F

Re: [DISCUSS] Metron Management UI

Well, I think that a UI that does what you show is a huge step forward and I definitely wouldn't want to stop it from getting into the code because of any of the additional features that we are talking about here. That said, I really would like to see the Kafka topic creation as a part of the UI b

Re: [DISCUSS] Metron Management UI

his UI. Would that work, or would you expect to be > creating the parser config before the data was flowing into kafka? In the > later case, we could probably rely on copy-pasted samples to design the > parser, and then auto-create topics if not already existing on parser save. > &g

Re: [DISCUSS][PROPOSAL] Side Loading and Installation of telemetry sources [METRON-258]

Awesome write up and ideas Otto, I also strongly support this idea. As someone who has the development of a few parsers quickly approaching the top of their to do list, I will happily beta test this for you when it's far enough along for that. Until then I will attempt to take a look at your bran

Re: [DISCUSS] Management of Elastic and other index schemas

PR and Simon defining a JSON schema for his CEF > > parser > > >>> PR. I think we need to unify these approaches and then propagate them > > to > > >>> all the parsers. I think what has to happen is the following: > > >>> > > >>&

Re: new committer: Josh Meyer

Congrats Josh! On Thu, Feb 23, 2017, 2:38 PM Otto Fowler wrote: > Nice! Congratulations! > > > On February 23, 2017 at 15:14:42, James Sirota (jsir...@apache.org) wrote: > > The Podling Project Management Committee (PPMC) for Apache Metron > (Incubating) > has asked Kyle Richardson to become a

Re: [DISCUSS] System time vs. Event Time

I'm actually a bit surprised to see METRON-691, because I know a while back I did some experiments to ensure that data was being written to the indexes that relate to the timestamp in the message, not the current time, and I thought that messages were getting written to the proper historical indexe

Re: [DISCUSS] Bro Zeppelin dashboards

Are you assuming only Conn, DNS, and HTTP logs from Bro? Right now I think that's all that is supported by default. I put something together a few months ago to handle all of the default-on Bro logs/fi

Re: Unable to build Ansible 2.0.0.2 on macOS using our instructions

rig. > > On Mon, Feb 13, 2017 at 09:34 zeo...@gmail.com wrote: > > > Ok sounds good. I'm traveling next week, but if the stars align I'll > > review when I get back. > > > > Jon > > > > On Mon, Feb 13, 2017 at 9:08 AM David Lyle wrote: > &

Re: Unable to build Ansible 2.0.0.2 on macOS using our instructions

t done and then publish a reconciled branch with the changes I had to make to get 671 working? -D... On Wed, Mar 1, 2017 at 1:32 PM, zeo...@gmail.com wrote: > Hey Dave, > > Any luck with METRON-196 <https://issues.apache.org/jira/browse/METRON-196 > >? > Happy to help no

Re: [DISCUSS] Wiki use and migration of docs

bump On Sat, Feb 11, 2017 at 2:15 PM zeo...@gmail.com wrote: > This morning I had an opportunity to watch the video from yesterday's > community demo, and there was some really good discussion towards the end > about documentation of examples that I wanted to follow up with.

Re: [DISCUSS] Wiki use and migration of docs

ke to > include > the concept of "cookbook" examples here as well. I think there is overlap > with demos and use cases, but cookbook examples can often be more specific > to a fine grained task. > > Mike > > > On Mon, Mar 6, 2017 at 7:02 AM, zeo...@gmail.com wro

Re: [DISCUSS] System time vs. Event Time

> @Jon, it looks like it is based on system date. > > > > From ElasticsearchWriter.write: > > String indexPostfix = dateFormat.format(new Date()); > > ... > > indexName = indexName + "_index_" + indexPostfix; > > ... > > IndexReques

Re: [DISCUSS] Unique id for messages

; > (Attached email that had similar discussion for error indexing) > > Regards, > RaghuM > > > > -- Forwarded message -- > From: "zeo...@gmail.com" > To: "dev@metron.incubator.apache.org" > Cc: > Bcc: > Date: Wed, 1 F

Re: [VOTE] Cesey Stella for Metron VP

+1 (non-binding) On Mon, Mar 13, 2017 at 6:34 PM James Sirota wrote: > +1 (binding) > > 13.03.2017, 15:34, "James Sirota" : > > This vote is to make Casey Stella our VP after graduation > > > > --- > > Thank you, > > > > James Sirota > > PPMC- Apache Metron (Incubating) > > jsiro

Re: [VOTE] Metron to graduate to TLP

0 (non-binding) On Mon, Mar 13, 2017 at 7:15 PM Ryan Merriman wrote: > +1 (binding) > > > On Mar 13, 2017, at 6:05 PM, Casey Stella wrote: > > > > +1 (binding) > > > >> On Mon, Mar 13, 2017 at 6:37 PM, James Sirota > wrote: > >> > >> +1 (binding) > >> > >> 13.03.2017, 15:37, "James Sirota" : >

Re: Cannot close JIRAs I didn't originally request

> the “Transition Issues” permission in the METRON project in Jira. > > --Matt > > On 2/17/17, 9:37 AM, "zeo...@gmail.com" wrote: > > Thoughts? Just want to put this one to rest, one way or another. > > Jon > > On Fri, Feb 3, 2017 at 8:03 PM

Re: new committer: Matt Foley

Congrats Matt! Jon On Wed, Mar 15, 2017, 12:04 AM Otto Fowler wrote: > Congratulations Matt!!! > > > On March 14, 2017 at 23:41:20, James Sirota (jsir...@apache.org) wrote: > > The Podling Project Management Committee (PPMC) for Apache Metron > (Incubating) > has asked Matt Foley to become a co

Re: Cannot close JIRAs I didn't originally request

k Allen wrote: > > > https://issues.apache.org/jira/browse/INFRA-13660 > > > > > > On Tue, Mar 14, 2017 at 2:03 PM, Nick Allen wrote: > > > >> No apprehension here. Sorry, Jon. I will open the INFRA ticket and > >> respond back to the list. > &

Re: [VOTE] Final Board Resolution Draft

Just for clarity, I assume that with removing the committers we'll also remove the committer affiliation? Since I don't have a CCLA in, I'm not a big fan of having CMU's name on the list. Jon On Wed, Mar 15, 2017 at 4:07 PM P. Taylor Goetz wrote: > A few things that should be corrected: > > -

Re: new committer: Jon Zeolla

Thank you everyone, I'm very excited to be a part of the team. Jon On Wed, Mar 15, 2017, 7:25 AM Kyle Richardson wrote: > Welcome Jon and Matt! Well deserved. Glad to have the opportunity to > continue working with you both. > > -Kyle > > > On Mar 14, 2017, at 11:57 PM, Otto Fowler > wrote: >

Re: Cannot close JIRAs I didn't originally request

Thanks Anand! Things seem to be working as expected. Jon On Fri, Mar 17, 2017 at 1:50 AM Anand Subramanian < asubraman...@hortonworks.com> wrote: Hey Jon, Here you go - https://issues.apache.org/jira/browse/METRON-772 -Anand On 3/15/17, 10:29 PM, "zeo...@gmail.com" wrot

Re: [DISCUSS] Stepping down as release manager

+1 for mattf On Tue, Mar 21, 2017 at 11:04 AM Ryan Merriman wrote: > +1 for Matt > > On Tue, Mar 21, 2017 at 9:44 AM, Matt Foley wrote: > > > Casey, you’ve been a great release manager. I know how much detail > effort > > goes into this role. > > > > I am willing to serve as RM for the next wh

Re: Metron Installation on an Ambari-Managed Cluster?

Just to add onto this, that is a feature I have similarly been looking for but my environment hasn't matured enough yet for me to push the topic. I've been installing various versions of master in my hardware environment using Ansible, but ever since the Ambari mpack I have been doing it more manu

Re: [DISCUSS][PROPOSAL] Maven Plugin to build packages with dependencies

I don't have a strong opinion here, but I'm interested to see what the direction on this one will be. Jon On Wed, Mar 22, 2017 at 3:30 PM Otto Fowler wrote: > As we have discussion previously, I am working on a plugin architecture for > parsers and stellar ( down the road ), base on Nifi’s Nar

Re: Unable to build Ansible 2.0.0.2 on macOS using our instructions

Hey Dave, Can you point me to which branch you were referring to? I'd be happy to take a stab at this - I really don't like having broken instructions sitting out there. Thanks, Jon On Wed, Mar 1, 2017 at 4:22 PM zeo...@gmail.com wrote: > Sounds good to me, I'll keep a

Re: [DISCUSS][PROPOSAL] Maven Plugin to build packages with dependencies

t; > I support option 1 if Infra will do it. Otherwise 2. But it might be > easier to achieve the Infra request after we have exited the incubator. > --Matt > > On 3/27/17, 6:25 PM, "zeo...@gmail.com" wrote: > > I don't have a strong opinion here, but I'm i

[DISCUSS] The bro kafka plugin

Today I was taking a look at METRON-812 , which made me recall some conversations from a while back regarding where the bro kafka plugin should ultimately live, and how to update it. Back in METRON-348

Re: [DISCUSS] The bro kafka plugin

ackage > > within Metron? I definitely would like to see the modifications at > > https://github.com/bro/bro-plugins/commit/b9f1f35415cb0db > > 065348da0a5043a8353b4a0a8 brought back into Metron and I'd love for us to > > host the plugin. > > > > Thoughts? >

Re: [DISCUSS] The bro kafka plugin

think this is a good idea, we can pose it to INFRA as a request. I'd love to see us be able to use the bro packaging infrastructure and get more visibility for the plugin. I'd be particularly interested in Nick's opinion on this, though. On Thu, Mar 30, 2017 at 11:12 PM, zeo...@gma

Re: [DISCUSS] The bro kafka plugin

airly easy to see by just doing a diff. It would be great if others want to take on any of that work. I would be glad to offer any support that you need. Thanks, Jon! On Thu, Mar 30, 2017 at 11:20 PM, zeo...@gmail.com wrote: > Ok, great. > > I agree, I definitely want to hear from

Re: [DISCUSS] The bro kafka plugin

: > We should be able to request just one alternate repo from INFRA, and put a > top hierarchical level in it that doesn’t include a maven pom. As far as > maven and clients are concerned, it > > just increases by 1 the path length to the root of the repo. > > On 3/31/17, 10:30

asf-site

I had considered pushing an updated website today as a part of METRON-810, but when I followed the instructions here I found a surprising amount of changes for asf-site. Is this expected? I sifted through some of the changes an

Re: How to clean Metro 0.3.1 quick-dev-platform box ?

Sorry about the brevity, answering on my phone. 1. By default the data comes from the sensor-stubs. For more details see https://github.com/apache/incubator-metron/blob/master/metron-deployment/roles/sensor-stubs/README.md 2. The vagrant details come from these two locations - https://atlas.has

Re: [GitHub] incubator-metron pull request #503: METRON-815 sensor-stubs sometimes send m...

Bro timestamps are often out of order depending on the log because some lines are written when the connection ends and others are written when an event within a connection occurs. As such, timestamps can be confusing to look at initially, but it is very normal for them not to be in order. Also, we

Re: [DISCUSS] The bro kafka plugin

Can someone on the PMC submit a ticket to INFRA? It looks like <https://www.apache.org/dev/infra-contact> committers aren't supposed to. Jon On Fri, Mar 31, 2017 at 4:23 PM zeo...@gmail.com wrote: > I would be happy to try it again but I attempted to do that before with > br

Re: [DISCUSS] next release proposal

How far out is the management UI? Jon On Tue, Apr 4, 2017, 2:09 PM Matt Foley wrote: > Hi all, > Although it’s only been a few weeks since the last release was finally > published, that process started in January :-) > Also, the last commit in 0.3.1 was Feb 23, and there’s been a ton of > reall

Re: [DISCUSS] The bro kafka plugin

ins version and pulling it into the Apache-hosted code. IANAL 2. Nick - are you OK with these changes? Jon On Mon, Apr 3, 2017 at 3:50 PM zeo...@gmail.com wrote: > Can someone on the PMC submit a ticket to INFRA? It looks like > <https://www.apache.org/dev/infra-contact> committers

Re: [DISCUSS] The bro kafka plugin

s a problem here. > > (2) I am OK with whatever we need to get this effort done and under ASF. > > > On Wed, Apr 5, 2017 at 1:12 PM, zeo...@gmail.com wrote: > > > I'm working on this > > <https://github.com/JonZeolla/incubator-metron/tree/METRON-348> in > &g

Re: [DISCUSS] The bro kafka plugin

what they've done just so we don't break convention. > > > > > > > On Wed, Apr 5, 2017 at 3:22 PM, Nick Allen wrote: > > > Yes, I will open an INFRA ticket. Just give me a little time to > research > > what we need. > > > >

[MENTORS] Licensing

*Background* We have a situation where a portion of code was created for Metron, which is a plugin for a separate open source project, bro. The code was separately pushed out by the initial author to the bro c

Re: [DISCUSS] The bro kafka plugin

Mentor discussion sent <https://lists.apache.org/thread.html/a4e2e7bb7fb7497033696645b011c5604790f23f3802aaab32f1bd01@%3Cdev.metron.apache.org%3E> Jon On Wed, Apr 5, 2017 at 4:34 PM zeo...@gmail.com wrote: > incubator-metron-bro-plugin-kafka is fine with me, in the hopes that

Failing build

We appear to have a failed build again: No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself. https://travis-ci.org/apache/incubator-metron/builds/219261745 Jon -- Jon

Re: [MENTORS] Create Additional Repo for Apache Metron Incubating

Thanks! Would you mind taking a look at my other thread, here ? It is related to the use of this new repo. Much appreciated, Jon On Mon, Apr 10, 2017 at 1:54 PM P. Taylor G

Re: [MENTORS] Licensing

gt; discussions, and I would recommend PMC members read and/or subscribe to > that list. > > -Taylor > > > On Apr 5, 2017, at 4:50 PM, zeo...@gmail.com wrote: > > > > *Background* > > We have a situation where a portion of code > > < > https://github.

Re: [DISCUSS] next release proposal

working on METRON-826 right now. I'll have a PR up today or > >> > > > > tomorrow at > >> > > > > the latest. I'd like to see it go as well. > >> > > > > > >> > > > > https://issues.apache.org/jira/browse/METR

Re: metron UI

The instructions that Ryan gave at the top of the PR are working for me. Namely: scp ./metron-interface/metron-rest/target/metron-rest-0.3.1-archive.tar.gz root@node1:/usr/metron/0.3.1/ ssh root@node1 cd /usr/metron/0.3.1/ tar -xf metron-rest-0.3.1-archive.tar.gz java -jar ./lib/metron-rest-0.3.1.

Re: metron UI

eeded. I updated the README but did not update the PR. Soon this UI will > be installed as part of the MPack so defaults won't matter after that. > > Ryan > > On Tue, Apr 11, 2017 at 2:44 PM, zeo...@gmail.com > wrote: > > > The instructions that Ryan gave at

Re: [MENTORS] Licensing

gin-kafka > > > > > On Mon, Apr 10, 2017 at 8:59 PM, zeo...@gmail.com > wrote: > > > Okay great, thanks you. I've sent an email out to general@ to discuss. > > > > It looks like things are all set up on asf > > <https://git-wip-us.apache.org/repos/asf?

Re: [DISCUSS] next release proposal

I agree conceptually but haven't looked at them each individually to see how much they impact and if a short timeline for merging is reasonable. METRON-821 just needs a minor change and then a final run-through before I'm comfortable merging it in. Jon On Wed, Apr 12, 2017 at 11:44 AM Nick Allen

Re: [DISCUSS] The bro kafka plugin

hub.com/JonZeolla/incubator-metron/tree/METRON-348/metron-sensors/bro-plugin-kafka> from the incubator-metron repo Jon On Wed, Apr 5, 2017 at 6:01 PM Nick Allen wrote: > Created the INFRA request. > > https://issues.apache.org/jira/browse/INFRA-13828 > > > On Wed, Apr 5, 201

Re: Having difficulty setting up both QuickDev and FullDev

Hmm, I just spun up full-dev without an issue. I had a similar issue the other day which was fixed via this , can you merge in master and retry? Jon On Wed, Apr 19, 2017 at 3:35 PM Rita McKissick wrote:

Re: [DISCUSS] Multitenancy for Metron

Lurker here (hi!). I'm also a potential user of metron in the near future (hence the lurking), but I've been waiting for the right features to make it worth the move, and one of those is multi-tenancy. My comments: To me, this primarily means a UI with strong access control/RBAC to the data, acce

Re: [DISCUSS] Metron assessment tool

However, it would be handy to have something like this perpetually running so you know when to scale up/out/down/in a cluster. On Fri, Apr 15, 2016, 13:35 Nick Allen wrote: > I think it is slightly different. I don't even want to install minimal > Kafka infrastructure (Look ma, no Kafka!) > > T

  1   2   3   >