Skip to content

Commit 59c74e4

Browse files
committed
Updating alt text
1 parent f4e26f1 commit 59c74e4

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/cosmos-db/merge.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -48,15 +48,15 @@ For containers using autoscale, this will show the max RU/s currently provisione
4848

4949
In the below example, we have an autoscale container provisioned with 5000 RU/s (scales between 500 - 5000 RU/s). It has 5 physical partitions and each physical partition has 1000 RU/s.
5050

51-
:::image type="content" source="media/merge/RU-per-physical-partition-metric.png" alt-text="Azure Monitor metric Physical Partition Throughput":::
51+
:::image type="content" source="media/merge/RU-per-physical-partition-metric.png" alt-text="Screenshot of Azure Monitor metric Physical Partition Throughput in Azure portal.":::
5252

5353
#### Criteria 2
5454

5555
To determine the current average storage per physical partition, first find the overall storage (data + index) of the container.
5656

5757
Navigate to **Insights** > **Storage** > **Data & Index Usage**. The total storage is the sum of the data and index usage. In the below example, the container has a total of 74 GB of storage.
5858

59-
:::image type="content" source="media/merge/storage-per-container.png" alt-text="Azure Monitor storage (data + index) metric for container":::
59+
:::image type="content" source="media/merge/storage-per-container.png" alt-text="Screenshot of Azure Monitor storage (data + index) metric for container in Azure portal.":::
6060

6161
Next, find the total number of physical partitions. This is the distinct number of **PhysicalPartitionIds** in the **PhysicalPartitionThroughput** chart we saw in Criteria 1. In our example, we have 5 physical partitions.
6262

0 commit comments

Comments
 (0)