Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Azure Frontdoor health probe request increase #82741

Closed
mllipi opened this issue Oct 21, 2021 · 3 comments
Closed

Azure Frontdoor health probe request increase #82741

mllipi opened this issue Oct 21, 2021 · 3 comments

Comments

@mllipi
Copy link

mllipi commented Oct 21, 2021

ISSUE: Accordingly to our public documentation. AFD probe requests should be around 200 requests per minute using the default probe configuration.
https://docs.microsoft.com/en-us/azure/frontdoor/front-door-health-probes

This information is outdated, as the number of AFD probe requests jumped to around 600 requests per minute.

ASK: Please amend the documentation to reflect the actual number of probe requests Azure Frontdoor will send to backend.

IMPACT: Customer may experience issues with backend due to the volume increase in probe requests and needs to adjust the probe interval to lower the number of probe requests.


Document Details

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

@GitaraniSharma-MSFT
Copy link
Contributor

@mllipi , thank you for your feedback. We'll review this and get back to you shortly!

@GitaraniSharma-MSFT
Copy link
Contributor

@mllipi , We have assigned this to the content owner/author for review.

@duongau , I've looped you in the internal email with the Front Door PG to confirm this & update the doc accordingly.

@duongau
Copy link
Contributor

duongau commented Mar 29, 2022

Hi @mllipi, apologies on the late response here. The PG team has updated the documentation with the following statement:

Since each Azure Front Door edge POP emits health probes to your origins, the health probe volume for your origins can be quite high. The number of probes depends on your customer's traffic location and your health probe frequency. If the Azure Front Door edge POP doesn’t receive real traffic from your end users, the frequency of the health probe from the edge POP is decreased from the configured frequency. If there is customer traffic to all the Azure Front Door edge POP, the health probe volume can be high depending on your health probes frequency.

An example to roughly estimate the health probe volume per minute to your origin when using the default probe frequency of 30 seconds. The probe volume on each of your origin is equal to the number of edge POPs times two requests per minute. The probing requests will be less if there is no traffic sent to all of the edge POPs. For a list of edge locations, see https://docs.microsoft.com/en-us/azure/frontdoor/edge-locations-by-region for Azure Front Door. There could be more than one POP in each edge location.

The information above should help users find a rough estimate of how many probes their backend resources would receive. Please let me know if you have any questions. For now I will archive this issue. Thank you. #please-close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants