Splunk Search

Why are we getting "Invalid value =" for parameter='INDEXED_EXTRACTIONS'" in the search.log when running a search using Hunk?

tsunamii
Path Finder

When running a search using Hunk, we are seeing a lot of these errors listed below in search log:

10-29-2015 22:22:56.942 ERROR IndexedExtractionsConfig - Invalid value='' for parameter='INDEXED_EXTRACTIONS'. 

Is this expected? If not, does it impact the search performance?

1 Solution

splunkIT
Splunk Employee
Splunk Employee

For Hunk/vix searches, these messages are pretty harmless as Hunk/vix searches do not support INDEXED_EXTRACTIONS yet. There is also an ER (SPL-108648) to have these messages removed in the Hunk search.log.

View solution in original post

splunkIT
Splunk Employee
Splunk Employee

For Hunk/vix searches, these messages are pretty harmless as Hunk/vix searches do not support INDEXED_EXTRACTIONS yet. There is also an ER (SPL-108648) to have these messages removed in the Hunk search.log.

Get Updates on the Splunk Community!

Now Available: Cisco Talos Threat Intelligence Integrations for Splunk Security Cloud ...

At .conf24, we shared that we were in the process of integrating Cisco Talos threat intelligence into Splunk ...

Preparing your Splunk Environment for OpenSSL3

The Splunk platform will transition to OpenSSL version 3 in a future release. Actions are required to prepare ...

Easily Improve Agent Saturation with the Splunk Add-on for OpenTelemetry Collector

Agent Saturation What and Whys In application performance monitoring, saturation is defined as the total load ...