ページ識別と命名の構成
表示名を構成して、さまざまなページと iframe をコントローラリストとダッシュボードで参照およびソートできます。このページでは、「ページ」という用語には、iframe と基本ページが含まれます。
ルールを使用すると、次のことができます。
- Splunk AppDynamics のデフォルトの命名ルールを使用します。このルールは、このままにするか、変更できます。
- デフォルトの規則を上書きするには、ページグループ化ルールを作成します。
- 特定の条件を満たすページをモニタリングから除外するには、カスタム除外ルールを作成します。
- デフォルトの命名構成を無効にして、ページグループ化ルールのみを使用します。
ページの名前がどのように指定されているかにかかわらず、Splunk AppDynamics は常に、ページ名を小文字でレポートします。
Access Rules
Evaluation Logic for the Rules
This is the order in which Splunk AppDynamics evaluates the page naming rules.
Modify Default Page Naming Rules
If you enable the default naming configuration and do not modify it, Splunk AppDynamics identifies and names your pages using the first two segments of the page URL.
You can modify the default configuration by double-clicking Default Naming Configuration in the Page Grouping Rules section. This opens the Page Grouping Rule popup, where you can select the drop-down list.
- Using parts of the URL to include the protocol or domain in the name, use different segments of the URL, or include query parameters or anchors in the name.
- Using Regex Match on the URL to match page names by running a regular expression.
- Parts of the URL
-
- Regex Match
-
If you do not want to use the default convention at all, disable it by clearing the Enabled checkbox. In this case, you must configure at least one custom page naming rule so that AppDynamics can identify and name pages.
Custom Page Grouping Rules
You can create custom Page Grouping rules for identifying and naming pages.
To create a custom include naming rule, from the Page Grouping Rules section, click Add. Then you use the same Page Grouping Rule popup to configure the custom include rule to identify and name the page.
The order of the include rules in the list determines the priority of the rules: The rules at the top are evaluated first, and the rules at the bottom are evaluated last. You cannot change the priority of Default Naming Configuration, but you can modify or disable it.
Guidelines for Using Regular Expressions in Page Grouping Rules
When using regular expressions to match URLs in your Page Grouping rules, note the following guidelines:
- URL strings are case-sensitive. So, although the page names displayed in Pages & Ajax Requests are converted to lowercase, your regular expressions still need to match the case used in URLs that your include rule are trying to capture.
- Your regular expression should match the entire URL, from beginning to end, not just a section; otherwise, the rule will not match. This differs from using regular expressions in custom match rules for naming transactions, which only need to match sections of the URL.
- Beacons for older browsers (primarily Internet Explorer 6-8) are sent using image requests, and therefore, have an inherent length limitation. To manage this limitation, Browser RUM does not support URLs longer than 180 characters, page names longer than 50 characters, and user data longer than 128 characters for these browsers.
Limitations
- If you are using the regex expression "and use groups" to group pages by a custom page name (i.e. you want the page /my-business/checkout to display as /checkout/my-business), the regex logic defaults to ascending order of the groups. For example, the regex expression "and use groups = 3,2" will default to "use groups = 2,3".
Example Page Grouping Rule
Suppose you have multiple pages that include the string search/r/region in their URLs, such as search/r/region01, search/r/region23, etc., and you want to name all the pages from that set as a single-page named search/r/region. By selecting the dropdown using a Regex match on the URL, you can enter a regular expression to remove the domain name and the number at the end of the URL, grouping all your /search/r/region URLs into one 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, AppDynamics uses the default page naming rule or a rule with higher priority.
Custom Page Exclude Rules
You can configure custom exclude rules for pages in the same way you configure page grouping rules. Any page with a URL matching the configuration is excluded from monitoring.