How to import/ingest a custom windows eventlog with AMA agent.

Jeroen van der Broek 25 Reputation points
2023-06-21T15:21:18.2933333+00:00

Hello,

I want to add a non default windows eventlog to get ingested in log analytic workspace trough the AMA agent. WIth the old MMA agent this was easy. But now i can not get it to work.

The event log is located under:

Applications and Services Logs\Microsoft\AzureADPasswordProtection\DCAgent\Admin

20

I made a data collection rule and tried under data source several Xpaths. Like for example:

Microsoft-AzureADPasswordProtection-DCAgent/Admin!*[System[(EventID=10014) )]]

2

Hope someone has any idea what i am missing here. Google does not show much and chatGPT only knows the MMA agent :P

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,635 questions
Microsoft Sentinel
Microsoft Sentinel
A scalable, cloud-native solution for security information event management and security orchestration automated response. Previously known as Azure Sentinel.
1,294 questions
0 comments No comments
{count} votes

Accepted answer
  1. AnuragSingh-MSFT 21,546 Reputation points Moderator
    2023-06-22T07:11:40.94+00:00

    @Jeroen van der Broek , thank you for the question.

    The steps that you are using are correct, however the following are some key areas where you should reverify that everything is setup properly:

    1. From the machine where you are collecting events, ensure that it is sending regular heartbeat to the target LA workspace (to ensure that there are no connectivity or other configuration issues). You can check this from the heartbeat table in the LA Workspace. Sample queries are available here - Sample Queries
    2. Ensure that the DCR is configured properly with Data Collection Endpoint in place for the machine, as shown in the doc here
    3. In your screenshot, I see that you have used filter operator as >=. When specifying range in local event viewer, the Path set contains the > character instead of ">" in XML format. However, this needs to be changed to ">" symbol for it to work.

    As available in the same doc, you can check the query using the Get-WinEvent PowerShell cmdlet to make sure that the query used is correct. See the output below:

    User's image

    Hope this helps.

    If the answer did not help, please add more context/follow-up question for it, and we will help you out. Else, if the answer helped, please click Accept answer so that it can help others in the community looking for help on similar topics.

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

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.