This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Dear Friends,
I have Standard public Load Balancer and I wont to monitor data path availability, but I cannot choose from metric it is missing . 
As per the below article, If your load balancer's backend pools are empty, the load balancer will not have any valid data paths to test. As a result, the data path availability metric will not be available, and any configured Azure Alerts on the data path availability metric will not trigger.
https://learn.microsoft.com/en-us/azure/load-balancer/load-balancer-standard-diagnostics#is-the-data-path-up-and-available-for-my-load-balancer-frontend
Can you please validate if the backend pools are not empty? I hope this helps! Let me know if you have any other questions.
----------
Please "Accept as Answer" and Upvote if any of the above helped so that it can help others in the community looking for remediation for similar issues.
Thanks for answer, it is not empty I have two machines and I am verified that I can reach both web sites using PIP of loadbalancer.
Hello @Surbanoski Aleksandar ,
Just wanted to provide an update on this issue. As I mentioned in my answer below, Azure Load Balancer Product Group team confirmed that this is not an expected behavior and were investigating this bug from their end.
They found that the metadata of this metric was missing some information and because of that it was taking time to show up in the metric list. They have updated it now with the correct information and the fix has been deployed to all regions.
Regards,
Gita
I found what it is. As I suspected it takes time until this metric shows up, for me took about 12+ hours.
Hello @Surbanoski Aleksandar ,
Thank you for the update. Glad to hear that the issue is now resolved.
Regards,
Gita
Hello @Surbanoski Aleksandar ,
I'm adding the summary of this issue here for a broader visibility:
I understand that you created a Standard public Load Balancer and wanted to monitor data path availability, but you couldn't this metric from the metric dropdown as it was missing. You had to wait and this metric showed up after 12+ hours.
By default, if your load balancer's backend pools are empty, the load balancer will not have any valid data paths to test. As a result, the data path availability metric will not be available, and any configured Azure Alerts on the data path availability metric will not trigger.
Refer: https://learn.microsoft.com/en-us/azure/load-balancer/load-balancer-standard-diagnostics#inbound-availability-alerting
However, this was not the case with your setup. Your load balancer's backend pool was not empty and it had two VMs and you verified that you are able to reach both web sites using the Public IP of load balancer.
So, I tried to recreate your setup in my lab and I was able to reproduce this issue. It looks like there is a lag in the availability of the "Data path availability" metric in Azure portal. I also found a few support cases raised by other customers with this issue.
I discussed this issue with the Azure Load Balancer Product Group team and they have confirmed that this is not an expected behavior. So looks like this is a bug in the product or infrastructure. I've already raised an internal work item for this bug and the PG team is investigating this from their end and will be fixing it soon. I will update this thread once this is fixed.
Kindly let us know if the above helps or you need further assistance on this issue.
----------------------------------------------------------------------------------------------------------------
Please "Accept the answer" if the information helped you. This will help us and others in the community as well.