Merge branch 'develop' into pr/16572

.gitignore

@@ -88,3 +88,6 @@ yarn-error.log
 .devcontainer
 
 src/images/infrastructure_screenshot_full_sonarqube-dashboard.webp
+
+# Local Netlify folder
+.netlify

env.js

@@ -10,6 +10,12 @@ const assetPrefix = () => {
   if (process.env.BUILD_LANG === 'kr') {
     return 'https://docs-website-kr.netlify.app';
   }
+  if (process.env.BUILD_LANG === 'es') {
+    return 'https://docs-website-es.netlify.app';
+  }
+  if (process.env.BUILD_LANG === 'pt') {
+    return 'https://docs-website-pt.netlify.app';
+  }
   return '';
 };
 

gatsby-config.js

@@ -374,15 +374,15 @@ module.exports = {
           },
         },
         layout: {
-          contentPadding: '2.625rem 5rem',
+          contentPadding: '5rem',
           maxWidth: '1600px',
           component: require.resolve('./src/layouts'),
           mobileBreakpoint: '760px',
           sidebarWidth: '340px',
         },
         i18n: {
           translationsPath: `${__dirname}/src/i18n/translations`,
-          additionalLocales: ['jp', 'kr'],
+          additionalLocales: LOCALES,
         },
         prism: {
           languages: [

netlify.toml

@@ -4,6 +4,10 @@ package = "@netlify/plugin-gatsby"
 [functions]
   included_files = ["!.cache/data/datastore/data.mdb","!.cache/query-engine"]
 
+[[edge_functions]]
+  path = "/*"
+  function = "osano-country"
+
 [[headers]]
 for = "/*"
 

netlify/edge-functions/osano-country.js

@@ -0,0 +1,53 @@
+import { HTMLRewriter } from 'https://ghuc.cc/worker-tools/html-rewriter/index.ts';
+
+export default async (request, context) => {
+  const response = await context.next();
+  const hasGdpr = new Set([
+    'AT',
+    'BE',
+    'BG',
+    'HR',
+    'CY',
+    'CZ',
+    'DK',
+    'EE',
+    'FI',
+    'FR',
+    'DE',
+    'GR',
+    'HU',
+    'IE',
+    'IT',
+    'LV',
+    'LT',
+    'LU',
+    'MT',
+    'NL',
+    'PL',
+    'PT',
+    'RO',
+    'SK',
+    'SI',
+    'ES',
+    'SE',
+  ]).has(context.geo.country.code);
+
+  if (hasGdpr) {
+    return new HTMLRewriter()
+      .on('script', {
+        element(element) {
+          const scriptSrc = element.getAttribute('src');
+          if (
+            typeof scriptSrc === 'string' &&
+            scriptSrc.startsWith('https://cmp.osano.com/')
+          ) {
+            element.setAttribute(
+              'src',
+              scriptSrc.replace(/variant=one/gi, 'variant=two')
+            );
+          }
+        },
+      })
+      .transform(response);
+  }
+};

package.json

@@ -10,7 +10,7 @@
     "@emotion/styled": "^11.3.0",
     "@mdx-js/mdx": "2.0.0-next.8",
     "@mdx-js/react": "2.0.0-next.8",
-    "@newrelic/gatsby-theme-newrelic": "9.3.2",
+    "@newrelic/gatsby-theme-newrelic": "9.4.3",
     "@splitsoftware/splitio-react": "^1.2.4",
     "ansi-colors": "^4.1.3",
     "cockatiel": "^3.0.0-beta.0",

src/content/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts.mdx

@@ -177,20 +177,6 @@ Here's a table with our standard roles. To better understand these roles, go to
       </td>
     </tr>
 
-    <tr>
-      <td>
-        <DoNotTranslate>**Manage v1 users**</DoNotTranslate>
-      </td>
-
-      <td>
-        For New Relic organizations that existed before July 30 2020 and have users on our [original user model](/docs/accounts/original-accounts-billing/original-users-roles/overview-user-models), this role lets you manage those "v1" users. This is used primarily for overseeing a [user migration process](/docs/accounts/original-accounts-billing/original-users-roles/user-migration/).
-      </td>
-
-      <td>
-        Required: full platform.
-      </td>
-    </tr>
-
   </tbody>
 </table>
 

src/content/docs/accounts/accounts-billing/new-relic-one-user-management/user-permissions.mdx

@@ -44,15 +44,11 @@ Our pre-built roles have various groupings of permissions. How our pre-built rol
 
 ## Permission definitions [#permission-definitions]
 
-Here's a screenshot of the permissions available in the permissions UI. These are only a subset of everything you can do in New Relic and represent the specific permissions we believe are likely to be valuable for creating custom roles. 
+You can go to the UI to view the permissions for each of our pre-built roles. In the lower-left corner of the [UI](https://one.newrelic.com), click on your name to open the user menu, and then go to **Administration > Access management > Roles**. Lists of permissions are available for the following roles:
 
-<img
-  title="New Relic user permissions screenshot"
-  alt="New Relic user permissions UI screenshot"
-  src={accountsUserManagementCapabilitiesUI}
-/>
-
-Note that permissions can change. The permissions in this doc were last updated April 3, 2023. 
+* All product admin
+* Standard user
+* Read only
 
 To learn more about specific permissions, select a category below, or try searching this doc for a specific term you're looking for.
 

src/content/docs/alerts-applied-intelligence/applied-intelligence/anomaly-detection/custom-anomalies.mdx

@@ -10,6 +10,7 @@ redirects:
 - /docs/alerts/new-relic-alerts/defining-conditions/create-anomaly-alert-conditions
 - /docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/create-anomaly-alert-conditions
 - /docs/alerts/new-relic-alerts/defining-conditions/create-anomaly-alert-conditions
+- /docs/alerts/new-relic-alerts/configuring-alert-policies/create-anomaly-alert-conditions/
 freshnessValidatedDate: never
 ---
 

src/content/docs/apis/nerdgraph/examples/nerdgraph-issues-api-via-github.mdx

@@ -716,19 +716,15 @@ The `issues` query allows you to paginate through all of your issues per account
                   "Anomaly: It was different from normal"
                 ]
               },
-
 ```
+
   </Collapser>
   <Collapser
      id="cursor"
      title="Cursor pagination"
    >
 
-In order to paginate through your data, you must include the `nextCursor` field on your initial query.
-
-With cursor pagination, you continue to make requests through the result data until the `nextCursor` returned from the response comes back empty. An empty response means you've arrived at the end of your results.
-
-Here's an example:
+Note that the maximum number of issues that can be returned through pagination is set by the NRQL [LIMIT MAX](/docs.newrelic.com/docs/nrql/nrql-syntax-clauses-functions/#sel-limit), and filtering will be required if this limit is exceeded. 
 
 ### Initial Request
 
@@ -1413,9 +1409,7 @@ The example below fetches `NewRelicIncident` incidents:
 ### Cursor pagination
 
 
-In order to paginate through your data, you must include the nextCursor field on your initial query.
-
-With cursor pagination, you continue to make a request through the result data until the nextCursor that is returned from the response comes back empty. It means you get to the end of your results.
+Note that the maximum number of incidents that can be returned through pagination is set by the NRQL [LIMIT MAX](/docs.newrelic.com/docs/nrql/nrql-syntax-clauses-functions/#sel-limit), and filtering will be required if this limit is exceeded.
 
 ### Filter Incidents
 

src/content/docs/apm/agents/java-agent/configuration/java-agent-configuration-config-file.mdx

@@ -4535,6 +4535,39 @@ Slow transaction detection is set in the `slow_transactions` and can be [overrid
 
     Determines how long a transaction has to take in milliseconds for a `SlowTransaction` event to be reported.
   </Collapser>
+
+<Collapser
+    id="cfg-evaluate_completed_transaction"
+    title="evaluate_completed_transaction"
+  >
+    <table>
+      <tbody>
+        <tr>
+          <th>
+            Type
+          </th>
+
+          <td>
+            Boolean
+          </td>
+        </tr>
+
+        <tr>
+          <th>
+            Default
+          </th>
+
+          <td>
+            `true`
+          </td>
+        </tr>
+      </tbody>
+    </table>
+
+    If this is set to true, every transaction will be checked for exceeding the defined threshold on
+    transaction completion. Note that if a large number of transactions exceed the threshold,
+    this can be computationally expensive since a stack trace is sent with every SlowTransaction event.
+  </Collapser>
 </CollapserGroup>
 
 ## Span events

src/content/docs/apm/agents/net-agent/configuration/net-agent-configuration.mdx

@@ -1786,13 +1786,53 @@ The `utilization` element supports the following attributes:
 Use these options to configure which elements of your application and environment to instrument. New Relic for .NET supports the following categories of instrumentation options:
 
 * [Instrumentation element](#instrumentation-element)
+* [Rules element](#instrumentation-rules)
 * [Applications element (instrumentation)](#application-instrumentation)
 * [Attributes element](#agent-attributes)
 
 ### Instrumentation element
 
 The `instrumentation` element is a child of the `configuration` element. By default, the .NET agent instruments IIS asp worker processes and Microsoft Azure web and worker roles. To instrument other processes, see [Instrumenting custom applications](/docs/agents/net-agent/features/instrumenting-custom-applications).
 
+### Rules element (instrumentation) [#instrumentation-rules]
+
+<Callout variant="important">
+This feature is available in .NET Agent 10.21.0 and above.
+</Callout>
+
+The `rules` element is a child of the `instrumentation` element. The `rules` element supports any number of `ignore` child elements, which instructs the Profiler to NOT instrument any methods defined in the specified assembly. Methods defined in other assemblies will still be instrumented.
+
+```xml
+<instrumentation>
+  <rules>
+    <ignore assemblyName="NameOfAssemblyToIgnore" />
+  </rules>
+</instrumentation>
+```
+
+The ignore rule allows you to optionally define a class name. In the following example, only methods defined in MyNamespace.MyClass in the assembly MyAssembly will be ignored. Other methods in other classes both inside that assembly and within other assemblies will not be ignored by the profiler.
+
+```xml
+<instrumentation>
+  <rules>
+    <ignore assemblyName="MyAssembly" className="MyNamespace.MyClass" />
+  </rules>
+</instrumentation>
+```
+
+More than one ignore rule can be specified. The following example disables both the Confluent Kafka and StackExchange Redis instrumentations.
+
+```xml
+<instrumentation>
+  <rules>
+    <ignore assemblyName="Confluent.Kafka" />
+    <ignore assemblyName="StackExchange.Redis" />
+  </rules>
+</instrumentation>
+```
+
+Please note that custom instrumentation cannot be ignored via the `rules` element.
+
 ### Applications element (instrumentation) [#application-instrumentation]
 
 The `applications` element is a child of the `instrumentation` element. The `applications` element supports `application` child elements which specify which non-web apps to instrument. The `application` element contains a `name` attribute.

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

@@ -89,11 +89,11 @@ Session traces help you understand:
 
     <tr>
       <td>
-        Core Web Vitals
+        Core web vitals
       </td>
 
       <td>
-        Look at the timing segments for first input delay and largest contentful paint to identify performance issues affecting your Core Web Vitals scores.
+        Look at the timing segments for interaction to next paint and largest contentful paint to identify performance issues affecting your [core web vitals](/docs/tutorial-improve-site-performance/guide-to-monitoring-core-web-vitals).
       </td>
     </tr>
 
@@ -230,11 +230,11 @@ The following table describes each segment of the session trace, with a link to
 
     <tr>
       <td>
-        [First input delay](/attribute-dictionary/?event=PageViewTiming&attribute=firstInputDelay)
+        [Interaction to next paint (INP)](/attribute-dictionary/?event=PageViewTiming&attribute=interactionToNextPaint)
       </td>
 
       <td>
-        Core Web Vitals: The time from when the request began to when the first browser response to user input was recorded.
+        Core web vitals: Measures how quickly a web page visually responds to user actions like clicks or taps.
       </td>
     </tr>
 

src/content/docs/browser/browser-monitoring/getting-started/browser-summary-page.mdx

@@ -22,7 +22,7 @@ import browserAddAlert from 'images/browser_screenshot-crop_browser-add-alert.we
 
 Our <InlinePopover type="browser" /> <DoNotTranslate>**Summary**</DoNotTranslate> page helps you troubleshoot issues with the real user browser performance of your app. Use the <DoNotTranslate>**Summary**</DoNotTranslate> page to:
 
-* Get core web vitals at a glance, including largest contentful paint (LCP), first input delay (FID), and cumulative layout shift (CLS).
+* Get core web vitals at a glance, including largest contentful paint (LCP), interaction to next paint (INP), and cumulative layout shift (CLS).
 * View trends in an app's browser-side performance.
 * Quickly troubleshoot page load timing issues.
 * Go directly to other browser UI pages to examine problems and issues in more detail.
@@ -48,7 +48,7 @@ To view a summary of a browser app's performance:
 Use the <DoNotTranslate>**Core web vitals**</DoNotTranslate> charts to understand how your browser performs according to [Google's Core Web Vitals](https://web.dev/vitals/#core-web-vitals). These include:
 
 * LCP: Largest contentful paint, which measures loading performance
-* FID: First input delay, which measures interactivity between user input and browser response
+* INP: Interaction to next paint, which measures interactivity between user input and browser response
 * CLS: Cumulative layout shift, which measures visual stability in the browser page
 
 Higher scores can help your organization save money and influence SEO. Lower scores can affect your users' perceptions of your organization's website, which could result in dissatisfied customers or lost business opportunities.
@@ -60,7 +60,7 @@ To learn more about monitoring core web vitals, see our [Guide to core web vital
 In addition to the charts with core web vitals data, evaluate your users' experience with your app by using the following data:
 
 * <DoNotTranslate>**User time on the site**</DoNotTranslate>
-* <DoNotTranslate>**User-centric page load times**</DoNotTranslate> and <DoNotTranslate>**Longest first input delay by URL**</DoNotTranslate>: To get more details about the [page load timing process](/docs/browser/new-relic-browser/page-load-timing-resources/page-load-timing-process), click the chart's title to go directly to the [<DoNotTranslate>**Page views**</DoNotTranslate> UI](/docs/browser/new-relic-browser/additional-standard-features/page-views-examine-page-performance).
+* <DoNotTranslate>**User-centric page load times**</DoNotTranslate> and <DoNotTranslate>**Longest interaction to next paint by URL**</DoNotTranslate>: To get more details about the [page load timing process](/docs/browser/new-relic-browser/page-load-timing-resources/page-load-timing-process), click the chart's title to go directly to the [<DoNotTranslate>**Page views**</DoNotTranslate> UI](/docs/browser/new-relic-browser/additional-standard-features/page-views-examine-page-performance).
 
 ## Locate browser performance problems [#performance]
 

src/content/docs/browser/new-relic-browser/browser-pro-features/browsers-problem-patterns-type-or-platform.mdx

@@ -37,7 +37,7 @@ In New Relic <InlinePopover type="browser" />, the <DoNotTranslate>**Browsers**<
 This page includes:
 
 * Top browsers by throughput (page views per minute or `ppm`) and page load time
-* Core Web Vitals data, including largest contentful paint (LCP), first input delay (FID), cumulative layout shift score (CSL), and more
+* Core web vitals data, including largest contentful paint (LCP), interaction to next paint (INP), cumulative layout shift score (CSL), and more
 * Top JavaScript errors by error, with a link to more details in the [JS errors UI](/docs/browser/new-relic-browser/browser-pro-features/javascript-errors-page-detect-analyze-errors/)
 * Filterable data by device type (mobile, tablet, desktop)
 

src/content/docs/browser/new-relic-browser/browser-pro-features/geography-webpage-metrics-location.mdx

@@ -47,7 +47,7 @@ Depending on the type of performance or usage data you select, the list next to
 To view or sort your browser monitoring performance data by location:
 
 1. Go to <DoNotTranslate>**[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Browser > **</DoNotTranslate> (select an app) <DoNotTranslate>**> Geography**</DoNotTranslate>.
-2. Use the dropdown to select the type of performance or usage data you want to view, such as page load or unique session count, average time for various processes, largest contentful paint, first input delay, cumulative layout shift, etc.
+2. Use the dropdown to select the type of performance or usage data you want to view, such as page load or unique session count, average time for various processes, largest contentful paint, interaction to next paint, cumulative layout shift, etc.
 3. To drill down to a specific area, mouse over or select any area on the geographical map, or select any of the locations on the list.
 4. To view specific performance data, [filter any attributes](#filter) below the funnel <Icon name="fe-filter"/> icon.
 5. To compare page load and network performance with historical data, review the charts below the map on the <DoNotTranslate>**Map view**</DoNotTranslate> and <DoNotTranslate>**Key attribute charts**</DoNotTranslate> tabs.

src/content/docs/browser/new-relic-browser/getting-started/browser-apps-index.mdx

@@ -23,8 +23,8 @@ The browser index page provides a list of your existing apps being monitored by
 ## Browser apps index features [#index]
 
 <img
-  title="browser_index.png"
-  alt="browser_index.png"
+  title="Browser index UI page"
+  alt="Screenshot of the browser index UI page"
   src={browserIndexSummary}
 />
 
@@ -125,8 +125,8 @@ Here are some tips for using the browser applications index.
         From any page in browser, select <DoNotTranslate>**Browser applications**</DoNotTranslate>, located above the name of your application.
 
         <img
-          title="browser_return_index.png"
-          alt="browser_return_index.png"
+          title="Return to browser index"
+          alt="Sreenshot of how to return to the browser index page"
           src={browserReturntoIndex}
         />
       </td>