Logs Leveled Up: April Product Power Hour Recap
Overview This month’s Product Power Hour was all about unlocking deeper visibility into your pipelines with enhanced log observability. We walked through the new structured logging UI, answered live questions, and gathered real-time feedback from our amazing community of practitioners. Whether you're debugging policy failures or preparing for audits, these enhancements are designed to save time and reduce friction—without sacrificing context. Key Highlights ⭐Structured Logs in the UI: Filter, search, and drill into logs directly from the interface to pinpoint policy outcomes and troubleshoot faster. ⭐Root Cause Clarity: See exactly why a policy passed or failed—including rule-level reasoning—without diving into raw code or configs. ⭐Audit-Friendly Workflows: Export logs to support compliance efforts with traceable and structured outputs. ⭐API Support: All log data is available via API, so you can integrate it with your SIEM or other observability tools. ⭐Live Feedback: Attendees shared feature ideas and logging improvements that are now being routed to our product team. Q&A Q: Can I access logs outside of the UI? A: Yes—logs are accessible via API for full integration into your observability stack. Q: What is best practice to onboard a device for logs—LogSources? Or do we have to enable LM Logs on each individual device? A: The best practice depends on the type of logs and source. If logs are exposed to services like the Windows Event Log, they can be ingested without per-device configuration. Otherwise, you’ll need an agent-based solution (e.g., FluentD, Fluent Bit, or LM’s upcoming OTEL collector). Device-by-device setup is not always necessary—LogSources can help standardize collection where supported. Q: Can we use WMI/WinRM for agentless log ingestion on Windows Servers—not for OS logs, but for app/service logs? A: Only if the application logs are exposed through the Windows Event Log service. If the logs live in a file on disk or aren’t exposed through standard logging services, an agent will be required to ingest them. Customer Call-outs ⭐“One thing that would help our uptake of logs is a more ‘end-to-end’ setup guide.” ⭐“The magic word: Correlation!” What’s Next 🪵Logs for Lunch May 14 –A Window into your Windows Logs ⚡Product Power Hour May 22 - Exploring Resource Explorer June 17 - Cost Optimization Want to check out previous Product Power Hours? Explore the Product Power Hour Hub in LM Community! 🍽️User Group Dinners Connect in person with other LM users in your city over dinner and real talk. Share wins, swap stories, and grow your network - RSVP here: Chicago – May 6 Nashville – May 13 Seattle - June 17 Portland - June 18 London @ Elevate - June 24 💻 Virtual User Groups Visit our LM Community User Group Hub for more details on upcoming virtual sessions. AMER East – June 3 AMER West – June 5 EMEA – June 10 APAC – June 12 🌍 Elevate Community Conferences Our flagship in-person event series is back! Connect with peers, attend expert-led sessions, and get hands-on product experience. Elevate 2025 will showcase the latest innovations in AI-powered observability, empowering enterprises to optimize their modern data centers. Sydney – May 29 London – June 25 Pre-Elevate LM Training | LIVE Already attending Elevate? Join us in Dallas and London a day early to earn your first Logs Badge through immersive, instructor-led training and hands-on labs. Perfect for new users or anyone looking to sharpen their logging skills. Register today! London – June 24 Additional Resources If you missed any part of the session or want to revisit the content, we’ve got you covered: Review the slide deck here Want to see the full session? Watch the recording below ⬇️
