Getting Data In

How To Seperate WinEventLog events from two different domains

barne_dn
Explorer

Hey Everyone,

I currently have events coming in from two different domains. I'm doing various transforms on the indexer to route events that are not wanted/needed into the nullqueue.

Until now, everything has worked ok, but we're starting to bring in more machines and we need to log more events. Our current props.conf file has all of our transforms listed under one source:

[WinEventLog:Security]

TRANSFORMS-set=drop01,drop02,keep01,keep02...etc

Now that our needs are getting more complicated this setup is not working anymore. Our transforms have become too complicated so I'm going to have to find a way to seperate the events coming from each domain.

What would be the best way to do this?

I was hoping I could setup something like this:

[WinEventLog:Security:Domain01]
TRANSFORMS-set=drop01,keep01,...etc

[WinEventLog:Security:Domain02]
TRANSFORMS-set=drop02,keep02...etc

Thanks!

Kate_Lawrence-G
Contributor

if you are using FQDN and the hostnames are logical per domain you can do something with the SOURCE_KEY?

SOURCE_KEY = metadata:host 
REGEX = <something>
DEST_KEY = <something>
FORMAT = <something>
0 Karma
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!

Developer Spotlight with Denis Gladkikh

From Splunk Engineer to Kubernetes App Builder Denis GladkikhWhat happens when a lifelong developer turns a ...

Governing Enterprise AI, Bringing Cisco Telemetry Home, and More from Splunk Lantern

Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...