Recent Discussions
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.
Needed Features for Network Topology Mapping
We need the ability to create topology map of our switches and routers showing the actual links between interfaces on the devices and showing the latest InMbps / OutMbps datapoints for each interface. The goal is to have a live network map for networks like Internet Service Provider networks, to be able to visualize the active state of the network and the bandwidth utilization and alert status of each device and interface / link. We need to be able to do the following: - Manually add the switch and router resources to the map. - Once the resource is on the map, click on the resource on the map and select an interface instance from the "network interfaces" LogicModule to add to a "Link". Then drag over to, or select, the connected resource, and select the associated interface instance from the "network interfaces" LogicModule on the second device. - This will visually show a link between the two devices, and the InMbps and/or OutMbps datapoints should be displayed over the link on each end of the link. - The color of each half or end of the link should also change based on the highest active alert level for the associated "network interfaces" instance on that end of the link. So for example, If we have Router1 interface GigEth0/1 connected to Router2 GigEth0/2, and Router1 GigEth0/1 has an active warning level alert for InBroadcastPkts, then that half of the line representing the link, should turn to yellow. - It's not enough to simply outline the resource with a color based on the alert level of the resource. We need to visually see each desired interface / link on the map and see visually which interface(s) is/are alerting. LogicMonitor has done an absolutely outstanding job of giving us immense flexibilty in how we can represent any datapoint on widgets on dashboards. But when it comes to the Topology mapping, we’re severely limited in how we can represent the exact same datapoints visually on the map. Also, for these kind of use-cases, people managing these kinds of network generally already know how their devices are connected, or can easily identify the connectivity. We don’t really need LogicMonitor to automatically detect connections between devices, because that’s too big of a challenge to automate that well. We just need to be able to manually say, “This interface on this device connects to this interface on this device. That’s a link.” The link itself is actually comprised of two sides, each being an instance on the resource’s LogicModule. And it could be “Interfaces 64 bit” or “Network Interfaces” or whatever other LogicModule we need. When we make w widget, we can select whatever LogicModule and Instance we need. We should be able to do the same thing on the topology map.Dependent Alert Mapping - reviewing cleared alerts
I recently had an LM support ticket open for some confusion we had around the Dependent Alert Mapping feature. Wanted to document some areas for improvement here that would make the feature work better. Currently, when an alert clears which was processed by Dependent Alert Mapping, the "Routing State" and "Dependency Role" columns set to blank. This makes it challenging to go back and review alerts after an outage to see what was "Originating" vs "Dependent" Please update the feature so that these columns on the alert table are still populated after an alert clears. This will help us with reviewing and reporting on resolved outages Currently when an alert is suppressed by dependent alert mapping, the alert message contains a lot of useful metadata related to the alert suppression. But if the originating alert clears and the dependent alert is still active, all of that metadata is removed and there is no indication that the alert was ever suppressed by the Dependent Alert Mapping feature This causes confusion when we go back to review past outages. It makes it look like the feature did not work as intended, even if it did. Fixing this along with item #1 would make the feature a lot easier for us to use and understand what it is doing.
Website Monitoring - Improvement Request
In Website monitoring, we are looking for A metric to configure threshold for response time and get alerted (Currently we just have graph for response time). To have historical data saved in LM portal for Total Download Time (Currently we can configure threshold, but unable to view historical data which could help us to determine the generic response time).