Getting Data In

Monitor Universal forwarder

ludoz13
Path Finder

Hello all,

I have somme issue with my universal forwarder and I would like to monitor the logs file of my forwader (metrics.log, splunkd.log, ...) from the indexer to see what's wrong.
Is there a way in a outputs.conf to forward this logs file to the indexer ? Or we need to put [monitor:///opt/splunk/var/log/splunk/metrics*] and [monitor:///opt/splunk/var/log/splunk/splunkd*] on the inputs.conf file.

Thanks a lot

LudoZ

Tags (1)
1 Solution

Mahieu
Communicator

Using the inputs.conf on the forwarder side sounds like a good option.
You should, push it to a specific index so that it doesn't fall into the main one.

View solution in original post

rkirkw
Path Finder

Make sure that you put index=_internal in your search if you are trying to query the splunkd.log files. I could not see mine even signed on as admin and starting the search with index="*"

0 Karma

Mahieu
Communicator

Using the inputs.conf on the forwarder side sounds like a good option.
You should, push it to a specific index so that it doesn't fall into the main one.

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

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...