HealthMonitor does not resolve variables.

Not applicable

We have following issue. All our test instances are using the only one target server, which is a simple HAProxy, driven by HTTP header.

To define which environment requests will be passed to we have a header with name="x-cloud-env"

For targets, callouts we set it with value of the variable taken from the global KVM, like:

<AssignMessage async="false" continueOnError="false" enabled="true" name="assign_aws_cloud_headers">
  <DisplayName>Assign AWS Headers Into Request</DisplayName>
  <Set>
    <Headers>
      <Header name="x-cloud-env">{flow.cloud-env}</Header>
    </Headers>
  </Set>
  <IgnoreUnresolvedVariables>true</IgnoreUnresolvedVariables>
  <AssignTo createNew="false" transport="http" type="request"/>
</AssignMessage>

For callout we have:

<Request clearPayload="true" variable="flow.ms.request">
        <Set>
            <Headers>
                <Header name="x-cloud-env">{flow.cloud-env}</Header>
            </Headers>
            <Path>{proxy.pathsuffix}</Path>
        </Set>
    </Request>

But it does not work for HealthMonitor:

<HealthMonitor>
      <IsEnabled>true</IsEnabled>
      <IntervalInSec>60</IntervalInSec>
      <HTTPMonitor>
        <Request>
          <ConnectTimeoutInSec>5</ConnectTimeoutInSec>
          <SocketReadTimeoutInSec>30</SocketReadTimeoutInSec>
          <Port>443</Port>
          <Verb>GET</Verb>
          <Header name="x-cloud-env">{flow.cloud-env}</Header>
          <Path>{flow.healthcheckurl}</Path>
        </Request>
        <SuccessResponse>
          <ResponseCode>200</ResponseCode>
        </SuccessResponse>
      </HTTPMonitor>
    </HealthMonitor>

Is there any possible solution for this? Right now we do some substitution during build, but it is a dirty hack and we'd like to get rid of it

1 3 145
3 REPLIES 3

Ahhh, let me see about that.

OK, I've raised a request-for-feature ticket for this. I agree this makes sense to do.

The ticket number is APIRT-3899 for your reference. If you have a commercial license, you can link your Customer account to that ticket number. To do that you need to open a ticket on the support portal.

That will allow you to get updates on that feature request, and it will allow us to formally track your interest in it.

I don't have an estimated delivery date, of course. This will go into the hopper and get triaged with all the other feature requests. We've done this sort of thing in the past, though. Pretty quickly.

@Dino @Dino-at-Google

Any update on this issue. Its been two years now for this.

We are facing similar issue.