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!

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...

New in Observability Cloud - Explicit Bucket Histograms

Splunk introduces native support for histograms as a metric data type within Observability Cloud with Explicit ...