Once OneAgent is installed on a host, it monitors all applications running on the host. All monitoring data is encapsulated into a sample placeholder application called
My web application. The reason we offer this placeholder application is to allow for more flexibility, as we leave it up to you how your application should be organized. There are cases, for example, where you may want to merge multiple domains into a single application. This is typically the case for sites that are offered in multiple languages, for example www.myshop.de and www.myshop.at.
My web application you will find a section called Top domains (see complete instructions below). This might be your starting point for defining your own application mappings. You can easily map the identified domains onto separate individual applications as you wish by opening the full details of the top domains section. If you want to create more applications, change existing application mappings, or if you need to define more complex rules looking at URLs and not only on domains, you can use the Application detection & RUM settings page (available at Settings > Web & mobile monitoring). Note that these settings are for web applications only.
Define an application the automated way
- Select Applications from the navigation menu.
- Click the My web application placeholder application.
- Scroll down to find the Top 3 included domains panel. This panel includes the domains that contain the largest number of actions that have been automatically detected by OneAgent in your environment.
- Click View full details.
- Select a domain from the list appearing under Top domains and expand it by clicking the arrow under Transfer domain.
- Click Create new application. Your application will be created and listed on the Applications page. From now on, all user actions that are monitored on this domain will be mapped onto the newly created application. Alternatively, you may want to add the domain to an existing application, in case some applications have already been created. To do this, expand the list box, select an application and click Transfer.
As you may want to use a more intuitive name for your application, you can easily rename it.
To rename an application
- Select Applications from the left-hand menu.
- Select your newly created application to access the application's overview page.
- Select the Browse button (...) and choose Edit.
- Type in the name you prefer in the text box at the top of the page. Note that application names must be unique.
Define an application using application detection rules
- Select Settings from the left-hand menu and choose Web & mobile monitoring.
- Select Application detection & RUM. Under Application detection rules, you can view the list of defined rules. For each application defined the automated way, a detection rule is automatically generated and added to the end of the list. Rules are applied sequentially, with rules at the top of the list taking priority over lower rules.
- Select Create application detection rule. Use the options offered on this page to create the appropriate detection rule for your application.
Best practices and recommendations
Define your applications based on team ownership so you can easily make use of management zones for access restrictions.
It may make sense to define applications based on the used technology stack, in order to apply the right settings and make management of specific settings easier. For example, activating support for specific XHR frameworks is typically required only for specific parts of a large application and for specific user action naming rules. It may help to separate such a large application into smaller ones because of the different technologies used or because of different owners of these parts.
You should avoid renaming
My web applicationto a specific application name, as
My web applicationwill contain all user actions on all domains that have not been included in any existing application rule. If you rename "My web application", it may be difficult to distinguish it from your other applications.
Separating applications by top level domain is always a good idea, as Dynatrace can’t correlate user actions across top level domains to user sessions anyway. This correlation is done via a cookie and therefore only works if the cookie can be set on the same top level domain. For example, user actions for www.dynatrace.com and blog.dynatrace.com can be captured in one application as the cookie can be set to dynatrace.com, but traffic for www.dynatrace.com and www.internal-dynatrace.com can’t be captured in one user session. You will still be able to separate user actions based on the domain, but user sessions will never have actions from both domains.
Low traffic applications should be grouped together. If you create an application based on a domain that has less than 10 actions per minute, Dynatrace won't automatically detect anomalies for this newly created application. Dynatrace depends on steady application traffic to correctly learn multidimensional baselines and to automatically report application problems. Your current anomaly detection settings can be changed in the anomaly detection settings for applications. Although this recommendation contradicts with the one mentioned above, for low traffic applications, it may make sense to combine them.
The application rules are processed in sequence for each request. More rules means more processing time and as the rules are processed within the OneAgents, you should try to have the rules for the most used applications that have the most traffic at the top of the list. As soon as one rule matches, no further requests are processed.
The more specific application detection rules should be defined first, while the more generic rules should be at the bottom of the list. Let's assume that you want to create an application called "A" onto which the following two domains will be mapped:
and another application "B" for the following domain:
If you create a generic grouping rule based on the
shopvalue, all three domains will be grouped into the same web application for monitoring. Therefore, you should first define a more specific rule, for example "If the URL ends with
shop.html" so that only the third URL is mapped to application "B". Then you can safely define a generic rule based on the
shopvalue, as the third URL will have already been mapped to the previous application and therefore won't be included in application "A".
Depending on your requirements, you can adjust the monitoring consumption and configure Real User Monitoring accordingly. To monitor traffic on a single application, you can opt to use user actions and session properties. To monitor separate applications and get complete insights into consumption per application, you can configure separate applications, use tagging to split the metrics, and define management zones.