Getting Data In

TCP_ROUTING Sub-folders of monitors fails

efo
Engager

Hi,
Monitoring subfolders of other monitors while using TCP_ROUTING results in subfolders not being indexed.
Do anyone of you have any experiences with this, or possible workarounds? 🙂

Removing the /var/log monitor will get data into to the customer01 and customer02 servers, so i know that the ROUTING is working.

Adding additional TCP_ROUTING to /var/log/ do not seem to help.

[monitor:///var/log/customer]
disabled=false
index=index1y
blacklist=.(gz|\d+)$
recursive=false
_TCP_ROUTING=customer01,customer02

[monitor:///var/log]
disabled = false
blacklist = (.(gz|bz2|z|zip)|lastlog|wtmp|btmp)$
followTail = 1
recursive = false

--
Best regards
Espen

0 Karma

elof
Path Finder

I guess you stumbled on the same "bug" as I did.
This was my workaround:
http://answers.splunk.com/answers/126064/bug-in-universal-forwarder-inputsconf-monitor-and-recursive...

0 Karma
Get Updates on the Splunk Community!

.conf24 | Registration Open!

Hello, hello! I come bearing good news: Registration for .conf24 is now open!   conf is Splunk’s rad annual ...

ICYMI - Check out the latest releases of Splunk Edge Processor

Splunk is pleased to announce the latest enhancements to Splunk Edge Processor.  HEC Receiver authorization ...

Introducing the 2024 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...