From 0ba5e7de0f14b7a8ba26bd57a61802a0633c3dc7 Mon Sep 17 00:00:00 2001
From: svc-docs-eng-opensource-bot <svc-docs-eng-opensource-bot@newrelic.com>
Date: Tue, 7 Jan 2025 12:04:37 +0000
Subject: [PATCH] chore: add translations

---
 .../docs/alerts/get-notified/destinations.mdx | 48 ++++++++-----------
 .../browser-pro-features/session-replay.mdx   |  2 +-
 .../connect/set-up-aws-api-polling.mdx        |  2 +-
 ...ware-tanzu-firehose-nozzle-integration.mdx |  4 +-
 ...ware-tanzu-nginx-buildpack-integration.mdx | 12 ++---
 ...mware-tanzu-service-broker-integration.mdx |  2 +-
 .../monitoring-jenkins-ot.mdx                 | 32 +++++++++++++
 ...hentication-domains-saml-sso-scim-more.mdx |  4 +-
 .../docs/alerts/get-notified/destinations.mdx | 46 ++++++++----------
 .../browser-pro-features/session-replay.mdx   |  4 ++
 ...ware-tanzu-firehose-nozzle-integration.mdx |  4 +-
 ...ware-tanzu-nginx-buildpack-integration.mdx | 12 ++---
 ...mware-tanzu-service-broker-integration.mdx |  2 +-
 .../monitoring-jenkins-ot.mdx                 | 32 +++++++++++++
 ...hentication-domains-saml-sso-scim-more.mdx |  4 +-
 .../docs/alerts/get-notified/destinations.mdx | 46 ++++++++----------
 ...ompatibility-requirements-nodejs-agent.mdx |  2 +-
 .../browser-pro-features/session-replay.mdx   |  4 ++
 .../connect/set-up-aws-api-polling.mdx        |  2 +-
 ...ware-tanzu-firehose-nozzle-integration.mdx |  4 +-
 ...ware-tanzu-nginx-buildpack-integration.mdx | 36 +++++++-------
 ...mware-tanzu-service-broker-integration.mdx |  2 +-
 .../monitoring-jenkins-ot.mdx                 | 32 +++++++++++++
 ...hentication-domains-saml-sso-scim-more.mdx |  4 +-
 .../docs/alerts/get-notified/destinations.mdx | 48 ++++++++-----------
 ...ompatibility-requirements-nodejs-agent.mdx |  2 +-
 .../browser-pro-features/session-replay.mdx   |  4 ++
 .../connect/set-up-aws-api-polling.mdx        |  2 +-
 ...ware-tanzu-firehose-nozzle-integration.mdx |  4 +-
 ...ware-tanzu-nginx-buildpack-integration.mdx | 12 ++---
 ...mware-tanzu-service-broker-integration.mdx |  2 +-
 .../monitoring-jenkins-ot.mdx                 | 32 +++++++++++++
 32 files changed, 280 insertions(+), 168 deletions(-)

diff --git a/src/i18n/content/es/docs/alerts/get-notified/destinations.mdx b/src/i18n/content/es/docs/alerts/get-notified/destinations.mdx
index c7f346330b7..cc5c13c2d90 100644
--- a/src/i18n/content/es/docs/alerts/get-notified/destinations.mdx
+++ b/src/i18n/content/es/docs/alerts/get-notified/destinations.mdx
@@ -16,12 +16,23 @@ La configuración de destino contiene los detalles de la conexión para integrar
 La plataforma de destino admitida incluye:
 
 * Atlassian Jira: Disponible en [flujo de trabajo](/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/incident-workflows/), [Errors Inbox](/docs/errors-inbox/).
+
 * ServiceNow: Disponible en [flujo de trabajo](/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/incident-workflows/).
+
 * Slack: Disponible en [flujo de trabajo](/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/incident-workflows/), [Errors Inbox](/docs/errors-inbox/) y [Discusiones](/docs/new-relic-solutions/new-relic-one/ui-data/collaborate/collaboration-slack-integration/).
+
 * Webhook: Disponible en [flujo de trabajo](/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/incident-workflows/).
+
+  <Callout variant="important">
+    Si emplea conectores basados en webhooks de Microsoft Office 365 en Teams para las alertas de New Relic, debe actualizar las URL de los webhooks al nuevo formato antes del 31 de enero de 2025. Para obtener más información sobre cómo actualizar la URL del webhook, consulte [Fin de vida útil (EOL) de Microsoft para los conectores de Office 365 en Teams](https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/).
+  </Callout>
+
 * Correo electrónico: Disponible en [flujo de trabajo](/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/incident-workflows/) y [Discusiones](/docs/new-relic-solutions/new-relic-one/ui-data/collaborate/collaborate-with-teammates/).
+
 * AWS EventBridge: Disponible en [flujo de trabajo](/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/incident-workflows/).
+
 * PagerDuty: Disponible en [flujo de trabajo](/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/incident-workflows/).
+
 * New Relic Mobile Push: Disponible en [flujo de trabajo](/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/incident-workflows/).
 
 Para más información sobre estos y otros destinos, consulte [notificación integración](/docs/alerts-applied-intelligence/notifications/notification-integrations).
