Overview This month's Product Power Hour focused on one of the most requested next steps in observability and AIOps: Automated Remediation . Building on the success of Automated Diagnostics, LogicMonitor introduced new capabilities that enable teams to automatically execute remediation actions when alerts occur, reducing manual intervention, shortening outages, and helping teams focus on higher-value work instead of repetitive operational tasks. The session included a live demo showcasing how remediation modules, action chains, and alert-driven automation work together to automatically resolve common infrastructure issues before they impact users. Assets Recording Key Highlights 🌟 Automated remediation reduces MTTR by fixing issues at the moment of alert Instead of simply generating another notification, Automated Remediation can execute scripts that attempt to resolve the underlying issue immediately when an alert fires. Whether it's restarting a service, cleaning up disk space, or killing a runaway process, teams can automate common recovery actions and reduce the duration and impact of incidents. 🌟 New remediation source modules extend LogicMonitor automation LogicMonitor introduced a new module type called Remediation Sources , complementing the existing Diagnostic Sources. Out-of-the-box modules currently support common Windows and Linux use cases such as: Restarting devices Starting or stopping processes Disk cleanup Preparing Windows clusters for maintenance Suspending or resuming cluster nodes These templates can also be customized for organization-specific workflows using PowerShell or Groovy scripts. 🌟 Action Rules automate recovery workflows The session demonstrated how Action Rules and Action Chains can automatically trigger remediation workflows when specific alert conditions occur. Similar to Alert Rules and Escalation Chains, teams can define: Which alerts trigger automation Which remediation modules run Multi-stage diagnostic and remediation workflows This enables proactive recovery without requiring operator intervention. 🌟 Diagnostics and remediation work together Automated Diagnostics continues to capture critical troubleshooting data at the exact moment an alert occurs. Examples shown included: Top CPU and memory-consuming processes Traceroutes Network interface statistics Event log collection This diagnostic context can be attached directly to alerts and ITSM tickets, helping responders investigate issues faster. Future roadmap plans include deeper integration between diagnostics and remediation workflows. 🌟 Deep Edwin integration is on the roadmap The team shared plans for Automated Remediation and Diagnostics to become tightly integrated with Edwin. Future capabilities include: Edwin understanding which diagnostics and remediations have already been attempted Edwin recommending remediation actions Executing remediation directly from Edwin workflows Leveraging remediation history to recommend playbooks and threshold tuning While not yet available, this integration represents a key direction for LogicMonitor's Agentic AIOps strategy. 🌟 Security and governance were built into the design The release includes new RBAC controls and auditing capabilities that allow teams to: Control who can create, edit, view, and execute remediations Track all remediation activity through audit logs Restrict which processes can be modified Store remediation-specific credentials separately from standard monitoring credentials Additional granular permissions are already planned for upcoming releases. 🌟 ITSM and workflow integrations extend automation beyond LogicMonitor Remediation and diagnostic outputs can now be passed directly into existing workflows, including: ServiceNow Jira PagerDuty ConnectWise Slack Microsoft Teams Custom HTTP integrations The team also discussed customer interest in triggering tools such as Ansible and Terraform through custom remediation modules. Q&A Q: Can Edwin trigger or perform remediation actions? A: Yes. APIs already exist, and future Edwin integrations will allow Edwin to recommend and execute diagnostics and remediation actions while incorporating the results into investigations. Q: Can diagnostic results automatically trigger remediation actions? A: Not today, but it is a key roadmap item. The team specifically discussed scenarios where diagnostic output (such as identifying the top CPU-consuming process) could automatically feed into a remediation workflow. Q: What prevents LogicMonitor from terminating critical processes accidentally? A: Customers explicitly define which processes or services can be acted upon. LogicMonitor only performs remediation actions against approved targets and supports allow-lists for additional control. Q: Are remediation modules custom-built or provided by LogicMonitor? A: Both. LogicMonitor ships several prebuilt remediation modules for common use cases, while customers can also build and customize their own remediation scripts using PowerShell or Groovy. Q: Can remediation modules trigger external tools like Ansible or Terraform? A: Yes. While there are no out-of-the-box modules today, customers can build custom remediation scripts that call APIs or webhooks to trigger external automation platforms. Q: Can users provide input when manually executing a remediation? A: Not currently, but support for runtime parameters and user inputs is planned for an upcoming release. This would allow operators to provide targets, credentials, or other execution-specific values before running a remediation. Q: Will LogicMonitor learn from remediation history to improve thresholds and playbooks? A: The long-term vision is for Edwin to leverage remediation history to recommend threshold tuning, improve playbooks, and suggest automation opportunities. This capability is not available today but is actively being explored. Q: Can credentials for remediation be sourced from privileged access management tools like CyberArk or Delinea? A: Today, remediation credentials are stored in dedicated remediation resource properties. Native PAM integrations are not currently available, but the team acknowledged the importance of this use case and plans to investigate future options. What's Next 🏆 LogicMonitor MVP Program Nominations Applications for the next MVP class are now open through July 15th . MVPs receive: Early product access Beta opportunities Direct engagement with product leaders Speaking opportunities Community recognition and exclusive events 👉 Apply through the LogicMonitor Community 🎓 LM Academy Deep Dive Sessions The LM Academy team continues to host monthly product deep dives featuring hands-on demonstrations and direct access to LogicMonitor trainers. 👉 Explore upcoming sessions in the Community Events section 🚀 Elevate 2025 Join LogicMonitor's flagship community event this fall: 📍 Chicago — October 13–14 📍 London — November 3–4 📍 Sydney — November 17–18 Attendees can also participate in LM Training Live , featuring hands-on workshops and technical labs, with dedicated experiences planned for MVPs. 👉 Register on the LogicMonitor Elevate homepage and use code: ECC26Comp06

