cleanup

Author: bwren

articles/azure-monitor/best-practices-cost.md

@@ -27,13 +27,12 @@ This article describes [Cost optimization](/azure/architecture/framework/cost/)
 
 ## Azure resources
 
+
 ### Design checklist
 
 > [!div class="checklist"]
-> - Use diagnostic settings and transformations to collect only critical resource log data from Azure resources.
-> - Configure VM agents to collect only critical events.
-> - Use transformations to filter resource logs for [supported tables](logs/tables-feature-support.md).
-> - Ensure that VMs aren't sending data to multiple workspaces.
+> - Collect only critical resource log data from Azure resources.
+
 
 ### Configuration recommendations
 
@@ -45,31 +44,52 @@ This article describes [Cost optimization](/azure/architecture/framework/cost/)
 
 ### Design checklist
 
+
+> [!div class="checklist"]
+> - Configure VM agents to collect only important events.
+> - Ensure that VMs aren't sending data to multiple workspaces.
+> - Use transformations to filter unnecessary data from collected events.
+
 ### Configuration recommendations
 
 | Recommendation | Description |
 |:---|:---|
-| Configure VM agents to collect only critical events. | Virtual machines can vary significantly in the amount of data they collect, depending on the amount of telemetry generated by the applications and services they have installed. See [Monitor virtual machines with Azure Monitor: Workloads](vm/monitor-virtual-machine-data-collection.md#controlling-costs) for guidance on data to collect and strategies for using XPath queries and transformations to limit it.|
+| Configure VM agents to collect only important events. | Virtual machines can vary significantly in the amount of data they collect, depending on the amount of telemetry generated by the applications and services they have installed. See [Monitor virtual machines with Azure Monitor: Workloads](vm/monitor-virtual-machine-data-collection.md#controlling-costs) for guidance on data to collect and strategies for using [XPath queries](agents/data-collection-rule-azure-monitor-agent.md#filter-events-using-xpath-queries) to limit it.|
 | Ensure that VMs aren't sending duplicate data. | Any configuration that uses multiple agents on a single machine or where you multi-home agents to send data to multiple workspaces may incur charges for the same data multiple times. If you do multi-home agents, make sure you're sending unique data to each workspace. See [Analyze usage in Log Analytics workspace](logs/analyze-usage.md) for guidance on analyzing your collected data to make sure you aren't collecting duplicate data. If you're migrating between agents, continue to use the Log Analytics agent until you [migrate to the Azure Monitor agent](./agents/azure-monitor-agent-migration.md) rather than using both together unless you can ensure that each is collecting unique data. |
+| Use transformations to filter unnecessary data from collected events. | [Transformations](essentials/data-collection-transformations.md) can be used in data collection rules to remove unnecessary data or even entire columns from events collected from the virtual machine which can significantly reduce the cost for their ingestion and retention. |
 
 ## Container insights
 
 ### Design checklist
 
+> [!div class="checklist"]
+> - Configure agent collection to remove unneeded data.
+> - Modify settings for collection of metric data.
+> - Limit Prometheus metrics collected.
+> - Configure Basic Logs.
 ### Configuration recommendations
 
 | Recommendation | Description |
 |:---|:---|
 | Configure agent collection to remove unneeded data. |  Analyze the data collected by Container insights as described in [Controlling ingestion to reduce cost](containers/container-insights-cost.md#control-ingestion-to-reduce-cost) and adjust your configuration to stop collection of data in ContainerLogs you don't need. |
-| Modify settings for collection of metric data |  You can reduce your costs by modifying the default collection settings Container insights uses for the collection of metric data. See [Enable cost optimization settings (preview)](containers/container-insights-cost-config.md) for details on modifying both the frequency that metric data is collected and the namespaces that are collected. |
-| Limit Prometheus metrics collected | If you configured Prometheus metric scraping, then follow the recommendations at [Controlling ingestion to reduce cost](containers/container-insights-cost.md#prometheus-metrics-scraping) to optimize your data collection for cost. |
-| Configure Basic Logs | [Convert your schema to ContainerLogV2](containers/container-insights-logging-v2.md) which is compatible with Basic logs and can provide significant cost savings as described in [Controlling ingestion to reduce cost](containers/container-insights-cost.md#configure-basic-logs). |
+| Modify settings for collection of metric data. |  You can reduce your costs by modifying the default collection settings Container insights uses for the collection of metric data. See [Enable cost optimization settings (preview)](containers/container-insights-cost-config.md) for details on modifying both the frequency that metric data is collected and the namespaces that are collected. |
+| Limit Prometheus metrics collected. | If you configured Prometheus metric scraping, then follow the recommendations at [Controlling ingestion to reduce cost](containers/container-insights-cost.md#prometheus-metrics-scraping) to optimize your data collection for cost. |
+| Configure Basic Logs. | [Convert your schema to ContainerLogV2](containers/container-insights-logging-v2.md) which is compatible with Basic logs and can provide significant cost savings as described in [Controlling ingestion to reduce cost](containers/container-insights-cost.md#configure-basic-logs). |
 
 
 ## Application Insights
 
 ### Design checklist
 
+> [!div class="checklist"]
+> - Use sampling to tune the amount of data collected.
+> - Use sampling to tune the amount of data collected.
+> - Limit the number of Ajax calls.
+> - Disable unneeded modules.
+> - Pre-aggregate metrics from any calls to TrackMetric.
+> - Limit the use of custom metrics.
+> - Ensure use of updated SDKs.
+
 ### Configuration recommendations
 
 | Recommendation | Description |
@@ -82,13 +102,6 @@ This article describes [Cost optimization](/azure/architecture/framework/cost/)
 | Limit the use of custom metrics. | The Application Insights option to [Enable alerting on custom metric dimensions](app/pre-aggregated-metrics-log-metrics.md#custom-metrics-dimensions-and-pre-aggregation) can increase costs. Using this option can result in the creation of more pre-aggregation metrics. |
 | Ensure use of updated SDKs. | Earlier versions of the ASP.NET Core SDK and Worker Service SDK [collect many counters by default](app/eventcounters.md#default-counters-collected), which were collected as custom metrics. Use later versions to specify [only required counters](app/eventcounters.md#customizing-counters-to-be-collected). |
 
-#### All log data collection
-
-| Recommendation | Description |
-|:---|:---|
-| Remove unnecssary data during data ingestion | After following all of the preveious recommendations, consider using Azure Monitor [data collection transformations](essentials/data-collection-transformations.md) to reduce the size of your data during ingestion. |
-
-
 
 
 ## Next step

articles/azure-monitor/faq.yml

@@ -506,7 +506,7 @@ sections:
         answer: |
           Yes, for experimental use. In the basic pricing plan, your application can send a certain allowance of data each month free of charge. The free allowance is large enough to cover development and publishing an app for a few users. You can set a cap to prevent more than a specified amount of data from being processed.
           
-          Larger volumes of telemetry are charged by the gigabyte. We provide some tips on how to [limit your charges](best-practices-cost.md#data-collection).
+          Larger volumes of telemetry are charged by the gigabyte. We provide some tips on how to [limit your charges](best-practices-cost.md#application-insights).
           
           The Enterprise plan incurs a charge for each day that each web server node sends telemetry. It's suitable if you want to use Continuous Export on a large scale.