Skip to content

Commit 8845716

Browse files
authored
Merge pull request #190205 from bwren/custom-log-migrate
custom logs migration
2 parents 3426298 + f836fe6 commit 8845716

File tree

2 files changed

+52
-0
lines changed

2 files changed

+52
-0
lines changed
Lines changed: 50 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
---
2+
title: Migrate from Data Collector API and custom fields-enabled tables to DCR-based custom logs
3+
description: Steps that you must perform when migrating from Data Collector API and custom fields-enabled tables to DCR-based custom logs.
4+
ms.topic: conceptual
5+
ms.date: 01/06/2022
6+
7+
---
8+
9+
# Migrate from Data Collector API and custom fields-enabled tables to DCR-based custom logs
10+
This article describes how to migrate from [Data Collector API](data-collector-api.md) or [custom fields](custom-fields.md) in Azure Monitor to [DCR-based custom logs](custom-logs-overview.md). It includes configuration required for tables in your Log Analytics workspace and applies to both [direct ingestion](custom-logs-overview.md) and [ingestion-time transformations](ingestion-time-transformations.md).
11+
12+
> [!IMPORTANT]
13+
> You do not need to follow this article if you are defining your DCR-based custom logs using the Azure Portal. This article only applies if you are using Resource Manager templates and the custom logs API.
14+
15+
## Background
16+
To use a table with the [direct ingestion](custom-logs-overview.md), and [ingestion-time transformations](ingestion-time-transformations.md), it must be configured to support these new features. When you complete the process described in this article, the following actions are taken:
17+
18+
- The table will be reconfigured to enable all DCR-based custom logs features. This includes DCR and DCE support and management with the new Tables control plane.
19+
- Any previously defined custom fields will stop populating.
20+
- The Data Collector API will continue to work but won't create any new columns. Data will only populate into any columns that was created prior to migration.
21+
- The schema and historic data is preserved and can be accessed the same way it was previously.
22+
23+
## Applicable scenarios
24+
This article is only applicable if all of the following criteria apply:
25+
26+
- You need to use the DCR-based custom logs functionality to send data to an existing table, preserving both schema and historical data in that table.
27+
- The table in question was either created using the Data Collector API, or has custom fields defined in it
28+
- You want to migrate using the custom logs API instead of the Azure portal.
29+
30+
If all of these conditions aren't true, then you can use DCR-based custom logs without following the procedure described here.
31+
32+
## Migration procedure
33+
If the table that you're targeting with DCR-based custom logs does indeed falls under the criteria described above, the following strategy is required for a graceful migration:
34+
35+
1. Configure your data collection rule (DCR) following procedures at [Send custom logs to Azure Monitor Logs using Resource Manager templates (preview)](tutorial-custom-logs-api.md) or [Add ingestion-time transformation to Azure Monitor Logs using Resource Manager templates (preview)](tutorial-ingestion-time-transformations-api.md).
36+
37+
1. If using the DCR-based API, also [configure the data collection endpoint (DCE)](tutorial-custom-logs-api.md#create-data-collection-endpoint) and the agent or component that will be sending data to the API.
38+
39+
1. Issue the following API call against your table. This call is idempotent, so there will be no effect if the table has already been migrated.
40+
41+
```rest
42+
POST /subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/microsoft.operationalinsights/workspaces/{workspaceName}/tables/{tableName}/migrate?api-version=2021-03-01-privatepreview
43+
```
44+
45+
1. Discontinue use of the Data Collector API and start using the new custom logs API.
46+
47+
## Next steps
48+
49+
- [Walk through a tutorial sending custom logs using the Azure portal.](tutorial-custom-logs.md)
50+
- [Walk through a tutorial sending custom logs using Resource Manager templates and REST API.](tutorial-custom-logs-api.md)

articles/azure-monitor/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -435,6 +435,8 @@ items:
435435
href: logs/tutorial-custom-logs.md
436436
- name: Tutorial (API)
437437
href: logs/tutorial-custom-logs-api.md
438+
- name: Migrate from Data Collector API
439+
href: logs/custom-logs-migrate.md
438440
- name: Data collector API
439441
items:
440442
- name: Overview

0 commit comments

Comments
 (0)