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.billbianco3 days agoNeophyte152Views4likes4Comments- 133Views0likes0Comments
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 propertiesBarb14 days agoAdvisor53Views1like0CommentsScripts 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.DDryang14 days agoNeophyte52Views2likes1CommentDashboard 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 +.15Views0likes1CommentExport 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 | LogicMonitorryang15 days agoNeophyte31Views0likes1CommentColoured Text instead of Coloured Bars
Can we get an option to have coloured text instead of coloured bars? This datasource I built can (probably should) have all values be coloured, so having the text be coloured would probably look neater than lots of coloured bars (+ there is obviously a max of 2 coloured bars). Will submit a feature request directly as well. Thanksldoodle24 days agoAdvisor15Views1like1Comment