-
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 #17220 from lchockalingam/whats-new-05-08-sessiont…
…races (WHAT'S NEW: 5/8; time TBD): session traces
- Loading branch information
Showing
1 changed file
with
28 additions
and
0 deletions.
There are no files selected for viewing
28 changes: 28 additions & 0 deletions
28
src/content/whats-new/2024/05/images/whats-new-05-08-sessiontraces.md
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,28 @@ | ||
--- | ||
title: 'Browser session traces billing update effective June 10, 2024' | ||
summary: 'Session traces sampling rate is now configurable and ingest is billable' | ||
releaseDate: '2024-05-08' | ||
learnMoreLink: 'https://docs.newrelic.com/docs/browser/browser-monitoring/browser-pro-features/session-traces-explore-webpages-life-cycle/' | ||
getStartedLink: '' | ||
--- | ||
|
||
Session traces provide a detailed timeline of events and interactions during a web page's full lifecycle so you can troubleshoot errors, page load times, or web app performance. Starting **June 10, 2024**, session trace data will contribute to your overall monthly product usage. This means it will be charged per your existing order. This change reflects the storage upgrade to the New Relic database (NRDB), which enables longer data retention and improved performance. | ||
|
||
We're also providing you with increased control over session trace data collection and associated costs starting **May 8**: | ||
|
||
* **Monitor consumption:** See the [docs](https://docs.newrelic.com/docs/browser/browser-monitoring/browser-pro-features/session-traces-explore-webpages-life-cycle/#plan-for-paid-consumption) to track your data usage related to session traces. | ||
* **Adjust the sampling rate:** Reduce the number of tracked sessions by modifying the sampling rate in your [browser application settings](https://docs.newrelic.com/docs/browser/browser-monitoring/browser-pro-features/session-traces-explore-webpages-life-cycle/#configure-sampling-rates). This will decrease data ingestion and its corresponding costs. You may do this beginning May 8, as you’ll want to better understand your session trace footprint before making adjustments. | ||
* **Disable session traces:** Session traces can be entirely disabled through the [browser application settings](https://docs.newrelic.com/docs/browser/browser-monitoring/browser-pro-features/session-traces-explore-webpages-life-cycle/#configure-sampling-rates) if you no longer require access. | ||
|
||
If you make no changes, we’ll continue collecting up to 90 session traces per hour per browser entity. | ||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|