Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Azure offers metrics in the Azure portal that provide insight into your Elastic SAN resources. This article provides definitions of the specific metrics you can select to monitor.
Metrics definitions
The following metrics are currently available for your Elastic SAN resource. You can configure and view them in the Azure portal:
| Metric | Definition |
|---|---|
| Availability | The percentage of availability for the storage service or the specified API operation. |
| Transactions | The number of requests made to a storage service or the specified API operation. This number includes successful and failed requests, as well as requests that produced errors. |
| E2E Latency | The average end-to-end latency of successful requests made to the resource or the specified API operation. |
| Server Latency | The average time used to process a successful request. This value doesn't include the network latency specified in E2E Latency. |
| Ingress | The amount of ingress data. This number includes ingress to the resource from external clients as well as ingress within Azure. |
| Egress | The amount of egress data. This number includes egress from the resource to external clients as well as egress within Azure. |
By default, all metrics are shown at the SAN level. To view these metrics at either the volume group or volume level, select a filter on your selected metric to view your data on a specific volume group or volume.
Resource logging
You can configure the diagnostic settings of your elastic SAN to send Azure platform logs and metrics to different destinations. Currently, there's one log configuration:
- Transactions - Every transaction log offered by the resource.
Audit logs are an attempt by each resource provider to provide the most relevant audit data, but might not be considered sufficient from an auditing standards perspective.
Available log categories:
- Write Success Requests
- Write Failed Requests
- Read Success Requests
- Read Failed Requests
- 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. 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%
Open the Create an alert rule dialog box. For more information, see Create or edit an alert rule.
In the Scope tab, select your Elastic SAN resource.
In the Condition tab, select the Availability metric.
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 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 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.
Click Next to go to the Details tab and fill in the details of the alert such as the alert name, description, and severity.
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.