Merge pull request #236697 from guywi-ms/patch-55

Update data-sources-custom-logs.md

Author: prmerger-automator[bot]

articles/azure-monitor/agents/data-sources-custom-logs.md

@@ -2,10 +2,10 @@
 title: Collect text logs with the Log Analytics agent in Azure Monitor
 description: Azure Monitor can collect events from text files on both Windows and Linux computers. This article describes how to define a new custom log and details of the records they create in Azure Monitor.
 ms.topic: conceptual
-author: bwren
-ms.author: bwren
-ms.date: 02/07/2022
-ms.reviewer: shseth
+author: guywi-ms
+ms.author: guywild
+ms.date: 05/03/2023
+ms.reviewer: luki
 
 ---
 
@@ -43,18 +43,19 @@ A Log Analytics workspace supports the following limits:
 >[!IMPORTANT]
 >Custom log collection requires that the application writing the log file flushes the log content to the disk periodically. This is because the custom log collection relies on filesystem change notifications for the log file being tracked.
 
-## Define a custom log
+## Define a custom log table
 
-Use the following procedure to define a custom log file. Scroll to the end of this article for a walkthrough of a sample of adding a custom log.
+Use the following procedure to define a custom log table. Scroll to the end of this article for a walkthrough of a sample of adding a custom log.
 
 ### Open the Custom Log wizard
 
 The Custom Log wizard runs in the Azure portal and allows you to define a new custom log to collect.
 
-1. In the Azure portal, select **Log Analytics workspaces** > your workspace.
-1. Under the **Classic** section, select **Legacy custom logs**.
-1. By default, all configuration changes are automatically pushed to all agents. For Linux agents, a configuration file is sent to the Fluentd data collector.
-1. Select **Add** to open the Custom Log wizard.
+1. In the Azure portal, select **Log Analytics workspaces** > your workspace > **Tables**.
+1. Select **Create** and then **New custom log (MMA-based)**.
+
+    By default, all configuration changes are automatically pushed to all agents. For Linux agents, a configuration file is sent to the Fluentd data collector.
+
 
 ### Upload and parse a sample log
 
@@ -66,7 +67,9 @@ If a timestamp delimiter is used, the TimeGenerated property of each record stor
 
 1. Select **Browse** and browse to a sample file. This button might be labeled **Choose File** in some browsers.
 1. Select **Next**.
-1. The Custom Log wizard uploads the file and lists the records that it identifies.
+
+    The Custom Log wizard uploads the file and lists the records that it identifies.
+
 1. Change the delimiter that's used to identify a new record. Select the delimiter that best identifies the records in your log file.
 1. Select **Next**.
 
@@ -110,12 +113,9 @@ After Azure Monitor starts collecting from the custom log, its records will be a
 
 The entire log entry will be stored in a single property called **RawData**. You'll most likely want to separate the different pieces of information in each entry into individual properties for each record. For options on parsing **RawData** into multiple properties, see [Parse text data in Azure Monitor](../logs/parse-text.md).
 
-## Remove a custom log
-
-Use the following process in the Azure portal to remove a custom log that you previously defined.
+## Delete a custom log table
 
-1. On the left, under the **Classic** section for your workspace, select **Legacy custom Logs** to list all your custom logs.
-1. Select **Remove** next to the custom log to remove the log.
+See [Delete a table](../logs/create-custom-table.md#delete-a-table).
 
 ## Data collection
 

articles/azure-monitor/logs/create-custom-table.md

@@ -39,7 +39,7 @@ To create a custom table, you need:
 Azure tables have predefined schemas. To store log data in a different schema, use data collection rules to define how to collect, transform, and send the data to a custom table in your Log Analytics workspace.
 
 > [!NOTE]
-> For information about creating a custom table for logs you ingest with the deprecated Log Analytics agent, also known as MMA or OMS, see [Collect text logs with the Log Analytics agent](../agents/data-sources-custom-logs.md#define-a-custom-log).
+> For information about creating a custom table for logs you ingest with the deprecated Log Analytics agent, also known as MMA or OMS, see [Collect text logs with the Log Analytics agent](../agents/data-sources-custom-logs.md#define-a-custom-log-table).
 
 # [Portal](#tab/azure-portal-1)