Different Target Server Paths for HealthMonitor

[#1]

Use Case:

Target Endpoints to health check

prod: https://live.api.org.com/v1/users/ping

test: https://private-cloud.org.com/backends/v1/users/ping

TargetEndpoint

<HTTPTargetConnection>
    <LoadBalancer>
        <Algorithm>RoundRobin</Algorithm>
        <Server name="backend"/>
        <RetryEnabled>true</RetryEnabled>
        <MaxFailures>10</MaxFailures>
    </LoadBalancer>
    <HealthMonitor>
        <IsEnabled>true</IsEnabled>
        <IntervalInSec>60</IntervalInSec>
        <HTTPMonitor>
            <Request>
                <ConnectTimeoutInSec>10</ConnectTimeoutInSec>
                <SocketReadTimeoutInSec>30</SocketReadTimeoutInSec>
                <Port>80</Port>
                <Verb>GET</Verb>
                <Path>/v1/users/ping</Path>
            </Request>
            <SuccessResponse>
                <ResponseCode>200</ResponseCode>
            </SuccessResponse>
        </HTTPMonitor>
    </HealthMonitor>
    <Path>/v1/users</Path>
    <SSLInfo>
        <Enabled>true</Enabled>
        <ClientAuthEnabled>false</ClientAuthEnabled>
        <KeyStore>keystore</KeyStore>
        <KeyAlias>keyalias</KeyAlias>
    </SSLInfo>
</HTTPTargetConnection>

Target Server

- Environment: prod
  name: backend
  host: live.api.org.com
  port: 443

- Environment: test
  name: backend
  host: private-cloud.org.com/backends #this not work!
  port: 443

How I configure Target Server "backend"?

Recalling that the HealthMonitor does not perform the flows.