Getting Data In

How to develop a regular expression that will blacklist my log paths in inputs.conf?

ppanchal
Path Finder

Below is my monitoring path

[monitor:///wasapps/WAS85/logs/restconnect_alppapp102was85Node01]

I want to blacklist the below files

/wasapps/WAS85/logs/restconnect_alppapp102was85Node01/restConnectApp.log
/wasapps/WAS85/logs/restconnect_alppapp102was85Node01/restConnectPerformance.log

I have tried the below regex, but none of them worked.

[monitor:///wasapps/WAS85/logs/restconnect_alppapp102was85Node01]
blacklist = restConnect*\.(log)$
blacklist = restConnect[App|Performance]\.(log)$

Can someone please help?

0 Karma

ddrillic
Ultra Champion

Some cheerful examples in the documentation at Whitelist- or blacklist-specific incoming data

It shows -

![alt text][2]

0 Karma

ckunath
Communicator
blacklist = restConnect.*\.log$

This should blacklist every file that starts with "restConnect" and ends with .log

0 Karma

ppanchal
Path Finder

I guess this did not work.
Any other solution?

0 Karma

ckunath
Communicator

Oh, my bad. Try

blacklist = .*restConnect.*\.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 ...