Getting Data In

Cannot filter WMI events to nullQueue in 4.2.x

Ellen
Splunk Employee
Splunk Employee

I am sending some events to the nullQueue and it used to work in 4.0.x and 4.1.x, but now it is not sending any events to nullQueue. I have the following configuration:

props.conf
[wmi] 
TRANSFORMS-nuke=wmi2nullQ

transforms.conf 
[wmi2nullQ] 
REGEX=(?im)(CategoryString=Logoff)[^$]+\s+(EventIdentifier=4634)
DEST_KEY = queue
FORMAT = nullQueue

Why does this no longer work? Nothing has changed since applying a newer 4.2.x release.

Tags (2)
1 Solution

Ellen
Splunk Employee
Splunk Employee

In 4.0.x and 4.1.x the stanza in props.conf had to be [wmi]

With 4.2.x you must use the actual sourcetype name.

For example:

[WMI:WinEventLog:Security]

TRANSFORMS-send2nullq= wmi2nullQ

View solution in original post

Ellen
Splunk Employee
Splunk Employee

In 4.0.x and 4.1.x the stanza in props.conf had to be [wmi]

With 4.2.x you must use the actual sourcetype name.

For example:

[WMI:WinEventLog:Security]

TRANSFORMS-send2nullq= wmi2nullQ

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!

Splunk Add-on for Microsoft Windows 11.0.3: Parse Once, Search Faster

The updated Splunk Add-on for Microsoft Windows helps customers search Windows events faster by reducing ...

What's New in Splunk Enterprise Security 8.8 and Beyond

Threats move at machine speed. Keeping up should not depend on having the biggest budget, the largest team, or ...

A Four-Part Event Series: State of Observability - Where AI Meets Performance

As AI agents take on more complex tasks, teams need greater visibility into how they behave, what they cost, ...