[
https://issues.apache.org/jira/browse/METRON-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16141653#comment-16141653
]
ASF GitHub Bot commented on METRON-1122:
----------------------------------------
Github user nickwallen commented on a diff in the pull request:
https://github.com/apache/metron/pull/709#discussion_r135264143
--- 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 --
Its a good thing to bring up and discuss @merrimanr . I agree with
@cestella . Doing it this way makes it less error-prone for the user. If the
user changes the enrichment output topic, the Profiler will get auto-magically
updated too.
I cannot think of a use case where the Profiler does not want the output of
Enrichment.
> 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)
