[ 
https://issues.apache.org/jira/browse/METRON-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16637354#comment-16637354
 ] 

ASF GitHub Bot commented on METRON-1695:
----------------------------------------

Github user anandsubbu commented on the issue:

    https://github.com/apache/metron/pull/1207
  
    @nickwallen suggested a great idea of making use of parser aggregation and 
thus starting the default parsers on full-dev as an aggregated parser topology. 
The latest commit makes use of PR #1215 which provides that ability.
    
    Now, on full-dev we start a single aggregated topology for the default 
configured sensors viz. "bro,snort,yaf".
    
    ## Testing Done
    - Spun up full-dev and noticed that a single topology named 
`bro__snort__yaf` is started
    - Verified Alerts UI has data from all three sensors:
    
    
![image](https://user-images.githubusercontent.com/20395490/46431349-33d6aa80-c769-11e8-8b6e-33940ef9b9eb.png)



> Expose pcap properties through Ambari
> -------------------------------------
>
>                 Key: METRON-1695
>                 URL: https://issues.apache.org/jira/browse/METRON-1695
>             Project: Metron
>          Issue Type: Bug
>            Reporter: Anand Subramanian
>            Assignee: Anand Subramanian
>            Priority: Major
>
> Currently, the $METRON_HOME/config/pcap.properties file is hardcoded with the 
> defaults. One has to hand edit the file before deploying the PCAP topology. 
> These properties should be configurable via Ambari.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to