Add paid banner, view consumption

src/content/docs/browser/browser-monitoring/browser-pro-features/session-traces-explore-webpages-life-cycle.mdx

@@ -24,6 +24,9 @@ import browserSessionTraceDetails from 'images/browser_screenshot-full_session-t
 
 import browserSessionTraces from 'images/browser_screenshot-full_session-traces.webp'
 
+<Callout variant="important">
+Session trace data will be billable starting June 10, 2024. See [Data consumption](#plan-for-paid-consumption) for details.
+</Callout>
 
 Our <InlinePopover type="browser" /> <DoNotTranslate>**Session traces**</DoNotTranslate> UI provides a detailed timeline of the load and interaction events during a webpage's full life cycle, for as long as ten minutes. After you select the session URL or session trace ID, you can use the detailed waterfall visualization and heat map overview to examine metrics and identify problems related to:
 
@@ -307,3 +310,36 @@ The following table describes each segment of the session trace, with a link to
 Session traces help you identify callbacks in your JavaScript code that execute slowly and block the execution of subsequent calls on the browser's main thread. These calls should execute quickly in order to allow the browser to quickly repaint the page in response to user actions.
 
 Session traces highlight any callbacks longer than 33ms. If called in rapid succession (such as inside a `requestAnimationFrame` loop), callbacks longer than 33ms reduce the frame rate below 30 frames per second. This speed seems sluggish to users.
+
+## Plan for paid consumption
+
+Starting June 10, 2024, session trace data will contribute to your overall monthly data consumption. This means it will be charged per your existing order. This change reflects the storage upgrade to the New Relic database (NRDB) which enables [customizing your sampling rate](#configure-sampling-rates), extending data retention, and improved performance.
+
+Run the following query in [query builder](https://one.newrelic.com/data-exploration/query-builder) to view your current monthly consumption of session trace data. If run from a [parent account](/docs/accounts/original-accounts-billing/original-users-roles/parent-child-account-structure/#hierarchy), the consumption of all child accounts will also be included in the results.
+
+```sql
+FROM NrConsumption SELECT rate(sum(consumption), 1 month) as monthly_SessionTrace_GBs WHERE usageMetric = 'UnbilledBrowserEventsBytes' SINCE '2024-04-25'
+```
+
+<img
+  title="Monthly session trace consumption query"
+  alt="A screenshot of monthly session trace consumption"
+  src={browserSessionTraces}
+/>
+
+For a more granular view, this query can be used to view your daily consumption by child account, if applicable:
+```sql
+FROM NrConsumption SELECT sum(consumption) as SessionTraceGBs WHERE usageMetric = 'UnbilledBrowserEventsBytes' FACET consumingAccountId, consumingAccountName SINCE '2024-04-25' TIMESERIES 1 day
+```
+<img
+  title="Daily session trace consumption query"
+  alt="A screenshot of daily session trace consumption"
+  src={browserSessionTraces}
+/>
+
+You can decrease your consumption of session trace data by [adjusting your sampling rates](#configure-sampling-rates) or disabling the feature by following these steps:
+
+  1. Go to <DoNotTranslate>**[one.newrelic.com](https://one.newrelic.com/all-capabilities) > All Capabilities > Browser**</DoNotTranslate>.
+  2. Select your browser app.
+  3. In the left-hand menu, click <DoNotTranslate>**Application settings**</DoNotTranslate>.
+  4. Toggle <DoNotTranslate>**Session traces**</DoNotTranslate> to OFF.