You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-When use the Azure portal to create a data collection rule for collecting text logs, Azure Monitor automatically creates a destination table in your Log Analytics workspace. When you create a data collection rule using the API, you must first [create a custom table](../logs/create-custom-table.md#create-a-custom-table) to send your logs to.
20
+
-[Custom table](../logs/create-custom-table.md) to send your logs to.
21
21
-[Permissions to create Data Collection Rule objects](../essentials/data-collection-rule-overview.md#permissions) in the workspace.
22
22
- A machine that write logs to a text file.
23
23
@@ -42,10 +42,11 @@ To create the data collection rule in the Azure portal:
42
42
43
43
[](media/data-collection-rule-azure-monitor-agent/data-collection-rules-updated.png#lightbox)
44
44
45
-
1. Enter a **Rule name** and specify a **Subscription**, **Resource Group**, **Region**, and **Platform Type**:
45
+
1. Enter a **Rule name** and specify a **Subscription**, **Resource Group**, **Region**, **Platform Type**, and **Data Collection Endpoint**:
46
46
47
47
-**Region** specifies where the DCR will be created. The virtual machines and their associations can be in any subscription or resource group in the tenant.
48
48
-**Platform Type** specifies the type of resources this rule can apply to. The **Custom** option allows for both Windows and Linux types.
49
+
-**Data Collection Endpoint** is required to collect custom logs.
49
50
50
51
[](media/data-collection-rule-azure-monitor-agent/data-collection-rule-basics-updated.png#lightbox)
51
52
@@ -80,8 +81,7 @@ To create the data collection rule in the Azure portal:
80
81
> Multiple log files of the same type commonly exist in the same directory. For example, a machine might create a new file every day to prevent the log file from growing too large. To collect log data in this scenario, you can use a file wildcard. Use the format `C:\directoryA\directoryB\*MyLog.txt` for Windows and `/var/*.log` for Linux. There is no support for directory wildcards.
81
82
82
83
83
-
-**Table name** - The name of the destination table you created in your Log Analytics Workspace. For more information, see [Prerequisites](#prerequisites).
84
-
84
+
-**Table name** - The name of the destination table you created in your Log Analytics Workspace. For more information, see [Prerequisites](#prerequisites).
85
85
-**Record delimiter** - Will be used in the future to allow delimiters other than the currently supported end of line (`/r/n`).
86
86
-**Transform** - Add an [ingestion-time transformation](../essentials/data-collection-transformations.md) or leave as **source** if you don't need to transform the collected data.
87
87
@@ -278,6 +278,7 @@ To create the data collection rule in the Azure portal:
278
278
:::image type="content" source="media/data-collection-text-log/select-resources.png" lightbox="media/data-collection-text-log/select-resources.png" alt-text="Screenshot that shows the Resources pane in the portal to add resources to the data collection rule.":::
279
279
280
280
---
281
+
281
282
## Troubleshoot
282
283
Use the following steps to troubleshoot collection of text logs.
0 commit comments