You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@metron.apache.org by GitBox <gi...@apache.org> on 2019/05/02 22:22:28 UTC

[GitHub] [metron] ottobackwards commented on issue #1398: METRON-2100: Update developer documentation for full dev management UI parser aggregation feature gap

ottobackwards commented on issue #1398: METRON-2100: Update developer documentation for full dev management UI parser aggregation feature gap
URL: https://github.com/apache/metron/pull/1398#issuecomment-488853309
 
 
   This doesn't help them if they actually want to _work_ with the full_dev.
   - how do you get rid of the aggregations?
   - what happens if you try to edit the configuration for bro, will a second bro topology be started?
   - how would you work with the sensors in the aggregation?
   
   I asked in the discuss and got no answer to the *real* number of issues with usability around this issue, for people that are using full_dev to test or doc or do things other than what our committers think developers do and can deal with.
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services