DCR Transformation Not Affecting Data Ingested via Azure Monitor Agent

SwathiDhanwada-MSFT 18,776 Reputation points
2024-08-01T06:19:49.5166667+00:00

Why is my DCR transformation at the table level in Log Analytics workspace not affecting the data ingested via the Azure Monitor Agent into the CommonSecurityLog table?

PS - Based on common issues that we have seen from customers and other sources, we are posting these questions to help the Azure community.

Azure Monitor
Azure Monitor
An Azure service that is used to collect, analyze, and act on telemetry data from Azure and on-premises environments.
3,327 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. SwathiDhanwada-MSFT 18,776 Reputation points
    2024-08-01T06:20:11.53+00:00

    When you apply a Data Collection Rule (DCR) transformation at the table level within your Log Analytics workspace, this method does not impact logs collected via the Azure Monitor Agent (AMA). This table-level transformation method supports logs collected through other methods such as Diagnostic Settings or the legacy Microsoft Monitoring Agent (MMA) or OMS agent. To correctly apply transformations to data being ingested via the Azure Monitor Agent, you need to modify the DCR at the DCR level.

    Here are the steps to resolve this issue:

    1. Go to the Data Collection Rule (DCR) that is configured to ingest the logs.
    2. Modify the DCR to apply the required transformation directly within the DCR.

    Here is a video tutorial to guide through this process: YouTube Video Tutorial.

    For further details, refer to the following resources:

    Please do not forget to "up-vote" wherever the information provided helps you, as this can be beneficial to other community members.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.