Built by Leaders. Powered by Community. Shaping the Future of Autonomous IT. One year ago, we launched the inaugural LogicMonitor MVP Program with a simple goal: recognize and connect the customers who are pushing the boundaries of observability, automation, and operational excellence. What happened next exceeded our expectations. Over the last year, our MVPs have helped influence product innovation, participated in beta programs, shared their expertise at community events, launched user groups, contributed thought leadership, and strengthened the LogicMonitor community in ways that continue to make an impact today. Now, we're excited to open applications for the 2026–2027 LogicMonitor MVP Cohort. Whether you're leading a major observability initiative, driving AI-powered operations, mentoring peers, or championing innovation within your organization, we want to hear from you. 👉 Apply today or nominate a fellow observability leader . 🚀 Why Become a LogicMonitor MVP? The MVP Program recognizes exceptional customers who don't just use LogicMonitor—they help shape the future of it. As an MVP, you'll have opportunities to: 🔹 Lead - Share your successes, present at events, contribute thought leadership, and become a recognized voice within the observability community. 🔹 Connect- Join an exclusive network of MVPs and gain direct access to LogicMonitor product leaders, executives, and subject matter experts. 🔹 Innovate - Influence the future of LogicMonitor through roadmap discussions, beta programs, product feedback sessions, and early-access opportunities. 🌟 Celebrating Our Inaugural MVP Class Over the past year, our MVPs have: 🏆 Influenced product direction through feedback sessions and beta participation 🎤 Shared expertise through community events, user groups, webinars, and speaking engagements ✍️ Published thought leadership and customer success stories 🤝 Connected practitioners across industries to exchange ideas and best practices 🚀 Helped advance the conversation around observability, AI Ops, and Autonomous IT MVP Impact Highlights 35 MVPs across industries and geographies Participation in Automated Diagnostics Beta Launch of new User Group programs Contributions to AI Heroes initiatives Product feedback sessions with executive and product leadership Community speaking engagements and content creation Representation from organizations including Yale, Abbott, Navy Federal, Johnson & Johnson, Deutsche Telekom, Crocs, Fujitsu, and others Published Blogs Taming the Alert Chaos - Managing LogicMonitor Escalation Chains and Alert Rules with Terraform How LogicMonitor Delivers Real Value in Higher Education IT Why Chaos Engineering Matters 🎁 What MVPs Receive Recognition & Visibility Featured MVP profile in the LogicMonitor Community Recognition across LogicMonitor channels Opportunities to amplify your personal brand Exclusive Access Monthly MVP meetings with product and executive leaders Early access to product features and beta programs Invitations to MVP-only experiences and events Career Growth Opportunities Speaking opportunities Content collaboration and thought leadership Networking with industry peers and LogicMonitor leadership The MVP Welcome Pack Every accepted MVP receives exclusive LogicMonitor MVP swag and recognition materials. ⏱ What's the Commitment? The program is designed to fit alongside your existing responsibilities. One 45-minute MVP meeting each month Opportunities to participate in events, content, feedback sessions, or beta programs based on your interests Typical commitment: approximately 1–2 hours per month Some months may only include the monthly meeting, and we understand priorities shift throughout the year. 👤 Who Should Apply? We're looking for: Observability and platform leaders Infrastructure and operations professionals Community contributors and mentors Automation and AI Ops practitioners LogicMonitor advocates driving meaningful outcomes in their organizations Partners, consultants, and MSPs making an impact with LogicMonitor 📅 2026–2027 MVP Selection Timeline Applications & Nominations: Through July 15 Interviews: Through July 31 Selection Process: July 31 – August 8 Notifications Sent: August 8 Public Announcement: August 11 First MVP Meeting: August 14 🙌 Know Someone Who Should Apply? Great MVPs don't always nominate themselves. If you know someone making an impact with LogicMonitor, submit a nomination and help us recognize their contributions. Ready to Shape the Future of Autonomous IT? 👉 Apply today or nominate a fellow observability leader . Applications close July 15 . We can't wait to meet the next class of LogicMonitor MVPs.

