Getting Data In

Configuring splunk forwarder. Have duplicate usernames over multiple linux hosts. How to identify unique source?

stu6000
New Member

I am pulling data from several linux hosts, each host has several users, and i am collecting data from each users llog folder.

host1:
/opt/ABC/log/logfile1
/opt/ABCDEV/log/logfile1

host2:
/opt/ABC/log/logfile1
/opt/ABCLIVE/log/logfile1

This is my config from \Client panel\Dynamic Options:

index=ABC sourcetype=host Logon | dedup source | rex field=source "\/.ABC(?.)\/lo.*" |eval Client=replace(Client,"\d","") | sort auto

Command used to add file to monitor on each host:

/opt/splunkforwarder/bin/splunk add monitor /opt//log/logfile1 -index ABC -sourcetype HOST

The issue is that within Splunk home page, I have HOST , CLIENT
However due to the generic username of 'ABC' on host1 & host2 it is resulting in only one entry for 'Client\source', so im missing a source for host2 ABC user.

Ie:

/opt/ABC/log/logfile1
/opt/ABCDEV/log/logfile1
/opt/ABCLIVE/log/logfile1

Is there a way that i can configure splunk in order to be able to identify the 'generic' user?

Tags (2)
0 Karma

esix_splunk
Splunk Employee
Splunk Employee

Your dedup is removing all the duplicated sources if I understand this correctly.

Why not use the host field for these sources? That will be unique... So do something similar as..

index=ABC sourcetype=host Logon | rex field=source "/opt\/(?P<Client>w+))\/" |stats count by host, Client 

Your host field will be unique to each event. You can extract the Client name from the path and then do a dedup or stats count on it.. That will give you a unique count of events by host and by Client (username/ path on disk..)

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!

Vibe-coding, AI, and Splunkcraft: Highlights from the .conf26 Builder Bar

If you stopped by the Builder Bar at .conf26, thank you! This year, we brought ...

Thanks for the Memories: .conf26 Took Learning to New Heights

Thank you, Splunk Community, for making .conf26 in Denver one for the books. From packed Splunk University ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...