Moogsoft Docs

Configuration Management Database


Note

AIOps CMDB integration is configured via setting up an ETL job to keep three tables in Moog's database in sync with your CMDB

For performance reasons Moog maintains a cache of CI data in a local table named entity_catalog .  Out of the box Moog will automatically add CIs to this table but it does not automatically add any further meta data unless you set up an ETL job to do so.

The main requirement is to ensure that there is a record for each CI in moogdb.entity_catalog and that it contains the name of a process and/or service that the CI is used for.  Process and Service are both shown in the Moog UI Situation view.  Because Moog Situations may contain one or more CIs the logic is simply that the Moog Situation shows a list of the one or more Processes or Services determined by ALL the CIs within a Situation.

Note

The Process and Service attributes of a Moog Situation may be used to store any two attributes of a Situation and can be renamed to represent any attributes of your choosing. The off the shelf intent was that Process refers to the name of the function that internal IT support staff would recognize (e.g. Microsoft Exchange) and Service refers to the name of an SLA-bound service that a business would recognize (e.g. Email Service)


The CMDB ETL simply needs to:

  1. Keep the moogdb.processes table populated with the name/description of the full list of Processes that CIs might be used for.
  2. Keep the moogdb.services table populated with the name/description of the full list of Services that CIs might be used for.
  3. Keep the moogdb.entity_catalog table populated with the name of each CI (i.e. the source attribute in each Alert) and the Process and/or Service it supports.

With this simple ETL synchronization in place Moog will automatically set the Process and Service for each Situation.

The net workflow result is that each Situation will have an automatically matched Processes Impacted and Service Impacted.

Note

The moogdb.entity_catalog is also used to match CIs to Competency groups.  This controls which Users (who have specific Competencies) are auto-invited to Situations.  This also controls the Situation Scope icons in the UI.  Further details on how this works and how the Situation Scope visuals can be customized/extended can be found here