Understanding the Profiler
A profile describes the behavior of an entity on a network. This feature is typically used by a data scientist and you should coordinate with the data scientist to determine if they need your assistance with customizing the Profiler values.
HCP installs the Profiler which runs as an independent Apache Storm topology. The
configuration for the Profiler topology is stored in Apache ZooKeeper at
/metron/topology/profiler. These properties also exist in the default
installation of HCP at
$METRON_HOME/config/zookeeper/profiler.json. You can
change the values on disk and then upload them to ZooKeeper using
The Profiler can persist any serializable object, not just numeric values.
HCP supports the following profiler properties:
The number of worker processes to create for the topology.
The number of executors to spawn per component.
The name of the Kafka topic from which to consume data.
The name of the Kafka topic to which profile data is written. Only used with profiles that use the
triage` result field](#result).
The duration of each profile period. Define this value along with
The units used to specify the profile period duration. Define this value along with
If a message has not been applied to a Profile in this period of time, the Profile is forgotten and its resources cleaned up. Define this value along with
The units used to specify
A salt is prepended to the row key to help prevent hotspotting. This constant is used to generate the sale. Ideally, this constant should be roughly equal to the number of nodes in the Apache HBase cluster.
The name of the HBase table that profiles are written to.
The column family used to store profiles.
The number of puts written in a single batch.
The maximum number of seconds between batch writes to HBase.