Splunk Search

Compare 2 fields

mcafeesecure
Explorer

Basically I have a line of data that looks like this:

Jun 28 14:15:10 sc4-app04.mcafeesecure.com portal: ACCESS Click Referrer[bluecigs.com][http://www.blucigs.com/privacy-policy]

I have rex set up to extract two parts of this:

rex "(?i) Referrer\\[(?P<REF1>[^\\]]*)(?=\\])" | rex "(?i)www\.(?P<REF2>[^/]*)(?=/)" 

This will basically give me 2 fields I can search on REF1 and REF2.

I would like only messages that do NOT have those two fields matching to show up for instance, in the previous entry I get

REF1=bluecigs.com
REF2=bluecigs.com

the following line I would have them NOT matching:

Jun 28 14:15:10 sc4-app04.mcafeesecure.com portal: ACCESS Click Referrer[bluecigs.com][http://www.SOMEOTHERDOMAIN.com/]

IE: REF1=bluecigs.com
REF2=SOMEOTHERDOMAIN.com

Is there a way to compare the fields?

Tags (2)

ziegfried
Influencer

You can do this by using the where command:

<your search> | where REF1!=REF2

bfaber
Communicator

I would imagine you could add this to the end of your search

| search NOT REF1=REF2

but that may also give you events where REF1 and REF2 don't exist.

Try it out and let us know!

0 Karma

ziegfried
Influencer

This won't work. It would compare the value of the field REF1 with the value "REF2" (ie. not the value of field REF2).

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!

Where Innovation Takes Flight: The Splunk4Aviation Flight Sim Lands at .conf26

If you hear someone at .conf26 shouting "gear down, GEAR DOWN" across the show floor, you have found us.  The ...

Turn Cisco Telemetry Into Action with Cisco Data Fabric, powered by the Splunk ...

The surge in machine data is already hitting enterprise budgets, and the agentic era will only intensify it. ...

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