Merge pull request #111641 from mrbullwinkle/mrb_04_16_2020_retire_classic_metrics

retire classic metrics

Author: tfosmark

.openpublishing.redirection.json

@@ -51119,6 +51119,11 @@
       "source_path": "articles/azure-monitor/insights/key-vault-insights-overview.md",
       "redirect_url": "/azure/azure-monitor/overview",
       "redirect_document_id": false
+    },
+	{
+      "source_path": "articles/azure-monitor/app/metrics-explorer.md",
+      "redirect_url": "/azure/azure-monitor/platform/metrics-charts",
+      "redirect_document_id": false
     },
     {
       "source_path": "articles/security/fundamentals/database-best-practices.md",

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

@@ -103,7 +103,7 @@ In Node.js projects, you can use `new applicationInsights.TelemetryClient(instru
 
 ## TrackEvent
 
-In Application Insights, a *custom event* is a data point that you can display in [Metrics Explorer](../../azure-monitor/app/metrics-explorer.md) as an aggregated count, and in [Diagnostic Search](../../azure-monitor/app/diagnostic-search.md) as individual occurrences. (It isn't related to MVC or other framework "events.")
+In Application Insights, a *custom event* is a data point that you can display in [Metrics Explorer](../../azure-monitor/platform/metrics-charts.md) as an aggregated count, and in [Diagnostic Search](../../azure-monitor/app/diagnostic-search.md) as individual occurrences. (It isn't related to MVC or other framework "events.")
 
 Insert `TrackEvent` calls in your code to count various events. How often users choose a particular feature, how often they achieve particular goals, or maybe how often they make particular types of mistakes.
 
@@ -441,7 +441,7 @@ requests
 
 Send exceptions to Application Insights:
 
-* To [count them](../../azure-monitor/app/metrics-explorer.md), as an indication of the frequency of a problem.
+* To [count them](../../azure-monitor/platform/metrics-charts.md), as an indication of the frequency of a problem.
 * To [examine individual occurrences](../../azure-monitor/app/diagnostic-search.md).
 
 The reports include the stack traces.
@@ -772,7 +772,7 @@ If your app groups users into accounts, you can also pass an identifier for the
 appInsights.setAuthenticatedUserContext(validatedId, accountId);
 ```
 
-In [Metrics Explorer](../../azure-monitor/app/metrics-explorer.md), you can create a chart that counts **Users, Authenticated**, and **User accounts**.
+In [Metrics Explorer](../../azure-monitor/platform/metrics-charts.md), you can create a chart that counts **Users, Authenticated**, and **User accounts**.
 
 You can also [search](../../azure-monitor/app/diagnostic-search.md) for client data points with specific user names and accounts.
 

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

@@ -50,7 +50,7 @@ There are plenty of ways to explore your data. Check out these articles:
 | [**Profiler**](../../azure-monitor/app/profiler.md)<br/>Inspect the execution profiles of sampled requests. |![Profiler](./media/app-insights-overview/profiler.png) |
 | [**Usage analysis**](../../azure-monitor/app/usage-overview.md)<br/>Analyze user segmentation and retention.|![Retention tool](./media/app-insights-overview/retention.png) |
 | [**Diagnostic search for instance data**](../../azure-monitor/app/diagnostic-search.md)<br/>Search and filter events such as requests, exceptions, dependency calls, log traces, and page views.  |![Search telemetry](./media/app-insights-overview/search-tn.png) |
-| [**Metrics Explorer for aggregated data**](../../azure-monitor/app/metrics-explorer.md)<br/>Explore, filter, and segment aggregated data such as rates of requests, failures, and exceptions; response times, page load times. |![Metrics](./media/app-insights-overview/metrics-tn.png) |
+| [**Metrics Explorer for aggregated data**](../../azure-monitor/platform/metrics-charts.md)<br/>Explore, filter, and segment aggregated data such as rates of requests, failures, and exceptions; response times, page load times. |![Metrics](./media/app-insights-overview/metrics-tn.png) |
 | [**Dashboards**](../../azure-monitor/app/overview-dashboard.md)<br/>Mash up data from multiple resources and share with others. Great for multi-component applications, and for continuous display in the team room. |![Dashboards sample](./media/app-insights-overview/dashboard-tn.png) |
 | [**Live Metrics Stream**](../../azure-monitor/app/live-stream.md)<br/>When you deploy a new build, watch these near-real-time performance indicators to make sure everything works as expected. |![Live metrics sample](./media/app-insights-overview/live-metrics-tn.png) |
 | [**Analytics**](../../azure-monitor/app/analytics.md)<br/>Answer tough questions about your app's performance and usage by using this powerful query language. |![Analytics sample](./media/app-insights-overview/analytics-tn.png) |

articles/azure-monitor/app/asp-net.md

@@ -89,7 +89,7 @@ The portal opens on a view of the telemetry from your app.
 In the portal, click any tile or chart to see more detail.
 
 ## Step 4: Publish your app
-Publish your app to your IIS server or to Azure. Watch [Live Metrics Stream](../../azure-monitor/app/metrics-explorer.md#live-metrics-stream) to make sure everything is running smoothly.
+Publish your app to your IIS server or to Azure. Watch [Live Metrics Stream](../../azure-monitor/app/live-stream.md) to make sure everything is running smoothly.
 
 Your telemetry builds up in the Application Insights portal, where you can monitor metrics, search your telemetry. You can also use the powerful [Kusto query language](/azure/kusto/query/) to analyze usage and performance, or to find specific events.
 

articles/azure-monitor/app/cloudservices.md

@@ -27,7 +27,7 @@ This option instruments your app at runtime, giving you all the telemetry that y
 
 If this option is all you need, you're done. 
 
-Your next steps are [viewing metrics from your app](../../azure-monitor/app/metrics-explorer.md), [querying your data with Analytics](../../azure-monitor/app/analytics.md). 
+Your next steps are [viewing metrics from your app](../../azure-monitor/platform/metrics-charts.md), [querying your data with Analytics](../../azure-monitor/app/analytics.md). 
 
 To monitor performance in the browser, you might also want to set up [availability tests](../../azure-monitor/app/monitor-web-app-availability.md) and [add code to your webpages](../../azure-monitor/app/javascript.md).
 
@@ -161,7 +161,7 @@ This step is only needed if you want to capture full SQL queries on .NET Framewo
 
 1. Open the Application Insights resources that you created.
 
-   Individual data points are displayed in [Search][diagnostic], and aggregated data is displayed in [Metric Explorer](../../azure-monitor/app/metrics-explorer.md).
+   Individual data points are displayed in [Search][diagnostic], and aggregated data is displayed in [Metric Explorer](../../azure-monitor/platform/metrics-charts.md).
 
 1. Add more telemetry (see the next sections) and then publish your app to get live diagnostics and usage feedback. 
 
@@ -180,7 +180,7 @@ You can find the [Azure Diagnostics](https://docs.microsoft.com/azure/monitoring
 * Windows event logs are shown as traces and custom events.
 * Application logs, ETW logs, and any diagnostics infrastructure logs appear as traces.
 
-To view performance counters and counts of events, open [Metrics Explorer](../../azure-monitor/app/metrics-explorer.md) and add the following chart:
+To view performance counters and counts of events, open [Metrics Explorer](../../azure-monitor/platform/metrics-charts.md) and add the following chart:
 
 ![Azure Diagnostics data](./media/cloudservices/23-wad.png)
 

articles/azure-monitor/app/code-sample-export-sql-stream-analytics.md

@@ -57,7 +57,7 @@ Continuous export always outputs data to an Azure Storage account, so you need t
     ![Choose event types](./media/code-sample-export-sql-stream-analytics/085-types.png)
 
 
-1. Let some data accumulate. Sit back and let people use your application for a while. Telemetry will come in and you'll see statistical charts in [metric explorer](../../azure-monitor/app/metrics-explorer.md) and individual events in [diagnostic search](../../azure-monitor/app/diagnostic-search.md). 
+1. Let some data accumulate. Sit back and let people use your application for a while. Telemetry will come in and you'll see statistical charts in [metric explorer](../../azure-monitor/platform/metrics-charts.md) and individual events in [diagnostic search](../../azure-monitor/app/diagnostic-search.md). 
 
     And also, the data will export to your storage. 
 2. Inspect the exported data, either in the portal - choose **Browse**, select your storage account, and then **Containers** - or in Visual Studio. In Visual Studio, choose **View / Cloud Explorer**, and open Azure / Storage. (If you don't have this menu option, you need to install the Azure SDK: Open the New Project dialog and open Visual C# / Cloud / Get Microsoft Azure SDK for .NET.)
@@ -236,7 +236,7 @@ After a few minutes, go back to SQL Server Management Tools and watch the data f
 
 
 ## Related articles
-* [Export to PowerBI using Stream Analytics](../../azure-monitor/app/export-power-bi.md )
+* [Export to Power BI using Stream Analytics](../../azure-monitor/app/export-power-bi.md )
 * [Detailed data model reference for the property types and values.](../../azure-monitor/app/export-data-model.md)
 * [Continuous Export in Application Insights](../../azure-monitor/app/export-telemetry.md)
 * [Application Insights](https://azure.microsoft.com/services/application-insights/)
@@ -245,7 +245,7 @@ After a few minutes, go back to SQL Server Management Tools and watch the data f
 
 [diagnostic]: ../../azure-monitor/app/diagnostic-search.md
 [export]: ../../azure-monitor/app/export-telemetry.md
-[metrics]: ../../azure-monitor/app/metrics-explorer.md
+[metrics]: ../../azure-monitor/platform/metrics-charts.md
 [portal]: https://portal.azure.com/
 [start]: ../../azure-monitor/app/app-insights-overview.md
 

articles/azure-monitor/app/configuration-with-applicationinsights-config.md

@@ -124,7 +124,7 @@ The standard initializers are all set either by the Web or WindowsServer NuGet p
 * `OperationNameTelemetryInitializer` updates the `Name` property of the `RequestTelemetry` and the `Name` property of the `Operation` context of all telemetry items based on the HTTP method, as well as names of ASP.NET MVC controller and action invoked to process the request.
 * `OperationIdTelemetryInitializer` or `OperationCorrelationTelemetryInitializer` updates the `Operation.Id` context property of all telemetry items tracked while handling a request with the automatically generated `RequestTelemetry.Id`.
 * `SessionTelemetryInitializer` updates the `Id` property of the `Session` context for all telemetry items with value extracted from the `ai_session` cookie generated by the ApplicationInsights JavaScript instrumentation code running in the user's browser.
-* `SyntheticTelemetryInitializer` or `SyntheticUserAgentTelemetryInitializer` updates the `User`, `Session`, and `Operation` contexts properties of all telemetry items tracked when handling a request from a synthetic source, such as an availability test or search engine bot. By default, [Metrics Explorer](../../azure-monitor/app/metrics-explorer.md) does not display synthetic telemetry.
+* `SyntheticTelemetryInitializer` or `SyntheticUserAgentTelemetryInitializer` updates the `User`, `Session`, and `Operation` contexts properties of all telemetry items tracked when handling a request from a synthetic source, such as an availability test or search engine bot. By default, [Metrics Explorer](../../azure-monitor/platform/metrics-charts.md) does not display synthetic telemetry.
 
     The `<Filters>` set identifying properties of the requests.
 * `UserTelemetryInitializer` updates the `Id` and `AcquisitionDate` properties of `User` context for all telemetry items with values extracted from the `ai_user` cookie generated by the Application Insights JavaScript instrumentation code running in the user's browser.

articles/azure-monitor/app/create-new-resource.md

@@ -149,12 +149,12 @@ For the full Azure CLI documentation for this command, and to learn how to retri
 
 ## Next steps
 * [Diagnostic Search](../../azure-monitor/app/diagnostic-search.md)
-* [Explore metrics](../../azure-monitor/app/metrics-explorer.md)
+* [Explore metrics](../../azure-monitor/platform/metrics-charts.md)
 * [Write Analytics queries](../../azure-monitor/app/analytics.md)
 
 <!--Link references-->
 
 [api]: ../../azure-monitor/app/api-custom-events-metrics.md
 [diagnostic]: ../../azure-monitor/app/diagnostic-search.md
-[metrics]: ../../azure-monitor/app/metrics-explorer.md
+[metrics]: ../../azure-monitor/platform/metrics-charts.md
 [start]: ../../azure-monitor/app/app-insights-overview.md

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

@@ -9,7 +9,7 @@ ms.date: 01/08/2019
 # Application Insights Export Data Model
 This table lists the properties of telemetry sent from the [Application Insights](../../azure-monitor/app/app-insights-overview.md) SDKs to the portal.
 You'll see these properties in data output from [Continuous Export](export-telemetry.md).
-They also appear in property filters in [Metric Explorer](../../azure-monitor/app/metrics-explorer.md) and [Diagnostic Search](../../azure-monitor/app/diagnostic-search.md).
+They also appear in property filters in [Metric Explorer](../../azure-monitor/platform/metrics-charts.md) and [Diagnostic Search](../../azure-monitor/app/diagnostic-search.md).
 
 Points to note:
 
@@ -123,16 +123,16 @@ All types of telemetry are accompanied by a context section. Not all of these fi
 | context.device.roleName |string | |
 | context.device.screenResolution |string | |
 | context.device.type |string |PC, Browser, ... |
-| context.location |object |Derived from clientip. |
-| context.location.city |string |Derived from clientip, if known |
+| context.location |object |Derived from `clientip`. |
+| context.location.city |string |Derived from `clientip`, if known |
 | context.location.clientip |string |Last octagon is anonymized to 0. |
 | context.location.continent |string | |
 | context.location.country |string | |
 | context.location.province |string |State or province |
-| context.operation.id |string |Items that have the same operation id are shown as Related Items in the portal. Usually the request id. |
+| context.operation.id |string |Items that have the same `operation id` are shown as Related Items in the portal. Usually the `request id`. |
 | context.operation.name |string |url or request name |
 | context.operation.parentId |string |Allows nested related items. |
-| context.session.id |string |Id of a group of operations from the same source. A period of 30 minutes without an operation signals the end of a session. |
+| context.session.id |string |`Id` of a group of operations from the same source. A period of 30 minutes without an operation signals the end of a session. |
 | context.session.isFirst |boolean | |
 | context.user.accountAcquisitionDate |string | |
 | context.user.accountId |string | |
@@ -143,7 +143,7 @@ All types of telemetry are accompanied by a context section. Not all of these fi
 | context.user.isAuthenticated |boolean | |
 | context.user.storeRegion |string | |
 | internal.data.documentVersion |string | |
-| internal.data.id |string | Unique id that is assigned when an item is ingested to Application Insights |
+| internal.data.id |string | `Unique id` that is assigned when an item is ingested to Application Insights |
 
 ## Events
 Custom events generated by [TrackEvent()](../../azure-monitor/app/api-custom-events-metrics.md#trackevent).
@@ -169,7 +169,7 @@ Reports [exceptions](../../azure-monitor/app/asp-net-exceptions.md) in the serve
 | basicException [0] failedUserCodeAssembly |string | |
 | basicException [0] handledAt |string | |
 | basicException [0] hasFullStack |boolean | |
-| basicException [0] id |string | |
+| basicException [0] `id` |string | |
 | basicException [0] method |string | |
 | basicException [0] message |string |Exception message. Max length 10k. |
 | basicException [0] outerExceptionMessage |string | |
@@ -206,7 +206,7 @@ Sent by TrackDependency. Used to report performance and usage of [calls to depen
 | remoteDependency [0] count |integer |100/([sampling](../../azure-monitor/app/sampling.md) rate). For example 4 => 25%. |
 | remoteDependency [0] dependencyTypeName |string |HTTP, SQL, ... |
 | remoteDependency [0] durationMetric.value |number |Time from call to completion of response by dependency |
-| remoteDependency [0] id |string | |
+| remoteDependency [0] `id` |string | |
 | remoteDependency [0] name |string |Url. Max length 250. |
 | remoteDependency [0] resultCode |string |from HTTP dependency |
 | remoteDependency [0] success |boolean | |
@@ -223,7 +223,7 @@ Sent by [TrackRequest](../../azure-monitor/app/api-custom-events-metrics.md#trac
 | --- | --- | --- |
 | request [0] count |integer |100/([sampling](../../azure-monitor/app/sampling.md) rate). For example: 4 => 25%. |
 | request [0] durationMetric.value |number |Time from request arriving to response. 1e7 == 1s |
-| request [0] id |string |Operation id |
+| request [0] `id` |string |`Operation id` |
 | request [0] name |string |GET/POST + url base.  Max length 250 |
 | request [0] responseCode |integer |HTTP response sent to client |
 | request [0] success |boolean |Default == (responseCode < 400) |

articles/azure-monitor/app/export-stream-analytics.md

@@ -51,7 +51,7 @@ Continuous export always outputs data to an Azure Storage account, so you need t
 
     ![Choose event types](./media/export-stream-analytics/080.png)
 
-1. Let some data accumulate. Sit back and let people use your application for a while. Telemetry will come in and you'll see statistical charts in [metric explorer](../../azure-monitor/app/metrics-explorer.md) and individual events in [diagnostic search](../../azure-monitor/app/diagnostic-search.md). 
+1. Let some data accumulate. Sit back and let people use your application for a while. Telemetry will come in and you'll see statistical charts in [metric explorer](../../azure-monitor/platform/metrics-charts.md) and individual events in [diagnostic search](../../azure-monitor/app/diagnostic-search.md). 
 
     And also, the data will export to your storage. 
 2. Inspect the exported data. In Visual Studio, choose **View / Cloud Explorer**, and open Azure / Storage. (If you don't have this menu option, you need to install the Azure SDK: Open the New Project dialog and open Visual C# / Cloud / Get Microsoft Azure SDK for .NET.)