Merge pull request #191749 from JasonAndrewWriter/Key_Depreciation-includesecond22

Court72 · web-flow · commit 86c80afe417f · 2022-03-15T12:25:13.000-06:00
remainder of key deprecation includes
diff --git a/articles/azure-monitor/app/data-model-request-telemetry.md b/articles/azure-monitor/app/data-model-request-telemetry.md
@@ -8,10 +8,12 @@ ms.reviewer: sergkanz
 
 # Request telemetry: Application Insights data model
 
-A request telemetry item (in [Application Insights](./app-insights-overview.md)) represents the logical sequence of execution triggered by an external request to your application. Every request execution is identified by unique `ID` and `url` containing all the execution parameters. You can group requests by logical `name` and define the `source` of this request. Code execution can result in `success` or `fail` and has a certain `duration`. Both success and failure executions may be grouped further by `resultCode`. Start time for the request telemetry defined on the envelope level.
+A request telemetry item (in [Application Insights](./app-insights-overview.md)) represents the logical sequence of execution triggered by an external request to your application. Every request execution is identified by unique `ID` and `url` containing all the execution parameters. You can group requests by logical `name` and define the `source` of this request. Code execution can result in `success` or `fail` and has a certain `duration`. Both success and failure executions may be grouped further by `resultCode`. Start time for the request telemetry defined on the envelope level.  
 
 Request telemetry supports the standard extensibility model using custom `properties` and `measurements`.
 
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+
 ## Name
 
 Name of the request represents code path taken to process the request. Low cardinality value to allow better grouping of requests. For HTTP requests it represents the HTTP method and URL path template like `GET /values/{id}` without the actual `id` value.
diff --git a/articles/azure-monitor/app/data-retention-privacy.md b/articles/azure-monitor/app/data-retention-privacy.md
@@ -30,6 +30,7 @@ The Application Insights service stores and analyzes the telemetry. To see the a
 You can have data exported from the Application Insights service, for example to a database or to external tools. You provide each tool with a special key that you obtain from the service. The key can be revoked if necessary. 
 
 Application Insights SDKs are available for a range of application types: web services hosted in your own Java EE or ASP.NET servers, or in Azure; web clients - that is, the code running in a web page; desktop apps and services; device apps such as Windows Phone, iOS, and Android. They all send telemetry to the same service.
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
 
 ## What data does it collect?
 There are three sources of data:
diff --git a/articles/azure-monitor/app/export-telemetry.md b/articles/azure-monitor/app/export-telemetry.md
@@ -16,6 +16,8 @@ Want to keep your telemetry for longer than the standard retention period? Or pr
 > Continuous export is only supported for classic Application Insights resources. [Workspace-based Application Insights resources](./create-workspace-resource.md) must use [diagnostic settings](./create-workspace-resource.md#export-telemetry).
 >
 
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+
 Before you set up continuous export, there are some alternatives you might want to consider:
 
 * The Export button at the top of a metrics or search tab lets you transfer tables and charts to an Excel spreadsheet.
diff --git a/articles/azure-monitor/app/ilogger.md b/articles/azure-monitor/app/ilogger.md
@@ -167,6 +167,8 @@ namespace WebApplication
 In the preceding code, `ApplicationInsightsLoggerProvider` is configured with your `"APPINSIGHTS_INSTRUMENTATIONKEY"` instrumentation key. Filters are applied, setting the log level to <xref:Microsoft.Extensions.Logging.LogLevel.Trace?displayProperty=nameWithType>.
 
 
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+
 #### Example Startup.cs
 
 ```csharp
diff --git a/articles/azure-monitor/app/java-2x-collectd.md b/articles/azure-monitor/app/java-2x-collectd.md
@@ -25,6 +25,8 @@ Take a copy of the instrumentation key, which identifies the resource.
 
 ![Browse all, open your resource, and then in the Essentials drop-down, select, and copy the Instrumentation Key](./media/java-collectd/instrumentation-key-001.png)
 
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+
 ## Install collectd and the plug-in
 On your Linux server machines:
 
diff --git a/articles/azure-monitor/app/java-2x-get-started.md b/articles/azure-monitor/app/java-2x-get-started.md
@@ -34,6 +34,8 @@ Application Insights is an extensible analytics service for web developers that
 
     ![In the new resource overview, click Properties and copy the Instrumentation Key](./media/java-get-started/instrumentation-key-001.png)
 
+    [!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+
 ## Add the Application Insights SDK for Java to your project
 
 *Choose your project type.*
diff --git a/articles/azure-monitor/app/java-2x-micrometer.md b/articles/azure-monitor/app/java-2x-micrometer.md
@@ -54,6 +54,8 @@ Steps
 1. Build your application and run
 2. The above should get you up and running with pre-aggregated metrics auto collected to Azure Monitor. For details on how to fine-tune Application Insights Spring Boot starter refer to the [readme on GitHub](https://github.com/Azure/azure-sdk-for-java/blob/master/sdk/spring/azure-spring-boot-starter/README.md).
 
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+
 ## Using Spring 2.x
 
 Add the following dependencies to your pom.xml or build.gradle file:
diff --git a/articles/azure-monitor/app/java-2x-trace-logs.md b/articles/azure-monitor/app/java-2x-trace-logs.md
@@ -19,6 +19,8 @@ If you're using Logback or Log4J (v1.2 or v2.0) for tracing, you can have your t
 > [!TIP]
 > You only need to set your Application Insights Instrumentation Key once for your application. If you are using a framework like Java Spring, you may have already registered the key elsewhere in your app's configuration.
 
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+
 ## Using the Application Insights Java agent
 
 By default, the Application Insights Java agent automatically captures logging performed at `WARN` level and above.
diff --git a/articles/azure-monitor/app/java-2x-troubleshoot.md b/articles/azure-monitor/app/java-2x-troubleshoot.md
@@ -35,6 +35,8 @@ Questions or problems with [Azure Application Insights in Java][java]? Here are
 * Please also look at [GitHub issues page](https://github.com/microsoft/ApplicationInsights-Java/issues) for known issues with the SDK.
 * Please ensure to use same version of Application Insights core, web, agent and logging appenders to avoid any version conflict issues.
 
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+
 #### I used to see data, but it has stopped
 * Have you hit your monthly quota of data points? Open Settings/Quota and Pricing to find out. If so, you can upgrade your plan, or pay for additional capacity. See the [pricing scheme](https://azure.microsoft.com/pricing/details/application-insights/).
 * Have you recently upgraded your SDK? Please ensure that only Unique SDK jars are present inside the project directory. There should not be two different versions of SDK present.
diff --git a/articles/azure-monitor/app/java-standalone-config.md b/articles/azure-monitor/app/java-standalone-config.md
@@ -15,6 +15,8 @@ ms.custom: devx-track-java
 > Please review all the configuration options below carefully, as the json structure has completely changed,
 > in addition to the file name itself which went all lowercase.
 
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+
 ## Connection string and role name
 
 Connection string and role name are the most common settings needed to get started:
diff --git a/articles/azure-monitor/app/java-standalone-upgrade-from-2x.md b/articles/azure-monitor/app/java-standalone-upgrade-from-2x.md
@@ -20,6 +20,8 @@ that was pointing to the 2.x agent.
 The rest of this document describes limitations and changes that you may encounter
 when upgrading from 2.x to 3.x, as well as some workarounds that you may find helpful.
 
+
+
 ## TelemetryInitializers and TelemetryProcessors
 
 The 2.x SDK TelemetryInitializers and TelemetryProcessors will not be run when using the 3.x agent.
@@ -31,6 +33,8 @@ or configuring [telemetry processors](./java-standalone-telemetry-processors.md)
 
 This use case is supported in Application Insights Java 3.x using [Instrumentation keys overrides (preview)](./java-standalone-config.md#instrumentation-keys-overrides-preview).
 
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+
 ## Operation names
 
 In the Application Insights Java 2.x SDK, in some cases, the operation names contained the full path, e.g.
diff --git a/articles/azure-monitor/app/javascript-click-analytics-plugin.md b/articles/azure-monitor/app/javascript-click-analytics-plugin.md
@@ -13,6 +13,8 @@ ms.devlang: javascript
 
 This plugin automatically tracks click events on web pages and uses data-* attributes on HTML elements to populate event telemetry.
 
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+
 ## Getting started
 
 Users can set up the Click Analytics Auto-collection plugin via npm.
diff --git a/articles/azure-monitor/app/javascript-sdk-load-failure.md b/articles/azure-monitor/app/javascript-sdk-load-failure.md
@@ -100,6 +100,8 @@ If there are exceptions being reported in the SDK script (for example ai.2.min.j
 
 To check for faulty configuration, change the configuration passed into the snippet (if not already) so that it only includes your instrumentation key as a string value.
 
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+
 ```js
 src: "https://js.monitor.azure.com/scripts/b/ai.2.min.js",
 cfg: {
diff --git a/articles/azure-monitor/app/javascript.md b/articles/azure-monitor/app/javascript.md
@@ -13,6 +13,8 @@ Find out about the performance and usage of your web page or app. If you add [Ap
 
 Application Insights can be used with any web pages - you just add a short piece of JavaScript. If your web service is [Java](java-in-process-agent.md) or [ASP.NET](asp-net.md), you can use the server-side SDKs with the client-side JavaScript SDK to get an end-to-end understanding of your app's performance.
 
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+
 ## Adding the JavaScript SDK
 
 > [!IMPORTANT]
diff --git a/articles/azure-monitor/app/live-stream.md b/articles/azure-monitor/app/live-stream.md
@@ -42,6 +42,8 @@ Live Metrics are currently supported for ASP.NET, ASP.NET Core, Azure Functions,
 
 3. [Secure the control channel](#secure-the-control-channel) if you might use sensitive data such as customer names in your filters.
 
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+
 ### Enable LiveMetrics using code for any .NET application
 
 Even though LiveMetrics is enabled by default when onboarding using recommended instructions for .NET Applications, the following shows how to setup Live Metrics
diff --git a/articles/azure-monitor/app/mobile-center-quickstart.md b/articles/azure-monitor/app/mobile-center-quickstart.md
@@ -29,6 +29,8 @@ To complete this tutorial, you need:
  
 If you don't have an Azure subscription, create a [free](https://azure.microsoft.com/free/) account before you begin.
 
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+
 ## Sign up with App Center
 To begin, create an account and [sign up with App Center](https://appcenter.ms/signup?utm_source=ApplicationInsights&utm_medium=Azure&utm_campaign=docs).
 
diff --git a/articles/azure-monitor/app/monitor-functions.md b/articles/azure-monitor/app/monitor-functions.md
@@ -13,6 +13,8 @@ Application Insights collects log, performance, and error data, and automaticall
 
 The required Application Insights instrumentation is built into Azure Functions. The only thing you need is a valid instrumentation key to connect your function app to an Application Insights resource. The instrumentation key should be added to your application settings when your function app resource is created in Azure. If your function app doesn't already have this key, you can set it manually. For more information read more about [monitoring Azure Functions](../../azure-functions/functions-monitoring.md?tabs=cmd).
 
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+
 ## Distributed tracing for Java applications (public preview)
 
 > [!IMPORTANT]
diff --git a/articles/azure-monitor/app/nodejs.md b/articles/azure-monitor/app/nodejs.md
@@ -36,6 +36,8 @@ Before you begin, make sure that you have an Azure subscription, or [get a new o
 1. Sign in to the [Azure portal][portal].
 2. [Create an Application Insights resource](create-new-resource.md)
 
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+
 ### <a name="sdk"></a> Set up the Node.js client library
 
 Include the SDK in your app, so it can gather data.
diff --git a/articles/azure-monitor/app/opencensus-python.md b/articles/azure-monitor/app/opencensus-python.md
@@ -27,6 +27,8 @@ You may have noted that OpenCensus is converging into [OpenTelemetry](https://op
 - Python installation. This article uses [Python 3.7.0](https://www.python.org/downloads/release/python-370/), although other versions will likely work with minor changes. The Opencensus Python SDK only supports Python v2.7 and v3.4+.
 - Create an Application Insights [resource](./create-new-resource.md). You'll be assigned your own instrumentation key (ikey) for your resource.
 
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+
 ## Introducing Opencensus Python SDK
 
 [OpenCensus](https://opencensus.io) is a set of open source libraries to allow collection of distributed tracing, metrics and logging telemetry. Through the use of [Azure Monitor exporters](https://github.com/census-instrumentation/opencensus-python/tree/master/contrib/opencensus-ext-azure), you will be able to send this collected telemetry to Application insights. This article walks you through the process of setting up OpenCensus and Azure Monitor Exporters for Python to send your monitoring data to Azure Monitor.
diff --git a/articles/azure-monitor/app/powershell.md b/articles/azure-monitor/app/powershell.md
@@ -225,6 +225,8 @@ Additional properties are available via the cmdlets:
 
 Refer to the [detailed documentation](/powershell/module/az.applicationinsights) for the parameters for these cmdlets.  
 
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+
 ## Set the data retention
 
 Below are three methods to programmatically set the data retention on an Application Insights resource.
diff --git a/articles/azure-monitor/app/pricing.md b/articles/azure-monitor/app/pricing.md
@@ -211,6 +211,8 @@ The volume of data you send can be managed using the following techniques:
     
 * **Throttling**: Throttling limits the data rate to 32,000 events per second, averaged over 1 minute per instrumentation key. The volume of data that your app sends is assessed every minute. If it exceeds the per-second rate averaged over the minute, the server refuses some requests. The SDK buffers the data and then tries to resend it. It spreads out a surge over several minutes. If your app consistently sends data at more than the throttling rate, some data will be dropped. (The ASP.NET, Java, and JavaScript SDKs try to resend data this way; other SDKs might drop throttled data.) If throttling occurs, a notification warning alerts you that this has occurred.
 
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+
 ## Manage your maximum daily data volume
 
 You can use the daily volume cap to limit the data collected. However, if the cap is met, a loss of all telemetry sent from your application for the remainder of the day occurs. It *isn't advisable* to have your application hit the daily cap. You can't track the health and performance of your application after it reaches the daily cap.
diff --git a/articles/azure-monitor/app/profiler-cloudservice.md b/articles/azure-monitor/app/profiler-cloudservice.md
@@ -61,6 +61,8 @@ Application Insights Profiler is installed with the Azure Diagnostics extension.
     > After the Visual Studio 15.5 Azure SDK release, only the instrumentation keys that are used by the application and the ApplicationInsightsProfiler sink need to match each other.
 
 1. Deploy your service with the new Diagnostics configuration, and Application Insights Profiler is configured to run on your service.
+
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
  
 ## Next steps
 
diff --git a/articles/azure-monitor/app/profiler-servicefabric.md b/articles/azure-monitor/app/profiler-servicefabric.md
@@ -53,3 +53,5 @@ To set up your environment, take the following actions:
 * Generate traffic to your application (for example, launch an [availability test](monitor-web-app-availability.md)). Then, wait 10 to 15 minutes for traces to start to be sent to the Application Insights instance.
 * See [Profiler traces](profiler-overview.md?toc=/azure/azure-monitor/toc.json) in the Azure portal.
 * For help with troubleshooting Profiler issues, see [Profiler troubleshooting](profiler-troubleshooting.md?toc=/azure/azure-monitor/toc.json).
+
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
diff --git a/articles/azure-monitor/app/profiler-trackrequests.md b/articles/azure-monitor/app/profiler-trackrequests.md
@@ -13,6 +13,8 @@ To view profiles for your application on the Performance page, Azure Application
 
 For other applications, such as Azure Cloud Services worker roles and Service Fabric stateless APIs, you need to write code to tell Application Insights where your requests begin and end. After you've written this code, requests telemetry is sent to Application Insights. You can view the telemetry on the Performance page, and profiles are collected for those requests. 
 
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+
 To manually track requests, do the following:
 
   1. Early in the application lifetime, add the following code:  
diff --git a/articles/azure-monitor/app/sampling.md b/articles/azure-monitor/app/sampling.md
@@ -404,6 +404,7 @@ Insert a line like `samplingPercentage: 10,` before the instrumentation key:
     appInsights.trackPageView(); 
 </script>
 ```
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
 
 For the sampling percentage, choose a percentage that is close to 100/N where N is an integer. Currently sampling doesn't support other values.
 
diff --git a/articles/azure-monitor/app/sdk-connection-string.md b/articles/azure-monitor/app/sdk-connection-string.md
@@ -21,6 +21,8 @@ The key value pairs provide an easy way for users to define a prefix suffix comb
 > [!TIP]
 > We recommend the use of connection strings over instrumentation keys.
 
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+
 ## Scenario overview 
 
 Customer scenarios where we visualize this having the most impact:
diff --git a/articles/azure-monitor/app/separate-resources.md b/articles/azure-monitor/app/separate-resources.md
@@ -11,6 +11,8 @@ When you are developing the next version of a web application, you don't want to
 
 (If your system is an Azure Cloud Service, there's [another method of setting separate ikeys](../../azure-monitor/app/cloudservices.md).)
 
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+
 ## About resources and instrumentation keys
 
 When you set up Application Insights monitoring for your web app, you create an Application Insights *resource* in Microsoft Azure. You open this resource in the Azure portal in order to see and analyze the telemetry collected from your app. The resource is identified by an *instrumentation key* (ikey). When you install the Application Insights package to monitor your app, you configure it with the instrumentation key, so that it knows where to send the telemetry.
diff --git a/articles/azure-monitor/app/sharepoint.md b/articles/azure-monitor/app/sharepoint.md
@@ -66,6 +66,8 @@ Add the code just before the </head> tag.
 
 ![Screenshot that shows where to add the code to your site page.](./media/sharepoint/04-code.png)
 
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+
 #### Or on individual pages
 To monitor a limited set of pages, add the script separately to each page. 
 
diff --git a/articles/azure-monitor/app/snapshot-collector-release-notes.md b/articles/azure-monitor/app/snapshot-collector-release-notes.md
@@ -13,6 +13,8 @@ This article contains the releases notes for the Microsoft.ApplicationInsights.S
 
 For bug reports and feedback, open an issue on GitHub at https://github.com/microsoft/ApplicationInsights-SnapshotCollector
 
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+
 ## Release notes
 
 ## [1.4.2](https://www.nuget.org/packages/Microsoft.ApplicationInsights.SnapshotCollector/1.4.2)
diff --git a/articles/azure-monitor/app/snapshot-debugger-troubleshoot.md b/articles/azure-monitor/app/snapshot-debugger-troubleshoot.md
@@ -72,6 +72,8 @@ If that doesn't solve the problem, then refer to the following manual troublesho
 
 Make sure you're using the correct instrumentation key in your published application. Usually, the instrumentation key is read from the ApplicationInsights.config file. Verify the value is the same as the instrumentation key for the Application Insights resource that you see in the portal.
 
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+
 ## <a id="SSL"></a>Check TLS/SSL client settings (ASP.NET)
 
 If you have an ASP.NET application that it is hosted in Azure App Service or in IIS on a virtual machine, your application could fail to connect to the Snapshot Debugger service due to a missing SSL security protocol.
diff --git a/articles/azure-monitor/app/snapshot-debugger-vm.md b/articles/azure-monitor/app/snapshot-debugger-vm.md
diff --git a/articles/azure-monitor/app/statsbeat.md b/articles/azure-monitor/app/statsbeat.md
diff --git a/articles/azure-monitor/app/status-monitor-v2-api-reference.md b/articles/azure-monitor/app/status-monitor-v2-api-reference.md
diff --git a/articles/azure-monitor/app/status-monitor-v2-detailed-instructions.md b/articles/azure-monitor/app/status-monitor-v2-detailed-instructions.md
diff --git a/articles/azure-monitor/app/transaction-diagnostics.md b/articles/azure-monitor/app/transaction-diagnostics.md
diff --git a/articles/azure-monitor/app/usage-overview.md b/articles/azure-monitor/app/usage-overview.md
diff --git a/articles/azure-monitor/app/visual-studio.md b/articles/azure-monitor/app/visual-studio.md
diff --git a/articles/azure-monitor/app/windows-desktop.md b/articles/azure-monitor/app/windows-desktop.md
diff --git a/articles/azure-monitor/app/worker-service.md b/articles/azure-monitor/app/worker-service.md

Original file line number	Diff line number	Diff line change
`@@ -16,6 +16,8 @@ Want to keep your telemetry for longer than the standard retention period? Or pr`
`16`	`16`	`> Continuous export is only supported for classic Application Insights resources. [Workspace-based Application Insights resources](./create-workspace-resource.md) must use [diagnostic settings](./create-workspace-resource.md#export-telemetry).`
`17`	`17`	`>`
`18`	`18`
	`19`	`+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]`
	`20`	`+`
`19`	`21`	`Before you set up continuous export, there are some alternatives you might want to consider:`
`20`	`22`
`21`	`23`	`* The Export button at the top of a metrics or search tab lets you transfer tables and charts to an Excel spreadsheet.`