Product Power Hour
Created Mar 4, 2025
8 members
18 discussions
Product Power Hour is our monthly series designed to keep you in the loop on the latest and greatest from our product team — in just one power-packed hour. Each session brings real-time insights, live demos, and practical tips straight from the experts shaping the roadmap. Whether you're looking to stay ahead of what’s new, explore fresh capabilities, or hear how other practitioners are solving real-world challenges, Product Power Hour delivers valuable content and conversation in a format built for busy technical teams. This space is your central hub for all things Product Power Hour — from upcoming event registrations to full recaps of past sessions. Catch what you missed, revisit highlights, and stay connected to the evolution of our platform.
This Product Power Hour gave the community a practical look at how Internet Performance Monitoring, or IPM, is evolving . The session focused on how teams can improve visibility across the full internet stack, from network paths and employee endpoints to customer-facing digital experiences. The call centered on three core IPM lenses: network experience, workforce experience, and customer experience . Attendees saw how synthetic monitoring, real user monitoring, endpoint monitoring, Internet Sonar, Envision, and Edwin AI can work together to help teams answer critical operational questions faster, such as whether an issue is caused by the application, the network, a SaaS provider, a user device, or a broader internet disruption. Key Highlights ⭐IPM brings together synthetic monitoring, real user monitoring, and Internet Sonar to provide visibility across websites, APIs, applications, endpoints, SaaS services, cloud providers, CDNs, and network paths. ⭐In-session traceroute helps improve network troubleshooting by establishing a TCP connection before sending probes, which can result in cleaner, more complete path visibility compared to traditional traceroute approaches. ⭐Node-to-node monitoring enables teams to test connectivity across enterprise, cloud, backbone, last mile, and wireless nodes , with visibility into latency, jitter, packet loss, and path health. ⭐Workforce Experience Monitoring now includes test-level proxy configuration , allowing teams to define proxy behavior per test instead of managing proxy settings only at the individual enterprise agent level. ⭐Endpoint call quality monitoring gives IT teams visibility into Zoom and Microsoft Teams experiences , including application score, jitter, packet loss, packet drop, CPU usage, memory utilization, and geographic trends. ⭐Catchpoint data can be pushed into Envision and correlated in Edwin AI , helping teams connect external experience signals with infrastructure telemetry, identify root cause, and surface suggested remediation steps. Q&A Q: Are shared SmartBoard links dynamic and updated in real time? A: Shared SmartBoard links capture the selected timeframe, so they are static snapshots of the data from that investigation window. However, the shared view is still interactive, meaning users can click through records and explore the captured data. For a live, dynamic view, teams can put these matrixes into a custom dashboard and share that instead. Q: Why do I only see instant tests under Endpoint and not the endpoint features shown in the demo? A: Endpoint is a separate product and requires its own license. If Endpoint is not enabled in your portal, you may only see limited options, such as instant tests. Teams interested in trying Endpoint should reach out to their account executive to discuss access or a POV. Q: Can I add an endpoint to monitor an enterprise Zoom experience throughout the day? A: Yes. With Endpoint enabled, teams can monitor how an endpoint behaves throughout the day, including CPU and memory utilization, what the user accessed, and the quality of their experience while using applications like Zoom. Q: Is Internet Sonar required to drill down on endpoint data? A: No. Endpoint and Internet Sonar are separate products that provide different types of visibility. Endpoint requires an agent to be installed on workforce devices, whereas Internet Sonar provides visibility into broader SaaS and internet service issues without requiring installation. Used together, they can help determine whether an issue is isolated to a user or the workforce, or affects a larger region or service. Q: If call quality issues appear in one location, should I check Internet Sonar to see whether the issue is broader? A: Yes. If call quality issues occur in a specific area, Internet Sonar can help determine whether the issue affects other companies, regions, or services, or is isolated to your own users. Q: What is the best way to monitor end-user experience for custom integrations and microservices? A: A combination of test types is usually needed. For microservices, API monitoring is often the starting point, along with supporting checks such as DNS and network reachability. To get an aggregate view, teams can use custom dashboards and widgets that combine synthetic, endpoint, RUM, and Internet Sonar data. These views can also be pushed into Envision to compare experience data alongside infrastructure data. Q: Are Catchpoint synthetics similar to Selenium synthetics? A: Catchpoint synthetics go beyond traditional Selenium-style transaction testing. The platform breaks monitoring into different protocols and test types, including HTTP checks, full browser tests using Playwright, scripted user flows with Playwright and Puppeteer, API microservice tests, DNS checks, ping, and traceroute. This allows teams to monitor the individual protocols and services that power a user experience. Q: Can the same synthetic tests run from POPs and endpoint agents? A: The full set of synthetic monitors can run from public agents and enterprise agents. Endpoint agents are lighter weight, so they support simpler scheduled tests such as HTTP checks, traceroutes, and pings. They do not run full browser tests because endpoint devices are already running user workloads. Q: When should I use in-session traceroute? A: In-session traceroute is useful when traditional traceroute results show incomplete paths, repeated hops, or packet loss that makes troubleshooting difficult. It helps measure a cleaner path by establishing the connection before probing. Q: Can in-session traceroute be used with enterprise nodes, or is it only for backbone nodes? A: In-session traceroute can be used with any node type, including enterprise nodes and backbone nodes. Q: How do I enable in-session traceroute? A: It is a simple change in the traceroute sub-monitor type. Select in session as the sub-monitor type. Teams can also copy an existing test, run the traditional and in-session versions side by side for a few hours, compare the results, and decide whether to update more tests. Customer Call-outs 🌟“Thank you so much - It's really helpful.” 🌟“Yeah, that's very cool. That's the first time I've seen that [Catchpoint events] done live in there with those, popping that in and using Edwin to pull all that out.” What’s Next 🚀 1H Announcement Webinar Join us for the 1H Announcement webinar, which will serve as the official public presentation of the release themes and product updates previewed during this meeting. This will be the broader launch moment for the autonomous IT story, upcoming innovations, and related release details. May 12 at 12 PM CT 👉 Register here ⚡ Product Power Hour Join the next Product Power Hour sessions to continue exploring product updates, live demos, and practical use cases across the platform. These sessions are built for technical practitioners who want to see what is new, understand how features work in context, and ask questions directly to the teams behind the product. Optimize Cloud Spend with Confidence 📅 May 19 🕙10am CT Automated Remediation for Faster Issue Resolution 📅 June 17 🕛12pm CT 🍽️ User Group Dinner LogicMonitor is continuing to bring customers together through in-person user group dinners and regional sessions. These events are a great way to connect with peers, share monitoring strategies, and discuss real-world operational challenges with other practitioners. Join us in Chicago on May 27th Elevate Community Conference LogicMonitor’s annual conference is coming up in October and will bring the broader community together for product updates, technical enablement, customer stories, and peer networking. This is the best opportunity to go deeper on the platform roadmap and learn how other teams are scaling observability across their organizations. Registration opens mid-May Resources and Review 🏅Want to upskill? Earn your Catchpoint badge! 💻 Review the slide deck here 📹Watch the recording here or directly on the event page
Overview LogicMonitor’s March 31 Product Power Hour highlighted how AI-driven investigations are becoming more precise, explainable, and operationally useful for technical teams working through incidents at speed. The session focused on recent enhancements to Edwin AI, including problem management, topology-based correlation, deeper log-driven root cause analysis, and change-aware investigations that help teams move from alert to action faster. A major theme throughout the conversation was trust. Attendees wanted to understand not just what Edwin recommends, but why it made that recommendation , what evidence it used, and how that information can be pushed into the tools their teams already rely on. The product team addressed that head-on by showing how Edwin surfaces logs, change requests, topology context, and knowledge sources directly inside the investigation experience. Key Highlights 🌟 Edwin AI now provides richer AI investigations with natural language summaries, root cause analysis, and actionable remediation guidance based on alert, log, and change data. 🌟 A new problem management experience helps teams identify recurring issues across the last 90 days so they can focus on deeper root cause resolution instead of repeatedly treating symptoms. 🌟 Topology-based correlation is helping Edwin group alerts more intelligently by understanding device relationships and dependency patterns. 🌟 The team shared that ServiceNow change integration is available today , with Jira planned next. 🌟 Customers showed strong interest in extending Edwin with additional data sources, especially Catchpoint, SOP and knowledge content, and metrics-driven reporting . 🌟 The discussion reinforced that users want Edwin to support both workflows: deep investigation in the Edwin UI and pushing relevant context into ITSM systems. Q&A Q: Is build of the topo maps dependent on monitoring protocols used? For example, SSH versus SNMP to monitor network devices? A: Yes. How we pull information from LogicMonitor depends on their dedicated topology sources, which use a mix of four or five different protocols to build the maps. It depends on the type of devices you are monitoring in LogicMonitor, and that dictates how the maps are built. We also are not limited to only network and network maps in the Element Vision side. If you have VMs, you will still get a map or connections that we can pull through to Edwin soon as well. Q: Can you use topology maps from other products such as NetBrain? A: Not right now. We are currently experimenting with Dynatrace, which has an MCP available that lets us fetch topology information. In theory, if NetBrain or another third party has an equivalent way for us to fetch topology information, then yes, we would be able to layer that into what we have. The key requirement is access to topology information in a format where we can determine how systems are connected. Q: What sources can you tap into for SOP-type material? A: Right now we are connected to ServiceNow, so you can set up the LMDX integration to allow us to read those articles. Next on the list are Confluence articles and SharePoint via MCP. If there is another data source you are interested in, please share it, because we are able to start adding those integrations. We can also do a public knowledge search, so if you want to tap into vendor documentation or other publicly available web content, you can query that from the agent too. Q: Is the change integration available today? A: Yes, it is with ServiceNow. If ServiceNow is your ITSM, that is available today. We are working on Jira next for changes. Q: It seems like there used to be an available Edwin AI Python SDK integration under Settings. I do not see it now. Am I misremembering it being available? A: It is available. We might just have to pass you the files for the SDK, because I do not think it is available to download anywhere. It should include how you send through events if you want to set up a custom integration. The other option is to use the webhook if you want to send events or information into Edwin, and it sends to that same endpoint as long as you include the required fields. Q: Is there an article for the webhook approach too? A: Yes. We do have documentation, although it probably needs to be updated because it does not clearly list the endpoint, which is likely the most helpful part. Right now it mostly covers the required fields, but we can make sure it gets updated so the endpoint is more obvious. Q: Could you tell us what’s behind the AI at LogicMonitor? What technologies, approaches, or architecture are used to build and operate this solution? A: It varies depending on the use case. Forecasting, for example, is best handled with a regression algorithm based on historical data. Edwin AI leverages both ML models and agentic frameworks to correlate alerts and fetch information from third-party sources. We try to match the type of AI we use to the particular use case we are solving for. Q: Why was the AI in LogicMonitor named Edwin? Is there a specific meaning or story behind that name? A: It was named after Edwin Hubble. The idea is that the Hubble telescope helped discover and reveal more of what is out there in space, and Edwin AI is meant to do something similar for your observability systems by combining information and giving you insights into your data. Customer Call-outs ⭐“Pushing the data into ITSM is necessary for sure. The additional functionality added to Edwin makes it compelling for SA's to use the Edwin UI.” What's Next ⚡Product Power Hour Smarter Alerting that Drives Faster Action April 23rd | 1pm CT The next Product Power Hour will focus on alerts, including alert tuning, management, routing, and upcoming alert-related features. This session is a strong follow-up for teams looking to improve signal quality and operational response workflows. 👉 Register here today 🪵Logs for Lunch More Value and Less Worry with Log Partitions April 8 | 12pm CT The next Logs for Lunch session will cover log partitions and will take place at 12:00 p.m. Central Time. This is a useful session for practitioners looking to deepen their log management strategy. 👉 Register here today 🍽️ User Group Dinners Join us as we head back on the road! Connect in person with other LM users in your city over dinner and real talk. Share wins, swap stories, and grow your network. San Francisco/Bay Area - April 28 Chicago - May 27 Resources and Review 🏅Want to upskill? Earn your Edwin AI badge ! 💻 Review the slide deck here 📹Watch the recording here or directly on the event page .
Overview February’s Product Power Hour focused on Removing Analytics Bottlenecks: From Investigation to Reporting , with practical walkthroughs showing how to move faster from “ something’s broken ” to “ here’s why and here’s the story we can share .” The session connected the investigation workflow to repeatable reporting, enabling teams to avoid rebuilding the same analysis for every incident. Key Highlights ⭐ Investigation without context switching: Reduce investigation time by pivoting directly from alerts and metrics into logs in context, without jumping across tools. ⭐ Log noise reduction through layered intelligence: Cut through log noise using anomaly signals, pattern detection, and guided analysis workflows to surface the log lines that actually explain the issue. ⭐ LogPilot for natural language queries: Translates natural language questions into queries so more people can troubleshoot effectively without needing deep query expertise. ⭐ Shared Query Library with RBAC: Save and share queries across teams using Public/Shared query groups while staying within role-based access controls. ⭐ From investigation to reporting: Powered by LogicMonitor Query Language (LMQL), the Advanced Metrics Widget and Metrics Explorer Report enable reusable analysis logic across dashboards and scheduled reporting for stakeholders. Q&A Q: How do dynamic thresholds work (especially for network interface traffic)? A: Dynamic thresholds are generally based on a baseline plus standard deviation logic (with configuration options), helping flag behavior that meaningfully deviates from “normal” rather than relying only on static thresholds. Q: What is LMQL, and where is it available today? A: LMQL (LogicMonitor Query Language) powers the Advanced Metrics Widget and the Metrics Explorer Report , enabling flexible filtering and aggregation across metrics, instances, and resources. Q: Is the Metrics Explorer Report available to all customers, and can it be used for SLA reporting? A: Yes. The Metrics Explorer Report is available broadly. Because it is driven by LMQL, customers can use it to build SLA-focused views, executive rollups, or tightly scoped operational reports without having to recreate analysis logic each time. Q: How does LogPilot support more advanced log analysis? A: LogPilot translates natural language prompts into structured queries, including more advanced query patterns. This allows users who may not know the underlying syntax to still perform deep analysis, accelerating time-to-insight during investigations. What’s Next 👥User Group In-person: February 26 - London, UK February 26 - Denver, CO Virtual: March 3 - MSP March 3 - AMER East March 3 - AMER West March 5 - EMEA March 5 - APAC ⚡Product Power Hours March 12 - Performance Without Blind Spots: End-to-End Internet Performance Monitoring March 17 - AI Investigation Enhancements for Faster Resolution 🎿LogicMonitor Ski School LogicMonitor Ski School is a free, 4-week guided enablement program designed to help teams confidently adopt AI-powered observability and operationalize Edwin AI. Through a structured, cohort-based journey, participants complete weekly LM Academy badges, join live, expert-led Ski Sessions, and apply what they learn directly in their own environments. Along the way, they earn official badges in AIOps Adoption, Resource Management, Alerts, and Edwin AI while reducing alert noise, accelerating time-to-value, and building internal LogicMonitor champions. March 9 to April 5 Register today 🪵Logs for Lunch March 11 - Leverage log data in Edwin for even smarter insights Additional Resources Review the slide deck here Watch the recording here or directly on the event page .
In our final Product Power Hour of the year, we explored how Automated Diagnostics accelerates troubleshooting by adding real-time, actionable context to alerts. Ed and Patrick walked through configuration, execution models, and future enhancements while showcasing how diagnostics streamline triage and reduce MTTR. The session drew strong engagement, with customers expressing enthusiasm and offering thoughtful questions that helped clarify functionality and roadmap direction. Key Highlights ⭐ Automated context at alert time - diagnostics can run as soon as an alert triggers, giving teams immediate visibility into the issue without waiting for manual investigation. ⭐ Flexible execution workflows - diagnostics can be configured to run automatically, on-demand, or through escalation chains, enabling workflows that validate issues before ticketing. ⭐ Granular RBAC controls - separate roles for diagnostics and remediation ensure teams can restrict execution permissions as needed. ⭐ Service-level and multi-device diagnostics planned - customers highlighted the need to run diagnostics across multiple systems, which is already on the roadmap. ⭐ Community interest in shared modules - attendees expressed excitement for community-built diagnostics and future sharing mechanisms. Q&A Highlights Q: How will Automated Diagnostics integrate with Edwin AI? A: First: getting the output of diagnostics into Edwin AI. Second: using that data to train Edwin AI’s models. Third: Edwin AI being able to execute diagnostics or remediation actions directly. That’s the pathway we’re heading toward. Q: If we already have LM Logs integrations configured, can diagnostics leverage that data? A: Yes. Right now, as far as automation goes, these would be triggered by data source alerts, but the plan is to extend that so they can be triggered by any type of alert, whether that’s from logs, configs, etc. The plan is to make these very extensible for any incoming data. Q: Will Automated Diagnostics eventually run across multiple servers or services? A: Today, Automated Diagnostics is limited to automatically executing against the resource that went into the alert condition. Integrating this closely with our services is definitely part of our plans. Q: Will diagnostics work on GA 39.001? A: They will be able to run on GD 39.001. For more information, visit the release notes for 39.001 as the latest GD collector release. Q: Can SSH-based diagnostic modules run on Linux devices monitored via SNMP? A: Yes, diagnostics can run on devices monitored using SNMP as long as the collector has the correct access (e.g., SSH credentials) to execute the diagnostic. Q: Are REST API calls allowed in diagnostic scripts? A: Yes, and you can get really creative with REST API calls — essentially, you can write a Groovy script to do whatever you want. Q: Are diagnostic permissions all-or-nothing today? A: Yes. Users can either view and manage or see nothing. Q: Will Role-Based Access Control (RBAC) for Automated Diagnostics and Automated Remediation be separate? A: Yes. Diagnostics and remediation permissions are separate, allowing organizations to grant diagnostic execution without allowing remediation actions. Q: What license is required for Automated Diagnostics? A: Today, this feature is available as part of our new Advanced and Signature platform packages. Outside of that, if you're currently on an Enterprise package or something like that, there is an add-on that you could work with your CSM to talk through the details of that. Customer Callouts ⭐ "I'm stupidly excited about these [features]. Can't wait for the demo." ⭐ "Definitely would be interested in any community modules people have made or are looking to make." ⭐ "This was great. Best demo I have had… really appreciate the live demo and answering all the questions so honestly and openly." ⭐ "Dashboarding is what makes LM better than all the other platforms for monitoring." What’s Next 🎁 LogicMonitor 2025 Wrapped: Unified Observability Without Blind Spots Join us for a special year-end event where we’ll unveil how LogicMonitor and Catchpoint joining forces transform LM Envision into the industry's leading AI-first observability platform. This session will cover: A showcase of 2025’s biggest product announcements, platform advancements, and community impact A first look at how LogicMonitor + Catchpoint delivers unified observability without blind spots A preview of how this momentum sets the foundation for innovation in 2026 📅 Wednesday Dec 17, 12 pm CT 👉 Register here 🪵Logs for Lunch Rapid Troubleshooting Using New Saved & Shared Queries 📅 Wednesday, Jan 14, 2026 🕙 10 AM PT / 12 PM CT / 1 PM ET / 6 PM GMT 👉 Register here Additional Resources If you missed any part of the session or want to revisit the content, we’ve got you covered: Watch the recording here
Overview This month’s Product Power Hour focused on Cloud Monitoring with Kubernetes and Containers , emphasizing simplified observability across containerized environments. The session demonstrated how LogicMonitor makes monitoring clusters, pods, and workloads easier without overwhelming teams with noise. Through demos, best practices, and customer discussions, attendees gained practical insights into deploying and managing monitoring at scale with AKS, EKS, and beyond. Key Highlights ⭐ Seamless Enablement: Existing PaaS customers can activate Kubernetes monitoring out of the box, while others can leverage LM’s container monitoring license for quick setup. ⭐ Deeper Visibility: Demonstrations showcased how LM provides observability across nodes, pods, and system containers—cutting through complexity without flooding teams with alerts. ⭐ Retention & History: The session clarified how historical K8s data is retained and how teams can use that data for trend analysis and capacity planning. ⭐ Best Practices: Real-world examples illustrated how to configure thresholds effectively to avoid alert fatigue, especially in sandbox or test clusters. Q&A Q: How can we enable this Kubernetes for existing customers? A: “For an existing PaaS customer you just configure it as it is included in the PaaS License — 1 PaaS license = 1 monitored pod (existing cloud licensing model). For AKS or EKS monitoring you just configure it in your cloud configuration (check the box). For a non-PaaS customer you need to add the LM Container Monitoring license (old license model).” Q: I am new to K8s — how do I monitor the critical components of the platform when there are so many system containers? A: “Focus on the system containers and use the out-of-the-box DataSources as a starting point, then tune thresholds to reduce noise.” Q: What will be the retention period of history data of K8s monitors? A: “Retention is handled according to LogicMonitor’s standard data retention policies, so you can view history for trending and analysis just like other monitored resources.” What’s Next 💻Level Up Your IT Universe: Next LogicMonitor Innovations Unveiled Webinar On September 24 , discover the latest Edwin AI and LM Envision capabilities, including noise-cutting AI agents, Dynamic Service Insights, and expanded multi-cloud monitoring, designed to move IT from reactive to resilient. ➡️ Register here to save your spot! 🪵 Logs for Lunch October 8: Logs Overages & Reducing MTTR with Cloud Logs ⚡ Next Product Power Hour October 29: App Visibility for ITOps Want to check out previous Product Power Hours? Explore the Product Power Hour Hub in the LM Community! 📚 Badges and Certifications Earn free, on-demand, digital badges that validate your product knowledge and platform skills. Available badges: 🛡️Getting Started 🛡️Collectors 🛡️Logs 🛡️AI Ops Adoption 🛡️Dashboards Review If you missed any part of the session or want to revisit the content, we’ve got you covered: Review the slide deck Want to dive deeper into this session? Watch the recording here
