Splunk Search

field::value vs field=value when doing search

htidore
Path Finder

I have a UF, Indexer, Search Head. My UF accepts UDP packets. I created a field in the UF so that I can identify that the packet go through this particular UF:

_meta = env=env1

I performed two searches:

env=env1
env::env1

The result is different.

What is the difference between field::value and field=value when we do search?
Thanks.

Tags (1)
0 Karma

knielsen
Contributor

If you had the meta field configured correctly on your search head, you should not see a difference.

:: is forcing to treat it as an indexed field, regardless of setting it up correctly in fields.conf. Btw, the syntax in your inputs.conf should also use :: instead of =, but maybe both is possible.

Have a look at this discussion: https://answers.splunk.com/answers/389567/why-is-a-search-for-fields-added-with-meta-in-inpu.html which I found when I was having issues with :: vs =.

Hth,
Kai.

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!

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

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...