Recent Discussions
Feature Request Transparency
I've recently been paying closer attention to feature requests and the responses they receive. Often, I see replies along the lines of, "We’ll pass that on to the developers." However, many of these requests seem to be quite old, and it's unclear whether any progress has been made. I understand there could be a number of reasons for this—technical limitations, resource constraints, shifting priorities, or simply a decision that the effort required may not justify the outcome. With that in mind, I wanted to ask: is there a centralized list of requested features that includes their current status from the LM team's perspective? Specifically, it would be helpful to know: What stage of development (if any) a request is in The priority level assigned to it Whether it's planned for a future release or update A development roadmap outlining features expected (or proposed) for release over the next year, regardless of whether they originated from community suggestions If such a list exists, where can I find it? And if not, could this be considered as a potential improvement? I believe having this kind of visibility would go a long way in helping users track progress, prioritize their own requests, and better understand which ideas are gaining traction.
Scripts on the Support portal should have a revision number
When a script is updated on the support portal eg a Netscan, they do not have a version. We have no idea if the version we have is the latest. We have to copy existing to a file. Copy the script off the support site and run a diff. eg Cisco Catalyst SD-WAN Monitoring | LogicMonitor How about a script revision number in the header? eg YYYY.MM.DD
DataSource/Property Source that monitors Cisco End of Life (EOL) or End of Support (EOS) dates.
DataSource/Property Source that monitors Cisco End of Life (EOL) or End of Support (EOS) dates. Using API from - https://developer.cisco.com/docs/support-apis/eox/#get-eox-by-serial-numbers with auto.entphysical.serialnum or auto.endpoint.serial_number propertiesExport Audit logs to 3rd party tools - like Splunk/Graylog etc
We can use the api to extract the audit logs, but it would be better if logs can be exported or sent to another tool like Splunk/Datadog/Graylog etc The api can get via: Swagger UI and specific to audit logs: Getting Access Log Details | LogicMonitorDashboard widget title sizing/centering
When making a widget, the required name cannot be scaled nor centered to the widget size. This causes an unreadable widget on bigger screens. The only workaround we currently have, is using a HTML widget, but this does not look great due to the names being a requirement. Currently, widgets look like this, you can imagine the Criticals text is very hard to read from a distance. Increasing the scale would benefit greatly on bigger screens. Placing the name in the center is an additional +.
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!
