Getting Data In

inputs.conf behaviour doesn't corespond with documentation

Christian
Path Finder

Hello all,

my direcotry structur :

/data/A/logs/aaaaaaa.log
/data/A/logs/aaaaaaa1.log
/data/B/logs/aaaaaaa.log
/data/B/logs/aaaaaaa1.log

my inputs.conf

[monitor:///data/*/logs]
sourcetype=mysourcetype
index=idx_myindex_dev
disabled=false

A) If I'am putting the Fullpath "for example /data/A/logs/" to the monitor field it works fine

B) If I try it with the inputs.conf above, he lists me only the directorys, but doesn't index any file. In the Splunkd.log he says Parsing configuration stanza: monitor:///data/*/logs. No error, no information.

According to the Documentation :
`The asterisk () matches anything in a single path segment;
unlike "...", it does not recurse. For example,
/foo/
/bar matches the files /foo/bar, /foo/1/bar, /foo/2/bar,
etc. However, it does not match /foo/1/2/bar.

wich is fine for me, anyway I tried it also with the ... witch would be also fine for me but that doesn't work either.

Q : Any Idea what I'am doing wrong ?

Universalforwarder : 4.2.3

OS : AIX 6.1

Documentation : http://docs.splunk.com/Documentation/Splunk/latest/Admin/inputsconf

Tags (2)
0 Karma
1 Solution

rroberts
Splunk Employee
Splunk Employee

rroberts
Splunk Employee
Splunk Employee

Christian
Path Finder

thx the refrence articel answers my qustion

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 ...

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...

Manage Edge Processor pipelines end to end with APIs

This guide uses the Data Management APIs to create an Edge Processor, onboard one instance, deploy a pipeline ...