Recent Discussions
Alert Trigger Information In LogFile Test
For an Eventsource module it would be nice to see which trigger is alerting at what severity when running a Logfile test. While it is usually easy to see why a line in the log got picked up there are times where a trigger may be misconfigured that is not caught in testing. Adding a few more columns to show why the line was caught and the expected severity of the alerting would help getting these modules setup a bit quicker and limit mistakes.
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 properties
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.
MSSQL blocking Queries
We have a Database account configured in Logicmonitor to monitor SQL metrics. Logic Monitor is connecting with "read committed" transaction isolation level to run multiple queries, and it blocks if any other query is running that is not in a shared lock mode. LM runs those queries for 30 minutes, and other queries gets blocked. We are looking if the query transaction isolation level can be changed from Logicmonitor or adjust the timeout to something smaller, perhaps 5 or 10 minutes.UIv4 Dashboards - Table Widget Sorting is broken
Sorting on table widgets currently does not work in the UIv4 Dashboards Page. You are able to sort within the context of the page you have selected, but not within the context of the entire table. So if a table widget has 8 pages and I try and sort by one of the columns, it only sorts the values on whatever page I have selected. Where it should obviously sort by that column within the context of the entire table. The way it currently works is not useful in any way and prevents me from being able to use the UIv4 table widgets for any real purpose. Which is frustrating since the filtering option is only available in UIv4.
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
