Merge pull request #50227 from bwren/la-language-transition

Retire log search transition article

Author: rjagiewich

.openpublishing.redirection.json

@@ -9243,6 +9243,11 @@
             "redirect_url": "https://docs.microsoft.com/azure/log-analytics/log-analytics-quick-collect-azurevm",
             "redirect_document_id": false
         },
+        {
+            "source_path": "articles/log-analytics/log-analytics-log-search-transition.md",
+            "redirect_url": "https://docs.microsoft.com/azure/log-analytics/query-language/get-started-queries",
+            "redirect_document_id": false
+        },
         {
             "source_path": "articles/machine-learning/machine-learning-apps-text-analytics.md",
             "redirect_url": "/azure/cognitive-services/cognitive-services-text-analytics-quick-start",

articles/log-analytics/log-analytics-app-insights-connector.md

@@ -84,7 +84,6 @@ Click the **Application Insights** tile to open the **Application Insights** das
 
 The dashboard includes the blades shown in the table. Each blade lists up to 10 items matching that blade's criteria for the specified scope and time range. You can run a log search that returns all records when you click **See all** at the bottom of the blade or when you click the blade header.
 
-[!INCLUDE [log-analytics-log-search-nextgeneration](../../includes/log-analytics-log-search-nextgeneration.md)]
 
 | **Column** | **Description** |
 | --- | --- |

articles/log-analytics/log-analytics-log-search-transition.md

@@ -225,8 +225,6 @@ View the summarized compliance assessments for your infrastructure and then dril
 
 If you have recommendations that you want to ignore, you can create a text file that Log Analytics uses to prevent recommendations from appearing in your assessment results.
 
-[!INCLUDE[log-analytics-log-search-nextgeneration](../../includes/log-analytics-log-search-nextgeneration.md)]
-
 ### To identify recommendations that you want to ignore
 1. In the Azure portal on the Log Analytics workspace page for your selected workspace, click the **Log Search** menu item.
 2. Use the following query to list recommendations that have failed for computers in your environment.

articles/log-analytics/log-analytics-scom-assessment.md

@@ -77,8 +77,6 @@ Following the same steps above, input the necessary parameters, and kick off a d
 To view Perf Data from your nodes:
 
 
-[!INCLUDE [log-analytics-log-search-nextgeneration](../../includes/log-analytics-log-search-nextgeneration.md)]
-
 - Launch the Log Analytics workspace from the Azure portal.
   ![Service Fabric](./media/log-analytics-service-fabric/6.png)
 - Go to Settings on the left pane, and select Data >> Windows Performance Counters >> "Add the selected performance counters":

articles/log-analytics/log-analytics-service-fabric-azure-resource-manager.md

@@ -170,8 +170,6 @@ View the summarized compliance assessments for your infrastructure and then dril
 ## Ignore recommendations
 If you have recommendations that you want to ignore, you can create a text file that Log Analytics will use to prevent recommendations from appearing in your assessment results.
 
-[!INCLUDE[log-analytics-log-search-nextgeneration](../../includes/log-analytics-log-search-nextgeneration.md)]
-
 ### To identify recommendations that you will ignore
 1. In the Azure portal on the Log Analytics workspace page for your selected workspace, click the **Log Search** tile.
 2. Use the following query to list recommendations that have failed for computers in your environment.

articles/log-analytics/log-analytics-sql-assessment.md

@@ -149,8 +149,6 @@ If you want to see additional ESXi host VM creation data, click an ESXi host nam
 #### Common search queries
 The solution includes other useful queries that can help you manage your ESXi hosts, such as high storage space, storage latency, and path failure.
 
-[!INCLUDE[log-analytics-log-search-nextgeneration](../../includes/log-analytics-log-search-nextgeneration.md)]
-
 ![queries](./media/log-analytics-vmware/queries.png)
 
 

articles/log-analytics/log-analytics-vmware.md

@@ -383,8 +383,6 @@ In the **Overview** page for your Log Analytics workspace in the Azure portal, c
 | Local Subnets | Shows the number of local subnets that agents have discovered.  Click the number to run a log search for <code>Type:WireData &#124; Measure Sum(TotalBytes) by LocalSubnet</code> that lists all subnets with the number of bytes sent over each one. Click a subnet in the list to run a log search returning the total number of bytes sent over the subnet. |
 | Application-level Protocols | Shows the number of application-level protocols in use, as discovered by agents. Click the number to run a log search for <code>Type:WireData &#124; Measure Sum(TotalBytes) by ApplicationProtocol</code>. Click a protocol to run a log search returning the total number of bytes sent using the protocol. |
 
-[!INCLUDE[log-analytics-log-search-nextgeneration](../../includes/log-analytics-log-search-nextgeneration.md)]
-
 ![Wire Data dashboard](./media/log-analytics-wire-data/wire-data-dash.png)
 
 You can use the **Agents capturing network traffic** blade to determine how much network bandwidth is being consumed by computers. This blade can help you easily find the _chattiest_ computer in your environment. Such computers could be overloaded, acting abnormally, or using more network resources than normal.

articles/log-analytics/log-analytics-wire-data.md

@@ -117,8 +117,6 @@
     items:
     - name: Language documentation
       items:
-      - name: Transition from legacy language
-        href: log-analytics-log-search-transition.md
       - name: Language reference
         href: https://docs.loganalytics.io
       - name: Get started