Splunk Search

DHCP and Proxy Search - Join Performance Issues

michaeldeck
Engager

I have a working search using join that correlates DHCP addresses by machine name to find web proxy traffic as the device changes IP addresses. Join is quite slow though. Is there a way to do a faster search that provides similar results with something like stats or eventstats instead of join?

index=proxy | join ip  usetime=true earlier=true [ search index=dhcp dest_hostname="computername"| rename dest as ip]
0 Karma
1 Solution

woodcock
Esteemed Legend

This should do it:

index=proxy [ search index=dhcp dest_hostname="computername"| stats values(dest) AS ip ]

View solution in original post

0 Karma

woodcock
Esteemed Legend

This should do it:

index=proxy [ search index=dhcp dest_hostname="computername"| stats values(dest) AS ip ]
0 Karma

woodcock
Esteemed Legend

Try this:

index=proxy OR (index=dhcp dest_hostname="computername"
| eval ip=coalesce(ip, dest)
| fields - dest
| stats list(*) AS * BY ip
0 Karma

michaeldeck
Engager

When I attempted to run this, it seems to return every proxy event sorted by IP instead of just the ones relative to IPs just used by "computername".

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!

From Data to Insight: Announcing the Winners of the Splunk Dashboard Contest

Hi Splunkers, First off, thank you to everyone who participated in our very first From Data to Insight: The ...

Splunk Developers: Construct Your Future at the .conf26 Builder Bar

Calling all Splunk architects, platform admins, and app developers: the site is open, and the blueprints are ...

Quick connection discovery mode for forwarders

When a Splunk forwarder loses connectivity to its indexers, it does not always reconnect immediately. In many ...