All Apps and Add-ons

TA-juniper "Bad regex value" error after upgrade from Splunk 6.2.6 to 6.3.5

pjohnson1
Path Finder

Hello,

After we upgraded Splunk to 6.3.5, our TA-juniper started producing a bad regex error:

btool.log

Bad regex value: '\s+([.-\w]+)\s+RT_FLOW', of param: transforms.conf / [dvc_for_junos_fw] / REGEX; why: in valid range in character class

transforms.conf

[dvc_for_junos_fw]
REGEX = \s+([.-\w]+)\s+RT_FLOW
FORMAT = dvc::$1

Could someone please shed some light on this?

Thanks.

1 Solution

twinspop
Influencer

Character classes are in square brackets. If you have a hyphen in the middle of the class, it thinks you want a range. You need to move the hyphen to the front of the class:

 [dvc_for_junos_fw]
 REGEX = \s+([-.\w]+)\s+RT_FLOW
 FORMAT = dvc::$1

View solution in original post

michael_sleep
Communicator

Like Twinspop mentioned it's the hyphen but you don't have to move it, you can escape it with a backslash:

 [dvc_for_junos_fw]
 REGEX = \s+([.\-\w]+)\s+RT_FLOW
 FORMAT = dvc::$1

twinspop
Influencer

Character classes are in square brackets. If you have a hyphen in the middle of the class, it thinks you want a range. You need to move the hyphen to the front of the class:

 [dvc_for_junos_fw]
 REGEX = \s+([-.\w]+)\s+RT_FLOW
 FORMAT = dvc::$1

pjohnson1
Path Finder

Thank you!

0 Karma
Get Updates on the Splunk Community!

Introducing Splunk Enterprise 9.2

WATCH HERE! Watch this Tech Talk to learn about the latest features and enhancements shipped in the new Splunk ...

Adoption of RUM and APM at Splunk

    Unleash the power of Splunk Observability   Watch Now In this can't miss Tech Talk! The Splunk Growth ...

Routing logs with Splunk OTel Collector for Kubernetes

The Splunk Distribution of the OpenTelemetry (OTel) Collector is a product that provides a way to ingest ...