Recent Discussions
🛠️ 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.
Feature request: SDT timings similar to Patch Tuesday schedules in Azure
Basically within azure you can schedule patches for the second Tuesday of the month +n days so you can apply patches the Thursday after patch Tuesday, which doesn’t necessarily fall on the second Thursday of the month, Take the current month as an example, the second Thursday falls before patch Tuesday Would love a feature option with SDT to accomplish this for more automation instead of having to set up an SDT for patching every month.
Cisco Meraki License monitoring - Subscription - Licensing Model
One of our clients is using “Subscription Licensing” model since few months. But we do see Cisco Meraki License Module currently supports only per-device licensing. Hence, raising this Feature request for “Subscription Licensing” model. Meraki Licensing - Cisco Meraki Documentation
Dependent Alert Mapping - defining the originating alert
In the current Dependent Alert Mapping feature, alert suppression will only take place if an upstream device has an alert for the Ping or Host Status datasources for overall reachability. There are many cases where the upstream device will not be completely down, and instead will have an alert for an interface or BGP peer going down. This will still impact downstream devices, but Dependent Alert Mapping does not work correctly in these cases because the upstream device was not technically "down". I would like to request that the Dependent Alert Mapping feature give us the option to allow other types of alerts be considered when it determines what alert is "Originating" vs "Dependent". Ideally we would be able to define this when we are defining entry points. We could have the option of only using Ping or Host Status like the feature does today, or we could choose to select our own datasources for determining what the "Originating" alert is. This would allow us to get a lot more granular and make the feature a lot more flexible/powerful than it is today.
Different options for "Delete Instances..."
Recently had this discussion with a customer and it was brought to my attention to raise a feature request for this. Customer is requesting that there are more than two options for deleting instances in a module. Instead of "delete immediately" or "delete after 30 days", they are suggesting a few more options such as "delete after 7 days" or "delete after 14 days".Shared Dashboard Filters/Dropdowns
In the new UI there is a feature to build dashboard filters that allow you to narrow down which resources are displayed based on properties. So I can have an overall health dashboard, and add a "By Location" filter to allow me to use a dropdown to select which site to display data for based on a location property. The filters work pretty well, but the problem is they are only saved at the user-level. So every single user who looks at the dashboard needs to manually create and then save the filters themselves. Not a very good design if you ask me. My feature request is to allow us to save dashboard Views at the dashboard-level. So I as an LM admin can create a useful dashboard View with filters/dropdowns, and then when I save it the View can then be used by other users who may not be as comfortable creating filters in LM. Allowing us to save dashboard Views at the dashboard-level would really increase the accessibility of this feature so that the average LM user can just open a dashboard and use the filters that we have already defined.
