[
https://issues.apache.org/jira/browse/METRON-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16141632#comment-16141632
]
ASF GitHub Bot commented on METRON-1122:
----------------------------------------
Github user cestella commented on a diff in the pull request:
https://github.com/apache/metron/pull/709#discussion_r135261379
--- Diff:
metron-deployment/packaging/ambari/metron-mpack/src/main/resources/common-services/METRON/CURRENT/package/scripts/params/params_linux.py
---
@@ -251,6 +253,26 @@
threat_intel_join_parallelism =
config['configurations']['metron-enrichment-env']['threat_intel_join_parallelism']
kafka_writer_parallelism =
config['configurations']['metron-enrichment-env']['kafka_writer_parallelism']
+# Profiler
+
+metron_profiler_topology = 'profiler'
+profiler_input_topic =
config['configurations']['metron-enrichment-env']['enrichment_output_topic']
--- End diff --
So, the profiler's input topic, in metron, is the output of the enrichment
topology. I did it this way to keep them in alignment. There is currently, to
my mind, not a usecase where the profiler does take its data from the output of
the enrichment topology.
> Add support for the profiler in the management pack
> ---------------------------------------------------
>
> Key: METRON-1122
> URL: https://issues.apache.org/jira/browse/METRON-1122
> Project: Metron
> Issue Type: Improvement
> Reporter: Casey Stella
>
> The Profiler should be installed via the management pack.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
