AppDynamics Application Intelligence Platform
You can configure the display names by which various pages, Ajax requests, and iframes are referred to in controller lists and dashboards.
In this topic, the term "pages" includes iframes, Ajax requests, and base pages.
No matter how the page is named, AppDynamics always reports the page name in lower-case.
1. Access the EUM configuration screen if you are not already there. Configure->Instrumentation
2. Select the End User Experience tab.
3. Select the Web Page Naming, Error Detection, Thresholds, etc. sub tab
4. Expand Configure how Pages, AJAX Requests, and Iframes will be named.
Whenever you make any changes, click Save to save the configuration.
This is the order in which AppDynamics evaluates the page naming rules.
If you enable the default naming configuration and do not modify it, AppDynamics identifies and names your pages using the first 2 segments of the page URL.
You can modify the default configuration in the Default Naming Configuration section. For example, you can include the protocol or domain in the name, or use different segments of the URL, or run a regular expression on the URL, or include query parameters in the name. For example, you can use the Show Domain option to identify third-party Ajax or iframe calls.
If you do not want to use the default convention at all, disable it by clearing the Enabled check box. In this case you must configure at least one custom page naming rule so that AppDynamics can identify and name pages.
You can create custom rules for identifying and naming pages.
To create a custom page naming rule, click the plus icon in the Custom Naming Rules section. Then configure the custom rule for AppDynamics to use to identify and name the page.
This configuration screen is similar to the default configuration screen but it includes a priority field. The priority specifies which rule to apply to the naming of a page if it could be identified by more than one rule. For example, if CustomRuleA specifies Use the first 3 segments of the URL and has a priority of 9 and CustomRuleB specifies Use the last 3 segments of the URL and has a priority of 8, a page in which the URI has more than 3 segments will be named by CustomRuleA because it has a higher priority.
The default rule, if enabled, has a priority of 0.
In the example below, you might have multiple pages that include "search/r/region" in their URLs, so "search/r/region01", "search/r/region23", and so forth. You want to name all the pages from that set as a single page named "search/r/region". Using the Run regex on URI option, you remove the domain name and the number at the end of the URL, grouping all your "/search/r/region" URLs into a single set. Because all the URLs contain "search/r/region", AppDynamics now collects information for them all under the single page name "search/r/region". Otherwise it would use the default page naming rule, or, if another rule with a priority greater than 4 exists, that higher priority rule.
You can configure custom exclude rules for pages. Any page with a URL matching the configuration is excluded from monitoring.