v7.0 Edwin AI Release Notes

You can now engage with the Edwin AI Agent from a centralized homepage without needing to access a specific insight. This new homepage offers a standalone chat experience across multiple Edwin agents. This streamlines your workflow by enabling proactive inquiries such as, “What are my top critical Insights?” with the ability to select into results and continue troubleshooting contextually.

To access this feature, navigate to LogicMonitor > Edwin AI > and select the Agent Homepage.

For more information, see Edwin AI Agents in the product documentation.

You can now integrate Edwin AI with PagerDuty to automatically create and update incidents. The integration supports both OAuth 2.0 and REST API key authentication methods and enables Edwin AI to create, acknowledge, resolve, and optionally assign incidents based on user information in PagerDuty.

You must have a PagerDuty account with administrative access, Edwin AI Client ID and Client Secret, and either OAuth 2.0 credentials or a REST API key.

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

You can now integrate Edwin AI with Dynatrace to receive event data in real time using payloads. The integration uses the Edwin Common Event Format (CEF) for structured JSON payloads. Payloads can be enriched with tags and assignments to support routing and visibility in Edwin AI and they supports severity-based routing through multiple webhook configurations.

You must have Dynatrace Operator v1.0 or later, integration permissions in Dynatrace, and an Edwin AI Client ID and Client Secret provided by your Edwin AI administrator.

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

You can now integrate Edwin AI with Jira Service Management to automate incident and event ticket creation. This new integration enables Edwin AI to create structured JSM tickets using customizable JSON payloads. It supports Jira service management (on-prem), using Personal Access Token (PAT) authentication for secure communication. Edwin-created tickets can be enriched with LM alert metadata, impacted configuration items (CIs), and can be identified through configurable custom fields.

You must configure a webhook in JSM and register Edwin AI for in-bound integration.

For more information, see the Edwin AI Jira Server Integration in the product documentation.