Using HealthMonitor on ApiProxy through ProxyServer

[#1]

Using Apigee Private Cloud 4.16.01 and have an API Proxy with a target server that is on the Internet. Have successfully setup the target server with SSL and using a ProxyServer to connect from the internal LAN to the Internet.following how to do forward proxying using apigee gateway Calls to the API Proxy work fine to the target server through the ProxyServer.

Running into a problem when adding Load Balancing with HealthCheck..to the API Proxy. The HealthCheck always fails. The log states

2017-06-1416:45:38,423 Apigee-Timer-3 WARN SERVICES.HEALTH_MONITOR-TCPMonitor.monitor() :ConnectFailed test.someserver.com:443

While there are several conditions that could cause the ConnectFailed (adding the reason to the log would be nice), the leading theory is the HealthCheck is not using the ProxyServer when making the health check call. Does the <Property name="use.proxy">true</Property> get used when the HealthCheck occurs?

To reiterate, the API Proxy is using the ProxyServer and is successfully making the API call, but the HealthCheck fails. We can duplicate the GET API call that is configured in the Health Check outside of Apigee and it works fine as long as the ProxyServer is used. Without the ProxyServer, the call simply times out as the firewall blocks it.

[#2]

Which path do you want to monitoring?

1. Data center Load Balancer to Router, or

2) API proxy to backend system

[#3]

Option 2 to the backend, which in this case is to an external provider.

[#4]

@Wayne Irwin

AFAIK that property doesn't apply to TCP monitor.
cc @Madhumita Kumari

[#5]

That was what we suspected. We tried both TCP and HTTP monitor and both failed when a proxyserver is required. Is this an enhancement I should request?