The Teams Manager Moolet is triggered by Moogsoft AIOps when a Situation is created, updated and deleted, and also when a team is created and updated. You can assign teams to Situations using the filters in the UI under Settings > Teams > General. If there are no filters for a team, it is assigned all new Situations by default.
If you use the "assignTeamsToSituation" Graze API endpoint or MoogDb method to assign teams to a Situation, Moogsoft AIOps marks the Situation as overridden. The Teams Manager Moolet can no longer act on it even if that Situation matches a filter.
You can alter the behavior of the Teams Manager Moolet by changing the "Situation Update Policy" in the UI under Settings > Teams.
One Teams Manager Moolet is run for every instance of Moogsoft AIOps.
Configure Teams Manager
You can configure the Teams Manager Moolet in the
$MOOGSOFT_HOME/config/moolets/teams_manager.conf configuration file.
Teams Manager Properties
The properties that relate to the Teams Manager Moolet are:
run_on_startup: Determines whether Teams Manager runs when Moogsoft AIOps starts. If you enable it, Teams Manager processes Moolet output from the moment the system starts, without you having to configure or start it manually.
The default Teams Manager configuration is:
classname are hardcoded and should not be changed.
These parameters control the output the Moolet processes:
process_output_of: The Moolets that perform actions that trigger the Teams Manager:
Sigaliser, Speedbird, Cookbook, Default Cookbook, SituationMgr
[ "Sigaliser", "Speedbird", "Cookbook", "Default Cookbook", "SituationMgr" ]