Merge branch 'newrelic:develop' into patch-1

package.json

@@ -59,6 +59,7 @@
     "rehype-format": "^5.0.0",
     "rehype-parse": "^7.0.1",
     "rehype-remark": "^8.0.0",
+    "remark-gfm": "^3.0.1",
     "remark-rehype": "^8.0.0",
     "rss": "^1.2.2",
     "sequelize": "^6.21.3",

scripts/actions/deserialize-html.mjs

@@ -14,6 +14,7 @@ import { encode as htmlEncode } from 'html-entities';
 
 import handlers from './utils/handlers.mjs';
 import { configuration } from './configuration.js';
+import remarkGfm from 'remark-gfm';
 
 /**
  * Deserialize a node from the HTML AST into a node for the MDX AST.
@@ -142,6 +143,7 @@ const processor = unified()
   // remark-mdx must come before remark-stringify, because it adds handlers
   // for MDX nodes like `mdxJsxTextElement` and otherwise, remark-stringfy
   // won't know how to stringify those nodes.
+  .use(remarkGfm)
   .use(remarkMdx)
   .use(stringify, {
     bullet: '*',

scripts/actions/serialize-mdx.mjs

@@ -5,6 +5,7 @@ import toMDAST from 'remark-parse10';
 import frontmatter from 'remark-frontmatter5';
 import remarkMdx from 'remark-mdx2.3';
 import remark2rehype from 'remark-rehype10';
+import remarkGfm from 'remark-gfm';
 import addClasses from 'rehype-add-classes';
 import rehypeStringify from 'rehype-stringify10';
 import format from 'rehype-format';
@@ -42,6 +43,7 @@ const mdxSpanExpression = (h, node) => {
 const processor = unified()
   .use(toMDAST)
   .use(remarkMdx)
+  .use(remarkGfm)
   .use(frontmatter, ['yaml'])
   .use(fencedCodeBlock)
   .use(customHeadingIds)

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

@@ -126,7 +126,7 @@ To learn more about specific permissions, select a category below, or try search
     * <DNT>**Application settings**</DNT>: relates to browser application settings.
     * <DNT>**Domain conditions**</DNT>: relates to [browser domain conditions](/docs/browser/new-relic-browser/configuration/monitor-or-block-specific-domains-subdomains).
     * <DNT>**Segment allow lists**</DNT>: relates to segmenting [allow lists](/docs/browser/new-relic-browser/configuration/group-browser-metrics-urls).
-    * <DNT>**View session replays**</DNT>: relates to [viewing replays.](/docs/browser/browser-monitoring/browser-pro-features/session-replay).
+    * <DNT>**View session replays**</DNT>: relates to [viewing replays.](/docs/browser/browser-monitoring/browser-pro-features/session-replay/get-started).
   </Collapser>
 
   <Collapser

src/content/docs/accounts/accounts/automated-user-management/okta-scimsso-application-configuration.mdx

@@ -109,7 +109,7 @@ To manage your users' user type from Okta:
 
 4. Next, you'll configure your Okta user profile to have this field. Steps:
    * In the <DNT>**Profile editor**</DNT>, go to <DNT>**Users**</DNT> and click the <DNT>**User (default)**</DNT> profile.
-   * Add a new <DNT>**New Relic user type**</DNT> attribute to that profile ([see Okta user profile instructions](https://developer.okta.com/docs/concepts/user-profiles/#universal-directory-schemas)). How you set this will depend on your own setup and preferences for defining user type. Note that the expected values for user type are `Basic User`, `Core User`, and `Full User`. Below is an example with information filled in.
+   * Add a new <DNT>**New Relic user type**</DNT> attribute to that profile ([see Okta user profile instructions](https://developer.okta.com/docs/concepts/user-profiles/#universal-directory-schemas)). How you set this will depend on your own setup and preferences for defining user type. Note that the expected values for user type are `Basic User`, `Core User`, and `Full User`, which all are case sensitive. Below is an example with information filled in.
      <img title="Set Okta user profile to have new attribute" alt="Set Okta user profile to have new attribute" src="/images/accounts_screenshot-crop_Okta-add-user-type-to-profile.webp"/>
 
 5. In the <DNT>**People**</DNT> section, define the user type for your users. How you do this will depend on your setup and preferences. For example, you may choose to set this manually by setting each user’s user type, or you may use Okta to manage these in bulk.

src/content/docs/accounts/accounts/automated-user-management/tutorial-manage-users-groups-scim.mdx

@@ -529,13 +529,13 @@ Once your SCIM API integration is complete, all users brought into New Relic sta
 
 The user's type attribute is defined in the [custom schema](/docs/accounts/accounts/automated-user-management/scim-support-automated-user-management#user-type) `urn:ietf:params:scim:schemas:extension:newrelic:2.0:User`. Include this schema and the `nrUserType` string attribute in your create or update request to set a user's type.
 
-Valid values for `nrUserType` include:
+Valid values for `nrUserType` include, which all are case sensitive:
 
 * `Full User`
 * `Core User`
 * `Basic User`
 
-To create a new `Basic user` send a `POST` request `/scim/v2/Users` and include the custom New Relic schema extension:
+To create a new `Basic User` send a `POST` request `/scim/v2/Users` and include the custom New Relic schema extension:
 
 ```shell
 curl -X 'POST' -H 'Content-Type: application/json' -H "Authorization: Bearer $YOUR_TOKEN" 'https://scim-provisioning.service.newrelic.com/scim/v2/Users' --data-binary @- <<EOF

src/content/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx

@@ -276,21 +276,21 @@ version.
 | --- | --- | --- | --- |
 | `@apollo/gateway` | 2.3.0 | 2.9.3 | `@newrelic/[email protected]` |
 | `@apollo/server` | 4.0.0 | 4.11.3 | `@newrelic/[email protected]` |
-| `@aws-sdk/client-bedrock-runtime` | 3.474.0 | 3.731.1 | 11.13.0 |
-| `@aws-sdk/client-dynamodb` | 3.0.0 | 3.733.0 | 8.7.1 |
-| `@aws-sdk/client-sns` | 3.0.0 | 3.732.0 | 8.7.1 |
-| `@aws-sdk/client-sqs` | 3.0.0 | 3.731.1 | 8.7.1 |
-| `@aws-sdk/lib-dynamodb` | 3.377.0 | 3.733.0 | 8.7.1 |
+| `@aws-sdk/client-bedrock-runtime` | 3.474.0 | 3.738.0 | 11.13.0 |
+| `@aws-sdk/client-dynamodb` | 3.0.0 | 3.738.0 | 8.7.1 |
+| `@aws-sdk/client-sns` | 3.0.0 | 3.738.0 | 8.7.1 |
+| `@aws-sdk/client-sqs` | 3.0.0 | 3.738.0 | 8.7.1 |
+| `@aws-sdk/lib-dynamodb` | 3.377.0 | 3.738.0 | 8.7.1 |
 | `@aws-sdk/smithy-client` | 3.47.0 | 3.374.0 | 8.7.1 |
 | `@elastic/elasticsearch` | 7.16.0 | 8.17.0 | 11.9.0 |
 | `@grpc/grpc-js` | 1.4.0 | 1.12.5 | 8.17.0 |
 | `@hapi/hapi` | 20.1.2 | 21.3.12 | 9.0.0 |
 | `@koa/router` | 11.0.2 | 13.1.0 | 3.2.0 |
-| `@langchain/core` | 0.1.17 | 0.3.33 | 11.13.0 |
+| `@langchain/core` | 0.1.17 | 0.3.37 | 11.13.0 |
 | `@nestjs/cli` | 9.0.0 | 11.0.2 | 10.1.0 |
-| `@opensearch-project/opensearch` | 2.1.0 | 3.1.0 | 12.10.0 |
-| `@prisma/client` | 5.0.0 | 6.2.1 | 11.0.0 |
-| `@smithy/smithy-client` | 2.0.0 | 4.1.2 | 11.0.0 |
+| `@opensearch-project/opensearch` | 2.1.0 | 3.2.0 | 12.10.0 |
+| `@prisma/client` | 5.0.0 | 6.3.0 | 11.0.0 |
+| `@smithy/smithy-client` | 2.0.0 | 4.1.3 | 11.0.0 |
 | `amqplib` | 0.5.0 | 0.10.5 | 2.0.0 |
 | `apollo-server` | 3.0.0 | 3.13.0 | `@newrelic/[email protected]` |
 | `apollo-server-express` | 3.0.0 | 3.13.0 | `@newrelic/[email protected]` |
@@ -312,7 +312,7 @@ version.
 | `mysql` | 2.2.0 | 2.18.1 | 1.32.0 |
 | `mysql2` | 2.0.0 | 3.12.0 | 1.32.0 |
 | `next` | 13.4.19 | 15.1.6 | 12.0.0 |
-| `openai` | 4.0.0 | 4.80.0 | 11.13.0 |
+| `openai` | 4.0.0 | 4.81.0 | 11.13.0 |
 | `pg` | 8.2.0 | 8.13.1 | 9.0.0 |
 | `pg-native` | 3.0.0 | 3.2.0 | 9.0.0 |
 | `pino` | 7.0.0 | 9.6.0 | 8.11.0 |

src/content/docs/apm/agents/php-agent/getting-started/php-agent-compatibility-requirements.mdx

@@ -31,6 +31,11 @@ Before you [install the PHP agent](/docs/apm/agents/php-agent/installation), mak
     </tr>
   </thead>
   <tbody>
+    <tr>
+      <td>8.4</td>
+      <td>&ge; [11.5.0.18](/docs/release-notes/agent-release-notes/php-release-notes/php-agent-11-5-0-18/)</td>
+      <td>Yes</td>
+    </tr>
     <tr>
       <td>8.3</td>
       <td>&ge; [10.15.0.4](/docs/release-notes/agent-release-notes/php-release-notes/php-agent-10-15-0-4/)</td>

src/content/docs/apm/agents/python-agent/getting-started/compatibility-requirements-python-agent.mdx

@@ -51,7 +51,7 @@ If you don't have one already, [create a New Relic account](https://newrelic.com
       </td>
 
       <td>
-        Python (CPython/PyPy) versions supported: 3.7, 3.8, 3.9, 3.10, 3.11, and 3.12.
+        Python (CPython/PyPy) versions supported: 3.7, 3.8, 3.9, 3.10, 3.11, 3.12, and 3.13.
 
         Recommendation: Use Python version 3.7 or higher with our agent.
 
@@ -178,15 +178,15 @@ The following are proposed time ranges. The actual release date may vary.
   <tbody>
     <tr>
       <td>
-        3.12
+        3.14
       </td>
 
       <td>
-        October 2023
+        October 2025
       </td>
 
       <td>
-        November 2023
+        November 2025
       </td>
     </tr>
   </tbody>

src/content/docs/apm/agents/python-agent/python-agent-api/datastoretrace-python-agent-api.mdx

@@ -24,7 +24,7 @@ Used to instrument calls to datastores.
 
 ## Description
 
-`datastore_trace` is used to add more detail to your [transaction traces](/docs/accounts-partnerships/education/getting-started-new-relic/glossary#transaction-trace) in the form of additional segments. Any calls reported with `datastore_trace` will appear on the [APM Databases page](/docs/apm/applications-menu/monitoring/databases-slow-queries-page). `datastore_trace` returns a [partial](https://docs.python.org/3.7/library/functools.html#functools.partial) of `DatastoreTraceWrapper` that can be used as a decorator for a function to time calls to your datastore.
+`datastore_trace` is used to add more detail to your [transaction traces](/docs/accounts-partnerships/education/getting-started-new-relic/glossary#transaction-trace) in the form of additional segments. Any calls reported with `datastore_trace` will appear on the [APM Databases page](/docs/apm/applications-menu/monitoring/databases-slow-queries-page). `datastore_trace` returns a [partial](https://docs.python.org/3.12/library/functools.html#functools.partial) of `DatastoreTraceWrapper` that can be used as a decorator for a function to time calls to your datastore.
 
 The `datastore_trace` decorator can be used on generators and coroutines with agent version 2.102.0.85 or higher. Timing of these objects begins when consumption starts, and ends when the object is exhausted or goes out of scope. This is a change from earlier versions where the metric represented the time taken to create the generator or coroutine object itself.
 

src/content/docs/apm/agents/python-agent/python-agent-api/externaltrace-python-agent-api.mdx

@@ -23,7 +23,7 @@ Report calls to external services as transaction trace segments.
 
 ## Description
 
-`external_trace` is used to add more detail to your [transaction traces](/docs/accounts-partnerships/education/getting-started-new-relic/glossary#transaction-trace) in the form of additional segments. Any calls reported with `external_trace` will appear on the externals tab in APM. `external_trace` returns a [partial](https://docs.python.org/3.7/library/functools.html#functools.partial) of `ExternalTraceWrapper` that can be used as a decorator for a function that calls an external service.
+`external_trace` is used to add more detail to your [transaction traces](/docs/accounts-partnerships/education/getting-started-new-relic/glossary#transaction-trace) in the form of additional segments. Any calls reported with `external_trace` will appear on the externals tab in APM. `external_trace` returns a [partial](https://docs.python.org/3.12/library/functools.html#functools.partial) of `ExternalTraceWrapper` that can be used as a decorator for a function that calls an external service.
 
 The `external_trace` decorator can be used on generators and coroutines with agent version 2.102.0.85 or higher. Timing of these objects begins when consumption starts, and ends when the object is exhausted or goes out of scope. This is a change from earlier versions where the metric represented the time taken to create the generator or coroutine object itself.
 

src/content/docs/apm/agents/python-agent/python-agent-api/initialize-python-agent-api.mdx

@@ -101,7 +101,7 @@ If you call `initialize` with no arguments, you must have already specified your
       </td>
 
       <td>
-        Optional. Sets the logging level. The agent uses [Python's logging module](https://docs.python.org/3.7/library/logging.html#logging-levels). Options are the same as for the [`log_level`](/docs/agents/python-agent/installation-configuration/python-agent-configuration#log_level) option in config file.
+        Optional. Sets the logging level. The agent uses [Python's logging module](https://docs.python.org/3.12/library/logging.html#logging-levels). Options are the same as for the [`log_level`](/docs/agents/python-agent/installation-configuration/python-agent-configuration#log_level) option in config file.
       </td>
     </tr>
   </tbody>

src/content/docs/apm/agents/python-agent/python-agent-api/messagetrace-python-agent-api.mdx

@@ -31,7 +31,7 @@ Agent version 2.88.0.72 or higher.
 
 ## Description
 
-[`message_transaction`](/docs/agents/python-agent/python-agent-api/message_transaction) (and its associated calls) report message functions as [transactions](/docs/accounts-partnerships/education/getting-started-new-relic/glossary#transaction). `message_trace` is used to add more detail to your [transaction traces](/docs/accounts-partnerships/education/getting-started-new-relic/glossary#transaction-trace) in the form of additional segments. `message_trace` returns a [partial](https://docs.python.org/3.7/library/functools.html#functools.partial) of `MessageTraceWrapper` that can be used as a decorator for a message function.
+[`message_transaction`](/docs/agents/python-agent/python-agent-api/message_transaction) (and its associated calls) report message functions as [transactions](/docs/accounts-partnerships/education/getting-started-new-relic/glossary#transaction). `message_trace` is used to add more detail to your [transaction traces](/docs/accounts-partnerships/education/getting-started-new-relic/glossary#transaction-trace) in the form of additional segments. `message_trace` returns a [partial](https://docs.python.org/3.12/library/functools.html#functools.partial) of `MessageTraceWrapper` that can be used as a decorator for a message function.
 
 The `message_trace` decorator can be used on generators and coroutines with agent version 2.102.0.85 or higher. Timing of these objects begins when consumption starts, and ends when the object is exhausted or goes out of scope. This is a change from earlier versions where the metric represented the time taken to create the generator or coroutine object itself.
 

src/content/docs/apm/agents/python-agent/python-agent-api/messagetransaction-python-agent-api.mdx

@@ -31,7 +31,7 @@ Agent version 2.88.0.72 or higher.
 
 ## Description
 
-This decorator returns a [partial](https://docs.python.org/3.7/library/functools.html#functools.partial) of `MessageTransactionWrapper` that can be used as a decorator for a messaging function. When used, the returned decorator records a message transaction and its message-related [attributes](/docs/accounts-partnerships/education/getting-started-new-relic/glossary#attribute).
+This decorator returns a [partial](https://docs.python.org/3.12/library/functools.html#functools.partial) of `MessageTransactionWrapper` that can be used as a decorator for a messaging function. When used, the returned decorator records a message transaction and its message-related [attributes](/docs/accounts-partnerships/education/getting-started-new-relic/glossary#attribute).
 
 If the decorator will not work in your application, you can use one of the following:
 

src/content/docs/apm/agents/python-agent/python-agent-api/profiletrace-python-agent-api.mdx

@@ -24,7 +24,7 @@ Adds additional attributes to function trace names.
 
 ## Description
 
-`profile_trace` is used to add more detail to your [transaction traces](/docs/accounts-partnerships/education/getting-started-new-relic/glossary#transaction-trace) in the form of additional segments. Any calls reported with `profile_trace` will appear on the [APM Databases page](/docs/apm/applications-menu/monitoring/databases-slow-queries-page). `profile_trace` returns a [partial](https://docs.python.org/3.7/library/functools.html#functools.partial) of `ProfileTraceWrapper` that can be used as a decorator for a function to time calls to your profiler.
+`profile_trace` is used to add more detail to your [transaction traces](/docs/accounts-partnerships/education/getting-started-new-relic/glossary#transaction-trace) in the form of additional segments. Any calls reported with `profile_trace` will appear on the [APM Databases page](/docs/apm/applications-menu/monitoring/databases-slow-queries-page). `profile_trace` returns a [partial](https://docs.python.org/3.12/library/functools.html#functools.partial) of `ProfileTraceWrapper` that can be used as a decorator for a function to time calls to your profiler.
 
 If you cannot use the decorator in your application, you can use the following call format: The wrapper form is `ProfileTraceWrapper`. It can be used to return a wrapped function without the use of a decorator.
 

src/content/docs/apm/agents/ruby-agent/api-guides/guide-using-ruby-agent-api.mdx

@@ -16,10 +16,10 @@ redirects:
 freshnessValidatedDate: never
 ---
 
-The New Relic <DNT>Ruby</DNT> agent provides a public API with documentation available on GitHub. The GitHub documentation tells you how to set up custom instrumentation of your <DNT>Ruby</DNT> app and collect more in-depth data:
+The New Relic <DNT>Ruby</DNT> agent provides a public API with documentation available on RubyDoc. The RubyDoc documentation tells you how to set up custom instrumentation of your <DNT>Ruby</DNT> app and collect more in-depth data:
 
-* [Overview](https://rubydoc.info/github/newrelic/newrelic-ruby-agent)
-* [Public API methods](https://rubydoc.info/github/newrelic/newrelic-ruby-agent/NewRelic/Agent)
+* [Overview](https://www.rubydoc.info/gems/newrelic_rpm/)
+* [Public API methods](https://www.rubydoc.info/gems/newrelic_rpm/NewRelic/Agent)
 
 The following sections explain common goals, solutions, and links to relevant parts of the documentation.