Skip to content

Commit 9b202a7

Browse files
committed
delay warning
1 parent f4f8639 commit 9b202a7

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

articles/azure-monitor/logs/custom-fields.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -11,11 +11,10 @@ ms.date: 03/31/2023
1111

1212
# Create custom fields in a Log Analytics workspace in Azure Monitor (Preview)
1313

14-
> [!NOTE]
15-
> Creation of new custom fields will be disabled starting March 31, 2023. Custom fields functionality will be deprecated, and existing custom fields will stop functioning by March 31, 2026. You should [migrate to ingestion-time transformations](custom-fields-migrate.md) to keep parsing your log records.
16-
1714
> [!IMPORTANT]
18-
> Custom fields increases the amount of data collected in the Log Analytics workspace which can increase your cost. See [Azure Monitor Logs pricing details](cost-logs.md) for details.
15+
> Creation of new custom fields will be disabled starting March 31, 2023. Custom fields functionality will be deprecated, and existing custom fields will stop functioning by March 31, 2026. You should [migrate to ingestion-time transformations](custom-fields-migrate.md) to keep parsing your log records.
16+
>
17+
> Currently, when you add a new custom field, it may take up to 7 days before data starts appearing.
1918
2019
The **Custom Fields** feature of Azure Monitor allows you to extend existing records in your Log Analytics workspace by adding your own searchable fields. Custom fields are automatically populated from data extracted from other properties in the same record.
2120

0 commit comments

Comments
 (0)