Often the number of app server transactions (requests per minute or rpm) is larger than the number of browser transactions (pages per minute or ppm) for the same application. Even sites where all pages are web-facing (no API or back-end-only components) may have between two and ten times more transactions than recorded browser page views.
Some common reasons that this can occur are:
|App requests (rpm) vs. browser transactions (ppm)||Possible reasons for differences|
|Instrumentation||You do not instrument every page of your app, or not every page uses auto-instrumentation.|
|Webpage format||Webpages are not text/html. (To avoid harming data, Browser does not instrument non-html pages, because they are not intended to be parsed by a browser.)|
Some requests to your backend are made through AJAX. AJAX throughput is tracked separately in New Relic Browser's AJAX page.
Note: AJAX tracking depends on your New Relic subscription level(Pro and higher).
|Cache||A cache exists between your app server and your end users. Depending on whether cached pages are properly instrumented, this may cause balance to skew the other direction, with more browser throughput than app server.|
Users navigate away from the page before it finishes loading or before it hits the window.onload() event.
For more help
If you would like to ensure all your pages are being instrumented, try troubleshooting your browser monitoring installation.