Splunk Dev

specified a regex without any named capturing group

biagiodipalma
Explorer

Hi there,

App Inspect v. 2.4.0.dev13 gives me this failure:

[TRANSFORMS-extract-fields] setting in props.conf specified a regex without any named capturing group. This is an incorrect usage. Please include at least one named capturing group. File: default/props.conf Line Number: 2

The regex affected are:

 

 

[extract-queue-statistics]
REGEX = ^.*rsyslogd-pstats\:\sim(?P<protocol>\w+)\W+(?P<port>\d+)\W\:\ssubmitted=(?P<submitted>\d+).*$

[extract-port-submitted]
REGEX = ^.*rsyslogd-pstats\:\s(?P<queue>[^:]+)\:\ssize=(?P<size>\d+)\senqueued=(?P<enqueued>\d+)\sfull=(?P<full>\d+)\sdiscarded\.full=(?P<discarded_full>\d+)\sdiscarded\.nf=(?P<discarded_nf>\d+)\smaxqsize=(?P<maxqsize>\d+).*$

 

How could I pass validation? I need to deploy this app on Splunk Cloud.

Labels (2)
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!

At .conf26, Don’t Just See What’s Next. Help Shape It at Innovation Labs.

Long before a new capability reaches the keynote stage, it begins as an idea waiting to be tested. At ...

Forwarder Topology Guidance: Intermediate HF vs Intermediate UF

Why Universal Forwarders Should Not Be Used as Intermediate Forwarders A practical Splunk forwarding topology ...

Data Management Digest – August 2026

Data Management Digest   Welcome to the August 2026 edition of Data Management Digest! August was a big month ...