We have an overarching application defined for matching a specific domain
(e.g. www.acme.com) Let's say that application is made up of 100 pages of interest
Call this application A
Within that definition there are specific set of pages that we want to define as its own application
For instance, lets say we want pages 1-10 to be defined as a separate application all together
Call this application B
Is this sort of definition possible? Is this seen as an acceptable practice?
The reason for this is that we want to be able to show Application statistics as a "whole"
(for example bounce rates, entry and exit actions) but also have this same level of application visibility for a subset of pages.
Does this cause any issues internally within the Dynatrace application?
Solved! Go to Solution.
I don't think this is possible, since the application rules won't allow the same domain for two different applications.
Sure you can create the rule, but the first rule that applies is where traffic is grouped.
Rules are applied sequentially, with rules at the top taking priority over lower rules.
If you want a Global rule for www.acme.com and then for www.acme.com/app1 for app1 or www.acme.com/app2 for app2 but www.acme.com rule is first, traffic will validate that rule and won't keep checking others.
You could create an application for all others and send www.acme.com to the bottom of the rules and then create charts for bounce rate for all applications and have entry/exit for single ones. But there would not be a "Global" One. www.acme.com would have the info of when the others rule won't apply.
As indicated by Dante, a given user action (e.g, URL) can only belong to one application at a time. One reason for this is the RUM configuration is controlled at the application level and we can't have possibly conflicting configs for example.
One option with how things currently work would be to define separate applications (they can be named in a manner that shows they are closely coupled (e.g. MyApp-SubApp) and you would still be able to chart things like bounce rates etc... across those applications simply by ensuring that dimension is not selected on your custom chart. You could filter down to certain applications via management zone filters.
This is something that seems to me that will become a limitation in Dynatrace's notion of application. I also stated a similar case here: