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!

Earn a $35 Gift Card for Answering our Splunk Admins & App Developer Survey

Survey for Splunk Admins and App Developers is open now! | Earn a $35 gift card!      Hello there,  Splunk ...

Continuing Innovation & New Integrations Unlock Full Stack Observability For Your ...

You’ve probably heard the latest about AppDynamics joining the Splunk Observability portfolio, deepening our ...

Monitoring Amazon Elastic Kubernetes Service (EKS)

As we’ve seen, integrating Kubernetes environments with Splunk Observability Cloud is a quick and easy way to ...