All Apps and Add-ons

TA-microsoft-sysmon bugged extraction User_as_user

mhessel
Path Finder

After figuring out what was going on, I figured I would feed this back up.

The current package has a bug in the extraction User_as_user.  The REPORT pointing to the extraction cannot work, as all of the transforms have to be lower case.  As a result, this REPORT in props doesn't work, and the resulting user field is essentially returning the same thing as if there was a FIELDALIAS instead linking User to user, including any "domain name\username" format.

Props.conf has:

REPORT-user_for_sysmon = User_as_user

and in Transforms.conf

[User_as_user]
SOURCE_KEY = User
REGEX = (?:[^\\]+\\)?(.+)
FORMAT = user::"$1"

To fix this, change User_as_user --> user_as_user in both places:

Props.conf:

REPORT-user_for_sysmon = user_as_user

and in Transforms.conf

[user_as_user]
SOURCE_KEY = User
REGEX = (?:[^\\]+\\)?(.+)
FORMAT = user::"$1"

Labels (1)
Tags (2)
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Observability Simplified: Combining User Experience, Application Performance & ...

Tech Talk Observability Simplified: Combining User Experience, Application Performance & Network ...

Event Series May & June: From Network Visibility to Service Intelligence

Unifying the Network: Moving from Alert Noise to Service Intelligence with Splunk ITSI In today’s hybrid ...

Global Splunk User Group Events: May + June 2026

Your Splunk Community Awaits: Discover Upcoming User Group Events Worldwide    Staying ahead in the fast-paced ...