Splunk Search

Bug in interactive field extractor (IFX)?

Ultra Champion

There seems to be a bug in the interactive field extractor regarding the naming of fields. If copy-pasting a regex (crafted through rex perhaps), where the field name contains a hyphen (minus/dash/-) instead of the the default placeholder <FIELDNAME>, there will be an error when you hit 'save' ("Illegal character in field name" or something like that).

However, there is nothing stopping you from saving a field extraction which has the default <FIELDNAME> placeholder in the regex, and where the name entered in the 'save' dialog box contains hyphens. The save goes through, but the field never shows up in searches.

Couldn't the same error checking be applied here, since this is a more likely scenario than the copy/paste variant?

This was tested on Splunk 4.3.1 (win-64), and neither the Changelog nor Known Issues for 4.3.2 mention this.

Best regards,


0 Karma

New Member

Thanks for submitting this issue Kristian. I just wanted to add that I originally found this problem on Ubuntu Server 12.04 LTS 64 bit.

I think it was a sort of happy accident that I discovered this after trying your suggestion to help fix my non-working extraction.

The reality is that this is probably happening to a lot of people. I wouldn't think that using the IFX tool and naming extractions with hyphens is terribly uncommon.



0 Karma
Get Updates on the Splunk Community!

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 ...

Splunkbase | Splunk Dashboard Examples App for SimpleXML End of Life

The Splunk Dashboard Examples App for SimpleXML will reach end of support on Dec 19, 2024, after which no new ...

Understanding Generative AI Techniques and Their Application in Cybersecurity

Watch On-Demand Artificial intelligence is the talk of the town nowadays, with industries of all kinds ...