Operations | Monitoring | ITSM | DevOps | Cloud

LM Logs troubleshooting starts at the alert. This Logs for Lunch session shows ITOps teams an alert-to-logs workflow and lesser-known LM Logs tips. Ryan Matuszewski demos a Tomcat application error. From the alert's Logs tab, he moves through log anomaly detection, All Logs, Log Patterns, and Log Analysis sorted by sentiment. He then opens the Logs page with the alert time range, and the same steps work for any alert type.

Autonomous IT requires three things: complete, AI-ready data; connected context; and governed action. In LogicMonitor's 2H announcement, we show enterprise IT and ITOps leaders how each layer works. LogicMonitor is the AI-first platform for Autonomous IT. This update covers the three layers behind autonomous IT operations as the category moves from systems of intelligence to systems of action. Your team decides when Edwin AI moves from recommending an action to taking it.

AI investigation for IT operations finds the likely root cause of an incident and shows the evidence behind it. This video covers how deep AI investigation works for ITOps, SRE, and platform engineering teams using LogicMonitor's Edwin AI. Engineers lose time stitching together alerts, logs, and recent changes after an alert fires. Deep AI investigation hands that first pass to AI agents, so your team starts closer to the fix. Edwin AI, LogicMonitor's AI agent for ITOps, correlates alerts, identifies root causes, and recommends remediation.