All Apps and Add-ons

FireEye Error

arkonner
Path Finder

During the splunk server restart and written into _internal index the error reported below is displayed - seems to be introduced by the default configuration on which the app is provided.

Well, any help you that you could give us to solve the error would be appreaciated.

index=_internal eventtype="splunkd-log" log_level=ERROR

05-17-2018 19:07:52.840 +0200 ERROR SearchOperator:kv - Cannot compile RE \"[\w-.]{1,30})\"\s*(sid=\"(?\d*)")?\s*(stype=\"(?[\w-]{1,30})\")?\" for transform 'EXTRACT-malware-info_for_fireeye': Regex: invalid range in character class

0 Karma

sriley_splunk
Splunk Employee
Splunk Employee

I found you need to move the hyphen to the end of your capture group.

[\w\.-]

instead of:

[\w-\.]

The full line would be:

<malware\sname=\"(?<malware_name>[\w\.-]{1,30})\"\s*(sid=\"(?<malware_sid>\d*)")?\s*(stype=\"(?<malware_stype>[\w-]{1,30})\")?
0 Karma

Azeemering
Builder

This means that the regex string in the inline field extraction called malware-info_for_fireeye is deemed not correct.
Go to Settings-->Fields-->Field Extractions.
First thing I would do is check if the regex there has not been modfied from the original app by anyone.

It looks to me like it has been modified maybe?
The original is <malware\sname=\"(?<malware_name>[\w-\.]{1,30})\"\s*(sid=\"(?<malware_sid>\d*)")?\s*(stype=\"(?<malware_stype>[\w-]{1,30})\")?

Second I would use regex101.com or regexr.com to check if the regex string is actually correct and works as design

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

(re)Introducing the Splunk Community Champions + 2026 – 2027 Splunk MVPs ...

This program exists as a channel to empower and recognize Splunk advocates and help supercharge initiatives to ...

Introducing the 2026 - 2027 SplunkTrust cohort!

The goal of the SplunkTrust™ membership has historically been to acknowledge and recognize those who go above ...

Pro Tips for .conf26: How to Prep Like a Splunk Veteran

There’s no shortage of incredible content lined up for .conf26 in Denver, from deep-dive technical sessions ...