Speaking to a customer/user of Ziti, they asked me the following question… if the ziti fabric does smart routing based on latency costs (both Route Costs + Dynamic Costs), is this information recorded in the fabric/controller and can this information be queried/extracted via the API - i.e., could we build a dashboard which shows which path is taken, why it was taken, what the improvement etc?
The controller records the latency information and the circuit path that is selected for each session. The information is available through the fabric’s management plane and can be accessed programmatically, but it is not currently exposed through the REST API.
Incorporating fabric information into the JSON/REST API has been a backlog item for a very long time.