To add some context to what we have achieved with other integrations with Cloudgenix in the past:
The Topology API contains the necessary information at a site level to show all of the VPN Fabric connections and their status. When posting for a particular Site ID, you obtain a list of several "Types" of topology. For making Topology maps for use in mapping your SD-WAN, you look for the type "vpn". This will give you source and destination nodes to make pretty maps of the underlaying fabric from spokes to hubs, or spokes to spokes.
But for connectivity validation, using the status of the type: "internet-stub" you get a better idea of your ISP's validity at each location that goes beyond just Link Up/Down on any particular ION's interface. It is a direct representation of the SWI's ability to connect to the portal itself and is also used by Cloudgenix for use in making pathing decisions. This is what the Topo_App from ebob9 in github is doing to provide this data via synthetic web transactions so that basic monitoring tools like Thousand Eyes or Solarwinds can monitor this data.
Having LM do this directly via the portal API is a great advantage to us as it eliminates the middleware portion of our current monitoring.
