Skip to content
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

Closed
rr0214 opened this issue May 10, 2021 · 3 comments
Closed

Capture All AJAX Requests #40

rr0214 opened this issue May 10, 2021 · 3 comments

Comments

@rr0214
Copy link

rr0214 commented May 10, 2021

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

@rr0214 rr0214 added this to Next: work planned within the next 90 days. These features may still be de-prioritized and moved to future. in Browser Agent Instrumentation Roadmap May 10, 2021
@smblee
Copy link

smblee commented May 14, 2021

I have raised an issue regarding New Relic not being able to capture AJAX requests in a fetch library i was using ky, but it seems more like a issue of Newrelic browser client. You can see my notes here: sindresorhus/ky#345

@rr0214 rr0214 added the roadmap label May 17, 2021
@lukeupup
Copy link

Thank you @smblee for debugging on this. We are also using ky and facing exact the same problem. Considering that ky is now the most popular request utility based on fetch (weekly download on npm is over 400k), we really want New Relic can fix it asap.

@rr0214 rr0214 changed the title Capture all AJAX Requests & Change to Dim Metrics Capture All AJAX Requests Jun 1, 2021
@rr0214 rr0214 moved this from Next: work planned within the next 90 days. These features may still be de-prioritized and moved to future. to Now: Features that are currently in progress. in Browser Agent Instrumentation Roadmap Jun 9, 2021
@coreyarnold coreyarnold added this to To do: Features here are prioritized in Browser Instrumentation Engineering Board Jun 11, 2021
@martinkuba martinkuba moved this from To do: Features here are prioritized to In progress: Issues being worked on in Browser Instrumentation Engineering Board Jun 16, 2021
@rr0214 rr0214 removed this from In progress: Issues being worked on in Browser Instrumentation Engineering Board Jul 6, 2021
Browser Agent Instrumentation Roadmap automation moved this from Now: Features In Progress to Recently Completed Mar 15, 2022
@aubreymasten
Copy link
Contributor

Shipped in Browser agent v1211

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

4 participants