PDFs

On this page:

Your Rating:
Results:
PatheticBadOKGoodOutstanding!
45 rates

You may find that some pages have not been monitored as expected. The sections below may help you determine the reason that these pages have not been monitored.

Verify Pages Have Been Injected

If only some web pages are not reporting data, first verify that those pages have been injected with the JavaScript Agent. See Verifying that the JavaScript Agent for Browser RUM was injected.

Check Exclude Rules

It the agent has been injected, the page may have been excluded from monitoring by custom exclude rules. You can check and modify these rules.

To access custom exclude rules for pages:

  1. Click Configuration > Instrumentation.
  2. Click the Web Page Naming, Error Detection, Thresholds, Percentiles, etc. tab.

  3. From the tabs Base Pages and iFramesAJAX, and Virtual Pages, check the custom rules under the Exclude Rules section.


  4.  To examine and/or modify a custom exclude rule select it in the list and click the icon:
  5. If you want to remove a custom exclude rule, select and click Delete.

Check Automatic Injection Configuration

In addition, certain pages could have been excluded by the injection configuration. This can happen when automatic injection is used with a limited set of pages enabled for injection. If you used automatic injection, check your automatic injection configuration to see if the missing pages are enabled for injection.

Examine the Request Match Rules and Request Exclude Rules lists under Only enable Automatic Injection for certain Pages in the Automatic JavaScript Injection tab. See Automatic Injection of the JavaScript Agent. Pages can also be bypassed by assisted injection using injection rules when an injection rule specifies only classes and methods to be injected. If you used assisted injection with injection rules, check your injection rules. See Assisted Injection.

  • No labels