LogicMonitor Data Exchange Upgrade to 3.1.0

Upgrading to LMDX version 3.1.0 or later involves installing the latest app from the ServiceNow Store, restoring existing scheduled jobs, and validating default configurations after the new version installs.

Version 3.1.0 of the LogicMonitor Data Exchange (LMDX) adds and enhances the following features:

• A new Payload Manager role enables authorized users to view inbound and outbound LMDX payloads for easier troubleshooting.
• A new validation action on the LMDX configuration page sends a test request from LMDX to Edwin (only available for non-domain separated environments).

• ServiceNow incidents created from Edwin AI insights now include affected CIs.
• Incidents, change requests, and task-related records now support the Load Historical Records action.
• The Load Historical Records action provides enhanced performance and reliability.
• Outbound transform mappings include created and updated timestamps where applicable.

Outbound payloads from ServiceNow to Edwin AI are not sent to LMDX versions older than 3.1.0. No data is lost—payloads continue to generate and queue as normal, but they do not transmit until the new configuration is completed. Inbound payloads from Edwin AI to ServiceNow continue to process, and outbound payloads are still generated and stored in ServiceNow’s outbound queue.

When the required upgrade is completed, all queued outbound payloads are sent during the next scheduled job execution. By default, scheduled jobs run every minute.

Requirements for Upgrading LogicMonitor Data Exchange

To upgrade LogicMonitor Data Exchange (LMDX) with domain separation, you must do the following:

• Download the latest LMDX package from the ServiceNow Store.
  For more information, see LogicMonitor Data Exchange from ServiceNow.
• Install LMDX in Edwin AI.
  For more information, see Installing LMDX.
• Update configuration files in the LMDX ServiceNow dashboard to reflect new endpoint associations.
• Redeploy the updated integration.

If any required configurations are not applied, outbound processing fails and logs the error.

Upgrading LogicMonitor Data Exchange

1. Download the latest LMDX package from the ServiceNow Store.
   For more information, see LogicMonitor Data Exchange from ServiceNow.
2. In ServiceNow, navigate to Scheduled Jobs.
   For more information, see Schedules jobs from ServiceNow.
3. Select the job you previously used for outbound payload prior to upgrading. 
4. Update the job script by doing the following:
   1. In the Script field, enter the following script exactly as written:

// Script to reset Scheduled jobs.
var instanceUrl = gs.getProperty("glide.servlet.uri");
var ctr = 0;
var sysAutoGR = new GlideRecord("sysauto_script");
sysAutoGR.addEncodedQuery("sys_scope=f9b2746bdba54110a8a86fccd3961962^sys_idINfd91b431db65a110fd60273a139619d3,a11f354e1b038d108414cb751a4bcb36,b851b4cd87088b50e467ca6e0ebb35ed");
sysAutoGR.query();
while(sysAutoGR.next()) {
    gs.info("-----------");
    ctr++;
    if(sysAutoGR.active == false) {
        gs.info(ctr + ". Scheduled Job " + sysAutoGR.name + " is set to false.");
        sysAutoGR.setValue("active", true);
        sysAutoGR.update();
    }
    var fullUrl = instanceUrl + sysAutoGR.getLink(false);
    gs.info(ctr + ". Active status of Scheduled Job " + sysAutoGR.name + " is " + sysAutoGR.active);
    gs.info("URL is " + fullUrl);
}

2. (Optional) On domain-separated instances, the scheduled job script may be overwritten during the upgrade. To restore it, navigate to LogicMonitor Data Exchange > Scheduled Jobs > LMDX – Process outbound payloads and update the script as follows:
   new x_lomo_dx.outboundRequestUtils(current.getUniqueValue());
3. Select Update.

5. (Optional) If validating the upgrade for a domain-separated environment, do the following:
   1. To validate that your specific environment settings were preserved, run the following validation script:

// Script to validate default configuration records
var instanceUrl = gs.getProperty("glide.servlet.uri");
var configGr = new GlideRecord("x_lomo_dx_config");
var ctr = 0;
configGr.addEncodedQuery("sys_idIN5a206254879b62d0e467ca6e0ebb3507,d0d1fc3d1b678910b6fa21be6e4bcbf5,a8fe0ac8db61a910fd60273a139619d2,f69413eb1b83a6908f7c5244604bcbfa");
configGr.query();
while(configGr.next()) {
    ctr++;
    var activeStr = "is not active.";
    if (configGr.active == true) {
        activeStr = "is active";
    }
    gs.info("-----------");
    gs.info(ctr + ". Configuration Number " + configGr.number + " " + activeStr);
    gs.info("URL is " + configGr.getLink(false));
    gs.info("Outbound business rule is active = " + configGr.business_rule.active + ".");
    if (gs.nil(configGr.trigger_fields)) {
        gs.info("Trigger Fields is empty" + configGr.trigger_fields + ".");
    } else {
        gs.info("Trigger Fields " + configGr.trigger_fields);
    }
}

2. Navigate to LogicMonitor Data Exchange > LMDX Properties and use the “Validate” action to ensure your API credentials and URL remain correctly configured following the upgrade.

Your LMDX environment is now upgraded to version 3.1.0.