Splunk Search

Filter syntax options in serverclass.conf

Peter
Path Finder

Is it possible to use regular expressions for the whitelist/blacklist filters in serverclass.conf? For example:

whitelist.0=mail[0-9]+.*

Tags (1)
1 Solution

gkanapathy
Splunk Employee
Splunk Employee

It is not possible currently (version 4.0). Only * as a wildcard for any character can be used.

View solution in original post

0 Karma

gkanapathy
Splunk Employee
Splunk Employee

It is not possible currently (version 4.0). Only * as a wildcard for any character can be used.

0 Karma

Jason
Motivator

If regex in these whitelists are anything like the regexp in stanza names, there was a bug in the docs. . means dot, * means anything but slash (meaning filenames only) and ... (three dots) means anything, your usual regex .*

0 Karma

Peter
Path Finder

I see that PCRE expressions have been added as of 4.1, but the mappings confuse me. My current serverclass.conf has name8., which mean to match name8.blah and name8.bleh. It would be easier for me to match name[0-9]+.., but the docs seem to indicate that '.' is converted to '.' and '' is converted to '.' Can you add clarity to this?

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!

Manage Edge Processor pipelines end to end with APIs

This guide uses the Data Management APIs to create an Edge Processor, onboard one instance, deploy a pipeline ...

Splunk Brings Proof of Control to Digital Asset Transfers

Digital assets now sit inside the core of financial services. HSBC launched its Tokenized Deposit Service in ...

Manage Ingest Processor pipelines end to end with APIs

This guide uses the Data Management APIs to create an Ingest Processor pipeline, deploy it to the ...