Overview Alert governance keeps your alerting program effective over time by giving teams a clear way to review, refine, and own the alerts they depend on. The strongest alerting programs are not just well configured at launch; they are maintained through ownership, review cycles, threshold hygiene, and continuous improvement.  Key Principles Alert quality is a lifecycle, not a one-time project Ownership should be explicit at both the service and routing layers Overrides need visibility and cleanup Review cadence matters more than reactive tuning alone Historical alert data should drive change decisions Alert Governance Features and Methods Ownership and review Internal enablement content frames tuning as an ongoing discipline supported by reports, dashboards, and recurring investigation of noisy or redundant conditions. That is exactly the right foundation for governance. A mature alerting program should define who owns thresholds, who owns routing, and who reviews drift over time. Threshold hygiene The Alert Thresholds report is especially useful for alert governance because it shows what global defaults have been overridden. Operational visibility The Alerts page supports saved views, custom columns, filtered investigations, and historical alert review. Those features are not just helpful in the moment. They also make it easier for teams to create repeatable review workflows by service, team, severity, or alert type.  Routing hygiene Governance also applies to routing. Alert rules that once made sense can become stale as environments evolve. Since rule processing is first match and rule order matters, even a small drift in priority or matching logic can change where alerts land. Reviewing the rule stack is part of governance, not just routing setup. Best Practices Create Ownership at Two Levels Define who owns the monitored service itself. Define who owns the alert path, including thresholds, routing, and escalation behavior. Recognize that service ownership and alert ownership may not always belong to the same team. Make ownership explicit, so alert quality does not become a shared responsibility with no actual owner. Review Overrides on a Schedule Use the Alert Thresholds report to review custom thresholds on a recurring basis. Identify where alerting has been disabled or heavily customized deeper in the hierarchy. Look for drift that may no longer reflect current operational needs. Treat override review as routine maintenance, not just a cleanup project. Use History to Drive Change Review alert volume and recurring patterns before changing thresholds or routing. Use trend data to identify noisy resources and repeat offenders. Base tuning decisions on actual alert behavior, not anecdotal feedback alone. Let historical signal quality guide improvement work. Keep Review Lightweight but Real Establish a practical review cadence that teams can sustain. Consider a monthly threshold review for noisy conditions and overrides. Use quarterly rule reviews to catch stale routing logic and priority drift. Add post-incident tuning reviews when major events expose alerting gaps. Implementation Checklist ✅ Assign clear owners for thresholds, routing, and service-level alert quality ✅ Create saved views for recurring review workflows ✅ Run the Alert Thresholds report regularly to identify drift ✅ Review alert trends for noisy resources or recurring patterns ✅ Audit alert rules for priority order and stale matching logic ✅ Review escalation chains when support coverage or team structure changes ✅ Capture major tuning decisions so future reviewers understand why they were made Conclusion Alert governance is what keeps alerts from slowly degrading as environments change. When ownership is clear, reports are used consistently, and tuning decisions are revisited over time, alerting stays relevant, trusted, and operationally useful. Additional Resources Alerts Thresholds Report Alert Trends Report Choosing a Report Type Managing Alerts from the Alerts Page Alert Rules Escalation Chains

What 1H 2026 Means for the Teams Using LogicMonitor Every Day Watch the full video here or directly on our Product Hub page for a deeper look at what’s coming in 1H 2026. If you use LogicMonitor every day, whether you are troubleshooting alerts, tracking service health, digging through logs, or trying to move faster during incidents, our 1H 2026 product announcement is built with your work in mind. This announcement is centered on three ideas: Autonomous Operations without Blind Spots Intelligence Grounded in Context From Insight to Action Those themes may sound big-picture, but for day-to-day users, they point to something very practical: helping you see more, understand more, and act faster. Autonomous Operations without Blind Spots The first theme is about visibility. In real environments, issues do not stay neatly in one place. What starts as an infrastructure problem can surface in logs, affect user experience, or be tied to an Internet dependency outside your immediate control. That is why this part of the 1H 2026 story matters. It is about expanding visibility across the parts of the platform that technical teams rely on most, including core observability, cloud and logs, and digital experience and Internet performance. For daily users, the value is straightforward: fewer blind spots when you are trying to understand what is happening and where to look first. Intelligence Grounded in Context The second theme is about making AI more useful in real operational work. Signals on their own are helpful, but context is what makes them actionable. Metrics, logs, topology, service relationships, and other operational contexts all play a role in understanding what is actually going on. That is where Edwin AI comes in. As the platform continues to bring more context together, the goal is not just to show you more data. It is to make the intelligence you see more relevant, more practical, and more trustworthy. For teams working in the platform every day, that can mean faster triage, less manual correlation, and a clearer starting point when something breaks. From Insight to Action The third theme is about response. Seeing an issue is important. Understanding it is even better. But what really matters in the moment is being able to take the next step quickly and confidently. That is why this part of the announcement focuses on moving from insight to action through automation and AI-driven response. For practitioners, this is where the platform becomes even more useful under pressure. It helps shorten the path from noticing a problem to understanding it to acting on it. And when you are managing incidents, supporting services, or trying to keep teams aligned, that speed matters. Why this matters for the community For our community, this announcement is not just about where the platform is going. It is about how that direction supports the work you are already doing. If you are in operations, support, SRE, platform engineering, or another hands-on technical role, these updates map directly to the workflows you care about most: getting broader visibility across your environment understanding issues with better context moving faster from investigation to response That is the real takeaway from 1H 2026. It is about making LogicMonitor more helpful for the people who use it every day. Looking ahead Autonomous IT is a big vision, but it only matters if it improves the experience of real teams doing real work. That is what makes the 1H 2026 announcement exciting. It is about broader visibility. Better context. Faster action. And for the technical users in our community, that means a platform that is increasingly built to support the way you actually work. Want a deeper walkthrough of the themes and product areas behind the announcement? Watch the video here or directly on our Product Hub page for a more in-depth explanation.

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

As LogicMonitor continues to evolve the dashboard experience, UIv3 Dashboards have now been deprecated in favor of the new dashboard experience. Dashboards are a critical part of how teams monitor performance, troubleshoot issues, and share insights across the business. Any change to that experience matters. The good news is that transitioning to the new dashboard experience is more straightforward than many users expect. Existing dashboards remain available, core functionality is still there, and the updated experience introduces meaningful improvements that make dashboards easier to use, manage, and share. To help users get up to speed quickly, we’ve put together a short set of videos that walk through the most important updates and show how to make the most of the new dashboard experience. What To Expect From The New Dashboard Experience The transition to the new UI is designed to be as seamless as possible. For most users, the biggest changes are not about rebuilding dashboards from scratch, but about learning a more modern, streamlined way to work. Here are a few practical tips to make the transition easier: Get Familiar With The Updated Layout The overall dashboard structure will still feel familiar, but navigation and actions are now more efficiently organized. Common controls like time range selection, adding widgets, and dashboard actions are easier to access, helping teams move faster in daily workflows. Watch: Navigation and Interface Updates Use Filters To Reduce Dashboard Sprawl One of the biggest improvements in the new dashboard experience is filtering. Instead of maintaining multiple versions of similar dashboards, users can quickly filter by customer, environment, or other criteria, and the full dashboard updates instantly. Saved views make repeat workflows even faster and more consistent across teams. Watch: Dashboard Filters: Improvements and Saved Views Share The Exact View You Want Others To See Collaboration is easier in the new experience. Shared dashboard links can preserve time ranges and applied filters, making it much easier to align teammates, stakeholders, or customers around the same set of data, without extra explanation. Watch: Sharing Dashboards and Enhanced Collaboration Take Advantage Of More Flexible, Query-Driven Analysis The Advanced Metrics widget brings a powerful new way to build dashboards. By using LMQL to define and reuse queries, teams can create more flexible visualizations for troubleshooting, reporting, and customer-specific views, all from the same underlying logic. Watch: Advanced Metrics Widget and Query-Driven Visualization Keep Using The Widgets You Already Know For teams already using Custom Graph, Big Number, and Pie Chart widgets, the good news is that those familiar capabilities remain in place. The main change is a cleaner, more structured configuration experience that makes widget setup and editing easier. Watch: Classic Widgets: Custom Graph, Big Number, and Pie Chart Why This Transition Matters The new dashboard experience is not just a visual refresh. It creates a stronger foundation for faster workflows today and more innovation going forward. With improved filtering, easier sharing, more flexible visualization options, and a more intuitive configuration experience, teams can get more value from dashboards with less effort. The move away from UIv3 Dashboards is an opportunity to simplify dashboard management, improve collaboration, and leverage a more modern experience built for how teams work today. With the right features already in place and guided walkthroughs available for the most important changes, getting comfortable with the new dashboard experience can be quick, practical, and immediately valuable.

Overview Advanced alert management helps teams turn alert data into smarter, more adaptive signals. By combining multi-level thresholds, intelligent suppression, disciplined routing, and automation-ready guardrails, teams can improve signal quality at scale without sacrificing visibility or operational control. Key Principles Detection and notification are not the same thing Adaptive alerting works best alongside hard guardrails Suppress noise without hiding operational truth Good automation depends on a good signal Correlation works best when the underlying alerts are already healthy Alert Management Features and Methods Dynamic and hybrid thresholds Dynamic thresholds use historical behavior data to learn expected ranges that show levels within thresholds or normalcy, and trigger alerts when a metric behaves outside the band of normalcy. LogicMonitor documents support anomalies, rate-of-change detection, and daily or weekly seasonality, which makes dynamic thresholds especially useful for variable metrics such as throughput, latency, or bursty utilization, or where a level is unknown and can be assessed over a time period. Dynamic and static thresholds can also coexist on the same datapoint. That hybrid approach is one of the most practical advanced patterns because it lets teams keep a hard business guardrail in place while also catching abnormal behavior, even if it has not crossed a fixed limit. Suppression strategy A good suppression strategy reduces interruption, not observability. LogicMonitor’s support documentation explicitly distinguishes between alerts that exist in the portal and those whose notifications are suppressed, including suppression driven by SDT, host-down conditions, collector issues, cluster logic, or anomaly detection. That gives teams room to reduce noise while preserving source context for investigation.  Dynamic thresholds also support suppressing static threshold notifications when a datapoint remains within its learned band. That is especially useful when a metric regularly crosses a static threshold during expected behavior, but still needs a hard limit for exceptional cases.  Routing for scale At scale, routing design has to do more than notify. It has to preserve ownership, control escalation timing, and avoid duplication. Alert rules still follow first-match logic, while escalation chains handle staged delivery and can include time-based routing and rate limits. That means advanced routing maturity often comes from refining structure, not from adding more rules.  Send alerts that matter! Signal quality for AI and automation Recent internal AIOps guidance is clear that AI-driven capabilities deliver the most value when paired with strong monitoring fundamentals. The recommendation is not to skip tuning, but to use dynamic thresholds and related AIOps features to tighten alerting without losing visibility. Internal community recap content also highlights that hybrid thresholds remain useful, and that noisy environments can still benefit from downstream correlation, but cleaner alert quality reduces unnecessary usage and operational friction. Best Practices Use Dynamic Thresholds Selectively Start with metrics that vary meaningfully and are relevant to your IT operational needs, such as interface bandwidth, latency, or queue depth. Apply dynamic thresholds where static-only alerting creates too much noise or misses abnormal behavior. Avoid enabling dynamic thresholds for every datapoint without validation. Pilot on a limited scope first, so you can evaluate signal quality before expanding. Keep Static Guardrails Where Business Risk Demands It Maintain static thresholds for conditions that should never cross a hard limit. Use static thresholds to protect critical services, capacity ceilings, or business-sensitive resources. Pair static thresholds with dynamic thresholds when both anomaly detection and hard boundaries are valuable. Use hybrid thresholding where operational risk requires both flexibility and control. Design Suppression Carefully Suppress routed noise where it improves the signal-to-noise ratio. Preserve enough alert visibility for investigation, trend analysis, and root cause review. Make sure suppression reduces interruption without reducing observability. Validate what remains visible in the portal after suppression settings are applied. Make Automation Safe Confirm ownership before alerts trigger downstream workflows. Control duplication across alert rules, escalation paths, and external integrations. Make escalation behavior intentional before introducing automation. Remember that automation amplifies the quality of the alerting design already in place. Implementation Checklist ✅ Identify high-variability datapoints that are poor fits for static-only alerting ✅ Pilot dynamic thresholds on a limited, high-value scope ✅ Decide where hybrid thresholds provide the right balance ✅ Enable suppression carefully and validate what remains visible ✅ Review rule priority and chain behavior for duplicate downstream notifications ✅ Confirm escalation timing, rate limits, and ownership before automation is added ✅ Revisit noisy conditions after rollout and adjust based on actual signal quality Conclusion Advanced alert management makes alerting adaptive, scalable, and ready for broader operational workflows. When teams combine clean fundamentals with dynamic thresholds, thoughtful suppression, and disciplined routing, they create a signal that is easier to trust and easier to act on. Additional Resources Dynamic Thresholds for Datapoints Different Levels for Enabling Alert Thresholds Alert Rules Escalation Chains Managing Alerts from the Alerts Page Datapoint Overview

