Github user cestella commented on a diff in the pull request:
https://github.com/apache/metron/pull/606#discussion_r121049130
--- Diff:
metron-platform/metron-common/src/main/java/org/apache/metron/common/stellar/StellarCompiler.java
---
@@ -76,14 +93,80 @@ public
Github user asfgit closed the pull request at:
https://github.com/apache/metron/pull/609
---
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 the feature is
Hi Simon,
We have noticed those issues as well. Can you share the changes you have
made? so we can merge it with our version. We have implemented about 40-50
more ciscotags so far. It would be great if we can optimize it and
contribute back to the community. However, we may end up reimplement it
I thought about compile of first use and cache as an approach, but decided it
would reduce the predictability of latency for a message, which is important in
the metron enrichment context. As you say, we could end up growing a large
number of Groks, but if the load of compile is all pushed to
I like the pre-compile idea. One concern is I see the number of grok objects
growing over time. This parser does not account for nearly all of the possible
ASA message types, currently only the most common ones. Is there a middle
ground implementation where we can compile on first use of a grok
The changes are pretty simple (pre-compile the grok, duh). Most other grok
parser just use a single expression, which is already pre-compiled (/checks
assumption in code) so really it’s just the ASA one because of it’s strange two
stage grok.
Shame, it would have been nice to find some more
Are these changes that all grok parsers can benefit from? Are your changes
to the base classes that they use or asa only?
On June 8, 2017 at 20:49:49, Simon Elliston Ball (
si...@simonellistonball.com) wrote:
I got mildly interested in parser performance as a result of some recent
work on
Github user mattf-horton commented on a diff in the pull request:
https://github.com/apache/metron/pull/614#discussion_r121001410
--- Diff: metron-platform/Performance-tuning-guide.md ---
@@ -0,0 +1,326 @@
+# Metron Performance Tunining Guide
+
+## Overview
+
Github user mattf-horton commented on a diff in the pull request:
https://github.com/apache/metron/pull/614#discussion_r121000712
--- Diff: metron-platform/Performance-tuning-guide.md ---
@@ -0,0 +1,326 @@
+# Metron Performance Tunining Guide
+
+## Overview
+
Github user mattf-horton commented on the issue:
https://github.com/apache/metron/pull/610
The Metron RPM build is broken with this patch, which interferes with
testing. Will have it fixed shortly. --Matt
---
If your project is set up for it, you can reply to this email and have
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/609
Do we want to add a version number to these configuration now? Then we can
say no version is 0, this is 1 etc.
---
If your project is set up for it, you can reply to this email and have
Github user mmiklavc commented on a diff in the pull request:
https://github.com/apache/metron/pull/614#discussion_r120979346
--- Diff: metron-platform/Performance-tuning-guide.md ---
@@ -0,0 +1,326 @@
+# Metron Performance Tunining Guide
+
+## Overview
+
+This
Github user mmiklavc commented on a diff in the pull request:
https://github.com/apache/metron/pull/614#discussion_r120979059
--- Diff: metron-platform/Performance-tuning-guide.md ---
@@ -0,0 +1,326 @@
+# Metron Performance Tunining Guide
+
+## Overview
+
+This
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/609
@cestella Perfect. Definitely didn't want to imply that belongs in this
ticket at all. I'm in full support of it being backwards compatible for now,
and keeping the discussion of how we prune
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/609
@justinleet yes, agreed. I wanted to get this functionality in and have it
be backwards compatible for the short term, but ultimately, I think that it's a
better approach and we should work toward
Github user simonellistonball commented on a diff in the pull request:
https://github.com/apache/metron/pull/614#discussion_r120961228
--- Diff: metron-platform/Performance-tuning-guide.md ---
@@ -0,0 +1,326 @@
+# Metron Performance Tunining Guide
+
+## Overview
+
Github user justinleet commented on a diff in the pull request:
https://github.com/apache/metron/pull/614#discussion_r120964479
--- Diff: metron-platform/Performance-tuning-guide.md ---
@@ -0,0 +1,326 @@
+# Metron Performance Tunining Guide
+
+## Overview
+
Github user justinleet commented on a diff in the pull request:
https://github.com/apache/metron/pull/614#discussion_r120964036
--- Diff: metron-platform/Performance-tuning-guide.md ---
@@ -0,0 +1,326 @@
+# Metron Performance Tunining Guide
--- End diff --
GitHub user mmiklavc opened a pull request:
https://github.com/apache/metron/pull/614
METRON-992: Create performance tuning guide
https://issues.apache.org/jira/browse/METRON-992
This guide covers performance tuning the Metron topologies. I will be
leaving this up for a
GitHub user merrimanr reopened a pull request:
https://github.com/apache/metron/pull/613
METRON-990: Clean up and organize flux properties
## Contributor Comments
This PR is mainly a refactor of the enrichment and indexing flux files
along with their matching property files.
Github user merrimanr closed the pull request at:
https://github.com/apache/metron/pull/613
---
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 the feature is
Github user justinleet commented on a diff in the pull request:
https://github.com/apache/metron/pull/609#discussion_r120932742
--- Diff:
metron-platform/metron-common/src/main/java/org/apache/metron/common/message/JSONFromPosition.java
---
@@ -40,10 +40,12 @@ public
Github user cestella commented on a diff in the pull request:
https://github.com/apache/metron/pull/609#discussion_r120932266
--- Diff: metron-platform/metron-enrichment/README.md ---
@@ -71,40 +73,94 @@ The `fieldMap`contents are of interest because they
contain the routing and
Github user justinleet commented on a diff in the pull request:
https://github.com/apache/metron/pull/606#discussion_r120926071
--- Diff:
metron-platform/metron-common/src/main/java/org/apache/metron/common/stellar/StellarCompiler.java
---
@@ -76,14 +93,80 @@ public
Github user cestella commented on a diff in the pull request:
https://github.com/apache/metron/pull/609#discussion_r120924836
--- Diff:
metron-platform/metron-enrichment/src/test/java/org/apache/metron/enrichment/adapters/stellar/StellarAdapterTest.java
---
@@ -0,0 +1,134 @@
Github user cestella commented on a diff in the pull request:
https://github.com/apache/metron/pull/609#discussion_r120924708
--- Diff:
metron-platform/metron-common/src/main/java/org/apache/metron/common/message/JSONFromPosition.java
---
@@ -40,10 +40,12 @@ public
Github user justinleet commented on a diff in the pull request:
https://github.com/apache/metron/pull/609#discussion_r120919459
--- Diff:
metron-platform/metron-common/src/main/java/org/apache/metron/common/message/JSONFromPosition.java
---
@@ -40,10 +40,12 @@ public
Github user justinleet commented on a diff in the pull request:
https://github.com/apache/metron/pull/609#discussion_r120921756
--- Diff:
metron-platform/metron-enrichment/src/test/java/org/apache/metron/enrichment/adapters/stellar/StellarAdapterTest.java
---
@@ -0,0 +1,134 @@
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/609
A lot of this brings up the discussions around deprecating / dropping
functionality (both for Stellar and in general). It seems like ideally, we'd
be deprecating the map functionality in favor
Github user cestella commented on a diff in the pull request:
https://github.com/apache/metron/pull/602#discussion_r120890884
--- Diff: metron-deployment/roles/ambari_config/vars/single_node_vm.yml ---
@@ -102,7 +102,7 @@ configurations:
required_configurations:
-
Github user asfgit closed the pull request at:
https://github.com/apache/metron/pull/600
---
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 the feature is
ok
>
> Il 8 giugno 2017 alle 11.54 "zeo...@gmail.com" ha
> scritto:
>
> Moving to user list
>
> Jon
>
> On Thu, Jun 8, 2017, 5:51 AM wrote:
>
> > >
> > Hei Jon,
> >
> > thank you.
> >
> > I don't know
Moving to user list
Jon
On Thu, Jun 8, 2017, 5:51 AM wrote:
> Hei Jon,
>
> thank you.
>
> I don't know which are the differences between 0.3.1 and 0.4.0.
>
> Unfortunately for me, my CPU does not support virtualization. That means
> that I cannot use Docker.
>
> The only
Hei Jon,
thank you.
I don't know which are the differences between 0.3.1 and 0.4.0.
Unfortunately for me, my CPU does not support virtualization. That means that
I cannot use Docker.
The only workaround that I found is to use AWS directly but for me that I have
never used Mentor it could be
Hello,
I didn't check the BIOS if I can enable it.
Then, I see that yesterday has been updated the installation guideline for
Metron 0.3.1 as follows:
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=68718548
Reading that, there is no mention to Docker.
Maybe for my
35 matches
Mail list logo