From 494454ac1355709feaf35334ec9735580f128190 Mon Sep 17 00:00:00 2001 From: jessiehaessler Date: Fri, 6 Dec 2024 12:52:57 +0100 Subject: [PATCH 1/5] Specialized workloads - Oracle IaaS baseline alerts --- .../oracle/oracle on azure iaas/FAQ.md | 41 +++++++++ .../oracle/oracle on azure iaas/_index.md | 84 +++++++++++++++++++ .../oracle on azure iaas/known-issues.md | 7 ++ 3 files changed, 132 insertions(+) create mode 100644 docs/content/patterns/specialized/oracle/oracle on azure iaas/FAQ.md create mode 100644 docs/content/patterns/specialized/oracle/oracle on azure iaas/_index.md create mode 100644 docs/content/patterns/specialized/oracle/oracle on azure iaas/known-issues.md diff --git a/docs/content/patterns/specialized/oracle/oracle on azure iaas/FAQ.md b/docs/content/patterns/specialized/oracle/oracle on azure iaas/FAQ.md new file mode 100644 index 000000000..9cb17e6b5 --- /dev/null +++ b/docs/content/patterns/specialized/oracle/oracle on azure iaas/FAQ.md @@ -0,0 +1,41 @@ +--- +title: Frequently Asked Questions +geekdocCollapseSection: true +weight: 80 +--- + +> ## Do I need to use the thresholds defined as default values in the metric rule alerts? +> +> It's provided as a starting point, we've based the initial thresholds on what we've seen and what Microsoft's documentation recommends. You will need to adjust the thresholds at some point. +> You will need to observe and if the alert is too chatty, adjust the threshold up; if it's not alerting when there's a problem, adjust the threshold down a bit, (or vice-versa depending on what metric or log error is being used as a monitoring source). Once you have decided upon an appropriate value, if you feel it's fit for more general consumption we would love to hear about it. +> +> ## Do I need to use these metrics or can they be replaced with ones more suited to my environment? +> +> The metric rules we've created are based on recommendations from Microsoft documentation and field experience. How you're using Azure resources may also be different so tailor the alerts to suit your needs. The main goal of this project is to help you have a way to do Azure Monitor alerts at scale, create new rules with your own thresholds. We'd love to hear about your new rules too so feel free to share back. +> +> ## How much does it cost to run the ALZ Baseline solution? +> +> This depends on numerous factors including how many of the alert rules you choose to deploy into your environment, this combined with how many subscriptions inherit the baseline policies and resources deployed within each subscription that match the policy rules triggering an alert rule and action group deployment influence the cost. +> +> The solution is comprised of alert rules. Each alert rule costs ~0.1$/month1. +> +> - Alert rules are charged based on evaluations. +> - Assuming the alert rule had data to evaluate all throughout the month, it'll cost ~0.1$1. +> - If the rule was only evaluating during parts of the month (e.g. because the monitored resource was down and didn't send telemetry), the customer would pay for the prorated amount of time the rule was performing evaluations. +> - Dynamic Threshold doubles the cost of the alert rule (~0.2$/month in total1) +> - Our solution configures an email address as part of the Action groups deployment (one per subscription) and these are charged at ~2$/month per 1,000 emails1. +> +> **Whilst it is not anticipated that the solution will incur significant costs, it is recommended that you assess costs as part of a deployment to a non-production environment to make sure you are clear on the costs incurred for your deployment** +> +> For costings related to your deployment please visit [Pricing - Azure Monitor](https://azure.microsoft.com/en-us/pricing/details/monitor/) and work with your local Microsoft account team to define a rough order of magnitude (RoM) costings +> +> 1 Depending on the region you deploy to their may be a small difference in the associated cost, the costs provided here are based on prices captured as of April 2023 +> +> ## Can I use AMBA without a GitHub repository +> +>

