Getting Data In

Deployment Monitor Throwing Errors

OldManEd
Builder

Just loaded the Deployment Monitor, v5.0.3, and it's throwing errors;

ERROR SearchOperator:kv - Cannot compile RE \"(?i)Subscription-Name>(?P<Subscription-Name>.+?)<\" for transform 'EXTRACT-Subscription_Name': Regex: syntax error in subpattern name (missing terminator)

And it's doing this for a bunch of fields;

Subscription-Name
Network-Status
Network-ID
Authentication-Type
Algorithm-Name
Subscription-Name
Network-Status
etc.

Has anyone seen this before?

0 Karma
1 Solution

OldManEd
Builder

OK, I opened up a trouble ticket with Splunk support on this one and they figured it out. In the /opt/splunk/etc/apps/search/local/props.conf file, under the [sprprovisioning] stanza, the fields were defined as follows;

EXTRACT-Subscription_Name = (?i)Subscription-Name>(?P<Subscription-Name>.+?)<

The problem was with the "(?P<Subscription-Name>" section. On support's suggestion I was asked to change the dash to an underscore on all the fields with problems as seen below;

EXTRACT-Subscription_Name = (?i)Subscription-Name>(?P<Subscription_Name>.+?)<

That cleaned it up.

View solution in original post

0 Karma

OldManEd
Builder

OK, I opened up a trouble ticket with Splunk support on this one and they figured it out. In the /opt/splunk/etc/apps/search/local/props.conf file, under the [sprprovisioning] stanza, the fields were defined as follows;

EXTRACT-Subscription_Name = (?i)Subscription-Name>(?P<Subscription-Name>.+?)<

The problem was with the "(?P<Subscription-Name>" section. On support's suggestion I was asked to change the dash to an underscore on all the fields with problems as seen below;

EXTRACT-Subscription_Name = (?i)Subscription-Name>(?P<Subscription_Name>.+?)<

That cleaned it up.

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!

From Data to Insight: Announcing the Winners of the Splunk Dashboard Contest

Hi Splunkers, First off, thank you to everyone who participated in our very first From Data to Insight: The ...

Splunk Developers: Construct Your Future at the .conf26 Builder Bar

Calling all Splunk architects, platform admins, and app developers: the site is open, and the blueprints are ...

Quick connection discovery mode for forwarders

When a Splunk forwarder loses connectivity to its indexers, it does not always reconnect immediately. In many ...