[
https://issues.apache.org/jira/browse/METRON-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824608#comment-15824608
]
ASF GitHub Bot commented on METRON-659:
---------------------------------------
Github user mmiklavc commented on the issue:
https://github.com/apache/incubator-metron/pull/417
@nickwallen Nice contribution! The docs are solid, and I like the
configurability of the batch size and frequency. And the quicker deploy time is
definitely a plus. Is that because we're no longer deploying the sensors by
default? I'm on the fence about how we should handle that. I originally thought
it best to deploy and not start the real sensors. But if we're saving 14
minutes in the Vagrant deployment, I could be convinced otherwise. And the more
I think about it, you could just run the Ansible role for the sensors which is
easy enough. I don't really have any other suggested changes besides the minor
remark above about the default of 100 vs 1000.
+1 from me pending the Travis checks.
> Emulate Sensors in Development Environments
> -------------------------------------------
>
> Key: METRON-659
> URL: https://issues.apache.org/jira/browse/METRON-659
> Project: Metron
> Issue Type: Improvement
> Affects Versions: 0.3.0
> Reporter: Nick Allen
> Assignee: Nick Allen
> Fix For: Next + 1
>
>
> Replace the Snort, Bro, and YAF sensors on the "Quick Dev" and "Full Dev"
> environments with a mechanism that consumes less resources.
> These environments are notoriously difficult to work with because the
> installed services consume nearly all available memory. The Bro, YAF, and
> Snort sensors, along with the PCAP Replay service, consume a considerable
> amount of these limited resources.
> Replacing these sensors with a lightweight mechanism should free-up
> additional resources, make the environment easier to work with, and result in
> faster deployments.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
