Cloud Log Monitoring & Root Cause Analysis | Logs for Lunch

Cloud log monitoring in LogicMonitor connects a service alert to the log event behind it. This Logs for Lunch July demo is for ITOps, CloudOps, and SRE teams.

Tom Chavez hosts Ismath Mohideen (Product Marketing) and Nick Doane (Senior Sales Engineer). They cover cloud observability and multi-cloud monitoring across AWS, Azure, GCP, and OCI in LM Envision, using cloud provider APIs with no extra collectors.

• LM Service Insights shows an "AWS Online Store" service at 50% availability, with an S3 bucket returning HTTP 403 errors.
• LM Logs uses machine learning for log anomaly detection and flags the anomalous entry.
• Root cause analysis finds a PutBucketPublicAccessBlock event (an S3 API call AWS CloudTrail logs record) by a Jenkins automation user.
• Log Tracked Queries turn log counts into time-series metrics with alert thresholds.
• Cloud cost optimization covers multi-cloud spend and EC2 rightsizing recommendations.

The Q&A covers stateful vs. time-window log alerts and OCI log ingestion.

🔗 LogicMonitor log management: https://www.logicmonitor.com/platform/log-management
🔗 LM Logs overview: https://www.logicmonitor.com/platform/logs
🔗 LogicMonitor cloud observability: https://www.logicmonitor.com/cloud

Subscribe for a new Logs for Lunch demo each month.

#CloudLogMonitoring #CloudObservability #LogAnomalyDetection #RootCauseAnalysis #MultiCloudMonitoring