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!

Quantify Your Splunk Investment Impact: Introducing Savings Metrics to Value Insights

Building on the foundation established in our initial Value Insights releases, we are introducing the Savings ...

Event Series: Telemetry Pipeline Management

Balancing Scale and Spend: Gaining Control Over High-Volume Metrics in Splunk Observability Cloud As ...

Kick the Tires Before You Commit: A Hands-On Tour of the Splunk Observability Cloud ...

Evaluating an enterprise observability platform usually goes like this: fill out a form, get a free trial with ...