Getting Data In

How to ingest files with multiple dots in them

nls7010
Path Finder

I am trying to upload documents from a user who's log files has multiple dots in the naming convention:

The logs have a *.0.1.log in its file extension, would it be possible to use *.*.*.log instead?

The logs have a *-20210218.000023-5644-5716.0.log in its file extension, would it be possible to use *.*.*.*.log instead?

The logs have a *-20201218.105324-11260-11240.0.log in its file extension, would it be possible to use *.*.*.log instead?

The logs have a *-20210209.145105-16220-11864.0.log in its file extension, would it be possible to use *.*.*.log instead?

The logs have a *-20201218.105324-25876-14744.0.log in its file extension, would it be possible to use *.*.*.log instead?

 

Is there a way to get all of these from .log to .*.*.*.log into Splunk using one monitoring stanza?

Labels (2)
0 Karma

scelikok
SplunkTrust
SplunkTrust

Hi @nls7010,

Since monitor stanza supports regex you can try something below;

[monitor:///path/to/log/.*\-\d{8}\.\d+-\d+-\d+|.*\.\d\.log]
If this reply helps you an upvote and "Accept as Solution" is appreciated.
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!

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...

Laser Bananas and Edge Hubs: Exploring Operational Technology (OT) Data Through a ...

  OT is a different environment to traditional IT and can have interesting challenges when interfacing the ...

Event Series: Mastering AI Tokenomics and Splunk Agent Observability

Beyond the Black Box: Correlating AI Performance and Tokenomics with Splunk Agent Observability   As ...