Merge pull request #302687 from denisacatalinastan/patch-26

Update elastic-san-metrics.md

Author: AnnaMHuff

articles/storage/elastic-san/elastic-san-metrics.md

@@ -4,7 +4,7 @@ description: Learn about the available metrics that can let you understand how y
 author: roygara
 ms.service: azure-elastic-san-storage
 ms.topic: concept-article
-ms.date: 06/28/2024
+ms.date: 07/14/2025
 ms.author: rogarana
 # Customer intent: As a cloud storage administrator, I want to monitor the performance metrics of my Azure Elastic SAN, so that I can optimize its availability and manage resource usage effectively.
 ---
@@ -44,6 +44,54 @@ Available log categories:
 - Persistent Reservation Requests
 - SendTargets Requests
 
+## Monitor workload performance
+ 
+### Monitor Availability 
+The **Availability** metric can be useful to view any visible issues from either an application or user perspective.
+ 
+When using this metric with Azure Elastic SAN, we recommend using the **Average** aggregation - using Average shows you what percentage of your requests are experiencing errors, and if they are within [Elastic SAN's SLA](https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services?lang=1).
+You can use the **Min** and **Max** aggregation for worst and best case availability scenarios. For instance - **Min** availability can be used for incident alerting.
+ 
+### How to create an alert for Availability < 99.9%
+ 
+1. Open the **Create an alert rule** dialog box. For more information, see [Create or edit an alert rule](/azure/azure-monitor/alerts/alerts-create-new-alert-rule).
+ 
+1. In the **Scope** tab, select your Elastic SAN resource.
+ 
+1. In the **Condition** tab, select the **Availability** metric.
+ 
+1. In the **Alert logic** tab, select the following attribute variable values from the drop down menu: 
+   
+   | Field             | Description  |
+   |------------------|--------------|
+   | Threshold         | Static       |
+   | Aggregation type  | Average      |
+   | Operator          | Less than    |
+   | Threshold value   | 99.9         |
+
+ 
+1. In the **When to evaluate** tab, select the following variable values from the drop down menu:
+   
+   | Field             | Description  |
+   |------------------|--------------|
+   | Check every      | 5 minutes    |
+   | Lookback period  | 1 hour       |
+ 
+1. Click **Next** to go to the **Actions** tab and add an action group (email, SMS, etc.) to the alert. You can select an existing action group or create a new action group.
+ 
+1. Click **Next** to go to the **Details** tab and fill in the details of the alert such as the alert name, description, and severity.
+ 
+1. Select **Review + create** to create the alert.
+ 
+ 
+### Monitor Utilization
+ 
+Utilization metrics that measure the amount of data being transmitted (throughput) or operations being serviced (IOPS) are commonly used to determine how much work is being performed by the application or workload. Transaction metrics can determine the number of operations or requests against the Azure Elastic SAN service over various time granularity.
+ 
+To determine the average I/O per second (IOPS) for your workload, first determine the total number of transactions using the **Transactions** metric over a minute and then divide that number by 60 seconds. For example, 120,000 transactions in 1 minute / 60 seconds = 2,000 average IOPS.
+ 
+To determine the average throughput for your workload, take the total amount of transmitted data by combining the **Ingress** and **Egress** metrics (total throughput) and divide that by 60 seconds. For example, 1 GiB total throughput over 1 minute / 60 seconds = 17 MiB average throughput.
+
 ## Next steps
 
 - [Azure Monitor Metrics overview](/azure/azure-monitor/essentials/data-platform-metrics)