Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into mon

Author: gitName

.openpublishing.publish.config.json

@@ -236,12 +236,6 @@
             "branch": "main",
             "branch_mapping": {}
         },
-        {
-            "path_to_root": "azure-iot-operations-samples-m3",
-            "url": "https://github.com/Azure-Samples/explore-iot-operations",
-            "branch": "release-m3",
-            "branch_mapping": {}
-        },
         {
             "path_to_root": "azure-iot-sdk-node",
             "url": "https://github.com/Azure/azure-iot-sdk-node",

.openpublishing.redirection.json

@@ -3599,6 +3599,16 @@
       "source_path_from_root": "/articles/third-party-notices.md",
       "redirect_url": "https://github.com/MicrosoftDocs/azure-docs/blob/main/ThirdPartyNotices.md",
       "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/reliability/glossary.md",
+      "redirect_url": "/azure/reliability/overview",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/reliability/resiliency-recommendations/recommend-cosmos-db-nosql.md",
+      "redirect_url": "/azure/reliability/reliability-cosmos-db-nosql",
+      "redirect_document_id": false
     }
   ]
 }

articles/avere-vfxt/avere-vfxt-add-storage.md

@@ -46,8 +46,6 @@ Follow these steps to add a NAS core filer:
 
 1. Click **Create**.
 
-   ![Screenshot of the Add new core filer page with a cursor over the Create button](media/avere-vfxt-add-core-filer-start.png)
-
 1. Fill in the required information in the wizard:
 
    * Name your core filer.

articles/avere-vfxt/avere-vfxt-cluster-gui.md

@@ -56,8 +56,6 @@ Depending on your browser, you might need to click **Advanced** and verify that
 
 Enter the username `admin` and the administrative password you provided when creating the cluster.
 
-![Screenshot of the Avere sign in page populated with the username 'admin' and a password](media/avere-vfxt-gui-login.png)
-
 Click **Login** or press enter on your keyboard.
 
 ## Next steps

articles/avere-vfxt/avere-vfxt-enable-support.md

@@ -18,9 +18,6 @@ Follow these steps from the Avere Control Panel to activate support. (Read [Acce
 
 1. Navigate to the **Settings** tab at the top.
 1. Click the **Support** link on the left and accept the privacy policy.
-
-   ![Screenshot showing Avere Control Panel and pop-up window with Confirm button to accept the privacy policy](media/avere-vfxt-privacy-policy.png)
-
 1. On the support configuration page, open the **Customer Info** section by clicking the triangle at the left.
 1. Click the **Revalidate upload information** button.
 1. Set the cluster's support name in **Unique Cluster Name**. Make sure this name uniquely identifies your cluster to support staff.

articles/avere-vfxt/media/avere-vfxt-add-core-filer-start.png

@@ -230,7 +230,6 @@ Some resources have a limit on the number instances per region. This limit is di
 ## Microsoft.Web
 
 * apiManagementAccounts/apis
-* certificates
 * sites
 
 ## Next steps

articles/avere-vfxt/media/avere-vfxt-gui-login.png

@@ -0,0 +1,52 @@
+---
+title: Configure the latest iteration of Azure VMware Solution private cloud performance and health metrics
+description: Learn how to take advantage of the latest improvements made to Azure VMware Solution private cloud performance and health metrics 
+ms.topic: how-to 
+ms.service: azure-vmware
+ms.date: 10/09/2024
+ms.custom: engagement-fy24
+
+#Customer intent: As an Azure service administrator, I want to collect key performance and reliability metrics from my Azure VMware Solution private cloud, so I can analyze for any diagnostic purposes.
+
+---
+
+# Configure the latest iteration of Azure VMware Solution private cloud performance and health metrics
+
+In this article, you learn how to take advantage of the latest iteration of metrics available to monitor your Azure VMware Solution private cloud. 
+
+Azure VMware Solution provides users with an array of high-level health and performance metrics to provide visibility into the health and performance of an Azure VMware Solution private cloud. Since early 2024, another set of identical metrics labeled with the word "(new)" were introduced, where a series of enhancements to the stability, reliability, and performance of these metrics were made to provide users a better experience relative to the older set of metrics.  
+  
+
+### View Azure VMware Solution metrics
+From your Azure VMware Solution private cloud, select **Metrics** under the **Monitoring** section. Then under the **Metric** dropdown, choose a metric that contains the word "(new)". These newer metrics are powered by our improved metrics engine, providing utmost reliability and stability. The metrics monitor items like memory consumption, datastore usage, and CPU across your Azure VMware Solution private cloud.
+
+:::image type="content" source="media/new-metrics/azure-vmware-solution-metrics-new-1.png" alt-text="Screenshot showing where to get the new metrics.":::
+
+### Setting up a chart
+
+Select a metric you'd like to build a chart for, such as "Percentage CPU (new)" in this example. Upon doing so, you will see a chart like the one below showing a time series for the metric you've selected.
+
+:::image type="content" source="media/new-metrics/azure-vmware-solution-metrics-new-2.png" alt-text="Screenshot showing an example metric.":::
+
+You can toggle the time window you are interested in this metric for by simply selecting the time window button in the top-right corner. The default window for your selected metric will be **24 hours**.
+
+Once you are ready to save, click **Save to Dashboard** and select one of the options presented for where this metric will live.
+
+### Send metrics to other monitoring solutions using the new metrics
+
+Additionally, you can hover over each metric in the **Metric** dropdown to see the Metric ID. You can use this Metric ID in your third-party monitoring tools to monitor your Azure VMware Solution private cloud.
+ >[!IMPORTANT]
+   >We strongly encourage all users - first time and repeat - to migrate to the new metrics suffixed with **"(new)"**.
+
+For those who have used the metrics previously and have built monitoring in downstream tools and configurations that rely on the old metric IDs, the following table provides the corresponding newer metric IDs you can use for the same set of metrics to seamlessly transition to using the newer set of metrics:
+
+| Metric Name (as viewed in the portal) | Current Metric ID | New Metric ID | 
+| :---     | :---      | :---     |
+| Datastore Disk Used   | UsedLatest  | DiskUsedLatest |
+| Datastore Disk Total Capacity   | CapacityLatest   | CapacityLatest |
+| Average Effective Memory   | EffectiveMemAverage   | ClusterSummaryEffectiveMemory  |
+| Average Total Memory   | TotalMbAverage    | ClusterSummaryTotalMemCapacityMB  |
+| Average Memory Overhead    | OverheadAverage   | MemOverheadAverage  |
+| Average Memory Usage   | UsageAverage    | MemUsageAverage  |
+| Percentage CPU   | EffectiveCpuAverage  | CpuUsageAverage   |
+| Percentage Datastore Disk Used    | DiskUsedPercentage   | DiskUsedPercentage   |