Follow

Description of rules.conf (Workflow configuration)

This document describes all of the configurable parameters for use with Workflow (formerly Rules) as defined in the rules.conf file (/opt/interset/rules/conf/rules.conf).

 

TopologyName - Name of your WorkFlow topology
NumWorkers - How many worker processes to create for the topology across machines in the cluster.
Tid - Tenant ID

KafkaZkHosts - Kafka Zookeeper server
KafkaBrokerZkPath - the root directory under which all the topics and partition information is stored. By default this is /brokers which is what the default Kafka implementation uses

KafkaSpoutWdcEnabled - Set to true for Endpoint installations
KafkaSpoutWdcTopic - Kafka topic where raw endpoint data is stored
KafkaSpoutWdcParallelismHint - Set this number to the maximum number of partitions on the Kafka Topic
KafkaSpoutWdcStateUpdateIntervalMs - setting for how often to save the current Kafka offset to ZooKeeper

KafkaSpoutRepoEnabled - Set to true for Repo installations
KafkaSpoutRepoTopic - Kafka topic where raw repo data is stored
KafkaSpoutRepoParallelismHint - Set this number to the maximum number of partitions on the Kafka Topic
KafkaSpoutRepoStateUpdateIntervalMs - setting for how often to save the current Kafka offset to ZooKeeper

KafkaSpoutAuthEnabled - Set to true for Auth (AD) installations
KafkaSpoutAuthTopic - Kafka topic where raw Auth data is stored
KafkaSpoutAuthParallelismHint - Set this number to the maximum number of partitions on the Kafka Topic
KafkaSpoutAuthStateUpdateIntervalMs - setting for how often to save the current Kafka offset to ZooKeeper

KafkaSpoutRiskScoresTopic - Kafka topic where raw Risk Scores are stored
KafkaSpoutRiskScoresParallelismHint - Set this number to the maximum number of partitions on the Kafka Topic
KafkaSpoutRiskScoresStateUpdateIntervalMs - setting for how often to save the current Kafka offset to ZooKeeper

RulesBoltParallelismHint - specifies the initial number of Rules executors
RulesSpoutMaxPending - This value puts a limit on how many records can be in flight, i.e. have not yet been acked or failed, in a Storm topology at any point of time
RulesPhoeniZk - Phoenix Zookeeper server list

KafkaBoltBrokerList - Kafka Broker List
KafkaBoltTopic - Kafka topic where violations are written to
KafkaBoltRequestRequiredAcks -
0, which means that the producer never waits for an acknowledgement from the broker. This option provides the lowest latency but the weakest durability guarantees (some data will be lost when a server fails).
1, which means that the producer gets an acknowledgement after the leader replica has received the data. This option provides better durability as the client waits until the server acknowledges the request as successful (only messages that were written to the now-dead leader but not yet replicated will be lost).
-1, which means that the producer gets an acknowledgement after all in-sync replicas have received the data. This option provides the best durability, we guarantee that no messages will be lost as long as at least one in sync replica remains.
KafkaBoltParallelismHint - Set this number to the maximum number of partitions on the Kafka Topic

RulesApiServer - Root URI of the Investigator Server
RulesApiServerAuthorizationToken - Investigator Server Auth Token
RulesApiServerPollIntervalMs - Poll Interval to reterive rules from the Investigator Server
RulesDrlFile - Temporary Location of the rules drl file

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk