2026-June 11 Edwin AI Release Notes (v.14.1)

The LogicMonitor Data Exchange (LMDX) now offers several new and enhanced features that improve ServiceNow integration and general usability. This enhancement includes the following features:

• A new Payload Manager role allows authorized users to view inbound and outbound LMDX payloads for easier troubleshooting.
• A new Validate action on the LMDX configuration page sends a test request from LMDX to Edwin, and confirms the request succeeds.
• ServiceNow incidents created from Edwin AI insights now include related affected CIs, enhancing incident context and service impact analysis.
• Incidents now support Load Historical Records actions, change requests, and task-related records, enabling you to send relevant historical data into LMDX.
• Outbound transform mappings now include created and updated timestamps where applicable, enhancing data completeness for recommendation workflows.
• The Load Historical Records action now provides enhanced performance and reliability.

To access the new application, install the latest version of LogicMonitor Data Exchange from ServiceNow.

To access the Load Historical Records features, you must configure Incident and Change Request ingestion for Edwin AI and define filters or limits for historical data loading as needed.

For more information, see Change Requests Agent and Similar Incidents Agent in product documentation.

You can now click the hyperlinked title of an insight or alert added as context in the Edwin AI Agent Homepage to open the corresponding Insight Details or Alert Details page. This enables you to validate findings, review source data, and continue investigations without disrupting your workflow.

To access this feature, download the newest version of LogicMonitor Data Exchange from ServiceNow. Navigate to the Edwin AI Agent Homepage and select the title of an insight or alert included in the context panel.

For more information, see Installing LMDX in product documentation.

You can now integrate Edwin AI with Terraform Cloud to streamline alert workflows. This integration provides real-time status and resolution update synchronization through a webhook with Terraform Cloud.

You must generate a new Edwin client ID and secret token to establish Basic Authentication, and create a webhoook within Terraform Cloud to send alert information to Edwin AI.

To generate a new client ID and secret token in Edwin AI, see Edwin AI API Credential Management in product documentation.

You can now connect Edwin AI to Elastic MCP Server using the Edwin AI Elastic Integration. This enables Edwin to observe queries to Elastic MCP server.

To access this feature, you must have the following Elastic credentials:

• ELASTIC_URL
• ELASTIC_API_KEY
• ELASTIC_VERIFY_SSL (FALSE by default)

For more information, see Edwin AI Elastic Integration in product documentation.

Edwin AI now supports multiple HTTP formats that include additional content in return payloads. This enhancement enables Edwin to parse inbound payload information into separate fields for correlation and contextualization within insights.

Edwin AI now supports the {"payload": {"id": 1}, {"url": "https://xyz"}} payload format, as well as the following fields:

• • HTTP.IncidentIdentifier
  • HTTP.URL
  • HTTP.state
  • HTTP.ClientID
  • HTTP.CI