Loading full navigation.

Agent Studio for Edwin AI

One Control Plane For Your AI Agents

Manage your Edwin AI agents, control which data and tools they can use, and keep agent behavior aligned with your standards.

Give AI agents more context without giving up control

AI agent management and governance

Control how Edwin AI agents work across your environment

Agent Studio brings AI agent administration, access, configuration, and oversight into one governed experience.

Manage
Govern
Configure
Observe
Extend

Know which agents are active and what they do

Agent Studio gives administrators one place to understand and manage the Edwin AI agents available to their organization.

  • Enable or disable supported Edwin AI agents from a centralized catalog
  • Review each agent’s purpose, capabilities, supporting MCP servers, and tools

Decide what each agent is allowed to use

AI agents become more useful as they gain access to operational context and tools. They also need clear boundaries.

  • Control which integrations and MCP tools are available to supported agents
  • Keep access aligned with customer-level permissions, governance, and operational requirements

Shape agent behavior around your operating model

Your teams already have runbooks, escalation patterns, reporting standards, and ways of working.

  • Configure supported tools to reflect operational requirements

See what an agent did, what it used, and what happened next

Agent Observability gives teams visibility into agent performance and behavior so admins and subject-matter experts can understand how Edwin AI reached an outcome and identify where an interaction needs improvement.

  • Review usage, response quality, latency, outcomes, context, data sources, and tool activity
  • Identify failed tool calls, missing data, degraded workflows, and other issues that affect agent performance

Connect Edwin AI to your broader agent ecosystem

Give Edwin approved access to third-party tools and data, connect with other AI systems through MCP and A2A patterns, and bring LogicMonitor context into supported custom workflows.

  • Connect agents with operational context across LogicMonitor and approved third-party systems
  • Extend governed LogicMonitor context into custom AI workflows and agent experiences where supported

MCP Integrations

Make every operational system agent-ready

LogicMonitor MCP connects Edwin AI with the systems teams already use across observability, digital experience, ITSM, automation, knowledge, collaboration, and cloud operations. It helps AI agents gather the right data, respect enterprise controls, and return useful context without forcing teams into a new workflow.

250+

tools across 30 categories for workflow-oriented access to monitoring context

One

governed endpoint for LogicMonitor, Edwin AI, and Catchpoint context

Domain-specific AI

AI grounded in real IT operations

Edwin AI reasons over operational context including alerts, metrics, logs, topology, tickets, changes, runbooks, and knowledge. That context helps agents explain what changed, what is affected, the likely cause, and the next action.

67%

ITSM incident reduction

STRATEGIC AI ECOSYSTEM

Agentic ITOps with LogicMonitor, OpenAI, IBM Red Hat, and AWS

Edwin AI is designed for an open agent ecosystem built around advanced reasoning, automation, model flexibility, and agent-to-agent collaboration. LogicMonitor’s work with OpenAI, IBM Red Hat, and AWS extends that foundation, while MCP provides a governed way for agents and operational systems to exchange context and coordinate action.

88%

alert volume reduction

Real Agentic ITOps ROI

313% ROI achieved with LogicMonitor Edwin AI

A commissioned study conducted by Forrester Consulting on behalf of LogicMonitor found that a composite organization achieved 313% ROI over with a 6 month or less payback with LogicMonitor Edwin AI.

<6

months payback period

313%

ROI

Leading companies don’t just monitor—they Envision peak performance

See how IT teams big and small cut alert noise, resolve issues faster, and keep networks running at full speed.

BY THE NUMBERS

Edwin AI: Built to deliver impact

0 %
less incident workload
0 hrs
saved per incident
0 %
eduction in MTTR

GET ANSWERS

Agent Studio FAQs

Get answers to common questions about managing, configuring, and governing Edwin AI agents.

What is Agent Studio for Edwin AI?

Agent Studio is the centralized management experience for Edwin AI agents. It gives administrators visibility into the agents available to their organization, what each agent is designed to do, which MCP servers and tools support it, and which supported capabilities the agent can access.

Can I customize Edwin AI agents in Agent Studio?

Agent Studio is designed to provide governed configuration rather than unrestricted modification of agent code. Depending on the capability and release, teams can configure elements such as agent availability and tool access, while maintaining enterprise controls.

Can customers build their own AI agents?

Agent Studio is expanding toward deeper agent customization and custom-agent experiences. Availability of net-new customer-built Edwin AI agents depends on the applicable product release or program. LogicMonitor MCP can also provide governed LogicMonitor context to supported customer-built AI agents and workflows outside Edwin.

How does Agent Studio control which tools an agent can use?

Agent Studio works with MCP-based tool access to define which supported integrations and capabilities are available to an agent. This gives teams a central way to grant useful operational access while preserving organizational permissions and governance boundaries.

How can teams understand what an Edwin AI agent did?

Agent Observability is designed to provide visibility into agent inputs, context, tools and data sources used, responses, failures, latency, and outcomes. This gives administrators and subject-matter experts evidence they can use to audit behavior and improve performance.

How is Agent Studio different from LogicMonitor MCP?

Agent Studio is the management and governance experience for Edwin AI agents. LogicMonitor MCP is the interoperability layer that gives supported agents and workflows governed access to tools and operational context. Agent Studio controls the agent; MCP connects it to approved systems.

How is Agent Studio different from Agent Workflow Studio?

Agent Studio focuses on managing, configuring, and governing individual agents. Agent Workflow Studio is designed to combine agents, tools, scripts, APIs, and actions into larger operational workflows. The two capabilities address different layers of agentic operations.

Does Agent Studio support existing enterprise permissions?

Agent Studio is being developed around enterprise governance requirements including RBAC, tool-level access controls, auditability, usage visibility, and governed MCP access. Specific controls depend on the product release and connected systems.

Your path to self-healing IT starts with Edwin AI