[GitHub] metron issue #1208: METRON-1790: Unsubscribe from every observable in the pc...

Github user tiborm commented on the issue: https://github.com/apache/metron/pull/1208 Checked and tested. Looks good to me. +1 ---

[jira] [Commented] (METRON-1790) Unsubscribe from every observable in the pcap panel UI component

[ https://issues.apache.org/jira/browse/METRON-1790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16625640#comment-16625640 ] ASF GitHub Bot commented on METRON-1790: Github user tiborm commented on the iss

[GitHub] metron issue #1207: METRON-1695: Expose pcap properties through Ambari

Github user nickwallen commented on the issue: https://github.com/apache/metron/pull/1207 > @anandsubbu: One thing I am not sure is, whether the topology name i.e. metron_pcap_topology should be fetched from the config or should be hard coded to 'pcap' I think what you have w

[jira] [Commented] (METRON-1695) Expose pcap properties through Ambari

[ https://issues.apache.org/jira/browse/METRON-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16625893#comment-16625893 ] ASF GitHub Bot commented on METRON-1695: Github user nickwallen commented on the

[GitHub] metron issue #1207: METRON-1695: Expose pcap properties through Ambari

Github user nickwallen commented on the issue: https://github.com/apache/metron/pull/1207 This is causing one problem on Full Dev. We have 6 slots in Full Dev, but since adding the Pcap Topology, we now require 7 slots for all of the topologies to run. What ends up happenin

[jira] [Commented] (METRON-1695) Expose pcap properties through Ambari

[ https://issues.apache.org/jira/browse/METRON-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626085#comment-16626085 ] ASF GitHub Bot commented on METRON-1695: Github user nickwallen commented on the

[GitHub] metron issue #1207: METRON-1695: Expose pcap properties through Ambari

Github user ottobackwards commented on the issue: https://github.com/apache/metron/pull/1207 We have an overall deficiency here I believe. The Slot management is a oft forgotten and manual task, for adding new parsers from the ui etc, you ( I believe ) still have to remember to have

[jira] [Commented] (METRON-1695) Expose pcap properties through Ambari

[ https://issues.apache.org/jira/browse/METRON-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626102#comment-16626102 ] ASF GitHub Bot commented on METRON-1695: Github user ottobackwards commented on

[GitHub] metron issue #1207: METRON-1695: Expose pcap properties through Ambari

Github user nickwallen commented on the issue: https://github.com/apache/metron/pull/1207 > @ottobackwards The Slot management is a oft forgotten and manual task, for adding new parsers from the ... Sure, worthy of a discuss. @anandsubbu I would just drop "snort" as

[jira] [Commented] (METRON-1695) Expose pcap properties through Ambari

[ https://issues.apache.org/jira/browse/METRON-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626274#comment-16626274 ] ASF GitHub Bot commented on METRON-1695: Github user nickwallen commented on the

[GitHub] metron issue #1207: METRON-1695: Expose pcap properties through Ambari

Github user mmiklavc commented on the issue: https://github.com/apache/metron/pull/1207 Might be worth looking at how we set what spins up by default. For instance, we might not want Pcap to start by default in *any* installation, let alone full dev. Is there an option in the mpack c

[jira] [Commented] (METRON-1695) Expose pcap properties through Ambari

[ https://issues.apache.org/jira/browse/METRON-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626301#comment-16626301 ] ASF GitHub Bot commented on METRON-1695: Github user mmiklavc commented on the i

[GitHub] metron issue #1207: METRON-1695: Expose pcap properties through Ambari

Github user nickwallen commented on the issue: https://github.com/apache/metron/pull/1207 @anandsubbu I am also running into a separate issue. After some period of time Ambari will start reporting the status of the pcap topology as stopped, even though it remains running in Storm. A

[jira] [Commented] (METRON-1695) Expose pcap properties through Ambari

[ https://issues.apache.org/jira/browse/METRON-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626377#comment-16626377 ] ASF GitHub Bot commented on METRON-1695: Github user nickwallen commented on the

[jira] [Created] (METRON-1791) Add GUID to Messages Produced by Profiler

Nick Allen created METRON-1791: -- Summary: Add GUID to Messages Produced by Profiler Key: METRON-1791 URL: https://issues.apache.org/jira/browse/METRON-1791 Project: Metron Issue Type: Bug

[GitHub] metron pull request #1210: METRON-1791 Add GUID to Messages Produced by Prof...

GitHub user nickwallen opened a pull request: https://github.com/apache/metron/pull/1210 METRON-1791 Add GUID to Messages Produced by Profiler If a profile defines a triage result when it is flushed the Profiler will generate a message containing the measurement data so that profile

[jira] [Commented] (METRON-1791) Add GUID to Messages Produced by Profiler

[ https://issues.apache.org/jira/browse/METRON-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626541#comment-16626541 ] ASF GitHub Bot commented on METRON-1791: GitHub user nickwallen opened a pull re