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

How to Azure Load Balancer Health Prob to monitor health and repair VMSS #92235

Closed
Deepudev13 opened this issue Apr 29, 2022 · 3 comments
Closed

Comments

@Deepudev13
Copy link

[Enter feedback here]


Document Details

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

@kobulloc-MSFT
Copy link
Contributor

@Deepudev13 Thank you for your feedback! We are reviewing this and will get back to you shortly.

@kobulloc-MSFT
Copy link
Contributor

kobulloc-MSFT commented May 3, 2022

@Deepudev13 Below is the documentation for automatic instance repairs for Azure virtual machine scale sets (which includes a link for information on both Load balancer health probes and Application Health extension although only one of these can be used at a time):

https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-automatic-instance-repairs

Enable application health monitoring for scale set

The scale set should have application health monitoring for instances enabled. This can be done using either Application Health extension or Load balancer health probes. Only one of these can be enabled at a time. The application health extension or the load balancer probes ping the application endpoint configured on virtual machine instances to determine the application health status. This health status is used by the scale set orchestrator to monitor instance health and perform repairs when required.

If you'd like additional assistance setting up your VMSS, reach out on the Microsoft Q&A forums:
https://docs.microsoft.com/en-us/answers/topics/123/azure-virtual-machines-scale-set.html

@kobulloc-MSFT
Copy link
Contributor

@Deepudev13 We are going to close this thread as resolved but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.

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

3 participants