When an alert fires, the hard part is often figuring out what it means. What systems depend on the affected resource? Is a critical service at risk? Are users feeling the impact? And what should your team do first? For IT operations, SRE, platform, cloud, and networking teams, answering those questions can mean moving between tools, sorting through noise, and piecing together context while an issue unfolds. LogicMonitorβs 2H innovations are designed to help teams move through that work with better data, clearer context, and a more direct path to action. Bring more operational data together Troubleshooting gets harder when key signals are spread across different places. LogicMonitor is expanding the data teams can bring into the platform, including OpenTelemetry metrics, application signals, and cost data. With these signals together in the same operational picture, practitioners can investigate performance and cost side by side. That broader view can help teams understand whatβs happening and make more informed decisions during an investigation. It also gives AI-assisted workflows more relevant information to work with. See whatβs connected and whoβs affected An alert by itself doesnβt show the full impact. Topology-aware correlation and the context graph help connect events to the resources and services they relate to, giving teams a clearer view of what may be affected. Digital experience data from Catchpoint adds another important perspective: what users are actually experiencing. By bringing infrastructure, application, and digital experience signals into a broader picture, teams can better prioritize issues affecting critical services and users instead of treating every alert the same. Use Edwin AI to reduce manual investigation During an incident, repetitive investigation steps take time away from resolving the issue. Enhancements to Edwin AI are designed to help teams investigate more deeply, group related events into Insights, and coordinate multi-agent workflows for a more useful starting point for triage. Edwin AI is also expanding into Slack, Microsoft Teams, and ServiceNow, bringing investigation and response closer to where teams already manage incidents. It can help prepare or recommend actions, while people remain in control of approvals, permissions, policies, and guardrails. A more practical path toward Autonomous IT For practitioners, these updates point toward less time spent sorting through noise, switching between tools, and rebuilding incident context. Better data helps establish whatβs happening. Context helps show what matters and who is affected. Guided action can help teams move forward with less manual work. Together, these capabilities support LogicMonitorβs vision for Autonomous IT: progressively reducing repetitive operational work while keeping human oversight in the decisions that matter. For more information about LogicMonitor's second-half announcement, read the full blog here . Stay tuned for more updates!
Community Blog
Explore thought-provoking blog posts, share your insights, and earn badges along the way. Every read and comment helps shape a richer community experience. Join us for themed writing challenges, featured posts, and collaborative content series.
This Product Power Hour gave the community a practical look at how LogicMonitor is bringing cloud monitoring, provider health, cost visibility, and optimization into a more connected Cloud Operations experience. The session focused on helping teams answer the operational questions that come up every day: what cloud resources do we have, are they healthy, is the provider experiencing an issue, how is our spend changing, and where can we optimize? Attendees saw workflows across Resource Explorer, Cloud Provider Health, cloud configuration, Billing, Cost Analysis, Budgets, and Recommendations. The goal is to give CloudOps, SRE, and infrastructure teams the context they need to move from visibility to investigation and action without switching between monitoring tools, cloud consoles, billing platforms, and provider health pages. Key Highlights β Resource Explorer provides a unified view of the cloud estate , helping teams understand resources discovered across their environment with monitoring context attached, including compute, databases, storage, Kubernetes, networking, and managed cloud services. β Cloud Provider Health brings AWS, GCP, and Azure service events directly into LogicMonitor , helping practitioners determine whether an issue originates in their own environment or from a broader provider disruption. β Billing and Cost Analysis connect cloud spend with operational context , including month-to-date spend, weekly and monthly trends, top movers, anomalies, and dynamic groupings by account, resource type, region, resource ID, and other dimensions. β Forecast-based Budgets help teams identify potential overspend before the end of the month. Teams can define budgets and thresholds, see when spend is expected to exceed them, and move directly into Cost Analysis with the relevant filters already applied. β Recommendations turn cost visibility into potential action , identifying opportunities such as idle resources and underutilized compute while showing the utilization data behind each recommendation. Q&A Q: Does Cloud Operations require the Cloud Cost Optimization license? A: It depends on the capability. Cloud Provider Health and cloud settings are available when you are monitoring cloud resources. Features that pull in billing data or provide recommendations for reducing cloud spend require the Cloud Cost Optimization license. Cloud Cost Optimization is also included with the Signature level of the Hybrid SKU. Q: If we do not have Cloud Cost Optimization, what would we still be able to use? A: You would still have access to Cloud Provider Health and cloud settings as part of the cloud monitoring experience. These capabilities help you investigate provider issues, understand affected resources, and manage cloud monitoring configurations. Billing, Cost Analysis, Budgets, and cost-saving Recommendations are part of Cloud Cost Optimization. Q: Is Azure supported in Cloud Provider Health? A: Yes. Cloud Provider Health includes events from AWS, GCP, and Azure. Azure publishes fewer global events, which is why Azure events may appear less frequently. The team is also working to incorporate more account-specific health alerts, which is especially relevant for Azure because many of its health notifications are account-specific. Whatβs Next π Elevate Community Conference Join the LogicMonitor community in person for deeper product conversations, technical enablement, customer stories, hands-on learning, and opportunities to connect directly with the teams building the platform. π Chicago: October 13β14 π London: November 3β4 π Sydney: November 19 π Register today with our Promo Code: ECC26Comp06 for free registration. β‘ Product Power Hour Join us for upcoming Product Power Hour sessions to continue exploring live LogicMonitor workflows, practical use cases, and new capabilities directly with the Product team. π Modernize Hybrid Monitoring with OpenTelemetry π¬ Continue the Conversation Have feedback on Cloud Operations or a workflow you want the Product team to consider? Submit feedback directly through your LogicMonitor portal or continue the discussion in the Community. Feedback submitted through these channels is reviewed and connected back to the Product team. Resources and Review π Want to upskill? Earn your Cloud badge! π» Review the slide deck here πΉWatch the recording here or directly on the event page
As LogicMonitor continues to modernize the platform experience, UIv3 Resources (including Services) have now been deprecated , with users transitioned to the UIv4 Resources and Services experience. Resources and Services are central to how teams organize, navigate, and understand their monitored environments, so we recognize that changes to these workflows can take some getting used to. The transition to UIv4 is designed to be straightforward: the functionality customers rely on remains available, no migration effort are required, and the updated experience provides a more consistent foundation for future enhancements across the LogicMonitor platform. To help users become familiar with the UIv4 experience, weβve put together a set of FAQs covering common questions, key differences, and what to expect when working with the new Resources and Services pages. FAQs: 1. What is changing? Effective August 31, 2026, LogicMonitor will retire the legacy UIv3 Resources experience, including UIv3 Services. After this date, UIv3 Resources and Services will no longer be accessible. Customers will manage their monitored Resources and Services through the UIv4 Resources and UIv4 Services experiences. This change affects the user interface only. Resources, Services, monitoring configurations, collected data, and associated monitoring functionality are not being retired. 2. When will UIv3 Resources and Services reach End-of-Life? The official End-of-Life date for UIv3 Resources, including UIv3 Services, is 31st August 2026 11:59 PM PST After this date, customers will need to use UIv4 for Resources and Services. 3. Who does this impact? This change impacts customers and users who were still using the legacy UIv3 Resources experience or access Services through UIv3 Resources. Customers already using UIv4 Resources and UIv4 Services should have no impact. 4. Are LogicMonitor Resources or Services being retired? No, only the legacy UIv3 user interface for Resources and Services is being retired.Β Β Resources, Services, monitoring configurations, monitoring data, and associated platform functionality are not retiring. All the functionality for Resources and Services remain available and supported through UIv4. 5. In UIv4, where can I find services? The primary navigation change is that Services is now a standalone area. In UIv4, customers select Services directly from the LogicMonitor left navigation menu. In UIv3, Services were accessed from the Services tab within the Resources tree. The Services experience provides its own Services tree and Favorites view. Customers can search and navigate Services and Service Groups, and access Service information such as Status, Alerts, Inventory, SDT, Graphs, Logs, and Maps. 6. What happens to my existing Resources/Services? Existing Resources/Services remain available in UIv4. In UIv4, Services are accessed through a standalone Services option in the left navigation menu, rather than through the Services tab within the Resources tree. Customers do not need to recreate Resources/Services or migrate Resources/Services configurations because of this UI change. Existing monitored devices, cloud resources, groups, instances, DataSources, properties, alerts, and related monitoring configurations continue to be available through the UIv4 Resources experience. 7. Do customers need to migrate data from UIv3 to UIv4? No, there is no separate data migration required for this transition. UIv3 and UIv4 are user interfaces for working with the same LogicMonitor platform data. Customers do not need to export and import their Resources or Services. 8. Will historical monitoring data be affected? No, the transition changes how customers access and manage Resources and Services. It does not require customers to migrate historical monitoring data. 9. Will monitoring or alerting stop on August 31, 2026? No. the End-of-Life applies to the legacy UIv3 Resources and Services user interface. Existing monitoring and alerting continue to operate. Customers will use UIv4 to view and manage their Resources and Services after the EOL date. 10. What is different about Resources in UIv4? UIv4 provides the current Resources experience with updated navigation, styling, and interaction patterns. The Resources page includes a navigation panel for browsing Resources and Favorites and a detail panel for working with the selected Resource. Customers can continue to navigate monitored Resources, search and filter the Resource tree, work with groups, access monitored instances and DataSources, manage Resource information, and perform Resource management operations. 11. What is different about Services in UIv4? The primary navigation change is that Services are now a standalone area. In UIv4, customers select Services directly from the LogicMonitor left navigation menu. In UIv3, Services were accessed from the Services tab within the Resources tree. The Services experience provides its own Services tree and Favorites view. Customers can search and navigate Services and Service Groups and access Service information such as Status, Alerts, Inventory, SDT, Graphs, Logs, and Maps. 12. Is there feature parity between UIv3 and UIv4? Aside from minor visual and styling differences, functionality and capabilities remain consistent between UIv3 and UIv4 Resources and Services. LogicMonitor continues to monitor and address remaining parity gaps as customers transition to UIv4. The primary navigation change is that Services are now a standalone area. In UIv4, customers select Services directly from the LogicMonitor left navigation menu. In UIv3, Services were accessed from the Services tab within the Resources tree. 13. Will APIs or integrations using Resources be affected? No, this deprecation applies to the UIv3 Resources and Services user interface. No API migration requirement has been announced as part of this UI EOL. Customers using LogicMonitor APIs or integrations should not need to change them solely because the UIv3 Resources and Services pages are being retired. 14. Are Resource properties affected? No change to Resource properties has been announced as part of this EOL. Existing Resource data and configurations remain in the LogicMonitor platform, and are accessible through UIv4. 15. Are Resource Groups or Dynamic Groups affected? No, this deprecation does not retire Resource Groups or Dynamic Groups. Customers will continue managing their Resources and groups through the UIv4 Resources experience. 16. Are Service Groups affected? No, Service Groups remain supported. Customers will manage Services and Service Groups from the standalone Services experience in UIv4. The primary navigation change is that Services is now a standalone area. In UIv4, customers select Services directly from the LogicMonitor left navigation menu. In UIv3, Services were accessed from the Services tab within the Resources tree. 17. What happens to Favorites? UIv4 Resources provides a Favorites view for quick access to frequently used Resources. The UIv4 Services page also provides a Favorites view for frequently accessed Services. 18. Why is LogicMonitor making this change? Retiring UIv3 allows LogicMonitor to focus development on a single user experience. The transition to UIv4 provides: A modernized and streamlined Resources and Services experience. Improved consistency and usability across the LogicMonitor platform. A dedicated Services experience. Continued enhancements and future innovation within a single UI. 19. What should customers do to prepare for this transition? We recommend that customers: Familiarize users with UIv4 Resources navigation and workflows. Familiarize Service Insight users with the standalone Services navigation. Validate commonly used operational workflows in UIv4. Update internal documentation, runbooks, screenshots, and training materials that reference the UIv3 Resources interface. Contact LogicMonitor Support or their Customer Success Manager, if they identify a workflow that does not behave as expected in UIv4. 20. What should customers check when validating UIv4? Customers should validate the workflows that matter to their teams. Depending on how they use LogicMonitor, this can include: Navigating Resource and Service trees. Searching and filtering Resources and Services. Viewing Resource and instance information. Managing Resource Groups. Viewing DataSources, instances, graphs, and alerts. Managing properties. Working with SDTs. Accessing and managing Services and Service Groups. Reviewing Service members, metrics, alerts, graphs, and maps. The goal is to familiarize users with the updated navigation and identify any workflow questions before UIv3 becomes unavailable. 21. What if a customer finds functionality they use in UIv3, but cannot find it in UIv4? Customers should first review the current UIv4 Resources and Services documentation. If a required workflow cannot be located or does not behave as expected, customers should contact LogicMonitor Technical Support or their Customer Success Manager. UIv4 Resources support page UIv4 services support page 22. Where can customers find the current Resources documentation? Customers should use the current LogicMonitor documentation for Navigating the Resources Page. The legacy Resources documentation is identified as applying to the legacy UI, and is no longer maintained. UIv4 Resources support page 23. Where can customers find the current Services documentation? Customers can use the current LogicMonitor documentation for: About LM Service Insights. Navigating the Service Insights Page. Adding a Service. Managing Services and Service Groups. In UIv4, Services are accessed directly from the Services option in the LogicMonitor navigation menu. UIv4 services support page 24. Who should customers contact if they need assistance? Customers who have questions about the UIv3 Resources and Services End-of-Life, or need assistance validating their workflows in UIv4, should contact their LogicMonitor Customer Success Manager or LogicMonitor Technical Support.
As we prepare to launch a new LogicMonitor Certification, we'll be retiring the LogicMonitor Certified Professional (LMCP) certification on September 21, 2026 . If you're currently working toward the LMCP certification, here's what you need to know. What does this mean? The LMCP certification exam will remain available until September 21, 2026. After that date, the exam will no longer be offered. If you're currently registered for the LMCP exam, you have until September 21 to complete it. I already earned the LMCP certification. Does this affect me? No. Your earned certification remains valid according to its existing terms. This announcement only affects new exam attempts after September 21, 2026. I'm currently registered for the LMCP exam. What should I do? Complete your exam before September 21, 2026. After that date, the exam will no longer be available. Can I register for the LMCP after September 21? No. New registrations will close when the certification is retired. What happens if I don't finish before September 21? Any incomplete LMCP exam registrations will expire when the certification is retired. To earn a LogicMonitor certification after that date, you'll need to pursue the new certification program. Will there still be LogicMonitor Certifications? We're excited to introduce our new LogicMonitor Certification, designed to better reflect today's platform capabilities and provide an updated learning and certification experience.
Following our earlier announcement , the End of Life (EOL) for Legacy Versions 5, 6, 7, and 8 for LM Container & Argus was successfully completed on July 31, 2026 . This milestone represents an important step in maintaining a secure, reliable, and modern platform. By retiring these legacy versions, we can continue investing in the latest capabilities, performance improvements, and security enhancements available in current releases. What this means for you Legacy Versions 5, 6, 7, and 8 are no longer supported by LogicMonitor. Engineering and Technical Support will no longer provide assistance for these legacy versions. Customers need to upgrade to the latest supported version 13.2.0 , to continue receiving support, security updates, and product enhancements. Keeping your environment on a supported release helps ensure access to the latest features, improved reliability, ongoing security updates, and the best possible experience with LogicMonitor. If you have questions or need assistance, please reach out to your Customer Success Manager (CSM) or contact LogicMonitor Technical Support . Thank you for partnering with us as we continue to modernize the platform and deliver new innovations.
If becoming LogicMonitor Certified is on your list this year, thereβs no better time to get started. Camp LogicMonitor is back, and this yearβs program has a new mission: helping users prepare for LogicMonitor Certification together. Camp LogicMonitor is LM Academyβs annual Certification readiness program , bringing the LogicMonitor community together for four weeks of guided learning, expert instruction, and live Campfire Chats designed to build the knowledge and confidence needed to pursue certification. Whether youβre preparing for your first certification or looking for a structured way to stay on track, Camp provides a flexible, community-driven experience that helps you learn alongside fellow LogicMonitor users and connect directly with LogicMonitor experts. Your Certification Preparation Path This yearβs Camp features four recommended certification preparation badges: π§© LogicModules π¦ Resource Management π¨ Alerts π Reports Complete one badge each week through LM Academy, then join our weekly Campfire Chats where product experts expand on the weekβs topic through demonstrations, best practices, and live Q&A. Why Join Camp? Camp is designed to make certification preparation easier, more engaging, and more achievable. Throughout the program, youβll: Build practical knowledge across recommended certification topics Learn directly from LogicMonitor product experts Stay motivated through a guided weekly learning path Prepare for LogicMonitor Certification alongside fellow users Complete all four featured certification preparation badges and attend at least one Campfire Chat to earn a complimentary LogicMonitor Certification exam attempt, plus exclusive Camp LogicMonitor rewards. Learn Together. Get LogicMonitor Certified. Camp LogicMonitor begins August 24 . Join the LogicMonitor community, prepare for certification with confidence, and take the next step toward becoming LogicMonitor Certified. Registration is now open. Weβll see you at Camp!