Merge pull request #228372 from rboucher/patch-30

Update costs per Github issue

Author: prmerger-automator[bot]

articles/azure-monitor/essentials/metrics-supported.md

@@ -50,7 +50,7 @@ Host OS metrics *are* available and listed in the tables. Host OS metrics relate
 > [!TIP]
 > A best practice is to use and configure the Azure Monitor agent to send guest OS performance metrics into the same Azure Monitor metric database where platform metrics are stored. The agent routes guest OS metrics through the [custom metrics](../essentials/metrics-custom-overview.md) API. You can then chart, alert, and otherwise use guest OS metrics like platform metrics. 
 >
-> Alternatively or in addition, you can send the guest OS metrics to Azure Monitor Logs by using the same agent. There you can query on those metrics in combination with non-metric data by using Log Analytics. 
+> Alternatively or in addition, you can send the guest OS metrics to Azure Monitor Logs by using the same agent. There you can query on those metrics in combination with non-metric data by using Log Analytics. Standard [Log Analytics workspace costs](https://azure.microsoft.com/pricing/details/monitor/) would then apply.  
 
 The Azure Monitor agent replaces the Azure Diagnostics extension and Log Analytics agent, which were previously used for guest OS routing. For important additional information, see [Overview of Azure Monitor agents](../agents/agents-overview.md).
 
@@ -4369,4 +4369,4 @@ This latest update adds a new column and reorders the metrics to be alphabetical
 - [Export metrics to storage, Event Hub, or Log Analytics](../essentials/platform-logs-overview.md)
 
 
-<!--Gen Date:  Wed Feb 01 2023 09:43:49 GMT+0200 (Israel Standard Time)-->
+<!--Gen Date:  Wed Feb 01 2023 09:43:49 GMT+0200 (Israel Standard Time)-->