Skip to content

Commit 0d7b99d

Browse files
authored
Update autoscale-common-metrics.md
removed duplicated metadata section
1 parent 4561c3e commit 0d7b99d

File tree

1 file changed

+1
-12
lines changed

1 file changed

+1
-12
lines changed

articles/azure-monitor/autoscale/autoscale-common-metrics.md

Lines changed: 1 addition & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -9,17 +9,6 @@ ms.subservice: autoscale
99
ms.reviewer: akkumari
1010
---
1111

12-
---
13-
title: Autoscale common metrics
14-
description: Learn which metrics are commonly used for autoscaling your cloud services, virtual machines, and web apps.
15-
author: EdB-MSFT
16-
ms.author: edbaynash
17-
ms.topic: conceptual
18-
ms.date: 04/17/2023
19-
ms.subservice: autoscale
20-
ms.reviewer: akkumari
21-
---
22-
2312
# Azure Monitor autoscaling common metrics
2413

2514
Azure Monitor autoscaling allows you to scale the number of running instances in or out, based on telemetry data or metrics. Scaling can be based on any metric, even metrics from a different resource. For example, scale a Virtual Machine Scale Set based on the amount of traffic on a firewall.
@@ -190,4 +179,4 @@ For Virtual Machine Scale Sets, you can update the autoscale setting in the Reso
190179
```
191180

192181
> [!NOTE]
193-
> For Service Bus, the resource group concept doesn't exist. Azure Resource Manager creates a default resource group per region. The resource group is usually in the Default-ServiceBus-[region] format. Examples are Default-ServiceBus-EastUS, Default-ServiceBus-WestUS, and Default-ServiceBus-AustraliaEast.
182+
> For Service Bus, the resource group concept doesn't exist. Azure Resource Manager creates a default resource group per region. The resource group is usually in the Default-ServiceBus-[region] format. Examples are Default-ServiceBus-EastUS, Default-ServiceBus-WestUS, and Default-ServiceBus-AustraliaEast.

0 commit comments

Comments
 (0)