Skip to content

Commit

Permalink
Merge pull request #140 from MicrosoftDocs/main
Browse files Browse the repository at this point in the history
9/12/2024 PM Publish
  • Loading branch information
Taojunshen authored Sep 12, 2024
2 parents 558a2a4 + bade5de commit e427034
Show file tree
Hide file tree
Showing 11 changed files with 36 additions and 36 deletions.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
64 changes: 32 additions & 32 deletions articles/service-fabric/service-fabric-versions.md

Large diffs are not rendered by default.

Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ This article assumes that you're familiar with:
- [Modifying](virtual-machine-scale-sets-upgrade-policy.md) Virtual Machine Scale Sets

> [!CAUTION]
> Application Health Extension expects to receive a consistent probe response at the configured port `tcp` or request path `http/https` in order to label a VM as *Healthy*. If no application is running on the VM, or you're unable to configure a probe response, your VM is going to show up as *Unhealthy* (Binary Health States) or *Unknown* (Rich Health States). See [application health samples](https://github.com/Azure-Samples/application-health-samples) for examples of emitting health probe responses to a local endpoint.
> Application Health Extension expects to receive a consistent probe response at the configured port `tcp` or request path `http/https` in order to label a VM as *Healthy*. If no application is running on the VM, or you're unable to configure a probe response, your VM is going to show up as *Unhealthy* (Binary Health States) or *Unknown* (Rich Health States). See [application health samples](https://github.com/Azure-Samples/application-health-samples) for examples of health probe responses being emitted to a local endpoint.
> [!NOTE]
> Only one source of health monitoring can be used for a Virtual Machine Scale Set, either an Application Health Extension or a Health Probe. If you have both options enabled, you will need to remove one before using orchestration services like Instance Repairs or Automatic OS Upgrades.
Expand Down Expand Up @@ -507,7 +507,7 @@ az vmss update-instances \
## Troubleshoot

### Need help configuring a probe response
See [application health samples](https://github.com/Azure-Samples/application-health-samples) for examples of emitting health probe responses to a local endpoint.
See [application health samples](https://github.com/Azure-Samples/application-health-samples) for examples of health probe responses being emitted to a local endpoint.

### View VMHealth - single instance
```azurepowershell-interactive
Expand Down
4 changes: 2 additions & 2 deletions articles/virtual-machines/extensions/health-extension.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ Application health monitoring is also available on virtual machine scale sets an
This article assumes that you're familiar with [Azure virtual machine extensions](overview.md).

> [!CAUTION]
> Application Health Extension expects to receive a consistent probe response at the configured port `tcp` or request path `http/https` in order to label a VM as *Healthy*. If no application is running on the VM, or you're unable to configure a probe response, your VM is going to show up as *Unhealthy* (Binary Health States) or *Unknown* (Rich Health States). See [application health samples](https://github.com/Azure-Samples/application-health-samples) for examples of emitting health probe responses to a local endpoint.
> Application Health Extension expects to receive a consistent probe response at the configured port `tcp` or request path `http/https` in order to label a VM as *Healthy*. If no application is running on the VM, or you're unable to configure a probe response, your VM is going to show up as *Unhealthy* (Binary Health States) or *Unknown* (Rich Health States). See [application health samples](https://github.com/Azure-Samples/application-health-samples) for examples of health probe responses being emitted to a local endpoint.
## When to use the Application Health extension
Application Health Extension reports on application health from inside the Virtual Machine. The extension probes on a local application endpoint and updates the health status based on TCP/HTTP(S) responses received from the application. This health status is used by Azure to monitor and detect patching failures during [Automatic VM Guest Patching](../automatic-vm-guest-patching.md).
Expand Down Expand Up @@ -421,7 +421,7 @@ The following example adds the Application Health extension to an existing virtu
## Troubleshoot

### Need help configuring a probe response
See [application health samples](https://github.com/Azure-Samples/application-health-samples) for examples of emitting health probe responses to a local endpoint.
See [application health samples](https://github.com/Azure-Samples/application-health-samples) for examples of health probe responses being emitted to a local endpoint.

### View VMHealth

Expand Down

0 comments on commit e427034

Please sign in to comment.