Getting Data In

too many sources

gnovak
Builder

Hi,

I just noticed something today and have an idea of maybe how to fix it but figured i would toss it by here too.

In splunk on 2 servers I have in the inputs.conf the following to be monitored:

[monitor:///opt/drs/var/log]
disabled = false
sourcetype = drs7

the problem i have noticed is that in this directory logs are generated every day with a different name. The date is included in the name so what's happening is in splunk under Sources on the summary page there are tons of entries for each and every one of these logs, instead of 1 source just being /opt/drs/var/log.

2 examples of some of the logs are below:

/opt/drs/var/log/drs.me-20110131_1525.log
/opt/drs/var/log/drs.gi-20110222_1559.log

If I was to change the entry in the inputs.conf to say:

[monitor:///opt/drs/var/log/drs.*.log]
disabled = false
sourcetype = drs7

Would this eliminate every single log being listed as a source?

Tags (1)
0 Karma

Lowell
Super Champion

You may also want to take a look a the following question/answer:

If you want to consolidate all files in a directory as a single source then using the [monitor] stanza that has an explicit source= setting will work, but if you have different types of log files in a single directory, then I recommend using a transformer-based approach (as detailed in the link above).

0 Karma

dwest
Engager

Not sure if there's some reason not to do this versus ron's answer, but I have a monitor pointing to a directory and I simply have source=sourcename in the stanza in inputs.conf, which causes there to be only one source set.

inputs.conf:

[monitor://my_directory]
source=singlesourcename
sourcetype=mysourcetype

Ron_Naken
Splunk Employee
Splunk Employee

I removed mine, in lieu of this answer.

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!

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

span_metrics: The OpenTelemetry-Idiomatic Way to See Inside Your Services

You open a trace in Splunk Observability Cloud and everything looks fine. One root span, order-pipeline, with ...