You may find that some Ajax requests have not been monitored as expected. The sections below may help you determine the reason that these pages have not been monitored.
Check Exclude Rules
It the agent has been injected, the Ajax event may have been excluded from monitoring by custom exclude rules. You can check and modify these rules.
To access custom exclude rules for pages:
Click Configuration > Instrumentation.
From the AJAX tab, check the custom rules under the Exclude Rules section.
- To examine and/or modify a custom exclude rule select it in the list and click the
- If you want to remove a custom exclude rule, select and click Delete.
Verify That XHR Objects Were Reused Correctly
Browser RUM can monitor multiple Ajax calls made from a reused
XMLHttpRequest object, but If the
Incorrect Method to Reuse XMLHttpRequest Object
In the example below, the
xhr object is making a request to
/multi-bt before the request to
When an Ajax request cannot be reported because the
Correct Method to Reuse XMLHttpRequest Object
The correct method to reuse the
XMLHttpRequest object to make more than one request is to nest the calls so that new calls are only made when previous calls have been completed. In the example below, the call to
/xhr/multi-bt2 is only made when the call to
/multi-bt has completed, so both calls are reported as Ajax requests.
Check Injection Configuration
In addition, certain Ajax requests could have been filtered out by the injection configuration. This can happen when the injection uses XHR filters to limit which Ajax requests are monitored. Check your injection configuration to verify that the filtering did not prevent the calls from being monitored.