212543df06
We investigated this at length and cannot figure out what could possibly be happening based on the logs. Logging the fact that kill failed should help us at least narrow it down further. Also adding a sleep between killing app health and vmwatch to reduce the chance of any races (vmwatch should die naturally when app health is killed but it may not happen immediately so giving it a second to respond should reduce the times it needs to be killed independently. |
||
|---|---|---|
| .devcontainer | ||
| .github/workflows | ||
| .vscode | ||
| integration-test | ||
| internal | ||
| main | ||
| misc | ||
| pkg/logging | ||
| vendor | ||
| .dockerignore | ||
| .gitattibutes | ||
| .gitignore | ||
| .travis.yml | ||
| ISSUE_TEMPLATE | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| SECURITY.md | ||
| go.mod | ||
| go.sum | ||
| test.Dockerfile | ||
README.md
Azure ApplicationHealth Extension for Linux (V2)
The application health extension periodically probes for application health within a Linux VM when configured. The result of the health checks guide automatic actions that can take place on VMs such as stopping rolling upgrades across a set of VMs and repairing VMs as they become unhealthy.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.