Splunk Search

Why is the Null Queue Not Working?

jordanking1992
Path Finder

Hello,

Here is a sample log event I would like to filter:

20180307 11:11:08.795 [process:flow] [INFO] Thread is returning to available thread pool DM.Appl.ThreadPool

Here is current props.conf
[source::/opt/CA/tracelog.txt]
TRANSFORMS-null= setnull

Here is current transforms.conf
[setnull]
REGEX = (?i)[INFO]
DEST_KEY = queue
FORMAT = nullQueue

I would like to send all events that contain [INFO] to null queue but the current configurations on the indexer do not seem to be working. Any thoughts on what might be wrong?

Thanks!

0 Karma
1 Solution

gcusello
SplunkTrust
SplunkTrust

hI jordanking1992,
square parenthesis is a special char for regexes so you have to escape them, try

REGEX = (?i)\[INFO\]

Bye.
Giuseppe

View solution in original post

gcusello
SplunkTrust
SplunkTrust

hI jordanking1992,
square parenthesis is a special char for regexes so you have to escape them, try

REGEX = (?i)\[INFO\]

Bye.
Giuseppe

king2jd
Path Finder

Giuseppe,

Thank you so much. Cant believe it was something so simple.

Respectfully,
Jordan

0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi hI jordanking1992,
if you're satisfied by this answer please accept and/or upvote it.
Bye.
Giuseppe

0 Karma
Get Updates on the Splunk Community!

Splunkers, Pack Your Bags: Why Cisco Live EMEA is Your Next Big Destination

The Power of Two: Splunk + Cisco at "Ludicrous Scale"   You know Splunk. You know Cisco. But have you seen ...

Data Management Digest – January 2026

Welcome to the January 2026 edition of Data Management Digest! Welcome to the January 2026 edition of Data ...

Splunk SOAR Now Available on Google Cloud Platform

We’re excited to announce that Splunk SOAR is now natively available as a SaaS solution on Google Cloud ...