[
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 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 config for one, or two, is
there a way to disable it via our blueprints? This way we don't alter the
existing set of topologies. One reason for this is that it's at least mildly
useful to have 2+ sensors worth of data writing out to ES that can be viewed in
Kibana. And while pcap doesn't go to indexing anyhow, we don't have anything
generating data into the pcap topology currently at all. It would just be
taking up a slot and doing nothing.
> 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)
