Github user merrimanr commented on a diff in the pull request:
https://github.com/apache/metron/pull/709#discussion_r135261317
--- Diff:
metron-deployment/packaging/ambari/metron-mpack/src/main/resources/common-services/METRON/CURRENT/package/scripts/params/status_params.py
---
@@ -52,6 +52,26 @@
update_table = 'metron_update'
update_cf = 't'
+# Profiler
+metron_profiler_topology = 'profiler'
+profiler_input_topic =
config['configurations']['metron-enrichment-env']['enrichment_output_topic']
+profiler_kafka_start =
config['configurations']['metron-profiler-env']['profiler_kafka_start']
+profiler_period_duration =
config['configurations']['metron-profiler-env']['profiler_period_duration']
+profiler_period_units =
config['configurations']['metron-profiler-env']['profiler_period_units']
+profiler_ttl =
config['configurations']['metron-profiler-env']['profiler_ttl']
--- End diff --
I found out the hard way, through experience. The ambari agent runs in a
polling loop and calls the "status" function on the command script
(profiler_master.py in this case). Not much documentation out there for this
as far as I know.
---
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.
---