All Apps and Add-ons

Linux AuditD - Missing inputs.conf?

nhertzberg
New Member

I was installing the Linux AuditD app and the TA on my Splunk instance and my forwarders installed on RHEL 7 systems when I noticed that there's no inputs.conf file in either the app or the TA. How are my indexers supposed to get and use any data from the systems without the forwarders sending the data over? Am I just supposed to make one myself?

I had a look at the video guide for version v2 (something like 6 years ago), and that one seems to have an inputs.conf file, unlike the current version v3.

Labels (1)
0 Karma

isoutamo
SplunkTrust
SplunkTrust

Hi

with quick look, this TA/app didn't contains any inputs at all. This is just for presenting auditd events on SH and also do needed filed extractions on SH/Indexer/HF. See https://github.com/doksu/splunk_auditd/wiki/Installation-and-Configuration

To get events from clients you should use e.g. your own TA with inputs or use e.g. Splunk Add-on for Unix and Linux https://splunkbase.splunk.com/app/833 to collect those from UFs

r. Ismo

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!

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