LM Logs Tips: Alert-to-Logs Workflow for Ops Team | Logs for Lunch
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.
Patrick Sites, product architect, shares tips:
- Open logs in context with metrics from alerts, resources, dashboards, and Service Insights
- Ask LogPilot natural language queries, such as "find errors by resource"
- Share a log query library with private, shared, and public folders
- Set log partitions and retention with separate ingestion limits
- Schedule CSV log reports for ranges beyond the 31-day query limit
LM Logs is built for ops, with retention between 7 days and 2 years in hot storage.
🔗 LogicMonitor log management: https://www.logicmonitor.com/platform/log-management
🔗 LM Logs overview: https://www.logicmonitor.com/platform/logs
Subscribe to the LogicMonitor channel to catch the next Logs for Lunch session.
#LMLogs #LogAnalysis #LogAnomalyDetection #LogPilot