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