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
Copy file name to clipboardExpand all lines: articles/azure-monitor/essentials/data-collection-rule-create-edit.md
-4Lines changed: 0 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -294,10 +294,6 @@ resource association 'Microsoft.Insights/dataCollectionRuleAssociations@2021-09-
294
294
```
295
295
---
296
296
297
-
The following tutorials include examples of manually creating DCRs.
298
-
299
-
-[Send data to Azure Monitor using Logs ingestion API (Resource Manager templates)](../logs/tutorial-logs-ingestion-api.md)
300
-
-[Add transformation in workspace data collection rule to Azure Monitor using Resource Manager templates](../logs/tutorial-workspace-transformations-api.md)
301
297
302
298
## Edit a DCR
303
299
To edit a DCR, you can use any of the methods described in the previous section to create a DCR using a modified version of the JSON.
Copy file name to clipboardExpand all lines: articles/azure-monitor/logs/logs-ingestion-api-overview.md
+65-65Lines changed: 65 additions & 65 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Logs Ingestion API in Azure Monitor
3
3
description: Send data to a Log Analytics workspace using REST API or client libraries.
4
4
ms.topic: conceptual
5
-
ms.date: 11/15/2023
5
+
ms.date: 03/23/2024
6
6
7
7
---
8
8
@@ -17,70 +17,6 @@ The data sent by your application to the API must be formatted in JSON and match
17
17
18
18
:::image type="content" source="../essentials/media/data-collection-rule-overview/overview-log-ingestion-api.png" lightbox="../essentials/media/data-collection-rule-overview/overview-log-ingestion-api.png" alt-text="Diagram that shows an overview of logs ingestion API." border="false":::
19
19
20
-
21
-
## Supported tables
22
-
23
-
Data sent to the ingestion API can be sent to the following tables:
24
-
25
-
| Tables | Description |
26
-
|:---|:---|
27
-
| Custom tables | Any custom table that you create in your Log Analytics workspace. The target table must exist before you can send data to it. Custom tables must have the `_CL` suffix. |
28
-
| Azure tables | The following Azure tables are currently supported. Other tables may be added to this list as support for them is implemented.<br><br>
> Column names must start with a letter and can consist of up to 45 alphanumeric characters and underscores (`_`). `_ResourceId`, `id`, `_ResourceId`, `_SubscriptionId`, `TenantId`, `Type`, `UniqueId`, and `Title` are reserved column names. Custom columns you add to an Azure table must have the suffix `_CF`.
83
-
84
20
## Configuration
85
21
The following table describes each component in Azure that you must configure before you can use the Logs Ingestion API.
86
22
@@ -171,6 +107,70 @@ Ensure that the request body is properly encoded in UTF-8 to prevent any issues
171
107
172
108
See [Sample code to send data to Azure Monitor using Logs ingestion API](tutorial-logs-ingestion-code.md?tabs=powershell#sample-code) for an example of the API call using PowerShell.
173
109
110
+
111
+
## Supported tables
112
+
113
+
Data sent to the ingestion API can be sent to the following tables:
114
+
115
+
| Tables | Description |
116
+
|:---|:---|
117
+
| Custom tables | Any custom table that you create in your Log Analytics workspace. The target table must exist before you can send data to it. Custom tables must have the `_CL` suffix. |
118
+
| Azure tables | The following Azure tables are currently supported. Other tables may be added to this list as support for them is implemented.<br><br>
> Column names must start with a letter and can consist of up to 45 alphanumeric characters and underscores (`_`). `_ResourceId`, `id`, `_ResourceId`, `_SubscriptionId`, `TenantId`, `Type`, `UniqueId`, and `Title` are reserved column names. Custom columns you add to an Azure table must have the suffix `_CF`.
173
+
174
174
## Limits and restrictions
175
175
176
176
For limits related to the Logs Ingestion API, see [Azure Monitor service limits](../service-limits.md#logs-ingestion-api).
0 commit comments