Closed mikegorman-nf closed 2 years ago
We have a separate issue for tracking link ip/port info. This issue is just to add ip/port of ERs when creating api sessions for router-embedded tunneler.
We currently only track IP address and not port for sessions created via REST. I'm tracking IP:Port for edge routers, but let me know if that will mess up reporting and if we should update the REST api sessions to also include port. @mikegorman-nf @mguthrie88
In order to attribute raw network connections (TCP,UDP,QUIC, etc) to Ziti links for performance analysis, there needs to be a method to index the two togther. Having the IP:PORT information in the logs will allow such attribution and enhance performance management.