Splunk Enterprise

How to resolve field extractor error

abhayneilam
Contributor

Hi,
I am getting the following error, kindly let me know what can be done if this error comes again and my searching is too slow, how to increase the speed of searching.

Field extractor name=usb_trans is unusually slow (max single event time=1078ms, probes=65 warning max=1000ms)

Please help as it is taking too much time to search for the data

Thanks in advance

0 Karma
1 Solution

MuS
SplunkTrust
SplunkTrust

hi abhayneilam

please use the search before asking questions, it took me not even 20 sec to find the answer for your message.....

The solutions are :

  • identify and improve the regexes/field extractions ( best to do )
  • or change the warning threshold for key values extraction ( this way you are only fighting the smoke but not the fire )

edit $SPLUNK_HOME/etc/system/local/limits.conf, and change max_extractor_time value

see http://docs.splunk.com/Documentation/Splunk/5.0/Admin/Limitsconf

[kv]
max_extractor_time = 
# Maximum amount of CPU time, in milliseconds, that a key-value pair extractor will be allowed to  take before warning. If the extractor exceeds this execution time on any event a warning will be issued  Defaults to 1000

avg_extractor_time = 
# Maximum amount of CPU time, in milliseconds, that the average (over search results) execution time of   a key-value pair extractor will be allowed to take before warning. Once the average becomes larger  than this amount of time a warning will be issued Defaults to 500

cheers,

MuS

View solution in original post

MuS
SplunkTrust
SplunkTrust

hi abhayneilam

please use the search before asking questions, it took me not even 20 sec to find the answer for your message.....

The solutions are :

  • identify and improve the regexes/field extractions ( best to do )
  • or change the warning threshold for key values extraction ( this way you are only fighting the smoke but not the fire )

edit $SPLUNK_HOME/etc/system/local/limits.conf, and change max_extractor_time value

see http://docs.splunk.com/Documentation/Splunk/5.0/Admin/Limitsconf

[kv]
max_extractor_time = 
# Maximum amount of CPU time, in milliseconds, that a key-value pair extractor will be allowed to  take before warning. If the extractor exceeds this execution time on any event a warning will be issued  Defaults to 1000

avg_extractor_time = 
# Maximum amount of CPU time, in milliseconds, that the average (over search results) execution time of   a key-value pair extractor will be allowed to take before warning. Once the average becomes larger  than this amount of time a warning will be issued Defaults to 500

cheers,

MuS

abhayneilam
Contributor

Many Many thanks MuS !!

0 Karma
Get Updates on the Splunk Community!

Splunk Observability Cloud | Unified Identity - Now Available for Existing Splunk ...

Raise your hand if you’ve already forgotten your username or password when logging into an account. (We can’t ...

Index This | How many sides does a circle have?

February 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...

Registration for Splunk University is Now Open!

Are you ready for an adventure in learning?   Brace yourselves because Splunk University is back, and it's ...