Getting Data In

Auditbeat add-one does not sourcetype log

sigma
Path Finder

Hi all,

I recently installed this add-one on my cluster (hfs, idxs, shs). I copied props.conf and transforms.conf into local directory and uncomment the mappings to sourcetype elastic:auditbeat:log. But this action had no effect and yet I just see one sourcetype: elastic:auditbeat:log

any ideas are appreciated.
Thanks.

Tags (2)
0 Karma

richgalloway
SplunkTrust
SplunkTrust

What exactly did you change and what were the expected results?

The comments in transforms.conf and props.conf must not be un-commented because they are not valid settings.

---
If this reply helps you, Karma would be appreciated.
0 Karma

sigma
Path Finder

Thank you. Yes I was wrong about transforms.conf

actually I wan to generate sourcetype from elastic:auditbeat:log based on events as This link has specified.

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