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.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
