Merge pull request #247748 from bwren/freshness

Freshness

Author: v-dirichards

.openpublishing.redirection.azure-monitor.json

@@ -6280,6 +6280,36 @@
             "redirect_url": "/azure/azure-monitor/containers/prometheus-authorization-proxy",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/articles/azure-monitor/azure-cli-metrics-alert-sample.md",
+            "redirect_url": "/azure/azure-monitor/alerts/azure-cli-metrics-alert-sample",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-monitor/terminology.md",
+            "redirect_url": "/azure/azure-monitor/overview",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-monitor/logs/create-pipeline-datacollector-api.md",
+            "redirect_url": "/azure/azure-monitor/logs/data-collector-api",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-monitor/visualize/vmext-troubleshoot.md",
+            "redirect_url": "/azure/azure-monitor/agents/vmext-troubleshoot",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-monitor/logs/unify-app-resource-data.md",
+            "redirect_url": "/azure/azure-monitor/logs/cross-workspace-query",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-monitor/insights/solution-agenthealth.md",
+            "redirect_url": "/azure/azure-monitor/agents/solution-agenthealth",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/azure-monitor/containers/container-insights-hybrid-setup.md",
             "redirect_url": "/azure/azure-monitor/containers/container-insights-enable-arc-enabled-clusters",

articles/azure-monitor/insights/media/solution-agenthealth/agenthealth-solution-dashboard.png renamed to articles/azure-monitor/agents/media/solution-agenthealth/agenthealth-solution-dashboard.png

@@ -2,9 +2,7 @@
 title: Agent Health solution in Azure Monitor | Microsoft Docs
 description: Learn how to use this solution to monitor the health of your agents reporting directly to Log Analytics or System Center Operations Manager.
 ms.topic: conceptual
-author: bwren
-ms.author: bwren
-ms.date: 02/06/2020
+ms.date: 08/09/2023
 ms.reviewer: shijain
 
 ---
@@ -17,8 +15,11 @@ You can also use the Agent Health solution to:
 * Keep track of how many agents are deployed and where they're distributed geographically.
 * Perform other queries to maintain awareness of the distribution of agents deployed in Azure, in other cloud environments, or on-premises.
 
+> [!IMPORTANT]
+> The Agent Health solution only monitors the health of the [Log Analytics agent](log-analytics-agent.md) which is on a deprecation path. This solution doesn't monitor the health of the [Azure Monitor agent](agents-overview.md).
+
 ## Prerequisites
-Before you deploy this solution, confirm that you have supported [Windows agents](../agents/agent-windows.md) reporting to the Log Analytics workspace or reporting to an [Operations Manager management group](../agents/om-agents.md) integrated with your workspace.
+Before you deploy this solution, confirm that you have supported [Windows agents](../agents/agent-windows.md) reporting to the Log Analytics workspace or reporting to an [Operations Manager management group](agents-overview.md) integrated with your workspace.
 
 ## Management packs
 If your Operations Manager management group is connected to a Log Analytics workspace, the following management packs are installed in Operations Manager. These management packs are also installed on directly connected Windows computers after you add this solution:
@@ -29,7 +30,7 @@ If your Operations Manager management group is connected to a Log Analytics work
 There's nothing to configure or manage with these management packs. For more information on how solution management packs are updated, see [Connect Operations Manager to Log Analytics](../agents/om-agents.md).
 
 ## Configuration
-Add the Agent Health solution to your Log Analytics workspace by using the process described in [Add solutions](solutions.md). No further configuration is required.
+Add the Agent Health solution to your Log Analytics workspace by using the process described in [Add solutions](../insights/solutions.md). No further configuration is required.
 
 ## Supported agents
 The following table describes the connected sources that this solution supports.
@@ -42,7 +43,7 @@ The following table describes the connected sources that this solution supports.
 ## Use the solution
 When you add the solution to your Log Analytics workspace, the **Agent Health** tile is added to your dashboard. This tile shows the total number of agents and the number of unresponsive agents in the last 24 hours.
 
