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!

See your relevant APM services, dashboards, and alerts in one place with the updated ...

As a Splunk Observability user, you have a lot of data you have to manage, prioritize, and troubleshoot on a ...

Cultivate Your Career Growth with Fresh Splunk Training

Growth doesn’t just happen—it’s nurtured. Like tending a garden, developing your Splunk skills takes the right ...

Introducing a Smarter Way to Discover Apps on Splunkbase

We’re excited to announce the launch of a foundational enhancement to Splunkbase: App Tiering.  Because we’ve ...