Azure-docs: Http setting does not support seperate port for probe

[Sudharma]

Currently there is no way to add additional port for the health probe in the http setting! We can only configure the backend port. So the suggestion could be to provide additional port for health probe either in http-setting or in the custom health probe! Currently this is a blocker.!

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 05a592c5-5d16-e44d-d6c7-5d0b2c0833c4
• Version Independent ID: dd9d601c-5d4b-f1bc-01df-7e1d6b57d0da
• Content: Health monitoring overview for Azure Application Gateway
• Content Source: articles/application-gateway/application-gateway-probe-overview.md
• Service: application-gateway
• GitHub Login: @vhorne
• Microsoft Alias: victorh

[SaurabhSharma-MSFT]

@Sudharma To assist you better on your query could you provide us with the link to the document you are referring to ?
In case your query in not related to document content, open a new forum thread either in MSDN or StackOverflow as it could be better place to get help on your scenario where the community members could provide their expert guidance to you based on their experience.

[Sudharma]

@saurabhsensharma I am referring to this one https://docs.microsoft.com/en-us/azure/application-gateway/application-gateway-probe-overview
However Currently there are work around to create a seperate http-setting and assign the port for probe! I would be eager to know if you guys can implement a solution where you can provide capability for a custom probe to define a port OR provide http-setting with multi port option!

[Sudharma]

Found somewhere this --> https://feedback.azure.com/forums/217313-networking/suggestions/14095221-setting-a-probe-port-other-than-a-service-port-in

I hope this could help

[TravisCragg-MSFT]

@Sudharma Thanks for the feedback! Unfortunately, as you have already found, this is a current limitation of the product.

For product feature requests, the best place to give that feedback is on feedback.azure.com, and you have already found an existing piece of feedback which addresses the issue. We prioritize features that multiple people request, so your best bet is to upvote & comment on that existing suggestion.

[TravisCragg-MSFT]

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

[Sudharma]

@TravisCragg-MSFT I assumed that since the feedback was almost 3 years ago and the product would have matured in this case hence I added that as reference! Could you then suggest how do we add the health probe at different port other than application! I am currently doing as follows,

1. Create separate probe for health and create separate http-setting and map it.
2. create separate probe for actual app(since this is needed for WAF to connect to backend) and create separate http-setting and map it.

However in the latter case I have to map the path to the actual app health of backend which is of course not desirable.! (Since backend is another gateway whose health check is already defined as another probe, its totally a stale mate. )

Would be eager to know what is your suggestion on the original question