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!

.conf24 | Day 0

Hello Splunk Community! My name is Chris, and I'm based in Canberra, Australia's capital, and I travelled for ...

Enhance Security Visibility with Splunk Enterprise Security 7.1 through Threat ...

(view in My Videos)Struggling with alert fatigue, lack of context, and prioritization around security ...

Troubleshooting the OpenTelemetry Collector

  In this tech talk, you’ll learn how to troubleshoot the OpenTelemetry collector - from checking the ...