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

added baseline alerts for oracle on azure iaas #449

Merged
merged 5 commits into from
Dec 18, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
jessiehaessler marked this conversation as resolved.
Show resolved Hide resolved
Original file line number Diff line number Diff line change
@@ -0,0 +1,44 @@
---
title: Frequently Asked Questions
geekdocCollapseSection: true
weight: 80
---

> ## Do I need to use the thresholds defined as default values in the metric rule alerts?
>
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 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?
>
> 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.
>
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
>
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)
> - [ARM Private deployment](https://github.com/Azure/ARM-private-deployment)
jessiehaessler marked this conversation as resolved.
Show resolved Hide resolved
Original file line number Diff line number Diff line change
@@ -0,0 +1,82 @@
---
title: Oracle on Azure IaaS
geekdocCollapseSection: true
---

## Overview

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.

> [!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)

## 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 [[email protected]](mailto:[email protected]) 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.
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
---
title: Known Issues
geekdocCollapseSection: true
weight: 100
---

## None at this time
Loading