Edwin AI Agents Overview
Last updated - 08 December, 2025
Edwin AI Agents are embedded in the Edwin platform and enable you to interact with insights, alerts, and data. These agents streamline common tasks such as data exploration, incident investigation, and documentation retrieval by responding to user prompts with contextual, AI-generated results.
The Edwin AI Agent chat is available on the Agent homepage for interacting with data and insights. The Edwin AI Agent chat is also integrated into the Insight Details page so you can directly troubleshoot an insight. You can ask follow-up questions, clarify details, or request additional context to better understand what is happening and why.


The following table provides information for each Edwin AI Agent to help guide your interactions:
| Agent Type | Description | Types of Requests | Example Prompts | Additional Configuration Needed |
| IT Ops Agent | Recommends triage actions, suggests troubleshooting steps, and drafts root cause analyses (RCAs) to accelerate incident resolution. | Remediation steps, summaries, and general operational questions | What is the typical remediation for frequent BGP session flaps between core routers? Can you generate a concise incident update for internal teams? | No |
| Insights Agent | Answers questions about any part of an insight, alert, or event to quickly understand what is happening and why. | Insight details, alert frequency, and customer impact | Summarize the key impacted services. What is the location or version of the impacted CIs? | No |
| Charts Agent | Creates real-time charts from Edwin AI data and lets you filter data to spot issues early. | Trend analysis and alert distribution | Show me the number of critical alerts in the EMEA data center over the last month. Which CI received the highest critical alerts in the last 24 hours? | No |
| Public Knowledge Agent | Answers questions using vendor documentation and other third party sources to help troubleshoot faster without leaving Edwin. | Vendor documentation, product issues, and known bugs | What are the recommended configurations for Cisco ASA devices? Is there a known issue on Cisco Routers version 17.6.3? | No |
| Metrics Agent | Surfaces information and answers questions about metrics data for a specific alert. | Alert metric data | What were CPU, memory, and disk metrics for this alert? What is the current value for CPU usage? | No |
| Similar Insights Agent | Finds and analyzes related insights based on event names to help explore connections, frequency patterns, and typical root causes. | Related insight discovery, frequency patterns, and root cause analysis | Show me similar insights. How often does this type of issue occur? What is the typical root cause analysis for similar insights? | Yes For more information, see Similar Insights Agent. |
| Similar Incidents Agent | Identifies and surfaces past incidents that closely match the current one, providing relevant root cause analysis (RCA) and resolutions to improve consistency. | Historical incident lookups, RCA comparison, and remediation recommendations | Find similar past incidents for this insight. What was the root cause in similar incidents? Show me how previous incidents with this alert were resolved. | Yes |
| Private Knowledge Base Agent | References your organization’s documentation to enable Edwin to generate analyses and respond to questions grounded in your verified processes. | Internal documentation lookups, process-based guidance, and article-matched analyses | Reference our internal KB and tell me the recommended workflow for triaging this alert. Do we have any SOPs on how to resolve this issue? | Yes |
| Change Request Agent | Identifies recent or ongoing change requests tied to impacted Configuration Items (CIs) so you can determine whether a change contributed to an issue. | Active or recent change request lookup, CI-related change correlation, and change-driven incident verification | Are there any recent or ongoing change requests related to this CI? Could any recent changes have contributed to this issue? | Yes |
Recommendation: To use agents effectively, ensure you ask specific questions and avoid vague language. Include specific details or CI names when relevant, and break complex prompts into individual requests. Always verify results before taking action, and share feedback to help improve agent performance.
Requirements for Using Edwin AI Agents
To use Edwin AI agents, ensure the following:
- Have access to Agent AI SKU.
- Have Correlation Models running and insights generated in your Edwin portal.
- A LogicMonitor user with the Edwin AI access, includes users with “View only” permissions.
For the Metrics AI Agent to access all metric data for your alerts, ensure that you have an API Edwin AI user with “View” permissions set for all resources.
To use the Similar Agent, Private Knowledge Base Agent, and Change Request Agent, you need the LMDX integration with the following:
- Enabled to send Edwin AI each record type
- Configured to include the ingestion settings and trigger fields needed for LogicMonitor to receive and update all relevant records.
For more information, see Installing LMDX.
Using Edwin AI Agents to Investigate an Insight
- In LogicMonitor, navigate to Edwin AI > select
AI Agent. - Select an insight, then select
Details, to open the conversational interface.
- Review the insight summary and details in the right-hand panel.
- In the chat window, enter the following sample questions:
- “What are the locations for the impacted CIs in this insight?”
- “Are there any known issues reported on the web about Twilio devices?”
- “Plot the number of alerts per CI over the last six months.”

- Review the agent response.
- For web results, Edwin includes source links.
- For charts, Edwin generates information in the AI Agent Output tab.