Getting Data In

Monitor Splunk Indexer OS Logs - Port Conflicts?

aferone
Builder

I want to monitor /var/log on all of my Splunk Indexers. However, when I configured this, I was then getting issues connecting to my Heavy Forwarders. I configured an outputs.conf to send the logs to the Heavy Forwarders, then back to the Indexers. This probably doesn't sound right.

How would this be accomplished?

Thanks!

P.S. How would I monitor the /var/log on my Heavy Forwards, Search Heads, etc?

0 Karma
1 Solution

aferone
Builder

I think I have it working by not specifying any outputs.conf on the Indexers.

View solution in original post

0 Karma

aferone
Builder

I think I have it working by not specifying any outputs.conf on the Indexers.

0 Karma

aferone
Builder

I think I have it working by not specifying any outputs.conf on the Indexers.

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!

Where Innovation Takes Flight: The Splunk4Aviation Flight Sim Lands at .conf26

If you hear someone at .conf26 shouting "gear down, GEAR DOWN" across the show floor, you have found us.  The ...

Turn Cisco Telemetry Into Action with Cisco Data Fabric, powered by the Splunk ...

The surge in machine data is already hitting enterprise budgets, and the agentic era will only intensify it. ...

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