Forrester Total Economic Impactâ„¢ study finds Edwin AI delivered a 313% ROI for composite organization.

Read more

This article describes how to configure the LogicMonitor Data Exchange (LMDX) application which integrates Edwin AI with your ServiceNow instances.

Note: The instructions here apply to non-domain separated ServiceNow instances. To route Edwin AI incidents across multiple ServiceNow instances, multiple ITSM platforms, or separate QA and production targets simultaneously, you must configure a domain separated instance.

Review this requirement with LogicMonitor before implementation, as the setup process for domain separated instances is different. For information on how to set these up, see Installing LMDX with Domain Separation.

Configuring the Edwin AI ServiceNow integration with LMDX involves the following:

  • Request and install the LMDX application from the ServiceNow Store
  • Create a ServiceNow integration service account.
  • Configure credentials in both Edwin AI and the LMDX application.
  • Activate and review the default LMDX configuration record.
  • Validate incident creation, updates, and callbacks.

Requirements

To configure LMDX, you need the following endpoints and credentials:

  • ServiceNow Admin Access—A ServiceNow user account with the administrator role
  • ServiceNow Integration Service Account—A dedicated ServiceNow account with the x_lomo_dx.api_user role
    You may also need the snc_internal role.
  • ServiceNow Instance URL—The endpoint ServiceNow instance URL
  • ServiceNow Credentials—A username and password for the integration service account
  • Edwin AI Endpoint—The Edwin AI endpoint URL for your organization
  • Edwin AI API Callback Credentials—Credentials for LMDX authentication with the integration_write permission
  • Secure Credential Exchange Path—A secure platform to share sensitive credentials and secrets
  • Test Window—Approved time window to validate incident creation and update behavior

Recommendation: Configuring LMDX requires action in both ServiceNow and Edwin AI. During the process, consider the following separation of responsibilities between LogicMonitor and the user:

Customer / ServiceNow Owner

  • Requests and installs LMDX
  • creates the integration service account
  • maintains ServiceNow credentials
  • confirms required ServiceNow fields, routing, and workflow behavior

LogicMonitor / Edwin Owner

  • Provides the Edwin AI endpoint and credential values
  • guides Edwin AI configuration with the ServiceNow instance details
  • supports Edwin-side validation and troubleshooting.

Shared

  • Review and validate create, update, callback, resolve, reopen, close, and cancel behavior.

Configuring LMDX

Installing the LMDX Application

  1. Navigate to the ServiceNow Store and request the LMDX application.
  2. After the request is approved, install the LMDX application from the store page.
  3. In the ServiceNow application menu, locate the LogicMonitor Data Exchange application.
  4. Select the installed application record and confirm that the LMDX application is version 3.1.0 or later.
  5. Note the following details for validation and support:
    • ServiceNow instance name
    • ServiceNow release version
    • LMDX version

Note: Keep the following in mind when installing the LMDX application:

  • If the application is not visible or the request is not approved, contact your LogicMonitor implementation owner or support contact before continuing.
  • Do not configure credentials until the LMDX application is installed and the menu is visible.
  • If you are upgrading from an existing LMDX installation, complete the installation or upgrade first, then follow the post-upgrade checks later in this guide before validating production traffic.

Creating a Service Account

Create a ServiceNow user record to allow Edwin AI to access the instance, for example an integration service account. For more information, see Create a user from ServiceNow.

Include the following when creating the user record:

  • Apply the x_lomo_dx.api_user role created when you install the LMDX application.
  • (Optional) Apply the snc_internal role if required by your ServiceNow environment for API access.
  • Set the account to Active.
  • Set the user type to Machine or Integration, matching the label on your ServiceNow release.
  • Deselect the Password needs reset checkbox.

Using a secure exchange platform, provide the username, password, and instance URL for this service account to your Edwin AI administrator. The administrator can add the user to your Edwin AI configuration. Your ServiceNow administrator can confirm that the integration account has the table and field access needed to create, update, and read the records used in your workflow.

Note: You can enable the Web Service Access Only setting for the account. This will ensure that the service account can only interact with the instance via web services, and cannot be used to log into the SN instance from the user interface. For more information, see ServiceNow documentation.

Configuring Authentication Properties

To configure authentication in the LMDX application, do the following:

  1. Request the following account details from your Edwin AI administrator:
    • The Edwin AI endpoint for your organization
    • The Edwin AI client ID and secret used for for ServiceNow and LMDX authentication.
    • Confirmation that the credentials include the integration_write scope
  2. In the LMDX application, navigate to Configuration properties > Outbound Request properties.
  3. In the LMDX Endpoint field, enter the Edwin AI endpoint URL.
  4. Enter the Edwin AI credential values shown for your LMDX version (3.x.x) based on the following:
    • If your LMDX configuration displays the API key field, enter the Edwin AI API key.
      Deselect Indicates if client credentials should be used for authentication with Edwin instead of the API key.
    • If your LMDX configuration displays Client ID and Client Secret fields, enter the Edwin AI client ID and client secret.
  5. Select Save.
