Moving App Insights FAQs

Author: v-jbasden

articles/azure-monitor/app/api-custom-events-metrics.md

@@ -1133,6 +1133,8 @@ To determine how long data is kept, see [Data retention and privacy](./data-rete
 
 ## Frequently asked questions
 
+This section provides answers to common questions.
+
 ### Why am I missing telemetry data?
 
 Both [TelemetryChannels](telemetry-channels.md#what-are-telemetry-channels) will lose buffered telemetry if it isn't flushed before an application shuts down.
@@ -1155,6 +1157,17 @@ The Application Insights SDK isn't compatible with autoinstrumentation. If autoi
 
 Turn off autoinstrumentation in the Azure portal on the Application Insights tab of the App Service page or set <code class="notranslate">ApplicationInsightsAgent_EXTENSION_VERSION</code> to <code class="notranslate">disabled</code>.
 
+### Why are the counts in Search and Metrics charts unequal?
+
+[Sampling](./sampling.md) reduces the number of telemetry items (like requests and custom events) that are sent from your app to the portal. In Search, you see the number of items received. In metric charts that display a count of events, you see the number of original events that occurred.
+          
+Each item that's transmitted carries an `itemCount` property that shows how many original events that item represents. To observe sampling in operation, you can run this query in Log Analytics:
+          
+```
+    requests | summarize original_events = sum(itemCount), transmitted_events = count()
+```
+          
+
 ## <a name="next"></a>Next steps
 
 * [Search events and logs](./diagnostic-search.md)

articles/azure-monitor/app/app-insights-overview.md

@@ -170,8 +170,49 @@ We're constantly assessing opportunities to expand our support for other languag
 
 ## Frequently asked questions
 
-Review [frequently asked questions](../faq.yml).
-
+This section provides answers to common questions.
+
+### What telemetry does Application Insights collect?
+
+From server web apps:
+          
+* HTTP requests.
+* [Dependencies](./asp-net-dependencies.md). Calls to SQL databases, HTTP calls to external services, Azure Cosmos DB, Azure Table Storage, Azure Blob Storage, and Azure Queue Storage.
+* [Exceptions](./asp-net-exceptions.md) and stack traces.
+* [Performance counters](./performance-counters.md): If you use the [Azure Monitor Application Insights agent](./application-insights-asp-net-agent.md), [Azure monitoring for VMs or virtual machine scale sets](./azure-vm-vmss-apps.md), or the [Application Insights collectd writer](/previous-versions/azure/azure-monitor/app/deprecated-java-2x#collectd-linux-performance-metrics-in-application-insights-deprecated).
+* [Custom events and metrics](./api-custom-events-metrics.md) that you code.
+* [Trace logs](./asp-net-trace-logs.md) if you configure the appropriate collector.
+          
+From [client webpages](./javascript-sdk.md):
+          
+* Uncaught exceptions in your app, including information on
+  * Stack trace
+  * Exception details and message accompanying the error
+  * Line & column number of error
+  * URL where error was raised
+* Network Dependency Requests made by your app XHR and Fetch (fetch collection is disabled by default) requests, include information on:
+  * Url of dependency source
+  * Command & Method used to request the dependency
+  * Duration of the request
+  * Result code and success status of the request
+  * ID (if any) of user making the request
+  * Correlation context (if any) where request is made
+* User information (for example, Location, network, IP)
+* Device information (for example, Browser, OS, version, language, model)
+* Session information
+
+  > [!Note]
+  > For some applications, such as single-page applications (SPAs), the duration may not be recorded and will default to 0.
+
+    For more information, see [Data collection, retention, and storage in Application Insights](./data-retention-privacy.md).
+          
+From other sources, if you configure them:
+          
+* [Azure diagnostics](../agents/diagnostics-extension-to-application-insights.md)
+* [Import to Log Analytics](../logs/data-collector-api.md)
+* [Log Analytics](../logs/data-collector-api.md)
+* [Logstash](../logs/data-collector-api.md)
+          
 ## Troubleshooting
 
 Review dedicated [troubleshooting articles](/troubleshoot/azure/azure-monitor/welcome-azure-monitor) for Application Insights.

articles/azure-monitor/app/data-model-complete.md

@@ -411,6 +411,16 @@ This field represents the node name used for billing purposes. Use it to overrid
 
 **Maximum length:** 256
 
+## Frequently asked questions
+
+This section provides answers to common questions.
+
+### How would I measure the impact of a monitoring campaign?
+
+PageView Telemetry includes URL and you could parse the UTM parameter using a regex function in Kusto.
+          
+Occasionally, this data might be missing or inaccurate if the user or enterprise disables sending User Agent in browser settings. The [UA Parser regexes](https://github.com/ua-parser/uap-core/blob/master/regexes.yaml) might not include all device information. Or Application Insights might not have adopted the latest updates.
+
 ## Next steps
 
 Learn how to use the [Application Insights API for custom events and metrics](./api-custom-events-metrics.md), including:

articles/azure-monitor/app/data-retention-privacy.md

@@ -321,6 +321,22 @@ You can [switch off some of the data by editing ApplicationInsights.config][conf
 
 No. Data is read-only and can only be deleted via the purge functionality. To learn more, see [Guidance for personal data stored in Log Analytics and Application Insights](../logs/personal-data-mgmt.md#delete).
 
+## Frequently asked questions
+
+This section provides answers to common questions.
+
+### What happens to Application Insight telemetry when a server or device loses connection with Azure?
+
+All of our SDKs, including the web SDK, include *reliable transport* or *robust transport*. When the server or device loses connection with Azure, telemetry is [stored locally on the file system](./data-retention-privacy.md#does-the-sdk-create-temporary-local-storage) (Server SDKs) or in HTML5 Session Storage (Web SDK). The SDK periodically retries to send this telemetry until our ingestion service considers it "stale" (48 hours for logs, 30 minutes for metrics). Stale telemetry is dropped. In some cases, such as when local storage is full, retry won't occur.
+
+### Is personal data sent in the telemetry?
+
+You can send personal data if your code sends such data. It can also happen if variables in stack traces include personal data. Your development team should conduct risk assessments to ensure that personal data is properly handled. Learn more about [data retention and privacy](./data-retention-privacy.md).
+          
+*All* octets of the client web address are always set to 0 after the geolocation attributes are looked up.
+          
+The [Application Insights JavaScript SDK](./javascript.md) doesn't include any personal data in its autocompletion, by default. However, some personal data used in your application might be picked up by the SDK (for example, full names in `window.title` or account IDs in XHR URL query parameters). For custom personal data masking, add a [telemetry initializer](./api-filtering-sampling.md#javascript-web-applications).   
+
 <!--Link references-->
 
 [api]: ./api-custom-events-metrics.md

articles/azure-monitor/app/ip-collection.md

@@ -265,6 +265,22 @@ Newly collected IP addresses will appear in the `customDimensions_client-ip` col
 
 If you're testing from localhost, and the value for `customDimensions_client-ip` is `::1`, this value is expected behavior. The `::1` value represents the loopback address in IPv6. It's equivalent to `127.0.0.1` in IPv4.
 
+## Frequently asked questions
+
+This section provides answers to common questions.
+
+### How is city, country/region, and other geolocation data calculated?
+
+We look up the IP address (IPv4 or IPv6) of the web client:
+          
+* Browser telemetry: We collect the sender's IP address.
+* Server telemetry: The Application Insights module collects the client IP address. It's not collected if `X-Forwarded-For` is set.
+* To learn more about how IP address and geolocation data is collected in Application Insights, see [Geolocation and IP address handling](./ip-collection.md).
+          
+You can configure `ClientIpHeaderTelemetryInitializer` to take the IP address from a different header. In some systems, for example, it's moved by a proxy, load balancer, or CDN to `X-Originating-IP`. [Learn more](https://apmtips.com/posts/2016-07-05-client-ip-address/).
+          
+You can [use Power BI](../logs/log-powerbi.md) to display your request telemetry on a map if you've [migrated to a workspace-based resource](./convert-classic-resource.md).          
+
 ## Next steps
 
 * Learn more about [personal data collection](../logs/personal-data-mgmt.md) in Application Insights.

articles/azure-monitor/app/javascript-framework-extensions.md

@@ -763,6 +763,16 @@ Check out the [Application Insights Angular demo](https://github.com/microsoft/a
 
 ---
 
+## Frequently asked questions
+
+This section provides answers to common questions.
+
+### How does Application Insights generate device information like browser, OS, language, and model?
+
+The browser passes the User Agent string in the HTTP header of the request. The Application Insights ingestion service uses [UA Parser](https://github.com/ua-parser/uap-core) to generate the fields you see in the data tables and experiences. As a result, Application Insights users are unable to change these fields.
+          
+Occasionally, this data might be missing or inaccurate if the user or enterprise disables sending User Agent in browser settings. The [UA Parser regexes](https://github.com/ua-parser/uap-core/blob/master/regexes.yaml) might not include all device information. Or Application Insights might not have adopted the latest updates.
+
 ## Next steps
 
 - [Confirm data is flowing](javascript-sdk.md#confirm-data-is-flowing).

articles/azure-monitor/app/javascript-sdk-configuration.md

@@ -325,6 +325,21 @@ This section only applies to you if you're using the deprecated functions and yo
 
 See the dedicated [troubleshooting article](/troubleshoot/azure/azure-monitor/app-insights/javascript-sdk-troubleshooting).
 
+## Frequently asked questions
+
+This section provides answers to common questions.
+
+### How can I update my third-party server configuration for the JavaScript SDK?
+
+The server side needs to be able to accept connections with those headers present. Depending on the `Access-Control-Allow-Headers` configuration on the server side, it's often necessary to extend the server-side list by manually adding `Request-Id`, `Request-Context`, and `traceparent` (W3C distributed header).
+
+Access-Control-Allow-Headers: `Request-Id`, `traceparent`, `Request-Context`, `<your header>`
+
+### How can I disable distributed tracing for the JavaScript SDK?
+
+Distributed tracing can be disabled in configuration.
+      
+
 ## Next steps
 
 * [Track usage](usage-overview.md)

articles/azure-monitor/app/javascript-sdk.md

@@ -164,6 +164,46 @@ If you want to use the extra features provided by plugins for specific framework
 
       For essential KQL operators, see [Learn common KQL operators](/azure/data-explorer/kusto/query/tutorials/learn-common-operators). 
 
+## Frequently asked questions
+
+This section provides answers to common questions.
+
+### What are the user and session counts?
+
+* The JavaScript SDK sets a user cookie on the web client, to identify returning users, and a session cookie to group activities.
+* If there's no client-side script, you can [set cookies at the server](https://apmtips.com/posts/2016-07-09-tracking-users-in-api-apps/).
+* If one real user uses your site in different browsers, or by using in-private/incognito browsing, or different machines, they're counted more than once.
+* To identify a signed-in user across machines and browsers, add a call to [setAuthenticatedUserContext()](./api-custom-events-metrics.md#authenticated-users).
+
+### What is the JavaScript SDK performance/overhead?
+
+The Application Insights JavaScript SDK has a minimal overhead on your website. At just 36 KB gzipped, and taking only ~15 ms to initialize, the SDK adds a negligible amount of load time to your website. The minimal components of the library are quickly loaded when you use the SDK, and the full script is downloaded in the background.
+
+Additionally, while the script is downloading from the CDN, all tracking of your page is queued, so you don't lose any telemetry during the entire life cycle of your page. This setup process provides your page with a seamless analytics system that's invisible to your users.
+
+### What browsers are supported by the JavaScript SDK?
+
+![Chrome](https://raw.githubusercontent.com/alrra/browser-logos/master/src/chrome/chrome_48x48.png) | ![Firefox](https://raw.githubusercontent.com/alrra/browser-logos/master/src/firefox/firefox_48x48.png) | ![IE](https://raw.githubusercontent.com/alrra/browser-logos/master/src/edge/edge_48x48.png) | ![Opera](https://raw.githubusercontent.com/alrra/browser-logos/master/src/opera/opera_48x48.png) | ![Safari](https://raw.githubusercontent.com/alrra/browser-logos/master/src/safari/safari_48x48.png)
+--- | --- | --- | --- | --- |
+Chrome Latest ✔ |  Firefox Latest ✔ | v3.x: IE 9+ & Microsoft Edge ✔<br>v2.x: IE 8+ Compatible & Microsoft Edge ✔ | Opera Latest ✔ | Safari Latest ✔ |
+
+### Where can I find code examples for the JavaScript SDK?
+
+For runnable examples, see [Application Insights JavaScript SDK samples](https://github.com/microsoft/ApplicationInsights-JS/tree/master/examples).
+
+### What is the ES3/Internet Explorer 8 compatibility with the JavaScript SDK?
+
+We need to take necessary measures to ensure that this SDK continues to "work" and doesn't break the JavaScript execution when loaded by an older browser. It would be ideal to not support older browsers, but numerous large customers can't control which browser their users choose to use.
+
+This statement doesn't mean that we only support the lowest common set of features. We need to maintain ES3 code compatibility. New features need to be added in a manner that wouldn't break ES3 JavaScript parsing and added as an optional feature.
+
+See GitHub for full details on [Internet Explorer 8 support](https://github.com/Microsoft/ApplicationInsights-JS#es3ie8-compatibility).
+      
+### Is the JavaScript SDK open-source?
+
+Yes, the Application Insights JavaScript SDK is open source. To view the source code or to contribute to the project, see the [official GitHub repository](https://github.com/Microsoft/ApplicationInsights-JS).
+      
+
 ## Support
 
 - If you can't run the application or you aren't getting data as expected, see the dedicated [troubleshooting article](/troubleshoot/azure/azure-monitor/app-insights/javascript-sdk-troubleshooting).

articles/azure-monitor/app/separate-resources.md

@@ -153,6 +153,34 @@ The build version number is generated only by the Microsoft Build Engine, not by
 
 If you use Azure DevOps, you can [get an annotation marker](../../azure-monitor/app/annotations.md) added to your charts whenever you release a new version.
 
+## Frequently asked questions
+
+This section provides answers to common questions.
+
+### How do I move an Application Insights resource to a new region?
+
+Moving existing Application Insights resources from one region to another is *currently not supported*. Historical data that you've collected *can't be migrated* to a new region. The only partial workaround is to:
+          
+1. Create a new Application Insights resource ([classic](/previous-versions/azure/azure-monitor/app/create-new-resource) or [workspace based](./app/create-workspace-resource.md)) in the new region.
+1. Re-create all unique customizations specific to the original resource in the new resource.
+1. Modify your application to use the new region resource's [instrumentation key](/previous-versions/azure/azure-monitor/app/create-new-resource#copy-the-instrumentation-key) or [connection string](./sdk-connection-string.md).
+1. Test to confirm that everything is continuing to work as expected with your new Application Insights resource.
+1. At this point, you can either keep or delete the original Application Insights resource. If you delete a classic Application Insights resource, *all historical data is lost*. If the original resource was workspace based, its data remains in Log Analytics. Keeping the original Application Insights resource allows you to access its historical data until its data retention settings run out.
+          
+Unique customizations that commonly need to be manually re-created or updated for the resource in the new region include but aren't limited to:
+          
+- Re-create custom dashboards and workbooks.
+- Re-create or update the scope of any custom log/metric alerts.
+- Re-create availability alerts.
+- Re-create any custom Azure role-based access control settings that are required for your users to access the new resource.
+- Replicate settings involving ingestion sampling, data retention, daily cap, and custom metrics enablement. These settings are controlled via the **Usage and estimated costs** pane.
+- Any integration that relies on API keys, such as [release annotations](./annotations.md) and [live metrics secure control channel](./live-stream.md#secure-the-control-channel). You need to generate new API keys and update the associated integration.
+- Continuous export in classic resources must be configured again.
+- Diagnostic settings in workspace-based resources must be configured again.
+          
+> [!NOTE]
+> If the resource you're creating in a new region is replacing a classic resource, we recommend that you explore the benefits of [creating a new workspace-based resource](./create-workspace-resource.md). Alternatively, [migrate your existing resource to workspace based](./convert-classic-resource.md).
+
 ## Next steps
 
 * [Shared resources for multiple roles](../../azure-monitor/app/app-map.md)