LogicMonitor announced a collaboration with IBM to integrate IBM watsonx and Red Hat Ansible Automation Platform with automation coding assistant into Edwin AI, LogicMonitor’s AI Agent for IT Operations.
This integration is designed to help customers scale autonomous IT operations by proactively detecting, diagnosing, and resolving issues before they impact service reliability.
LogicMonitor’s Edwin AI helps customers identify anomalies and, together with Red Hat Ansible Automation Platform, translate insights into action. When an issue arises, Edwin AI uses Ansible Automation Platform to recommend or trigger the appropriate Ansible Playbook. If no playbook exists, the automation coding assistant within Red Hat Ansible Automation Platform and IBM watsonx automatically generate one to help troubleshoot or restore services automatically. All of this can be achieved by the joint solution for accelerated reaction and response times. Once identified, automation is orchestrated via Red Hat Ansible Automation Platform, enabling IT teams to control and approve it as trusted automation before it executes. Additionally, automation can be scaled across teams without specialized training.
“This is automation with frontier intelligence,” said Karthik SJ, General Manager of AI, LogicMonitor. “By combining LogicMonitor’s AI-powered observability with Red Hat Ansible Automation Platform and watsonx, we can offer customers a trusted ally designed to anticipate and resolve issues autonomously, freeing teams to focus on building the future.”
The integration is designed to deliver less firefighting and more innovation. Enterprises can gain confidence from predictive resilience, efficient incident response, and the ability to accelerate self-healing across hybrid and multi-cloud estates, which is expected to drive these benefits:
- Stop incidents before they happen: Edwin AI identifies abnormal behavior across infrastructure, helping teams prevent outages before they affect critical services.
- Fix problems automatically, not manually: The system is designed to resolve incidents from detection to remediation, reducing handoffs and on-call fatigue.
- Recover faster when incidents occur: Automated resolution shortens response times during outages, helping keep business-critical services online and minimizing disruption.
- Extend automation to more teams and environments: Teams can standardize self-healing workflows across hybrid and multi-cloud environments without relying on deep automation expertise.
“Logic Monitor’s Edwin AI platform combined with IBM watsonx and Red Hat Ansible Automation Platform enables automated prevention, detection, and remediation of infrastructure issues to help enterprises achieve less down time and more efficient enterprise IT operations,” said Nick Holda, Vice President, AI Technology Partnerships at IBM. “This is a great example of how IBM and our ecosystem partners can bring together complimentary technologies to offer new end-to-end solutions to our clients."
LogicMonitor continues to innovate with IBM’s watsonx suite of products to offer solutions designed to help enterprises anticipate, automate, and renew their operations in an increasingly complex digital era.
The Latest
In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ...
In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...
When most people think about cybersecurity, they picture firewalls, encryption, and access controls — technical tools designed to protect systems and data. But beneath the technology lies a deeper set of principles about trust, decision-making, and resilience ... The best leaders don't eliminate risk. They manage it intelligently. And in many ways, cybersecurity offers a surprisingly useful playbook for doing exactly that ...
Many organizations assumed their infrastructure strategy was settled. It had been implemented, optimized and built into long-term plans. Recent changes in technology and vendor consolidation are forcing a second look. Cloud outages and licensing changes have exposed how much dependency exists on a small number of platforms. As a result, organizations are reevaluating whether those decisions still hold up under current conditions ...
Edge AI is strategically embedded in core IT and infrastructure spending across industries, according to the 2026 Edge AI Survey from ZEDEDA. The research shows that 83% of C-suite and IT executive respondents say edge AI is important to their core business strategy ...
As AI adoption accelerates, operational complexity — not model intelligence — is becoming the primary barrier to reliable AI at scale, according to the State of AI Engineering 2026 from Datadog ... The report highlights a compounding complexity challenge as AI systems scale ... Around 5% of AI model requests fail in production, with nearly 60% of those failures caused by capacity limits ...
For years, production operations teams have treated alert fatigue as a quality-of-life problem: something that makes on-call rotations miserable but isn't considered a direct contributor to outages. That framing doesn't capture how these systems fail, and we now have data to show why. More importantly, it's now clear alert fatigue is a symptom of a deeper issue: production systems have outgrown the current operational approaches ...
I was on a customer call last fall when an enterprise architect said something I haven't been able to shake. Her team had just spent four months trying to swap one AI vendor for another. The original plan said three weeks. "We didn't switch vendors," she told me. "We rebuilt half our integrations and discovered what we'd actually been depending on." Most enterprise leaders don't expect that to be the experience ...
Ask any senior SRE or platform engineer what keeps them up at night, and the answer probably isn't the monitoring tool — it's the data feeding it. The proliferation of APM, observability, and AIOps platforms has created a telemetry sprawl problem that most teams manage reactively rather than architect proactively. Metrics are going to one platform. Traces routed somewhere else. Logs duplicated across multiple backends because nobody wants to be caught without them when something breaks. Every redundant stream costs money ...
80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...