LMDX integration configuration

Note: If the expected fields are not visible, confirm LMDX version 3.0 or later is installed.

The LMDX Config record properties are used when creating new configuration records, and can be safely ignored at this point. For more information, see Creating a new Table and Artifacts.

Completing the Default Configuration

LMDX includes packaged configuration records for common ServiceNow data types such as Incident, Knowledge Base, CMDB, and Change Request. These records are disabled by default.

After saving the LMDX authentication properties in the application, activate and review the default LMDX configuration record using the following steps. For the standard Edwin AI incident integration, configure the default Incident record first.

LMDX configurations page

Configuring Default Incident Record

  1. In the LogicMonitor Data Exchange application, navigate to Configuration properties.
  2. Select the default configuration record.
  3. Select the Active checkbox.
  4. Select the Inbound tab and do the following:
    1. Select one or more Trigger fields.
      Trigger fields instruct LMDX to update Edwin AI when the associated field changes.
    2. (Optional) Set a Condition to filter the records that should be processed.
    3. (Optional) Select one or more Trigger Fields to act as Important update fields.

Recommendation: Select Updated and State as default Trigger Fields.

  1. Select the Outbound tab and do the following:
    1. Select one or more fields as Trigger fields, as needed.
      These fields instruct LMDX to send an update back to Edwin AI when the associated field changes.
    2. (Optional) Set a Condition to filter the records to be processed.
    3. (Optional) Select one or more Trigger Fields to act as Important update fields.

Recommendation: Select Updated and State as default Trigger Fields.

  1. Select Save.
LMDX application default incident record

Activating LMDX Scheduled Jobs

Scheduled jobs in LMDX process outbound callbacks and updates from ServiceNow to Edwin AI. To configure scheduled jobs, do the following:

  1. In the LogicMonitor Data Exchange application, navigate to LMDX scheduled jobs.
  2. In the Name dropdown, locate the LMDX outbound payload processing job for your LMDX version.For example, select “LMDX – Process outbound payloads” or “Process Outbound Payloads.”
  3. In the scheduled job record, confirm Active is selected.
  4. Select Save.

Note: ServiceNow may install scheduled job packages in a disabled state. LMDX outbound updates and callbacks will not process until the outbound payload scheduled job is active.

Validating the LMDX Connection

To confirm that ServiceNow / LMDX can reach Edwin AI, do the following:

  1. In the LogicMonitor Data Exchange application, navigate to Configuration properties.
  2. Select Validate.
    A notice appears when validation completes successfully.
  3. If validation fails, confirm the Edwin AI endpoint, credential value, and integration_write scope.
    For more information, see Configuring Authentication Properties.
  4. Once the correct values are applied and saved, Select Validate.

LMDX is now active and ready to process data between Edwin AI and your ServiceNow instance.

Updating LMDX for ServiceNow Case Management

Note: Perform this procedure only if you use ServiceNow Customer Service Management (CSM).

If leveraging ServiceNow’s Customer Service Management (CSM) package, you will need an XML file that creates additional LMDX configuration entries for Customer Service cases. This can be provided on request from the Edwin AI team. 

Once you have the XML file, do the following to update LMDX to work with CSM:

  1. In the LogicMonitor Data Exchange application, navigate to System Update Sets > Retrieved Update Sets.
  2. Select Import Update Set from XML and import the XML file. 
  3. In the Retrieved Update Sets section, Select the new update set record. 
  4. (Optional) Select Preview Update Set to review the content for errors or conflicts.
  5. Select Commit Update Set to apply it to the instance.
  6. Navigate to in Configuration > Configuration to view and activate the new configuration
  7. Select the Inbound tab to access the Table Transform Map for a list of the currently set up fields.
    Table Transform Map inbound tab
  8. Select the Outbound tab to configure the data and the conditions under which the LMDX application sends updates to Edwin AI.
    Table Transform Map outbound tab
  9. Select Update.

Note: By default, the provided Update Set integrates with the “sn_customerservice_case” table. If you need to integrate with a different table (for example “sn_customerservice_repair_case”) update all occurrences of “sn_customerservice_case” in the XML file to the required table name.

Recommendation: Validate that LMDX processes data successfully before using the integration for production incident handling.

Confirm the following actions are complete:

  • The default configuration record is active.
  • Required trigger fields are properly selected.
  • Important update fields are configured if needed.
  • Required incident fields are mapped correctly for the target ServiceNow instance.
  • Edwin AI successfully creates a test ServiceNow incident.
  • Edwin AI successfully updates the test ServiceNow incident.
  • ServiceNow / LMDX sends the expected update or callback to Edwin AI.

If your organization utilizes separate environments (for example development, test, UAT, sandbox, production), validate field mappings for each specific instance.

If any validation fails, gather the following details to expedite support:

  • ServiceNow instance name and release version
  • LMDX version
  • Edwin AI portal name
  • Test incident number and timestamp
  • Specific error messages or the failed state
  • If failure occurs during create, update, callback, resolve, reopen, close, or cancel.