Click the Start a free trial link to start a 15-day SaaS trial of our product and join our community as a trial user. If you are an existing customer do not start a free trial.
AppDynamics customers and established members should click the sign in button to authenticate.
We're seeing a missmatch between the numbers that are showing in EUM and other statistics that we're gathering.
EUM ajax calls equals 800 whilst in applications the same API is 1700
EUM VirtualPage - booking_confirmation is 80, in SiteCat (Omniture) its 150
Previously I understood that Browser Snapshots are not 100%, but I thought the Pages & Requests, or Sessions and Analysis in EUM were 100%.
any clarity or help much appreciated, as we want to make sure all the numbers from the different monitoring solutions are consistent.
Can you please verify if you are not running into the 500 Ajax Page Limits.
Please see the docs which talks about the same.
Having said the above,EUM will capture metrics that comes from Browser/Device endpoint.
If there's any API calls within application,then it won't get tracked under EUM metrics.
So you can verify if the resource is called from other parts of your app.
Hope this helps.
Someone else has also confirmed the same as my observations, that the Pages and Ajax request are not 100%.
The Session's and Analytics parts (which are reflected in the VP and AJAX calls) should or shouldnt be 100%?
We would like to know so that we can report correct metrics back to the product teams.
Ideally the metrics should be 100%.
However the metrics are taken from what browsers report and not all browsers report them consistently everytime. Hence there is a possibility that there are some metrics which are rejected by the EUM server (in parts or in entirety) because they are missing information. With that said, this should not be a huge number.
Other reason for rejecting metrics is if the request is either explicitly added to the exclude rule, or there are custom exclude rules in place which are rejecting certain pages/AJAX.
Looking into your Excluded requests under EUM + reviewing your custom exclude rules should give us an idea about what is being excluded. Plus the DroppedBeacons.log should provide us further idea on what it is dropping and for what reason.