@@ -35,30 +46,13 @@ La configuración de destino requiere [permisos](/docs/accounts/accounts-billing
 
 ## Gestionar destinos [#manage-destinations]
 
-<img
-  title="Destinations overview page"
-  alt="Destinations overview page."
-  src="/images/accounts_screenshot-full_destinations-overview.webp"
-/>
+<img title="Destinations overview page" alt="Destinations overview page." src="/images/accounts_screenshot-full_destinations-overview.webp" />
 
 <figcaption>
-  Vaya a <DNT>**[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Alerts > Destinations**</DNT>. Utilice destinos para elegir dónde se envía su notificación.
+  Vaya a <DNT>**[one.newrelic.com &gt; All capabilities](https://one.newrelic.com/all-capabilities) &amp;gt; Alerts &amp;gt; Destinations**</DNT>. Utilice destinos para elegir dónde se envía su notificación.
 </figcaption>
 
-1. Vaya a
-
-   <DNT>
-     **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Alerts > Enrich and Notify > Destinations**
-   </DNT>
-
-   . La tabla
-
-   <DNT>
-     **Destinations**
-   </DNT>
-
-   muestra información sobre los destinos existentes y permite al usuario habilitarlos, deshabilitarlos y modificarlos.
-
+1. Vaya a <DNT>**[one.newrelic.com &gt; All capabilities](https://one.newrelic.com/all-capabilities) &amp;gt; Alerts &amp;gt; Enrich and Notify &amp;gt; Destinations**</DNT>. La tabla <DNT>**Destinations**</DNT> muestra información sobre los destinos existentes y permite al usuario habilitarlos, deshabilitarlos y modificarlos.
 2. Para agregar un destino, haga clic en el mosaico de la plataforma correspondiente. Para modificar la configuración de destino, haga clic en la fila de destino en la tabla de destinos.
 
 También puedes configurar destinos con nuestra [API NerdGraph](/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-destinations).
@@ -84,14 +78,10 @@ Estados disponibles:
 
 Puede ver el estado del destino en la tabla <DNT>**Destinations**</DNT> y en el paso <DNT>**Select a destination**</DNT> mientras configura la plantilla del canal. También puedes revisar el estado usando la API de Nerdgraph con la propiedad `status` .
 
-<img
-  title="Destination status in the Destinations table."
-  alt="Destination status in the Destinations table."
-  src="/images/accounts_screenshot-full_destinations-status.webp"
-/>
+<img title="Destination status in the Destinations table." alt="Destination status in the Destinations table." src="/images/accounts_screenshot-full_destinations-status.webp" />
 
 <figcaption>
-  Vaya a <DNT>**[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Alerts > Destinations**</DNT>. Haga clic en la pestaña <DNT>**Destinations**</DNT> para ver la tabla de destinos.
+  Vaya a <DNT>**[one.newrelic.com &gt; All capabilities](https://one.newrelic.com/all-capabilities) &amp;gt; Alerts &amp;gt; Destinations**</DNT>. Haga clic en la pestaña <DNT>**Destinations**</DNT> para ver la tabla de destinos.
 </figcaption>
 
 ### Log de notificaciones de problemas [#notifications-log]
@@ -104,7 +94,9 @@ Si, por algún motivo, un evento de notificación no se envía, el error consigu
 
 Esto es especialmente útil si se utiliza la característica <DNT>**Alert conditions (policies)**</DNT> y [flujo de trabajo](/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/incident-workflows/) . De esta manera, puede crear una condición que se active en caso de un error de notificación y se puede enviar una nueva notificación a otro lugar.
 
-A continuación se puede encontrar una demostración paso a paso de cómo agregar un notificador de errores:<Video type="wistia" id="b89ctyjolq"/>
+A continuación se muestra una demostración paso a paso de cómo agregar un notificador de errores:
+
+<Video type="wistia" id="b89ctyjolq" />
 
 Condición de ejemplo:
 
@@ -118,4 +110,4 @@ Luego, puede usar esta condición en el generador de consultas de la configuraci
 
 ### Destino pospuesto [#Snoozed-destination]
 
-Posponer: Para minimizar el ruido de error en destinos defectuosos, "posponemos" los destinos. Si falla el envío de una notificación a un destino específico en un período de dos horas, "posponemos" el destino durante unos minutos. En este período no enviaremos notificaciones a ese destino.
+Posponer: Para minimizar el ruido de error en destinos defectuosos, &quot;posponemos&quot; los destinos. Si falla el envío de una notificación a un destino específico en un período de dos horas, &quot;posponemos&quot; el destino durante unos minutos. En este período no enviaremos notificaciones a ese destino.
\ No newline at end of file
diff --git a/src/i18n/content/es/docs/browser/browser-monitoring/browser-pro-features/session-replay.mdx b/src/i18n/content/es/docs/browser/browser-monitoring/browser-pro-features/session-replay.mdx
index ae4d6c596bc..3a9dde99859 100644
--- a/src/i18n/content/es/docs/browser/browser-monitoring/browser-pro-features/session-replay.mdx
+++ b/src/i18n/content/es/docs/browser/browser-monitoring/browser-pro-features/session-replay.mdx
@@ -174,7 +174,7 @@ Para obtener más detalles sobre Session Replay, consulte las siguientes seccion
 </Steps>
 
 <Callout variant="important">
-  Certain setting, including enabling or disabling the session replay and adjusting sample rates for overall and errors, have been moved to server-side configuration. For example, After you update these settings for copy/paste installation method, there&apos;s no need to redeploy the script. This is applicable for browser agent version `1.259.0` or higher.
+  Certain settings, including enabling or disabling session replay and adjusting sample rates for overall and errors, have been moved to server-side configuration. For example, after you update these settings for copy/paste installation method, there&apos;s no need to redeploy the script. This is applicable for browser agent version `1.259.0` or higher.
 </Callout>
 
 ## Resolución de problemas [#troubleshoot]
diff --git a/src/i18n/content/es/docs/infrastructure/amazon-integrations/connect/set-up-aws-api-polling.mdx b/src/i18n/content/es/docs/infrastructure/amazon-integrations/connect/set-up-aws-api-polling.mdx
index b61bdb1d06e..cbce494193f 100644
--- a/src/i18n/content/es/docs/infrastructure/amazon-integrations/connect/set-up-aws-api-polling.mdx
+++ b/src/i18n/content/es/docs/infrastructure/amazon-integrations/connect/set-up-aws-api-polling.mdx
@@ -24,7 +24,7 @@ Para los usuarios AWS que quieran recopilar datos sobre todos los demás servici
 * El intervalo de sondeo más rápido para el sondeo API es de 5 minutos, mientras que CloudWatch Metric Streams realiza transmisiones métricas en menos de 2 minutos.
 * AWS limita el sondeo de API, mientras que la integración de CloudWatch Metric Streams elimina la limitación de API por completo.
 
-Consulte nuestra documentación para [instalar la integración de New Relic CloudWatch Metric Streams ](/docs/infrastructure/amazon-integrations/connect/aws-metric-stream-setup)o para [migrar su integración de sondeo API a CloudWatch Metric Streams](/docs/infrastructure/amazon-integrations/connect/aws-metric-stream-setup/#migrate).
+Consulta nuestra documentación para [instalar una integración de New Relic CloudWatch Metric Streams ](/install/aws-cloudwatch)o para [migrar tu integración de sondeo API a CloudWatch Metric Streams](/install/aws-cloudwatch/?task=migrate).
 
 ## Configurar el sondeo de API [#set-up-api]
 
diff --git a/src/i18n/content/es/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-firehose-nozzle-integration.mdx b/src/i18n/content/es/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-firehose-nozzle-integration.mdx
index e1392fa6a89..97d3a9c78e5 100644
--- a/src/i18n/content/es/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-firehose-nozzle-integration.mdx
+++ b/src/i18n/content/es/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-firehose-nozzle-integration.mdx
@@ -26,7 +26,7 @@ New Relic para VMware Tanzu tiene los siguientes requisitos:
 
 * Una cuenta New Relic activa con una licencia Pro o Pro Trial. Si aún no tienes una cuenta de New Relic, puedes obtener una [licencia de prueba gratuita de 14 días](http://newrelic.com/signup?funnel=pivotal-cloud-foundry&partner=Pivotal+Cloud+Foundry).
 * New Relic Insights incluida en la licencia
-* VMware Tanzu versiones v2.10.x a v6.0.x.
+* VMware Tanzu versiones v2.10.x a v10.0.x.
 
 ## Característica clave [#key-features]
 
@@ -128,7 +128,7 @@ La siguiente tabla proporciona información sobre la versión y la compatibilida
       </td>
 
       <td>
-        versión 2.10.x, v2.11.x, v2.12.x, v2.13.x, v3.0.x, v4.0.x, v5.0.x y v6.0.x
+        versión 2.10.x, v2.11.x, v2.12.x, v2.13.x, v3.0.x, v4.0.x, v5.0.x, v6.0.x y v10.0.x
       </td>
     </tr>
 
diff --git a/src/i18n/content/es/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-nginx-buildpack-integration.mdx b/src/i18n/content/es/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-nginx-buildpack-integration.mdx
index ca763167bad..61ef124cdbe 100644
--- a/src/i18n/content/es/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-nginx-buildpack-integration.mdx
+++ b/src/i18n/content/es/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-nginx-buildpack-integration.mdx
@@ -15,7 +15,7 @@ Optimice el monitoreo y la resolución de problemas de NGINX con el paquete de c
 
 ## Requisitos y compatibilidad [#requirements-compatibility]
 
-Este producto fue probado y es compatible con VMware Tanzu OpsManager versiones hasta v3.0 inclusive y Tanzu aplicación Service 4.0, 5.0 y 6.0.
+Certificamos el producto con VMware Tanzu OpsManager versiones hasta v3.0.x, y Tanzu aplicación Service versiones 4.x, 5.x, 6.x y 10.x.
 
 El paquete de compilación de integración New Relic NGINX para VMware Tanzu requiere lo siguiente:
 
@@ -49,7 +49,7 @@ La siguiente tabla proporciona información de compatibilidad de versiones sobre
       </td>
 
       <td>
-        1.0.2
+        1.1.2
       </td>
     </tr>
 
@@ -59,7 +59,7 @@ La siguiente tabla proporciona información de compatibilidad de versiones sobre
       </td>
 
       <td>
-        9 de agosto de 2024
+        6 de enero de 2025
       </td>
     </tr>
 
@@ -69,7 +69,7 @@ La siguiente tabla proporciona información de compatibilidad de versiones sobre
       </td>
 
       <td>
-        Paquete de integración de NGINX de New Relic para VMware Tanzu 1.0.2
+        Paquete de integración de NGINX de New Relic para VMware Tanzu 1.1.2
       </td>
     </tr>
 
@@ -89,7 +89,7 @@ La siguiente tabla proporciona información de compatibilidad de versiones sobre
       </td>
 
       <td>
-        4.0.x, 5.0.x y 6.0.x
+        4.x, 5.x, 6.x y 10.x
       </td>
     </tr>
 
@@ -136,7 +136,7 @@ Puede instalar los paquetes de compilación como un mosaico en Ops Manager o ind
     <TabsPageItem id="ops-manager-tile">
       <Steps>
         <Step>
-          Descargue la última versión del mosaico (actualmente `newrelic-nginx-buildpack-1.0.1.pivotal`) desde el [sitio de descarga de Broadcom](https://support.broadcom.com/group/ecx/productdownloads?subfamily=New%20Relic%20Nginx%20Integration%20Buildpack%20for%20VMware%20Tanzu) o desde [el repositorio de GitHub de New Relic en versiones](https://github.com/newrelic/newrelic-pcf-nginx-buildpack/releases).
+          Descargue la última versión del mosaico (actualmente `newrelic-nginx-buildpack-1.1.2.pivotal`) desde el [sitio de descarga de Broadcom](https://support.broadcom.com/group/ecx/productdownloads?subfamily=New%20Relic%20Nginx%20Integration%20Buildpack%20for%20VMware%20Tanzu) o desde [el repositorio de GitHub de New Relic en versiones](https://github.com/newrelic/newrelic-pcf-nginx-buildpack/releases).
         </Step>
 
         <Step>
diff --git a/src/i18n/content/es/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-service-broker-integration.mdx b/src/i18n/content/es/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-service-broker-integration.mdx
index 6c79d508784..ac5b65bc05e 100644
--- a/src/i18n/content/es/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-service-broker-integration.mdx
+++ b/src/i18n/content/es/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-service-broker-integration.mdx
@@ -109,7 +109,7 @@ La siguiente tabla proporciona información sobre la versión y la compatibilida
       </td>
 
       <td>
-        2.10.x, 2.11.x, 2.12.x, 2.13.x, 3.x, 4.x, 5.x, 6.x, and 10.x
+        2.10.x, 2.11.x, 2.12.x, 2.13.x, 3.x, 4.x, 5.x, 6.x y 10.x
       </td>
     </tr>
 
diff --git a/src/i18n/content/es/docs/infrastructure/other-infrastructure-integrations/monitoring-jenkins-ot.mdx b/src/i18n/content/es/docs/infrastructure/other-infrastructure-integrations/monitoring-jenkins-ot.mdx
index eae9407bfde..bcec8c8fcdd 100644
--- a/src/i18n/content/es/docs/infrastructure/other-infrastructure-integrations/monitoring-jenkins-ot.mdx
+++ b/src/i18n/content/es/docs/infrastructure/other-infrastructure-integrations/monitoring-jenkins-ot.mdx
@@ -83,4 +83,36 @@ Después de haber enviado los datos de su canalización de Jenkins a New Relic,
   New Relic no mantiene el complemento Jenkins OpenTelemetry, por lo que si tiene algún problema con la instrumentación, [cree un nuevo problema en el repositorio de GitHub del complemento](https://github.com/jenkinsci/opentelemetry-plugin/issues).
 </Callout>
 
+## Atributo de recurso y etiqueta [#attributes]
+
+Puede agregar el atributo de recurso a la configuración del complemento Jenkins. Esto le permite incluir atributos para todos los datos de log, métricas y trazas generados por el complemento. El atributo de recurso que tiene nombres que comienzan con `tags.` también agregará [la etiqueta de entidad a su entidad de Jenkins](/docs/opentelemetry/best-practices/opentelemetry-best-practices-resources/#tags).
+
+Puedes definir atributo de dos maneras:
+
+<CollapserGroup>
+  <Collapser id="attributes-config" title="Definir atributo en la configuración del complemento Jenkins">
+    Puede agregar el atributo de recurso al elemento `configurationProperties` en el archivo `io.jenkins.plugins.opentelemetry.JenkinsOpenTelemetryPluginConfiguration.xml` .
+
+    Ejemplo:
+
+    ```xml
+      <configurationProperties>
+        otel.resource.attributes=attribute1=value1,attribute2=value2,tags.tag1=tagValue1
+      </configurationProperties>
+    ```
+  </Collapser>
+
+  <Collapser id="attributes-env" title="Definir atributo en las variables de entorno">
+    Puede definir el atributo de recurso empleando la variable de entorno `OTEL_RESOURCE_ATTRIBUTES` .
+
+    Esto se puede hacer en un sistema Ubuntu editando la configuración de systemctl para jenkins usando `systemctl edit jenkins` y agregando a la parte override.conf de la configuración:
+
+    ```yml
+      [Service]
+      # Set OTel Environment Options
+      Environment="OTEL_RESOURCE_ATTRIBUTES=attribute1=value1,attribute2=value2,tags.tag1=tagValue1"
+    ```
+  </Collapser>
+</CollapserGroup>
+
 <InstallFeedback />
\ No newline at end of file
diff --git a/src/i18n/content/jp/docs/accounts/accounts-billing/new-relic-one-user-management/authentication-domains-saml-sso-scim-more.mdx b/src/i18n/content/jp/docs/accounts/accounts-billing/new-relic-one-user-management/authentication-domains-saml-sso-scim-more.mdx
index 611a857c7c7..f7d9773eefd 100644
--- a/src/i18n/content/jp/docs/accounts/accounts-billing/new-relic-one-user-management/authentication-domains-saml-sso-scim-more.mdx
+++ b/src/i18n/content/jp/docs/accounts/accounts-billing/new-relic-one-user-management/authentication-domains-saml-sso-scim-more.mdx
@@ -80,9 +80,9 @@ New Relic 組織を作成するときのデフォルトの認証設定は次の
 
 認証ドメインを表示および構成するには、[ユーザー メニュー](/docs/accounts/accounts-billing/general-account-settings/intro-account-settings)から<DNT>**Administration &gt; Authentication domains**</DNT>に移動します。
 
-既存のドメインがある場合は、左に表示されます。ほとんどの組織では、せいぜい2つまたは3つのドメインを持っていることに注意してください。1つは手動のデフォルト設定、1つまたは2つはIDプロバイダーに関連する設定です。
+既存のドメインがある場合は、テーブルに表示されます。 ほとんどの組織では、最大で 2 つまたは 3 つのドメイン (手動のデフォルト設定用のドメイン 1 つと、ID プロバイダー関連の設定用のドメイン 1 つまたは 2 つ) が存在することに注意してください。
 
-認証ドメイン UI ページから新しいドメインを作成するには、 <DNT>**Create authentication domain**</DNT>をクリックします。 設定オプションの詳細については、読み続けてください。
+認証ドメイン UI ページから新しいドメインを作成するには、 <DNT>**Create authentication domain**</DNT>をクリックします。 認証ドメインを管理または削除するには、各認証ドメインのメニュー項目を選択します。
 
 ## 別のドメインに切り替える [#switch]
 
diff --git a/src/i18n/content/jp/docs/alerts/get-notified/destinations.mdx b/src/i18n/content/jp/docs/alerts/get-notified/destinations.mdx
index 1d3bdec195f..409d7586fc7 100644
--- a/src/i18n/content/jp/docs/alerts/get-notified/destinations.mdx
+++ b/src/i18n/content/jp/docs/alerts/get-notified/destinations.mdx
@@ -16,12 +16,23 @@ translationType: machine
 対応するデスティネーション・プラットフォームは以下の通りです。
 
 * Atlassian Jira: [ワークフロー](/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/incident-workflows/)、[エラー インボックス](/docs/errors-inbox/)で利用できます。
+
 * ServiceNow。 [ワークフローで利用可能](/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/incident-workflows/).
+
 * Slack: [ワークフロー](/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/incident-workflows/)、[エラー インボックス](/docs/errors-inbox/)、 [ディスカッション](/docs/new-relic-solutions/new-relic-one/ui-data/collaborate/collaboration-slack-integration/)で利用できます。
+
 * Webhookです。 [ワークフローで利用可能](/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/incident-workflows/).
+
+  <Callout variant="important">
+    New Relic アラート用に Teams で Microsoft Office 365 Webhook ベースのコネクタを使用している場合は、2025 年 1 月 31 日までに Webhook URL を新しい形式に更新する必要があります。 Webhook URL の更新の詳細については、 [Microsoft の Teams における Office 365 コネクタのサポート終了 (EOL) を](https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/)参照してください。
+  </Callout>
+
 * メール: [ワークフロー](/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/incident-workflows/)と [ディスカッション](/docs/new-relic-solutions/new-relic-one/ui-data/collaborate/collaborate-with-teammates/)で利用できます。
+
 * AWS EventBridge： [ワークフロー](/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/incident-workflows/)で利用できます。
+
 * PagerDuty： [ワークフローで利用可能](/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/incident-workflows/).
+
 * New Relic Mobile Push: [ワークフロー](/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/incident-workflows/)で利用できます。
 
 これらの宛先やその他の宛先については、 [通知の統合](/docs/alerts-applied-intelligence/notifications/notification-integrations) を参照してください。
@@ -35,28 +46,13 @@ translationType: machine
 
 ## 目的地の管理 [#manage-destinations]
 
-<img
-  title="Destinations overview page"
-  alt="Destinations overview page."
-  src="/images/accounts_screenshot-full_destinations-overview.webp"
-/>
+<img title="Destinations overview page" alt="Destinations overview page." src="/images/accounts_screenshot-full_destinations-overview.webp" />
 
 <figcaption>
-  <DNT>**[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Alerts > Destinations**</DNT>に移動します。 通知の送信先を選択するには、送信先を使用します。
+  <DNT>**[one.newrelic.com &gt; All capabilities](https://one.newrelic.com/all-capabilities) &amp;gt; Alerts &amp;gt; Destinations**</DNT>に移動します。 通知の送信先を選択するには、送信先を使用します。
 </figcaption>
 
-1. <DNT>
-     **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Alerts > Enrich and Notify > Destinations**
-   </DNT>
-
-   に移動します。
-
-   <DNT>
-     **Destinations**
-   </DNT>
-
-   テーブルには既存の宛先に関する情報が表示され、ユーザーは有効化、無効化、および変更を行うことができます。
-
+1. <DNT>**[one.newrelic.com &gt; All capabilities](https://one.newrelic.com/all-capabilities) &amp;gt; Alerts &amp;gt; Enrich and Notify &amp;gt; Destinations**</DNT>に移動します。 <DNT>**Destinations**</DNT>テーブルには既存の宛先に関する情報が表示され、ユーザーは有効化、無効化、および変更を行うことができます。
 2. デスティネーションを追加するには、適切なプラットフォームタイルをクリックします。目的地の設定を変更するには、目的地テーブルで目的地の行をクリックします。
 
 [NerdGraphAPI](/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-destinations)を使用して宛先を構成することもできます。
@@ -82,14 +78,10 @@ translationType: machine
 
 チャネル テンプレートの設定中に、 <DNT>**Destinations**</DNT>テーブルと<DNT>**Select a destination**</DNT>ステップで宛先のステータスを確認できます。 Nerdgraph API と`status`プロパティを使用して状態を確認することもできます。
 
-<img
-  title="Destination status in the Destinations table."
-  alt="Destination status in the Destinations table."
-  src="/images/accounts_screenshot-full_destinations-status.webp"
-/>
+<img title="Destination status in the Destinations table." alt="Destination status in the Destinations table." src="/images/accounts_screenshot-full_destinations-status.webp" />
 
 <figcaption>
-  <DNT>**[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Alerts > Destinations**</DNT>に移動します。 <DNT>**Destinations**</DNT>タブをクリックして宛先テーブルを表示します。
+  <DNT>**[one.newrelic.com &gt; All capabilities](https://one.newrelic.com/all-capabilities) &amp;gt; Alerts &amp;gt; Destinations**</DNT>に移動します。 <DNT>**Destinations**</DNT>タブをクリックして宛先テーブルを表示します。
 </figcaption>
 
 ### 問題通知ログ [#notifications-log]
@@ -102,7 +94,9 @@ translationType: machine
 
 これは、 <DNT>**Alert conditions (policies)**</DNT>および[ワークフロー](/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/incident-workflows/)機能を使用する場合に特に便利です。このようにして、通知エラーのイベントでトリガーする条件を作成し、新しい通知を別の場所に送信できます。
 
-エラー通知機能を追加するステップバイステップのデモは、以下にあります。<Video type="wistia" id="b89ctyjolq"/>
+エラー通知を追加する手順を説明したデモは以下にあります。
+
+<Video type="wistia" id="b89ctyjolq" />
 
 条件例
 
@@ -116,4 +110,4 @@ WHERE category = 'NotificationError'
 
 ### スヌーズされた目的地 [#Snoozed-destination]
 
-スヌーズ: 障害のある宛先でのエラー ノイズを最小限に抑えるために、宛先を「スヌーズ」します。特定の宛先への通知送信が 2 時間以内に失敗した場合、その宛先は数分間「スヌーズ」されます。この期間中、その宛先に通知は送信されません。
+スヌーズ: 障害のある宛先でのエラー ノイズを最小限に抑えるために、宛先を「スヌーズ」します。特定の宛先への通知送信が 2 時間以内に失敗した場合、その宛先は数分間「スヌーズ」されます。この期間中、その宛先に通知は送信されません。
\ No newline at end of file
diff --git a/src/i18n/content/jp/docs/browser/browser-monitoring/browser-pro-features/session-replay.mdx b/src/i18n/content/jp/docs/browser/browser-monitoring/browser-pro-features/session-replay.mdx
index 1957bbfeee4..42c3e01af08 100644
--- a/src/i18n/content/jp/docs/browser/browser-monitoring/browser-pro-features/session-replay.mdx
+++ b/src/i18n/content/jp/docs/browser/browser-monitoring/browser-pro-features/session-replay.mdx
@@ -173,6 +173,10 @@ translationType: machine
   </Step>
 </Steps>
 
+<Callout variant="important">
+  Certain settings, including enabling or disabling session replay and adjusting sample rates for overall and errors, have been moved to server-side configuration. For example, after you update these settings for copy/paste installation method, there&apos;s no need to redeploy the script. This is applicable for browser agent version `1.259.0` or higher.
+</Callout>
+
 ## トラブルシューティング [#troubleshoot]
 
 <CollapserGroup>
diff --git a/src/i18n/content/jp/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-firehose-nozzle-integration.mdx b/src/i18n/content/jp/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-firehose-nozzle-integration.mdx
index ad109343cd8..7e62ef393ad 100644
--- a/src/i18n/content/jp/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-firehose-nozzle-integration.mdx
+++ b/src/i18n/content/jp/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-firehose-nozzle-integration.mdx
@@ -26,7 +26,7 @@ VMware Tanzu 用 New Relic Nozzle には次の要件があります。
 
 * Pro または Pro Trial ライセンスを持つアクティブな New Relic アカウント。New Relic アカウントをまだお持ちでない場合は、 [14 日間の無料試用ライセンス](http://newrelic.com/signup?funnel=pivotal-cloud-foundry&partner=Pivotal+Cloud+Foundry)を取得できます。
 * New Relic Insights がライセンスに含まれています
-* VMware Tanzu バージョン v2.10.x から v6.0.x まで。
+* VMware Tanzu バージョン v2.10.x から v10.0.x まで。
 
 ## 主な特徴 [#key-features]
 
@@ -128,7 +128,7 @@ VMware Tanzu 用 New Relic Nozzle には次の要件があります。
       </td>
 
       <td>
-        v2.10.x、 v2.11.x、v2.12.x、v2.13.x、v3.0.x、v4.0.x、v5.0.x、v6.0.x
+        v2.10.x、 v2.11.x、v2.12.x、v2.13.x、v3.0.x、v4.0.x、v5.0.x、v6.0.x、v10.0.x
       </td>
     </tr>
 
diff --git a/src/i18n/content/jp/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-nginx-buildpack-integration.mdx b/src/i18n/content/jp/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-nginx-buildpack-integration.mdx
index 3da83fc4369..ab21dab3a32 100644
--- a/src/i18n/content/jp/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-nginx-buildpack-integration.mdx
+++ b/src/i18n/content/jp/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-nginx-buildpack-integration.mdx
@@ -15,7 +15,7 @@ VMware Tanzu 用のNew Relic NGINX 統合ビルドパックを使用して、NGI
 
 ## 要件と互換性 [#requirements-compatibility]
 
-この製品はテスト済みで、v3.0 までの VMware Tanzu OpsManager バージョンおよび Tanzu アプリケーション サービス 4.0、5.0、および 6.0 と互換性があります。
+この製品は、v3.0.x までの VMware Tanzu OpsManager バージョンと、Tanzu アプリケーション サービス バージョン 4.x、5.x、6.x、および 10.x で認定されています。
 
 VMware Tanzu 用のNew Relic NGINX 統合ビルドパックには以下が必要です。
 
@@ -49,7 +49,7 @@ VMware Tanzu 用のNew Relic NGINX 統合ビルドパックには以下が必要
       </td>
 
       <td>
-        1.0.2
+        1.1.2
       </td>
     </tr>
 
@@ -59,7 +59,7 @@ VMware Tanzu 用のNew Relic NGINX 統合ビルドパックには以下が必要
       </td>
 
       <td>
-        2024年8月9日
+        2025年1月6日
       </td>
     </tr>
 
@@ -69,7 +69,7 @@ VMware Tanzu 用のNew Relic NGINX 統合ビルドパックには以下が必要
       </td>
 
       <td>
-        VMware Tanzu 1.0.2 用New Relic NGINX 統合ビルドパック
+        VMware Tanzu 1.1.2 用 New Relic NGINX 統合ビルドパック
       </td>
     </tr>
 
@@ -89,7 +89,7 @@ VMware Tanzu 用のNew Relic NGINX 統合ビルドパックには以下が必要
       </td>
 
       <td>
-        4.0.x、 5.0.x および 6.0.x
+        4.x、5.x、6.x、および 10.x
       </td>
     </tr>
 
@@ -136,7 +136,7 @@ VMware Tanzu 用のNew Relic NGINX 統合ビルドパックには以下が必要
     <TabsPageItem id="ops-manager-tile">
       <Steps>
         <Step>
-          タイルの最新バージョン (現在`newrelic-nginx-buildpack-1.0.1.pivotal` ) を[Broadcom ダウンロード サイト](https://support.broadcom.com/group/ecx/productdownloads?subfamily=New%20Relic%20Nginx%20Integration%20Buildpack%20for%20VMware%20Tanzu)、または[リリースの下にある New Relic の GitHub リポジトリ](https://github.com/newrelic/newrelic-pcf-nginx-buildpack/releases)からダウンロードします。
+          タイルの最新バージョン (現在`newrelic-nginx-buildpack-1.1.2.pivotal` ) を[Broadcom ダウンロード サイト](https://support.broadcom.com/group/ecx/productdownloads?subfamily=New%20Relic%20Nginx%20Integration%20Buildpack%20for%20VMware%20Tanzu)、または[リリースの下にある New Relic の GitHub リポジトリ](https://github.com/newrelic/newrelic-pcf-nginx-buildpack/releases)からダウンロードします。
         </Step>
 
         <Step>
diff --git a/src/i18n/content/jp/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-service-broker-integration.mdx b/src/i18n/content/jp/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-service-broker-integration.mdx
index c0437da3061..5fc03037c78 100644
--- a/src/i18n/content/jp/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-service-broker-integration.mdx
+++ b/src/i18n/content/jp/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-service-broker-integration.mdx
@@ -109,7 +109,7 @@ VMware Tanzu 用 New Relic Nozzle には次の要件があります。
       </td>
 
       <td>
-        2.10.x、 2.11.x、2.12.x、2.13.x、3.x、4.x、5.x、および 6.x
+        2.10.x、 2.11.x、2.12.x、2.13.x、3.x、4.x、5.x、6.x、および 10.x
       </td>
     </tr>
 
diff --git a/src/i18n/content/jp/docs/infrastructure/other-infrastructure-integrations/monitoring-jenkins-ot.mdx b/src/i18n/content/jp/docs/infrastructure/other-infrastructure-integrations/monitoring-jenkins-ot.mdx
index 9a14a232559..769e6f280c4 100644
--- a/src/i18n/content/jp/docs/infrastructure/other-infrastructure-integrations/monitoring-jenkins-ot.mdx
+++ b/src/i18n/content/jp/docs/infrastructure/other-infrastructure-integrations/monitoring-jenkins-ot.mdx
@@ -83,4 +83,36 @@ Jenkins パイプライン データを New Relic に送信した後、 [New Rel
   Jenkins OpenTelemetry プラグインは New Relic によって保守されていないため、インストルメンテーションに問題がある場合は、[プラグインの GitHub リポジトリで新しい問題を作成してください](https://github.com/jenkinsci/opentelemetry-plugin/issues)。
 </Callout>
 
+## リソースの属性とタグ [#attributes]
+
+Jenkinsプラグインの設定にリソースのプロパティを追加できます。 これにより、プラグインで生成されたすべてのログ、メトリクス、およびトレース データのプロパティを含めることができます。 名前が`tags.`で始まるリソース属性も、 [Jenkins エンティティにエンティティ タグを](/docs/opentelemetry/best-practices/opentelemetry-best-practices-resources/#tags)追加します。
+
+属性は次の 2 つの方法で定義できます。
+
+<CollapserGroup>
+  <Collapser id="attributes-config" title="Jenkinsプラグイン設定で属性を定義する">
+    `io.jenkins.plugins.opentelemetry.JenkinsOpenTelemetryPluginConfiguration.xml`ファイルの`configurationProperties`要素にリソース属性を追加できます。
+
+    例：
+
+    ```xml
+      <configurationProperties>
+        otel.resource.attributes=attribute1=value1,attribute2=value2,tags.tag1=tagValue1
+      </configurationProperties>
+    ```
+  </Collapser>
+
+  <Collapser id="attributes-env" title="環境変数の属性を定義する">
+    `OTEL_RESOURCE_ATTRIBUTES`環境変数を使用してリソース属性を定義できます。
+
+    これは、Ubuntu システムでは、 `systemctl edit jenkins`を使用して jenkins の systemctl 設定を編集し、設定の override.conf 部分に追加することで実行できます。
+
+    ```yml
+      [Service]
+      # Set OTel Environment Options
+      Environment="OTEL_RESOURCE_ATTRIBUTES=attribute1=value1,attribute2=value2,tags.tag1=tagValue1"
+    ```
+  </Collapser>
+</CollapserGroup>
+
 <InstallFeedback />
\ No newline at end of file
diff --git a/src/i18n/content/kr/docs/accounts/accounts-billing/new-relic-one-user-management/authentication-domains-saml-sso-scim-more.mdx b/src/i18n/content/kr/docs/accounts/accounts-billing/new-relic-one-user-management/authentication-domains-saml-sso-scim-more.mdx
index 7c2e11c652c..26e0eb67309 100644
--- a/src/i18n/content/kr/docs/accounts/accounts-billing/new-relic-one-user-management/authentication-domains-saml-sso-scim-more.mdx
+++ b/src/i18n/content/kr/docs/accounts/accounts-billing/new-relic-one-user-management/authentication-domains-saml-sso-scim-more.mdx
@@ -80,9 +80,9 @@ New Relic에 사용자를 추가하면 항상 특정 인증 도메인에 추가
 
 인증 도메인을 보고 구성하려면 [사용자 메뉴](/docs/accounts/accounts-billing/general-account-settings/intro-account-settings) 에서 <DNT>**Administration &gt; Authentication domains**</DNT> 로 이동하세요.
 
-기존 도메인이 있는 경우 왼쪽에 있습니다. 대부분의 조직에는 최대 2개 또는 3개의 도메인이 있습니다. 하나는 수동 기본 설정이고 다른 하나는 ID 공급자 관련 설정입니다.
+기존 도메인이 있는 경우 표에 표시됩니다. 대부분 조직은 많아야 2-3개의 도메인을 보유합니다. 하나는 수동 기본 설정을 위한 도메인이고, 1-2개는 ID 공급자 관련 설정을 위한 도메인입니다.
 
-인증 도메인 UI 페이지에서 새 도메인을 생성하려면 <DNT>**Create authentication domain**</DNT> 클릭합니다. 설정 옵션에 대한 자세한 내용을 보려면 계속 읽으세요.
+인증 도메인 UI 페이지에서 새 도메인을 만들려면 <DNT>**Create authentication domain**</DNT> 클릭하세요. 인증 도메인을 관리하거나 삭제하려면 각 인증 도메인에 대한 메뉴 항목을 선택하세요.
 
 ## 다른 도메인으로 전환 [#switch]
 
diff --git a/src/i18n/content/kr/docs/alerts/get-notified/destinations.mdx b/src/i18n/content/kr/docs/alerts/get-notified/destinations.mdx
index f18f3e6970b..9bd69d41036 100644
--- a/src/i18n/content/kr/docs/alerts/get-notified/destinations.mdx
+++ b/src/i18n/content/kr/docs/alerts/get-notified/destinations.mdx
@@ -16,12 +16,23 @@ translationType: machine
 지원되는 대상 플랫폼은 다음과 같습니다.
 
 * Atlassian Jira: [워크플로](/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/incident-workflows/) , [오류 받은 편지함](/docs/errors-inbox/) 에서 사용할 수 있습니다.
+
 * ServiceNow: [워크플로](/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/incident-workflows/) 에서 사용할 수 있습니다.
+
 * Slack: [워크플로](/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/incident-workflows/) , [오류 수신함](/docs/errors-inbox/) 및 [토론](/docs/new-relic-solutions/new-relic-one/ui-data/collaborate/collaboration-slack-integration/) 에서 사용할 수 있습니다.
+
 * Webhook: [워크플로](/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/incident-workflows/) 에서 사용할 수 있습니다.
+
+  <Callout variant="important">
+    Teams에서 뉴렐릭 알림을 위해 Microsoft Office 365 웹훅 기반 커넥터를 사용하는 경우 2025년 1월 31일까지 웹훅 URL을 새 형식으로 업데이트해야 합니다. 웹훅 URL을 업데이트하는 방법에 대한 자세한 내용은 [Teams의 Office 365 커넥터에 대한 Microsoft의 EOL(수명 종료)을](https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/) 참조하세요.
+  </Callout>
+
 * 이메일: [워크플로](/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/incident-workflows/) 및 [토론](/docs/new-relic-solutions/new-relic-one/ui-data/collaborate/collaborate-with-teammates/) 에서 사용할 수 있습니다.
+
 * AWS EventBridge: [워크플로](/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/incident-workflows/) 에서 사용 가능 .
+
 * PagerDuty: [워크플로](/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/incident-workflows/) 에서 사용할 수 있습니다.
+
 * New Relic Mobile Push: [워크플로](/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/incident-workflows/) 에서 사용할 수 있습니다.
 
 이러한 대상 및 기타 대상에 대한 자세한 내용은 [알림 통합](/docs/alerts-applied-intelligence/notifications/notification-integrations) 을 참조하십시오.
@@ -35,28 +46,13 @@ translationType: machine
 
 ## 목적지 관리 [#manage-destinations]
 
-<img
-  title="Destinations overview page"
-  alt="Destinations overview page."
-  src="/images/accounts_screenshot-full_destinations-overview.webp"
-/>
+<img title="Destinations overview page" alt="Destinations overview page." src="/images/accounts_screenshot-full_destinations-overview.webp" />
 
 <figcaption>
-  <DNT>**[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Alerts > Destinations**</DNT> 로 이동합니다. 목적지를 사용하여 공지가 전송되는 위치를 선택하세요.
+  <DNT>**[one.newrelic.com &gt; All capabilities](https://one.newrelic.com/all-capabilities) &amp;gt; Alerts &amp;gt; Destinations**</DNT> 로 이동합니다. 목적지를 사용하여 공지가 전송되는 위치를 선택하세요.
 </figcaption>
 
-1. <DNT>
-     **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Alerts > Enrich and Notify > Destinations**
-   </DNT>
-
-   로 이동합니다.
-
-   <DNT>
-     **Destinations**
-   </DNT>
-
-   테이블은 기존 대상에 대한 정보를 표시하며 사용자가 활성화, 비활성화 및 수정할 수 있도록 합니다.
-
+1. <DNT>**[one.newrelic.com &gt; All capabilities](https://one.newrelic.com/all-capabilities) &amp;gt; Alerts &amp;gt; Enrich and Notify &amp;gt; Destinations**</DNT> 로 이동합니다. <DNT>**Destinations**</DNT> 테이블은 기존 대상에 대한 정보를 표시하며 사용자가 활성화, 비활성화 및 수정할 수 있도록 합니다.
 2. 대상을 추가하려면 해당 플랫폼 타일을 클릭합니다. 대상 설정을 수정하려면 대상 테이블에서 대상 행을 클릭합니다.
 
 [NerdGraph API](/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-destinations) 를 사용하여 목적지를 구성할 수도 있습니다.
@@ -82,14 +78,10 @@ translationType: machine
 
 채널 템플릿을 설정하는 동안 <DNT>**Destinations**</DNT> 테이블과 <DNT>**Select a destination**</DNT> 단계에서 대상 상태를 볼 수 있습니다. `status` 속성과 함께 Nerdgraph API를 사용하여 상태를 검토할 수도 있습니다.
 
-<img
-  title="Destination status in the Destinations table."
-  alt="Destination status in the Destinations table."
-  src="/images/accounts_screenshot-full_destinations-status.webp"
-/>
+<img title="Destination status in the Destinations table." alt="Destination status in the Destinations table." src="/images/accounts_screenshot-full_destinations-status.webp" />
 
 <figcaption>
-  <DNT>**[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Alerts > Destinations**</DNT> 로 이동합니다. 목적지 테이블을 보려면 <DNT>**Destinations**</DNT> 탭을 클릭하세요.
+  <DNT>**[one.newrelic.com &gt; All capabilities](https://one.newrelic.com/all-capabilities) &amp;gt; Alerts &amp;gt; Destinations**</DNT> 로 이동합니다. 목적지 테이블을 보려면 <DNT>**Destinations**</DNT> 탭을 클릭하세요.
 </figcaption>
 
 ### 문제 알림 로그 [#notifications-log]
@@ -102,7 +94,9 @@ translationType: machine
 
 이는 <DNT>**Alert conditions (policies)**</DNT> 및 [워크플로](/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/incident-workflows/) 기능을 사용하는 경우 특히 유용합니다. 이런 식으로 알림 오류가 발생할 때 트리거되는 조건을 구축할 수 있으며 새 알림을 다른 곳으로 보낼 수 있습니다.
 
-오류 알리미를 추가하는 단계별 데모는 아래에서 찾을 수 있습니다.<Video type="wistia" id="b89ctyjolq"/>
+오류 알림을 추가하는 단계별 데모는 아래에서 확인할 수 있습니다.
+
+<Video type="wistia" id="b89ctyjolq" />
 
 예시 조건:
 
@@ -116,4 +110,4 @@ WHERE category = 'NotificationError'
 
 ### 일시 중지된 목적지 [#Snoozed-destination]
 
-다시 알림: 잘못된 대상의 오류 노이즈를 최소화하기 위해 대상을 "다시 알림"합니다. 특정 대상으로의 알림 전송이 2시간 이내에 실패하면 몇 분 동안 해당 대상을 "일시 중지"합니다. 이 기간에는 해당 목적지로 알림을 보내지 않습니다.
+다시 알림: 잘못된 대상의 오류 노이즈를 최소화하기 위해 대상을 &quot;다시 알림&quot;합니다. 특정 대상으로의 알림 전송이 2시간 이내에 실패하면 몇 분 동안 해당 대상을 &quot;일시 중지&quot;합니다. 이 기간에는 해당 목적지로 알림을 보내지 않습니다.
\ No newline at end of file
diff --git a/src/i18n/content/kr/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx b/src/i18n/content/kr/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx
index 6e5394d5aa9..318bdaecd81 100644
--- a/src/i18n/content/kr/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx
+++ b/src/i18n/content/kr/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx
@@ -251,7 +251,7 @@ Node.js 에이전트는 [npm(Node Package Manager) 저장소](https://npmjs.org/
 
 **참고**: 지원되는 최신 버전은 지원되는 최신 버전을 반영하지 않을 수 있습니다.
 
-| 패키지 이름 | 최소 지원 버전 | 최신 지원 버전 | 도입된 버전\* | | --- | --- | --- | --- | | `@apollo/gateway` | 2.3.0 | 2.9.3 | `@newrelic/apollo-server-plugin@1.0.0` | | `@apollo/server` | 4.0.0 | 4.11.2 | `@newrelic/apollo-server-plugin@2.1.0` | | `@aws-sdk/client-bedrock-runtime` | 3.474.0 | 3.714.0 | 11.13.0 | | `@aws-sdk/client-dynamodb` | 3.0.0 | 3.714.0 | 8.7.1 | | `@aws-sdk/client-sns` | 3.0.0 | 3.714.0 | 8.7.1 | | `@aws-sdk/client-sqs` | 3.0.0 | 3.714.0 | 8.7.1 | | `@aws-sdk/lib-dynamodb` | 3.377.0 | 3.714.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.24 | 11.13.0 | | `@nestjs/cli` | 9.0.0 | 10.4.9 | 10.1.0 | | `@prisma/client` | 5.0.0 | 6.1.0 | 11.0.0 | | `@smithy/smithy-client` | 2.0.0 | 3.5.0 | 11.0.0 | | `amqplib` | 0.5.0 | 0.10.5 | 2.0.0 | | `apollo-server` | 3.0.0 | 3.13.0 | `@newrelic/apollo-server-plugin@1.0.0` | | `apollo-server-express` | 3.0.0 | 3.13.0 | `@newrelic/apollo-server-plugin@1.0.0` | | `aws-sdk` | 2.2.48 | 2.1692.0 | 6.2.0 | | `bluebird` | 2.0.0 | 3.7.2 | 1.27.0 | | `bunyan` | 1.8.12 | 1.8.15 | 9.3.0 | | `cassandra-driver` | 3.4.0 | 4.7.2 | 1.7.1 | | `connect` | 3.0.0 | 3.7.0 | 2.6.0 | | `express` | 4.6.0 | 4.21.2 | 2.6.0 | | `fastify` | 2.0.0 | 5.2.0 | 8.5.0 | | `generic-pool` | 3.0.0 | 3.9.0 | 0.9.0 | | `ioredis` | 4.0.0 | 5.4.1 | 1.26.2 | | `kafkajs` | 2.0.0 | 2.2.4 | 11.19.0 | | `koa` | 2.0.0 | 2.15.3 | 3.2.0 | | `koa-route` | 3.0.0 | 4.0.1 | 3.2.0 | | `koa-router` | 11.0.2 | 13.0.1 | 3.2.0 | | `memcached` | 2.2.0 | 2.2.2 | 1.26.2 | | `mongodb` | 4.1.4 | 6.12.0 | 1.32.0 | | `mysql` | 2.2.0 | 2.18.1 | 1.32.0 | | `mysql2` | 2.0.0 | 3.11.5 | 1.32.0 | | `next` | 13.4.19 | 15.1.1 | 12.0.0 | | `openai` | 4.0.0 | 4.77.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.5.0 | 8.11.0 | | `q` | 1.3.0 | 1.5.1 | 1.26.2 | | `redis` | 3.1.0 | 4.7.0 | 1.31.0 | | `restify` | 11.0.0 | 11.1.0 | 2.6.0 | | `superagent` | 3.0.0 | 10.1.1 | 4.9.0 | | `undici` | 5.0.0 | 7.2.0 | 11.1.0 | | `when` | 3.7.0 | 3.7.8 | 1.26.2 | | `winston` | 3.0.0 | 3.17.0 | 8.11.0 |
+| 패키지 이름 | 최소 지원 버전 | 최신 지원 버전 | 도입된 버전\* | | --- | --- | --- | --- | | `@apollo/gateway` | 2.3.0 | 2.9.3 | `@newrelic/apollo-server-plugin@1.0.0` | | `@apollo/server` | 4.0.0 | 4.11.2 | `@newrelic/apollo-server-plugin@2.1.0` | | `@aws-sdk/client-bedrock-runtime` | 3.474.0 | 3.716.0 | 11.13.0 | | `@aws-sdk/client-dynamodb` | 3.0.0 | 3.716.0 | 8.7.1 | | `@aws-sdk/client-sns` | 3.0.0 | 3.716.0 | 8.7.1 | | `@aws-sdk/client-sqs` | 3.0.0 | 3.716.0 | 8.7.1 | | `@aws-sdk/lib-dynamodb` | 3.377.0 | 3.716.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.27 | 11.13.0 | | `@nestjs/cli` | 9.0.0 | 10.4.9 | 10.1.0 | | `@opensearch-project/opensearch` | 2.1.0 | 2.13.0 | 12.10.0 | | `@prisma/client` | 5.0.0 | 6.1.0 | 11.0.0 | | `@smithy/smithy-client` | 2.0.0 | 3.5.2 | 11.0.0 | | `amqplib` | 0.5.0 | 0.10.5 | 2.0.0 | | `apollo-server` | 3.0.0 | 3.13.0 | `@newrelic/apollo-server-plugin@1.0.0` | | `apollo-server-express` | 3.0.0 | 3.13.0 | `@newrelic/apollo-server-plugin@1.0.0` | | `aws-sdk` | 2.2.48 | 2.1692.0 | 6.2.0 | | `bluebird` | 2.0.0 | 3.7.2 | 1.27.0 | | `bunyan` | 1.8.12 | 1.8.15 | 9.3.0 | | `cassandra-driver` | 3.4.0 | 4.7.2 | 1.7.1 | | `connect` | 3.0.0 | 3.7.0 | 2.6.0 | | `express` | 4.6.0 | 4.21.2 | 2.6.0 | | `fastify` | 2.0.0 | 5.2.0 | 8.5.0 | | `generic-pool` | 3.0.0 | 3.9.0 | 0.9.0 | | `ioredis` | 4.0.0 | 5.4.2 | 1.26.2 | | `kafkajs` | 2.0.0 | 2.2.4 | 11.19.0 | | `koa` | 2.0.0 | 2.15.3 | 3.2.0 | | `koa-route` | 3.0.0 | 4.0.1 | 3.2.0 | | `koa-router` | 11.0.2 | 13.0.1 | 3.2.0 | | `memcached` | 2.2.0 | 2.2.2 | 1.26.2 | | `mongodb` | 4.1.4 | 6.12.0 | 1.32.0 | | `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.3 | 12.0.0 | | `openai` | 4.0.0 | 4.77.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 | | `q` | 1.3.0 | 1.5.1 | 1.26.2 | | `redis` | 3.1.0 | 4.7.0 | 1.31.0 | | `restify` | 11.0.0 | 11.1.0 | 2.6.0 | | `superagent` | 3.0.0 | 10.1.1 | 4.9.0 | | `undici` | 5.0.0 | 7.2.0 | 11.1.0 | | `when` | 3.7.0 | 3.7.8 | 1.26.2 | | `winston` | 3.0.0 | 3.17.0 | 8.11.0 |
 
 \*패키지를 지정하지 않으면 `newrelic` 패키지 내에서 지원됩니다.
 
diff --git a/src/i18n/content/kr/docs/browser/browser-monitoring/browser-pro-features/session-replay.mdx b/src/i18n/content/kr/docs/browser/browser-monitoring/browser-pro-features/session-replay.mdx
index 183cb049cb4..5655f213f93 100644
--- a/src/i18n/content/kr/docs/browser/browser-monitoring/browser-pro-features/session-replay.mdx
+++ b/src/i18n/content/kr/docs/browser/browser-monitoring/browser-pro-features/session-replay.mdx
@@ -173,6 +173,10 @@ translationType: machine
   </Step>
 </Steps>
 
+<Callout variant="important">
+  Certain settings, including enabling or disabling session replay and adjusting sample rates for overall and errors, have been moved to server-side configuration. For example, after you update these settings for copy/paste installation method, there&apos;s no need to redeploy the script. This is applicable for browser agent version `1.259.0` or higher.
+</Callout>
+
 ## 문제점 해결 [#troubleshoot]
 
 <CollapserGroup>
diff --git a/src/i18n/content/kr/docs/infrastructure/amazon-integrations/connect/set-up-aws-api-polling.mdx b/src/i18n/content/kr/docs/infrastructure/amazon-integrations/connect/set-up-aws-api-polling.mdx
index 787b7cae722..c59ee8e1b01 100644
--- a/src/i18n/content/kr/docs/infrastructure/amazon-integrations/connect/set-up-aws-api-polling.mdx
+++ b/src/i18n/content/kr/docs/infrastructure/amazon-integrations/connect/set-up-aws-api-polling.mdx
@@ -24,7 +24,7 @@ translationType: machine
 * API 폴링의 가장 빠른 폴링 간격은 5분인 반면, CloudWatch Metric Streams는 2분 이내에 메트릭을 스트리밍합니다.
 * AWS는 API 폴링을 제한하는 반면, CloudWatch Metric Streams 통합은 API 제한을 완전히 제거합니다.
 
-[새로운 CloudWatch Metric Streams 통합을 설치](/docs/infrastructure/amazon-integrations/connect/aws-metric-stream-setup) 하거나 [API 폴링 통합을 CloudWatch Metric Streams로 마이그레이션](/docs/infrastructure/amazon-integrations/connect/aws-metric-stream-setup/#migrate) 하려면 문서를 확인하세요.
+[새로운 CloudWatch Metric Streams 통합을 설치](/install/aws-cloudwatch) 하거나 [API 폴링 통합을 CloudWatch Metric Streams로 마이그레이션](/install/aws-cloudwatch/?task=migrate) 하려면 문서를 확인하세요.
 
 ## API 폴링 설정 [#set-up-api]
 
diff --git a/src/i18n/content/kr/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-firehose-nozzle-integration.mdx b/src/i18n/content/kr/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-firehose-nozzle-integration.mdx
index cc0eb87ef24..7f8a18f6e95 100644
--- a/src/i18n/content/kr/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-firehose-nozzle-integration.mdx
+++ b/src/i18n/content/kr/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-firehose-nozzle-integration.mdx
@@ -26,7 +26,7 @@ VMware Tanzu용 New Relic Nozzle의 요구 사항은 다음과 같습니다.
 
 * Pro 또는 Pro 평가판 라이선스가 있는 활성 New Relic 계정. 아직 New Relic 계정이 없다면 [14일 무료 평가판 라이센스를](http://newrelic.com/signup?funnel=pivotal-cloud-foundry&partner=Pivotal+Cloud+Foundry) 얻을 수 있습니다.
 * 라이선스에 포함된 New Relic Insights
-* VMware Tanzu 버전 v2.10.x부터 v6.0.x까지.
+* VMware Tanzu 버전 v2.10.x부터 v10.0.x까지.
 
 ## 주요 특징들 [#key-features]
 
@@ -128,7 +128,7 @@ Firehose에서 많은 수의 이벤트가 스트리밍되는 경우 Firehose에
       </td>
 
       <td>
-        v2.10.x, v2.11.x, v2.12.x, v2.13.x, v3.0.x, v4.0.x, v5.0.x 및 v6.0.x
+        v2.10.x, v2.11.x, v2.12.x, v2.13.x, v3.0.x, v4.0.x, v5.0.x, v6.0.x 및 v10.0.x
       </td>
     </tr>
 
diff --git a/src/i18n/content/kr/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-nginx-buildpack-integration.mdx b/src/i18n/content/kr/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-nginx-buildpack-integration.mdx
index c99da02226e..dad250e49fd 100644
--- a/src/i18n/content/kr/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-nginx-buildpack-integration.mdx
+++ b/src/i18n/content/kr/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-nginx-buildpack-integration.mdx
@@ -15,19 +15,19 @@ VMware Tanzu용 뉴렐릭 NGINX 통합 빌드팩을 사용하여 NGINX 모니터
 
 ## 요구 사항 및 호환성 [#requirements-compatibility]
 
-본 제품은 테스트를 거쳐 VMware Tanzu OpsManager 버전 3.0 이하 및 Tanzu 앱 서비스 4.0, 5.0, 6.0과 호환되는 것으로 확인되었습니다.
+이 제품은 VMware Tanzu OpsManager 버전 3.0.x 이하와 Tanzu 애플리케이션 서비스 버전 4.x, 5.x, 6.x, 10.x에서 인증되었습니다.
 
-VMware Tanzu용 뉴켈릭 NGINX 통합 빌드팩에는 다음이 필요합니다.
+VMware Tanzu용 뉴렐릭 NGINX 통합 빌드팩에는 다음이 필요합니다.
 
 * CF CLI: 이 빌드팩은 앱 매니페스트에서 다중 빌드팩으로 설치되므로 버전 6.38 이상이 필요합니다.
 * NGINX 빌드팩: 이 빌드팩은 [`nginx_buildpack`](https://support.broadcom.com/group/ecx/productdownloads?subfamily=NGINX%20Buildpack) 위에 설치되어야 합니다.
-* 블루베리 계정 및 볼륨 키: 볼륨 키가 있는 활성 블루베리 계정이 필요합니다. 이 키는 뉴렐릭 플랫폼에 지표를 전송하는 뉴렐릭 인프라 에이전트에 NGINX 서버를 바인딩하는 데 사용됩니다.
+* 뉴렐릭 계정 및 볼륨 키: 볼륨 키가 있는 활성 뉴렐릭 계정이 필요합니다. 이 키는 뉴렐릭 플랫폼에 지표를 전송하는 뉴렐릭 인프라 에이전트에 NGINX 서버를 바인딩하는 데 사용됩니다.
 
 매니페스트에 여러 빌드팩을 추가하는 방법에 대한 일반 정보는 [Cloud Foundry 문서: 여러 빌드팩을 사용하여 앱 푸시 를](https://docs.cloudfoundry.org/buildpacks/use-multiple-buildpacks.html) 참조하세요.
 
 ### 버전 및 지원 정보 [#version-and-support]
 
-다음 표에서는 VMware Tanzu용 뉴켈릭 NGINX 통합 빌드팩에 대한 버전 지원 정보를 제공합니다.
+다음 표에서는 VMware Tanzu용 뉴렐릭 NGINX 통합 빌드팩에 대한 버전 지원 정보를 제공합니다.
 
 <table>
   <thead>
@@ -49,7 +49,7 @@ VMware Tanzu용 뉴켈릭 NGINX 통합 빌드팩에는 다음이 필요합니다
       </td>
 
       <td>
-        1.0.2
+        1.1.2
       </td>
     </tr>
 
@@ -59,7 +59,7 @@ VMware Tanzu용 뉴켈릭 NGINX 통합 빌드팩에는 다음이 필요합니다
       </td>
 
       <td>
-        2024년 8월 9일
+        2025년 1월 6일
       </td>
     </tr>
 
@@ -69,7 +69,7 @@ VMware Tanzu용 뉴켈릭 NGINX 통합 빌드팩에는 다음이 필요합니다
       </td>
 
       <td>
-        뉴렐릭 VMware Tanzu 1.0.2용 NGINX 통합 빌드팩
+        뉴렐릭 VMware Tanzu 1.1.2용 NGINX 통합 빌드팩
       </td>
     </tr>
 
@@ -89,7 +89,7 @@ VMware Tanzu용 뉴켈릭 NGINX 통합 빌드팩에는 다음이 필요합니다
       </td>
 
       <td>
-        4.0.x, 5.0.x 및 6.0.x
+        4.x, 5.x, 6.x 및 10.x
       </td>
     </tr>
 
@@ -117,7 +117,7 @@ VMware Tanzu용 뉴켈릭 NGINX 통합 빌드팩에는 다음이 필요합니다
 
 ## 설치 및 구성 [#install-and-configure]
 
-이 섹션에서는 VMware Tanzu용 뉴켈릭 NGINX 통합 빌드팩을 설치하고 구성하는 방법을 설명합니다.
+이 섹션에서는 VMware Tanzu용 뉴렐릭 NGINX 통합 빌드팩을 설치하고 구성하는 방법을 설명합니다.
 
 Ops Manager에서 타일로 빌드팩을 설치하거나 CF CLI를 사용하여 개별적으로 빌드팩을 설치할 수 있습니다.
 
@@ -136,7 +136,7 @@ Ops Manager에서 타일로 빌드팩을 설치하거나 CF CLI를 사용하여
     <TabsPageItem id="ops-manager-tile">
       <Steps>
         <Step>
-          [Broadcom 다운로드 사이트](https://support.broadcom.com/group/ecx/productdownloads?subfamily=New%20Relic%20Nginx%20Integration%20Buildpack%20for%20VMware%20Tanzu) 또는 [릴리즈 아래의 뉴렐릭 GitHub 리포지터리](https://github.com/newrelic/newrelic-pcf-nginx-buildpack/releases) 에서 타일의 최신 버전(현재 `newrelic-nginx-buildpack-1.0.1.pivotal`)을 다운로드합니다.
+          [Broadcom 다운로드 사이트](https://support.broadcom.com/group/ecx/productdownloads?subfamily=New%20Relic%20Nginx%20Integration%20Buildpack%20for%20VMware%20Tanzu) 또는 [릴리즈 아래의 뉴렐릭 GitHub 리포지터리](https://github.com/newrelic/newrelic-pcf-nginx-buildpack/releases) 에서 타일의 최신 버전(현재 `newrelic-nginx-buildpack-1.1.2.pivotal`)을 다운로드합니다.
         </Step>
 
         <Step>
@@ -334,7 +334,7 @@ Ops Manager에서 타일로 빌드팩을 설치하거나 CF CLI를 사용하여
 
              * 필요한 조치: 이 파일을 올바른 애플리케이션 정보로 업데이트하고 빌드팩 순서가 올바르게 지정되었는지 확인하세요. 이는 애플리케이션을 적절하게 배포하는 데 중요합니다.
 
-             * 블루베리 클러스터 키: 이 통합에는 [클러스터 키 가](/docs/apis/intro-apis/new-relic-api-keys/#license-key) 필요합니다. 환경 변수 `NEW_RELIC_LICENSE_KEY: <ingest_key_value>` 을 사용하여 `manifest.yml` 파일에서 설정할 수 있습니다. 또는, 뉴켈릭 서비스 브로커에서 바인딩 키를 얻을 수도 있습니다.
+             * 뉴렐릭 클러스터 키: 이 통합에는 [클러스터 키 가](/docs/apis/intro-apis/new-relic-api-keys/#license-key) 필요합니다. 환경 변수 `NEW_RELIC_LICENSE_KEY: <ingest_key_value>` 을 사용하여 `manifest.yml` 파일에서 설정할 수 있습니다. 또는, 뉴렐릭 서비스 브로커에서 바인딩 키를 얻을 수도 있습니다.
 
              * 상태 포트: NGINX 설정에 따라 상태 포트 정보가 필요합니다. 기본 포트 값은 `8080` 이며 환경 변수 `STATUS_PORT: 8080` 을 사용하여 설정할 수 있습니다.
                * 참고: 요구 사항에 따라 추가 [환경 변수를](/docs/infrastructure/install-infrastructure-agent/configuration/infrastructure-agent-configuration-settings/) 설정할 수 있습니다.
@@ -360,8 +360,8 @@ Ops Manager에서 타일로 빌드팩을 설치하거나 CF CLI를 사용하여
 
            * [`nginx-config.yml`](/install/nginx/):
 
-             * 이 템플릿에는 뉴켈릭 NGINX 통합에 대한 설정 설정이 포함되어 있습니다.
-             * 필요한 조치: 다양한 설정 옵션을 이해하고 필요에 따라 설정을 조정하려면 [뉴켈릭 NGINX 설명서를](/install/nginx/) 참조하세요.
+             * 이 템플릿에는 뉴렐릭 NGINX 통합에 대한 설정 설정이 포함되어 있습니다.
+             * 필요한 조치: 다양한 설정 옵션을 이해하고 필요에 따라 설정을 조정하려면 [뉴렐릭 NGINX 설명서를](/install/nginx/) 참조하세요.
              * 참고: `nginx.conf` 의 `location /nginx_status` 가 `nginx-config.yml` 의 `STATUS_URL` 와 일치하는지 확인하세요.
 
            * `public`:
@@ -384,11 +384,11 @@ Ops Manager에서 타일로 빌드팩을 설치하거나 CF CLI를 사용하여
   </Step>
 
   <Step>
-    ### (선택 사항) 뉴켈릭 브로커 서비스에 합류를 바인딩합니다. [#bind-with-newrelic-broker-service]
+    ### (선택 사항) 뉴렐릭 브로커 서비스에 합류를 바인딩합니다. [#bind-with-newrelic-broker-service]
 
-    [뉴켈릭 브로커 서비스](/docs/infrastructure/host-integrations/host-integrations-list/cloudfoundry-integrations/vmware-tanzu-service-broker-integration/) 와 기능을 통합하려면 다음 단계를 따르세요.
+    [뉴렐릭 브로커 서비스](/docs/infrastructure/host-integrations/host-integrations-list/cloudfoundry-integrations/vmware-tanzu-service-broker-integration/) 와 기능을 통합하려면 다음 단계를 따르세요.
 
-    1. Cloud Foundry CLI를 사용하여 뉴켈릭 서비스 연결을 생성합니다.
+    1. Cloud Foundry CLI를 사용하여 뉴렐릭 서비스 연결을 생성합니다.
 
        ```sh
        cf create-service newrelic <NEWRELIC_PLAN_NAME> <YOUR_NEWRELIC_SERVICE_INSTANCE_NAME>
@@ -396,7 +396,7 @@ Ops Manager에서 타일로 빌드팩을 설치하거나 CF CLI를 사용하여
 
        `<NEWRELIC_PLAN_NAME>` 원하는 뉴렐릭 계획으로 바꾸고 `<YOUR_NEWRELIC_SERVICE_INSTANCE_NAME>` 서비스 이름으로 바꾸세요.
 
-    2. CF CLI를 사용하여 뉴켈릭 서비스에 바인딩합니다.
+    2. CF CLI를 사용하여 뉴렐릭 서비스에 바인딩합니다.
 
        ```sh
        cf bind-service my_app <YOUR_NEWRELIC_SERVICE_INSTANCE_NAME>
@@ -419,7 +419,7 @@ Ops Manager에서 타일로 빌드팩을 설치하거나 CF CLI를 사용하여
   </Step>
 </Steps>
 
-## 뉴켈릭으로 모델링 [#monitoring-with-New-Relic]
+## 뉴렐릭으로 모델링 [#monitoring-with-New-Relic]
 
 기능이 성공적으로 푸시되면 NGINX 통합이 NGINX 지표를 뉴렐릭으로 보내기 시작합니다.
 
diff --git a/src/i18n/content/kr/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-service-broker-integration.mdx b/src/i18n/content/kr/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-service-broker-integration.mdx
index c708956a821..2681b706642 100644
--- a/src/i18n/content/kr/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-service-broker-integration.mdx
+++ b/src/i18n/content/kr/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-service-broker-integration.mdx
@@ -109,7 +109,7 @@ VMware Tanzu용 New Relic Nozzle의 요구 사항은 다음과 같습니다.
       </td>
 
       <td>
-        2.10.x, 2.11.x, 2.12.x, 2.13.x, 3.x, 4.x, 5.x 및 6.x
+        2.10.x, 2.11.x, 2.12.x, 2.13.x, 3.x, 4.x, 5.x, 6.x 및 10.x
       </td>
     </tr>
 
diff --git a/src/i18n/content/kr/docs/infrastructure/other-infrastructure-integrations/monitoring-jenkins-ot.mdx b/src/i18n/content/kr/docs/infrastructure/other-infrastructure-integrations/monitoring-jenkins-ot.mdx
index 772b0ed48c3..89daf1d5b36 100644
--- a/src/i18n/content/kr/docs/infrastructure/other-infrastructure-integrations/monitoring-jenkins-ot.mdx
+++ b/src/i18n/content/kr/docs/infrastructure/other-infrastructure-integrations/monitoring-jenkins-ot.mdx
@@ -83,4 +83,36 @@ Jenkins 파이프라인 데이터를 New Relic으로 보낸 후에는 [New Relic
   Jenkins OpenTelemetry 플러그인은 New Relic에서 유지 관리하지 않으므로 계측에 문제가 있는 경우 [플러그인의 GitHub 저장소에서 새 문제를 생성하세요](https://github.com/jenkinsci/opentelemetry-plugin/issues).
 </Callout>
 
+## 리소스 속성 및 태그 [#attributes]
+
+Jenkins 플러그인 설정에 리소스 속성을 추가할 수 있습니다. 이를 통해 모든 플러그인 생성 로그, 지표 및 트레이스 데이터에 대한 속성을 포함할 수 있습니다. 이름이 `tags.` 으로 시작하는 리소스 속성은 [Jenkins 분할에도 태그를](/docs/opentelemetry/best-practices/opentelemetry-best-practices-resources/#tags) 추가합니다.
+
+속성은 두 가지 방법으로 정의할 수 있습니다.
+
+<CollapserGroup>
+  <Collapser id="attributes-config" title="Jenkins 플러그인 설정에서 속성 정의">
+    `io.jenkins.plugins.opentelemetry.JenkinsOpenTelemetryPluginConfiguration.xml` 파일의 `configurationProperties` 요소에 리소스 속성을 추가할 수 있습니다.
+
+    예시:
+
+    ```xml
+      <configurationProperties>
+        otel.resource.attributes=attribute1=value1,attribute2=value2,tags.tag1=tagValue1
+      </configurationProperties>
+    ```
+  </Collapser>
+
+  <Collapser id="attributes-env" title="환경 변수에서 속성을 정의합니다.">
+    `OTEL_RESOURCE_ATTRIBUTES` 환경 변수를 사용하여 리소스 속성을 정의할 수 있습니다.
+
+    이 작업은 `systemctl edit jenkins` 사용하여 jenkins에 대한 systemctl 설정을 편집하고 설정의 override.conf 부분에 추가하여 Ubuntu 시스템에서 수행할 수 있습니다.
+
+    ```yml
+      [Service]
+      # Set OTel Environment Options
+      Environment="OTEL_RESOURCE_ATTRIBUTES=attribute1=value1,attribute2=value2,tags.tag1=tagValue1"
+    ```
+  </Collapser>
+</CollapserGroup>
+
 <InstallFeedback />
\ No newline at end of file
diff --git a/src/i18n/content/pt/docs/accounts/accounts-billing/new-relic-one-user-management/authentication-domains-saml-sso-scim-more.mdx b/src/i18n/content/pt/docs/accounts/accounts-billing/new-relic-one-user-management/authentication-domains-saml-sso-scim-more.mdx
index 39bd52802f1..99972aa1b02 100644
--- a/src/i18n/content/pt/docs/accounts/accounts-billing/new-relic-one-user-management/authentication-domains-saml-sso-scim-more.mdx
+++ b/src/i18n/content/pt/docs/accounts/accounts-billing/new-relic-one-user-management/authentication-domains-saml-sso-scim-more.mdx
@@ -80,9 +80,9 @@ Se você atender aos [requisitos](#requirements), poderá adicionar e gerenciar
 
 Para visualizar e configurar domínios de autenticação: no [menu do usuário](/docs/accounts/accounts-billing/general-account-settings/intro-account-settings), acesse <DNT>**Administration &gt; Authentication domains**</DNT>.
 
-Se você tiver domínios existentes, eles estarão à esquerda. Observe que a maioria das organizações terá, no máximo, dois ou três domínios: um com as configurações manuais e padrão e um ou dois para as configurações associadas ao provedor de identidade.
+Se você já tiver domínios, eles estarão na tabela. Observe que a maioria das organizações terá, no máximo, dois ou três domínios: um com as configurações manuais e padrão e um ou dois para as configurações associadas ao provedor de identidade.
 
-Para criar um novo domínio na página da interface do domínio de autenticação, clique em <DNT>**Create authentication domain**</DNT>. Para mais informações sobre as opções de configuração, continue lendo.
+Para criar um novo domínio na página da interface do usuário do domínio de autenticação, clique em <DNT>**Create authentication domain**</DNT>. Para gerenciar ou excluir um domínio de autenticação, selecione o item de menu para cada domínio de autenticação.
 
 ## Mudar para domínio diferente [#switch]
 
diff --git a/src/i18n/content/pt/docs/alerts/get-notified/destinations.mdx b/src/i18n/content/pt/docs/alerts/get-notified/destinations.mdx
index 70a5449ea13..ba1f87fd460 100644
--- a/src/i18n/content/pt/docs/alerts/get-notified/destinations.mdx
+++ b/src/i18n/content/pt/docs/alerts/get-notified/destinations.mdx
@@ -16,12 +16,23 @@ As configurações de destino contêm os detalhes da conexão para integração
 A plataforma de destino suportada inclui:
 
 * Atlassian Jira: Disponível em [fluxo de trabalho](/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/incident-workflows/), [Errors Inbox](/docs/errors-inbox/).
+
 * ServiceNow: Disponível em [fluxo de trabalho](/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/incident-workflows/).
+
 * Slack: Disponível em [Fluxo de trabalho](/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/incident-workflows/), [Errors Inbox](/docs/errors-inbox/) e [Discussões](/docs/new-relic-solutions/new-relic-one/ui-data/collaborate/collaboration-slack-integration/).
+
 * Webhook: Disponível em [fluxo de trabalho](/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/incident-workflows/).
+
+  <Callout variant="important">
+    Se você estiver usando conectores baseados em webhook do Microsoft Office 365 no Teams para alertas do New Relic, atualize os URLs do webhook para o novo formato até 31 de janeiro de 2025. Para obter mais informações sobre como atualizar o URL do webhook, consulte [o Fim da vida útil (EOL) da Microsoft para conectores do Office 365 no Teams](https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/).
+  </Callout>
+
 * E-mail: Disponível em [Fluxo de trabalho](/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/incident-workflows/) e [Discussões](/docs/new-relic-solutions/new-relic-one/ui-data/collaborate/collaborate-with-teammates/).
+
 * AWS EventBridge: Disponível em [fluxo de trabalho](/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/incident-workflows/).
+
 * PagerDuty: Disponível em [fluxo de trabalho](/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/incident-workflows/).
+
 * New Relic Mobile Push: Disponível em [fluxo de trabalho](/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/incident-workflows/).
 
 Para saber mais sobre esses e outros destinos, consulte [integração de notificação](/docs/alerts-applied-intelligence/notifications/notification-integrations).
@@ -35,30 +46,13 @@ As configurações de destino exigem [permissões](/docs/accounts/accounts-billi
 
 ## Gerenciar destinos [#manage-destinations]
 
-<img
-  title="Destinations overview page"
-  alt="Destinations overview page."
-  src="/images/accounts_screenshot-full_destinations-overview.webp"
-/>
+<img title="Destinations overview page" alt="Destinations overview page." src="/images/accounts_screenshot-full_destinations-overview.webp" />
 
 <figcaption>
-  Vá para <DNT>**[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Alerts > Destinations**</DNT>. Utilize destinos para escolher para onde suas notificações serão enviadas.
+  Vá para <DNT>**[one.newrelic.com &gt; All capabilities](https://one.newrelic.com/all-capabilities) &amp;gt; Alerts &amp;gt; Destinations**</DNT>. Utilize destinos para escolher para onde suas notificações serão enviadas.
 </figcaption>
 
-1. Vá para
-
-   <DNT>
-     **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Alerts > Enrich and Notify > Destinations**
-   </DNT>
-
-   . A tabela
-
-   <DNT>
-     **Destinations**
-   </DNT>
-
-   mostra informações sobre os destinos existentes e permite que o usuário ative, desative e modifique.
-
+1. Vá para <DNT>**[one.newrelic.com &gt; All capabilities](https://one.newrelic.com/all-capabilities) &amp;gt; Alerts &amp;gt; Enrich and Notify &amp;gt; Destinations**</DNT>. A tabela <DNT>**Destinations**</DNT> mostra informações sobre os destinos existentes e permite que o usuário ative, desative e modifique.
 2. Para adicionar um destino, clique no bloco da plataforma apropriado. Para modificar as configurações de destino, clique na linha de destino na tabela de destinos.
 
 Você também pode configurar destinos com nossa [API NerdGraph](/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-destinations).
@@ -84,14 +78,10 @@ Status disponíveis:
 
 Você pode visualizar o status do destino na tabela <DNT>**Destinations**</DNT> e na etapa <DNT>**Select a destination**</DNT> ao configurar o modelo de canal. Você também pode revisar o estado usando a API Nerdgraph com a propriedade `status` .
 
-<img
-  title="Destination status in the Destinations table."
-  alt="Destination status in the Destinations table."
-  src="/images/accounts_screenshot-full_destinations-status.webp"
-/>
+<img title="Destination status in the Destinations table." alt="Destination status in the Destinations table." src="/images/accounts_screenshot-full_destinations-status.webp" />
 
 <figcaption>
-  Vá para <DNT>**[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Alerts > Destinations**</DNT>. Clique na guia <DNT>**Destinations**</DNT> para ver a tabela de destinos.
+  Vá para <DNT>**[one.newrelic.com &gt; All capabilities](https://one.newrelic.com/all-capabilities) &amp;gt; Alerts &amp;gt; Destinations**</DNT>. Clique na guia <DNT>**Destinations**</DNT> para ver a tabela de destinos.
 </figcaption>
 
 ### logde notificação de problemas [#notifications-log]
@@ -104,7 +94,9 @@ Se, por algum motivo, o envio de um evento de notificação falhar, o erro resul
 
 Isto é especialmente útil se estiver usando o recurso <DNT>**Alert conditions (policies)**</DNT> e [fluxo de trabalho](/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/incident-workflows/) . Dessa forma, você pode criar uma condição que é acionada no caso de um erro de notificação, e uma nova notificação pode ser enviada para outro lugar.
 
-Uma demonstração passo a passo de como adicionar um notificador de erros pode ser encontrada abaixo:<Video type="wistia" id="b89ctyjolq"/>
+Uma demonstração passo a passo de como adicionar um notificador de erros pode ser encontrada abaixo:
+
+<Video type="wistia" id="b89ctyjolq" />
 
 Condição de exemplo:
 
@@ -118,4 +110,4 @@ Depois, você pode utilizar esta condição no criador de consulta da configura
 
 ### Destino adiado [#Snoozed-destination]
 
-Adiar: Para minimizar o ruído de erro em destinos com falha, "adiamos" os destinos. Se uma notificação enviada para um destino específico falhar dentro de um período de duas horas, "suspendemos" o destino por alguns minutos. Neste período não enviaremos notificações para esse destino.
+Adiar: Para minimizar o ruído de erro em destinos com falha, &quot;adiamos&quot; os destinos. Se uma notificação enviada para um destino específico falhar dentro de um período de duas horas, &quot;suspendemos&quot; o destino por alguns minutos. Neste período não enviaremos notificações para esse destino.
\ No newline at end of file
diff --git a/src/i18n/content/pt/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx b/src/i18n/content/pt/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx
index 3e7957bacea..a89766f4599 100644
--- a/src/i18n/content/pt/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx
+++ b/src/i18n/content/pt/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx
@@ -251,7 +251,7 @@ Após a instalação, o agente automaticamente instrumento com nosso catálogo d
 
 **Nota**: A versão suportada mais recente pode não refletir a versão suportada mais recente.
 
-| Nome do pacote | Versão mínima suportada | Última versão suportada | Introduzido em\* | | --- | --- | --- | --- | | `@apollo/gateway` | 2.3.0 | 2.9.3 | `@newrelic/apollo-server-plugin@1.0.0` | | `@apollo/server` | 4.0.0 | 4.11.2 | `@newrelic/apollo-server-plugin@2.1.0` | | `@aws-sdk/client-bedrock-runtime` | 3.474.0 | 3.714.0 | 11.13.0 | | `@aws-sdk/client-dynamodb` | 3.0.0 | 3.714.0 | 8.7.1 | | `@aws-sdk/client-sns` | 3.0.0 | 3.714.0 | 8.7.1 | | `@aws-sdk/client-sqs` | 3.0.0 | 3.714.0 | 8.7.1 | | `@aws-sdk/lib-dynamodb` | 3.377.0 | 3.714.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.24 | 11.13.0 | | `@nestjs/cli` | 9.0.0 | 10.4.9 | 10.1.0 | | `@prisma/client` | 5.0.0 | 6.1.0 | 11.0.0 | | `@smithy/smithy-client` | 2.0.0 | 3.5.0 | 11.0.0 | | `amqplib` | 0.5.0 | 0.10.5 | 2.0.0 | | `apollo-server` | 3.0.0 | 3.13.0 | `@newrelic/apollo-server-plugin@1.0.0` | | `apollo-server-express` | 3.0.0 | 3.13.0 | `@newrelic/apollo-server-plugin@1.0.0` | | `aws-sdk` | 2.2.48 | 2.1692.0 | 6.2.0 | | `bluebird` | 2.0.0 | 3.7.2 | 1.27.0 | | `bunyan` | 1.8.12 | 1.8.15 | 9.3.0 | | `cassandra-driver` | 3.4.0 | 4.7.2 | 1.7.1 | | `connect` | 3.0.0 | 3.7.0 | 2.6.0 | | `express` | 4.6.0 | 4.21.2 | 2.6.0 | | `fastify` | 2.0.0 | 5.2.0 | 8.5.0 | | `generic-pool` | 3.0.0 | 3.9.0 | 0.9.0 | | `ioredis` | 4.0.0 | 5.4.1 | 1.26.2 | | `kafkajs` | 2.0.0 | 2.2.4 | 11.19.0 | | `koa` | 2.0.0 | 2.15.3 | 3.2.0 | | `koa-route` | 3.0.0 | 4.0.1 | 3.2.0 | | `koa-router` | 11.0.2 | 13.0.1 | 3.2.0 | | `memcached` | 2.2.0 | 2.2.2 | 1.26.2 | | `mongodb` | 4.1.4 | 6.12.0 | 1.32.0 | | `mysql` | 2.2.0 | 2.18.1 | 1.32.0 | | `mysql2` | 2.0.0 | 3.11.5 | 1.32.0 | | `next` | 13.4.19 | 15.1.1 | 12.0.0 | | `openai` | 4.0.0 | 4.77.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.5.0 | 8.11.0 | | `q` | 1.3.0 | 1.5.1 | 1.26.2 | | `redis` | 3.1.0 | 4.7.0 | 1.31.0 | | `restify` | 11.0.0 | 11.1.0 | 2.6.0 | | `superagent` | 3.0.0 | 10.1.1 | 4.9.0 | | `undici` | 5.0.0 | 7.2.0 | 11.1.0 | | `when` | 3.7.0 | 3.7.8 | 1.26.2 | | `winston` | 3.0.0 | 3.17.0 | 8.11.0 |
+| Nome do pacote | Versão mínima suportada | Última versão suportada | Introduzido em\* | | --- | --- | --- | --- | | `@apollo/gateway` | 2.3.0 | 2.9.3 | `@newrelic/apollo-server-plugin@1.0.0` | | `@apollo/server` | 4.0.0 | 4.11.2 | `@newrelic/apollo-server-plugin@2.1.0` | | `@aws-sdk/client-bedrock-runtime` | 3.474.0 | 3.716.0 | 11.13.0 | | `@aws-sdk/client-dynamodb` | 3.0.0 | 3.716.0 | 8.7.1 | | `@aws-sdk/client-sns` | 3.0.0 | 3.716.0 | 8.7.1 | | `@aws-sdk/client-sqs` | 3.0.0 | 3.716.0 | 8.7.1 | | `@aws-sdk/lib-dynamodb` | 3.377.0 | 3.716.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.27 | 11.13.0 | | `@nestjs/cli` | 9.0.0 | 10.4.9 | 10.1.0 | | `@opensearch-project/opensearch` | 2.1.0 | 2.13.0 | 12.10.0 | | `@prisma/client` | 5.0.0 | 6.1.0 | 11.0.0 | | `@smithy/smithy-client` | 2.0.0 | 3.5.2 | 11.0.0 | | `amqplib` | 0.5.0 | 0.10.5 | 2.0.0 | | `apollo-server` | 3.0.0 | 3.13.0 | `@newrelic/apollo-server-plugin@1.0.0` | | `apollo-server-express` | 3.0.0 | 3.13.0 | `@newrelic/apollo-server-plugin@1.0.0` | | `aws-sdk` | 2.2.48 | 2.1692.0 | 6.2.0 | | `bluebird` | 2.0.0 | 3.7.2 | 1.27.0 | | `bunyan` | 1.8.12 | 1.8.15 | 9.3.0 | | `cassandra-driver` | 3.4.0 | 4.7.2 | 1.7.1 | | `connect` | 3.0.0 | 3.7.0 | 2.6.0 | | `express` | 4.6.0 | 4.21.2 | 2.6.0 | | `fastify` | 2.0.0 | 5.2.0 | 8.5.0 | | `generic-pool` | 3.0.0 | 3.9.0 | 0.9.0 | | `ioredis` | 4.0.0 | 5.4.2 | 1.26.2 | | `kafkajs` | 2.0.0 | 2.2.4 | 11.19.0 | | `koa` | 2.0.0 | 2.15.3 | 3.2.0 | | `koa-route` | 3.0.0 | 4.0.1 | 3.2.0 | | `koa-router` | 11.0.2 | 13.0.1 | 3.2.0 | | `memcached` | 2.2.0 | 2.2.2 | 1.26.2 | | `mongodb` | 4.1.4 | 6.12.0 | 1.32.0 | | `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.3 | 12.0.0 | | `openai` | 4.0.0 | 4.77.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 | | `q` | 1.3.0 | 1.5.1 | 1.26.2 | | `redis` | 3.1.0 | 4.7.0 | 1.31.0 | | `restify` | 11.0.0 | 11.1.0 | 2.6.0 | | `superagent` | 3.0.0 | 10.1.1 | 4.9.0 | | `undici` | 5.0.0 | 7.2.0 | 11.1.0 | | `when` | 3.7.0 | 3.7.8 | 1.26.2 | | `winston` | 3.0.0 | 3.17.0 | 8.11.0 |
 
 \*Quando o pacote não é especificado, o suporte está dentro do pacote `newrelic` .
 
diff --git a/src/i18n/content/pt/docs/browser/browser-monitoring/browser-pro-features/session-replay.mdx b/src/i18n/content/pt/docs/browser/browser-monitoring/browser-pro-features/session-replay.mdx
index b769228e92a..fb1c9a6b8ab 100644
--- a/src/i18n/content/pt/docs/browser/browser-monitoring/browser-pro-features/session-replay.mdx
+++ b/src/i18n/content/pt/docs/browser/browser-monitoring/browser-pro-features/session-replay.mdx
@@ -173,6 +173,10 @@ Para obter mais detalhes sobre Session Replay, consulte as seções a seguir:
   </Step>
 </Steps>
 
+<Callout variant="important">
+  Certain settings, including enabling or disabling session replay and adjusting sample rates for overall and errors, have been moved to server-side configuration. For example, after you update these settings for copy/paste installation method, there&apos;s no need to redeploy the script. This is applicable for browser agent version `1.259.0` or higher.
+</Callout>
+
 ## Resolução de problemas [#troubleshoot]
 
 <CollapserGroup>
diff --git a/src/i18n/content/pt/docs/infrastructure/amazon-integrations/connect/set-up-aws-api-polling.mdx b/src/i18n/content/pt/docs/infrastructure/amazon-integrations/connect/set-up-aws-api-polling.mdx
index 58000470e6f..ca6588efb76 100644
--- a/src/i18n/content/pt/docs/infrastructure/amazon-integrations/connect/set-up-aws-api-polling.mdx
+++ b/src/i18n/content/pt/docs/infrastructure/amazon-integrations/connect/set-up-aws-api-polling.mdx
@@ -24,7 +24,7 @@ Para usuários AWS que desejam coletar dados sobre todos os outros serviços, re
 * O intervalo de sondagem mais rápido para pesquisa API é de 5 minutos, enquanto CloudWatch Metric Streams transmite dados métricos em menos de 2 minutos.
 * A AWS limita a pesquisa de API, enquanto a integração do CloudWatch Metric Streams elimina completamente a limitação de API.
 
-Confira nossa documentação para [instalar a integração do New Relic CloudWatch Metric Streams ](/docs/infrastructure/amazon-integrations/connect/aws-metric-stream-setup)ou para [migrar sua integração de pesquisa API para CloudWatch Metric Streams](/docs/infrastructure/amazon-integrations/connect/aws-metric-stream-setup/#migrate).
+Confira nossa documentação para [instalar uma integração do New Relic CloudWatch Metric Streams ](/install/aws-cloudwatch)ou para [migrar sua integração de pesquisa API para CloudWatch Metric Streams](/install/aws-cloudwatch/?task=migrate).
 
 ## Configurar sondagem de API [#set-up-api]
 
diff --git a/src/i18n/content/pt/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-firehose-nozzle-integration.mdx b/src/i18n/content/pt/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-firehose-nozzle-integration.mdx
index cd62b682098..ff8f730bffc 100644
--- a/src/i18n/content/pt/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-firehose-nozzle-integration.mdx
+++ b/src/i18n/content/pt/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-firehose-nozzle-integration.mdx
@@ -26,7 +26,7 @@ O New Relic Nozzle para VMware Tanzu tem os seguintes requisitos:
 
 * Uma conta New Relic ativa com uma licença Pro ou Pro Trial. Se você ainda não possui uma conta New Relic, você pode obter uma [licença teste grátis de 14 dias](http://newrelic.com/signup?funnel=pivotal-cloud-foundry&partner=Pivotal+Cloud+Foundry).
 * Insights da New Relic incluídos na licença
-* VMware Tanzu versões v2.10.x até v6.0.x.
+* VMware Tanzu versões v2.10.x até v10.0.x.
 
 ## Recurso chave [#key-features]
 
@@ -128,7 +128,7 @@ A tabela a seguir fornece informações de versão e suporte de versão sobre o
       </td>
 
       <td>
-        v2.10.x, v2.11.x, v2.12.x, v2.13.x, v3.0.x, v4.0.x, v5.0.x e v6.0.x
+        v2.10.x, v2.11.x, v2.12.x, v2.13.x, v3.0.x, v4.0.x, v5.0.x, v6.0.x e v10.0.x
       </td>
     </tr>
 
diff --git a/src/i18n/content/pt/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-nginx-buildpack-integration.mdx b/src/i18n/content/pt/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-nginx-buildpack-integration.mdx
index 59a4e8c049d..994ffc4d79e 100644
--- a/src/i18n/content/pt/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-nginx-buildpack-integration.mdx
+++ b/src/i18n/content/pt/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-nginx-buildpack-integration.mdx
@@ -15,7 +15,7 @@ Simplifique o monitoramento e a resolução de problemas do NGINX com o buildpac
 
 ## Requisitos e compatibilidade [#requirements-compatibility]
 
-Este produto foi testado e é compatível com as versões do VMware Tanzu OpsManager até e incluindo v3.0 e Tanzu aplicativo Service 4.0, 5.0 e 6.0.
+Certificamos o produto com versões do VMware Tanzu OpsManager até v3.0.x e Tanzu aplicativo Service versões 4.x, 5.x, 6.x e 10.x.
 
 O buildpack de integração New Relic NGINX para VMware Tanzu requer o seguinte:
 
@@ -49,7 +49,7 @@ A tabela a seguir fornece informações de suporte de versão sobre o buildpack
       </td>
 
       <td>
-        1.0.2
+        1.1.2
       </td>
     </tr>
 
@@ -59,7 +59,7 @@ A tabela a seguir fornece informações de suporte de versão sobre o buildpack
       </td>
 
       <td>
-        09 de agosto de 2024
+        06 de janeiro de 2025
       </td>
     </tr>
 
@@ -69,7 +69,7 @@ A tabela a seguir fornece informações de suporte de versão sobre o buildpack
       </td>
 
       <td>
-        Pacote de integração New Relic NGINX para VMware Tanzu 1.0.2
+        Pacote de integração New Relic NGINX para VMware Tanzu 1.1.2
       </td>
     </tr>
 
@@ -89,7 +89,7 @@ A tabela a seguir fornece informações de suporte de versão sobre o buildpack
       </td>
 
       <td>
-        4.0.x, 5.0.x e 6.0.x
+        4.x, 5.x, 6.x e 10.x
       </td>
     </tr>
 
@@ -136,7 +136,7 @@ Você pode instalar os buildpacks como um bloco no Ops Manager ou individualment
     <TabsPageItem id="ops-manager-tile">
       <Steps>
         <Step>
-          Baixe a versão mais recente do bloco (atualmente `newrelic-nginx-buildpack-1.0.1.pivotal`) no [site de download da Broadcom](https://support.broadcom.com/group/ecx/productdownloads?subfamily=New%20Relic%20Nginx%20Integration%20Buildpack%20for%20VMware%20Tanzu) ou no [repositório GitHub da New Relic em releases](https://github.com/newrelic/newrelic-pcf-nginx-buildpack/releases).
+          Baixe a versão mais recente do bloco (atualmente `newrelic-nginx-buildpack-1.1.2.pivotal`) no [site de download da Broadcom](https://support.broadcom.com/group/ecx/productdownloads?subfamily=New%20Relic%20Nginx%20Integration%20Buildpack%20for%20VMware%20Tanzu) ou no [repositório GitHub da New Relic em releases](https://github.com/newrelic/newrelic-pcf-nginx-buildpack/releases).
         </Step>
 
         <Step>
diff --git a/src/i18n/content/pt/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-service-broker-integration.mdx b/src/i18n/content/pt/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-service-broker-integration.mdx
index 22a2bc22349..083e059d2d3 100644
--- a/src/i18n/content/pt/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-service-broker-integration.mdx
+++ b/src/i18n/content/pt/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-service-broker-integration.mdx
@@ -109,7 +109,7 @@ A tabela a seguir fornece informações de versão e suporte de versão sobre o
       </td>
 
       <td>
-        2.10.x, 2.11.x, 2.12.x, 2.13.x, 3.x, 4.x, 5.x e 6.x
+        2.10.x, 2.11.x, 2.12.x, 2.13.x, 3.x, 4.x, 5.x, 6.x e 10.x
       </td>
     </tr>
 
diff --git a/src/i18n/content/pt/docs/infrastructure/other-infrastructure-integrations/monitoring-jenkins-ot.mdx b/src/i18n/content/pt/docs/infrastructure/other-infrastructure-integrations/monitoring-jenkins-ot.mdx
index ffbcef8d443..94c51b6b58e 100644
--- a/src/i18n/content/pt/docs/infrastructure/other-infrastructure-integrations/monitoring-jenkins-ot.mdx
+++ b/src/i18n/content/pt/docs/infrastructure/other-infrastructure-integrations/monitoring-jenkins-ot.mdx
@@ -83,4 +83,36 @@ Depois de enviar os dados do pipeline Jenkins para o New Relic, você também po
   O plug-in Jenkins OpenTelemetry não é mantido pela New Relic, portanto, se você tiver algum problema com a instrumentação, [crie um novo problema no repositório GitHub do plug-in](https://github.com/jenkinsci/opentelemetry-plugin/issues).
 </Callout>
 
+## Atributo e tag de recurso [#attributes]
+
+Você pode adicionar atributos de recursos à configuração do plugin Jenkins. Isso permite que você inclua atributos para todos os dados de log, métrica e trace gerados pelo plugin. Atributos de recursos que têm nomes começando com `tags.` também adicionarão [a tag entidade à sua entidade do Jenkins](/docs/opentelemetry/best-practices/opentelemetry-best-practices-resources/#tags).
+
+Você pode definir atributo de duas maneiras:
+
+<CollapserGroup>
+  <Collapser id="attributes-config" title="Definir atributo na configuração do plugin Jenkins">
+    Você pode adicionar o atributo de recurso ao elemento `configurationProperties` no arquivo `io.jenkins.plugins.opentelemetry.JenkinsOpenTelemetryPluginConfiguration.xml` .
+
+    Exemplo:
+
+    ```xml
+      <configurationProperties>
+        otel.resource.attributes=attribute1=value1,attribute2=value2,tags.tag1=tagValue1
+      </configurationProperties>
+    ```
+  </Collapser>
+
+  <Collapser id="attributes-env" title="Defina atributo nas variáveis de ambiente">
+    Você pode definir o atributo de recurso usando a variável de ambiente `OTEL_RESOURCE_ATTRIBUTES` .
+
+    Isso pode ser feito em um sistema Ubuntu editando a configuração systemctl para jenkins usando `systemctl edit jenkins` e adicionando à parte override.conf da configuração:
+
+    ```yml
+      [Service]
+      # Set OTel Environment Options
+      Environment="OTEL_RESOURCE_ATTRIBUTES=attribute1=value1,attribute2=value2,tags.tag1=tagValue1"
+    ```
+  </Collapser>
+</CollapserGroup>
+
 <InstallFeedback />
\ No newline at end of file