Recent Discussions
Device Notes Tab
Currently, my team tends to attach small important notes for devices (firewalls, servers, switches, etc.) in the Description box. These notes might indicate if the device is supposed to be decommed soon, which vault the device's credentials are stored in, if the device is fully managed, who/manages owns the device, who deployed the device, or various other things. The description box is not designed for this. So, there are obviously many issues with it. No accountability, no formatting, no separation, etc. Could we please request a feature where each device in LM has its own proper "Notes" tab? Notes could be time-stamped, author-stamped, edited, or deleted. Examples: "Device is scheduled to be decommissioned in 2 months. -User123 4/30/2025 18:00:00UTC" "Device is not managed. No creds available. Alert client in event of issues. -User567 4/05/2025 03:00:00UTC" "Power Supply replaced on 2/10/2024. -User567 2/10/2024 10:00:00UTC" Below shows where a note has been added to the Description Box for this device, indicating the PSUs were reseated on 4/30/2025. If there were a Notes tab, this snippet could be put there instead. Anyone seeing that device afterward would see that User123 made that note today at 2pm. Someone could add an additional note a few months later indicating those PSUs have been replaced, while removing the old note. If there is already a feature similar to this (or one in the works), please let me know.
Versa SD-WAN SNMP
Hello! We would like to request the development of a new LogicModule to support Versa SD-WAN monitoring using SNMP, rather than relying solely on the existing API-based module. While the current Versa SD-WAN module works for environments where API access is available and stable, not all deployments have consistent API accessibility — due to security restrictions, network segmentation, or other operational constraints. As a result, the current module isn't always viable in certain customer environments. We are requesting a set of SNMP-based LogicModules that can monitor the following key metrics: CPU utilization Memory (RAM) usage Ping/Reachability Interface status and traffic Uptime and system health Any other relevant metrics exposed via Versa’s SNMP MIBs (e.g. BGP state, device role, tunnels, throughput, etc.) This would allow LogicMonitor users to monitor Versa SD-WAN devices reliably even when the API is not accessible, and enable greater flexibility across hybrid and security-conscious environments. Thank you for considering this request!How to submit a Feature Request.
At LogicMonitor, we are dedicated to providing our customers with the best monitoring solutions and services. To ensure that we are meeting your needs, please share your feedback on our products by visiting our feedback form in the LM portal https://lmcloud.logicmonitor.com/santaba/uiv3/dashboard To submit your feedback successfully, please follow these steps: Click on the link provided Sign in to your LogicMonitor account Navigate to the ‘Support’ section Click ‘Contact Support’ Lastly, click ‘Feedback’ Provide a summary and descriptive message Click on ‘Submit’ Your input is invaluable in helping us understand how we can improve and continue to provide the best possible monitoring experience for our customers. You can share your ideas, vote on existing suggestions, and see what other members of our community are saying. We appreciate your time and effort in providing feedback and look forward to hearing from you. Thank you, The LogicMonitor Community Team.20 Collectors do not have an escalation chain set.
"No escalation chain has been specified for Collector 300, Collector 301, Collector 302, Collector 510, Collector 511, Collector 512, Collector 519, Collector 520, Collector 521, Collector 522, Collector 523, Collector 524, Collector 525, Collector 530, Collector 532, Collector 533, Collector 536, Collector 539, Collector 540, Collector 554" Yeah I know what it all means, but can we make the Escalation Chain column sortable so i can float "None" to the top.UIv4 Dashboards Page - Table Widgets and instance-level properties
In the new UIv4 dashboards page, we are now able to add properties to a Table Widget as columns. However we can currently only add device-level properties to Table Widgets. It would be really useful for a lot of use cases if we could add instance-level properties to a dashboard widget as well. For example if we had a table which showed interfaces, it would be useful to be able to show instance-level properties of the interface such as the interface description or interface vlan. Also being able to use the ##DSIDESCRIPTION## token within a table widget would be useful for the instance description, but we cannot do that either.Log Alerting - Clearing of stateful alerts
With alerts configured via LM Logs, we have the option to clear alerts after a certain time interval. The maximum time interval is 4 days. This is fine for Basic or Window-based log alerts where we have no clear condition, but with Stateful alerts there should be no maximum time that the alert can be active for. The purpose of Stateful alerts is to trigger an alert based off of a matching log, and then clear the alert based off of a different matching log which would indicate the issue is resolved. This would be great, except the maximum time limit of 4 days still applies to Stateful alerts. Please either increase the maximum time limit for Stateful alerts to something more reasonable like 30+ days, or remove the limit altogether so that the alert can only be cleared via the defined clear condition, or an Acknowledgement of the alert in LM.Issue with group-level thresholds in UIv4
In Uiv4, we now have the option to add a custom trigger or clear interval at the instance or group-level. This is good, but I noticed that if you don't set a custom trigger or clear interval on the threshold, then it defaults to "immediately" for the trigger/clear intervals. My feature request is to have the default trigger/clear interval be "inherit from datasource", and then if we want to customize at the group-level we can do so. Having the default trigger interval be "Immediately" for any instance or group-level threshold causes lots of problems if we have users setting thresholds who aren't aware that it will overwrite any trigger/clear interval set on the datasource-level.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.Topology Mapping - Edge connection alert status
In the current topology mapping, the device-level nodes will light up red/orange/yellow depending on what the highest severity alert is on that device. My feature request is to give us the option to show the status of the individual connections. So show the connection lines as green if they are healthy/connected, but if the interface or BGP peer is down then the connection should be red based on the alert status of the connected instance. Would also like more control over which alerts cause the mapping nodes/edges to light up. For example I might only want the NODE to light up if there is an alert for HostStatus, but if there is an alert for BGP or an Interface then I might want the edge to light up instead. That way I could get a great idea of what was going on just by looking at the map.
