The Situation Manager listens for Situation creation, update, or closure actions and passes the Situation to an associated Moobot. It runs as a standalone Moolet by default.
You can define the algorithms for which the Situation Manager processes output, the Moobot it passes Situations to and the actions performed on those Situations.
When a Moobot receives a Situation, you can configure it to perform functions such as data enrichment, auto-assignment to a user or notifying a third-party tool to raise a ticket.
The Situation Manager configuration file is located here: $MOOGSOFT_HOME/config/moolets/situation_manager.conf. You can define the following properties:
Determines whether Situation Manager starts when Moogsoft Enterprise starts.
Type | String |
Required | Yes |
Default | N/A |
Determines whether Situation Manager is included in the events processing metric for Self Monitoring.
Type | Boolean |
Required | No |
Default | False |
Determines which Moobot receives Situations from the Situation Manager. The Moobot JavaScript files are located here: $MOOGSOFT_HOME/bots/moobots.
Moolets are capable of supporting multiple Moobots. By configuring a Moolet to run multiple Moobots, you can customize the functions of the default Moobot. You can use this feature to customize 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 Situation Manager parameters below and notice the default "moobot" property which contains one Moobot: "SituationMgrLabeller.js".
Type | String |
Required | Yes |
Default | SituationMgr.js |
Determines whether Situation Manager runs as a standalone Moolet.
Type | Boolean |
Required | No |
Default | True |
An example Situation Manager Moolet configuration as as follows:
{
name : "SituationMgr",
classname : "CEmptyMoolet",
run_on_startup : true,
metric_path_moolet : false,
moobot : "SituationMgrLabeller.js",
standalone_moolet : true,
mooms_event_handler : false,
event_handlers : [ "SigAction" ]
}Note
Do not change the name and classname properties.
Thie Situation Manager listens for the following Situation Actions:
Added alerts to Situation
Removed alerts from Situation
Created by merge
Situation superseding others
Used in merge
Situation closed
If you want to listen for other events, create an Empty Moolet and define the events in the 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 our 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 |
The Situation Manager can send Situations to one of three Moobots. You can customize these to meet your requirements:
Situation Manager: Situation Manager's default associated Moobot. The configuration file is
SituationManager.js. For information on how to configure it, see Moobot Modules.Situation Manager Labeler: You can use the Situation Manager Labeler to enrich Situations by dynamically adding alert properties to the Situation description. The configuration file is
SituationMgrLabeller.js. See Situation Manager Labeler for more information.Situation Manager Netcool: This Moobot is required for the Netcool legacy LAM. The configuration file is
SituationMgrNetcool.js. For more information see Netcool Legacy LAM.