Getting Data In

is there a problem with logs that end in the date?

Path Finder

I have a log structure like so:

/opt/data/logs/tomcat/foo or /opt/data/logs/tomcat/bar

the logs themselves are something like log1.out.2012-05-01, etc.

I've tried several monitor stanzas like:

whitelist: foo\.out\.*



but nothing is picking up these logs...

Tags (2)
0 Karma

Splunk Employee
Splunk Employee

The monitor path looks good.

Are your file starting with the same first lines ?
Maybe is it the crc calculation on the first 256 chars causing the logs file to be considered as identical.
A workaround for this is to add crcSalt in inputs.conf, see

If there is no timestamp in the events, maybe the timestamp is extracted from the filename, please search over all time for source=myfile

Finally to check what the tailing processor is saying, use the REST API

Path Finder

the rest API was great, that provided good clues.. had to do with overlapping monitor stanzas. in old environment, server had separate folders, move to new one, I changed all monitor stanzas to the same folder, but apparently only one whitelist applied!

Changed to a (x.log|y.log) etc, whitelist and one stanza...

0 Karma

Path Finder

I think web mangled... I had the "." characters escaped, btw

0 Karma
Get Updates on the Splunk Community!

There's No Place Like Chrome and the Splunk Platform

Watch On DemandMalware. Risky Extensions. Data Exfiltration. End-users are increasingly reliant on browsers to ...

The Great Resilience Quest: 5th Leaderboard Update

The fifth leaderboard update for The Great Resilience Quest is out >> 🏆 Check out the ...

Devesh Logendran, Splunk, and the Singapore Cyber Conquest

At this year’s Splunk University, I had the privilege of chatting with Devesh Logendran, one of the winners in ...