-![Screenshot that shows the Agent Health tile on the dashboard.](./media/solution-agenthealth/agenthealth-solution-tile-homepage.png)
+:::image type="content" source="media/solution-agenthealth/agenthealth-solution-tile-homepage.png" alt-text="Screenshot that shows the Agent Health tile on the dashboard." lightbox="media/solution-agenthealth/agenthealth-solution-tile-homepage.png":::
 
 Select the **Agent Health** tile to open the **Agent Health** dashboard. The dashboard includes the columns in the following table. Each column lists the top 10 events by count that match that column's criteria for the specified time range. You can run a log search that provides the entire list. Select **See all** beneath each column or select the column heading.
 
@@ -57,7 +58,7 @@ Select the **Agent Health** tile to open the **Agent Health** dashboard. The das
 | Geo-location of agents | A partition of the countries/regions where you have agents, and a total count of the number of agents that have been installed in each country/region|
 | Count of gateways installed | The number of servers that have the Log Analytics gateway installed, and a list of these servers|
 
-![Screenshot that shows an example of the Agent Health solution dashboard.](./media/solution-agenthealth/agenthealth-solution-dashboard.png)
+:::image type="content" source="media/solution-agenthealth/agenthealth-solution-dashboard.png" alt-text="Screenshot that shows an example of the Agent Health solution dashboard." lightbox="media/solution-agenthealth/agenthealth-solution-dashboard.png":::
 
 ## Azure Monitor log records
 The solution creates one type of record in the Log Analytics workspace: heartbeat. Heartbeat records have the properties listed in the following table.

articles/azure-monitor/insights/media/solution-agenthealth/agenthealth-solution-tile-homepage.png renamed to articles/azure-monitor/agents/media/solution-agenthealth/agenthealth-solution-tile-homepage.png

@@ -2,8 +2,6 @@
 title: Troubleshoot the Azure Log Analytics VM extension
 description: Describe the symptoms, causes, and resolution for the most common issues with the Log Analytics VM extension for Windows and Linux Azure VMs.
 ms.topic: conceptual
-author: bwren
-ms.author: bwren
 ms.date: 06/06/2019
 
 ---

articles/azure-monitor/visualize/media/vmext-troubleshoot/log-analytics-vmview-extensiondetails.png renamed to articles/azure-monitor/agents/media/vmext-troubleshoot/log-analytics-vmview-extensiondetails.png

@@ -2,8 +2,6 @@
 title: Create metric alert monitors in Azure CLI
 description: Learn how to create metric alerts in Azure Monitor with Azure CLI commands. These samples create alerts for a virtual machine and an App Service Plan.
 ms.topic: sample
-author: bwren
-ms.author: bwren
 ms.date: 04/05/2022
 ms.custom: devx-track-azurecli
 
@@ -19,7 +17,7 @@ These samples create metric alert monitors in Azure Monitor by using Azure CLI c
 
 This alert monitors an existing virtual machine named `VM07` in the resource group named `ContosoVMRG`.
 
-You can create a resource group by using the [az group create](/cli/azure/group#az-group-create) command. For information about creating virtual machines, see [Create a Windows virtual machine with the Azure CLI](../virtual-machines/windows/quick-create-cli.md),  [Create a Linux virtual machine with the Azure CLI](../virtual-machines/linux/quick-create-cli.md), and the [az vm create](/cli/azure/vm#az-vm-create) command.
+You can create a resource group by using the [az group create](/cli/azure/group#az-group-create) command. For information about creating virtual machines, see [Create a Windows virtual machine with the Azure CLI](../../virtual-machines/windows/quick-create-cli.md),  [Create a Linux virtual machine with the Azure CLI](../../virtual-machines/linux/quick-create-cli.md), and the [az vm create](/cli/azure/vm#az-vm-create) command.
 
 ```azurecli
 # resource group name: ContosoVMRG
@@ -116,5 +114,5 @@ This article uses the following Azure CLI commands:
 
 ## Next steps
 
-- [Azure Monitor CLI samples](cli-samples.md)
-- [Understand how metric alerts work in Azure Monitor](alerts/alerts-metric-overview.md)
+- [Azure Monitor CLI samples](../cli-samples.md)
+- [Understand how metric alerts work in Azure Monitor](alerts-metric-overview.md)

articles/azure-monitor/visualize/media/vmext-troubleshoot/log-analytics-vmview-extensions.png renamed to articles/azure-monitor/agents/media/vmext-troubleshoot/log-analytics-vmview-extensions.png

@@ -3,8 +3,6 @@ title: Resource Manager template samples for log query alerts
 description: Sample Azure Resource Manager templates to deploy Azure Monitor log query alerts.
 ms.topic: sample
 ms.custom: devx-track-arm-template
-author: bwren
-ms.author: bwren
 ms.date: 05/11/2022
 ---
 

articles/azure-monitor/insights/solution-agenthealth.md renamed to articles/azure-monitor/agents/solution-agenthealth.md

@@ -6,7 +6,7 @@ ms.topic: conceptual
 ms.tgt_pltfrm: na
 ms.custom: ignite-2022
 ms.workload: infrastructure-services
-ms.date: 07/28/2022
+ms.date: 08/09/2023
 ms.reviewer: bwren
 ---
 
@@ -30,9 +30,7 @@ Azure resources generate a significant amount of monitoring data. Azure Monitor
 
 Metrics in Azure Monitor are stored in a time-series database that's optimized for analyzing time-stamped data. Time-stamping makes metrics well suited for alerting and fast detection of issues. Metrics can tell you how your system is performing but typically must be combined with logs to identify the root cause of issues.
 
-Metrics are available for interactive analysis in the Azure portal with [Azure Metrics Explorer](essentials/metrics-getting-started.md). They can be added to an [Azure dashboard](app/tutorial-app-dashboards.md) for visualization in combination with other data and used for near-real-time [alerting](alerts/alerts-metric.md).
-
-To read more about Azure Monitor metrics, including their sources of data, see [Metrics in Azure Monitor](essentials/data-platform-metrics.md).
+Azure Monitor Metrics includes two types of metrics - native metrics and Prometheus metrics. See a comparison of the two and further details about Azure Monitor metrics, including their sources of data, at [Metrics in Azure Monitor](essentials/data-platform-metrics.md).
 
 ### Logs
 
@@ -68,19 +66,6 @@ Once [Change Analysis is enabled](./change/change-analysis-enable.md), the `Micr
 
 Read more about Change Analysis, including data sources in [Use Change Analysis in Azure Monitor](./change/change-analysis.md).
 
-## Compare Azure Monitor metrics and logs
-
-The following table compares metrics and logs in Azure Monitor.
-
-| Attribute  | Metrics | Logs |
-|:---|:---|:---|
-| Benefits | Lightweight and capable of near-real time scenarios such as alerting. Ideal for fast detection of issues. | Analyzed with rich query language. Ideal for deep analysis and identifying root cause. |
-| Data | Numerical values only | Text or numeric data |
-| Structure | Standard set of properties including sample time, resource being monitored, a numeric value. Some metrics include multiple dimensions for further definition. | Unique set of properties depending on the log type. |
-| Collection | Collected at regular intervals. | May be collected sporadically as events trigger a record to be created. |
-| Analyze in Azure portal | Metrics Explorer | Log Analytics |
-| Data sources include | Platform metrics collected from Azure resources<br>Applications monitored by Application Insights<br>Azure Monitor agent<br>Custom defined by application or API | Application and resource logs<br>Azure Monitor agent<br>Application requests and exceptions<br>Logs ingestion API<br>Azure Sentinel<br>Microsoft Defender for Cloud |
-
 ## Collect monitoring data
 Different [sources of data for Azure Monitor](data-sources.md) will write to either a Log Analytics workspace (Logs) or the Azure Monitor metrics database (Metrics) or both. Some sources will write directly to these data stores, while others may write to another location such as Azure storage and require some configuration to populate logs or metrics.