Yes, as long as the ARM templates are publicly accessible. There are several linked templates in this solution which require to be publicly accessible. This is because when the top level ARM template is submitted to Azure Resource Manager, the linked templates are not automatically uploaded and therefore need to pulled in at deploy time from Azure. This means they must be referenced using a URL which can be accessed from Azure (e.g. via a public GitHub repository)

+>

An alternative is to use Template specs. Instead of maintaining your linked templates at an accessible endpoint, you can create a template spec that packages the main template and its linked templates into a single entity you can deploy. The template spec is a resource in your Azure subscription. It makes it easy to securely share the template with users in your organization. You use Azure role-based access control (Azure RBAC) to grant access to the template spec. This feature is currently in preview.

+> +> References: +> - [Template specs](https://learn.microsoft.com/en-us/azure/azure-resource-manager/templates/linked-templates?tabs=azure-powershell#template-specs) +> - [ARM Private deployment](https://github.com/Azure/ARM-private-deployment) diff --git a/docs/content/patterns/specialized/oracle/oracle on azure iaas/_index.md b/docs/content/patterns/specialized/oracle/oracle on azure iaas/_index.md new file mode 100644 index 000000000..a0ad7e299 --- /dev/null +++ b/docs/content/patterns/specialized/oracle/oracle on azure iaas/_index.md @@ -0,0 +1,84 @@ +--- +title: Oracle on Azure IaaS +geekdocCollapseSection: true +--- + +## Overview + +Monitoring Oracle on Azure IaaS allows for timely actions towards performance, reliability and security nd improves these. +This solution helps in setting up the right Azure Monitor alerts for your utilization on the virtual machines and disks. Action owners will receive email notifications if utilization metrics exceeds set threshold. + +{{< hint type=note >}} +Please do not operate Oracle on Azure IaaS solutions outside the thresholds provided below. If you ignore alerts for the threshold values below performance degradation appear. Following if thresholds are exceeded an always available database cannot be guaranteed. +{{< /hint >}} + +**Current Version:** +v0 (Dec 6, 2024) + +## Alerts Table + +Table below shows the Alerts configured after the deployment. + +| Name | Threshold(s) (Severity) | Signal Type | Frequency | \# Alert Rules | +| ---------------------------------------------------------- | ------------------------------------------ | ----------------------- | --------- | -------------- | +| Percentage CPU > 95 | 95 (2) | Log Analytics | 5 min | Default | +| Percentage CPU >= 85 | 85 (1) | Log Analytics | 5 min | Default | +| Percentage CPU >= 75 | 75 (2) | Log Analytics | 5 min | Default | +| VmAvailabilityMetric < 1 | < 1 (0) | Log Analytics | 5 min | Default | +| OS Disk Bandwidth Consumed Percentage >= 95 | 95 (0) | Log Analytics | 5 min | Default | +| OS Disk Bandwidth Consumed Percentage >= 90 | 90 (1) | Log Analytics | 5 min | Default | +| Available Memory Bytes < 500000000 | < 500000000 (1) | Log Analytics | 5 min | Default | +| VM cached Bandwidth Consumed Percentage > 95 | 95 (2) | Log Analytics | 5 min | Default | +| VM cached Bandwidth Consumed Percentage > 85 | 85 (2) | Log Analytics | 5 min | Default | +| VM cached Bandwidth Consumed Percentage > 75 | 75 (2) | Log Analytics | 5 min | Default | +| VM uncached Bandwidth Consumed Percentage > 95 | 95 (2) | Log Analytics | 5 min | Default | +| VM uncached Bandwidth Consumed Percentage > 85 | 85 (2) | Log Analytics | 5 min | Default | +| VM uncached Bandwidth Consumed Percentage > 75 | 75 (2) | Log Analytics | 5 min | Default | +| Data Disk IOPS Consumed Percentage > 95 | 95 (2) | Log Analytics | 5 min | Default +| Data Disk IOPS Consumed Percentage > 85 | 85 (2) | Log Analytics | 5 min | Default | +| Data Disk IOPS Consumed Percentage > 75 | 75 (2) | Log Analytics | 5 min | Default | +| OS Disk Bandwidth Consumed Percentage > 95 | 95 (2) | Log Analytics | 5 min | Default | +| OS Disk Bandwidth Consumed Percentage > 85 | 85 (2) | Log Analytics | 5 min | Default | +| OS Disk Bandwidth Consumed Percentage > 75 | 75 (2) | Log Analytics | 5 min | Default | +| VolumeConsumedSizePercentage per Lun >= 95 | \>=95 (0) | Log Analytics | 5 min | Default | +| VolumeConsumedSizePercentage >= 90 | \>=90 (2) | Log Analytics | 5 min | Default | +| UnhealthyHostCount >=1 | \>=1 (0) | Log Analytics | 5 min | Default | + + +## 📣Feedback 📣 + +Once you've had an opportunity to deploy the solution we'd love to hear from you! Click [here](https://aka.ms/alz/monitor/feedback) to leave your feedback. + +If you have encountered a problem please file an issue in our GitHub repo [GitHub Issue](https://github.com/Azure/azure-monitor-baseline-alerts/issues). + +## Monitor Oracle on Azure IaaS + +Review [Manage and Monitor Oracle](/azure/cloud-adoption-framework/scenarios/oracle-iaas/oracle-manage-monitor-iaas) for further guidance. + +## Contributing + +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](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](https://opensource.microsoft.com/codeofconduct/). +For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or +contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments. + +{{< hint type=note >}} +Details on contributing to this repo can be found [here](../../../contributing) +{{< /hint >}} + +## Trademarks + +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](https://www.microsoft.com/legal/intellectualproperty/trademarks/usage/general). +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. \ No newline at end of file diff --git a/docs/content/patterns/specialized/oracle/oracle on azure iaas/known-issues.md b/docs/content/patterns/specialized/oracle/oracle on azure iaas/known-issues.md new file mode 100644 index 000000000..f92774493 --- /dev/null +++ b/docs/content/patterns/specialized/oracle/oracle on azure iaas/known-issues.md @@ -0,0 +1,7 @@ +--- +title: Known Issues +geekdocCollapseSection: true +weight: 100 +--- + +## None at this time From 2def68f64ab2455c4b21c77ab594d6e0d12e846d Mon Sep 17 00:00:00 2001 From: jessiehaessler Date: Fri, 6 Dec 2024 13:46:14 +0100 Subject: [PATCH 2/5] PR for adding Oracle on Azure IaaS baseline alerts --- .../specialized/oracle/oracle on azure iaas/_index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/content/patterns/specialized/oracle/oracle on azure iaas/_index.md b/docs/content/patterns/specialized/oracle/oracle on azure iaas/_index.md index a0ad7e299..11c193b9d 100644 --- a/docs/content/patterns/specialized/oracle/oracle on azure iaas/_index.md +++ b/docs/content/patterns/specialized/oracle/oracle on azure iaas/_index.md @@ -25,8 +25,8 @@ Table below shows the Alerts configured after the deployment. | Percentage CPU >= 85 | 85 (1) | Log Analytics | 5 min | Default | | Percentage CPU >= 75 | 75 (2) | Log Analytics | 5 min | Default | | VmAvailabilityMetric < 1 | < 1 (0) | Log Analytics | 5 min | Default | -| OS Disk Bandwidth Consumed Percentage >= 95 | 95 (0) | Log Analytics | 5 min | Default | -| OS Disk Bandwidth Consumed Percentage >= 90 | 90 (1) | Log Analytics | 5 min | Default | +| OS Disk Bandwidth Consumed Percentage > 95 | 95 (0) | Log Analytics | 5 min | Default | +| OS Disk Bandwidth Consumed Percentage > 90 | 90 (1) | Log Analytics | 5 min | Default | | Available Memory Bytes < 500000000 | < 500000000 (1) | Log Analytics | 5 min | Default | | VM cached Bandwidth Consumed Percentage > 95 | 95 (2) | Log Analytics | 5 min | Default | | VM cached Bandwidth Consumed Percentage > 85 | 85 (2) | Log Analytics | 5 min | Default | From 08f26de61b4e21c8ead458c3b4cf144d7967fc09 Mon Sep 17 00:00:00 2001 From: jessiehaessler Date: Tue, 17 Dec 2024 10:32:13 +0100 Subject: [PATCH 3/5] changes incorporated --- .../oracle/oracle on azure iaas/FAQ.md | 41 ++++++++++--------- .../oracle/oracle on azure iaas/_index.md | 8 ++-- 2 files changed, 25 insertions(+), 24 deletions(-) diff --git a/docs/content/patterns/specialized/oracle/oracle on azure iaas/FAQ.md b/docs/content/patterns/specialized/oracle/oracle on azure iaas/FAQ.md index 9cb17e6b5..9fa479012 100644 --- a/docs/content/patterns/specialized/oracle/oracle on azure iaas/FAQ.md +++ b/docs/content/patterns/specialized/oracle/oracle on azure iaas/FAQ.md @@ -6,35 +6,38 @@ weight: 80 > ## Do I need to use the thresholds defined as default values in the metric rule alerts? > -> It's provided as a starting point, we've based the initial thresholds on what we've seen and what Microsoft's documentation recommends. You will need to adjust the thresholds at some point. -> You will need to observe and if the alert is too chatty, adjust the threshold up; if it's not alerting when there's a problem, adjust the threshold down a bit, (or vice-versa depending on what metric or log error is being used as a monitoring source). Once you have decided upon an appropriate value, if you feel it's fit for more general consumption we would love to hear about it. +The initial thresholds are based on our observations and Microsoft's documentation recommendations. These thresholds are intended as a starting point and should be adjusted over time. + +Monitor the alerts closely to fine-tune the thresholds. If the alerts are too frequent, increase the threshold. Conversely, if the alerts do not trigger when issues arise, decrease the threshold accordingly. The adjustments will depend on the metrics or log errors used as monitoring sources. + +Once you have determined an appropriate threshold value, we encourage you to share it with us if you think it could benefit broader use. + > > ## Do I need to use these metrics or can they be replaced with ones more suited to my environment? > -> The metric rules we've created are based on recommendations from Microsoft documentation and field experience. How you're using Azure resources may also be different so tailor the alerts to suit your needs. The main goal of this project is to help you have a way to do Azure Monitor alerts at scale, create new rules with your own thresholds. We'd love to hear about your new rules too so feel free to share back. +> The metric rules provided are based on Microsoft's documentation recommendations and real-world field experience. These rules are intended as a starting point, and you may need to adjust the thresholds over time. + +You can tailor the alerts to suit your specific environment and how you use Azure resources. The main goal of this project is to help you implement Azure Monitor alerts at scale. You can create new rules specific to your thresholds. + +We would love to hear about any new rules you develop, so please share them with us if you believe they could benefit others. > > ## How much does it cost to run the ALZ Baseline solution? > -> This depends on numerous factors including how many of the alert rules you choose to deploy into your environment, this combined with how many subscriptions inherit the baseline policies and resources deployed within each subscription that match the policy rules triggering an alert rule and action group deployment influence the cost. -> -> The solution is comprised of alert rules. Each alert rule costs ~0.1$/month1. -> -> - Alert rules are charged based on evaluations. -> - Assuming the alert rule had data to evaluate all throughout the month, it'll cost ~0.1$1. -> - If the rule was only evaluating during parts of the month (e.g. because the monitored resource was down and didn't send telemetry), the customer would pay for the prorated amount of time the rule was performing evaluations. -> - Dynamic Threshold doubles the cost of the alert rule (~0.2$/month in total1) -> - Our solution configures an email address as part of the Action groups deployment (one per subscription) and these are charged at ~2$/month per 1,000 emails1. -> -> **Whilst it is not anticipated that the solution will incur significant costs, it is recommended that you assess costs as part of a deployment to a non-production environment to make sure you are clear on the costs incurred for your deployment** -> -> For costings related to your deployment please visit [Pricing - Azure Monitor](https://azure.microsoft.com/en-us/pricing/details/monitor/) and work with your local Microsoft account team to define a rough order of magnitude (RoM) costings +> The cost of running the ALZ Baseline solution depends on several factors, including the number of alert rules you deploy, the number of subscriptions inheriting the baseline policies, and the resources within each subscription that match the policy rules. + +Each alert rule costs approximately $0.10 monthly based on continuous data evaluation. If the rule only evaluates data intermittently, the cost is prorated. Dynamic Thresholds double the price to around $0.20 per month. Additionally, Action groups configured with an email address are charged about $2 monthly for every 1,000 emails. + +**While significant costs are not anticipated, it is recommended that you assess costs in a non-production environment to understand the expenses for your deployment.** + +For detailed cost information, visit the Azure Monitor [Pricing - Azure Monitor](https://azure.microsoft.com/en-us/pricing/details/monitor/) pricing and consult with your local Microsoft account team to estimate the costs for your deployment. > -> 1 Depending on the region you deploy to their may be a small difference in the associated cost, the costs provided here are based on prices captured as of April 2023 +Depending on the region you deploy to their may be a small difference in the associated cost, the costs provided here are based on prices captured as of April 2023 > > ## Can I use AMBA without a GitHub repository > ->

Yes, as long as the ARM templates are publicly accessible. There are several linked templates in this solution which require to be publicly accessible. This is because when the top level ARM template is submitted to Azure Resource Manager, the linked templates are not automatically uploaded and therefore need to pulled in at deploy time from Azure. This means they must be referenced using a URL which can be accessed from Azure (e.g. via a public GitHub repository)

->

An alternative is to use Template specs. Instead of maintaining your linked templates at an accessible endpoint, you can create a template spec that packages the main template and its linked templates into a single entity you can deploy. The template spec is a resource in your Azure subscription. It makes it easy to securely share the template with users in your organization. You use Azure role-based access control (Azure RBAC) to grant access to the template spec. This feature is currently in preview.

+You can use AMBA without a GitHub repository if the ARM templates are publicly accessible. The linked templates in this solution must be accessible via a URL when the top-level ARM template is submitted to Azure Resource Manager. This ensures they can be pulled in at deployment time. + +Alternatively, you can use Template specs. This allows you to package the main template and its linked templates into a single entity within your Azure subscription. Template specs make it easy to securely share the template with users in your organization using Azure role-based access control (Azure RBAC). This feature is currently in preview. > > References: > - [Template specs](https://learn.microsoft.com/en-us/azure/azure-resource-manager/templates/linked-templates?tabs=azure-powershell#template-specs) diff --git a/docs/content/patterns/specialized/oracle/oracle on azure iaas/_index.md b/docs/content/patterns/specialized/oracle/oracle on azure iaas/_index.md index 11c193b9d..e4fd4e763 100644 --- a/docs/content/patterns/specialized/oracle/oracle on azure iaas/_index.md +++ b/docs/content/patterns/specialized/oracle/oracle on azure iaas/_index.md @@ -5,12 +5,10 @@ geekdocCollapseSection: true ## Overview -Monitoring Oracle on Azure IaaS allows for timely actions towards performance, reliability and security nd improves these. -This solution helps in setting up the right Azure Monitor alerts for your utilization on the virtual machines and disks. Action owners will receive email notifications if utilization metrics exceeds set threshold. +Monitoring Oracle on Azure IaaS enables timely actions to enhance performance, reliability, and security. This solution helps set up appropriate Azure Monitor alerts for virtual machine and disk utilization. Action owners will receive email notifications if utilization metrics exceed the set thresholds. -{{< hint type=note >}} -Please do not operate Oracle on Azure IaaS solutions outside the thresholds provided below. If you ignore alerts for the threshold values below performance degradation appear. Following if thresholds are exceeded an always available database cannot be guaranteed. -{{< /hint >}} +> [!NOTE] +> Please adhere to the thresholds provided below when operating Oracle on Azure IaaS solutions. Ignoring alerts for these threshold values may lead to performance degradation and compromise the availability of the database **Current Version:** v0 (Dec 6, 2024) From ba9614bfb206a958b646391392906b256fe78591 Mon Sep 17 00:00:00 2001 From: jessiehaessler Date: Wed, 18 Dec 2024 11:30:12 +0100 Subject: [PATCH 4/5] Fixing issues based on feedback --- .../oracle/oracle on azure iaas/_index.md | 48 +++++++++---------- 1 file changed, 24 insertions(+), 24 deletions(-) diff --git a/docs/content/patterns/specialized/oracle/oracle on azure iaas/_index.md b/docs/content/patterns/specialized/oracle/oracle on azure iaas/_index.md index e4fd4e763..ad09027d2 100644 --- a/docs/content/patterns/specialized/oracle/oracle on azure iaas/_index.md +++ b/docs/content/patterns/specialized/oracle/oracle on azure iaas/_index.md @@ -17,30 +17,30 @@ v0 (Dec 6, 2024) Table below shows the Alerts configured after the deployment. -| Name | Threshold(s) (Severity) | Signal Type | Frequency | \# Alert Rules | -| ---------------------------------------------------------- | ------------------------------------------ | ----------------------- | --------- | -------------- | -| Percentage CPU > 95 | 95 (2) | Log Analytics | 5 min | Default | -| Percentage CPU >= 85 | 85 (1) | Log Analytics | 5 min | Default | -| Percentage CPU >= 75 | 75 (2) | Log Analytics | 5 min | Default | -| VmAvailabilityMetric < 1 | < 1 (0) | Log Analytics | 5 min | Default | -| OS Disk Bandwidth Consumed Percentage > 95 | 95 (0) | Log Analytics | 5 min | Default | -| OS Disk Bandwidth Consumed Percentage > 90 | 90 (1) | Log Analytics | 5 min | Default | -| Available Memory Bytes < 500000000 | < 500000000 (1) | Log Analytics | 5 min | Default | -| VM cached Bandwidth Consumed Percentage > 95 | 95 (2) | Log Analytics | 5 min | Default | -| VM cached Bandwidth Consumed Percentage > 85 | 85 (2) | Log Analytics | 5 min | Default | -| VM cached Bandwidth Consumed Percentage > 75 | 75 (2) | Log Analytics | 5 min | Default | -| VM uncached Bandwidth Consumed Percentage > 95 | 95 (2) | Log Analytics | 5 min | Default | -| VM uncached Bandwidth Consumed Percentage > 85 | 85 (2) | Log Analytics | 5 min | Default | -| VM uncached Bandwidth Consumed Percentage > 75 | 75 (2) | Log Analytics | 5 min | Default | -| Data Disk IOPS Consumed Percentage > 95 | 95 (2) | Log Analytics | 5 min | Default -| Data Disk IOPS Consumed Percentage > 85 | 85 (2) | Log Analytics | 5 min | Default | -| Data Disk IOPS Consumed Percentage > 75 | 75 (2) | Log Analytics | 5 min | Default | -| OS Disk Bandwidth Consumed Percentage > 95 | 95 (2) | Log Analytics | 5 min | Default | -| OS Disk Bandwidth Consumed Percentage > 85 | 85 (2) | Log Analytics | 5 min | Default | -| OS Disk Bandwidth Consumed Percentage > 75 | 75 (2) | Log Analytics | 5 min | Default | -| VolumeConsumedSizePercentage per Lun >= 95 | \>=95 (0) | Log Analytics | 5 min | Default | -| VolumeConsumedSizePercentage >= 90 | \>=90 (2) | Log Analytics | 5 min | Default | -| UnhealthyHostCount >=1 | \>=1 (0) | Log Analytics | 5 min | Default | +| Name | Threshold(s) (Severity) | Signal Type | Frequency | \# Alert Rules | +| ---------------------------------------------- | ----------------------- | ------------- | --------- | -------------- | +| Percentage CPU > 95 | 95 (2) | Log Analytics | 5 min | Default | +| Percentage CPU >= 85 | 85 (1) | Log Analytics | 5 min | Default | +| Percentage CPU >= 75 | 75 (2) | Log Analytics | 5 min | Default | +| VmAvailabilityMetric < 1 | < 1 (0) | Log Analytics | 5 min | Default | +| OS Disk Bandwidth Consumed Percentage > 95 | 95 (0) | Log Analytics | 5 min | Default | +| OS Disk Bandwidth Consumed Percentage > 90 | 90 (1) | Log Analytics | 5 min | Default | +| Available Memory Bytes < 500000000 | < 500000000 (1) | Log Analytics | 5 min | Default | +| VM cached Bandwidth Consumed Percentage > 95 | 95 (2) | Log Analytics | 5 min | Default | +| VM cached Bandwidth Consumed Percentage > 85 | 85 (2) | Log Analytics | 5 min | Default | +| VM cached Bandwidth Consumed Percentage > 75 | 75 (2) | Log Analytics | 5 min | Default | +| VM uncached Bandwidth Consumed Percentage > 95 | 95 (2) | Log Analytics | 5 min | Default | +| VM uncached Bandwidth Consumed Percentage > 85 | 85 (2) | Log Analytics | 5 min | Default | +| VM uncached Bandwidth Consumed Percentage > 75 | 75 (2) | Log Analytics | 5 min | Default | +| Data Disk IOPS Consumed Percentage > 95 | 95 (2) | Log Analytics | 5 min | Default | +| Data Disk IOPS Consumed Percentage > 85 | 85 (2) | Log Analytics | 5 min | Default | +| Data Disk IOPS Consumed Percentage > 75 | 75 (2) | Log Analytics | 5 min | Default | +| OS Disk Bandwidth Consumed Percentage > 95 | 95 (2) | Log Analytics | 5 min | Default | +| OS Disk Bandwidth Consumed Percentage > 85 | 85 (2) | Log Analytics | 5 min | Default | +| OS Disk Bandwidth Consumed Percentage > 75 | 75 (2) | Log Analytics | 5 min | Default | +| VolumeConsumedSizePercentage per Lun >= 95 | \>=95 (0) | Log Analytics | 5 min | Default | +| VolumeConsumedSizePercentage >= 90 | \>=90 (2) | Log Analytics | 5 min | Default | +| UnhealthyHostCount >=1 | \>=1 (0) | Log Analytics | 5 min | Default | ## 📣Feedback 📣 From 4300a49352795f87f2c1e6079cc1c8e94b47005b Mon Sep 17 00:00:00 2001 From: jessiehaessler Date: Wed, 18 Dec 2024 11:38:57 +0100 Subject: [PATCH 5/5] working on linting issues --- .../patterns/specialized/oracle/oracle on azure iaas/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/patterns/specialized/oracle/oracle on azure iaas/_index.md b/docs/content/patterns/specialized/oracle/oracle on azure iaas/_index.md index ad09027d2..20786d05c 100644 --- a/docs/content/patterns/specialized/oracle/oracle on azure iaas/_index.md +++ b/docs/content/patterns/specialized/oracle/oracle on azure iaas/_index.md @@ -79,4 +79,4 @@ 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](https://www.microsoft.com/legal/intellectualproperty/trademarks/usage/general). 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. \ No newline at end of file +Any use of third-party trademarks or logos are subject to those third-party's policies.