Incorrect number of Probes in template reference

[AndreasMWalter]

The minimum probe interval is 5 seconds and the minimum number of unhealthy responses is 2. The total duration of all intervals cannot exceed 120 seconds.

Your JSON example templates reference "numberOfProbes": 1 I know I might be having OCD here, but all three JSON template boxes reference an incorrect number of probes. The minimum allowed value is 2.

Also the minimum value is not reflected in the Arm template reference (and no maximum given): https://docs.microsoft.com/en-us/azure/templates/microsoft.network/loadbalancers?tabs=bicep#probepropertiesformat (should i open a different issue there?)

---

Document Details

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

• ID: 0e1e7cb2-c5a7-7122-c729-dc259db99a40
• Version Independent ID: 45c6fd72-5114-fcda-0bab-2d80ac6bed33
• Content: Health probes to scale and provide HA for your service - Azure Load Balancer
• Content Source: articles/load-balancer/load-balancer-custom-probe-overview.md
• Service: load-balancer
• GitHub Login: @asudbring
• Microsoft Alias: allensu

[ChaitanyaNaykodi-MSFT]

Hello @AndreasMWalter Thank you for your feedback! We will review and update as appropriate.

[cburuzie]

reassign:thisisanniefang

[thisisanniefang]

@AndreasMWalter Thanks for the feedback! The example templates are actually correct and the recommend configuration due to a current ongoing Known Issue (just added to https://docs.microsoft.com/en-us/azure/load-balancer/whats-new, and should appear soon).

We recommend setting the numberOfProbes property to 1 to reflect the current behavior.

please-close

[AndreasMWalter]

@AndreasMWalter Thanks for the feedback! The example templates are actually correct and the recommend configuration due to a current ongoing Known Issue (just added to https://docs.microsoft.com/en-us/azure/load-balancer/whats-new, and should appear soon).

We recommend setting the numberOfProbes property to 1 to reflect the current behavior.

please-close

Oh, ok, is this an issue that only affects the portal or also the API? And also is it generally recommended to use 1 or just due to the issue?

So many questions :)

[thisisanniefang]

@AndreasMWalter Apologies for the late reply! This is an issue that affects the API and Portal. We recommended using 1 due to the issue for the time being, as to not cause confusion with the actual behavior.

[AndreasMWalter]

@thisisanniefang so I tried setting this via Terraform, which would result in this error returned by the Azure API: So no dice in regards to setting this value to 1 via the API

Error: updating Load Balancer "lb" (Resource Group "rg") for Probe "probe": network.LoadBalancersClient#CreateOrUpdate: Failure sending request: StatusCode=400 -- Original Error: Code="NumberOfProbesIsOutOfRange" Message="NumberOfProbes value for probe azuinf-prd-probe is out of range. When IntervalInSeconds is 5, the value must be between 2 and 429496729." Details=[]
│ 
│   with module.infoblox.azurerm_lb_probe.internal_lb_probe,
│   on .terraform/3_loadbalancer.tf line 20, in resource "azurerm_lb_probe" "internal_lb_probe":
│   20: resource "azurerm_lb_probe" "internal_lb_probe" {

Terraform uses the most recent azure-sdk-for-go "github.com/Azure/azure-sdk-for-go/services/network/mgmt/2021-05-01/network"

[thisisanniefang]

Hi @AndreasMWalter thanks for reaching out, we're working to resolve this issue and remove the validation that is blocking the ability to set the value to 1.

For the time being, setting it to 2 will result in the same behavior as if it were set to 1 due to the known issue. Apologies for the confusion!