-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #4398 from daynaslord/whats-new-10-12-ajax-requests
Whats-New-10-12-Ajax-Requests
- Loading branch information
Showing
3 changed files
with
18 additions
and
0 deletions.
There are no files selected for viewing
Binary file added
BIN
+424 KB
src/content/whats-new/2021/10/images/browser-with-ajax-highlighted.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
--- | ||
title: 'Browser Agent Update: Capturing All AJAX Requests' | ||
summary: 'With agent version 1211, all AJAX requests will be captured as events.' | ||
releaseDate: '2021-10-12' | ||
learnMoreLink: 'https://docs.newrelic.com/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1211/' | ||
getStartedLink: 'https://docs.newrelic.com/docs/browser/single-page-app-monitoring/get-started/introduction-single-page-app-monitoring/' | ||
--- | ||
Today, with the use of the [SPA Browser agent](https://docs.newrelic.com/docs/browser/single-page-app-monitoring/get-started/introduction-single-page-app-monitoring/), you can query in dashboards AJAX requests that are part of a route change. With the release [v1211](https://docs.newrelic.com/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1211/), we are expanding this ability to make all AJAX requests available to filter and facet on in the dashboard for customers using the Pro or SPA agent. In addition, we will ensure all AJAX requests show up as spans in distributed tracing. | ||
|
||
**What’s the impact?** | ||
|
||
With the addition of this feature, if you are using the Pro or SPA version of the agent, you will now see an increase in data consumption. If you want to dial back the amount of data consumed, you have two options: | ||
|
||
**Option 1 (recommended option):** In browser settings on NR1, there is a deny list where you can add URLs where you don’t need AJAX data collection. This will ensure the agent does not collect those AJAX calls. Refer to [this documentation](https://docs.newrelic.com/docs/browser/new-relic-browser/configuration/filter-ajax-request-events/) for more information. | ||
|
||
![New AJAX settings](./images/browser-with-ajax-highlighted.png "Browser with AJAX Settings Highlighted") | ||
|
||
**Option 2:** Drop data on ingest. Because the AJAX requests are being stored as events, you also have an option to set up rules to drop them on ingest. Refer to [this documentation](https://docs.newrelic.com/docs/browser/new-relic-browser/configuration/filter-ajax-request-events/) for more information. |
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.