Can anyone explain how the httpmonitor works?

Google Cloud Apigee
1

Hi,

We configured the httpmonitor in one of our proxy with an timeinterval of 5 sec. Below is our configuration

<IsEnabled>true</IsEnabled>
    <IntervalInSec>5</IntervalInSec>
    <HTTPMonitor>
        <Request>
            <ConnectTimeoutInSec>2</ConnectTimeoutInSec>
            <SocketReadTimeoutInSec>5</SocketReadTimeoutInSec>
            <Port>443</Port>
            <Verb>GET</Verb>
            <Path>/deepPing</Path>
            <Header name="TraceIdPrefix">loadbalancer_liveness_test</Header>
        </Request>
        <SuccessResponse>
            <ResponseCode>200</ResponseCode>
        </SuccessResponse>
    </HTTPMonitor>
</HealthMonitor><br />

As per our expectation,it has to do 36 (60 seconds / 5 probes * 3 targets) requests per minute but we are seeing 5700 requests per minute.

Why it is happening? Is it depends on the number of message processors?

Any quick help can be appreciable.

Regards,

Balu

2

Even when we allow for the number of message processors and the poll period and the number of target endpoints we still see a 3/4 fold increase in the number of heath monitor request hitting our target servers.

3

WOW - thats a lot of probes. 5700 requests per minute is too much.

I suggest that you contact Apigee Support regarding this.

4

The message processor has to be allowed to do the implementation and the endpoints have to be correct. The codes which have been provided here can be very useful for those who are going to implement that. The connect error 10060 could be solved by the code with some modification.

5

Thanks Dino,

We raise support ticket with Apigee, hope will get some solution.

6

I think you have put your comment on the wrong issue because it doesn’t appear to have any correlation to the original question?

1 Like