Getting Data In

Help with regex on whitelist

a212830
Champion

Hi,

I need to whitelist on the following:

SIPServer-RTP-Routing1-PR-001.20171212_124642_595.log

Anything that has SIPServer, then anything, and then "-PR-001", following the timestamp and then .log.

My attempt... whitelist = SIPServer-???-Routing?-PR-001.*.log

0 Karma

Maverick904
Explorer

Can you please try below query and confirm if it fulfill your requirement.

1.   (?<FileName>SIPServer-.*?-Routing[a-zA-Z0-9]-PR-001.\d+_\d+_\d+.log)

mayurr98
Super Champion

hey @a212830,

Try this in inputs.conf, It will work 100%

[monitor://<mention path>]
whitelist = SIPServer-.*-PR-001\.\d+_\d+_\d+\.log

Let me know if it helps!

0 Karma

hardikJsheth
Motivator

If you want to consider both Routing and PR-001, you can use following regex:

SIPServer-\w*-Routing\d*-PR-001.[0-9_]+.log
0 Karma

wenthold
Communicator

This should work, but you may want to adjust it based upon the format of the timestamps you might see...

SIPServer.*?-PR-001\.[0-9]{8}_[0-9]{6}_[0-9]{3}\.log$

Less strict:

SIPServer.*?-PR-001\.[0-9_]+.log$
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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...