topic Re: application detection rule issue in Real User Monitoring

application detection rule issue

adm — Mon, 26 Jul 2021 19:49:16 GMT

Is it possible for a URL to fall under 2 separate detection rules? Seems like this is occurring in a tenant I'm looking at. Docs say the URL should just fall into the app with the first matching rule.

Re: application detection rule issue

ryan_ott — Mon, 26 Jul 2021 20:35:42 GMT

Hello,

URLs should only be grouped into a single application within Dynatrace - falling into whichever rule matches first, with rules at the top taking priority over lower rules. If you want to test to see which application a URL might fall into, you can use the 'Check your existing detection rules' option within the 'Web and Mobile Monitoring' settings page, as shown in the screenshot below. Hope this helps.

-Ryan

Re: application detection rule issue

adm — Tue, 27 Jul 2021 20:21:04 GMT

Yep, tested it before asking. Strange

Re: application detection rule issue

rastislav_danis — Wed, 28 Jul 2021 08:31:24 GMT

Many issues in app detection rules comes from fact, that domain name of app (as seen in browser) can be changed on route until request arrives to agent, where app detection executes. I have customer, where standard application domain name xy.com is not detectable on agent and app has to be detected via specific virtualhost.domain name.
You can check which domain name is correct in requests metadata in backend service requests.

Re: application detection rule issue

adm — Fri, 30 Jul 2021 13:21:49 GMT

Not sure your reply is relevant to my issue. You describe an issue of app detection failing to pick up a URL whereas I'm having a URL picked up too much.

Re: application detection rule issue

rastislav_danis — Fri, 30 Jul 2021 13:30:34 GMT

If it's picked "too much", it can happen that it's not the same all the time.

Re: application detection rule issue

ct_27 — Fri, 30 Jul 2021 14:34:19 GMT

We had similar issue and what @rastislav_danis is mentioning was our problem yet to this day we still can't figure out where the URL is changing. We thought it was our Firewall VIP but wasn't there either. The problem URL wasn't significant enough for us to spend any more time on so we generalized the DT criteria to capture it.

Very early on in our implementation we had issues where rules were just not in the correct priority order and it caused too much collect and sometimes not enough collection.

I must say that DT is very accurate in that once the URL falls into a bucket, it's done, it will never fall into more than one bucket. It's truly, a situation where the computer does what and only what the human tells it to do.

So, I would suggest going over the rules from the top down in extreme detail to find the problem.