Merge pull request #257050 from v-jbasden/v-jbasden-convert-images-to-learn-format-autoscale-1

[BULK UPDATE #1] Converting Azure Monitor legacy image formatting to Learn formatting - autoscale subservice

Author: prmerger-automator[bot]

articles/azure-monitor/autoscale/autoscale-overview.md

@@ -27,7 +27,7 @@ When your application experiences higher load, autoscale adds resources to handl
 
 For example, scale out your application by adding VMs when the average CPU usage per VM is above 70%. Scale it back by removing VMs when CPU usage drops to 40%.
 
-:::image type="content" source="./media/autoscale-overview/AutoscaleConcept.png" alt-text="A diagram that shows scaling out by adding virtual machine instances.":::
+:::image type="content" source="./media/autoscale-overview/AutoscaleConcept.png" lightbox="./media/autoscale-overview/AutoscaleConcept.png" alt-text="A diagram that shows scaling out by adding virtual machine instances.":::
 
 When the conditions in the rules are met, one or more autoscale actions are triggered, adding or removing VMs. You can also perform other actions like sending email, notifications, or webhooks to trigger processes in other systems.
 
@@ -37,7 +37,7 @@ Autoscale scales in and out, or horizontally. Scaling horizontally is an increas
 
 In contrast, scaling up and down, or vertical scaling, keeps the same number of resource instances constant but gives them more capacity in terms of memory, CPU speed, disk space, and network. Vertical scaling is limited by the availability of larger hardware, which eventually reaches an upper limit. Hardware size availability varies in Azure by region. Vertical scaling might also require a restart of the VM during the scaling process. Autoscale does not support vertical scaling.
 
-:::image type="content" source="./media/autoscale-overview/vertical-scaling.png" alt-text="A diagram that shows scaling up by adding CPU and memory to a virtual machine.":::
+:::image type="content" source="./media/autoscale-overview/vertical-scaling.png" lightbox="./media/autoscale-overview/vertical-scaling.png" alt-text="A diagram that shows scaling up by adding CPU and memory to a virtual machine.":::
 
 When the conditions in the rules are met, one or more autoscale actions are triggered, adding or removing VMs. You can also perform other actions like sending email, notifications, or webhooks to trigger processes in other systems.
 
@@ -58,7 +58,7 @@ You can set up autoscale via:
 
 The following diagram shows the autoscale architecture.
 
- ![Diagram that shows autoscale flow.](./media/autoscale-overview/Autoscale_Overview_v4.png)
+ :::image type="content" source="./media/autoscale-overview/Autoscale_Overview_v4.png" lightbox="./media/autoscale-overview/Autoscale_Overview_v4.png" alt-text="Diagram that shows autoscale flow.":::
 
 ### Resource metrics
 
@@ -109,7 +109,7 @@ Autoscale uses the following terminology and structure.
 | Schedule         | recurrence   | Indicates when autoscale should put this scale condition or profile into effect. You can have multiple scale conditions, which allow you to handle different and overlapping requirements. For example, you can have different scale conditions for different times of day or days of the week. |
 | Notify           | notification | Defines the notifications to send when an autoscale event occurs. Autoscale can notify one or more email addresses or make a call by using one or more webhooks. You can configure multiple webhooks in the JSON but only one in the UI.                               |
 
-![Diagram that shows Azure autoscale setting, profile, and rule structure.](./media/autoscale-overview/azure-resource-manager-rule-structure-3.png)
+:::image type="content" source="./media/autoscale-overview/azure-resource-manager-rule-structure-3.png" lightbox="./media/autoscale-overview/azure-resource-manager-rule-structure-3.png" alt-text="Diagram that shows Azure autoscale setting, profile, and rule structure.":::
 
 The full list of configurable fields and descriptions is available in the [Autoscale REST API](/rest/api/monitor/autoscalesettings).
 

articles/azure-monitor/autoscale/autoscale-troubleshoot.md

@@ -46,16 +46,16 @@ An autoscale setting for a virtual machine scale set:
 Let's review the metrics from the autoscale service.
 
 The following chart shows a **Percentage CPU** metric for a virtual machine scale set.
-
-![Screenshot that shows a virtual machine scale set percentage CPU example.](media/autoscale-troubleshoot/autoscale-vmss-CPU-ex-full-1.png)
+<!-- convertborder later -->
+:::image type="content" source="media/autoscale-troubleshoot/autoscale-vmss-CPU-ex-full-1.png" lightbox="media/autoscale-troubleshoot/autoscale-vmss-CPU-ex-full-1.png" alt-text="Screenshot that shows a virtual machine scale set percentage CPU example." border="false":::
 
 The next chart shows the **Observed Metric Value** metric for an autoscale setting.
-
-![Screenshot that shows another virtual machine scale set percentage CPU example.](media/autoscale-troubleshoot/autoscale-vmss-CPU-ex-full-2.png)
+<!-- convertborder later -->
+:::image type="content" source="media/autoscale-troubleshoot/autoscale-vmss-CPU-ex-full-2.png" lightbox="media/autoscale-troubleshoot/autoscale-vmss-CPU-ex-full-2.png" alt-text="Screenshot that shows another virtual machine scale set percentage CPU example." border="false":::
 
 The final chart shows the **Metric Threshold** and **Observed Capacity** metrics. The **Metric Threshold** metric at the top for the scale-out rule is 70. The **Observed Capacity** metric at the bottom shows the number of active instances, which is currently 3.
-
-![Screenshot that shows Metric Threshold and Observed Capacity.](media/autoscale-troubleshoot/autoscale-metric-threshold-capacity-ex-full.png)
+<!-- convertborder later -->
+:::image type="content" source="media/autoscale-troubleshoot/autoscale-metric-threshold-capacity-ex-full.png" lightbox="media/autoscale-troubleshoot/autoscale-metric-threshold-capacity-ex-full.png" alt-text="Screenshot that shows Metric Threshold and Observed Capacity." border="false":::
 
 > [!NOTE]
 > You can filter **Metric Threshold** by the metric trigger rule dimension scale-out (increase) rule to see the scale-out threshold and by the scale-in rule (decrease).
@@ -71,24 +71,24 @@ In this case, the autoscale engine's observed metric value is calculated as the
 The following screenshots show two metric charts.
 
 The **Avg Outbound Flows** chart shows the value of the **Outbound Flows** metric. The actual value is 6.
-
-![Screenshot that shows the Average Outbound Flows page with an example of a virtual machine scale set autoscale metrics chart.](media/autoscale-troubleshoot/autoscale-vmss-metric-chart-ex-1.png)
+<!-- convertborder later -->
+:::image type="content" source="media/autoscale-troubleshoot/autoscale-vmss-metric-chart-ex-1.png" lightbox="media/autoscale-troubleshoot/autoscale-vmss-metric-chart-ex-1.png" alt-text="Screenshot that shows the Average Outbound Flows page with an example of a virtual machine scale set autoscale metrics chart." border="false":::
 
 The following chart shows a few values:
 
  - The **Observed Metric Value** metric in the middle is 3 because there are 2 active instances, and 6 divided by 2 is 3.
  - The **Observed Capacity** metric at the bottom shows the instance count seen by an autoscale engine.
  - The **Metric Threshold** metric at the top is set to 10.
-
-   ![Screenshot that shows a virtual machine scale set autoscale metrics charts example.](media/autoscale-troubleshoot/autoscale-vmss-metric-chart-ex-2.png)
+   <!-- convertborder later -->
+   :::image type="content" source="media/autoscale-troubleshoot/autoscale-vmss-metric-chart-ex-2.png" lightbox="media/autoscale-troubleshoot/autoscale-vmss-metric-chart-ex-2.png" alt-text="Screenshot that shows a virtual machine scale set autoscale metrics charts example." border="false":::
 
 If there are multiple scale action rules, you can use splitting or the **add filter** option in the metrics explorer chart to look at a metric by a specific source or rule. For more information on splitting a metric chart, see [Advanced features of metric charts - splitting](../essentials/metrics-charts.md#apply-splitting).
 
 ## Example 3: Understand autoscale events
 
 In the autoscale setting screen, go to the **Run history** tab to see the most recent scale actions. The tab also shows the change in **Observed Capacity** over time. To find more information about all autoscale actions, including operations such as update/delete autoscale settings, view the activity log and filter by autoscale operations.
-
-![Screenshot that shows autoscale settings run history.](media/autoscale-troubleshoot/autoscale-setting-run-history-smaller.png)
+<!-- convertborder later -->
+:::image type="content" source="media/autoscale-troubleshoot/autoscale-setting-run-history-smaller.png" lightbox="media/autoscale-troubleshoot/autoscale-setting-run-history-smaller.png" alt-text="Screenshot that shows autoscale settings run history." border="false":::
 
 ## Autoscale resource logs
 
@@ -102,8 +102,8 @@ As with any Azure Monitor supported service, you can use [diagnostic settings](.
 - Your Log Analytics workspace for detailed analytics.
 - Azure Event Hubs and then to non-Azure tools.
 - Your Azure Storage account for archive.
-
-![Screenshot that shows autoscale diagnostic settings.](media/autoscale-troubleshoot/diagnostic-settings.png)
+<!-- convertborder later -->
+:::image type="content" source="media/autoscale-troubleshoot/diagnostic-settings.png" lightbox="media/autoscale-troubleshoot/diagnostic-settings.png" alt-text="Screenshot that shows autoscale diagnostic settings." border="false":::
 
 The preceding screenshot shows the Azure portal autoscale **Diagnostics settings** pane. There you can select the **Diagnostic/Resource Logs** tab and enable log collection and routing. You can also perform the same action by using the REST API, the Azure CLI, PowerShell, and Azure Resource Manager templates for diagnostic settings by choosing the resource type as **Microsoft.Insights/AutoscaleSettings**.