Template Matcher Moolet


Template Matcher was deprecated from the release of Moogsoft AIOps V7.0.0. See Deprecation Notice: Template Matcher for more information.

The Situation Templates enable users to provide feedback to Moogsoft AIOps that indicates the quality of the Situations produced and consequently what Moogsoft AIOps should do if it detects a similar situation in the future.


The TemplateMatcher Moolet should be activated in Moogfarmd if you wish your system to discover “Priority Templates”. By default, Moogfarmd always suppresses the creation of SPAM templates, regardless of the Moolet they are generated by.

You can configure the Teams Manager Moolet in the $MOOGSOFT_HOME/config/moolets/teams_manager.conf configuration file.

Moolets are capable of supporting multiple Moobots. By configuring a Moolet to run multiple Moobots, you can customise the functions of the default Moobot. You can use this feature to customise the actions for Workflow Engine. To do this, locate the Moobot property in the Moolet configuration file and add a comma-separated list of the Moobots you want to run. See the extract Template Matcher Moolet parameters below and notice the default "moobot" property which contains one Moobot: "TemplateMatcher.js".

There is no special configuration required for the Moolet; it is either “on” or “off”. TemplateMatcher should run after the Alert Builder or Alert Rules Engine depending upon the system configuration. The default configuration for the TemplateMatcher is shown below:

name               : "TemplateMatcher",
classname          : "CTemplateMatcher",
run_on_startup     : false,
#process_output_of : "AlertRulesEngine",
process_output_of  : "AlertBuilder",
threads            : 4
moobot             : "TemplateMatcher.js"
Standalone Execution

The TemplateMatcher Moolet can be executed in a “stand-alone” mode via the moog_primer/sigaliser utility using the following command:

sigaliser --moolet=TemplateMatcher