I'm looking to configure the application detection rule.
We have application detection rule already in place to bucket below URL pattern
However, I wanted to setup rule based on following criteria,
where '1' could be any value. What I can see, from the setting that we cannot use regular expression to achieve this.
Has anyone encountered with such situation and resolve it by any other means?
Solved! Go to Solution.
In such situations I use this example rule:
For example I have another application that ended "/user". I can restrict injection on application settings.
for example */landing/*
Default RUM application (My web application) - RUM monitoring is off.
Test = APPLICATION-79B0DAD604B5C946
curl --user-agent "dtHealthCheck" http://192.168.1.120/landing/23423/user -v -o /dev/null
< Set-Cookie: dtCookie=v_4_srv_30_sn_B88ADDA55966E736DDDEC26D38CC79AF_perc_100000_ol_0_mul_1_app-3A79b0dad604b5c946_1_rcs-3Acss_0; Path=/
< x-dtHealthCheck: OK_BUT_URL_RESTRICTION|0xc5d82544e4620574
curl --user-agent "dtHealthCheck" http://192.168.1.120/crm/23423/user -v -o /dev/null
< Set-Cookie: dtCookie=v_4_srv_43_sn_38CF1324938283CE50D925DE73D1CEB4_perc_100000_ol_0_mul_1_app-3A79b0dad604b5c946_1_rcs-3Acss_0; Path=/
< x-dtHealthCheck: OK|0xc5d82544e4620574
curl --user-agent "dtHealthCheck" http://192.168.1.120/ -v -o /dev/null
< x-dtHealthCheck: CAPTURING_OFF_APP_CONF|0xc5d82544e4620574
< x-dtAgentId: 0xc5d82544e4620574
Application for 192.168.1.120 defined and RUM is off.
Thank you for the response.
Above example would work in case we know that specific word surely appear in the URL however, how we can do it for below example, (This would be second application for bucketing all such URLs)
application.com/1/user application.com/2/user application.com/3/user . . application.com/n/user
And the first application would be bucketing of below URL,
Other posts asking regex in application detection rules were discarted:
I had raised this idea: Application detection rules: More than one condition
With more than one condition, then, you would be able to use something as:
begins with "application.com/" AND ends with "/user"
But this is not in product, feel free to support my idea. I do not see another option than create one rule per URL pointing to same application. This is going to be difficult to maintain and it is not scalable, but I do not see other way right now.
Sure thing, rather than creating new RFE, lets follow-up and upvote existing RFE's