Enrich Alerts Using a JDBC Data Source

You can use JDBC Enrichment Workflow Engine with the the JDBC Enrichment Integration in Moogsoft AIOps to add information from external databases to your alerts.

This topic and its related topics use an example scenario to walk you through the process to add information like physical location from a CMDB to an alert’s custom_info object. For general information on enrichment, see Enrichment.

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

jdbc_enrichment.png

To walk through the enrichment process:

  1. Prepare to Enrich. Define your goals for the enrichment. For example, you want to use your CMDB to add hardware physical location information to alerts to satisfy your operators' requirements.

  2. Analyze Your JDBC Source Data. Gather information about your source database: connection details, credentials, and the tables and columns that contain enrichment data. For example, the CMDB stores the physical location in the "location" field in the "ci" table.

  3. Configure the JDBC Enrichment Integration. Create a database definition in the JDBC that includes the alert field to use in the database query and the connection information and table definitions for your enrichment database. For example if you want to use the "source" field to query the CMDB to retrieve the location field from the server table.

  4. Create an Enrichment Workflow. Set up a workflow in the Enrichment Workflow Engine to forward alerts to the JDBC Enrichment Workflow Engine.

  5. Create a JDBC Enrichment Workflow. Set up a workflow in the JDBC Workflow Engine to trigger the JDBC Enrichment integration. When you set up your workflow, you can specify which table definition to use to enrich alert data for the workflow.

Learn more

To walk through a JDBC enrichment example scenario, go to step 1: Prepare to Enrich.

For more information about enrichment and situation design:

For details on JDBC enrichment components: