|
2 | 2 | title: Migrate an Application Insights classic resource to a workspace-based resource - Azure Monitor | Microsoft Docs
|
3 | 3 | description: Learn about the steps required to upgrade your Application Insights classic resource to the new workspace-based model.
|
4 | 4 | ms.topic: conceptual
|
5 |
| -ms.date: 08/22/2022 |
| 5 | +ms.date: 08/23/2022 |
6 | 6 | ms.custom: devx-track-azurepowershell
|
7 | 7 | ms.reviewer: cawa
|
8 | 8 | ---
|
@@ -229,6 +229,51 @@ Once a workspace-based Application Insights resource has been created, you can m
|
229 | 229 |
|
230 | 230 | From within the Application Insights resource pane, select **Properties** > **Change Workspace** > **Log Analytics Workspaces**.
|
231 | 231 |
|
| 232 | +## Frequently asked questions |
| 233 | + |
| 234 | +### Is there any implication on the cost from migration? |
| 235 | + |
| 236 | +There is usually no difference, with a couple of exceptions. |
| 237 | + |
| 238 | + - Migrated Application Insights resources can leverage [Log Analytics Commitment Tiers](../logs/cost-logs.md#commitment-tiers) to reduce cost if the data volumes in the workspace are high enough. |
| 239 | + - Very old Application Insights resources that get 1GB per month free (a grandfathering from the original Application Insights pricing model) will lose this when they are migrated. |
| 240 | + |
| 241 | +### How will telemetry capping work? |
| 242 | + |
| 243 | +Set a [daily cap on the Log Analytics workspace](../logs/daily-cap.md#application-insights). |
| 244 | + |
| 245 | +There is no strict (billing-wise) capping available. |
| 246 | + |
| 247 | +### How will ingestion-based sampling work? |
| 248 | + |
| 249 | +There are no changes to ingestion-based sampling. |
| 250 | + |
| 251 | +### Will there be any gap in data collected during migration? |
| 252 | + |
| 253 | +No. We merge data during query time. |
| 254 | + |
| 255 | +### Will my old logs queries continue to work? |
| 256 | + |
| 257 | +Yes, they will continue to work. |
| 258 | + |
| 259 | +### Will my dashboards that have pinned metric and log charts continue to work after migration? |
| 260 | + |
| 261 | +Yes, they will continue to work. |
| 262 | + |
| 263 | +### Will migration impact AppInsights API accessing data? |
| 264 | + |
| 265 | +No, migration will not impact existing API access to data. After migration you will be able to access data directly from a workspace using a [slightly different schema](#workspace-based-resource-changes). |
| 266 | + |
| 267 | +### Will there be any impact on Live Metrics or other monitoring experiences? |
| 268 | + |
| 269 | +No, there is no impact to [Live Metrics](live-stream.md#live-metrics-monitor--diagnose-with-1-second-latency) or other monitoring experiences. |
| 270 | + |
| 271 | +### What happens with Continuous export after migration? |
| 272 | + |
| 273 | +Continuous export does not support workspace-based resources. |
| 274 | + |
| 275 | +You will need to switch to [Diagnostic Settings](../essentials/diagnostic-settings.md#diagnostic-settings-in-azure-monitor). |
| 276 | + |
232 | 277 | ## Troubleshooting
|
233 | 278 |
|
234 | 279 | ### Access mode
|
|
0 commit comments