Azure VMware Solution
It is crucial to monitor the resource utilization in order to take timely action. This solution helps in setting up Azure Monitor alerts for Azure VMware Solution Private Cloud. Action owners will receive email notifications if utilization metrics exceeds set threshold.
Please do not operate Azure VMware Solution Private Cloud above the thresholds provided below. If you ignore alerts for the threshold values below then in case of outage, Azure credits are not provided. Similarly, do not upgrade HCX past the latest greenfield tested version. If you do so, no Azure credits are provided for any outage.
Current Version: v1.1.0 (Apr 15, 2024)
Table below shows the Alerts configured after the deployment.
| Name | Threshold(s) (Severity) | Signal Type | Frequency | # Alert Rules |
|---|---|---|---|---|
| CPU - Percentage CPU (%) | 80 (2) | EffectiveCpuAverage | Every 5 minutes | 1 |
| CPU - Percentage CPU (%) (Critical) | 95 (0) | EffectiveCpuAverage | Every 5 minutes | 1 |
| Memory - Average Memory Usage (%) | 80 (2) | UsageAverage | Every 5 minutes | 1 |
| Memory - Average Memory Usage (%) (Critical) | 95 (0) | UsageAverage | Every 5 minutes | 1 |
| Disk - Percentage Datastore Disk Used (%) | 70 (2) | DiskUsedPercentage | Every 5 minutes | 1 |
| Disk - Percentage Datastore Disk Used (%) (Critical) | 75 (0) | DiskUsedPercentage | Every 5 minutes | 1 |
| Service Health Alerts | N/A | ServiceHealth | N/A | 1 |
Table below shows additional Alerts to be configured. These are not yet covered as part of the deployment script. Monitor these metrics manually.
| Name | Threshold(s) (Severity) | Signal Type | Frequency | # Alert Rules |
|---|---|---|---|---|
| Cluster node count | 14 (2) | N/A | After every node addition | N/A |
| Private Cloud node count | 90 (2) | N/A | After every node addition | N/A |
| Delete lock on resource group count | 1 (2) | N/A | After Private Cloud creation | N/A |
| Stretched cluster ExpressRoute circuit count | 2 (2) | N/A | After Private Cloud creation | N/A |
| Private Cloud (Primary + Secondary) count | 2 (2) | N/A | After Private Cloud creation | N/A |
| Private Cloud LDAPS Identity source count | 2 (2) | N/A | After Private Cloud creation | N/A |
| Private Cloud DNS server count | 3 (2) | N/A | After Private Cloud creation | N/A |
| Private Cloud vSAN FTT configuration (< 6 nodes) | RAID-1 FTT-1 (2) | N/A | After Private Cloud creation | N/A |
| Private Cloud vSAN FTT configuration (>= 6 nodes) | RAID-1/6 FTT-2 (2) | N/A | After Private Cloud creation | N/A |
| vSphere DRS Automation Level (on-premises VCenter Server) | Partially Automated (2) | N/A | After Private Cloud creation/HCX Upgrade/Redeploy | N/A |
Once you’ve had an opportunity to deploy the solution we’d love to hear from you! Click here to leave your feedback.
If you have encountered a problem please file an issue in our GitHub repo GitHub Issue.
We have a Deployment Guide available for guidance on how to consume the contents of this repo.
Please see the Known Issues.
Please see the Frequently Asked Questions.
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
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.
Details on contributing to this repo can be found here
When you deploy the IP located in this repo, Microsoft can identify the installation of said IP with the deployed Azure resources. Microsoft can correlate these resources used to support the software. Microsoft collects this information to provide the best experiences with their products and to operate their business. The telemetry is collected through customer usage attribution. The data is collected and governed by Microsoft’s privacy policies.
If you don’t wish to send usage data to Microsoft, or need to understand more about its’ use details can be found here.
This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft’s Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party’s policies.