Splunk Search

Why am I getting an error message when using Wildcard for file based lookup?

sylim_splunk
Splunk Employee
Splunk Employee

I'm trying to use WILDCARD for file based lookup and get an error message, "match_type is malformed" as below - According to the descriptions in UI page, I'm using WILDCARD(A*, B*,..) and get the error.

Optionally set up non-exact matching of a comma-and-space-delimited field list. Format is (, ,...). Available values for match_type are WILDCARD and CIDR.

alt text

0 Karma
1 Solution

sylim_splunk
Splunk Employee
Splunk Employee

This is a UI bug and will be corrected.
Correct way for match_type for multiple fields is like, WILDCARD(A*), WILDCARD(B*) as described in spec.

match_type =
A comma and space-delimited list of < match_type >(< field_name >)
specification to allow for non-exact matching
The available match_type values are WILDCARD, CIDR, and EXACT. EXACT is
the default and does not need to be specified. Only fields that should
use WILDCARD or CIDR matching should be specified in this list

View solution in original post

sylim_splunk
Splunk Employee
Splunk Employee

This is a UI bug and will be corrected.
Correct way for match_type for multiple fields is like, WILDCARD(A*), WILDCARD(B*) as described in spec.

match_type =
A comma and space-delimited list of < match_type >(< field_name >)
specification to allow for non-exact matching
The available match_type values are WILDCARD, CIDR, and EXACT. EXACT is
the default and does not need to be specified. Only fields that should
use WILDCARD or CIDR matching should be specified in this list

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!

A Four-Part Event Series: Full Stack Observability For the AI Era

As AI reshapes applications, infrastructure, and the way teams operate, the traditional boundaries of ...

SOC4Kafka - New Kafka Connector Powered by OpenTelemetry

The new SOC4Kafka connector, built on OpenTelemetry, enables the collection of Kafka messages and forwards ...

Event Series: Level up your SOC: Advancing with Splunk Enterprise Security

AI has fundamentally raised the stakes for security operations, and this three-part series is your guide to ...