-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Capture All AJAX Requests #40
Comments
I have raised an issue regarding New Relic not being able to capture AJAX requests in a fetch library i was using |
Thank you @smblee for debugging on this. We are also using |
Shipped in Browser agent v1211 |
Problem
Customers would like all Ajax Requests available to query in Insights. The confusion lies when just a subset of ajax requests are captured as event data, the rest are not-so-easy-to-query aggregate metric data.
Ajax calls are currently captured as events (AjaxRequest) _ only _when the call happens as part of a browser interaction that is captured. Since out of the box we capture only interactions that are classified as route changes, many ajax calls do not get recorded as events.
Ajax requests that are stored as event data are the starting point for Distributed Tracing, so by not representing all requests in the system, we lose some visibility.
What we need to do
We need to capture all AJAX requests in a way that customers can facet and filter by AJAX and not missing AJAX requests when using DT
The goal of this effort is to consolidate all AJAX requests into one data collection type, that is queryable via Insights and a seamless experience for our customers.
Proposed Solutions
All ajax requests as events (which come with storage concerns)
Ajax requests as dimensional metrics, which likely requires some rework for DT? This is likely the better candidate.
BROWAGENT-50
Related Operational Links
The text was updated successfully, but these errors were encountered: