Recent Discussions
Feature Request: Alerts Clear Customization
It would be a great feature to allow customization when alerts clear in the Manage Alert Rules. Currently its off or on. Currently our escalation chain includes a phone call for Critical alerts as well as an integration with our ticketing system on Stage 1. When that alert clears, we still want the clear alert to go to our integration, but we don't want to trigger a phone call.
Synthetic Datasources - Complex datapoints
I would like to request that we have the option to create complex datapoints for the below 2 datasources. These modules currently cannot be customized without breaking, which LM support confirms is intended behavior for the synthetic datasources. Selenium_Synthetics_Overall SyntheticsSelenium I have a need to stop alerting on a specific status code (430 - Session not Created) which can only be done using a complex datapoint. This status code is reported when there is an issue with the Selenium node itself, not with the synthetic check necessarily. So when the Selenium node has an issue, we get a false alert from every synthetic check assigned to the Selenium node. We want to have alerts for a status code of 430 alert via a separate datapoint so we can route them to the team who manages the Selenium node. Instead of having them all be routed to the owner of the application we are monitoring with the synthetic check, which to them is a false alert.Network Interface - interface.description.alert_enable Property
Request that when the 'interface.description.alert_enable' property is used to identify interfaces we want to monitor and alert for UP\DOWN, that the 'Alerting Status' toggle, in the 'Instances' view within the UI, changes to OFF in the LogicMonitor UI for those we don't want to alert on. As opposed to having to manual check and review the RAW DATA for each interface and verify that the status is either '1' for alerting enabled or -1 to indicate alerting has been disabled.
Scale Computing HyperCore modules
With more and more customers looking to switch from VMware to Scale Computing HyperCore due to increased licence costs, it would be good if there were modules directly setup to cover collecting metrics e.g. Datasource, ConfigSource, PropertySource etc I'm sure the industry is going to be moving at large scale from VMware to Scale Computing HyperCore so it would be good to get this on the LogicMonitor radar. ThanksUIv4 Issue: Alert links no longer open new tab
I noticed that in UIv4, several types of alert links no longer open a new tab when you click on them. Instead they open the link in the current tab. This makes it frustrating to drill down into alerts when looking at a dashboard or list of alerts on the Resources tab. The below types of alert links no longer open a new tab, where they always have prior to UIv4. This negatively affects our NOC's workflow of troubleshooting alerts during an outage. Alerts tab on the resource tree when clicking the Resource or Instance links of an individual alert Alerts widget on dashboards when clicking the Resource link of an alert this used to go to the alerting instance Resource or Group link on log entry in LM Logs page If I am looking at a list of filtered alerts on a folder of the resources page and then click one of the alerts, I then would have to hit the Back button on the browser to go back to the folder and would lose filters. Same if I was looking at dashboard alerts, if I drill down into one I then have to press Back to return to the dashboard unless I do right-click and "Open New Tab".Add “Low” and “Informational” Severity Levels to Alignment with ITIL Framework
In an MSP environment, it's important to align the monitoring system severity levels with that of the ticketing system. Please consider adding the following severity levels: Low – For alerts that indicate minor issues or early signs of potential degradation, which do not yet require immediate action. Informational – For non-actionable alerts such as status updates, successful job completions, or environmental observations.
TLS Email Secure Delivery from Customer
Case 00303768 Customer would like to have TLS email encryption allowed on incoming emails to Logic Monitor for acknowledging alarms through email. TLS ensures that the connection between sending and receiving mail servers is encrypted, protecting email content from being intercepted and is a security requirement for our compliance with audits and customers. Thanks, Janus Henderson Investors
🛠️ Feature Request: Optimize Dell ME4 LogicModules to Reduce Excessive Login Activity
Summary: We’ve observed that the Dell PowerVault ME4 LogicModules in LogicMonitor are generating an excessive number of login events—up to 90+ per hour—using the same service account. This behavior is causing the Dell SAN Management Controller to interpret the activity as a brute-force attempt, leading to memory exhaustion and controller resets. Details: Each polling instance (volumes, pools, controllers, etc.) performs its own login once per hour. The Groovy scripts used in the LogicModules: Authenticate for every collection. Do not reuse tokens. Do not call /logout after completing the task. This results in a buildup of session data, triggering alerts like:“The Management Controller entered a memory exhaustion state and will reboot to recover.” Impact: Controller memory buffers fill up due to unclosed sessions. The SAN reboots to recover, risking operational stability. Audit logs show consistent spikes in login/session-expired events. Request: Please consider enhancing the Dell ME4 LogicModules to: Reuse authentication tokens across polling instances within the same collector session. Explicitly call /logout after each session to release memory. Consolidate login activity to reduce overhead and improve SAN performance. Why It Matters: This change would significantly reduce unnecessary login traffic, prevent SAN controller resets, and improve overall system reliability—especially in environments with high instance counts. Thank you for considering this request. Happy to provide logs and examples if needed.