Skip to content

Commit 990a895

Browse files
Merge pull request #228857 from guywi-ms/patch-46
Update create-custom-table.md
2 parents 763a3e5 + 1351e11 commit 990a895

File tree

2 files changed

+10
-5
lines changed

2 files changed

+10
-5
lines changed

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

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -33,6 +33,7 @@ To create a custom table, you need:
3333
```
3434

3535
For information about the `TimeGenerated` format, see [supported datetime formats](/azure/data-explorer/kusto/query/scalar-data-types/datetime#supported-formats).
36+
3637
## Create a custom table
3738

3839
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.
@@ -181,6 +182,10 @@ To delete a table using PowerShell:
181182
## Add or delete a custom column
182183

183184
You can modify the schema of custom tables and add custom columns to, or delete columns from, a standard table.
185+
186+
> [!NOTE]
187+
> Column names must start with a letter and can consist of up to 45 alphanumeric characters and the characters `_` and `-`. The following are reserved column names: `Type`, `TenantId`, `resource`, `resourceid`, `resourcename`, `resourcetype`, `subscriptionid`, `tenanted`.
188+
184189
# [Portal](#tab/azure-portal-3)
185190

186191
To add a custom column to a table in your Log Analytics workspace, or delete a column:

articles/azure-monitor/logs/logs-ingestion-api-overview.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.date: 06/27/2022
88

99
# Logs Ingestion API in Azure Monitor
1010

11-
The Logs Ingestion API in Azure Monitor lets you send data to a Log Analytics workspace from any REST API client. By using this API, you can send data from almost any source to [supported built-in tables](#supported-tables) or to custom tables that you create. You can even extend the schema of built-in tables with custom columns.
11+
The Logs Ingestion API in Azure Monitor lets you send data to a Log Analytics workspace from any REST API client. By using this API, you can send data from almost any source to [supported Azure tables](#supported-tables) or to [custom tables that you create](../logs/create-custom-table.md#create-a-custom-table). You can even [extend the schema of Azure tables with custom columns](../logs/create-custom-table.md#add-or-delete-a-custom-column).
1212

1313
> [!NOTE]
1414
> The Logs Ingestion API was previously referred to as the custom logs API.
@@ -32,19 +32,19 @@ You can modify the target table and workspace by modifying the DCR without any c
3232

3333
### Custom tables
3434

35-
The Logs Ingestion API can send data to any custom table that you create and to certain built-in tables in your Log Analytics workspace. The target table must exist before you can send data to it. Custom tables must have the `_CL` suffix.
35+
The Logs Ingestion API can send data to any custom table that you create and to certain Azure tables in your Log Analytics workspace. The target table must exist before you can send data to it. Custom tables must have the `_CL` suffix.
3636

37-
### Built-in tables
37+
### Azure tables
3838

39-
The Logs Ingestion API can send data to the following built-in tables. Other tables may be added to this list as support for them is implemented. Columns extended on top of built-in tables must have the suffix `_CF`. Columns in a custom table don't need this suffix.
39+
The Logs Ingestion API can send data to the following Azure tables. Other tables may be added to this list as support for them is implemented.
4040

4141
- [CommonSecurityLog](/azure/azure-monitor/reference/tables/commonsecuritylog)
4242
- [SecurityEvents](/azure/azure-monitor/reference/tables/securityevent)
4343
- [Syslog](/azure/azure-monitor/reference/tables/syslog)
4444
- [WindowsEvents](/azure/azure-monitor/reference/tables/windowsevent)
4545

4646
> [!NOTE]
47-
> Column names can consist of alphanumeric characters and the characters `_` and `-`, and they must start with a letter.
47+
> Column names must start with a letter and can consist of up to 45 alphanumeric characters and the characters `_` and `-`. The following are reserved column names: `Type`, `TenantId`, `resource`, `resourceid`, `resourcename`, `resourcetype`, `subscriptionid`, `tenanted`. Custom columns you add to an Azure table must have the suffix `_CF`.
4848
4949
## Authentication
5050

0 commit comments

Comments
 (0)