Destination IP is not present when enabling client side check

idan_frimark · May 16, 2019, 4:48am

Hi All,

I’ve tried to perform Istio checks base on destination IP’s.
Problem is that when the mixer-check is called on client side, destination.ip & destination.port are not present, however, on mixer-report those values are present.

From looking up the code, it seems that when calling to “ExtractCheckAttributes” on http/tcp there is not call to “GetDestinationIpPort()”.

Is it by design? Does a simple call to “GetDestinationIpPort()” like in “ExtractReportAttributes” will solve it?

Topic		Replies	Views
Missing destination side telemetry Policies and Telemetry	2	948	June 8, 2019
Out of process Mixer adapter to receive information about non-HTTP calls Policies and Telemetry	8	1135	March 21, 2019
Listchecker adapter not working with values of type ip_address Policies and Telemetry	3	1007	January 15, 2019
Collecting attribute instances from istio-ingressgateway on incoming requests Policies and Telemetry	5	792	February 25, 2019
External / originating IP not present in Access Logs Policies and Telemetry security	0	523	July 12, 2022

Destination IP is not present when enabling client side check

Related topics