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
Get Updates on the Splunk Community!

AI for AppInspect

We’re excited to announce two new updates to AppInspect designed to save you time and make the app approval ...

App Platform's 2025 Year in Review: A Year of Innovation, Growth, and Community

As we step into 2026, it’s the perfect moment to reflect on what an extraordinary year 2025 was for the Splunk ...

Operationalizing Entity Risk Score with Enterprise Security 8.3+

Overview Enterprise Security 8.3 introduces a powerful new feature called “Entity Risk Scoring” (ERS) for ...