Edit

Migrate from MMA custom text log to AMA DCR based custom text logs

  • Article

This article describes the steps to migrate a MMA Custom text log table so you can use it as a destination for a new AMA custom text logs DCR. When you follow the steps, you won't lose any data. If you're creating a new AMA custom text log table, then this article doesn't pertain to you.

Background

MMA custom text logs must be configured to support new features in order for AMA custom text log DCRs to write to it. The following actions are taken:

  • The table is reconfigured to enable all DCR-based custom logs features.
  • All MMA custom fields stop updating in the table. AMA can write data to any column in the table.
  • The MMA Custom text log can write to noncustom fields, but it will not be able to create new columns. The portal table management UI can be used to change the schema after migration.

Migration procedure

You should follow the steps only if the following criteria are true:

  1. Configure your data collection rule (DCR) following procedures at collect text logs with Azure Monitor Agent
  2. Issue the following API call against your existing custom logs table to enable ingestion from Data Collection Rule and manage your table from the portal UI. This call is idempotent and future calls have no effect. Migration is one-way, you can't migrate the table back to MMA.

POST
https://management.azure.com/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.OperationalInsights/workspaces/{workspaceName}/tables/{tableName}/migrate?api-version=2021-12-01-preview
  1. Discontinue MMA custom text log collection and start using the AMA custom text log. MMA and AMA can both write to the table as you migrate your agents from MMA to AMA.

Next steps