Overview This month’s Product Power Hour focused on a topic that continues to matter for every operations team: how to reduce alert noise without losing visibility into what matters most . The session brought together product and training experts to walk through alert tuning best practices, threshold strategies, routing guidance, topology-driven troubleshooting, and new diagnostic and remediation capabilities . The biggest takeaway was clear: effective alerting starts with tuning before routing . Rather than sending every alert downstream and overwhelming teams, the presenters encouraged customers to use alert reports, review noisy signals regularly, and build a more intentional alerting strategy that evolves with the environment. Key Highlights 🌟 Start with reports before routing alerts. The team recommended using Alert Frequency and recent alert reports to identify what is noisy versus what is actionable. 🌟 Treat alert tuning as an ongoing process. As environments scale and change, thresholds and alert strategies should be reviewed regularly instead of being treated as a one-time setup. 🌟 Use the right threshold model for the workload. Static thresholds work well for predictable resources like disk capacity, while dynamic thresholds are better suited for changing environments such as cloud and autoscaling workloads. 🌟 Combine static and dynamic thresholds for critical systems. A hybrid model can provide both a hard safety net and early anomaly detection for customer-facing applications, APIs, and databases. 🌟 Keep alert routing simple. Strong resource group structure reduces complexity and makes it easier to route alerts to the right team, system, or escalation path. Leverage topology, dependent alert mapping, and new troubleshooting tools. Automated diagnostics, remediation workflows, correlated metrics, and topology edge status can help teams identify root cause faster and reduce alert storms. Q&A Q: Does our LogicMonitor alert policies fully cover our Azure architecture, including dependencies such as load balancers, VNets, SQL MI, application gateways, and managed PAS services? Enhancement planned? A: Yes. LogicMonitor attaches built-in logic modules to those Azure and cloud components. Some of those modules include default alert thresholds, and if they do not, or if the defaults are not right for your environment, you can customize them. Q: Is there a report that lists static threshold modifications below the module level so admins can see where thresholds were changed from default? A: Yes. You can use the alert threshold report for that. If you have a large environment, you may need to filter by resource group or narrow the results. You can also use audit logs to see who changed what. Q: Do we have some real-time use cases as templates or ready-to-go settings that we can utilize for alert thresholds? A: Yes. The default thresholds built into logic modules are the starting point. They are based on LogicMonitor and customer experience, but you should still review and tune them for your own environment. Q: If you update logic modules, will you lose historical data? A: There is potential for that, depending on what changes in the module. That is why it is important to review the impact before updating. LogicMonitor does provide ways to compare the current and new versions before you apply changes. Q: Are automated diagnostics and remediation included in platform pricing, or is there additional pricing? A: It is included in the newer platform packages: Essentials, Advanced, and Signature. For other package types, it may require an add-on. Q: Does LogicMonitor automatically detect GeoIP or geolocation for servers in a hybrid infrastructure? A: Not automatically, based on the discussion in this session. You would typically need to set that location property yourself, usually through CSV upload, APIs, or a custom logic module. Q: How can we restore a module after an update? A: The best practice is to clone before updating. There is also a revert option in the module toolbox that lets you compare versions and roll back changes. Customer Call-outs ⭐️ “I like that [geolocation] custom module option that you mentioned.” 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 Hours Detect Digital Experience Issues Earlier with Catchpoint A Catchpoint-focused Product Power Hour is coming in May on detecting digital experience issues. This session will spotlight how teams can more effectively identify and troubleshoot user experience problems. Tuesday, May 5 at 11 AM CT 👉 Register here Optimize Cloud Spend with Confidence The next cost optimization session is scheduled for May 19 and will cover how practitioners can turn cloud cost visibility into action and explore new cost views in Resource Explorer and Cloud Budget Alerts to help teams stay ahead of spend and act faster across multi-cloud environments. May 19 at 10 AM CT 👉 Register here 🍽️ Chicago User Group The team is heading back on the road with an upcoming Chicago user group, featuring community conversations and field engagement with LogicMonitor experts. May 27 at 6 PM CT 👉 Register here Resources and Review 🏅Want to upskill? Earn your Alerts badge ! 💻 Review the slide deck here 📹Watch the recording here or directly on the event page .