Situation Manager
Situation Manager listens for Situations being created, updated or closed and passes them to an associated Moobot.
You can:
-
Determine the origin of Situations.
-
Define the Moobots to process Situations.
-
Specify functions to apply to Situations.
You can configure a moobot to perform functions such as data enrichment, auto-assignment, or notifying a third-party tool to raise a ticket.
You can configure the Situation Manager in the $MOOGSOFT_HOME/config/moolets/situation_manager.conf file.
The Situation Manager parameters that can be configured are as follows:
Determines whether Situation Manager runs when Moogsoft AIOps starts or not.
Type: Boolean
Default: false
Determines whether or not Situation Manager is included in the Event Processing metric for Self Monitoring.
Type: Boolean
Default: false
Specifies a JavaScript file found in $MOOGSOFT_HOME/bots/moobots.
Examples of available Moobots include SituationMgr.js, SituationMgrLabeller.js or
SituationMgrNetcool.js. These can be customized to meet your needs.
Type: String
Default: "SituationMgr.js"
When set to true, listens to messages sent on the sigs topic by any Moolet running on a different farmd instance. This option directly replaces standalone, which is now deprecated but preserved for backwards-compatibility.
Type: Boolean
Default: true
Determines which algorithms Situation Manager processes the output of. This might be a single Sigaliser algorithm or multiple algorithms.
Type: List
Default: "Sigaliser", "TemplateMatcher", "Speedbird", "Default Cookbook".
An example Situation Manager configuration is as follows:
{
name: "SituationMgr",
classname: "CSituationMgr",
run_on_startup: true,
metric_path_moolet: true,
moobot: "SituationMgr.js",
mooms_event_handler: true,
process_output_of:
[
"Sigaliser_1",
"Sigaliser_2",
"Sigaliser_3",
"TemplateMatcher",
"Speedbird",
"Cookbook"
]
}
Note
Do not change the classname. It is hardcoded.
Situation Manager listens for three event types by default:
-
Sig- a new Situation being created. -
SigClose- a Situation being closed. -
SigUpdate- a Situation being updated.
If you want to listen for other events, create an Empty Moolet and define the other events
under event_handler. See the eventType method in
Constants
for a full list of event types.
You can listen for specific Situation actions using the SigAction event.
It can filter out the following actions:
Assigned Moderator Situation Resolved Situation Revived Situation Closed Assigned Queue Created By Merge Used In Merge Created By Split Used For Split Ran Tool Acknowledged Situation Moderator |
Deacknowledged Situation Moderator Added Alerts To Situation Added Entry To Thread Changed Situation Processes Changed Situation Services Created Thread Agreed With Thread Entry Commented On Thread Entry Disagreed With Thread Entry Changed Situation Custom Info |
Described Situation Excluded User Invited User Moved Alerts To Situation Removed Alerts From Situation Situation Teams Changes Marked Thread Entry As Resolving Unmarked Thread Entry As Resolving Situation Rating Situation Rating Removed |
There are three Moobots available in $MOOGSOFT_HOME/bots/moobots that
Situations can be sent to by Situation Manager. You can customize these to meet your requirements.
Situation Manager's default associated Moobot is called SituationManager.js.
See Moobot Modules for more information on how to configure it.
Another application of the Situation Manager is Situation Manager Labeler.
You can use it to enrich Situations by dynamically adding alert properties to the Situation description. See Situation Manager Labeler for more information.
This Situation Manager Moobot is required for the Legacy Netcool integration.
See Netcool Legacy LAM for more information.