Getting Data In

Problem with monitor configuration in inputs.conf

C_Sparn
Communicator

Hello,
I want to monitor rolling logfiles with extension x.log0 to x.log9.
The problem is, that I only can monitor the files when I monitor the parent directory of the log files. If I try to set the stanza like this: [monitor://tmp/logs/x.log*] nothing happens!
How can I monitor every single file from x.log0 to x.log9 without using the parent directory?
Thanks

1 Solution

grijhwani
Motivator

Your example stanza is missing a slash.

[monitor:///tmp/logs/x.log*]

You could try monitoring the directory, and only whitelisting the desired files, although I'm not sure whether that is a deprecated mechanism:

[monitor:///tmp/logs/]
whitelist = \.log[0-9]

(No guarantees this is exactly correct, but you get the idea. We use a similar mechanism which is the inverse - i.e. we blacklist what we don't want.)

blacklist = (\.gz$|sa/sar\d+|sa/sa\d+|tmp$|\.gz\.\d+$|\.tgz$|\.bz$|\.bz2$|\.old)

View solution in original post

grijhwani
Motivator

Your example stanza is missing a slash.

[monitor:///tmp/logs/x.log*]

You could try monitoring the directory, and only whitelisting the desired files, although I'm not sure whether that is a deprecated mechanism:

[monitor:///tmp/logs/]
whitelist = \.log[0-9]

(No guarantees this is exactly correct, but you get the idea. We use a similar mechanism which is the inverse - i.e. we blacklist what we don't want.)

blacklist = (\.gz$|sa/sar\d+|sa/sa\d+|tmp$|\.gz\.\d+$|\.tgz$|\.bz$|\.bz2$|\.old)

C_Sparn
Communicator

Hello,

the * in my stanza didnt show any effect in my case, but with whitelist everything is fine. Thanks!
Greetings

0 Karma
Get Updates on the Splunk Community!

Aligning Observability Costs with Business Value: Practical Strategies

 Join us for an engaging Tech Talk on Aligning Observability Costs with Business Value: Practical ...

Mastering Data Pipelines: Unlocking Value with Splunk

 In today's AI-driven world, organizations must balance the challenges of managing the explosion of data with ...

Splunk Up Your Game: Why It's Time to Embrace Python 3.9+ and OpenSSL 3.0

Did you know that for Splunk Enterprise 9.4, Python 3.9 is the default interpreter? This shift is not just a ...