After years of suffering with the horrific (and broken) topology mapping, how about just giving us the ability to create our own dependencies/maps, similar to The Dude or MangeEngine's OpManager?

This is currently being worked on. We recognize the need to be able to fill in the gaps and correct things to get complete maps and facilitate RCA. I'm hesitant to post mockups here, but if you'd like to see the design we're working on I'd love to get some time on any of your calendar's to show you and get some feedback. Your CSM can arrange this if you just ask them for some time with Michael to see the "manual mapping" concept. As it stands now, you'd be able to drag and drop one node onto another. This would bring up a dialog that would let you input the edge type, direction, and in some cases allow you to search for an instance on the dragged device. But big picture, the goal is to allow you to create edges without having to write code, or even leave the mapping canvas.

Agreed, this needs a simple UI designer. Check out the learning bytes in the training portal. There's one called "Manual Topology Mapping". Maybe one of these days i'll make a UI where you can pick and choose the things you want related and it'll just spit out the topology source...

As it stands now, you'd be able to drag and drop one node onto another. This would bring up a dialog that would let you input the edge type, direction, and in some cases allow you to search for an instance on the dragged device. But big picture, the goal is to allow you to create edges without having to write code, or even leave the mapping canvas. I wanted to give this a bump here: This isn’t functioning if it is supposed to be in place.at best, the “Manual Mapping” option lets you attempt to create a line between two objects, but when you do make this attempt a prompt appears stating: “Both Source and Target should have External Resource ID (ERI) defined.” or, when both have an ERI defined: “The selected source node doesn't have valid instance available, manual edge can not be created.”So multiple Edges on devices with ERI’s can’t be created due to this. While I understand that this feature, in particular, is currently in testing… The entire community has voiced that the Topology feature, as it stands, is in dire need of revision and Dev attention.Version 1.86 has only made things worse.

From our Support Docs…Topology Mapping Overview | LogicMonitorhttps://www.logicmonitor.com/support/forecasting/topology-mapping/topology-mapping-overview LogicMonitor’s topology mapping capabilities are focused on layer 2 and layer 3 mapping. Specifically, the LogicMonitor platform leverages Link Layer Discovery Protocol (LLDP), Cisco Discovery Protocol (CDP), Border Gateway Protocol (BGP), Open Shortest Path First (OSPF), and Enhanced Interior Gateway Routing Protocol (EIGRP) to dynamically generate network topology maps that show how data flows among the many resources (switches, hosts, firewalls, routers, and other network components) in your environment.

Look in exchange for L3X4CH "Manual topology mapping" Set 'manual.upstream.deviceid' as a property, and give it the Device ID number(s) of the parent resource(s) separated by a comma. In cases where topo.namespace by the upstream device(s) you must provide the namespace(s) of the upstream device(s) using 'manual.upstream.namespace' separated by a comma. Use "none" if no namespace is required for one of a subset of device/namespaces e.g. namespace1,none,namespace2 Just tag devices from bottom up and it done! ie DB -> Web -> LoadBalancer

Manual topology mapping | LogicMonitor

21 Replies

michaeld
2 years ago
I’d be happy if topology mapping would just utilize LLDP/CDP as a starting point. It’d be better & more accurate than what’s currently happening.
Jordan-Eil
2 years ago

As it stands now, you'd be able to drag and drop one node onto another. This would bring up a dialog that would let you input the edge type, direction, and in some cases allow you to search for an instance on the dragged device. But big picture, the goal is to allow you to create edges without having to write code, or even leave the mapping canvas.

I wanted to give this a bump here: This isn’t functioning if it is supposed to be in place.
at best, the “Manual Mapping” option lets you attempt to create a line between two objects, but when you do make this attempt a prompt appears stating: “Both Source and Target should have External Resource ID (ERI) defined.” or, when both have an ERI defined: “The selected source node doesn't have valid instance available, manual edge can not be created.”
So multiple Edges on devices with ERI’s can’t be created due to this.
While I understand that this feature, in particular, is currently in testing… The entire community has voiced that the Topology feature, as it stands, is in dire need of revision and Dev attention.
Version 1.86 has only made things worse.
Mike_Rodrigues
Product Manager
2 years ago
This is currently being worked on. We recognize the need to be able to fill in the gaps and correct things to get complete maps and facilitate RCA. I'm hesitant to post mockups here, but if you'd like to see the design we're working on I'd love to get some time on any of your calendar's to show you and get some feedback. Your CSM can arrange this if you just ask them for some time with Michael to see the "manual mapping" concept.

As it stands now, you'd be able to drag and drop one node onto another. This would bring up a dialog that would let you input the edge type, direction, and in some cases allow you to search for an instance on the dragged device. But big picture, the goal is to allow you to create edges without having to write code, or even leave the mapping canvas.
Mosh
Professor
2 years ago
Agree, at every enterprise I've worked, manual topology mapping has been the only way to accurately describe an IT service.
Michael_Baker
Neophyte
2 years ago
Look in exchange for L3X4CH "Manual topology mapping"

Set 'manual.upstream.deviceid' as a property, and give it the Device ID number(s) of the parent resource(s) separated by a comma.

In cases where topo.namespace by the upstream device(s) you must provide the namespace(s) of the upstream device(s) using 'manual.upstream.namespace' separated by a comma. Use "none" if no namespace is required for one of a subset of device/namespaces e.g. namespace1,none,namespace2

Just tag devices from bottom up and it done! ie DB -> Web -> LoadBalancer
- neilticktin
  Neophyte
  2 months ago
  >> Look in exchange for L3X4CH "Manual topology mapping"
  Michael_BakerJust to make sure that I'm not being lame, you're saying there's a manual topology mapping module we can download from Exchange? I ask because in looking, I'm not seeing one.
  - Stuart_Weenig
    Legend
    2 months ago
    That may be one way. Another way is to use the built in manual mapping option.
    
    I did find that module in the exchange. It was built before LM had the aforementioned manual option. It's probably still valid though.
Stuart_Weenig
Legend
2 years ago
Agreed, this needs a simple UI designer.

Check out the learning bytes in the training portal. There's one called "Manual Topology Mapping". Maybe one of these days i'll make a UI where you can pick and choose the things you want related and it'll just spit out the topology source...