Skip to main content

Configure the JDBC Enrichment Integration

To set up JDBC Enrichment in Moogsoft Enterprise, configure the JDBC Enrichment integration to access the data in your external database. The integration includes the connection information, table definitions for your enrichment database, and the alert field to use in queries. This topic covers the second step in the JDBC enrichment example Enrich Alerts Using a JDBC Data Source.

The following diagram illustrates the process to enrich alert data from an external database:


The JDBC Enrichment Integration lets you specify one or more database definitions to control data access as follows:

  • Connection Information: the database connection details you found in Analyze Your JDBC Source Data.

  • Database Cache Settings: the length of time to cache query results in memory for subsequent alerts that match the query criteria in the Workflow Engine.

  • Table Definition: information about how to query a specific table in the database, which fields to return, and where to store the results in the custom_info.enrichment object of the alert. You can use the table definition to customize the format of the query results. See JDBC Enrichment Reference for more detail.

After you configure the JDBC Enrichment integration, you are ready to Create a Workflow to Forward to JDBC Enrichment.

Step 2 example: Configure the JDBC Enrichment integration

Using the information you gathered from Analyze Your JDBC Source Data, you can configure the JDBC Enrichment integration. In this example, you create a database definition called "CMDB".

Configure the database connection

Configure the integration with the connection information you gathered from Analyze Your JDBC Source Data as follows:

  • Integration Name: Configuration Management Database

  • Database Definition Name: CMDB

    Use this name when you configure the JDBC Enrichment Workflow.

  • Database Type: mySql

  • Database Host:

  • Database Port: 3306

  • Database Name: cmdb

  • Database User: enricher

  • Password: password123

For the example scenario, do not change the Additional Properties or Cache Results.

Configure the table definition

  1. Create a table definition called "server", to access the data from the server table as follows:

    • Name: server

    • Table: server

    • Custom Info Path To Store Results: cmdb_info

      This stores the JDBC enrichment data to custom_info.enrichment.cmdb_info.

    • Query: name = "$source"

      Add quotes around the alert field name or variable name when you specify the query.

    The integration substitutes the value of the source from the alert to create a WHERE clause for the query. For example, for an alert with {"source":"sflinux101"} :

    WHERE name = "sflinux101"
  2. Create a field definition to retrieve the location data as follows:

    • Table Field Name: location

    • UI Alias: location

    • Summarize This Field As A List: <unchecked>

  3. Create another field definition to retrieve the support group data as follows:

    • Table Field Name: support_group

    • UI Alias: support_group

    • Summarize This Field As A List: <unchecked>

You don't need to summarize field as a list in this configuration because you expect a single result. When you complete the configuration, click Confirm to save your table definition.

Learn more

To continue with the JDBC Enrichment example, go to step 3: Create a Workflow to Forward to JDBC Enrichment.

For more information on the JDBC Enrichment integration, see JDBC Enrichment and JDBC Enrichment Reference.