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 likeInternet 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 theresource’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.182Views26likes12CommentsAbility to group interface instances?
Hello, As an MSP we've the need to group multiple interface instances (from different devices &different clients as well) in order to set common thresholds, reports, etc... From my research that isn't possible within LM. Anyone able to do that? This would be very useful from the monitoring/management perspective. Regards,26Views4likes2CommentsDynamic Instance Group Alert Tuning
This is not an advertisement by any means, just offering to help anyone who struggles with this as well. As an MSP,we have struggled with how to handle alert tuning in bulk with it comes to things like Interfaces (instances). Some of the interfaces you want to alarm as critical, some you want as error and others you don't care about at all. LM provided a partial fix for that with their Groovy based "Status" alarm based on the interface description, but it didn't take it far enough. We started creating manual interface groups called "Critical" and performing Alert Tuning on that "parent" only to find out that it doesn't work as interfaces move in and out of it. I was beyond disappointed, but it said it right at the top of the page:Changes made to Alerting or Thresholds will only affect existing instances currently in this Instance Group. Instances added later will not be subject to the changes. Anyway, long story short we finally decided to write our own application to do it and built it in Azure. We built it to handle multiple data sources so we could group other instances (like VMware vDisks) and do the same bulk changes. It was written to be a data source in your environment, so that you can apply it to whatever devices you want and just call out to the API with the device name. If you have any interest in using it, let me know. There are costs associated as Azure bills based on usage, but it is pretty small for us (< $200/mo). Trust me, I wish LM solved this without having to write the app!63Views1like1Comment