From 993cb245a04de1f1e2f9a011b9a3b0ffdb7de204 Mon Sep 17 00:00:00 2001 From: svc-docs-eng-opensource-bot Date: Tue, 12 Aug 2025 12:05:30 +0000 Subject: [PATCH 1/2] chore: add translations --- .../nerdgraph-scorecards-custom-tutorial.mdx | 85 +++--- .../manage-synthetics-monitors-rest-api.mdx | 279 ++++++++---------- .../ssl-or-connection-errors-java.mdx | 14 +- .../nodejs-agent-configuration.mdx | 12 +- .../browser-apis/addpageaction.mdx | 2 +- .../browser-apis/recordCustomEvent.mdx | 2 +- .../instrumentation-browser-monitoring.mdx | 2 +- .../browser-monitoring-performance-impact.mdx | 4 +- .../change-tracking-events.mdx | 2 +- .../agent-control/configuration.mdx | 217 +++++++++++--- .../pipeline-control/cloud-rules-api.mdx | 6 +- .../data-dropping-gateway.mdx | 8 +- .../pipeline-control/nrql-functions.mdx | 4 +- .../docs-release-notes/docs-7-25-2025.mdx | 2 +- .../docs-release-notes/docs-8-08-2025.mdx | 60 ++++ .../new-relic-infrastructure-agent-1655.mdx | 5 +- .../new-relic-android-5306.mdx | 11 + .../browser-agent-v1.295.mdx | 39 +++ .../github-integration.mdx | 2 +- .../guide-to-monitoring-core-web-vitals.mdx | 226 ++++---------- .../organize-large-logs.mdx | 26 +- .../nerdgraph-scorecards-custom-tutorial.mdx | 85 +++--- .../manage-synthetics-monitors-rest-api.mdx | 13 +- .../ssl-or-connection-errors-java.mdx | 2 +- .../nodejs-agent-configuration.mdx | 12 +- .../browser-apis/addpageaction.mdx | 2 +- .../browser-apis/recordCustomEvent.mdx | 2 +- .../instrumentation-browser-monitoring.mdx | 2 +- .../browser-monitoring-performance-impact.mdx | 4 +- .../change-tracking-events.mdx | 2 +- .../agent-control/configuration.mdx | 217 +++++++++++--- .../pipeline-control/cloud-rules-api.mdx | 6 +- .../data-dropping-gateway.mdx | 8 +- .../pipeline-control/nrql-functions.mdx | 4 +- .../docs-release-notes/docs-7-25-2025.mdx | 2 +- .../docs-release-notes/docs-8-08-2025.mdx | 60 ++++ .../new-relic-infrastructure-agent-1655.mdx | 5 +- .../new-relic-android-5306.mdx | 11 + .../browser-agent-v1.295.mdx | 39 +++ .../github-integration.mdx | 2 +- .../guide-to-monitoring-core-web-vitals.mdx | 58 ++-- .../organize-large-logs.mdx | 24 +- .../nerdgraph-scorecards-custom-tutorial.mdx | 83 +++--- .../manage-synthetics-monitors-rest-api.mdx | 13 +- .../ssl-or-connection-errors-java.mdx | 4 +- .../browser-apis/addpageaction.mdx | 2 +- .../browser-apis/recordCustomEvent.mdx | 2 +- .../browser-monitoring-performance-impact.mdx | 4 +- .../change-tracking-events.mdx | 2 +- .../agent-control/configuration.mdx | 217 +++++++++++--- .../pipeline-control/cloud-rules-api.mdx | 6 +- .../data-dropping-gateway.mdx | 8 +- .../pipeline-control/nrql-functions.mdx | 4 +- .../docs-release-notes/docs-7-25-2025.mdx | 2 +- .../docs-release-notes/docs-8-08-2025.mdx | 60 ++++ .../new-relic-infrastructure-agent-1655.mdx | 11 +- .../new-relic-android-5306.mdx | 11 + .../browser-agent-v1.295.mdx | 39 +++ .../github-integration.mdx | 4 +- .../guide-to-monitoring-core-web-vitals.mdx | 212 ++++--------- .../organize-large-logs.mdx | 24 +- .../nerdgraph-scorecards-custom-tutorial.mdx | 85 +++--- .../manage-synthetics-monitors-rest-api.mdx | 13 +- .../ssl-or-connection-errors-java.mdx | 6 +- .../browser-apis/addpageaction.mdx | 2 +- .../browser-apis/recordCustomEvent.mdx | 2 +- .../instrumentation-browser-monitoring.mdx | 2 +- .../browser-monitoring-performance-impact.mdx | 4 +- .../change-tracking-events.mdx | 2 +- .../agent-control/configuration.mdx | 217 +++++++++++--- .../pipeline-control/cloud-rules-api.mdx | 6 +- .../data-dropping-gateway.mdx | 8 +- .../pipeline-control/nrql-functions.mdx | 4 +- .../docs-release-notes/docs-7-25-2025.mdx | 2 +- .../docs-release-notes/docs-8-08-2025.mdx | 60 ++++ .../new-relic-infrastructure-agent-1655.mdx | 5 +- .../new-relic-android-5306.mdx | 11 + .../browser-agent-v1.295.mdx | 39 +++ .../github-integration.mdx | 2 +- .../guide-to-monitoring-core-web-vitals.mdx | 212 ++++--------- .../organize-large-logs.mdx | 24 +- .../nerdgraph-scorecards-custom-tutorial.mdx | 85 +++--- .../manage-synthetics-monitors-rest-api.mdx | 13 +- .../ssl-or-connection-errors-java.mdx | 4 +- .../nodejs-agent-configuration.mdx | 12 +- .../browser-apis/addpageaction.mdx | 2 +- .../browser-apis/recordCustomEvent.mdx | 2 +- .../instrumentation-browser-monitoring.mdx | 2 +- .../browser-monitoring-performance-impact.mdx | 4 +- .../cci/configure-cci/general-setting.mdx | 12 +- .../change-tracking-events.mdx | 2 +- .../agent-control/configuration.mdx | 217 +++++++++++--- .../pipeline-control/cloud-rules-api.mdx | 6 +- .../data-dropping-gateway.mdx | 8 +- .../pipeline-control/nrql-functions.mdx | 4 +- .../docs-release-notes/docs-7-25-2025.mdx | 2 +- .../docs-release-notes/docs-8-08-2025.mdx | 60 ++++ .../new-relic-infrastructure-agent-1655.mdx | 5 +- .../new-relic-android-5306.mdx | 11 + .../browser-agent-v1.295.mdx | 39 +++ .../github-integration.mdx | 2 +- .../guide-to-monitoring-core-web-vitals.mdx | 226 ++++---------- .../organize-large-logs.mdx | 24 +- 103 files changed, 2247 insertions(+), 1477 deletions(-) create mode 100644 src/i18n/content/es/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx create mode 100644 src/i18n/content/es/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5306.mdx create mode 100644 src/i18n/content/es/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx create mode 100644 src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx create mode 100644 src/i18n/content/fr/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5306.mdx create mode 100644 src/i18n/content/fr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx create mode 100644 src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx create mode 100644 src/i18n/content/jp/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5306.mdx create mode 100644 src/i18n/content/jp/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx create mode 100644 src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx create mode 100644 src/i18n/content/kr/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5306.mdx create mode 100644 src/i18n/content/kr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx create mode 100644 src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx create mode 100644 src/i18n/content/pt/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5306.mdx create mode 100644 src/i18n/content/pt/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx diff --git a/src/i18n/content/es/docs/apis/nerdgraph/examples/nerdgraph-scorecards-custom-tutorial.mdx b/src/i18n/content/es/docs/apis/nerdgraph/examples/nerdgraph-scorecards-custom-tutorial.mdx index 85f8918c7e2..839d633f9ea 100644 --- a/src/i18n/content/es/docs/apis/nerdgraph/examples/nerdgraph-scorecards-custom-tutorial.mdx +++ b/src/i18n/content/es/docs/apis/nerdgraph/examples/nerdgraph-scorecards-custom-tutorial.mdx @@ -98,24 +98,23 @@ New Relic proporciona varias mutaciones de NerdGraph para crear roles personaliz #### Solicitud de muestra ```graphql - { + { customerAdministration { - permissions(filter: {scope: {eq: "organization"}}) { - items { - feature - category - id - product - } + permissions(filter: { scope: { eq: "organization" } }) { + items { + feature + category + id + product } } } - + } ``` #### Ejemplo de respuesta - ```graphql + ```json { "data": { "customerAdministration": { @@ -174,31 +173,28 @@ New Relic proporciona varias mutaciones de NerdGraph para crear roles personaliz } } } - ``` Copie y pegue la información relacionada con Scorecards en un archivo de texto que coincida con los siguientes criterios: * `category: MANAGE` - * `"feature"``: "Scorecards"` o `“Scorecards Rules”` + * `"feature"``: "Scorecards"` o `"Scorecards Rules"` Por ejemplo, en la respuesta anterior, lo siguiente coincide con los criterios: - ```graphql - + ```json { - "category": "MANAGE", - "feature": "Scorecards Rules", - "id": "xxxxx", - "product": "New Relic One" - }, + "category": "MANAGE", + "feature": "Scorecards Rules", + "id": "xxxxx", + "product": "New Relic One" + }, { - "category": "MANAGE", - "feature": "Scorecards", - "id": "xxxxx", - "product": "New Relic One" - } - + "category": "MANAGE", + "feature": "Scorecards", + "id": "xxxxx", + "product": "New Relic One" + } ``` @@ -208,19 +204,18 @@ New Relic proporciona varias mutaciones de NerdGraph para crear roles personaliz #### Solicitud de muestra ```graphql - { + { actor { organization { id - } } } - + } ``` #### Ejemplo de respuesta - ```graphql + ```json { "data": { "actor": { @@ -230,7 +225,6 @@ New Relic proporciona varias mutaciones de NerdGraph para crear roles personaliz } } } - ``` Copie el ID de la organización y déjelo a un lado para crear un rol. @@ -323,11 +317,11 @@ New Relic proporciona varias mutaciones de NerdGraph para crear roles personaliz - `PermissionId` + `permissionIds` - En t + \[Int] @@ -370,10 +364,9 @@ New Relic proporciona varias mutaciones de NerdGraph para crear roles personaliz #### Solicitud de muestra ```graphql - mutation { customRoleCreate( - container: {id: "xxx****xxx-xx**00**-xxx-x*x*-xx**XXX**XX", type: "organization"} + container: { id: "xxx****xxx-xx**00**-xxx-x*x*-xx**XXX**XX", type: "organization" } name: "Scorecards manager" permissionIds: [xxxxx, xxxxx] scope: "organization" @@ -381,13 +374,11 @@ New Relic proporciona varias mutaciones de NerdGraph para crear roles personaliz id } } - ``` #### Ejemplo de respuesta - ```graphql - + ```json { "data": { "customRoleCreate": { @@ -395,7 +386,6 @@ New Relic proporciona varias mutaciones de NerdGraph para crear roles personaliz } } } - ``` @@ -487,10 +477,9 @@ New Relic proporciona varias mutaciones de NerdGraph para crear roles personaliz #### Solicitud de muestra ```graphql - { customerAdministration { - groups(filter: {organizationId: {eq: "xxx****xxx-xx**00**-xxx-x*x*-xx**XXX**XX"}}) { + groups(filter: { organizationId: { eq: "xxx****xxx-xx**00**-xxx-x*x*-xx**XXX**XX" } }) { nextCursor items { id @@ -505,7 +494,6 @@ New Relic proporciona varias mutaciones de NerdGraph para crear roles personaliz } } } - ``` De la lista de ID de grupo que se muestra, copie el ID de grupo que desee asociar con el rol de Scorecard personalizado que creó anteriormente. @@ -552,11 +540,7 @@ New Relic proporciona varias mutaciones de NerdGraph para crear roles personaliz @@ -585,7 +569,10 @@ New Relic proporciona varias mutaciones de NerdGraph para crear roles personaliz ```graphql mutation { authorizationManagementGrantAccess( - grantAccessOptions: {organizationAccessGrants: {roleId: "99999999"}, groupId: "xxx****xxx-xx**00**-xxx-x*x*-xx**XXX**XX"} + grantAccessOptions: { + organizationAccessGrants: { roleId: "99999999" } + groupId: "xxx****xxx-xx**00**-xxx-x*x*-xx**XXX**XX" + } ) { roles { id @@ -597,12 +584,11 @@ New Relic proporciona varias mutaciones de NerdGraph para crear roles personaliz } } } - ``` #### Ejemplo de respuesta - ```graphql + ```json { "data": { "authorizationManagementGrantAccess": { @@ -619,7 +605,6 @@ New Relic proporciona varias mutaciones de NerdGraph para crear roles personaliz } } } - ``` diff --git a/src/i18n/content/es/docs/apis/synthetics-rest-api/monitor-examples/manage-synthetics-monitors-rest-api.mdx b/src/i18n/content/es/docs/apis/synthetics-rest-api/monitor-examples/manage-synthetics-monitors-rest-api.mdx index 8ecdbc734fb..fd9492f51e6 100644 --- a/src/i18n/content/es/docs/apis/synthetics-rest-api/monitor-examples/manage-synthetics-monitors-rest-api.mdx +++ b/src/i18n/content/es/docs/apis/synthetics-rest-api/monitor-examples/manage-synthetics-monitors-rest-api.mdx @@ -13,11 +13,15 @@ Utilice la API REST de sintéticos para crear y administrar [el monitor de monit ## Antes de que empieces [#before-you-start] + + El 22 de octubre de 2024 [pondremos fin a la vida útil](/whats-new/2024/04/whats-new-04-09-eol-synthetics-runtime-cpm) de las versiones minion privado (CPM) en contenedores y tiempo de ejecución sintético legacy. A partir del 26 de agosto de 2024, ya no podrá crear nuevos monitores empleando versiones legacy de tiempo de ejecución sintética. Sintéticos API REST solo admite la creación de monitores empleando versiones legacy de tiempo de ejecución sintético. Emplee [las API de NerdGraph](/docs/apis/nerdgraph/examples/nerdgraph-synthetics-tutorial/) para gestionar sus monitores Sintético empleando nuestros últimos tiempos de ejecución para evitar la degradación. + + Nuestra API REST de sintéticos es una forma de administrar su monitor de monitoreo sintético a través de API, pero la forma recomendada es usar [nuestra API NerdGraph](/docs/apis/nerdgraph/examples/nerdgraph-synthetics-tutorial). ## Permisos [#permissions] -Para utilizar la API REST de sintéticos, debe tener [permisos](/docs/accounts/accounts-billing/new-relic-one-user-management/user-permissions) relacionados con el monitoreo sintético y un . +Para utilizar la API REST de sintéticos, debe tener [permisos](/docs/accounts/accounts-billing/new-relic-one-user-management/user-permissions) relacionados con el monitoreo sintético y un . Puede [utilizar NRQL consulta para analizar cambios anteriores realizados a través de la API](/docs/synthetics/new-relic-synthetics/administration/audit-synthetics-account-changes). @@ -83,7 +87,7 @@ Estos son los [tiposmonitor ](/docs/synthetics/new-relic-synthetics/using-monito ## Utilice la API [#use-api] -Para utilizar la [API REST de monitoreo sintético](/docs/apis/synthetics-rest-api), debe tener la capacidad de administrar el monitor de monitoreo sintético y usar una [clave de usuario](/docs/apis/rest-api-v2/getting-started/introduction-new-relic-rest-api-v2#api_key) (la clave de API REST no funcionará). +Para emplear la [API REST de monitoreo sintético](/docs/apis/synthetics-rest-api), debe tener la capacidad de gestionar monitores sintéticos y emplear una [clave de usuario](/docs/apis/rest-api-v2/getting-started/introduction-new-relic-rest-api-v2#api_key). Esta API se puede utilizar para todos los monitores de monitoreo sintético. (También hay disponibles métodos API adicionales para [browser con secuencias de comandos y monitores de prueba de API](#scripted-api-monitors-api) para actualizar las script asociadas con esos monitores). Todos los datos de monitoreo sintético están disponibles a través de la API. Los ejemplos de API muestran el comando curl. @@ -104,42 +108,36 @@ https://synthetics.eu.newrelic.com/synthetics/api - + Para ver una lista de todos los monitores en su cuenta New Relic, envíe una solicitud GET a `$API_ENDPOINT/v3/monitors`. Por ejemplo: - ``` + ```sh curl -v \ - -H "Api-Key:$API_KEY" $API_ENDPOINT/v3/monitors + -H "Api-Key:$API_KEY" $API_ENDPOINT/v3/monitors ``` Una solicitud exitosa devolverá una respuesta `200 OK` . Los [datos devueltos](/docs/apis/synthetics-rest-api/monitor-examples/payload-attributes-synthetics-rest-api#api-attributes) serán un objeto JSON en el siguiente formato: - ``` + ```json { - "monitors": [ - { - "id": "2a1bc369-7654-489d-918e-f6g135h7i2jk", - "name": "monitor1", - "type": "BROWSER", - "frequency": 60, - "uri": "http://example.com", - "locations": [ - "AWS_US_WEST_1" - ], - "status": "DISABLED", - "slaThreshold": 7, - "options": {}, - "modifiedAt": "2016-09-26T23:12:46.981+0000", - "createdAt": "2016-09-26T23:12:46.981+0000", - "userId": 0, - "apiVersion": "0.2.2" - } - ], - "count": 1 + "monitors": [ + { + "id": "2a1bc369-7654-489d-918e-f6g135h7i2jk", + "name": "monitor1", + "type": "BROWSER", + "frequency": 60, + "uri": "http://example.com", + "locations": ["AWS_US_WEST_1"], + "status": "DISABLED", + "slaThreshold": 7, + "options": {}, + "modifiedAt": "2016-09-26T23:12:46.981+0000", + "createdAt": "2016-09-26T23:12:46.981+0000", + "userId": 0, + "apiVersion": "0.2.2" + } + ], + "count": 1 } ``` @@ -150,9 +148,9 @@ https://synthetics.eu.newrelic.com/synthetics/api Puede incluirlos en su comando curl de la siguiente manera: - ``` + ```sh curl -v \ - -H "Api-Key:$API_KEY" $API_ENDPOINT/v3/monitors \ + -H "Api-Key:$API_KEY" $API_ENDPOINT/v3/monitors \ -G -d 'offset=20&limit=100' ``` @@ -163,21 +161,17 @@ https://synthetics.eu.newrelic.com/synthetics/api ``` - + Para ver un único monitor de monitoreo sintético, envíe una solicitud GET a `$API_ENDPOINT/v3/monitors/$MONITOR_ID`. - ``` + ```sh curl -v \ - -H "Api-Key:$API_KEY" $API_ENDPOINT/v3/monitors/$MONITOR_ID + -H "Api-Key:$API_KEY" $API_ENDPOINT/v3/monitors/$MONITOR_ID ``` Una solicitud exitosa devolverá una respuesta `200 OK` . Los [datos devueltos](/docs/apis/synthetics-rest-api/monitor-examples/payload-attributes-synthetics-rest-api#api-attributes) serán un objeto JSON en el siguiente formato: - ``` + ```json { "id": UUID, "name": string, @@ -195,29 +189,29 @@ https://synthetics.eu.newrelic.com/synthetics/api Una ID de monitor no válida devolverá `404 Not Found: The specified monitor doesn't exist`. - + + + El 22 de octubre de 2024 [pondremos fin a la vida útil](/whats-new/2024/04/whats-new-04-09-eol-synthetics-runtime-cpm) de las versiones minion privado (CPM) en contenedores y tiempo de ejecución sintético legacy. A partir del 26 de agosto de 2024, ya no podrá crear nuevos monitores empleando versiones legacy de tiempo de ejecución sintética. Sintéticos API REST solo admite la creación de monitores empleando versiones legacy de tiempo de ejecución sintético. Emplee [las API de NerdGraph](/docs/apis/nerdgraph/examples/nerdgraph-synthetics-tutorial/) para gestionar sus monitores Sintético empleando nuestros últimos tiempos de ejecución para evitar la degradación. + + Para agregar un nuevo monitor a su cuenta de monitoreo sintético, envíe una solicitud POST a `$API_ENDPOINT/v3/monitors` con una carga útil JSON que describa el monitor. Todos los campos del siguiente ejemplo son obligatorios a menos que se indique lo contrario: - ``` + ```json { - "name": string [required], - "type": string (SIMPLE, BROWSER, SCRIPT_API, SCRIPT_BROWSER) [required], - "frequency": integer (minutes) [required, must be one of 1, 5, 10, 15, 30, 60, 360, 720, or 1440], - "uri": string [required for SIMPLE and BROWSER type], - "locations": array of strings [at least one required], - "status": string (ENABLED, DISABLED) [required], - "slaThreshold": double, - "options": { - "validationString": string [only valid for SIMPLE and BROWSER types], - "verifySSL": boolean (true, false) [only valid for SIMPLE and BROWSER types], - "bypassHEADRequest": boolean (true, false) [only valid for SIMPLE types], - "treatRedirectAsFailure": boolean (true, false) [only valid for SIMPLE types] + "name": string [required], + "type": string (SIMPLE, BROWSER, SCRIPT_API, SCRIPT_BROWSER) [required], + "frequency": integer (minutes) [required, must be one of 1, 5, 10, 15, 30, 60, 360, 720, or 1440], + "uri": string [required for SIMPLE and BROWSER type], + "locations": array of strings [at least one required], + "status": string (ENABLED, DISABLED) [required], + "slaThreshold": double, + "options": { + "validationString": string [only valid for SIMPLE and BROWSER types], + "verifySSL": boolean (true, false) [only valid for SIMPLE and BROWSER types], + "bypassHEADRequest": boolean (true, false) [only valid for SIMPLE types], + "treatRedirectAsFailure": boolean (true, false) [only valid for SIMPLE types] } } ``` @@ -226,9 +220,9 @@ https://synthetics.eu.newrelic.com/synthetics/api Reemplace el [atributo de API REST de monitoreo sintético](/docs/apis/synthetics-rest-api/monitor-examples/payload-attributes-synthetics-rest-api) en el siguiente ejemplo con sus valores específicos: - ``` + ```sh curl -v \ - -X POST -H "Api-Key:$API_KEY" \ + -X POST -H "Api-Key:$API_KEY" \ -H 'Content-Type: application/json' $API_ENDPOINT/v3/monitors \ -d '{ "name" : "monitor1", "frequency" : 15, "uri" : "http://my-uri.com", "locations" : [ "AWS_US_WEST_1" ], "type" : "browser", "status" : "enabled", "slaThreshold" : "1.0"}' ``` @@ -239,22 +233,27 @@ https://synthetics.eu.newrelic.com/synthetics/api * `402 Payment Required`: La creación del monitor aumentará sus checks programados más allá del límite de checks comprados de su cuenta. - + Para actualizar un monitor existente en New Relic, envíe una solicitud PUT a `$API_ENDPOINT/v3/monitors/$MONITOR_ID`. Además, para monitores con script, siga los procedimientos para [actualizar el script codificado en BASE64](/docs/apis/synthetics-rest-api/monitor-examples/manage-synthetics-monitor-scripts-rest-api). Todos los campos son obligatorios. Sin embargo, se cambiará el `TYPE` del monitor **cannot** . Utilice un ID de monitor específico y reemplace el [atributo de API REST de monitoreo sintético](/docs/apis/synthetics-rest-api/monitor-examples/payload-attributes-synthetics-rest-api) con sus valores específicos. - ``` + ```sh curl -v \ - -X PUT -H "Api-Key:$API_KEY" \ + -X PUT -H "Api-Key:$API_KEY" \ -H 'Content-Type: application/json' $API_ENDPOINT/v3/monitors/$MONITOR_ID \ - -d '{ "name" : "updated monitor name", "type": "monitor type", "frequency" : 15, "uri" : "http://my-uri.com/", "locations" : [ "AWS_US_WEST_1" ], "status" : "enabled", "slaThreshold": "7.0" }' + -d \ + '{ + "name": "updated monitor name", + "type": "monitor type", + "frequency": 15, + "uri": "http://my-uri.com/", + "locations": ["AWS_US_WEST_1"], + "status": "enabled", + "slaThreshold": "7.0" + }' ``` Las solicitudes PUT están destinadas a reemplazar la entidad objetivo, por lo que todos los atributos necesarios en la carga útil JSON al [crear un nuevo monitor](/docs/apis/synthetics-rest-api/monitor-examples/manage-synthetics-monitors-via-rest-api#add-simple-ping-monitor) también se requieren al actualizar un monitor existente. @@ -265,20 +264,16 @@ https://synthetics.eu.newrelic.com/synthetics/api * `404 Not Found`: El monitor especificado no existe. - + Para parchear un monitor existente en New Relic, envíe una solicitud PATCH a `$API_ENDPOINT/v3/monitors/$MONITOR_ID`. Utilice un ID de monitor específico y reemplace el [atributo de API REST de monitoreo sintético](/docs/apis/synthetics-rest-api/monitor-examples/payload-attributes-synthetics-rest-api) con sus valores específicos. - ``` + ```sh curl -v \ - -X PATCH -H "Api-Key:$API_KEY" \ + -X PATCH -H "Api-Key:$API_KEY" \ -H 'Content-Type: application/json' $API_ENDPOINT/v3/monitors/$MONITOR_ID \ - -d '{ "name" : "updated monitor name" }' + -d '{ "name": "updated monitor name" }' ``` Las solicitudes de PATCH están destinadas a actualizar un atributo individual de su monitor de monitoreo sintético en lugar de actualizar la entidad completa, por lo que puede proporcionar solo el atributo que desea actualizar. @@ -289,32 +284,24 @@ https://synthetics.eu.newrelic.com/synthetics/api * `404 Not Found`: El monitor especificado no existe. - + Para eliminar un monitor existente en monitoreo sintético, envíe una solicitud DELETE al extremo`/v3/monitors/$MONITOR_ID`: - ``` + ```sh curl -v \ - -H "Api-Key:$API_KEY" \ + -H "Api-Key:$API_KEY" \ -X DELETE $API_ENDPOINT/v3/monitors/$MONITOR_ID ``` Una solicitud exitosa devolverá una respuesta `204 No Content` con un cuerpo vacío. Una solicitud fallida devolverá la respuesta `404 Not Found`: el monitor especificado no existe. - + Para recuperar la lista de ubicaciones válidas en su monitor de monitoreo sintético, use el siguiente comando: - ``` + ```sh curl -v \ - -X GET -H "Api-Key:$API_KEY" $API_ENDPOINT/v1/locations + -X GET -H "Api-Key:$API_KEY" $API_ENDPOINT/v1/locations ``` @@ -324,21 +311,18 @@ https://synthetics.eu.newrelic.com/synthetics/api Además de la API general, existen varios métodos API para el navegador con secuencias de comandos (`SCRIPT_BROWSER`) y el navegador de prueba API (`SCRIPT_API`). Estos ejemplos muestran el comando curl. - - Para ver el script asociado con un `SCRIPT_BROWSER` o `SCRIPT_API` específico en el monitor de monitoreo sintético de su cuenta, envíe una solicitud GET al extremo`/v3/monitors/$MONITOR_ID/script`. Por ejemplo: + + Para ver el script asociado a un `SCRIPT_BROWSER` o `SCRIPT_API` específico en los monitores Sintético de su cuenta, envíe una solicitud GET a `$API_ENDPOINT/v3/monitors/$MONITOR_ID/script`. Por ejemplo: - ``` + ```sh curl -v - -H "Api-Key:$API_KEY" + -H "Api-Key:$API_KEY" $API_ENDPOINT/v3/monitors/$MONITOR_ID/script ``` Una solicitud exitosa devolverá una respuesta `200 OK` . Los datos devueltos serán un objeto JSON en el siguiente formato: - ``` + ```json { "scriptText": BASE64 encoded string } @@ -350,10 +334,7 @@ Además de la API general, existen varios métodos API para el navegador con sec * `404 Not Found:` El monitor especificado no existe o el script asociado con el monitor no existe. - + Para agregar un nuevo monitor con script a sus monitores de monitoreo sintético con la API REST: 1. Siga [los procedimientos API estándar para agregar un nuevo monitor](/docs/apis/synthetics-rest-api/monitor-examples/manage-synthetics-monitors-rest-api#create-monitor) e identifique el `type` como `SCRIPT_BROWSER` o `SCRIPT_API`. @@ -365,18 +346,13 @@ Además de la API general, existen varios métodos API para el navegador con sec Si está utilizando la ubicación privada con [la ejecución de script verificada](/docs/synthetics/new-relic-synthetics/private-locations/verified-script-execution-private-locations) habilitada, consulte [Ubicaciones de script con ejecución de script verificada](#scriptlocations). - - Para actualizar el script asociado con un monitor `SCRIPT_BROWSER` o `SCRIPT_API` específico, envíe una solicitud PUT al extremo`/v3/monitors/$MONITOR_ID/script` con una carga útil JSON que contenga `scriptText` (obligatorio). + + Para actualizar el script asociado con un monitor `SCRIPT_BROWSER` o `SCRIPT_API` específico, envíe una solicitud PUT a `$API_ENDPOINT/v3/monitors/$MONITOR_ID/script` con una carga JSON que contenga `scriptText` (obligatorio). - ``` + ```sh scriptPayload='{"scriptText":BASE64 encoded string}' - - curl -v -X PUT \ - -H "Api-Key:$API_KEY" \ + -H "Api-Key:$API_KEY" \ -H 'Content-Type: application/json' \ $API_ENDPOINT/v3/monitors/$MONITOR_UUID/script \ -d $scriptPayload @@ -391,13 +367,10 @@ Además de la API general, existen varios métodos API para el navegador con sec * `404 Not Found:` El monitor especificado no existe. - + Al crear o actualizar un monitor para ubicación privada que tiene activada [la ejecución de script verificada](/docs/synthetics/new-relic-synthetics/private-locations/verified-script-execution-private-locations) , debe usar `scriptLocations` para establecer la contraseña: - ``` + ```json { "scriptText": BASE64 encoded String, "scriptLocations": [ @@ -413,19 +386,26 @@ Además de la API general, existen varios métodos API para el navegador con sec Aquí hay un ejemplo del script: - ``` + ```js var assert = require('assert'); assert.equal('1', '1'); ``` Este ejemplo utiliza `password` como contraseña para `scriptLocation`: - ``` + ```shell curl -v - -X PUT -H "Api-Key:$API_KEY" - -H 'content-type: application/json' - $API_ENDPOINT}/v3/monitors/$MONITOR_ID/script - -d '{ "scriptText": "dmFyIGFzc2VydCA9IHJlcXVpcmUoJ2Fzc2VydCcpOw0KYXNzZXJ0LmVxdWFsKCcxJywgJzEnKTs=","scriptLocations": [ { "name": "my_vse_enabled_location", "hmac": "MjhiNGE4MjVlMDE1N2M4NDQ4MjNjNDFkZDEyYTRjMmUzZDE3NGJlNjU0MWFmOTJlMzNiODExOGU2ZjhkZTY4ZQ=="} ]}' + -X PUT -H "Api-Key:$API_KEY" + -H 'content-type: application/json' + $API_ENDPOINT/v3/monitors/$MONITOR_ID/script + -d \ + '{ + "scriptText": "dmFyIGFzc2VydCA9IHJlcXVpcmUoJ2Fzc2VydCcpOw0KYXNzZXJ0LmVxdWFsKCcxJywgJzEnKTs=", + "scriptLocations": [{ + "name": "my_vse_enabled_location", + "hmac": "MjhiNGE4MjVlMDE1N2M4NDQ4MjNjNDFkZDEyYTRjMmUzZDE3NGJlNjU0MWFmOTJlMzNiODExOGU2ZjhkZTY4ZQ==" + }] + }' ``` @@ -445,47 +425,50 @@ Además de la API general, existen varios métodos API para el navegador con sec A continuación se muestra un ejemplo del uso de la API REST de New Relic y el script bash para crear un script de monitor de navegador. - + El siguiente ejemplo muestra el comando curl para crear un script de monitor de navegador. * En la parte superior del script, reemplace las variables con sus valores específicos. * Para la variable `scriptfile` , identifique el nombre de archivo del script que se creará. A continuación se muestra un script de muestra que se puede guardar como `sample_synth_script.js` para utilizarlo en el ejemplo: - ``` + ```js var assert = require("assert"); - $browser.get("http://example.com").then(function(){ - // Check the H1 title matches "Example Domain" - return $browser.findElement($driver.By.css("h1")).then(function(element){ - return element.getText().then(function(text){ - assert.equal("Example Domain", text, "Page H1 title did not match"); + $browser + .get("http://example.com") + .then(function() { + // Check the H1 title matches "Example Domain" + return $browser.findElement($driver.By.css("h1")).then(function (element) { + return element.getText().then(function (text) { + assert.equal("Example Domain", text, "Page H1 title did not match"); + }); }); + }) + .then(function() { + // Check that the external link matches "http://www.iana.org/domains/example" + return $browser + .findElement($driver.By.css("div > p > a")) + .then(function (element) { + return element.getAttribute("href").then(function (link) { + assert.equal( + "http://www.iana.org/domains/example", + link, + "More information link did not match" + ); + }); + }); }); - }).then(function(){ - // Check that the external link matches "http://www.iana.org/domains/example" - return $browser.findElement($driver.By.css("div > p > a")).then(function(element){ - return element.getAttribute("href").then(function(link){ - assert.equal("http://www.iana.org/domains/example", link, "More information link did not match"); - }); - }); - }); ``` - + Este ejemplo muestra el script bash que creará el monitor `SCRIPTED_BROWSER` . En algunos casos, es posible que desee utilizar `-w 0`, que deshabilitará el ajuste de línea: `base64 -w 0 $scriptfile` - ``` + ```sh #!/bin/bash # API key from your account settings @@ -518,7 +501,7 @@ A continuación se muestra un ejemplo del uso de la API REST de New Relic y el s HTTP*) read PROTO STATUS MSG <<< "$key{$value:+:$value}" ;; esac - done < <(curl -sS -i -X POST -H "Api-Key:$API_KEY" -H 'Content-Type:application/json' https://synthetics.newrelic.com/synthetics/api/v3/monitors -d "$payload") + done < <(curl -sS -i -X POST -H "Api-Key:$API_KEY" -H 'Content-Type:application/json' https://synthetics.newrelic.com/synthetics/api/v3/monitors -d "$payload") # Validate monitor creation & add script unless it failed if [ $STATUS = 201 ]; then @@ -527,7 +510,7 @@ A continuación se muestra un ejemplo del uso de la API REST de New Relic y el s # base64 encode script encoded=`echo "$script" | base64` scriptPayload="{\"scriptText\":\"$encoded\"}" - curl -s -X PUT -H "Api-Key:$API_KEY" -H 'Content-Type:application/json' "$LOCATION/script" -d $scriptPayload + curl -s -X PUT -H "Api-Key:$API_KEY" -H 'Content-Type:application/json' "$LOCATION/script" -d $scriptPayload echo "Script uploaded" else echo "Monitor creation failed" @@ -538,4 +521,4 @@ A continuación se muestra un ejemplo del uso de la API REST de New Relic y el s fi ``` - + \ No newline at end of file diff --git a/src/i18n/content/es/docs/apm/agents/java-agent/troubleshooting/ssl-or-connection-errors-java.mdx b/src/i18n/content/es/docs/apm/agents/java-agent/troubleshooting/ssl-or-connection-errors-java.mdx index 6987e50b675..a6cc993542b 100644 --- a/src/i18n/content/es/docs/apm/agents/java-agent/troubleshooting/ssl-or-connection-errors-java.mdx +++ b/src/i18n/content/es/docs/apm/agents/java-agent/troubleshooting/ssl-or-connection-errors-java.mdx @@ -10,7 +10,7 @@ freshnessValidatedDate: never translationType: machine --- -## Problema A: Errores de conexión/SSL en el registro [#ssl-error-logs] +## Problema A: Errores de conexión/SSL en el log [#ssl-error-logs] [Los datoslog ](/docs/agents/java-agent/troubleshooting/generate-debug-logs-troubleshooting-java)de su agente de Java New Relic muestran errores de conexión o SSL. @@ -20,7 +20,7 @@ translationType: machine ### Solución A [#ssl-error-logs-solution] -Los errores al conectarse a través de SSL suelen aparecer al principio del archivo de registro del agente de Java. Por ejemplo: +Los errores al conectarse a través de SSL suelen aparecer al principio del archivo de log del agente de Java. Por ejemplo: ``` PKIX path building failed: java.security.cert.CertPathBuilderException: PKIXCertPathBuilderImpl could not build a valid CertPath @@ -33,13 +33,13 @@ Cannot find the specified class com.ibm.websphere.ssl.protocol.SSLSocketFactory Si ve alguno de estos errores, es probable que su instancia JDK esté utilizando un almacén de confianza personalizado. -**Recommendation:** Agregue la Autoridad de certificación raíz (CA) global de DigiCert, de la cual se deriva el certificado de New Relic, a su almacén de confianza. +Recomendación: agregue la autoridad de certificación raíz global de DigiCert (CA), de la que se deriva el certificado de New Relic, a su almacén de confianza. -Puede descargar [DigiCert Global Root CA](https://www.digicert.com/kb/digicert-root-certificates.htm) desde DigiCert en la sección "Otros certificados raíz" (elija la opción "Descargar PEM"). +Puede descargar [DigiCert Global Root CA](https://www.digicert.com/kb/digicert-root-certificates.htm) desde DigiCert en la sección "Otros certificados raíz" (elija la opción "Descargar PEM"). Para importar el certificado a su almacén de confianza, utilice este comando o consulte [la documentación Java SE de Oracle para keytool](https://docs.oracle.com/javase/6/docs/technotes/tools/solaris/keytool.html): -``` +```sh keytool -importcert -alias ca_alias -file ca_file.pem -keystore truststore.ts -storepass ts_password ``` @@ -101,7 +101,7 @@ Los parámetros incluyen:
- El ID del rol personalizado creado en la sección - - [Rol personalizado]() - - . + El ID del rol personalizado creado en la sección Rol personalizado.
-## Problema B: excepción de presentación de registro [#log-exception] +## Problema B: excepción de presentación de log [#log-exception] [Los datoslog ](/docs/agents/java-agent/troubleshooting/generate-debug-logs-troubleshooting-java)de su agente de Java New Relic muestran lo siguiente `CertificateException`. @@ -113,4 +113,4 @@ Lo más probable es que esto esté relacionado con este [problema de JDK](https: ### Solución B [#log-exception-solution] -Examine y valide que el encabezado y pie de página de sus certificados no tengan espacios en blanco al final. Si es así, edite o utilice certificados diferentes. +Examine y valide que el encabezado y pie de página de sus certificados no tengan espacios en blanco al final. Si es así, edite o utilice certificados diferentes. \ No newline at end of file diff --git a/src/i18n/content/es/docs/apm/agents/nodejs-agent/installation-configuration/nodejs-agent-configuration.mdx b/src/i18n/content/es/docs/apm/agents/nodejs-agent/installation-configuration/nodejs-agent-configuration.mdx index dc87ce6ea2c..3c0cb09be15 100644 --- a/src/i18n/content/es/docs/apm/agents/nodejs-agent/installation-configuration/nodejs-agent-configuration.mdx +++ b/src/i18n/content/es/docs/apm/agents/nodejs-agent/installation-configuration/nodejs-agent-configuration.mdx @@ -824,10 +824,20 @@ Esta sección define las variables del agente de Node.js en el orden en que suel - Ruta completa al log del agente New Relic, incluido el nombre del archivo. El valor predeterminado es `filepath: require('path').join(process.cwd(), 'newrelic_agent.log')`. El agente cerrará el proceso si no puede crear este archivo. El agente crea un archivo de registro con los mismos permisos que el proceso del agente principal de Node.js. + Ruta completa al log del agente de New Relic, incluido el nombre del archivo. El valor predeterminado es `filepath: require('path').join(process.cwd(), 'newrelic_agent.log')`. Si el agente no puede crear el archivo de log, entonces: + + * Registra el error `New Relic failed to open log file` empleando `console.error`. + * Almacena en memoria intermedia todos los mensajes de log posteriores. + * Cuando el buffer de memoria alcanza su límite de 128 MiB, el agente descarta cualquier nuevo mensaje de log y emite la siguiente advertencia vía `process.emitWarning`: `[NRWARN001] NewRelicWarning: Dropping log message, buffer would overflow.` + + Al crear el archivo de log, el agente establece las licencias del archivo en 0o600 (lectura/escritura para el propietario). * Para escribir todos los registros en **stdout**, configúrelo en `stdout`. * Para escribir todos los registros en **stderr**, configúrelo en `stderr`. + + + En versiones del agente anteriores a 7.0.0, el agente apagaba el proceso si no podía crear este archivo. + diff --git a/src/i18n/content/es/docs/browser/new-relic-browser/browser-apis/addpageaction.mdx b/src/i18n/content/es/docs/browser/new-relic-browser/browser-apis/addpageaction.mdx index 544a17d8049..bf3b94d5b68 100644 --- a/src/i18n/content/es/docs/browser/new-relic-browser/browser-apis/addpageaction.mdx +++ b/src/i18n/content/es/docs/browser/new-relic-browser/browser-apis/addpageaction.mdx @@ -45,7 +45,7 @@ Informa un evento PageAction browser junto con un nombre y un atributo opcional. Esta llamada API envía un [evento`PageAction` ](/docs/insights/explore-data/custom-events/insert-browser-custom-events-attributes-insights-javascript-api)del navegador con su nombre definido por el usuario y un atributo opcional al [dashboard](/docs/query-your-data/explore-query-data/dashboards/introduction-new-relic-one-dashboards), junto con [varios atributos predeterminados](/attribute-dictionary/?event=PageAction). Esto es útil para rastrear cualquier evento que el agente del navegador aún no rastrea automáticamente, como hacer clic en un botón **Subscribe** o acceder a un tutorial. * `PageAction` Los eventos se envían cada 30 segundos. -* Si se observan 1.000 eventos, el agente recolectará el evento almacenado inmediatamente, omitiendo el intervalo del ciclo de recolección. +* Si se observan 1000 eventos o si el tamaño de la carga de recolección es mayor a 16 KB, el agente recolectará los eventos almacenados en búfer inmediatamente, omitiendo el intervalo del ciclo de recolección. En versiones anteriores del agente, los eventos se descartaban luego de observar 120. El límite de eventos se incrementó de 120 a 1000 en la versión [1.264.0](https://docs.newrelic.com/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.264.0/) y ya no se eliminan. diff --git a/src/i18n/content/es/docs/browser/new-relic-browser/browser-apis/recordCustomEvent.mdx b/src/i18n/content/es/docs/browser/new-relic-browser/browser-apis/recordCustomEvent.mdx index f8c36826a6e..9b67c7c87dc 100644 --- a/src/i18n/content/es/docs/browser/new-relic-browser/browser-apis/recordCustomEvent.mdx +++ b/src/i18n/content/es/docs/browser/new-relic-browser/browser-apis/recordCustomEvent.mdx @@ -45,7 +45,7 @@ Informa sobre un evento browser personalizado bajo un eventType especificado con Esta API de llamada envía un evento browser personalizado con su eventType definido por el usuario y un atributo opcional al [tablero](/docs/query-your-data/explore-query-data/dashboards/introduction-new-relic-one-dashboards), junto con cualquier atributo personalizado que pueda configurar para su aplicación. Esto es útil para rastrear cualquier evento que no sea rastreado automáticamente por el agente del browser mejorado por reglas y atribución que usted controla. * `custom` Los eventos se envían cada 30 segundos. -* Si se observan 1.000 eventos, el agente recolectará el evento almacenado inmediatamente, omitiendo el intervalo del ciclo de recolección. +* Si se observan 1000 eventos o si el tamaño de la carga de recolección es mayor a 16 KB, el agente recolectará los eventos almacenados en búfer inmediatamente, omitiendo el intervalo del ciclo de recolección. ## Parámetros [#parameters] diff --git a/src/i18n/content/es/docs/browser/new-relic-browser/page-load-timing-resources/instrumentation-browser-monitoring.mdx b/src/i18n/content/es/docs/browser/new-relic-browser/page-load-timing-resources/instrumentation-browser-monitoring.mdx index c9cfab41ee6..fe4019969b6 100644 --- a/src/i18n/content/es/docs/browser/new-relic-browser/page-load-timing-resources/instrumentation-browser-monitoring.mdx +++ b/src/i18n/content/es/docs/browser/new-relic-browser/page-load-timing-resources/instrumentation-browser-monitoring.mdx @@ -160,7 +160,7 @@ Para ambas páginas web https **and** http, transmitimos datos a trav - Los datos se envían 10 segundos después de la carga de la página inicial y luego cada 30 segundos. + Los datos se envían 10 segundos luego de la carga inicial de la página y luego cada 30 segundos. Si el tamaño de la carga útil de la cosecha es mayor a 16 KB, los datos se envían anticipadamente. diff --git a/src/i18n/content/es/docs/browser/new-relic-browser/performance-quality/browser-monitoring-performance-impact.mdx b/src/i18n/content/es/docs/browser/new-relic-browser/performance-quality/browser-monitoring-performance-impact.mdx index f4fdfa5f527..3783a500896 100644 --- a/src/i18n/content/es/docs/browser/new-relic-browser/performance-quality/browser-monitoring-performance-impact.mdx +++ b/src/i18n/content/es/docs/browser/new-relic-browser/performance-quality/browser-monitoring-performance-impact.mdx @@ -162,7 +162,7 @@ El agente consta de múltiples scripts para reducir el tamaño inicial del " - `PageViewTiming` Los eventos son recopilados por todos los agentes e incluyen datos de tiempo como mediciones principales de Métricas web. La primera recolección ocurre 10 segundos después del evento del ciclo de vida de la página `load` . Se realizan recopilaciones adicionales cada 30 segundos según sea necesario cuando hay datos para enviar. Consulte los [documentos de PageViewTiming](/docs/browser/new-relic-browser/page-load-timing-resources/pageviewtiming-async-or-dynamic-page-details/#interactivity-metrics) para obtener una lista de eventos informados. + `PageViewTiming` Los eventos son recopilados por todos los agentes e incluyen datos de tiempo como mediciones de elementos sitio web vitales básicos. La primera cosecha ocurre 10 segundos luego del evento del ciclo de vida de la página `load` . Se producen cosechas adicionales cada 30 segundos según sea necesario cuando hay datos para enviar o si el tamaño de la carga útil de la cosecha es mayor a 16 KB. Consulte la [documentación de PageViewTiming](/docs/browser/new-relic-browser/page-load-timing-resources/pageviewtiming-async-or-dynamic-page-details/#interactivity-metrics) para obtener una lista de los eventos informados. @@ -300,7 +300,7 @@ El agente consta de múltiples scripts para reducir el tamaño inicial del " - `PageAction` Los eventos se recopilan después del evento del ciclo de vida de la página `load` . Las recopilaciones posteriores ocurren cada 30 segundos. + `PageAction` Los eventos se recolectan luego del ciclo de vida de la página `load` . Las cosechas posteriores ocurren cada 30 segundos o si el tamaño de la carga de cosecha es mayor a 16 KB. diff --git a/src/i18n/content/es/docs/change-tracking/change-tracking-events.mdx b/src/i18n/content/es/docs/change-tracking/change-tracking-events.mdx index 71623c6bcee..58da3c023ff 100644 --- a/src/i18n/content/es/docs/change-tracking/change-tracking-events.mdx +++ b/src/i18n/content/es/docs/change-tracking/change-tracking-events.mdx @@ -29,7 +29,7 @@ translationType: machine La capacidad de seguimiento de cambios le permite capturar, visualizar y analizar cambios en su aplicación e infraestructura. Esta función está diseñada para ayudarlo a comprender cómo los cambios afectan tanto a su sistema como a sus clientes. -* **Capture all changes impacting your system:** Send change events for any type of change, including deployments, feature flags changes, configuration changes, and business events. You can also create custom change events tailored to your specific requirements. Use the [`changeTrackingCreateEvent`](#change-tracking-event-mutation) NerdGraph mutation to easily send various types of change events. +* **Capture todos los cambios que impactan su sistema:** envíe eventos de cambio para cualquier tipo de cambio, incluidos cambios de implementación, cambios de indicadores de características, cambios de configuración y eventos comerciales. También puede crear eventos de cambio personalizados adaptados a sus requisitos específicos. Emplee la mutación NerdGraph [`changeTrackingCreateEvent`](#change-tracking-event-mutation) para enviar fácilmente varios tipos de eventos de cambio. * **Obtenga una vista integral para gestionar cambios en todo el sistema:** vea y filtre sin problemas eventos de cambio en todas sus entidades y cuentas desde una interfaz unificada. Identifique los cambios sin esfuerzo filtrando por equipo, tipo, atributo personalizado y cualquier otro criterio. diff --git a/src/i18n/content/es/docs/new-relic-control/agent-control/configuration.mdx b/src/i18n/content/es/docs/new-relic-control/agent-control/configuration.mdx index 21076f89067..abe6b24873a 100644 --- a/src/i18n/content/es/docs/new-relic-control/agent-control/configuration.mdx +++ b/src/i18n/content/es/docs/new-relic-control/agent-control/configuration.mdx @@ -306,21 +306,22 @@ Para configuraciones de proxy que emplean autenticación HTTPS con certificados secretName: ca-certs # Configure Flux components to use proxy - flux2: - sourceController: - extraEnv: - # Configure Flux source-controller to proxy all requests - - name: HTTPS_PROXY - value: https://proxy-service:8080 - # Except for in-cluster requests - - name: "NO_PROXY" - value: ".cluster.local.,.cluster.local,cluster.local,.svc,127.0.0.0/8,10.0.0.0/8" - volumeMounts: - # Mount CA certificate bundle to source-controller trust root store. The bundle should contain the - # proxy CA cert. - - mountPath: /etc/ssl/certs/ - name: ca-certs - volumes: + agent-control-cd: + flux2: + sourceController: + extraEnv: + # Configure Flux source-controller to proxy all requests + - name: HTTPS_PROXY + value: https://proxy-service:8080 + # Except for in-cluster requests + - name: "NO_PROXY" + value: ".cluster.local.,.cluster.local,cluster.local,.svc,127.0.0.0/8,10.0.0.0/8" + volumeMounts: + # Mount CA certificate bundle to source-controller trust root store. The bundle should contain the + # proxy CA cert. + - mountPath: /etc/ssl/certs/ + name: ca-certs + volumes: - name: ca-certs secret: secretName: ca-certs @@ -338,20 +339,160 @@ Para configuraciones de proxy que emplean autenticación HTTPS con certificados Al emplear un proxy, también debe configurar los ajustes del proxy para cada agente gestionado individualmente. Consulte la documentación específica de cada agente para conocer las opciones de configuración del proxy. -## Private repository configuration +## Gestión de secretos -Agent Control supports configuring private Helm repositories to deploy both Agent Control itself and the managed agents. This enables environments where the New Relic Helm charts are not directly accessible. +Agent Control provides a robust mechanism for managing sensitive data, such as passwords and API keys, by retrieving them from dedicated secret providers. This ensures that sensitive information is not hard-coded directly into configuration files. The system currently supports the following secret providers: + +* HashiCorp Vault: referred to as `nr-vault` in configurations. +* Kubernetes Secrets: referred to as `nr-kubesec` in configurations. + +### Defining Secrets in Configuration + +To utilize secrets, define them within your Agent-Control configuration YAML file by following these steps: + +1. **Define the `secrets_providers` section:** Configure your secret providers centrally in this section. Ensure each entry corresponds to a supported provider. +2. **Configure secret sources:** For each provider, specify one or more sources. A source includes the necessary configuration details (e.g., URL, token) for Agent control to connect to and retrieve a group of secrets. +3. **Use placeholders in agent configurations:** Instead of the actual sensitive data, Use a placeholder string within your agent's configuration. Agent control automatically replaces these placeholders with the retrieved secrets during the rendering process. + + + If Agent control fails to retrieve a secret, the configuration rendering will fail, and the agent will not be executed. This is a critical security feature to prevent agents from running with incomplete or incorrect configurations. + + +The following agent-control configuration example demonstrates how to configure for retrieving secrets from two Vault sources within the `secrets_providers` section: + +```yaml +secrets_providers: + vault: + sources: + local-instance: + url: http://localhost:8200/v1/ + token: root + engine: kv2 + remote: + url: http://my-remote-server:8200/v1/ + token: root + engine: kv1 + +fleet_control: + ... + +agents: + ... +``` + +#### Using Secrets in an Agent Configuration + +After the sources are defined, in an agent configuration, you can reference the vault using a specific placeholder syntax with the correct path. Agent control retrieves the secret and uses it to render the final configuration file that the agent is going to use. + +Example of agent configuration using vault placeholders: + +```yaml +config_agent: |+ + enable_process_metrics: true + custom_attributes: + username: "${nr-vault:local-instance:secret:my_secret:username}" + organization: "${nr-vault:remote:my_mount:my_path:organization}" +``` + +En este ejemplo: + +The placeholder `${nr-vault:local-instance:secret:my_secret:username}` instructs Agent control to retrieve the value associated with the key username from the secret at the path `secret/my_secret` using the local-instance vault source. The placeholder `${nr-vault:remote:my_mount:my_path:organization}` similarly retrieves the value for the organization key from the remote source. + +After successful retrieval, Agent control renders these secrets from the specified source and path, storing the result in a K8s secret or private config file for use by the corresponding agent. + +### Secretos de la bóveda + +Set up the vault sources with the following settings: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Clave YAML + + Descripción +
+ `url` + + URL para solicitar datos +
+ `token` + + Used to authenticate to the endpoint. +
+ `engine` + + Specify **`kv1`** or **`kv2`**. +
+ +In the configuration file, each secret stored in Vault can be accessed by setting a placeholder with: + +* **source\_name**: The name of the Vault source defined in `secrets_providers`. +* **mount**: The name of the secrets engine mount. +* **path**: The specific path to the secret. +* **specific key**: The specific key within the secret to be retrieved. + +Example of full placeholder format: + +``` +"${nr-vault:source_name:my_mount:my_path:my_value}" +``` + +### Kubernetes secrets + +If the agent-control pod has permissions, such as through a Service Account and Role-Based Access Control (RBAC), to access the required secrets and namespaces, Agent control can directly access secrets from the Kubernetes API without needing a separate sources configuration. + +In the agent configuration file, retrieve each secret value using a placeholder specifying: + +* **namespace**: The Kubernetes namespace where the secret is located. +* **name**: The name of the Kubernetes secret object. +* **specific key**: The specific key within the secret from which to retrieve the value. + +For example, use the placeholder format: + +``` +"${nr-kubesec:my_namespace:my_secret:my_value}" +``` + +## Configuración del repositorio privado + +Agente Control admite la configuración de un repositorio Helm privado para implementar tanto el propio Agente Control como el agente gestionado. Esto permite entornos en los que no se puede acceder directamente a los gráficos de New Relic Helm. - When using private Helm repositories, the charts need to be compatible and the referenced images within the charts must be reachable. If not, the agents will not work as expected. + Al emplear el repositorio privado Helm, los gráficos deben ser compatibles y las imágenes referenciadas dentro de los gráficos deben ser accesibles. De lo contrario, el agente no funcionará como se espera. -### 1. Enable private repositories for agents +### 1. Habilitar repositorio privado para agente -For security reasons, only explicitly enabled repositories will be allowed in remote configurations. To enable specific repositories, you need to update the Agent Control configuration: +Por razones de seguridad, solo se permitirá el repositorio habilitado explícitamente en la configuración remota. Para habilitar un repositorio específico, necesita actualizar la configuración del agente Control: - + ```yaml # values-newrelic.yaml @@ -371,7 +512,7 @@ For security reasons, only explicitly enabled repositories will be allowed in re -The allowed repository configurations can then be used in your remote configurations within New Relic Control. Example: +La configuración del repositorio permitida se puede usar luego en su configuración remota dentro de New Relic Control. Ejemplo: ```yaml chart_version: "1.2.3" @@ -380,19 +521,19 @@ chart_repository: name: "my-chart-name" # Optional: use only if the chart name doesn't match New Relic's chart name ``` -Additionally, you need to configure Agent Control's Helm installation to use your private repository if the `agent-control` chart itself is in a private repository. This is separate from the configuration for managed agents. Refer to the `agent-control` Helm chart [values.yaml](https://github.com/newrelic/helm-charts/blob/master/charts/agent-control/values.yaml) to set up the `installationJob` section. Specifically: +Además, debe configurar la instalación Helm del agente Control para emplear su repositorio privado si el gráfico `agent-control` en sí está en un repositorio privado. Esto es independiente de la configuración del agente gestionado. Consulta el archivo `agent-control` Helm chart [values.yaml](https://github.com/newrelic/helm-charts/blob/master/charts/agent-control/values.yaml) para configurar la sección `installationJob`. Específicamente: -* `chartRepositoryUrl` containing your repository URL -* `name` if using a different chart name -* `repositorySecretReferenceName` and `repositoryCertificateSecretReferenceName` for authentication (see the authentication section below for details) +* `chartRepositoryUrl` contiene la URL de su repositorio +* `name` si se emplea un nombre de gráfico diferente +* `repositorySecretReferenceName` y `repositoryCertificateSecretReferenceName` para autenticación (consulte la sección de autenticación a continuación para obtener más detalles) -### 2. Set up authentication for private repositories +### 2. Configurar la autenticación para el repositorio privado -You need to set up additional resources to enable authentication for accessing your private repository: +Necesita configurar recursos adicionales para habilitar la autenticación para acceder a su repositorio privado: - To authenticate using basic authentication (username and password), you need to create a secret in the Agent Control namespace containing the expected values in `data.username` and `data.password`. + Para autenticar mediante la autenticación básica (nombre de usuario y contraseña), debe crear un secreto en el namespace de control del agente que contenga los valores esperados en `data.username` y `data.password`. Ejemplo: @@ -406,9 +547,9 @@ You need to set up additional resources to enable authentication for accessing y password: "myPassword" ``` - For more details, see the [Flux documentation](https://fluxcd.io/flux/components/source/helmrepositories/#secret-reference). + Para obtener más detalles, consulte la [documentación de Flux](https://fluxcd.io/flux/components/source/helmrepositories/#secret-reference). - When using basic authentication, the remote configuration should be configured as follows: + Al emplear la autenticación básica, la configuración remota debe configurar de la siguiente manera: ```yaml chart_repository: @@ -418,13 +559,13 @@ You need to set up additional resources to enable authentication for accessing y ``` - - To authenticate using TLS, you need to create a secret containing: + + Para autenticar mediante TLS, debe crear un secreto que contenga: - * `tls.crt` and `tls.key`: client certificate and private key used for TLS client authentication - * `ca.crt`: CA certificate used to verify the server (required if the server uses a self-signed certificate) + * `tls.crt` y `tls.key`: certificado de cliente y clave privada empleados para la autenticación del cliente TLS + * `ca.crt`:Certificado CA empleado para verificar el servidor (obligatorio si el servidor emplea un certificado autofirmado) - The Secret should be of type `Opaque` or `kubernetes.io/tls`. All files in the Secret are expected to be PEM-encoded. + El secreto debe ser de tipo `Opaque` o `kubernetes.io/tls`. Se espera que todos los archivos del secreto estén codificados en PEM. Ejemplo: @@ -442,9 +583,9 @@ You need to set up additional resources to enable authentication for accessing y ca.crt: ``` - For more details, see the [Flux documentation](https://fluxcd.io/flux/components/source/helmrepositories/#secret-reference). + Para obtener más detalles, consulte la [documentación de Flux](https://fluxcd.io/flux/components/source/helmrepositories/#secret-reference). - When using TLS certificate authentication, the remote configuration should be configured as follows: + Al emplear la autenticación de certificado TLS, la configuración remota debe configurar de la siguiente manera: ```yaml chart_repository: diff --git a/src/i18n/content/es/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx b/src/i18n/content/es/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx index 0e43b55e0cf..63e9c6f53bb 100644 --- a/src/i18n/content/es/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx +++ b/src/i18n/content/es/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx @@ -280,7 +280,7 @@ mutation { pipelineCloudRuleEntity: { description: "Since we only care about MyEvent in staging and production, let's drop all MyEvent data in the test environment", name: "Drop MyEvent in test environment", - nrql: "DELETE FROM MyEvent where environment = 'test'", + nrql: "DELETE FROM MyEvent WHERE environment = 'test'", scope: { id: "your_nr_account_id", type: ACCOUNT @@ -304,7 +304,7 @@ mutation { pipelineCloudRuleEntity: { description: "We don't care about jvmId and targetAttr in the test environment, let's drop those attributes", name: "Drop jvmId and targetAttr from MyEvent in test environment", - nrql: "DELETE jvmId, targetAttr FROM MyEvent where environment = 'test'", + nrql: "DELETE jvmId, targetAttr FROM MyEvent WHERE environment = 'test'", scope: { id: "your_nr_account_id", type: ACCOUNT @@ -529,7 +529,7 @@ mutation { pipelineCloudRuleEntity: { description: "We don't care about targetAttr in the test environment in dimensional metric rolloups, let's drop those attributes", name: "Drop targetAttr from Metric aggregate rollups in test environment", - nrql: "DELETE targetAttr FROM MetricAggregate where environment = 'test'", + nrql: "DELETE targetAttr FROM MetricAggregate WHERE environment = 'test'", scope: { id: "your_nr_account_id", type: ACCOUNT diff --git a/src/i18n/content/es/docs/new-relic-control/pipeline-control/data-dropping-gateway.mdx b/src/i18n/content/es/docs/new-relic-control/pipeline-control/data-dropping-gateway.mdx index 80288809681..fb32eda7449 100644 --- a/src/i18n/content/es/docs/new-relic-control/pipeline-control/data-dropping-gateway.mdx +++ b/src/i18n/content/es/docs/new-relic-control/pipeline-control/data-dropping-gateway.mdx @@ -524,7 +524,7 @@ La siguiente tabla enumera: - `DELETE FROM SqlTrace WHERE uri = 'Custom\/Simple\/sqlTransaction'` + `DELETE FROM SqlTrace WHERE uri = 'Custom/Simple/sqlTransaction'` @@ -586,7 +586,7 @@ La siguiente tabla enumera: - `DELETE FROM TransactionTrace WHERE uri = 'Custom\/Simple\/sqlTransaction'` + `DELETE FROM TransactionTrace WHERE uri = 'Custom/Simple/sqlTransaction'` @@ -730,7 +730,7 @@ La siguiente tabla enumera: - `DELETE instanceType,inodesTotal NetworkSample WHERE entityKey = 'vagrant'` + `DELETE instanceType, inodesTotal NetworkSample WHERE entityKey = 'vagrant'` @@ -774,7 +774,7 @@ La siguiente tabla enumera: - `DELETE FROM ContainerSample WHERE agentName='ContainerSampleAgent'` + `DELETE FROM ContainerSample WHERE agentName = 'ContainerSampleAgent'` diff --git a/src/i18n/content/es/docs/new-relic-control/pipeline-control/nrql-functions.mdx b/src/i18n/content/es/docs/new-relic-control/pipeline-control/nrql-functions.mdx index 3c7d1982e0c..2b787ba0323 100644 --- a/src/i18n/content/es/docs/new-relic-control/pipeline-control/nrql-functions.mdx +++ b/src/i18n/content/es/docs/new-relic-control/pipeline-control/nrql-functions.mdx @@ -185,8 +185,8 @@ Este documento describe las funciones NRQL admitidas por el portal de control de Estos ejemplos demuestran cómo se pueden combinar múltiples funciones y usarlas en escenarios más complejos para lograr un filtrado y eliminación de datos precisos. -* `DELETE FROM ContainerSample WHERE state = 'exited' and status LIKE '%Exited%' and status NOT LIKE '%second%' and status not like '%About a minute ago%' and not (status like '%minute%' and numeric(aparse(status,'%Exited (%) * minutes ago%')) < 10)` +* `DELETE FROM ContainerSample WHERE state = 'exited' AND status LIKE '%Exited%' AND status NOT LIKE '%second%' AND status NOT LIKE '%About a minute ago%' AND NOT (status LIKE '%minute%' AND numeric(aparse(status,'%Exited (%) * minutes ago%')) < 10)` * `DELETE FROM Log, LogExtendedRecord WHERE dimensions() LIKE '%collectd%' AND newrelic.logs.customEventType IS NULL` -* `DELETE FROM Log WHERE message LIKE '%lib/ladon/middleware/caching.rb:49 run> terminated with exception%' and floor(timestamp/101) = (timestamp/101)` +* `DELETE FROM Log WHERE message LIKE '%lib/ladon/middleware/caching.rb:49 run> terminated with exception%' AND floor(timestamp/101) = (timestamp/101)` Estas nuevas funciones amplían significativamente las capacidades de su consulta NRQL cuando trabaja con el gateway de Control de pipelines, permitiendo un análisis y gestión de datos más precisos. \ No newline at end of file diff --git a/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx b/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx index 5ff5a92db0d..04d79857004 100644 --- a/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx +++ b/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx @@ -10,7 +10,7 @@ translationType: machine * Se agregó una nueva característica sobre [Cómo depurar problemas del agente New Relic Browser ](/docs/browser/new-relic-browser/troubleshooting/how-to-debug-browser-agent/), que incluye logging detallado, monitoreo de solicitudes de red e inspección de eventos para una resolución mejorada de problemas en las versiones del agente 1.285.0 y superiores. * Se agregó compatibilidad con [Azure Functions](/docs/serverless-function-monitoring/azure-function-monitoring/introduction-azure-monitoring/) para la supervisión de funciones `python` y `.node.js`. * Se agregó [un optimizador de costos](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/compute-optimizer/) para obtener información procesable valiosa para mejorar la eficiencia del cálculo, con una función para identificar ineficiencias, brindar recomendaciones de optimización y estimar ahorros de CCU en la plataforma New Relic. -* Added [Cloud Cost Intelligence](/docs/cci/getting-started/overview), offering tools for visibility and management of cloud costs, including features such as comprehensive cost breakdowns, Kubernetes cost allocation, real-time cost estimation, and cross-account data collection, currently supporting only AWS cloud costs. +* Se agregó [Inteligencia para costos en la nube](/docs/cci/getting-started/overview), que ofrece herramientas para la visibilidad y la gestión de los costos cloud, incluidas características como desgloses completos de costos, asignación de costos Kubernetes, estimación de costos en tiempo real y recopilación de datos entre cuentas, y que actualmente solo admite los costos AWS cloud. * Se agregó [la observabilidad OpenTelemetry para Kubernetes con la integración independiente del proveedor de la característica New Relic](/docs/kubernetes-pixie/k8s-otel/intro/) para un monitoreo continuo del clúster a través del diagrama Helm, mejorando las señales de telemetría para métricas, eventos y logs transmitidos a las herramientas y el tablero de New Relic. * Se agregó [limitación y resolución de problemas para la integración Windows](/docs/kubernetes-pixie/kubernetes-integration/troubleshooting/troubleshooting-windows/) * Se agregó la integración de AWS a través de [CloudFormation y CloudWatch Metric Streams](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation/), lo que admite el sondeo de API para servicios no compatibles. diff --git a/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx b/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx new file mode 100644 index 00000000000..01456861c55 --- /dev/null +++ b/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx @@ -0,0 +1,60 @@ +--- +subject: Docs +releaseDate: '2025-08-08' +version: 'August 01 - August 07, 2025' +translationType: machine +--- + +### Nuevos documentos + +* Se agregó [el tutorial de NerdGraph: Crear un rol personalizado para Teams](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/compute-budgets/overview) para guiarlo en el uso de la API de NerdGraph de New Relic para crear y gestionar roles personalizados para Teams. + +### Cambios menores + +* Se modificó el [umbral de alerta de evento por condición](/docs/alerts/admin/rules-limits-alerts) a 1k por minuto. +* Se actualizaron las últimas [versiones y requisitos compatibles del agente .Net](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements) verificados. +* Se actualizó la información de versión y soporte de versión acerca del agente de servicio para [VMware Tanzu](/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-service-broker-integration). +* Se actualizó la información de soporte de la versión sobre el paquete de compilación de integración NGINX de New Relic para [VMware Tanzu](/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-nginx-buildpack-integration). +* Se actualizó la información de versión y soporte de versiones de New Relic Nozzle para [VMware Tanzu](/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-firehose-nozzle-integration/#product-snapshot). + +### Notas de la versión + +* Consulta nuestras publicaciones de Novedades: + + * [Errors Inbox ahora está integrada dentro de carga de trabajo](/whats-new/2025/08/whats-new-08-06-workloads-errors-inbox). + +* Mantener actualizado con nuestros últimos lanzamientos: + + * [Administrador de trabajos v452](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-452): + * Se agregaron mejoras internas para el manejo de excepciones al procesar mensajes de la cola. + + * [IntegraciónKubernetes v3.43.3](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-43-3): + * Se agregó un gráfico Helm para implementar la solución de monitoreo Kubernetes New Relic. + + * [Control de tuberías Gateway v1.1.0](/docs/release-notes/pipeline-control-gateway-release-notes/pipeline-control-gateway-25-08-05): + + * Se implementó una nueva funcionalidad para descartar selectivamente datos y atributos de `SqlTrace` y `TransactionTrace` incluso usando reglas de descartado. + + * Se abordaron vulnerabilidades en el paquete `golang.org/x/net`, incluido un problema de script entre sitios y una omisión de proxy HTTP relacionada con los ID de zona IPv6. + + * Se actualizó a Go `1.24` y las siguientes dependencias se actualizan para mejorar la seguridad e incorporar correcciones recientes: + + * `golang.org/x/net to v0.38.0` + * `golang.org/x/sys to v0.31.0` + * `golang.org/x/text to v0.23.0` + + * [Aplicación móvil para iOS v6.9.11](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6101): + * Se redujo el flujo de inicio de sesión en dos pasos al almacenar el dominio de autenticación de un usuario y redirigirlo directamente a su página de inicio de sesión. + + * [Agente deFlutter v1.1.13](/docs/release-notes/mobile-release-notes/flutter-release-notes/flutter-agent-1113): + + * Agente nativo Android mejorado actualizado a la versión 7.6.8 + * Agente nativo de iOS mejorado actualizado a la versión 7.5.8 + + * [Agente .NET MAUI v1.1.11](/docs/release-notes/mobile-release-notes/net-maui-release-notes/net-maui-agent-1111) + + * Agente nativo Android mejorado actualizado a la versión 7.6.8 + * Agente nativo de iOS mejorado actualizado a la versión 7.5.8 + + * [agente de infraestructura v1.65.5](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1655): + * Se modificó el soporte de montaje de AWS EFS en muestras de almacenamiento. \ No newline at end of file diff --git a/src/i18n/content/es/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1655.mdx b/src/i18n/content/es/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1655.mdx index b28d3d94b7e..5a0fadfe327 100644 --- a/src/i18n/content/es/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1655.mdx +++ b/src/i18n/content/es/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1655.mdx @@ -6,17 +6,18 @@ translationType: machine --- - **Known issues**: this release has a known issue with diskUsedPercent calculation because of StorageSample containing NFSv4 mount data on Linux hosts having NFSv4 mounts. + **Problemas conocidos**: esta versión tiene un problema conocido con el cálculo de diskUsedPercent debido a que StorageSample contiene datos de montaje NFSv4 en hosts Linux que tienen montajes NFSv4. Por favor considere una de estas alternativas: +* Use any version higher than `1.65.5` * Emplee cualquier versión inferior a `1.65.5` Se lanzó una nueva versión del agente. Siga los procedimientos estándar para [actualizar el agente de infraestructura](https://docs.newrelic.com/docs/infrastructure/install-configure-manage-infrastructure/update-or-uninstall/update-infrastructure-agent). New Relic recomienda que actualices el agente periódicamente y como mínimo cada 3 meses. A partir de esta versión, la versión compatible más antigua es [agente de infraestructura 1.51.0](https://docs.newrelic.com/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1510/). ## Cambió -* Característica: compatibilidad con montajes de AWS EFS en muestras de almacenamiento en #2069 +* feat: support AWS EFS mounts in storage samples in #2069 * chore(deps): golpe golang.org\\/x\\/oauth2 de 0,20.0 a 0,27.0 en #2093 * chore(deps): actualizar la versión de nri-prometheus a v2.27.0 en #2094 \ No newline at end of file diff --git a/src/i18n/content/es/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5306.mdx b/src/i18n/content/es/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5306.mdx new file mode 100644 index 00000000000..27697a1c7c7 --- /dev/null +++ b/src/i18n/content/es/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5306.mdx @@ -0,0 +1,11 @@ +--- +subject: Mobile app for Android +releaseDate: '2025-08-07' +version: 5.30.6 +downloadLink: 'https://play.google.com/store/apps/details?id=com.newrelic.rpm' +translationType: machine +--- + +### Mejoras + +* Compatibilidad con claves de acceso para inicios de sesión SAML y sociales \ No newline at end of file diff --git a/src/i18n/content/es/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx b/src/i18n/content/es/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx new file mode 100644 index 00000000000..0f31403d612 --- /dev/null +++ b/src/i18n/content/es/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx @@ -0,0 +1,39 @@ +--- +subject: Browser agent +releaseDate: '2025-08-04' +version: 1.295.0 +downloadLink: 'https://www.npmjs.com/package/@newrelic/browser-agent' +features: + - Add error cause detection +bugs: + - Add monkey-patching warnings + - Calculate first and last timestamps from raw data +security: [] +translationType: machine +--- + +## v1.295.0 + +### Característica + +#### Agregar detección de causa de error + +Detectar y reportar la causa del atributo en el evento JavaScriptError capturado. Si la causa es una instancia de un Error, se capturará el rastreo de la stack, de lo contrario se informará el contenido en cadena de la causa. Esto se podrá consultar en JavaScriptError incluso bajo el atributo `cause`. + +### Corrección de errores + +#### Agregar advertencias sobre parches de mono + +Se agregó detección y advertencias para cuando los valores globales esperados fueron parcheados antes de que el agente se ejecutó en la página. Esto puede provocar comportamientos inesperados y la intención es informar a los clientes sobre este comportamiento. + +#### Calcular la primera y la última marca de tiempo a partir de datos sin procesar + +Cerciorar de que el agente calcule manualmente la primera y la última marca de tiempo de una carga de SessionReplay antes de la recolección para ayudar a mejorar la consistencia en el reproductor UI. + +## Declaración de apoyo + +New Relic recomienda que actualices el agente periódicamente para garantizar que obtengas las últimas características y beneficios de rendimiento. Las versiones anteriores ya no recibirán soporte cuando lleguen [al final de su vida útil](https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/browser-agent-eol-policy/). Las fechas de lanzamiento reflejan la fecha de publicación original de la versión del agente. + +Las nuevas versiones del agente del browser se lanzan a los clientes en pequeñas etapas a lo largo de un periodo de tiempo. Debido a esto, la fecha en que el lanzamiento esté disponible en su cuenta puede no coincidir con la fecha de publicación original. Consulte este [dashboard de estado](https://newrelic.github.io/newrelic-browser-agent-release/) para obtener más información. + +De acuerdo con nuestra [política de compatibilidad de navegadores](https://docs.newrelic.com/docs/browser/new-relic-browser/getting-started/compatibility-requirements-browser-monitoring/#browser-types), la versión 1.295.0 del agente del navegador se creó y probó con estos navegadores y rangos de versiones: Chrome 128-138, Edge 128-138, Safari 17-19 y Firefox 130-140. Para dispositivos móviles, la versión v1.295.0 fue creada y probada para Android OS 16 e iOS Safari 17-26. \ No newline at end of file diff --git a/src/i18n/content/es/docs/service-architecture-intelligence/github-integration.mdx b/src/i18n/content/es/docs/service-architecture-intelligence/github-integration.mdx index dd65b0c2ffb..1d063b5799c 100644 --- a/src/i18n/content/es/docs/service-architecture-intelligence/github-integration.mdx +++ b/src/i18n/content/es/docs/service-architecture-intelligence/github-integration.mdx @@ -53,7 +53,7 @@ Esta integración agiliza el proceso de incorporación de usuarios y equipos, si **Asignación de repositorios a equipos New Relic** -Puede asignar automáticamente el repositorio de GitHub a sus equipos creando una propiedad personalizada `teamOwningRepo` en GitHub. +Puede asignar automáticamente el repositorio de GitHub a sus equipos agregando `teamOwningRepo` como una propiedad personalizada en GitHub. 1. Cree la propiedad personalizada en el nivel de organización y asigne un valor a la propiedad personalizada en el nivel de repositorio. Además, puede configurar una propiedad personalizada para varios repositorios a nivel de organización simultáneamente. 2. Luego, en New Relic Teams, habilite la función [Automated Ownership](/docs/service-architecture-intelligence/teams/manage-teams/#assign-ownership), cerciorar de usar `team` como clave de etiqueta. diff --git a/src/i18n/content/es/docs/tutorial-improve-site-performance/guide-to-monitoring-core-web-vitals.mdx b/src/i18n/content/es/docs/tutorial-improve-site-performance/guide-to-monitoring-core-web-vitals.mdx index 434dffdf562..242c9c40c35 100644 --- a/src/i18n/content/es/docs/tutorial-improve-site-performance/guide-to-monitoring-core-web-vitals.mdx +++ b/src/i18n/content/es/docs/tutorial-improve-site-performance/guide-to-monitoring-core-web-vitals.mdx @@ -1,30 +1,32 @@ --- -title: Monitor tus principales web Métricas +title: Monitorea tus Core Web Vitals tags: - Browser - Browser monitoring - Guides -metaDescription: A guide to monitor Google's core web vitals. +metaDescription: A guide to monitor Google's Core Web Vitals. freshnessValidatedDate: '2024-03-21T00:00:00.000Z' translationType: machine --- -Las métricas web principales son las métricas de Google que miden la experiencia global del usuario. Brindan información valiosa sobre cómo los usuarios ven su negocio, lo que puede influir en la clasificación SEO de su sitio. Al tener una puntuación que captura la experiencia del usuario, puede tomar medidas sobre problemas específicos en lugar de adivinar lo que necesita su sitio. +Core Web Vitals (CWV) son la métrica de Google que mide la experiencia general del usuario. Proporcionan información valiosa sobre cómo los usuarios ven su negocio, lo que puede influir en las clasificaciones SEO de su sitio. Al tener un puntaje que captura la experiencia del usuario, puede tomar medidas sobre problemas específicos en lugar de adivinar qué necesita su sitio. ## Objetivos [#objectives] -Este tutorial lo guiará a través del uso de New Relic para desglosar sus principales web Métricas. Al final del tutorial, habrá completado estas tareas: +Este tutorial le mostrará cómo emplear New Relic para descomponer su CWV. Al finalizar el tutorial, completaste estas tareas: -* Encuentre core web vitals en New Relic. -* Comprenda cómo los principales web de Métricas se traducen en el rendimiento del sitio. +* Encuentra CWV en New Relic. +* Comprenda cómo CWV se traduce en el rendimiento del sitio. * Explore sus datos de New Relic para identificar qué contribuye a su puntuación. -## Conoce los core web vitals [#learn] +## Aprenda sobre CWV [#learn] Google mide el rendimiento general del sitio web mediante estas tres métricas: * [Pintura de contenido más grande](https://web.dev/articles/lcp) (LCP): cuánto tiempo tarda en cargarse el contenido principal de una página. Por ejemplo, un usuario que llega a una página web con un LCP lento puede ver una pantalla en blanco durante varios segundos antes de que aparezca el contenido. + * [Interacción con la siguiente pintura](https://web.dev/articles/inp) (INP): Cuánto tiempo tarda una página en responder a la interacción de un usuario. Por ejemplo, si un usuario hace clic en un botón, INP mide cuánto tiempo pasa entre el clic y la apertura de la siguiente página. Un INP alto refleja una experiencia de página web lenta y que no responde, lo que dificulta la participación del usuario. + * [Cambio de diseño acumulativo](https://web.dev/articles/cls) (CLS): con qué frecuencia se producen cambios de diseño inesperados en una página mientras se carga. Por ejemplo, un usuario que está a punto de hacer clic en un botón puede encontrar que el contenido salta a un nuevo lugar en la pantalla, lo que podría hacer que haga clic en otra cosa accidentalmente. Un CLS alto puede hacer que una página web parezca torpe y difícil de interactuar. Cada web vital tiene el siguiente umbral para ayudarle a realizar un seguimiento del rendimiento y el SEO de su aplicación: @@ -32,7 +34,7 @@ Cada web vital tiene el siguiente umbral para ayudarle a realizar un seguimiento - diff --git a/src/i18n/content/fr/docs/browser/new-relic-browser/performance-quality/browser-monitoring-performance-impact.mdx b/src/i18n/content/fr/docs/browser/new-relic-browser/performance-quality/browser-monitoring-performance-impact.mdx index 123d8e1e8a0..2fe47954d24 100644 --- a/src/i18n/content/fr/docs/browser/new-relic-browser/performance-quality/browser-monitoring-performance-impact.mdx +++ b/src/i18n/content/fr/docs/browser/new-relic-browser/performance-quality/browser-monitoring-performance-impact.mdx @@ -162,7 +162,7 @@ L'agent se compose de plusieurs scripts pour réduire la taille initiale du @@ -300,7 +300,7 @@ L'agent se compose de plusieurs scripts pour réduire la taille initiale du diff --git a/src/i18n/content/fr/docs/change-tracking/change-tracking-events.mdx b/src/i18n/content/fr/docs/change-tracking/change-tracking-events.mdx index 6d05fa08c48..78a84531329 100644 --- a/src/i18n/content/fr/docs/change-tracking/change-tracking-events.mdx +++ b/src/i18n/content/fr/docs/change-tracking/change-tracking-events.mdx @@ -29,7 +29,7 @@ translationType: machine La fonctionnalité de suivi des changements vous permet de capturer, de visualiser et d'analyser les changements dans vos applications et infrastructure. Cette fonctionnalité est conçue pour vous aider à comprendre comment les changements impactent à la fois votre système et vos clients. -* **Capture all changes impacting your system:** Send change events for any type of change, including deployments, feature flags changes, configuration changes, and business events. You can also create custom change events tailored to your specific requirements. Use the [`changeTrackingCreateEvent`](#change-tracking-event-mutation) NerdGraph mutation to easily send various types of change events. +* **Capturez tous les changements impactant votre système :** envoyez un événement de modification pour tout type de changement, y compris les changements de fonctionnalités, les indicateurs de fonctionnalités, les changements configuration et les événements commerciaux. Vous pouvez également créer des événements de changement personnalisés adaptés à vos besoins spécifiques. Utilisez la mutation NerdGraph [`changeTrackingCreateEvent`](#change-tracking-event-mutation) pour envoyer facilement différents types d'événements de changement. * **Bénéficiez d'une vue complète pour gérer les modifications à l'échelle du système :** visualisez et filtrez de manière transparente les événements de modification sur l'ensemble de votre entité et de vos comptes à partir d'une interface unifiée. Identifiez sans effort les changements en filtrant par équipe, type, attribut personnalisé et tout autre critère. diff --git a/src/i18n/content/fr/docs/new-relic-control/agent-control/configuration.mdx b/src/i18n/content/fr/docs/new-relic-control/agent-control/configuration.mdx index a5d82150e91..e6b97f2b3f5 100644 --- a/src/i18n/content/fr/docs/new-relic-control/agent-control/configuration.mdx +++ b/src/i18n/content/fr/docs/new-relic-control/agent-control/configuration.mdx @@ -306,21 +306,22 @@ Pour les configurations de proxy utilisant l'authentification HTTPS avec de secretName: ca-certs # Configure Flux components to use proxy - flux2: - sourceController: - extraEnv: - # Configure Flux source-controller to proxy all requests - - name: HTTPS_PROXY - value: https://proxy-service:8080 - # Except for in-cluster requests - - name: "NO_PROXY" - value: ".cluster.local.,.cluster.local,cluster.local,.svc,127.0.0.0/8,10.0.0.0/8" - volumeMounts: - # Mount CA certificate bundle to source-controller trust root store. The bundle should contain the - # proxy CA cert. - - mountPath: /etc/ssl/certs/ - name: ca-certs - volumes: + agent-control-cd: + flux2: + sourceController: + extraEnv: + # Configure Flux source-controller to proxy all requests + - name: HTTPS_PROXY + value: https://proxy-service:8080 + # Except for in-cluster requests + - name: "NO_PROXY" + value: ".cluster.local.,.cluster.local,cluster.local,.svc,127.0.0.0/8,10.0.0.0/8" + volumeMounts: + # Mount CA certificate bundle to source-controller trust root store. The bundle should contain the + # proxy CA cert. + - mountPath: /etc/ssl/certs/ + name: ca-certs + volumes: - name: ca-certs secret: secretName: ca-certs @@ -338,20 +339,160 @@ Pour les configurations de proxy utilisant l'authentification HTTPS avec de Lorsque vous utilisez un proxy, vous devez également configurer les paramètres de proxy pour chaque agent géré individuellement. Reportez-vous à la documentation spécifique de chaque agent pour les options de configuration du proxy. -## Private repository configuration +## Gestion des secrets -Agent Control supports configuring private Helm repositories to deploy both Agent Control itself and the managed agents. This enables environments where the New Relic Helm charts are not directly accessible. +Agent Control provides a robust mechanism for managing sensitive data, such as passwords and API keys, by retrieving them from dedicated secret providers. This ensures that sensitive information is not hard-coded directly into configuration files. The system currently supports the following secret providers: + +* HashiCorp Vault: referred to as `nr-vault` in configurations. +* Kubernetes Secrets: referred to as `nr-kubesec` in configurations. + +### Defining Secrets in Configuration + +To utilize secrets, define them within your Agent-Control configuration YAML file by following these steps: + +1. **Define the `secrets_providers` section:** Configure your secret providers centrally in this section. Ensure each entry corresponds to a supported provider. +2. **Configure secret sources:** For each provider, specify one or more sources. A source includes the necessary configuration details (e.g., URL, token) for Agent control to connect to and retrieve a group of secrets. +3. **Use placeholders in agent configurations:** Instead of the actual sensitive data, Use a placeholder string within your agent's configuration. Agent control automatically replaces these placeholders with the retrieved secrets during the rendering process. + + + If Agent control fails to retrieve a secret, the configuration rendering will fail, and the agent will not be executed. This is a critical security feature to prevent agents from running with incomplete or incorrect configurations. + + +The following agent-control configuration example demonstrates how to configure for retrieving secrets from two Vault sources within the `secrets_providers` section: + +```yaml +secrets_providers: + vault: + sources: + local-instance: + url: http://localhost:8200/v1/ + token: root + engine: kv2 + remote: + url: http://my-remote-server:8200/v1/ + token: root + engine: kv1 + +fleet_control: + ... + +agents: + ... +``` + +#### Using Secrets in an Agent Configuration + +After the sources are defined, in an agent configuration, you can reference the vault using a specific placeholder syntax with the correct path. Agent control retrieves the secret and uses it to render the final configuration file that the agent is going to use. + +Example of agent configuration using vault placeholders: + +```yaml +config_agent: |+ + enable_process_metrics: true + custom_attributes: + username: "${nr-vault:local-instance:secret:my_secret:username}" + organization: "${nr-vault:remote:my_mount:my_path:organization}" +``` + +Dans cet exemple : + +The placeholder `${nr-vault:local-instance:secret:my_secret:username}` instructs Agent control to retrieve the value associated with the key username from the secret at the path `secret/my_secret` using the local-instance vault source. The placeholder `${nr-vault:remote:my_mount:my_path:organization}` similarly retrieves the value for the organization key from the remote source. + +After successful retrieval, Agent control renders these secrets from the specified source and path, storing the result in a K8s secret or private config file for use by the corresponding agent. + +### Les secrets du coffre-fort + +Set up the vault sources with the following settings: + +
+ Bien @@ -114,7 +116,7 @@ Cada web vital tiene el siguiente umbral para ayudarle a realizar un seguimiento ### ¿Cómo se calcula la puntuación CLS? - La puntuación acumulativa de cambio de diseño es un valor sin unidades entre 0 e infinito, no una medida basada en el tiempo como los otros core web vitals. Refleja la suma del impacto de los cambios inesperados de diseño que ocurren durante el proceso de carga de una página web. Así es como se calcula la puntuación CLS: + El puntaje de cambio de diseño acumulativo es un valor sin unidades entre 0 e infinito, no una medición basada en el tiempo como las otras CWV. Refleja la suma del impacto de los cambios de diseño inesperados que ocurren durante el proceso de carga de un sitio web. Así es como se calcula el puntaje CLS: * Puntuación de cambio de diseño: esto considera dos factores: @@ -126,13 +128,13 @@ Cada web vital tiene el siguiente umbral para ayudarle a realizar un seguimiento **Good** web vitals puede ayudar a su organización a ahorrar dinero y aumentar el SEO. **Poor** o **Needs improvement** pueden reflejar percepciones negativas de los usuarios sobre su organización, lo que podría generar clientes insatisfechos o pérdida de oportunidades comerciales. -New Relic aprovecha [la biblioteca API`web-vitals` ](https://github.com/GoogleChrome/web-vitals)de Google para recopilar datos vitales web en su estado original, sin introducir cálculos adicionales. Para obtener más información sobre por qué son importantes los core web vitals y cómo se calculan, consulte el artículo de web.dev [rendimiento métrico centrado en el usuario](https://web.dev/articles/user-centric-performance-metrics). +New Relic aprovecha [la biblioteca API`web-vitals` ](https://github.com/GoogleChrome/web-vitals)de Google para recopilar datos sitio web vitales en su estado original, sin introducir cálculos adicionales. Para obtener más información sobre por qué son importantes los CWV y cómo se calculan, consulte el artículo de sitio web.dev [Rendimiento métrico centrado en el usuario](https://web.dev/articles/user-centric-performance-metrics). -## Encuentre core web vitals en New Relic [#view-data-in-nr] +## Encuentra CWV en New Relic [#view-data-in-nr] -Los core web vitals están integrados en muchas características New Relic , pero la mejor manera de ver web vitals en un alto nivel es: +Los CWV están integrados en muchas características New Relic, pero la mejor forma de ver los sitio web vitals a un alto nivel es: -1. Vaya a **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Browser**. +1. Vaya a **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Browser**. 2. Seleccione una aplicación. @@ -140,163 +142,56 @@ Los core web vitals están integrados en muchas características New Relic , per La página de **Web Vitals** muestra los promedios de Web Vitals para todo su sitio web. Desde esta vista, puede profundizar en páginas específicas o métricas para ver qué está impactando las puntuaciones. - overview of the web vitals page + overview of the web vitals page ### Profundizar en páginas específicas [#drill-down] -Si desea incluir información valiosa en una página importante (por ejemplo, una página de pago de comercio electrónico), búsquela en la tabla **Page URL** . Verá un desglose de lo que contribuye a los principales web de Métricas, que puede utilizar para comprender cómo el usuario final experimenta esas áreas de su sitio. Por ejemplo, si observa un patrón de rendimiento deficiente en el navegador Chrome, puede seleccionar mejoras futuras para esa base de usuarios. +Si desea información valiosa en una página importante (por ejemplo, una página de pago de comercio electrónico), búsquela en la tabla **Page URL**. Verá un desglose de lo que contribuye a las CWV, que puede usar para comprender cómo sus usuarios finales experimentan esas áreas de su sitio. Por ejemplo, si nota un patrón de bajo rendimiento en los navegadores Chrome, puede planear futuras mejoras para esa base de usuarios. -Click on a page URL to see page-specific web vitals. +Click on a page URL to see page-specific web vitals.
- **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Browser > (select an app) > Monitor > Web vitals > (click on a page URL)**: Vea un desglose de los principales web de Métricas para las páginas web más impactantes. + **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Browser > (select an app) > Monitor > Web vitals > (click a page URL)**:Vea un desglose de los CWV para los sitios web más impactantes.
### Filtrar por atributo clave [#key-attributes] -Si desea investigar algo en particular, como cómo un cambio de backend o un problema de rendimiento afectó a los principales web de Métricas, puede utilizar la herramienta **Filter by** para filtrar cualquier atributo clave. +Si desea investigar algo en individuo, como cómo un cambio de backend o un problema de rendimiento afectó a los CWV, puede usar la herramienta **Filter by** para filtrar cualquier atributo clave. -Filter by key attributes +Filter by key attributes
- **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Browser > (select an app) > Monitor > Web vitals > (add filters)**: Utilice la herramienta de filtro para filtrar Métricas web principales por atributo clave. + **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Browser > (select an app) > Monitor > Web vitals > (add filters)**: Utilice la herramienta de filtro para filtrar Métricas web principales por atributo clave.
Aunque puede filtrar por casi cualquier atributo clave, siga leyendo para conocer algunos ejemplos útiles. - - Supongamos que desea comparar el rendimiento de la computadora de escritorio con el del dispositivo móvil y cómo las Métricas web principales difieren entre las dos plataformas. Para investigar esto en **Web vitals**: - - 1. En el campo - - - **Filter by** - - - , establezca - - - **Attribute** - - - en`deviceType` y - - - **Value** - - - en `desktop`. - - 2. En un browser duplicado, establezca + + Digamos que desea comparar el rendimiento de computadoras de escritorio con el de dispositivos móviles y cómo los CWV difieren entre las dos plataformas. Para investigar esto en **Web vitals**: - - **Attribute** - - - en`deviceType` y - - - **Value** - - - en `mobile` y luego compare los resultados. + 1. En el campo **Filter by** , establezca **Attribute** en`deviceType` y **Value** en `desktop`. + 2. En un browser duplicado, establezca **Attribute** en`deviceType` y **Value** en `mobile` y luego compare los resultados. - + Supongamos que un usuario final informó problemas de rendimiento en la página de pago de su sitio el 1 de noviembre, alrededor de las 12:00 p. m., y desea ver qué sucedió con este usuario. Para investigar esto en **Web vitals**: 1. Establezca el rango de tiempo al 1 de noviembre, entre las 11 a. m. y la 1 p. m. + 2. En la tabla **Page URL** , haga clic en la URL de la página de pago. + 3. En el campo **Filter by** , establezca **Attribute** en `userID` y **Value** en `user ID`. - 2. En la tabla - - - **Page URL** - - - , haga clic en la URL de la página de pago. - - 3. En el campo - - - **Filter by** - - - , establezca - - - **Attribute** - - - en `userID` y - - - **Value** - - - en `user ID`. - - - `userID` es un atributo personalizado que deberá configurar mediante la [API SPA del navegador](/docs/browser/new-relic-browser/browser-agent-spa-api/setcustomattribute-browser-agent-api/). Si `userID` no está disponible, también puede filtrar por otra información de usuario como `username` o `session`. - + + `userID` es un atributo personalizado que deberá configurar mediante la [API SPA del navegador](/docs/browser/new-relic-browser/browser-agent-spa-api/setcustomattribute-browser-agent-api/). Si `userID` no está disponible, también puede filtrar por otra información de usuario como `username` o `session`. + - - Supongamos que su organización actualizó recientemente imágenes en la página de inicio del sitio el 10 de noviembre a las 8 a. m. y desea ver si los cambios afectaron a Métricas web principales. Para investigar esto en **Web vitals**: + + Digamos que su organización actualizó recientemente las imágenes en la página de inicio del sitio el 10 de noviembre a las 8 a. m. y desea ver si los cambios afectaron a los CWV. Para investigar esto en **Web vitals**: 1. Establezca el rango de tiempo para el 10 de noviembre entre las 7 a. m. y las 9 a. m. - - 2. En la tabla - - - **Page URL** - - - , haga clic en la URL de la página de inicio. - - 3. En el campo - - - **Filter by** - - - , establezca - - - **Attribute** - - - en `elementTagName` y - - - **Value** - - - en `IMG`. + 2. En la tabla **Page URL**, haga clic en la URL de la página de inicio. + 3. En el campo **Filter by** , establezca **Attribute** en `elementTagName` y **Value** en `IMG`. @@ -304,47 +199,32 @@ Aunque puede filtrar por casi cualquier atributo clave, siga leyendo para conoce New Relic captura datos sobre la sesión de un usuario en una página determinada. El rastreo de sesión se muestra aleatoriamente, lo que le permite ver cómo un usuario experimentó problemas de tiempo de carga de la página, eventos de JavaScript u otros errores. -Session traces in Browser UI lets you look at real user sessions for a given page +Session traces in Browser UI lets you look at real user sessions for a given page -Recomendamos utilizar rastreo de sesión para encontrar patrones en diferentes sesiones de usuario. Si uno de sus puntajes principales web de Métricas podría mejorarse, una opción es mirar el rastreo de sesión para ver qué atributo común se comparte entre las diferentes sesiones de usuario. Aquí tienes un ejemplo de cómo el rastreo de sesión puede ayudarte a mejorar tu sitio: +Recomendamos emplear el rastreo de sesiones para encontrar patrones en diferentes sesiones de usuario. Si se pudiera mejorar alguna de sus puntajes CWV, una opción es consultar el seguimiento de sesiones para ver qué atributos comunes se comparten entre las diferentes sesiones de usuario. A continuación se muestra un ejemplo de cómo el seguimiento de sesiones puede ayudarlo a mejorar su sitio: -1. En la pestaña +1. En la pestaña **Web vitals** , haga clic en la página que tiene un rendimiento deficiente. Usando la imagen de arriba como ejemplo, verá que su sitio tiene una buena puntuación LCP general, pero también notará que algunas de sus páginas individuales necesitan mejorar. +2. Si observa la sección **Page URLs** de la página **Web vitals** , verá que la URL de su página de inicio tiene una puntuación LCP superior a cuatro segundos. ¿Se debe a un error que afecta a todos los usuarios o sólo afecta a un tipo de usuario? Por ejemplo, si nota que un usuario con una versión de Chrome o un determinado sistema operativo experimenta un tiempo de carga de la página lento, podrá solucionar mejor la causa específica del problema. +3. Se abrirá una nueva ventana cuando haga clic en la URL que desea solucionar. Observa que su puntuación LCP es mucho más alta que la puntuación LCP general de su sitio. Al desplazarse a la sección **Session traces** en la parte inferior de esta página, verá varios ejemplos de sesiones de usuarios reales. Estas sesiones pueden brindarle detalles más granulares sobre cómo ese usuario experimentó solicitudes AJAX, problemas relacionados con la carga de DOM, eventos de JavaScript u otros errores. - - **Web vitals** - - - , haga clic en la página que tiene un rendimiento deficiente. Usando la imagen de arriba como ejemplo, verá que su sitio tiene una buena puntuación LCP general, pero también notará que algunas de sus páginas individuales necesitan mejorar. - -2. Si observa la sección +Los datos de sesiones aleatorias le ayudan a encontrar patrones en cientos o miles de interacciones de usuarios con una página web. Si aparece un patrón en estos datos seleccionados al azar, puede tener más confianza en que su plan para resolver un problema mejorará las puntuaciones de su página. - - **Page URLs** - +## Mejore su comprensión con Session Replay [#session-replays] - de la página +Si se identificó un LCP deficiente o un CLS alto, Session Replay proporciona un registro visual de lo ocurrido, lo que ayuda a localizar rápidamente el elemento o evento exacto que causa el problema. - - **Web vitals** - +A continuación se muestra un ejemplo de cómo Session Replay puede ayudarlo a mejorar su sitio: - , verá que la URL de su página de inicio tiene una puntuación LCP superior a cuatro segundos. ¿Se debe a un error que afecta a todos los usuarios o sólo afecta a un tipo de usuario? Por ejemplo, si nota que un usuario con una versión de Chrome o un determinado sistema operativo experimenta un tiempo de carga de la página lento, podrá solucionar mejor la causa específica del problema. +1. Identificar un problema de rendimiento: en la página **Web vitals**, haga clic en la URL correspondiente para abrir su vista detallada de rendimiento. Esta acción redirecciona a una vista detallada de la información de sitio web vitals para esa página. Examine los puntajes CWV y busque cualquiera con las etiquetas **Needs improvement** o **Poor**. También puedes filtrar los resultados por tipo de dispositivo o navegador, ya que los problemas de rendimiento pueden variar significativamente según la plataforma. Comprender estos detalles ayuda a identificar áreas específicas para la optimización. -3. Se abrirá una nueva ventana cuando haga clic en la URL que desea solucionar. Observa que su puntuación LCP es mucho más alta que la puntuación LCP general de su sitio. Al desplazarse a la sección +2. Acceder a las repeticiones relevantes: haga clic en el número en la columna **Session replays** correspondiente al punto de datos que está investigando. Esta acción filtra automáticamente las repeticiones para mostrar las sesiones que experimentaron el problema de rendimiento específico. Por ejemplo, al hacer clic en el recuento de repeticiones de sesión de una página con un LCP deficiente, se mostrará una lista de sesiones en las que el LCP fue lento. - - **Session traces** - +3. Mira y diagnostica: Mira las grabaciones de video para obtener una comprensión visual del problema. Podrías descubrir: - en la parte inferior de esta página, verá varios ejemplos de sesiones de usuarios reales. Estas sesiones pueden brindarle detalles más granulares sobre cómo ese usuario experimentó solicitudes AJAX, problemas relacionados con la carga de DOM, eventos de JavaScript u otros errores. + * Problemas de LCP: una imagen de héroe o un video de gran tamaño que se cargó lentamente, lo que provocó una pantalla en blanco durante varios segundos. + * Problemas de CLS: un anuncio o contenido de terceros que se cargó tarde, lo que provocó que el contenido de la página cambiara de manera inesperada. + * Problemas de INP: un botón o un elemento interactivo que responde lentamente puede causar frustración. -Los datos de sesiones aleatorias le ayudan a encontrar patrones en cientos o miles de interacciones de usuarios con una página web. Si aparece un patrón en estos datos seleccionados al azar, puede tener más confianza en que su plan para resolver un problema mejorará las puntuaciones de su página. +Al combinar los datos técnicos del seguimiento de sesión con el contexto visual de Session Replay, puede desarrollar un plan integral para resolver problemas de rendimiento y mejorar significativamente su experiencia de usuario final. - + \ No newline at end of file diff --git a/src/i18n/content/es/docs/tutorial-manage-large-log-volume/organize-large-logs.mdx b/src/i18n/content/es/docs/tutorial-manage-large-log-volume/organize-large-logs.mdx index cb4e51c591d..5bf264e53bf 100644 --- a/src/i18n/content/es/docs/tutorial-manage-large-log-volume/organize-large-logs.mdx +++ b/src/i18n/content/es/docs/tutorial-manage-large-log-volume/organize-large-logs.mdx @@ -33,9 +33,9 @@ Analizar su log durante la ingesta es la mejor manera de hacer que usted y otros Análisis previo: - ``` + ```json { - "message": "32 4329 store_Portland" + "message": "32 4329 store_Portland" } @@ -45,17 +45,17 @@ Analizar su log durante la ingesta es la mejor manera de hacer que usted y otros Análisis posterior: - ``` + ```json { - "transaction_total": "32", - "purchase_number": "4329", - "store_location": "store_Portland", + "transaction_total": "32", + "purchase_number": "4329", + "store_location": "store_Portland", } ``` -Esto le permite consultar fácilmente el atributo recién definido, como `transaction_total` en el panel y alerta. +Esto le permite consultar fácilmente el atributo recién definido, como `transaction_total` en el dashboard y alerta. ## Organiza tu log @@ -120,9 +120,9 @@ Para hacerlo: Trabajemos con el ejemplo que usamos anteriormente en este documento. Tienes un log que sigue este patrón: - ``` + ```json { - "message": "32 4329 store_Portland" + "message": "32 4329 store_Portland" } ``` @@ -136,11 +136,11 @@ Para hacerlo: Una vez que se crea la regla de análisis con el patrón anterior, devolverá el log de la siguiente manera: - ``` + ```json { - "transaction_total": "32", - "purchase_number": "4329", - "store_location": "store_Portland", + "transaction_total": "32", + "purchase_number": "4329", + "store_location": "store_Portland", } ``` diff --git a/src/i18n/content/fr/docs/apis/nerdgraph/examples/nerdgraph-scorecards-custom-tutorial.mdx b/src/i18n/content/fr/docs/apis/nerdgraph/examples/nerdgraph-scorecards-custom-tutorial.mdx index 37e85edfd5e..dfdc395a4ab 100644 --- a/src/i18n/content/fr/docs/apis/nerdgraph/examples/nerdgraph-scorecards-custom-tutorial.mdx +++ b/src/i18n/content/fr/docs/apis/nerdgraph/examples/nerdgraph-scorecards-custom-tutorial.mdx @@ -98,24 +98,23 @@ New Relic fournit diverses mutations NerdGraph pour créer un rôle personnalis #### Demande d'échantillon ```graphql - { + { customerAdministration { - permissions(filter: {scope: {eq: "organization"}}) { - items { - feature - category - id - product - } + permissions(filter: { scope: { eq: "organization" } }) { + items { + feature + category + id + product } } } - + } ``` #### Exemple de réponse - ```graphql + ```json { "data": { "customerAdministration": { @@ -174,31 +173,28 @@ New Relic fournit diverses mutations NerdGraph pour créer un rôle personnalis } } } - ``` Copiez et collez les informations relatives aux Scorecards dans un fichier texte correspondant aux critères suivants : * `category: MANAGE` - * `"feature"``: "Scorecards"` ou `“Scorecards Rules”` + * `"feature"``: "Scorecards"` ou `"Scorecards Rules"` Par exemple, dans la réponse précédente, ce qui suit correspond aux critères : - ```graphql - + ```json { - "category": "MANAGE", - "feature": "Scorecards Rules", - "id": "xxxxx", - "product": "New Relic One" - }, + "category": "MANAGE", + "feature": "Scorecards Rules", + "id": "xxxxx", + "product": "New Relic One" + }, { - "category": "MANAGE", - "feature": "Scorecards", - "id": "xxxxx", - "product": "New Relic One" - } - + "category": "MANAGE", + "feature": "Scorecards", + "id": "xxxxx", + "product": "New Relic One" + } ``` @@ -208,19 +204,18 @@ New Relic fournit diverses mutations NerdGraph pour créer un rôle personnalis #### Demande d'échantillon ```graphql - { + { actor { organization { id - } } } - + } ``` #### Exemple de réponse - ```graphql + ```json { "data": { "actor": { @@ -230,7 +225,6 @@ New Relic fournit diverses mutations NerdGraph pour créer un rôle personnalis } } } - ``` Copiez l’ID de l’organisation et conservez-le pour créer un rôle. @@ -323,11 +317,11 @@ New Relic fournit diverses mutations NerdGraph pour créer un rôle personnalis
- `PermissionId` + `permissionIds` - Int + \[Int] @@ -370,10 +364,9 @@ New Relic fournit diverses mutations NerdGraph pour créer un rôle personnalis #### Demande d'échantillon ```graphql - mutation { customRoleCreate( - container: {id: "xxx****xxx-xx**00**-xxx-x*x*-xx**XXX**XX", type: "organization"} + container: { id: "xxx****xxx-xx**00**-xxx-x*x*-xx**XXX**XX", type: "organization" } name: "Scorecards manager" permissionIds: [xxxxx, xxxxx] scope: "organization" @@ -381,13 +374,11 @@ New Relic fournit diverses mutations NerdGraph pour créer un rôle personnalis id } } - ``` #### Exemple de réponse - ```graphql - + ```json { "data": { "customRoleCreate": { @@ -395,7 +386,6 @@ New Relic fournit diverses mutations NerdGraph pour créer un rôle personnalis } } } - ``` @@ -487,10 +477,9 @@ New Relic fournit diverses mutations NerdGraph pour créer un rôle personnalis #### Demande d'échantillon ```graphql - { customerAdministration { - groups(filter: {organizationId: {eq: "xxx****xxx-xx**00**-xxx-x*x*-xx**XXX**XX"}}) { + groups(filter: { organizationId: { eq: "xxx****xxx-xx**00**-xxx-x*x*-xx**XXX**XX" } }) { nextCursor items { id @@ -505,7 +494,6 @@ New Relic fournit diverses mutations NerdGraph pour créer un rôle personnalis } } } - ``` Dans la liste affichée des ID de groupe, copiez l’ID de groupe souhaité pour associer le rôle de dashboard personnalisé que vous avez créé précédemment. @@ -552,11 +540,7 @@ New Relic fournit diverses mutations NerdGraph pour créer un rôle personnalis @@ -585,7 +569,10 @@ New Relic fournit diverses mutations NerdGraph pour créer un rôle personnalis ```graphql mutation { authorizationManagementGrantAccess( - grantAccessOptions: {organizationAccessGrants: {roleId: "99999999"}, groupId: "xxx****xxx-xx**00**-xxx-x*x*-xx**XXX**XX"} + grantAccessOptions: { + organizationAccessGrants: { roleId: "99999999" } + groupId: "xxx****xxx-xx**00**-xxx-x*x*-xx**XXX**XX" + } ) { roles { id @@ -597,12 +584,11 @@ New Relic fournit diverses mutations NerdGraph pour créer un rôle personnalis } } } - ``` #### Exemple de réponse - ```graphql + ```json { "data": { "authorizationManagementGrantAccess": { @@ -619,7 +605,6 @@ New Relic fournit diverses mutations NerdGraph pour créer un rôle personnalis } } } - ``` diff --git a/src/i18n/content/fr/docs/apis/synthetics-rest-api/monitor-examples/manage-synthetics-monitors-rest-api.mdx b/src/i18n/content/fr/docs/apis/synthetics-rest-api/monitor-examples/manage-synthetics-monitors-rest-api.mdx index c718e3dda0e..e2894348f5a 100644 --- a/src/i18n/content/fr/docs/apis/synthetics-rest-api/monitor-examples/manage-synthetics-monitors-rest-api.mdx +++ b/src/i18n/content/fr/docs/apis/synthetics-rest-api/monitor-examples/manage-synthetics-monitors-rest-api.mdx @@ -351,7 +351,6 @@ En plus de l'API générale, il existe plusieurs méthodes API pour le navi ```sh scriptPayload='{"scriptText":BASE64 encoded string}' - curl -v -X PUT \ -H "Api-Key:$API_KEY" \ -H 'Content-Type: application/json' \ @@ -394,12 +393,12 @@ En plus de l'API générale, il existe plusieurs méthodes API pour le navi Cet exemple utilise `password` comme mot de passe pour `scriptLocation`: - ``` + ```shell curl -v - -X PUT -H "Api-Key:$API_KEY" - -H 'content-type: application/json' - $API_ENDPOINT/v3/monitors/$MONITOR_ID/script - -d \ + -X PUT -H "Api-Key:$API_KEY" + -H 'content-type: application/json' + $API_ENDPOINT/v3/monitors/$MONITOR_ID/script + -d \ '{ "scriptText": "dmFyIGFzc2VydCA9IHJlcXVpcmUoJ2Fzc2VydCcpOw0KYXNzZXJ0LmVxdWFsKCcxJywgJzEnKTs=", "scriptLocations": [{ @@ -469,7 +468,7 @@ Voici un exemple d'utilisation de l'API REST de New Relic et du script Dans certains cas, vous souhaiterez peut-être utiliser `-w 0`, ce qui désactivera le retour à la ligne : `base64 -w 0 $scriptfile` - ```bash + ```sh #!/bin/bash # API key from your account settings diff --git a/src/i18n/content/fr/docs/apm/agents/java-agent/troubleshooting/ssl-or-connection-errors-java.mdx b/src/i18n/content/fr/docs/apm/agents/java-agent/troubleshooting/ssl-or-connection-errors-java.mdx index 6a371a85c17..ad3e286f7b3 100644 --- a/src/i18n/content/fr/docs/apm/agents/java-agent/troubleshooting/ssl-or-connection-errors-java.mdx +++ b/src/i18n/content/fr/docs/apm/agents/java-agent/troubleshooting/ssl-or-connection-errors-java.mdx @@ -39,7 +39,7 @@ Vous pouvez télécharger le [DigiCert Global Root CA](https://www.digicert.com/ Pour importer le certificat dans votre magasin de confiance, utilisez cette commande ou consultez [la documentation Java SE d'Oracle pour keytool](https://docs.oracle.com/javase/6/docs/technotes/tools/solaris/keytool.html): -``` +```sh keytool -importcert -alias ca_alias -file ca_file.pem -keystore truststore.ts -storepass ts_password ``` diff --git a/src/i18n/content/fr/docs/apm/agents/nodejs-agent/installation-configuration/nodejs-agent-configuration.mdx b/src/i18n/content/fr/docs/apm/agents/nodejs-agent/installation-configuration/nodejs-agent-configuration.mdx index 7b16f25e2d8..fade13ced4d 100644 --- a/src/i18n/content/fr/docs/apm/agents/nodejs-agent/installation-configuration/nodejs-agent-configuration.mdx +++ b/src/i18n/content/fr/docs/apm/agents/nodejs-agent/installation-configuration/nodejs-agent-configuration.mdx @@ -824,10 +824,20 @@ Cette section définit les variables de l'agent Node.js dans l'ordre d
- L'ID de rôle personnalisé créé dans la section - - [Rôle personnalisé]() - - . + L'ID de rôle personnalisé créé dans la section Rôle personnalisé.
- Chemin complet vers le log de l'agent New Relic, y compris le nom de fichier. La valeur par défaut est `filepath: require('path').join(process.cwd(), 'newrelic_agent.log')`. L'agent arrêtera le processus s'il ne peut pas créer ce fichier. L'agent crée un fichier log avec les mêmes autorisations que le Node.js agent processus parent. + Chemin complet vers le log de l'agent New Relic, y compris le nom du fichier. La valeur par défaut est `filepath: require('path').join(process.cwd(), 'newrelic_agent.log')`. Si l'agent ne peut pas créer le fichier de log, alors il : + + * Enregistre l'erreur `New Relic failed to open log file` en utilisant `console.error`. + * Met en mémoire tampon tous les messages de log suivants. + * Lorsque la mémoire tampon atteint sa limite de 128 Mio, l'agent rejette tout nouveau message de log et émet l'avertissement suivant via `process.emitWarning`: `[NRWARN001] NewRelicWarning: Dropping log message, buffer would overflow.` + + Lors de la création du fichier de log, l'agent définit les autorisations du fichier sur 0o600 (lisible/inscriptible par le propriétaire). * Pour écrire toute le logging dans **stdout**, définissez ceci sur `stdout`. * Pour écrire toute le logging dans **stderr**, définissez ceci sur `stderr`. + + + Dans les versions d'agent antérieures à 7.0.0, l'agent arrêtait le processus s'il ne parvenait pas à créer ce fichier. + diff --git a/src/i18n/content/fr/docs/browser/new-relic-browser/browser-apis/addpageaction.mdx b/src/i18n/content/fr/docs/browser/new-relic-browser/browser-apis/addpageaction.mdx index f93ddb136f3..0184b024f7a 100644 --- a/src/i18n/content/fr/docs/browser/new-relic-browser/browser-apis/addpageaction.mdx +++ b/src/i18n/content/fr/docs/browser/new-relic-browser/browser-apis/addpageaction.mdx @@ -45,7 +45,7 @@ Rapporte un événement PageAction du navigateur avec un nom et un attribut facu Cet appel d'API envoie un [événement`PageAction` ](/docs/insights/explore-data/custom-events/insert-browser-custom-events-attributes-insights-javascript-api)du navigateur avec votre nom défini par l'utilisateur et un attribut facultatif au [dashboard](/docs/query-your-data/explore-query-data/dashboards/introduction-new-relic-one-dashboards), ainsi que [plusieurs attributs par défaut](/attribute-dictionary/?event=PageAction). Cela est utile pour suivre tout événement qui n'est pas déjà suivi automatiquement par l'agent du navigateur, comme cliquer sur un bouton **Subscribe** ou accéder à un didacticiel. * `PageAction` événement sont envoyés toutes les 30 secondes. -* Si 1 000 événements sont observés, l'agent récoltera immédiatement l'événement mis en mémoire tampon, en contournant l'intervalle du cycle de collecte. +* Si 1 000 événements sont observés ou si la taille de la charge de collecte est supérieure à 16 Ko, l'agent récoltera immédiatement l'événement mis en mémoire tampon, en contournant l'intervalle du cycle de collecte. Dans les versions antérieures de l'agent, les événements étaient abandonnés après que 120 aient été observés. La limite des événements a été augmentée de 120 à 1 000 dans la version [1.264.0](https://docs.newrelic.com/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.264.0/) et n'est plus supprimée. diff --git a/src/i18n/content/fr/docs/browser/new-relic-browser/browser-apis/recordCustomEvent.mdx b/src/i18n/content/fr/docs/browser/new-relic-browser/browser-apis/recordCustomEvent.mdx index ea419a7567b..15d4b0fb0ea 100644 --- a/src/i18n/content/fr/docs/browser/new-relic-browser/browser-apis/recordCustomEvent.mdx +++ b/src/i18n/content/fr/docs/browser/new-relic-browser/browser-apis/recordCustomEvent.mdx @@ -45,7 +45,7 @@ Signale un événement de navigateur personnalisé sous un eventType spécifié Cet appel d'API envoie un événement de navigateur personnalisé avec votre eventType défini par l'utilisateur et un attribut facultatif au [dashboard](/docs/query-your-data/explore-query-data/dashboards/introduction-new-relic-one-dashboards), ainsi que tout attribut personnalisé que vous avez peut-être défini pour votre application. Cela est utile pour suivre tout événement qui n'est pas déjà suivi automatiquement par l'agent du navigateur, amélioré par des règles et une attribution que vous contrôlez. * `custom` événement sont envoyés toutes les 30 secondes. -* Si 1 000 événements sont observés, l'agent récoltera immédiatement l'événement mis en mémoire tampon, en contournant l'intervalle du cycle de collecte. +* Si 1 000 événements sont observés ou si la taille de la charge de collecte est supérieure à 16 Ko, l'agent récoltera immédiatement l'événement mis en mémoire tampon, en contournant l'intervalle du cycle de collecte. ## Paramètres [#parameters] diff --git a/src/i18n/content/fr/docs/browser/new-relic-browser/page-load-timing-resources/instrumentation-browser-monitoring.mdx b/src/i18n/content/fr/docs/browser/new-relic-browser/page-load-timing-resources/instrumentation-browser-monitoring.mdx index ff2a403d585..096420e28dd 100644 --- a/src/i18n/content/fr/docs/browser/new-relic-browser/page-load-timing-resources/instrumentation-browser-monitoring.mdx +++ b/src/i18n/content/fr/docs/browser/new-relic-browser/page-load-timing-resources/instrumentation-browser-monitoring.mdx @@ -160,7 +160,7 @@ Pour les deux pages Web https **and** http, nous transmettons les don 		- Les données sont envoyées 10 secondes après le chargement initial de la page, puis toutes les 30 secondes par la suite. + Les données sont envoyées 10 secondes après le chargement initial de la page, puis toutes les 30 secondes par la suite. Si la taille de la charge utile de récolte est supérieure à 16 Ko, les données sont envoyées plus tôt.
- `PageViewTiming` Les événements sont collectés par tous les agents et incluent des données de synchronisation telles que les mesures des principaux éléments vitaux du Web. La première récolte se produit 10 secondes après l'événement du cycle de vie de la page `load` . Des récoltes supplémentaires se produisent toutes les 30 secondes selon les besoins lorsqu'il y a des données à envoyer. Consultez la [documentation PageViewTiming](/docs/browser/new-relic-browser/page-load-timing-resources/pageviewtiming-async-or-dynamic-page-details/#interactivity-metrics) pour obtenir une liste des événements signalés. + `PageViewTiming` Les événements sont collectés par tous les agents et incluent des données de synchronisation telles que les mesures des éléments vitaux du Web (core web vitals). La première récolte a lieu 10 secondes après l'événement du cycle de vie de la page `load` . Des récoltes supplémentaires se produisent toutes les 30 secondes selon les besoins lorsqu'il y a des données à envoyer ou si la taille de la charge utile de récolte est supérieure à 16 Ko. Consultez la [documentation PageViewTiming](/docs/browser/new-relic-browser/page-load-timing-resources/pageviewtiming-async-or-dynamic-page-details/#interactivity-metrics) pour obtenir une liste des événements signalés.
- `PageAction` Les événements sont récoltés après le cycle de vie de la page `load` . Les récoltes ultérieures se produisent toutes les 30 secondes. + `PageAction` Les événements sont récoltés après le cycle de vie de la page `load` . Les récoltes suivantes se produisent toutes les 30 secondes ou si la taille de la charge de récolte est supérieure à 16 Ko.
+ + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Clé YAML + + Description +
+ `url` + + URL pour demander des données +
+ `token` + + Used to authenticate to the endpoint. +
+ `engine` + + Specify **`kv1`** or **`kv2`**. +
+ +In the configuration file, each secret stored in Vault can be accessed by setting a placeholder with: + +* **source\_name**: The name of the Vault source defined in `secrets_providers`. +* **mount**: The name of the secrets engine mount. +* **path**: The specific path to the secret. +* **specific key**: The specific key within the secret to be retrieved. + +Example of full placeholder format: + +``` +"${nr-vault:source_name:my_mount:my_path:my_value}" +``` + +### Kubernetes secrets + +If the agent-control pod has permissions, such as through a Service Account and Role-Based Access Control (RBAC), to access the required secrets and namespaces, Agent control can directly access secrets from the Kubernetes API without needing a separate sources configuration. + +In the agent configuration file, retrieve each secret value using a placeholder specifying: + +* **namespace**: The Kubernetes namespace where the secret is located. +* **name**: The name of the Kubernetes secret object. +* **specific key**: The specific key within the secret from which to retrieve the value. + +For example, use the placeholder format: + +``` +"${nr-kubesec:my_namespace:my_secret:my_value}" +``` + +## Configuration du référentiel privé + +Agent Control prend en charge la configuration de Helm privé pour déployer à la fois Agent Control lui-même et les agents gérés. Cela permet des environnements dans lesquels les cartes New Relic Helm ne sont pas directement accessibles. - When using private Helm repositories, the charts need to be compatible and the referenced images within the charts must be reachable. If not, the agents will not work as expected. + Lors de l'utilisation du référentiel privé Helm, les cartes doivent être compatibles et les images référencées dans les cartes doivent être accessibles. Dans le cas contraire, les agents ne fonctionneront pas comme prévu. -### 1. Enable private repositories for agents +### 1. Activer le référentiel privé pour les agents -For security reasons, only explicitly enabled repositories will be allowed in remote configurations. To enable specific repositories, you need to update the Agent Control configuration: +Pour des raisons de sécurité, seul le référentiel explicitement activé sera autorisé en configuration à distance. Pour activer un référentiel spécifique, vous devez mettre à jour la configuration de l'Agent Control : - + ```yaml # values-newrelic.yaml @@ -371,7 +512,7 @@ For security reasons, only explicitly enabled repositories will be allowed in re -The allowed repository configurations can then be used in your remote configurations within New Relic Control. Example: +La configuration référentielle autorisée peut ensuite être utilisée dans votre configuration à distance au sein de New Relic Control. Exemple: ```yaml chart_version: "1.2.3" @@ -380,19 +521,19 @@ chart_repository: name: "my-chart-name" # Optional: use only if the chart name doesn't match New Relic's chart name ``` -Additionally, you need to configure Agent Control's Helm installation to use your private repository if the `agent-control` chart itself is in a private repository. This is separate from the configuration for managed agents. Refer to the `agent-control` Helm chart [values.yaml](https://github.com/newrelic/helm-charts/blob/master/charts/agent-control/values.yaml) to set up the `installationJob` section. Specifically: +De plus, vous devez configurer l'installation Helm d'Agent Control pour utiliser votre référentiel privé si le graphique `agent-control` lui-même se trouve dans un référentiel privé. Ceci est distinct de la configuration des agents gérés. Reportez-vous au fichier `agent-control` Helm chart [values.yaml](https://github.com/newrelic/helm-charts/blob/master/charts/agent-control/values.yaml) pour configurer la section `installationJob`. Spécifiquement: -* `chartRepositoryUrl` containing your repository URL -* `name` if using a different chart name -* `repositorySecretReferenceName` and `repositoryCertificateSecretReferenceName` for authentication (see the authentication section below for details) +* `chartRepositoryUrl` contenant l'URL de votre référentiel +* `name` si vous utilisez un nom de graphique différent +* `repositorySecretReferenceName` et `repositoryCertificateSecretReferenceName` pour l'authentification (voir la section authentification ci-dessous pour plus de détails) -### 2. Set up authentication for private repositories +### 2. Configurer l'authentification pour le référentiel privé -You need to set up additional resources to enable authentication for accessing your private repository: +Vous devez configurer des ressources supplémentaires pour activer l'authentification pour accéder à votre référentiel privé : - To authenticate using basic authentication (username and password), you need to create a secret in the Agent Control namespace containing the expected values in `data.username` and `data.password`. + Pour vous authentifier à l'aide de l'authentification de base (nom d'utilisateur et mot de passe), vous devez créer un secret dans l'espace de nommage Agent Control contenant les valeurs attendues dans `data.username` et `data.password`. Exemple: @@ -406,9 +547,9 @@ You need to set up additional resources to enable authentication for accessing y password: "myPassword" ``` - For more details, see the [Flux documentation](https://fluxcd.io/flux/components/source/helmrepositories/#secret-reference). + Pour plus de détails, consultez la [documentation Flux](https://fluxcd.io/flux/components/source/helmrepositories/#secret-reference). - When using basic authentication, the remote configuration should be configured as follows: + Lors de l'utilisation de l'authentification de base, la configuration à distance doit être configurée comme suit : ```yaml chart_repository: @@ -418,13 +559,13 @@ You need to set up additional resources to enable authentication for accessing y ``` - - To authenticate using TLS, you need to create a secret containing: + + Pour vous authentifier à l’aide de TLS, vous devez créer un secret contenant : - * `tls.crt` and `tls.key`: client certificate and private key used for TLS client authentication - * `ca.crt`: CA certificate used to verify the server (required if the server uses a self-signed certificate) + * `tls.crt` et `tls.key`: certificat client et clé privée utilisés pour l'authentification client TLS + * `ca.crt`: Certificat CA utilisé pour vérifier le serveur (requis si le serveur utilise un certificat auto-signé) - The Secret should be of type `Opaque` or `kubernetes.io/tls`. All files in the Secret are expected to be PEM-encoded. + Le secret doit être de type `Opaque` ou `kubernetes.io/tls`. Tous les fichiers du Secret doivent être codés en PEM. Exemple: @@ -442,9 +583,9 @@ You need to set up additional resources to enable authentication for accessing y ca.crt: ``` - For more details, see the [Flux documentation](https://fluxcd.io/flux/components/source/helmrepositories/#secret-reference). + Pour plus de détails, consultez la [documentation Flux](https://fluxcd.io/flux/components/source/helmrepositories/#secret-reference). - When using TLS certificate authentication, the remote configuration should be configured as follows: + Lors de l'utilisation de l'authentification par certificat TLS, la configuration à distance doit être configurée comme suit : ```yaml chart_repository: diff --git a/src/i18n/content/fr/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx b/src/i18n/content/fr/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx index 8038a7c5625..dd8901d75bd 100644 --- a/src/i18n/content/fr/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx +++ b/src/i18n/content/fr/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx @@ -280,7 +280,7 @@ mutation { pipelineCloudRuleEntity: { description: "Since we only care about MyEvent in staging and production, let's drop all MyEvent data in the test environment", name: "Drop MyEvent in test environment", - nrql: "DELETE FROM MyEvent where environment = 'test'", + nrql: "DELETE FROM MyEvent WHERE environment = 'test'", scope: { id: "your_nr_account_id", type: ACCOUNT @@ -304,7 +304,7 @@ mutation { pipelineCloudRuleEntity: { description: "We don't care about jvmId and targetAttr in the test environment, let's drop those attributes", name: "Drop jvmId and targetAttr from MyEvent in test environment", - nrql: "DELETE jvmId, targetAttr FROM MyEvent where environment = 'test'", + nrql: "DELETE jvmId, targetAttr FROM MyEvent WHERE environment = 'test'", scope: { id: "your_nr_account_id", type: ACCOUNT @@ -529,7 +529,7 @@ mutation { pipelineCloudRuleEntity: { description: "We don't care about targetAttr in the test environment in dimensional metric rolloups, let's drop those attributes", name: "Drop targetAttr from Metric aggregate rollups in test environment", - nrql: "DELETE targetAttr FROM MetricAggregate where environment = 'test'", + nrql: "DELETE targetAttr FROM MetricAggregate WHERE environment = 'test'", scope: { id: "your_nr_account_id", type: ACCOUNT diff --git a/src/i18n/content/fr/docs/new-relic-control/pipeline-control/data-dropping-gateway.mdx b/src/i18n/content/fr/docs/new-relic-control/pipeline-control/data-dropping-gateway.mdx index cab6b15ff54..7254699a0f1 100644 --- a/src/i18n/content/fr/docs/new-relic-control/pipeline-control/data-dropping-gateway.mdx +++ b/src/i18n/content/fr/docs/new-relic-control/pipeline-control/data-dropping-gateway.mdx @@ -524,7 +524,7 @@ Le tableau suivant répertorie : - `DELETE FROM SqlTrace WHERE uri = 'Custom\/Simple\/sqlTransaction'` + `DELETE FROM SqlTrace WHERE uri = 'Custom/Simple/sqlTransaction'` @@ -586,7 +586,7 @@ Le tableau suivant répertorie : - `DELETE FROM TransactionTrace WHERE uri = 'Custom\/Simple\/sqlTransaction'` + `DELETE FROM TransactionTrace WHERE uri = 'Custom/Simple/sqlTransaction'` @@ -730,7 +730,7 @@ Le tableau suivant répertorie : - `DELETE instanceType,inodesTotal NetworkSample WHERE entityKey = 'vagrant'` + `DELETE instanceType, inodesTotal NetworkSample WHERE entityKey = 'vagrant'` @@ -774,7 +774,7 @@ Le tableau suivant répertorie : - `DELETE FROM ContainerSample WHERE agentName='ContainerSampleAgent'` + `DELETE FROM ContainerSample WHERE agentName = 'ContainerSampleAgent'` diff --git a/src/i18n/content/fr/docs/new-relic-control/pipeline-control/nrql-functions.mdx b/src/i18n/content/fr/docs/new-relic-control/pipeline-control/nrql-functions.mdx index 22ecb3c38d9..c931e2444b9 100644 --- a/src/i18n/content/fr/docs/new-relic-control/pipeline-control/nrql-functions.mdx +++ b/src/i18n/content/fr/docs/new-relic-control/pipeline-control/nrql-functions.mdx @@ -185,8 +185,8 @@ Ce document décrit les fonctions NRQL prises en charge par le gateway Pipeline Ces exemples montrent comment vous pouvez combiner plusieurs fonctions et les utiliser dans des scénarios plus complexes pour obtenir un filtrage et une suppression précis des données. -* `DELETE FROM ContainerSample WHERE state = 'exited' and status LIKE '%Exited%' and status NOT LIKE '%second%' and status not like '%About a minute ago%' and not (status like '%minute%' and numeric(aparse(status,'%Exited (%) * minutes ago%')) < 10)` +* `DELETE FROM ContainerSample WHERE state = 'exited' AND status LIKE '%Exited%' AND status NOT LIKE '%second%' AND status NOT LIKE '%About a minute ago%' AND NOT (status LIKE '%minute%' AND numeric(aparse(status,'%Exited (%) * minutes ago%')) < 10)` * `DELETE FROM Log, LogExtendedRecord WHERE dimensions() LIKE '%collectd%' AND newrelic.logs.customEventType IS NULL` -* `DELETE FROM Log WHERE message LIKE '%lib/ladon/middleware/caching.rb:49 run> terminated with exception%' and floor(timestamp/101) = (timestamp/101)` +* `DELETE FROM Log WHERE message LIKE '%lib/ladon/middleware/caching.rb:49 run> terminated with exception%' AND floor(timestamp/101) = (timestamp/101)` Ces nouvelles fonctions étendent considérablement les capacités de votre requête NRQL lorsque vous travaillez avec le gateway de Pipeline Control, permettant une analyse et une gestion des données plus précises. \ No newline at end of file diff --git a/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx b/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx index 6327859b3c0..d1b209af713 100644 --- a/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx +++ b/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx @@ -10,7 +10,7 @@ translationType: machine * Ajout d'une nouvelle fonctionnalité sur [la façon de déboguer les problèmes de l'agent New Relic Browser ](/docs/browser/new-relic-browser/troubleshooting/how-to-debug-browser-agent/), y compris le logging détaillé, monitoring des demandes réseau et l'événement d'inspection pour un dépannage amélioré dans les versions d'agent 1.285.0 et supérieures. * Ajout de la prise en charge [d’Azure Functions](/docs/serverless-function-monitoring/azure-function-monitoring/introduction-azure-monitoring/) pour le monitoring des fonctions `python` et `.node.js`. * Ajout [d'un optimiseur de coûts](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/compute-optimizer/) pour des informations détaillées exploitables pour améliorer l'efficacité du calcul, avec une fonctionnalité permettant d'identifier les inefficacités, de fournir des recommandations d'optimisation et d'estimer les économies de CCU dans la plateforme New Relic. -* Added [Cloud Cost Intelligence](/docs/cci/getting-started/overview), offering tools for visibility and management of cloud costs, including features such as comprehensive cost breakdowns, Kubernetes cost allocation, real-time cost estimation, and cross-account data collection, currently supporting only AWS cloud costs. +* Ajout [d'Intelligence Coûts du cloud](/docs/cci/getting-started/overview), offrant des outils de visibilité et de gestion des coûts cloud, y compris des fonctionnalités telles que la répartition complète des coûts, l'allocation des coûts Kubernetes, l'estimation des coûts en temps réel et la collecte de données inter-comptes, prenant actuellement en charge uniquement les coûts AWS cloud. * Ajout [de l'observabilité OpenTelemetry pour Kubernetes avec l'intégration indépendante du fournisseur de fonctionnalités New Relic](/docs/kubernetes-pixie/k8s-otel/intro/) pour monitoring transparente du cluster via le graphique Helm, améliorant les signaux de télémétrie pour les métriques, les événements et les logs transmis aux outils et au tableau de bord de New Relic. * Ajout [de limitations et de dépannage pour l'intégration Windows](/docs/kubernetes-pixie/kubernetes-integration/troubleshooting/troubleshooting-windows/) * Ajout de l'intégration AWS via [CloudFormation et flux de métriques CloudWatch](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation/), prenant en charge l'API Polling pour les services non pris en charge. diff --git a/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx b/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx new file mode 100644 index 00000000000..d1b3ded6ad8 --- /dev/null +++ b/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx @@ -0,0 +1,60 @@ +--- +subject: Docs +releaseDate: '2025-08-08' +version: 'August 01 - August 07, 2025' +translationType: machine +--- + +### Nouveaux documents + +* [Tutoriel NerdGraph ajouté : Créer un rôle personnalisé pour les équipes](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/compute-budgets/overview) pour vous guider dans l’utilisation de l’API New Relic NerdGraph pour créer et gérer des rôles personnalisés pour les équipes. + +### Modifications mineures + +* Modification du [seuil d'alerte événement par condition](/docs/alerts/admin/rules-limits-alerts) à 1k par minutes. +* Mise à jour des dernières [versions et exigences compatibles avec l'agent .Net](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements) vérifiées. +* Mise à jour des informations de version et de prise en charge des versions concernant le courtier de services pour [VMware Tanzu](/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-service-broker-integration). +* Mise à jour des informations de prise en charge de la version concernant le buildpack d'intégration New Relic NGINX pour [VMware Tanzu](/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-nginx-buildpack-integration). +* Mise à jour des informations de version et de support de version concernant New Relic Nozzle pour [VMware Tanzu](/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-firehose-nozzle-integration/#product-snapshot). + +### Notes de version + +* Consultez nos articles Quoi de neuf : + + * [Errors Inbox est désormais intégrée à la charge de travail](/whats-new/2025/08/whats-new-08-06-workloads-errors-inbox). + +* Restez au courant de nos dernières sorties : + + * [Gestionnaire de tâches v452](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-452): + * Améliorations internes ajoutées pour la gestion des exceptions dans le traitement des messages de file d'attente. + + * [IntégrationKubernetes v3.43.3](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-43-3): + * Ajout d'un graphique Helm pour déployer la solution monitoring New Relic Kubernetes. + + * [Contrôle de pipeline Gateway v1.1.0](/docs/release-notes/pipeline-control-gateway-release-notes/pipeline-control-gateway-25-08-05): + + * Implémentation d'une nouvelle fonctionnalité permettant de supprimer de manière sélective les données et les attributs des événements `SqlTrace` et `TransactionTrace` à l'aide de règles de suppression. + + * Des vulnérabilités ont été corrigées dans le package `golang.org/x/net`, notamment un problème de script intersite et un contournement du proxy HTTP lié aux ID de zone IPv6. + + * Mise à niveau vers Go `1.24` et les dépendances suivantes sont mises à jour pour améliorer la sécurité et intégrer les correctifs récents : + + * `golang.org/x/net to v0.38.0` + * `golang.org/x/sys to v0.31.0` + * `golang.org/x/text to v0.23.0` + + * [Application mobile pour iOS v6.9.11](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6101): + * Le flux de connexion a été réduit de deux étapes en stockant le domaine d'authentification d'un utilisateur et en le redirigeant directement vers sa page de connexion. + + * [Agent Flutter v1.1.13](/docs/release-notes/mobile-release-notes/flutter-release-notes/flutter-agent-1113): + + * Agent Android natif amélioré mis à jour vers la version 7.6.8 + * Agent iOS natif amélioré mis à jour vers la version 7.5.8 + + * [Agent .NET MAUI v1.1.11](/docs/release-notes/mobile-release-notes/net-maui-release-notes/net-maui-agent-1111) + + * Agent Android natif amélioré mis à jour vers la version 7.6.8 + * Agent iOS natif amélioré mis à jour vers la version 7.5.8 + + * [Agent d'infrastructure v1.65.5](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1655): + * Modification de la prise en charge des montages AWS EFS dans les exemples de stockage \ No newline at end of file diff --git a/src/i18n/content/fr/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1655.mdx b/src/i18n/content/fr/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1655.mdx index f5d4dfcbb4a..715a427ca3a 100644 --- a/src/i18n/content/fr/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1655.mdx +++ b/src/i18n/content/fr/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1655.mdx @@ -6,17 +6,18 @@ translationType: machine --- - **Known issues**: this release has a known issue with diskUsedPercent calculation because of StorageSample containing NFSv4 mount data on Linux hosts having NFSv4 mounts. + **Problèmes connus**: cette sortie présente un problème connu avec le calcul de diskUsedPercent en raison de StorageSample contenant des données de montage NFSv4 sur des hôtes Linux ayant des montages NFSv4. Veuillez considérer l’une de ces alternatives : +* Use any version higher than `1.65.5` * Utilisez n'importe quelle version inférieure à `1.65.5` Une nouvelle version de l'agent a été sortie. Suivez les procédures standard pour [mettre à jour l'agent d'infrastructure](https://docs.newrelic.com/docs/infrastructure/install-configure-manage-infrastructure/update-or-uninstall/update-infrastructure-agent). New Relic vous recommande de mettre à niveau l'agent régulièrement et au moins tous les 3 mois. À partir de cette sortie, la version la plus ancienne prise en charge est [l'agent d'infrastructure 1.51.0](https://docs.newrelic.com/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1510/). ## Modifié -* exploit : prise en charge des montages AWS EFS dans les exemples de stockage dans #2069 +* feat: support AWS EFS mounts in storage samples in #2069 * chore(deps): bump golang.org/x/oauth2 de 0,20,0 à 0,27,0 dans #2093 * chore(deps) : mise à jour de la version nri-Prometheus vers la version 2.27.0 dans #2094 \ No newline at end of file diff --git a/src/i18n/content/fr/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5306.mdx b/src/i18n/content/fr/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5306.mdx new file mode 100644 index 00000000000..7394c9baa68 --- /dev/null +++ b/src/i18n/content/fr/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5306.mdx @@ -0,0 +1,11 @@ +--- +subject: Mobile app for Android +releaseDate: '2025-08-07' +version: 5.30.6 +downloadLink: 'https://play.google.com/store/apps/details?id=com.newrelic.rpm' +translationType: machine +--- + +### Améliorations + +* Prise en charge des clés d'accès pour SAML et les connexions sociales \ No newline at end of file diff --git a/src/i18n/content/fr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx b/src/i18n/content/fr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx new file mode 100644 index 00000000000..e635be395dd --- /dev/null +++ b/src/i18n/content/fr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx @@ -0,0 +1,39 @@ +--- +subject: Browser agent +releaseDate: '2025-08-04' +version: 1.295.0 +downloadLink: 'https://www.npmjs.com/package/@newrelic/browser-agent' +features: + - Add error cause detection +bugs: + - Add monkey-patching warnings + - Calculate first and last timestamps from raw data +security: [] +translationType: machine +--- + +## v1.295.0 + +### Caractéristiques + +#### Ajouter une détection de cause d'erreur + +Détecter et signaler l'attribut de cause sur l'événement JavaScriptError capturé. Si la cause est une instance d'une erreur, la trace des appels sera capturée, sinon le contenu stringifié de la cause sera signalé. Cela sera interrogeable dans l'événement JavaScriptError sous l'attribut `cause`. + +### Débogage + +#### Ajouter des avertissements de mise à jour de singe + +Ajout d'une détection et d'avertissements lorsque les variables globales attendues ont été corrigées avant que l'agent ne soit exécuté sur la page. Cela peut entraîner des comportements inattendus et l’objectif est d’informer les clients de ce comportement. + +#### Calculer le premier et le dernier horodatage à partir des données brutes + +Assurez-vous que l'agent calcule manuellement le premier et le dernier horodatage d'une charge SessionReplay avant la récolte pour aider à améliorer la cohérence sur le lecteur d'interface utilisateur. + +## Déclaration de soutien + +New Relic vous recommande de mettre à niveau l'agent régulièrement pour vous assurer de bénéficier des dernières fonctionnalités et avantages en termes de performances. Les sorties plus anciennes ne seront plus prises en charge lorsqu'elles atteindront [la fin de leur vie](https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/browser-agent-eol-policy/). Les dates de sortie reflètent la date de publication originale de la version de l'agent. + +Les nouveaux agents de navigation sont déployés auprès des clients par petites étapes sur une période donnée. De ce fait, la date à laquelle la sortie devient accessible sur votre compte peut ne pas correspondre à la date de publication d'origine. Veuillez consulter ce [dashboard d'état](https://newrelic.github.io/newrelic-browser-agent-release/) pour plus d'informations. + +Conformément à notre [politique de prise en charge des navigateurs](https://docs.newrelic.com/docs/browser/new-relic-browser/getting-started/compatibility-requirements-browser-monitoring/#browser-types), la version 1.295.0 de l'agent de Browser a été conçue et testée sur ces navigateurs et plages de versions : Chrome 128-138, Edge 128-138, Safari 17-19 et Firefox 130-140. Pour les appareils mobiles, la version 1.295.0 a été créée et testée pour Android OS 16 et iOS Safari 17-26. \ No newline at end of file diff --git a/src/i18n/content/fr/docs/service-architecture-intelligence/github-integration.mdx b/src/i18n/content/fr/docs/service-architecture-intelligence/github-integration.mdx index 911e598e859..7f546f0205b 100644 --- a/src/i18n/content/fr/docs/service-architecture-intelligence/github-integration.mdx +++ b/src/i18n/content/fr/docs/service-architecture-intelligence/github-integration.mdx @@ -53,7 +53,7 @@ Cette intégration rationalise le processus d'intégration des utilisateurs **Attribution d'un référentiel aux équipes New Relic** -Vous pouvez attribuer automatiquement le référentiel GitHub à leurs équipes en créant une propriété personnalisée `teamOwningRepo` dans GitHub. +Vous pouvez attribuer automatiquement le référentiel GitHub à leurs équipes en ajoutant `teamOwningRepo` comme propriété personnalisée dans GitHub. 1. Créez la propriété personnalisée au niveau de l’organisation et attribuez une valeur à la propriété personnalisée au niveau du référentiel. De plus, vous pouvez configurer une propriété personnalisée pour plusieurs référentiels au niveau de l'organisation simultanément. 2. Ensuite, dans New Relic Teams, activez la fonctionnalité [Automated Ownership](/docs/service-architecture-intelligence/teams/manage-teams/#assign-ownership), en veillant à utiliser `team` comme clé de tag. diff --git a/src/i18n/content/fr/docs/tutorial-improve-site-performance/guide-to-monitoring-core-web-vitals.mdx b/src/i18n/content/fr/docs/tutorial-improve-site-performance/guide-to-monitoring-core-web-vitals.mdx index 0ed6b73df31..261e1fb5d99 100644 --- a/src/i18n/content/fr/docs/tutorial-improve-site-performance/guide-to-monitoring-core-web-vitals.mdx +++ b/src/i18n/content/fr/docs/tutorial-improve-site-performance/guide-to-monitoring-core-web-vitals.mdx @@ -1,25 +1,25 @@ --- -title: Monitorez vos principaux éléments vitaux du Web +title: Monitorez vos Core Web Vitals tags: - Browser - Browser monitoring - Guides -metaDescription: A guide to monitor Google's core web vitals. +metaDescription: A guide to monitor Google's Core Web Vitals. freshnessValidatedDate: '2024-03-21T00:00:00.000Z' translationType: machine --- -Core web vitals sont les mesures de Google qui évaluent l'expérience globale des utilisateurs. Ils fournissent des informations précieuses et détaillées sur la façon dont les utilisateurs perçoivent votre entreprise, ce qui peut influencer le classement SEO de votre site. En ayant un score qui capture l'expérience utilisateur, vous pouvez agir sur des problèmes spécifiques plutôt que de deviner ce dont votre site a besoin. +Core Web Vitals (CWV) sont les mesures de Google qui évaluent l'expérience utilisateur globale. Ils fournissent des informations précieuses détaillées sur la façon dont les utilisateurs perçoivent votre entreprise, ce qui peut influencer le classement SEO de votre site. En ayant un score qui capture l'expérience utilisateur, vous pouvez agir sur des problèmes spécifiques plutôt que de deviner ce dont votre site a besoin. ## Objectifs [#objectives] -Ce didacticiel vous guide dans l’utilisation de New Relic pour décomposer vos principaux éléments Web vitaux. À la fin du didacticiel, vous aurez terminé ces tâches : +Ce tutoriel vous explique comment utiliser New Relic pour décomposer votre CWV. À la fin du didacticiel, vous aurez terminé ces tâches : -* Trouvez les éléments essentiels du Web dans New Relic. -* Comprenez comment les éléments essentiels du Web se traduisent par des performances de site. +* Trouvez CWV dans New Relic. +* Comprendre comment le CWV se traduit par des performances de site. * Explorez vos données New Relic pour identifier ce qui contribue à votre score. -## En savoir plus sur les éléments essentiels du Web [#learn] +## En savoir plus sur CWV [#learn] Google mesure les performances globales d'un site Web selon ces trois paramètres : @@ -116,7 +116,7 @@ Chaque élément Web essentiel possède le seuil suivant pour vous aider à suiv ### Comment le score CLS est-il calculé ? - Le score de décalage de mise en page cumulé est une valeur sans unité comprise entre 0 et l'infini, et non une mesure basée sur le temps comme les autres éléments essentiels du Web. Il reflète la somme de l’impact des changements de mise en page inattendus qui se produisent pendant le processus de chargement d’une page Web. Voici comment le score CLS est calculé : + Le score de décalage de disposition cumulé est une valeur sans unité comprise entre 0 et l'infini, et non une mesure basée sur le temps comme les autres CWV. Il reflète la somme de l’impact des changements de mise en page inattendus qui se produisent pendant le processus de chargement d’une page Web. Voici comment le score CLS est calculé : * Score de décalage de mise en page : il prend en compte deux facteurs : @@ -128,11 +128,11 @@ Chaque élément Web essentiel possède le seuil suivant pour vous aider à suiv **Good** Web Vitals peut aider votre organisation à économiser de l'argent et à augmenter son référencement. **Poor** ou **Needs improvement** peuvent refléter des perceptions négatives des utilisateurs de votre organisation, ce qui pourrait entraîner des clients insatisfaits ou des opportunités commerciales perdues. -New Relic s'appuie sur [la bibliothèque API`web-vitals` ](https://github.com/GoogleChrome/web-vitals)de Google pour collecter les données Web vitales dans leur état brut, sans introduire de calculs supplémentaires. Pour en savoir plus sur l'importance des indicateurs Web essentiels et sur la manière dont ils sont calculés, consultez l'article web.dev [sur les mesures de performance centrées sur l'utilisateur](https://web.dev/articles/user-centric-performance-metrics). +New Relic exploite [la bibliothèque API`web-vitals` ](https://github.com/GoogleChrome/web-vitals)de Google pour collecter les données Web vitales à l'état brut, sans introduire de calculs supplémentaires. Pour en savoir plus sur l'importance des CWV et sur la manière dont ils sont calculés, consultez l'article web.dev [utilisateur-centric performance métriques](https://web.dev/articles/user-centric-performance-metrics). -## Trouver les éléments essentiels du Web dans New Relic [#view-data-in-nr] +## Trouver des CWV dans New Relic [#view-data-in-nr] -Core web vitals sont intégrés à de nombreuses fonctionnalités de New Relic, mais la meilleure façon de visualiser les éléments Web vitaux à un niveau élevé est la suivante : +Les CWV sont intégrés à de nombreuses fonctionnalités de New Relic, mais la meilleure façon de visualiser les Web Vitals à un niveau élevé est : 1. Allez à **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Browser**. @@ -142,21 +142,21 @@ Core web vitals sont intégrés à de nombreuses fonctionnalités de New Relic, La page **Web Vitals** affiche vos moyennes Web Vitals pour l'ensemble de votre site Web. À partir de cette vue, vous pouvez explorer en détail des pages ou des mesures spécifiques pour voir ce qui a un impact sur les scores. - overview of the web vitals page + overview of the web vitals page ### Accédez à des pages spécifiques [#drill-down] -Si vous souhaitez des informations détaillées sur une page importante — par exemple, une page de paiement de commerce électronique — recherchez-les dans le tableau **Page URL** . Vous verrez une répartition de ce qui contribue aux éléments essentiels du Web, que vous pouvez utiliser pour comprendre comment vos utilisateurs finaux vivent ces zones de votre site. Par exemple, si vous remarquez une tendance à la baisse des performances des navigateurs Chrome , vous pouvez planifier les améliorations futures à apporter à cette base d'utilisateurs. +Si vous souhaitez des informations détaillées sur une page importante — par exemple, une page de paiement de commerce électronique — recherchez-les dans le tableau **Page URL**. Vous verrez une répartition de ce qui contribue aux CWV, que vous pouvez utiliser pour comprendre comment vos utilisateurs finaux vivent ces zones de votre site. Par exemple, si vous remarquez une tendance à la baisse des performances des navigateurs Chrome, vous pouvez organiser les améliorations futures à apporter à cette base d'utilisateurs. -Click on a page URL to see page-specific web vitals. +Click on a page URL to see page-specific web vitals.
- **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Browser > (select an app) > Monitor > Web vitals > (click on a page URL)**: Consultez une répartition des éléments essentiels du Web pour les pages Web les plus impactantes. + **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Browser > (select an app) > Monitor > Web vitals > (click a page URL)**: Consultez une répartition des CWV pour les pages Web les plus impactantes.
### Filtrer par attribut clé [#key-attributes] -Si vous souhaitez enquêter sur un élément particulier, comme l'impact d'un changement de backend ou d'un problème de performances sur les principaux éléments Web Vitals, vous pouvez utiliser l'outil **Filter by** pour filtrer n'importe quel attribut clé. +Si vous souhaitez enquêter sur un élément particulier, comme l'impact d'un changement de backend ou d'un problème de performances sur les CWV, vous pouvez utiliser l'outil **Filter by** pour filtrer n'importe quel attribut clé. Filter by key attributes @@ -168,7 +168,7 @@ Bien que vous puissiez filtrer par presque n'importe quel attribut clé, li - Disons que vous souhaitez comparer les performances des ordinateurs de bureau et des appareils mobiles et voir en quoi les éléments essentiels du Web diffèrent entre les deux plateformes. Pour enquêter sur cela dans **Web vitals**: + Supposons que vous souhaitiez comparer les performances des ordinateurs de bureau et des appareils mobiles et la manière dont les CWV diffèrent entre les deux plateformes. Pour enquêter sur cela dans **Web vitals**: 1. Dans le champ **Filter by** , définissez **Attribute** sur`deviceType` et **Value** sur `desktop`. 2. Dans un navigateur dupliqué, définissez **Attribute** sur`deviceType` et **Value** sur `mobile`, puis comparez les résultats. @@ -187,10 +187,10 @@ Bien que vous puissiez filtrer par presque n'importe quel attribut clé, li - Supposons que votre organisation ait récemment mis à jour les images sur la page d'accueil du site le 10 novembre à 8 heures du matin et que vous souhaitiez voir si les modifications ont eu un impact sur les éléments Web essentiels. Pour enquêter sur cela dans **Web vitals**: + Supposons que votre organisation ait récemment mis à jour les images sur la page d'accueil du site le 10 novembre à 8 heures du matin et que vous souhaitiez voir si les modifications ont eu un impact sur les CWV. Pour enquêter sur cela dans **Web vitals**: 1. Réglez la plage horaire sur le 10 novembre entre 7h et 9h. - 2. Dans le tableau **Page URL** , cliquez sur l’URL de la page d’accueil. + 2. Dans le tableau **Page URL**, cliquez sur l’URL de la page d’accueil. 3. Dans le champ **Filter by** , définissez **Attribute** sur `elementTagName` et **Value** sur `IMG`. @@ -201,7 +201,7 @@ New Relic capture des données sur la session d'un utilisateur sur une page Session traces in Browser UI lets you look at real user sessions for a given page -Nous vous recommandons d'utiliser trace de session pour trouver des modèles dans différentes sessions utilisateur. Si l’un de vos principaux scores Web Vitals peut être amélioré, une option consiste à examiner la trace de session pour voir quels attributs communs sont partagés entre différentes sessions utilisateur. Voici un exemple de la manière dont la trace de session peut vous aider à améliorer votre site : +Nous vous recommandons d'utiliser trace de session pour trouver des modèles dans différentes sessions utilisateur. Si l'un de vos scores CWV peut être amélioré, une option consiste à examiner la trace de session pour voir quels attributs communs sont partagés entre différentes sessions d'utilisateurs. Voici un exemple de la manière dont la trace de session peut vous aider à améliorer votre site : 1. Dans l’onglet **Web vitals** , cliquez sur la page dont les performances sont médiocres. En utilisant l'image ci-dessus comme exemple, vous voyez que votre site a un bon score LCP global, mais vous remarquez également que certaines de vos pages individuelles doivent être améliorées. 2. En regardant la section **Page URLs** de la page **Web vitals** , vous voyez que l'URL de votre page d'accueil a un score LCP supérieur à quatre secondes. Est-ce dû à une erreur qui affecte tous les utilisateurs ou cela affecte-t-il uniquement un type d'utilisateur ? Par exemple, si vous remarquez qu'un utilisateur avec une version de Chrome ou un certain système d'exploitation rencontre des temps de chargement de page lents, vous pouvez mieux résoudre la cause spécifique d'un problème. @@ -209,4 +209,22 @@ Nous vous recommandons d'utiliser trace de session pour trouver des modèle Les données provenant de sessions randomisées vous aident à trouver des modèles parmi des centaines ou des milliers d'interactions d'utilisateurs avec une page Web. Si un modèle apparaît dans ces données sélectionnées au hasard, vous pouvez être plus sûr que votre plan pour résoudre un problème améliorera les scores de vos pages. +## Améliorez votre compréhension avec Session Replay [#session-replays] + +Si un LCP médiocre ou un CLS élevé a été identifié, Session Replay fournit un enregistrement visuel de ce qui s'est produit, aidant à identifier rapidement l'élément ou l'événement exact à l'origine du problème. + +Voici un exemple de la manière dont Session Replay peut vous aider à améliorer votre site : + +1. Identifiez un problème de performances : sur la page **Web vitals**, cliquez sur l’URL correspondante pour ouvrir sa vue détaillée des performances. Cette action redirige vers une vue détaillée des informations Web Vitals pour cette page. Examinez les scores CWV et recherchez ceux portant les étiquettes **Needs improvement** ou **Poor**. Vous pouvez également filtrer les résultats par type d'appareil ou par navigateur, car les problèmes de performances peuvent varier considérablement selon la plateforme. Comprendre ces détails permet d’identifier les domaines spécifiques à optimiser. + +2. Accédez aux rediffusions pertinentes : cliquez sur le numéro dans la colonne **Session replays** correspondant au point de données que vous étudiez. Cette action filtre automatiquement les rediffusions pour afficher les sessions qui ont rencontré le problème de performances spécifique. Par exemple, cliquer sur le nombre de relectures de session pour une page avec un LCP médiocre affichera une liste de sessions où le LCP était lent. + +3. Regardez et diagnostiquez : Regardez les enregistrements vidéo pour avoir une compréhension visuelle du problème. Vous pourriez découvrir : + + * Problèmes LCP : une grande image ou vidéo de héros qui se charge lentement, provoquant un écran vide pendant plusieurs secondes. + * Problèmes CLS : une publicité ou un contenu tiers qui s'est chargé tardivement, provoquant un changement inattendu du contenu de la page. + * Problèmes INP : un bouton ou un élément interactif qui répond lentement peut être source de frustration. + +En combinant les données techniques de la trace de session avec le contexte visuel de Session Replay, vous pouvez développer un plan complet pour résoudre les problèmes de performances et améliorer considérablement votre expérience utilisateur. + \ No newline at end of file diff --git a/src/i18n/content/fr/docs/tutorial-manage-large-log-volume/organize-large-logs.mdx b/src/i18n/content/fr/docs/tutorial-manage-large-log-volume/organize-large-logs.mdx index d4365d098e7..168d777e196 100644 --- a/src/i18n/content/fr/docs/tutorial-manage-large-log-volume/organize-large-logs.mdx +++ b/src/i18n/content/fr/docs/tutorial-manage-large-log-volume/organize-large-logs.mdx @@ -33,9 +33,9 @@ Analyser vos logs lors de l'ingestion est le meilleur moyen de rendre vos d Pré-analyse : - ``` + ```json { - "message": "32 4329 store_Portland" + "message": "32 4329 store_Portland" } @@ -45,11 +45,11 @@ Analyser vos logs lors de l'ingestion est le meilleur moyen de rendre vos d Post-analyse : - ``` + ```json { - "transaction_total": "32", - "purchase_number": "4329", - "store_location": "store_Portland", + "transaction_total": "32", + "purchase_number": "4329", + "store_location": "store_Portland", } ``` @@ -120,9 +120,9 @@ Pour ce faire : Travaillons avec l’exemple que nous avons utilisé plus tôt dans ce document. Vous avez des logs qui suivent ce modèle : - ``` + ```json { - "message": "32 4329 store_Portland" + "message": "32 4329 store_Portland" } ``` @@ -136,11 +136,11 @@ Pour ce faire : Une fois la règle d'analyse créée avec le modèle ci-dessus, elle renverra les logs de la manière suivante : - ``` + ```json { - "transaction_total": "32", - "purchase_number": "4329", - "store_location": "store_Portland", + "transaction_total": "32", + "purchase_number": "4329", + "store_location": "store_Portland", } ``` diff --git a/src/i18n/content/jp/docs/apis/nerdgraph/examples/nerdgraph-scorecards-custom-tutorial.mdx b/src/i18n/content/jp/docs/apis/nerdgraph/examples/nerdgraph-scorecards-custom-tutorial.mdx index ca3cc7f38de..2f2d02587f6 100644 --- a/src/i18n/content/jp/docs/apis/nerdgraph/examples/nerdgraph-scorecards-custom-tutorial.mdx +++ b/src/i18n/content/jp/docs/apis/nerdgraph/examples/nerdgraph-scorecards-custom-tutorial.mdx @@ -98,24 +98,23 @@ New Relic は、スコアカード マネージャー用のカスタム ロー #### サンプルリクエスト ```graphql - { + { customerAdministration { - permissions(filter: {scope: {eq: "organization"}}) { - items { - feature - category - id - product - } + permissions(filter: { scope: { eq: "organization" } }) { + items { + feature + category + id + product } } } - + } ``` #### サンプル回答 - ```graphql + ```json { "data": { "customerAdministration": { @@ -174,31 +173,28 @@ New Relic は、スコアカード マネージャー用のカスタム ロー } } } - ``` 次の条件に一致するテキスト ファイルにスコアカードに関連する情報をコピーして貼り付けます。 * `category: MANAGE` - * `"feature"``: "Scorecards"` または `“Scorecards Rules”` + * `"feature"``: "Scorecards"` または `"Scorecards Rules"` たとえば、前の応答では、次のものが基準に一致します。 - ```graphql - + ```json { - "category": "MANAGE", - "feature": "Scorecards Rules", - "id": "xxxxx", - "product": "New Relic One" - }, + "category": "MANAGE", + "feature": "Scorecards Rules", + "id": "xxxxx", + "product": "New Relic One" + }, { - "category": "MANAGE", - "feature": "Scorecards", - "id": "xxxxx", - "product": "New Relic One" - } - + "category": "MANAGE", + "feature": "Scorecards", + "id": "xxxxx", + "product": "New Relic One" + } ``` @@ -208,19 +204,18 @@ New Relic は、スコアカード マネージャー用のカスタム ロー #### サンプルリクエスト ```graphql - { + { actor { organization { id - } } } - + } ``` #### サンプル回答 - ```graphql + ```json { "data": { "actor": { @@ -230,7 +225,6 @@ New Relic は、スコアカード マネージャー用のカスタム ロー } } } - ``` 組織 ID をコピーして、ロールを作成するために保管しておきます。 @@ -323,11 +317,11 @@ New Relic は、スコアカード マネージャー用のカスタム ロー - `PermissionId` + `permissionIds` - Int + \[Int] @@ -370,10 +364,9 @@ New Relic は、スコアカード マネージャー用のカスタム ロー #### サンプルリクエスト ```graphql - mutation { customRoleCreate( - container: {id: "xxx****xxx-xx**00**-xxx-x*x*-xx**XXX**XX", type: "organization"} + container: { id: "xxx****xxx-xx**00**-xxx-x*x*-xx**XXX**XX", type: "organization" } name: "Scorecards manager" permissionIds: [xxxxx, xxxxx] scope: "organization" @@ -381,13 +374,11 @@ New Relic は、スコアカード マネージャー用のカスタム ロー id } } - ``` #### サンプル回答 - ```graphql - + ```json { "data": { "customRoleCreate": { @@ -395,7 +386,6 @@ New Relic は、スコアカード マネージャー用のカスタム ロー } } } - ``` @@ -487,10 +477,9 @@ New Relic は、スコアカード マネージャー用のカスタム ロー #### サンプルリクエスト ```graphql - { customerAdministration { - groups(filter: {organizationId: {eq: "xxx****xxx-xx**00**-xxx-x*x*-xx**XXX**XX"}}) { + groups(filter: { organizationId: { eq: "xxx****xxx-xx**00**-xxx-x*x*-xx**XXX**XX" } }) { nextCursor items { id @@ -505,7 +494,6 @@ New Relic は、スコアカード マネージャー用のカスタム ロー } } } - ``` 表示されたグループ ID のリストから、必要なグループ ID をコピーして、先ほど作成したカスタム スコアカード ロールに関連付けます。 @@ -552,9 +540,7 @@ New Relic は、スコアカード マネージャー用のカスタム ロー @@ -583,7 +569,10 @@ New Relic は、スコアカード マネージャー用のカスタム ロー ```graphql mutation { authorizationManagementGrantAccess( - grantAccessOptions: {organizationAccessGrants: {roleId: "99999999"}, groupId: "xxx****xxx-xx**00**-xxx-x*x*-xx**XXX**XX"} + grantAccessOptions: { + organizationAccessGrants: { roleId: "99999999" } + groupId: "xxx****xxx-xx**00**-xxx-x*x*-xx**XXX**XX" + } ) { roles { id @@ -595,12 +584,11 @@ New Relic は、スコアカード マネージャー用のカスタム ロー } } } - ``` #### サンプル回答 - ```graphql + ```json { "data": { "authorizationManagementGrantAccess": { @@ -617,7 +605,6 @@ New Relic は、スコアカード マネージャー用のカスタム ロー } } } - ``` diff --git a/src/i18n/content/jp/docs/apis/synthetics-rest-api/monitor-examples/manage-synthetics-monitors-rest-api.mdx b/src/i18n/content/jp/docs/apis/synthetics-rest-api/monitor-examples/manage-synthetics-monitors-rest-api.mdx index dbc5d005287..43c1132cf07 100644 --- a/src/i18n/content/jp/docs/apis/synthetics-rest-api/monitor-examples/manage-synthetics-monitors-rest-api.mdx +++ b/src/i18n/content/jp/docs/apis/synthetics-rest-api/monitor-examples/manage-synthetics-monitors-rest-api.mdx @@ -351,7 +351,6 @@ https://synthetics.eu.newrelic.com/synthetics/api ```sh scriptPayload='{"scriptText":BASE64 encoded string}' - curl -v -X PUT \ -H "Api-Key:$API_KEY" \ -H 'Content-Type: application/json' \ @@ -394,12 +393,12 @@ https://synthetics.eu.newrelic.com/synthetics/api この例では、`password`を`scriptLocation`のパスワードとして使用します。 - ``` + ```shell curl -v - -X PUT -H "Api-Key:$API_KEY" - -H 'content-type: application/json' - $API_ENDPOINT/v3/monitors/$MONITOR_ID/script - -d \ + -X PUT -H "Api-Key:$API_KEY" + -H 'content-type: application/json' + $API_ENDPOINT/v3/monitors/$MONITOR_ID/script + -d \ '{ "scriptText": "dmFyIGFzc2VydCA9IHJlcXVpcmUoJ2Fzc2VydCcpOw0KYXNzZXJ0LmVxdWFsKCcxJywgJzEnKTs=", "scriptLocations": [{ @@ -469,7 +468,7 @@ New RelicのREST APIとbashスクリプトを使用して、スクリプト化 場合によっては、行の折り返しを無効にする`-w 0`を使用することができます。 `base64 -w 0 $scriptfile` - ```bash + ```sh #!/bin/bash # API key from your account settings diff --git a/src/i18n/content/jp/docs/apm/agents/java-agent/troubleshooting/ssl-or-connection-errors-java.mdx b/src/i18n/content/jp/docs/apm/agents/java-agent/troubleshooting/ssl-or-connection-errors-java.mdx index bdba019cf6b..6601f2e262b 100644 --- a/src/i18n/content/jp/docs/apm/agents/java-agent/troubleshooting/ssl-or-connection-errors-java.mdx +++ b/src/i18n/content/jp/docs/apm/agents/java-agent/troubleshooting/ssl-or-connection-errors-java.mdx @@ -39,7 +39,7 @@ Cannot find the specified class com.ibm.websphere.ssl.protocol.SSLSocketFactory 証明書をトラストストアにインポートするには、このコマンドを使用するか、または [Oracle の Java SE のドキュメントである keytool](https://docs.oracle.com/javase/6/docs/technotes/tools/solaris/keytool.html) を参照してください。 -``` +```sh keytool -importcert -alias ca_alias -file ca_file.pem -keystore truststore.ts -storepass ts_password ``` @@ -113,4 +113,4 @@ java.security.cert.CertificateException: Could not parse certificate: java.io.IO ### ソリューションB [#log-exception-solution] -証明書のヘッダーとフッターに末尾のホワイトスペースがないことを確認してください。空白がある場合は、編集するか、別の証明書を使用してください。 +証明書のヘッダーとフッターに末尾のホワイトスペースがないことを確認してください。空白がある場合は、編集するか、別の証明書を使用してください。 \ No newline at end of file diff --git a/src/i18n/content/jp/docs/browser/new-relic-browser/browser-apis/addpageaction.mdx b/src/i18n/content/jp/docs/browser/new-relic-browser/browser-apis/addpageaction.mdx index dd0bea42f28..73a0768d636 100644 --- a/src/i18n/content/jp/docs/browser/new-relic-browser/browser-apis/addpageaction.mdx +++ b/src/i18n/content/jp/docs/browser/new-relic-browser/browser-apis/addpageaction.mdx @@ -45,7 +45,7 @@ newrelic.addPageAction(string $name[, JSON object $attributes]) このAPI コールは、ユーザーが定義した名前とオプションのプロパティ、および[ いくつかのデフォルトのプロパティ](/attribute-dictionary/?event=PageAction) を含む[ ブラウザ](/docs/query-your-data/explore-query-data/dashboards/introduction-new-relic-one-dashboards) [`PageAction`イベント を](/docs/insights/explore-data/custom-events/insert-browser-custom-events-attributes-insights-javascript-api) ダッシュボード に送信します。これは、 **Subscribe**ボタンのクリックやチュートリアルへのアクセスなど、ブラウザ エージェントによってまだ自動的に追跡されていないイベントを追跡するのに役立ちます。 * `PageAction` イベントは30秒ごとに送信されます。 -* 1,000 件のイベントが観測された場合、エージェントは収集サイクル間隔をバイパスして、バッファリングされたイベントを直ちに収集します。 +* 1,000 件のイベントが観測された場合、または収集ペイロード サイズが 16 KB を超える場合、エージェントは収集サイクル間隔をバイパスして、バッファリングされたイベントを直ちに収集します。 以前のエージェント バージョンでは、120 件のイベントが観測されると、イベントはドロップされました。バージョン[1.264.0](https://docs.newrelic.com/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.264.0/)ではイベント制限が 120 から 1,000 に増加され、ドロップされなくなりました。 diff --git a/src/i18n/content/jp/docs/browser/new-relic-browser/browser-apis/recordCustomEvent.mdx b/src/i18n/content/jp/docs/browser/new-relic-browser/browser-apis/recordCustomEvent.mdx index 9c9d264d08f..96599e2679d 100644 --- a/src/i18n/content/jp/docs/browser/new-relic-browser/browser-apis/recordCustomEvent.mdx +++ b/src/i18n/content/jp/docs/browser/new-relic-browser/browser-apis/recordCustomEvent.mdx @@ -45,7 +45,7 @@ newrelic.recordCustomEvent(string $eventType[, JSON object $attributes]) このAPI コールは、アプリケーションbrowser に設定し[ ](/docs/query-your-data/explore-query-data/dashboards/introduction-new-relic-one-dashboards)たカスタム に送信します。これは、制御するルールと属性によって強化されたブラウザエージェントによってまだ自動的に追跡されていないイベントを追跡するのに役立ちます。 * `custom` イベントは30秒ごとに送信されます。 -* 1,000 件のイベントが観測された場合、エージェントは収集サイクル間隔をバイパスして、バッファリングされたイベントを直ちに収集します。 +* 1,000 件のイベントが観測された場合、または収集ペイロード サイズが 16 KB を超える場合、エージェントは収集サイクル間隔をバイパスして、バッファリングされたイベントを直ちに収集します。 ## パラメーター [#parameters] diff --git a/src/i18n/content/jp/docs/browser/new-relic-browser/performance-quality/browser-monitoring-performance-impact.mdx b/src/i18n/content/jp/docs/browser/new-relic-browser/performance-quality/browser-monitoring-performance-impact.mdx index 626e6ba8d7a..cb1005f8a95 100644 --- a/src/i18n/content/jp/docs/browser/new-relic-browser/performance-quality/browser-monitoring-performance-impact.mdx +++ b/src/i18n/content/jp/docs/browser/new-relic-browser/performance-quality/browser-monitoring-performance-impact.mdx @@ -162,7 +162,7 @@ JavaScriptのオーバーヘッドは、ユーザーへの影響とお客様の @@ -300,7 +300,7 @@ JavaScriptのオーバーヘッドは、ユーザーへの影響とお客様の diff --git a/src/i18n/content/jp/docs/change-tracking/change-tracking-events.mdx b/src/i18n/content/jp/docs/change-tracking/change-tracking-events.mdx index 8410d1f3c88..fb7d32cfdbe 100644 --- a/src/i18n/content/jp/docs/change-tracking/change-tracking-events.mdx +++ b/src/i18n/content/jp/docs/change-tracking/change-tracking-events.mdx @@ -29,7 +29,7 @@ translationType: machine 変更追跡 (変更追跡機能) 機能を使用すると、アプリケーションとインフラストラクチャ全体の変更をキャプチャ、視覚化、分析できます。 この機能は、変更がシステムと顧客の両方にどのような影響を与えるかを理解できるように設計されています。 -* **システムに影響を与えるすべての変更をキャプチャする:**機能フラグの変更、設定の変更、ビジネス イベントなど、あらゆるタイプの変更について変更イベントを送信します。 特定の要件に合わせてカスタム変更イベントを作成することもできます。[`changeTrackingCreateEvent`](#change-tracking-event-mutation) NerdGraph ミューテーションを使用すると、さまざまな種類の変更イベントを簡単に送信できます。 +* **システムに影響を与えるすべての変更をキャプチャします。**デプロイメント、機能フラグの変更、設定の変更、ビジネス イベントなど、あらゆる種類の変更について変更イベントを送信します。 特定の要件に合わせてカスタム変更イベントを作成することもできます。[`changeTrackingCreateEvent`](#change-tracking-event-mutation) NerdGraph ミューテーションを使用すると、さまざまな種類の変更イベントを簡単に送信できます。 * **システム全体の変更を管理するための包括的なビューを取得します。1**つの統合インターフェースから、すべてのエンティティとアカウントにわたる変更イベントをシームレスに表示およびフィルタリングします。チーム、タイプ、カスタムアトリビュート、その他の基準でフィルタリングすることで、変更を簡単に特定します。 diff --git a/src/i18n/content/jp/docs/new-relic-control/agent-control/configuration.mdx b/src/i18n/content/jp/docs/new-relic-control/agent-control/configuration.mdx index 8cd2cdc6bd6..f4ba3ad3d5c 100644 --- a/src/i18n/content/jp/docs/new-relic-control/agent-control/configuration.mdx +++ b/src/i18n/content/jp/docs/new-relic-control/agent-control/configuration.mdx @@ -306,21 +306,22 @@ Agent Control次の優先順位でプロキシ設定を使用します。 secretName: ca-certs # Configure Flux components to use proxy - flux2: - sourceController: - extraEnv: - # Configure Flux source-controller to proxy all requests - - name: HTTPS_PROXY - value: https://proxy-service:8080 - # Except for in-cluster requests - - name: "NO_PROXY" - value: ".cluster.local.,.cluster.local,cluster.local,.svc,127.0.0.0/8,10.0.0.0/8" - volumeMounts: - # Mount CA certificate bundle to source-controller trust root store. The bundle should contain the - # proxy CA cert. - - mountPath: /etc/ssl/certs/ - name: ca-certs - volumes: + agent-control-cd: + flux2: + sourceController: + extraEnv: + # Configure Flux source-controller to proxy all requests + - name: HTTPS_PROXY + value: https://proxy-service:8080 + # Except for in-cluster requests + - name: "NO_PROXY" + value: ".cluster.local.,.cluster.local,cluster.local,.svc,127.0.0.0/8,10.0.0.0/8" + volumeMounts: + # Mount CA certificate bundle to source-controller trust root store. The bundle should contain the + # proxy CA cert. + - mountPath: /etc/ssl/certs/ + name: ca-certs + volumes: - name: ca-certs secret: secretName: ca-certs @@ -338,20 +339,160 @@ Agent Control次の優先順位でプロキシ設定を使用します。 プロキシを使用する場合は、管理対象エージェントごとにプロキシ設定を個別に構成する必要があります。プロキシ設定オプションについては、各エージェントの固有のドキュメントを参照してください。 -## Private repository configuration +## 秘密管理 -Agent Control supports configuring private Helm repositories to deploy both Agent Control itself and the managed agents. This enables environments where the New Relic Helm charts are not directly accessible. +Agent Control provides a robust mechanism for managing sensitive data, such as passwords and API keys, by retrieving them from dedicated secret providers. This ensures that sensitive information is not hard-coded directly into configuration files. The system currently supports the following secret providers: + +* HashiCorp Vault: referred to as `nr-vault` in configurations. +* Kubernetes Secrets: referred to as `nr-kubesec` in configurations. + +### Defining Secrets in Configuration + +To utilize secrets, define them within your Agent-Control configuration YAML file by following these steps: + +1. **Define the `secrets_providers` section:** Configure your secret providers centrally in this section. Ensure each entry corresponds to a supported provider. +2. **Configure secret sources:** For each provider, specify one or more sources. A source includes the necessary configuration details (e.g., URL, token) for Agent control to connect to and retrieve a group of secrets. +3. **Use placeholders in agent configurations:** Instead of the actual sensitive data, Use a placeholder string within your agent's configuration. Agent control automatically replaces these placeholders with the retrieved secrets during the rendering process. + + + If Agent control fails to retrieve a secret, the configuration rendering will fail, and the agent will not be executed. This is a critical security feature to prevent agents from running with incomplete or incorrect configurations. + + +The following agent-control configuration example demonstrates how to configure for retrieving secrets from two Vault sources within the `secrets_providers` section: + +```yaml +secrets_providers: + vault: + sources: + local-instance: + url: http://localhost:8200/v1/ + token: root + engine: kv2 + remote: + url: http://my-remote-server:8200/v1/ + token: root + engine: kv1 + +fleet_control: + ... + +agents: + ... +``` + +#### Using Secrets in an Agent Configuration + +After the sources are defined, in an agent configuration, you can reference the vault using a specific placeholder syntax with the correct path. Agent control retrieves the secret and uses it to render the final configuration file that the agent is going to use. + +Example of agent configuration using vault placeholders: + +```yaml +config_agent: |+ + enable_process_metrics: true + custom_attributes: + username: "${nr-vault:local-instance:secret:my_secret:username}" + organization: "${nr-vault:remote:my_mount:my_path:organization}" +``` + +この例では + +The placeholder `${nr-vault:local-instance:secret:my_secret:username}` instructs Agent control to retrieve the value associated with the key username from the secret at the path `secret/my_secret` using the local-instance vault source. The placeholder `${nr-vault:remote:my_mount:my_path:organization}` similarly retrieves the value for the organization key from the remote source. + +After successful retrieval, Agent control renders these secrets from the specified source and path, storing the result in a K8s secret or private config file for use by the corresponding agent. + +### ヴォールトの秘密 + +Set up the vault sources with the following settings: + +
- [カスタム ロール]() - - セクションで作成されたカスタム ロール ID。 + カスタム ロール セクションで作成されたカスタム ロール ID。
- `PageViewTiming` イベントはすべてのエージェントによって収集され、コア Web バイタル測定値などのタイミング データが含まれます。最初の収集は、 `load` ページ ライフサイクル イベントの 10 秒後に行われます。追加の収集は、送信するデータがある場合に必要に応じて 30 秒ごとに行われます。報告されたイベントのリストについては、 [PageViewTiming ドキュメント](/docs/browser/new-relic-browser/page-load-timing-resources/pageviewtiming-async-or-dynamic-page-details/#interactivity-metrics) を参照してください。 + `PageViewTiming` イベントはすべてのエージェントによって収集され、コア ウェブ バイタル測定などのタイミング データが含まれます。最初の収集は、 `load`ページ ライフサイクル イベントの 10 秒後に行われます。送信するデータがある場合、または収集ペイロード サイズが 16 KB を超える場合は、必要に応じて 30 秒ごとに追加の収集が行われます。報告されるイベントのリストについては、 [PageViewTiming のドキュメントを](/docs/browser/new-relic-browser/page-load-timing-resources/pageviewtiming-async-or-dynamic-page-details/#interactivity-metrics)参照してください。
- `PageAction` イベントは `load` ページ ライフサイクル イベントの後に収集され、その後の収集は 30 秒ごとに行われます。 + `PageAction` イベントは、 `load`ページのライフサイクル イベントの後に収集されます。それ以降の収集は 30 秒ごとに行われるか、収集ペイロード サイズが 16 KB を超えている場合に行われます。
+ + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ YAMLキー + + 説明 +
+ `url` + + データを要求するURL +
+ `token` + + Used to authenticate to the endpoint. +
+ `engine` + + Specify **`kv1`** or **`kv2`**. +
+ +In the configuration file, each secret stored in Vault can be accessed by setting a placeholder with: + +* **source\_name**: The name of the Vault source defined in `secrets_providers`. +* **mount**: The name of the secrets engine mount. +* **path**: The specific path to the secret. +* **specific key**: The specific key within the secret to be retrieved. + +Example of full placeholder format: + +``` +"${nr-vault:source_name:my_mount:my_path:my_value}" +``` + +### Kubernetes secrets + +If the agent-control pod has permissions, such as through a Service Account and Role-Based Access Control (RBAC), to access the required secrets and namespaces, Agent control can directly access secrets from the Kubernetes API without needing a separate sources configuration. + +In the agent configuration file, retrieve each secret value using a placeholder specifying: + +* **namespace**: The Kubernetes namespace where the secret is located. +* **name**: The name of the Kubernetes secret object. +* **specific key**: The specific key within the secret from which to retrieve the value. + +For example, use the placeholder format: + +``` +"${nr-kubesec:my_namespace:my_secret:my_value}" +``` + +## プライベートリポジトリ設定 + +Agent Control は、Agent Control 自体と管理対象エージェントの両方をデプロイするためのプライベート Helm リポジトリの構成をサポートしています。これにより、New Relic Helm チャートに直接アクセスできない環境が可能になります。 - When using private Helm repositories, the charts need to be compatible and the referenced images within the charts must be reachable. If not, the agents will not work as expected. + プライベート Helm リポジトリを使用する場合、チャートは互換性があり、チャート内の参照イメージにアクセスできる必要があります。そうしないと、エージェントは期待どおりに動作しません。 -### 1. Enable private repositories for agents +### 1. エージェントのプライベートリポジトリを有効にする -For security reasons, only explicitly enabled repositories will be allowed in remote configurations. To enable specific repositories, you need to update the Agent Control configuration: +セキュリティ上の理由から、リモート設定では明示的に有効化されたリポジトリのみが許可されます。 特定のリポジトリを有効にするには、 Agent Control設定を更新する必要があります。 - + ```yaml # values-newrelic.yaml @@ -371,7 +512,7 @@ For security reasons, only explicitly enabled repositories will be allowed in re -The allowed repository configurations can then be used in your remote configurations within New Relic Control. Example: +許可されたリポジトリ設定は、 New Relic Control 内のリモート設定で使用できるようになります。 例： ```yaml chart_version: "1.2.3" @@ -380,19 +521,19 @@ chart_repository: name: "my-chart-name" # Optional: use only if the chart name doesn't match New Relic's chart name ``` -Additionally, you need to configure Agent Control's Helm installation to use your private repository if the `agent-control` chart itself is in a private repository. This is separate from the configuration for managed agents. Refer to the `agent-control` Helm chart [values.yaml](https://github.com/newrelic/helm-charts/blob/master/charts/agent-control/values.yaml) to set up the `installationJob` section. Specifically: +さらに、 `agent-control`チャート自体がプライベート リポジトリ内にある場合は、プライベート リポジトリを使用するようにAgent ControlのHelmを構成する必要があります。 マネージドエージェントの設定とは別のものです。 `installationJob`セクションを設定するには、 `agent-control` Helm チャート[values.yaml](https://github.com/newrelic/helm-charts/blob/master/charts/agent-control/values.yaml)を参照してください。具体的には： -* `chartRepositoryUrl` containing your repository URL -* `name` if using a different chart name -* `repositorySecretReferenceName` and `repositoryCertificateSecretReferenceName` for authentication (see the authentication section below for details) +* `chartRepositoryUrl` リポジトリのURLを含む +* `name` 別のチャート名を使用する場合 +* `repositorySecretReferenceName` 認証には`repositoryCertificateSecretReferenceName`使用します（詳細は以下の認証セクションを参照してください） -### 2. Set up authentication for private repositories +### 2. プライベートリポジトリの認証を設定する -You need to set up additional resources to enable authentication for accessing your private repository: +プライベート リポジトリにアクセスするための認証を有効にするには、追加のリソースを設定する必要があります。 - To authenticate using basic authentication (username and password), you need to create a secret in the Agent Control namespace containing the expected values in `data.username` and `data.password`. + 基本認証 (ユーザー名とパスワード) を使用して認証するには、 Agent Controlネームスペースに、 `data.username`および`data.password`の予想される値を含むシークレットを作成する必要があります。 例： @@ -406,9 +547,9 @@ You need to set up additional resources to enable authentication for accessing y password: "myPassword" ``` - For more details, see the [Flux documentation](https://fluxcd.io/flux/components/source/helmrepositories/#secret-reference). + 詳細については、 [Flux のドキュメント](https://fluxcd.io/flux/components/source/helmrepositories/#secret-reference)を参照してください。 - When using basic authentication, the remote configuration should be configured as follows: + 基本認証を使用する場合、リモート設定は次のように構成する必要があります。 ```yaml chart_repository: @@ -418,13 +559,13 @@ You need to set up additional resources to enable authentication for accessing y ``` - - To authenticate using TLS, you need to create a secret containing: + + TLS を使用して認証するには、次の内容を含むシークレットを作成する必要があります。 - * `tls.crt` and `tls.key`: client certificate and private key used for TLS client authentication - * `ca.crt`: CA certificate used to verify the server (required if the server uses a self-signed certificate) + * `tls.crt` および`tls.key` : TLSクライアント認証に使用されるクライアント証明書と秘密鍵 + * `ca.crt`: サーバーの検証に使用される CA 証明書 (サーバーが自己署名証明書を使用する場合に必要) - The Secret should be of type `Opaque` or `kubernetes.io/tls`. All files in the Secret are expected to be PEM-encoded. + Secret のタイプは`Opaque`または`kubernetes.io/tls`である必要があります。Secret 内のすべてのファイルは PEM でエンコードされている必要があります。 例： @@ -442,9 +583,9 @@ You need to set up additional resources to enable authentication for accessing y ca.crt: ``` - For more details, see the [Flux documentation](https://fluxcd.io/flux/components/source/helmrepositories/#secret-reference). + 詳細については、 [Flux のドキュメント](https://fluxcd.io/flux/components/source/helmrepositories/#secret-reference)を参照してください。 - When using TLS certificate authentication, the remote configuration should be configured as follows: + TLS 証明書認証を使用する場合、リモート設定は次のように構成する必要があります。 ```yaml chart_repository: diff --git a/src/i18n/content/jp/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx b/src/i18n/content/jp/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx index 2a9ef2ac83a..4cc20cbf721 100644 --- a/src/i18n/content/jp/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx +++ b/src/i18n/content/jp/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx @@ -280,7 +280,7 @@ mutation { pipelineCloudRuleEntity: { description: "Since we only care about MyEvent in staging and production, let's drop all MyEvent data in the test environment", name: "Drop MyEvent in test environment", - nrql: "DELETE FROM MyEvent where environment = 'test'", + nrql: "DELETE FROM MyEvent WHERE environment = 'test'", scope: { id: "your_nr_account_id", type: ACCOUNT @@ -304,7 +304,7 @@ mutation { pipelineCloudRuleEntity: { description: "We don't care about jvmId and targetAttr in the test environment, let's drop those attributes", name: "Drop jvmId and targetAttr from MyEvent in test environment", - nrql: "DELETE jvmId, targetAttr FROM MyEvent where environment = 'test'", + nrql: "DELETE jvmId, targetAttr FROM MyEvent WHERE environment = 'test'", scope: { id: "your_nr_account_id", type: ACCOUNT @@ -531,7 +531,7 @@ mutation { pipelineCloudRuleEntity: { description: "We don't care about targetAttr in the test environment in dimensional metric rolloups, let's drop those attributes", name: "Drop targetAttr from Metric aggregate rollups in test environment", - nrql: "DELETE targetAttr FROM MetricAggregate where environment = 'test'", + nrql: "DELETE targetAttr FROM MetricAggregate WHERE environment = 'test'", scope: { id: "your_nr_account_id", type: ACCOUNT diff --git a/src/i18n/content/jp/docs/new-relic-control/pipeline-control/data-dropping-gateway.mdx b/src/i18n/content/jp/docs/new-relic-control/pipeline-control/data-dropping-gateway.mdx index 419f3c4f8fa..fa44522a5f7 100644 --- a/src/i18n/content/jp/docs/new-relic-control/pipeline-control/data-dropping-gateway.mdx +++ b/src/i18n/content/jp/docs/new-relic-control/pipeline-control/data-dropping-gateway.mdx @@ -524,7 +524,7 @@ translationType: machine - `DELETE FROM SqlTrace WHERE uri = 'Custom\/Simple\/sqlTransaction'` + `DELETE FROM SqlTrace WHERE uri = 'Custom/Simple/sqlTransaction'` @@ -586,7 +586,7 @@ translationType: machine - `DELETE FROM TransactionTrace WHERE uri = 'Custom\/Simple\/sqlTransaction'` + `DELETE FROM TransactionTrace WHERE uri = 'Custom/Simple/sqlTransaction'` @@ -730,7 +730,7 @@ translationType: machine - `DELETE instanceType,inodesTotal NetworkSample WHERE entityKey = 'vagrant'` + `DELETE instanceType, inodesTotal NetworkSample WHERE entityKey = 'vagrant'` @@ -774,7 +774,7 @@ translationType: machine - `DELETE FROM ContainerSample WHERE agentName='ContainerSampleAgent'` + `DELETE FROM ContainerSample WHERE agentName = 'ContainerSampleAgent'` diff --git a/src/i18n/content/jp/docs/new-relic-control/pipeline-control/nrql-functions.mdx b/src/i18n/content/jp/docs/new-relic-control/pipeline-control/nrql-functions.mdx index 1fbda0e39c2..e76ac08e3ed 100644 --- a/src/i18n/content/jp/docs/new-relic-control/pipeline-control/nrql-functions.mdx +++ b/src/i18n/content/jp/docs/new-relic-control/pipeline-control/nrql-functions.mdx @@ -185,8 +185,8 @@ translationType: machine これらの例では、複数の関数を組み合わせて、より複雑なシナリオで使用し、正確なデータのフィルタリングと削除を実現する方法を示します。 -* `DELETE FROM ContainerSample WHERE state = 'exited' and status LIKE '%Exited%' and status NOT LIKE '%second%' and status not like '%About a minute ago%' and not (status like '%minute%' and numeric(aparse(status,'%Exited (%) * minutes ago%')) < 10)` +* `DELETE FROM ContainerSample WHERE state = 'exited' AND status LIKE '%Exited%' AND status NOT LIKE '%second%' AND status NOT LIKE '%About a minute ago%' AND NOT (status LIKE '%minute%' AND numeric(aparse(status,'%Exited (%) * minutes ago%')) < 10)` * `DELETE FROM Log, LogExtendedRecord WHERE dimensions() LIKE '%collectd%' AND newrelic.logs.customEventType IS NULL` -* `DELETE FROM Log WHERE message LIKE '%lib/ladon/middleware/caching.rb:49 run> terminated with exception%' and floor(timestamp/101) = (timestamp/101)` +* `DELETE FROM Log WHERE message LIKE '%lib/ladon/middleware/caching.rb:49 run> terminated with exception%' AND floor(timestamp/101) = (timestamp/101)` これらの新しい関数により、Pipeline Control ゲートウェイを操作する際の NRQL クエリの機能が大幅に拡張され、より正確なデータ分析と管理が可能になります。 \ No newline at end of file diff --git a/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx b/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx index f2adbb73ad9..41e13015edf 100644 --- a/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx +++ b/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx @@ -10,7 +10,7 @@ translationType: machine * [New Relic Browserエージェントの問題をデバッグする方法](/docs/browser/new-relic-browser/troubleshooting/how-to-debug-browser-agent/)に関する新しい機能が追加されました。これには、バージョン 1.285.0 以降で強化されたトラブルシューティングのための詳細なログ記録、ネットワーク リクエストの監視、検査イベントが含まれます。 * `python`および`.node.js`関数の監視に[Azure Functions の](/docs/serverless-function-monitoring/azure-function-monitoring/introduction-azure-monitoring/)サポートが追加されました。 * New Relicプラットフォームで非効率性を特定し、最適化の推奨事項を提供し、CCU 削減量を見積もる機能を備えた、計算効率を高めるための実用的なインサイト用の[コスト オプティマイザー](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/compute-optimizer/)を追加しました。 -* \[ Cloud Cost Intelligence ] を追加しました。これは、包括的なコストの内訳、 Kubernetesコストの割り当て、手動コストの見積もり、クロスアカウントのデータ収集などの機能を含む、 cloudコストの可視化と管理のためのツールを提供します。現在はAWSクラウド コストのみをサポートしています。 +* [Cloud Cost Intelligence](/docs/cci/getting-started/overview)を追加しました。 cloudコストの可視化と管理のためのツールを提供します。これには、包括的なコストの内訳、 Kubernetesコストの割り当て、手動コストの見積もり、クロスアカウント データ収集などの機能が含まれます。現在はAWSクラウド コストのみをサポートしています。 * [KubernetesにOpenTelemetryオブザーバNew Relic](/docs/kubernetes-pixie/k8s-otel/intro/)を追加し、 Helmチャートを介してクラスタをシームレスに監視するための New Relic 機能プロバイダーに依存しない統合を使用して、 New Relicのツールとダッシュボードに送信されるメトリクス、イベント、ログのテレメトリー信号を強化しました。 * [Windowsインテグレーションの制限とトラブルシューティング](/docs/kubernetes-pixie/kubernetes-integration/troubleshooting/troubleshooting-windows/)を追加 * [CloudFormation およびCloudWatch Metric Streams](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation/)を介したAWSインテグレーションが追加され、サポートされていないサービスのAPIポーリングがサポートされました。 diff --git a/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx b/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx new file mode 100644 index 00000000000..9e024f7adf7 --- /dev/null +++ b/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx @@ -0,0 +1,60 @@ +--- +subject: Docs +releaseDate: '2025-08-08' +version: 'August 01 - August 07, 2025' +translationType: machine +--- + +### 新しいドキュメント + +* [NerdGraph チュートリアル「チームのカスタム ロールの作成」が追加され、](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/compute-budgets/overview) New Relic NerdGraph API を使用してチームのカスタム ロールを作成および管理する方法が説明されました。 + +### マイナーチェンジ + +* [条件ごとの集中イベントの値を](/docs/alerts/admin/rules-limits-alerts)1 分あたり 1,000 に変更しました。 +* 最新の検証済み[.Net エージェント互換バージョンと要件](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements)を更新しました。 +* [VMware Tanzu](/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-service-broker-integration)のサービス ブローカーのバージョンおよびバージョン サポート情報を更新しました。 +* [VMware Tanzu](/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-nginx-buildpack-integration)用のNew Relic NGINX 統合ビルドパックに関するバージョン サポート情報を更新しました。 +* New Relic Nozzle for [VMware Tanzu](/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-firehose-nozzle-integration/#product-snapshot)のバージョンおよびバージョン サポート情報を更新しました。 + +### リリースノート + +* 新着情報投稿をご覧ください: + + * [Errors Inboxはワークロード内に統合されました](/whats-new/2025/08/whats-new-08-06-workloads-errors-inbox)。 + +* 弊社の最新リリース情報を常に把握してください: + + * [ジョブマネージャー v452](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-452) : + * キュー メッセージの処理における例外処理の内部的な改善を追加しました。 + + * [Kubernetesインテグレーション v3.43.3](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-43-3) : + * New Relic Kubernetes 監視ソリューションをデプロイするための Helm チャートを追加しました。 + + * [Pipeline Controlゲートウェイ v1.1.0](/docs/release-notes/pipeline-control-gateway-release-notes/pipeline-control-gateway-25-08-05) : + + * ドロップ ルールを使用して`SqlTrace`および`TransactionTrace`イベントからデータと属性を選択的にドロップする新しい機能を実装しました。 + + * クロスサイト スクリプトの問題や、IPv6 ゾーン ID に関連する HTTP プロキシ バイパスなど、 `golang.org/x/net`パッケージの脆弱性に対処しました。 + + * Go `1.24`にアップグレードされ、セキュリティを強化し、最近の修正を組み込むために次の依存関係が更新されました。 + + * `golang.org/x/net to v0.38.0` + * `golang.org/x/sys to v0.31.0` + * `golang.org/x/text to v0.23.0` + + * [iOS向けモバイルアプリv6.9.11](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6101) : + * ユーザーの認証ドメインを保存し、ユーザーをサインイン ページに直接リダイレクトすることで、ログイン フローを 2 ステップ削減しました。 + + * [Flutterエージェント v1.1.13](/docs/release-notes/mobile-release-notes/flutter-release-notes/flutter-agent-1113) : + + * ネイティブ Android エージェントがバージョン 7.6.8 にアップデートされました + * ネイティブ iOS エージェントがバージョン 7.5.8 にアップデートされました + + * [.NET MAUI エージェント v1.1.11](/docs/release-notes/mobile-release-notes/net-maui-release-notes/net-maui-agent-1111) + + * ネイティブ Android エージェントがバージョン 7.6.8 にアップデートされました + * ネイティブ iOS エージェントがバージョン 7.5.8 にアップデートされました + + * [インフラストラクチャエージェント v1.65.5](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1655) : + * ストレージサンプルのAWS efsマウントのサポートを変更しました \ No newline at end of file diff --git a/src/i18n/content/jp/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1655.mdx b/src/i18n/content/jp/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1655.mdx index 9eb3f0df919..2a43fb231c2 100644 --- a/src/i18n/content/jp/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1655.mdx +++ b/src/i18n/content/jp/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1655.mdx @@ -5,10 +5,19 @@ version: 1.65.5 translationType: machine --- + + **既知の問題**: このリリースには、NFSv4 マウントを持つ Linux ホスト上の NFSv4 マウント データを含む StorageSample が原因で、diskUsedPercent の計算に既知の問題があります。 + + +次のいずれかの代替案を検討してください。 + +* Use any version higher than `1.65.5` +* 以下のバージョンより低いものを使用してください `1.65.5` + エージェントの新しいバージョンがリリースされました。標準手順に従って[インフラストラクチャエージェントを更新します](https://docs.newrelic.com/docs/infrastructure/install-configure-manage-infrastructure/update-or-uninstall/update-infrastructure-agent)。 New Relic では、エージェントを定期的に、少なくとも 3 か月ごとにアップグレードすることを推奨しています。このリリースの時点で、サポートされている最も古いバージョンは[インフラストラクチャエージェント 1.51.0](https://docs.newrelic.com/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1510/)です。 ## かわった -* 機能: #2069 のストレージ サンプルで AWS EFS マウントをサポート +* feat: support AWS EFS mounts in storage samples in #2069 * chore(deps): golang.org/x/oauth2 をバンプします#2093 で 0.20.0 から 0.27.0 に変更 * chore(deps): #2094 で nri-prometheus のバージョンを v2.27.0 に更新しました \ No newline at end of file diff --git a/src/i18n/content/jp/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5306.mdx b/src/i18n/content/jp/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5306.mdx new file mode 100644 index 00000000000..d9a1c73504b --- /dev/null +++ b/src/i18n/content/jp/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5306.mdx @@ -0,0 +1,11 @@ +--- +subject: Mobile app for Android +releaseDate: '2025-08-07' +version: 5.30.6 +downloadLink: 'https://play.google.com/store/apps/details?id=com.newrelic.rpm' +translationType: machine +--- + +### 機能強化 + +* SAMLおよびソーシャルログインのパスキーサポート \ No newline at end of file diff --git a/src/i18n/content/jp/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx b/src/i18n/content/jp/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx new file mode 100644 index 00000000000..6e5b982a15b --- /dev/null +++ b/src/i18n/content/jp/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx @@ -0,0 +1,39 @@ +--- +subject: Browser agent +releaseDate: '2025-08-04' +version: 1.295.0 +downloadLink: 'https://www.npmjs.com/package/@newrelic/browser-agent' +features: + - Add error cause detection +bugs: + - Add monkey-patching warnings + - Calculate first and last timestamps from raw data +security: [] +translationType: machine +--- + +## v1.295.0 + +### 特徴 + +#### エラー原因検出を追加 + +キャプチャされた JavaScriptError イベントの原因属性を検出して報告します。原因がエラーのインスタンスである場合はスタックトレースがキャプチャされ、それ以外の場合は原因の文字列化された内容が報告されます。 これは、属性`cause`の下の JavaScriptError イベントでクエリ可能になります。 + +### バグ修正 + +#### モンキーパッチの警告を追加する + +エージェントがページで実行される前に、予期されるグローバルにモンキーパッチが適用された場合の検出と警告を追加しました。これにより予期しない動作が発生する可能性があり、この動作について顧客に通知することが目的です。 + +#### 生データから最初と最後のタイムスタンプを計算する + +UI リプレーヤーの一貫性を向上させるために、収集前にエージェントが SessionReplay ペイロードの最初と最後のタイムスタンプを手動で計算することを確認します。 + +## サポートステートメント + +New Relic では、最新の機能とパフォーマンス上のメリットを確実に得られるよう、エージェントを定期的にアップグレードすることをお勧めします。古いリリースは[サポート終了](https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/browser-agent-eol-policy/)になるとサポートされなくなります。リリース日は、エージェント バージョンの元の公開日を反映します。 + +新しいブラウザエージェントのリリースは、一定期間にわたって小さな段階で顧客に展開されます。 このため、リリースがアカウントでアクセス可能になる日付は、元の公開日と一致しない可能性があります。詳細については、この[ステータス ダッシュボード](https://newrelic.github.io/newrelic-browser-agent-release/)をご覧ください。 + +弊社の[ブラウザ サポート ポリシー](https://docs.newrelic.com/docs/browser/new-relic-browser/getting-started/compatibility-requirements-browser-monitoring/#browser-types)に従い、 Browserの v1.295.0 は、 Chrome 128 ～ 138、Edge 128 ～ 138、Safari 17 ～ 19、Firefox 130 ～ 140 のブラウザとバージョン範囲向けに構築され、テストされました。 モバイル デバイスの場合、v1.295.0 は Android OS 16 および iOS Safari 17-26 用に構築およびテストされました。 \ No newline at end of file diff --git a/src/i18n/content/jp/docs/service-architecture-intelligence/github-integration.mdx b/src/i18n/content/jp/docs/service-architecture-intelligence/github-integration.mdx index 8546f83f922..5779ced4102 100644 --- a/src/i18n/content/jp/docs/service-architecture-intelligence/github-integration.mdx +++ b/src/i18n/content/jp/docs/service-architecture-intelligence/github-integration.mdx @@ -53,10 +53,10 @@ New RelicGitHub インテグレーションは、GitHub アカウントからユ **New Relic Teamsへのリポジトリの割り当て** -GitHub で`teamOwningRepo`カスタム プロパティを作成すると、GitHub リポジトリをチームに自動的に割り当てることができます。 +GitHub でカスタム プロパティとして`teamOwningRepo`追加することで、GitHub リポジトリをチームに自動的に割り当てることができます。 1. 組織レベルでカスタム プロパティを作成し、リポジトリ レベルでカスタム プロパティの値を割り当てます。さらに、組織レベルで複数のリポジトリに対して同時にカスタム プロパティを設定することもできます。 -2. 次に、New Relic Teams で[自動所有権](/docs/service-architecture-intelligence/teams/manage-teams/#assign-ownership)機能を有効にし、 `teamOwningRepo`タグ キーとして使用するようにします。 +2. 次に、New Relic Teams で[自動所有権](/docs/service-architecture-intelligence/teams/manage-teams/#assign-ownership)機能を有効にし、 `team`タグ キーとして使用するようにします。 これを設定すると、各リポジトリが適切なチームに自動的にマッチングされます。 diff --git a/src/i18n/content/jp/docs/tutorial-improve-site-performance/guide-to-monitoring-core-web-vitals.mdx b/src/i18n/content/jp/docs/tutorial-improve-site-performance/guide-to-monitoring-core-web-vitals.mdx index 000d39f976d..9461ee848d9 100644 --- a/src/i18n/content/jp/docs/tutorial-improve-site-performance/guide-to-monitoring-core-web-vitals.mdx +++ b/src/i18n/content/jp/docs/tutorial-improve-site-performance/guide-to-monitoring-core-web-vitals.mdx @@ -1,30 +1,32 @@ --- -title: ウェブ上の重要な要素を監視する +title: Core Web Vitalsをモニタリングする tags: - Browser - Browser monitoring - Guides -metaDescription: A guide to monitor Google's core web vitals. +metaDescription: A guide to monitor Google's Core Web Vitals. freshnessValidatedDate: '2024-03-21T00:00:00.000Z' translationType: machine --- -コア ウェブ バイタルは、全体的なユーザー エクスペリエンスを評価する Google の指標です。これらは、ユーザーがあなたのビジネスをどのように見ているかについての貴重な洞察を提供し、サイトの SEO ランキングに影響を与える可能性があります。ユーザー エクスペリエンスを把握するスコアを取得することで、サイトが何を必要としているかを推測するのではなく、特定の問題に対してアクションを起こすことができます。 +Core Web Vitals (CWV) は、全体的なユーザー エクスペリエンスを測定する Google のメトリクスです。 これらは、ユーザーがあなたのビジネスをどのように見ているかについてインサイトに貴重な情報を提供し、サイトの SEO ランキングに影響を与える可能性があります。 ユーザーエクスペリエンスを捉えたスコアを取得することで、サイトに何が必要かを推測するのではなく、特定の問題に対して対策を講じることができます。 ## 目的 [#objectives] -このチュートリアルでは、New Relic を使用して Web の重要な要素を分析する方法を説明します。チュートリアルが終わるまでに、次のタスクが完了します。 +このチュートリアルでは、New Relic を使用して CWV を分解する方法について説明します。チュートリアルの最後には、次のタスクが完了します。 -* New Relicでコアウェブバイタルを見つけてください。 -* Web の重要な要素がサイトのパフォーマンスにどのように反映されるかを理解します。 +* New Relic で CWV を見つけます。 +* CWV がサイトのパフォーマンスにどのように反映されるかを理解します。 * New Relic データを調査して、スコアに寄与しているものを特定します。 -## コアウェブバイタルについて知る [#learn] +## CWVについて学ぶ [#learn] Google は、ウェブサイト全体のパフォーマンスを次の 3 つのメトリクスで測定します。 * [最大コンテンツフル ペイント](https://web.dev/articles/lcp)(LCP): ページのメイン コンテンツの読み込みにかかる時間。 たとえば、LCP が遅い Web ページにアクセスしたユーザーには、コンテンツが表示される前に数秒間空白の画面が表示されることがあります。 + * [インタラクションから次のペイントまで](https://web.dev/articles/inp)(INP): ページがユーザーのインタラクションに応答するまでにかかる時間。 たとえば、ユーザーがボタンをクリックした場合、INP はクリックしてから次のページが開くまでにかかる時間を測定します。 INP が高い場合は、Web ページのエクスペリエンスが遅く応答しないことを反映しており、ユーザー エンゲージメントが妨げられます。 + * [累積レイアウト シフト](https://web.dev/articles/cls)(CLS): 読み込み中にページ上で予期しないレイアウト シフトが発生する頻度。 たとえば、ユーザーがボタンをクリックしようとすると、コンテンツが画面上の新しい場所にジャンプしてしまい、誤って別のものをクリックしてしまう可能性があります。 CLS が高いと、Web ページがぎこちなく感じられ、操作が困難になることがあります。 各ウェブ バイタルには、アプリのパフォーマンスと SEO を追跡するのに役立つ次のしきい値があります。 @@ -32,7 +34,7 @@ Google は、ウェブサイト全体のパフォーマンスを次の 3 つの - @@ -586,7 +586,7 @@ translationType: machine @@ -730,7 +730,7 @@ translationType: machine @@ -774,7 +774,7 @@ translationType: machine diff --git a/src/i18n/content/kr/docs/new-relic-control/pipeline-control/nrql-functions.mdx b/src/i18n/content/kr/docs/new-relic-control/pipeline-control/nrql-functions.mdx index e8aef4da5f8..f2ecea8d08f 100644 --- a/src/i18n/content/kr/docs/new-relic-control/pipeline-control/nrql-functions.mdx +++ b/src/i18n/content/kr/docs/new-relic-control/pipeline-control/nrql-functions.mdx @@ -185,8 +185,8 @@ translationType: machine 이러한 예제는 여러 기능을 결합하고 이를 보다 복잡한 시나리오에서 사용하여 정확한 데이터 필터링 및 삭제를 달성하는 방법을 보여줍니다. -* `DELETE FROM ContainerSample WHERE state = 'exited' and status LIKE '%Exited%' and status NOT LIKE '%second%' and status not like '%About a minute ago%' and not (status like '%minute%' and numeric(aparse(status,'%Exited (%) * minutes ago%')) < 10)` +* `DELETE FROM ContainerSample WHERE state = 'exited' AND status LIKE '%Exited%' AND status NOT LIKE '%second%' AND status NOT LIKE '%About a minute ago%' AND NOT (status LIKE '%minute%' AND numeric(aparse(status,'%Exited (%) * minutes ago%')) < 10)` * `DELETE FROM Log, LogExtendedRecord WHERE dimensions() LIKE '%collectd%' AND newrelic.logs.customEventType IS NULL` -* `DELETE FROM Log WHERE message LIKE '%lib/ladon/middleware/caching.rb:49 run> terminated with exception%' and floor(timestamp/101) = (timestamp/101)` +* `DELETE FROM Log WHERE message LIKE '%lib/ladon/middleware/caching.rb:49 run> terminated with exception%' AND floor(timestamp/101) = (timestamp/101)` 이러한 새로운 기능은 분산 컨덕턴스 게이트웨이를 사용할 때 NRQL 쿼리의 기능을 크게 확장하여 보다 정확한 데이터 분석 및 관리가 가능합니다. \ No newline at end of file diff --git a/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx b/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx index 486d10790b5..b128a998800 100644 --- a/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx +++ b/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx @@ -10,7 +10,7 @@ translationType: machine * 에이전트 버전 1.285.0 이상에서 향상된 문제 해결을 위한 세부 로깅, 네트워크 요청 모니터링, 검사 이벤트를 포함하여 [뉴렐릭 브라우저 에이전트 문제를 디버깅하는 방법](/docs/browser/new-relic-browser/troubleshooting/how-to-debug-browser-agent/) 에 대한 새로운 기능이 추가되었습니다. * `python` 및 `.node.js` 함수 모니터링에 대한 [Azure Functions](/docs/serverless-function-monitoring/azure-function-monitoring/introduction-azure-monitoring/) 지원이 추가되었습니다. * 뉴렐릭 플랫폼에서 비효율성을 식별하고, 최적화 권장 사항을 제공하고, CCU 절감액을 추정하는 기능을 통해 컴퓨트 효율성을 향상시키기 위해 실행 가능한 인사이트를 위한 [비용 최적화 기능](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/compute-optimizer/) 을 추가했습니다. -* Added [Cloud Cost Intelligence](/docs/cci/getting-started/overview), offering tools for visibility and management of cloud costs, including features such as comprehensive cost breakdowns, Kubernetes cost allocation, real-time cost estimation, and cross-account data collection, currently supporting only AWS cloud costs. +* [클라우드 비용 인텔리전스](/docs/cci/getting-started/overview) 가 추가되어 포괄적인 비용 분석, Kubernetes 비용 할당, 미래 비용 추정, 계정 간 데이터 수집 등의 기능을 포함하여 cloud 비용의 가시성과 관리를 위한 도구를 제공하며 현재는 AWS 클라우드 비용만 지원합니다. * Helm 차트를 통한 클러스터의 원활한 모니터링을 위해 [뉴렐릭 기능 제공자 독립적 통합이 포함된 Kubernetes 용OpenTelemetry 옵저버빌리티가](/docs/kubernetes-pixie/k8s-otel/intro/) 추가되었으며, 메트릭, 이벤트에 대한 텔메트리 신호가 향상되고 뉴렐릭 도구와 대시보드로 전송됩니다. * [Windows 통합에 대한 제한 사항 및 문제 해결, 해결](/docs/kubernetes-pixie/kubernetes-integration/troubleshooting/troubleshooting-windows/)추가 * [CloudFormation 및 CloudWatch Metric Streams를](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation/) 통해 AWS 통합을 추가하여 지원되지 않는 서비스에 대한 API 폴링을 지원합니다. diff --git a/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx b/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx new file mode 100644 index 00000000000..8223f140d0d --- /dev/null +++ b/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx @@ -0,0 +1,60 @@ +--- +subject: Docs +releaseDate: '2025-08-08' +version: 'August 01 - August 07, 2025' +translationType: machine +--- + +### 새로운 문서 + +* [NerdGraph 튜토리얼을 추가했습니다: Teams에 대한 사용자 지정 역할 만들기는](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/compute-budgets/overview) NerdGraph API 사용하여 Teams에 대한 사용자 지정 역할을 만들고 관리하는 방법을 안내합니다. + +### 사소한 변경 사항 + +* [조건별 알림 이벤트를 분당 1,000개로](/docs/alerts/admin/rules-limits-alerts) 변경했습니다. +* 최신 검증된 [.Net 에이전트 호환 버전과 요구 사항을](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements) 업데이트했습니다. +* [VMware Tanzu](/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-service-broker-integration) 의 서비스 브로커에 대한 버전 및 버전 지원 정보가 업데이트되었습니다. +* [VMware Tanzu](/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-nginx-buildpack-integration) 용 뉴렐릭 NGINX 통합 빌드팩에 대한 버전 지원 정보를 업데이트했습니다. +* [VMware Tanzu](/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-firehose-nozzle-integration/#product-snapshot) 용 뉴렐릭 Nozzle에 대한 버전 및 버전 지원 정보를 업데이트했습니다. + +### 릴리즈 정보 + +* 새로운 소식 게시물을 확인하세요. + + * [의 인박스(errors inbox)가 이제 워크로드 내에 통합되었습니다](/whats-new/2025/08/whats-new-08-06-workloads-errors-inbox). + +* 최신 릴리스에 대한 최신 정보를 받아보세요. + + * [작업 관리자 v452](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-452): + * 대기열 메시지 처리 시 예외 처리를 위한 내부 개선 사항이 추가되었습니다. + + * [Kubernetes 통합 v3.43.3](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-43-3): + * 뉴렐릭 Kubernetes 모니터링 솔루션을 구현하고 배포하기 위해 Helm 차트를 추가했습니다. + + * [파이프라인 컨트롤 게이트웨이 v1.1.0](/docs/release-notes/pipeline-control-gateway-release-notes/pipeline-control-gateway-25-08-05): + + * 삭제 규칙을 사용하여 `SqlTrace` 및 `TransactionTrace` 이벤트에서 데이터와 속성을 선택적으로 삭제하는 새로운 기능을 구현했습니다. + + * IPv6 영역 ID와 관련된 HTTP 프록시 우회 및 사이트 간 스프레드시트 문제를 포함하여 `golang.org/x/net` 패키지의 취약점을 해결했습니다. + + * Go `1.24` 로 업그레이드되었으며 다음 의존성/종속성이 보안을 강화하고 최근 수정 사항을 통합하도록 업데이트되었습니다. + + * `golang.org/x/net to v0.38.0` + * `golang.org/x/sys to v0.31.0` + * `golang.org/x/text to v0.23.0` + + * [iOS v6.9.11용 모바일 앱](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6101): + * 사용자의 인증 도메인을 저장하고 사용자를 로그인 페이지로 직접 리디렉션하여 로그인 흐름을 두 단계로 줄였습니다. + + * [플러터 에이전트 v1.1.13](/docs/release-notes/mobile-release-notes/flutter-release-notes/flutter-agent-1113): + + * 개선된 네이티브 Android 에이전트가 버전 7.6.8로 업데이트되었습니다. + * 향상된 네이티브 iOS 에이전트가 버전 7.5.8로 업데이트되었습니다. + + * [.NET MAUI 에이전트 v1.1.11](/docs/release-notes/mobile-release-notes/net-maui-release-notes/net-maui-agent-1111) + + * 개선된 네이티브 Android 에이전트가 버전 7.6.8로 업데이트되었습니다. + * 향상된 네이티브 iOS 에이전트가 버전 7.5.8로 업데이트되었습니다. + + * [인프라 에이전트 v1.65.5](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1655): + * 저장소 샘플에서 지원 AWS EFS 마운트를 변경했습니다. \ No newline at end of file diff --git a/src/i18n/content/kr/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1655.mdx b/src/i18n/content/kr/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1655.mdx index 0e8ad92b164..e2babb7d46d 100644 --- a/src/i18n/content/kr/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1655.mdx +++ b/src/i18n/content/kr/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1655.mdx @@ -6,17 +6,18 @@ translationType: machine --- - **Known issues**: this release has a known issue with diskUsedPercent calculation because of StorageSample containing NFSv4 mount data on Linux hosts having NFSv4 mounts. + **알려진 문제**: 이 릴리스에는 NFSv4 마운트가 있는 Linux 호스트에서 NFSv4 마운트 데이터가 포함된 StorageSample로 인해 diskUsedPercent 계산에 알려진 문제가 있습니다. 다음 대안 중 하나를 고려해 보세요. +* Use any version higher than `1.65.5` * 다음 버전보다 낮은 버전을 사용하세요. `1.65.5` 에이전트의 새로운 버전이 출시되었습니다. [인프라 에이전트를 업데이트](https://docs.newrelic.com/docs/infrastructure/install-configure-manage-infrastructure/update-or-uninstall/update-infrastructure-agent) 하려면 표준 절차를 따르세요. 뉴렐릭은 에이전트를 정기적으로, 그리고 최소 3개월마다 업그레이드할 것을 권장합니다. 이번 릴리스부터 지원되는 가장 오래된 버전은 [안드로이드 에이전트 1.51.0](https://docs.newrelic.com/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1510/) 입니다. ## 변경됨 -* 기능: #2069의 저장소 샘플에서 AWS EFS 마운트 지원 +* feat: support AWS EFS mounts in storage samples in #2069 * chore(deps): 범프 golang.org/x/oauth2 #2093에서 0.20.0에서 0.27.0으로 * chore(deps): #2094에서 nri-prometheus 버전을 v2.27.0으로 업데이트 \ No newline at end of file diff --git a/src/i18n/content/kr/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5306.mdx b/src/i18n/content/kr/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5306.mdx new file mode 100644 index 00000000000..8f9d0ed4b27 --- /dev/null +++ b/src/i18n/content/kr/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5306.mdx @@ -0,0 +1,11 @@ +--- +subject: Mobile app for Android +releaseDate: '2025-08-07' +version: 5.30.6 +downloadLink: 'https://play.google.com/store/apps/details?id=com.newrelic.rpm' +translationType: machine +--- + +### 개선 사항 + +* SAML 및 소셜 로그인에 대한 Passkey 지원 \ No newline at end of file diff --git a/src/i18n/content/kr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx b/src/i18n/content/kr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx new file mode 100644 index 00000000000..d2e754e3a25 --- /dev/null +++ b/src/i18n/content/kr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx @@ -0,0 +1,39 @@ +--- +subject: Browser agent +releaseDate: '2025-08-04' +version: 1.295.0 +downloadLink: 'https://www.npmjs.com/package/@newrelic/browser-agent' +features: + - Add error cause detection +bugs: + - Add monkey-patching warnings + - Calculate first and last timestamps from raw data +security: [] +translationType: machine +--- + +## v1.295.0 + +### 특징 + +#### 오류 원인 감지 추가 + +캡처된 JavaScriptError 이벤트에서 원인 속성을 감지하고 보고합니다. 원인이 오류의 인스턴스인 경우 스택 추적이 캡처되고, 그렇지 않은 경우 원인의 문자열화된 내용이 보고됩니다. 이는 `cause` 속성 아래의 JavaScriptError 이벤트에서 쿼리될 수 있습니다. + +### 버그 수정 + +#### 몽키 패칭 경고 추가 + +에이전트가 페이지에서 실행되기 전에 예상되는 글로벌 변수에 몽키 패치가 적용된 경우 감지 및 경고가 추가되었습니다. 이로 인해 예상치 못한 동작이 발생할 수 있으며, 고객에게 이러한 동작에 대해 알리는 것이 목적입니다. + +#### 원시 데이터에서 첫 번째 및 마지막 타임스탬프 계산 + +UI 리플레이어의 일관성을 개선하기 위해 수집하기 전에 에이전트가 SessionReplay 페이로드의 첫 번째 및 마지막 타임스탬프를 수동으로 계산하도록 합니다. + +## 지지 성명 + +뉴렐릭은 에이전트를 정기적으로 업그레이드하여 최신 기능과 성능 이점을 얻을 것을 권장합니다. 이전 릴리스는 지원 [종료](https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/browser-agent-eol-policy/) 시점부터 더 이상 지원되지 않습니다. 출시일은 에이전트 버전의 원래 출판일을 반영합니다. + +새로운 브라우저 에이전트 릴리스는 일정 기간 동안 작은 단계로 고객에게 출시됩니다. 이로 인해, 귀하의 계정에서 해당 릴리스에 접근할 수 있는 날짜가 원래 게시 날짜와 일치하지 않을 수 있습니다. 자세한 내용은 이 [상태 대시보드를](https://newrelic.github.io/newrelic-browser-agent-release/) 참조하세요. + +[브라우저 지원 정책](https://docs.newrelic.com/docs/browser/new-relic-browser/getting-started/compatibility-requirements-browser-monitoring/#browser-types) 에 따라, 브라우저 에이전트 v1.295.0은 다음 브라우저 및 버전 범위에 맞춰 빌드되고 테스트되었습니다: Chrome 128-138, Edge 128-138, Safari 17-19, Firefox 130-140. 모바일 장치의 경우 v1.295.0은 Android OS 16 및 iOS Safari 17-26용으로 구축 및 테스트되었습니다. \ No newline at end of file diff --git a/src/i18n/content/kr/docs/service-architecture-intelligence/github-integration.mdx b/src/i18n/content/kr/docs/service-architecture-intelligence/github-integration.mdx index 71b1b7f7463..3274627673b 100644 --- a/src/i18n/content/kr/docs/service-architecture-intelligence/github-integration.mdx +++ b/src/i18n/content/kr/docs/service-architecture-intelligence/github-integration.mdx @@ -53,7 +53,7 @@ translationType: machine **뉴렐릭 Teams에 구성원 할당** -GitHub에서 `teamOwningRepo` 사용자 정의 속성을 만들어 GitHub 저장소를 해당 팀에 자동으로 할당할 수 있습니다. +GitHub에서 `teamOwningRepo` 사용자 정의 속성으로 추가하여 GitHub 저장소를 해당 팀에 자동으로 할당할 수 있습니다. 1. 조직 수준에서 사용자 정의 속성을 만들고 저장소 수준에서 사용자 정의 속성에 대한 값을 할당합니다. 또한, 조직 수준에서 여러 저장소에 대한 사용자 정의 속성을 동시에 설정할 수 있습니다. 2. 그런 다음 뉴렐릭 Teams에서 [자동 소유권](/docs/service-architecture-intelligence/teams/manage-teams/#assign-ownership) 기능을 활성화하고 태그 키로 `team` 사용해야 합니다. diff --git a/src/i18n/content/kr/docs/tutorial-improve-site-performance/guide-to-monitoring-core-web-vitals.mdx b/src/i18n/content/kr/docs/tutorial-improve-site-performance/guide-to-monitoring-core-web-vitals.mdx index e5f2e8fba0a..20b907a58ab 100644 --- a/src/i18n/content/kr/docs/tutorial-improve-site-performance/guide-to-monitoring-core-web-vitals.mdx +++ b/src/i18n/content/kr/docs/tutorial-improve-site-performance/guide-to-monitoring-core-web-vitals.mdx @@ -1,30 +1,32 @@ --- -title: 핵심 웹 바이탈 모니터링 +title: Core Web Vitals모니터링 tags: - Browser - Browser monitoring - Guides -metaDescription: A guide to monitor Google's core web vitals. +metaDescription: A guide to monitor Google's Core Web Vitals. freshnessValidatedDate: '2024-03-21T00:00:00.000Z' translationType: machine --- -핵심 웹 바이탈은 전반적인 사용자 경험을 측정하는 Google의 측정항목입니다. 사용자가 귀하의 비즈니스를 보는 방식에 대한 귀중한 통찰력을 제공하여 사이트의 SEO 순위에 영향을 줄 수 있습니다. 사용자 경험을 포착하는 점수를 가지면 사이트에 필요한 것이 무엇인지 추측하는 대신 특정 문제에 대해 조치를 취할 수 있습니다. +CWV( Core Web Vitals )는 전반적인 사용자 환경을 평가하는 Google의 지수입니다. 이들은 사용자가 귀하의 사업을 어떻게 보는지에 대한 귀중한 정보를 제공하며, 이는 귀하 사이트의 SEO 순위에 영향을 미칠 수 있습니다. 사용자 경험을 포착하는 점수를 통해 사이트에 필요한 것이 무엇인지 추측하는 대신 구체적인 문제에 대한 조치를 취할 수 있습니다. ## 목표 [#objectives] -이 튜토리얼은 New Relic을 사용하여 핵심 웹 바이탈을 분석하는 과정을 안내합니다. 자습서가 끝나면 다음 작업을 완료하게 됩니다. +이 튜토리얼에서는 뉴렐릭을 사용하여 CWV를 분석하는 방법을 안내합니다. 튜토리얼을 마치면 다음 작업이 완료됩니다. -* 뉴렐릭에서 코어 웹 바이탈을 찾아보세요. -* 핵심 웹 바이탈이 사이트 성능으로 변환되는 방식을 이해합니다. +* 뉴렐릭에서 CWV를 찾아보세요. +* CWV가 사이트 성능에 어떻게 반영되는지 알아보세요. * 뉴렐릭 데이터를 탐색하여 점수에 기여하는 요소를 파악하세요. -## 코어 웹 바이탈에 대해 알아보세요 [#learn] +## CWV에 대해 알아보세요 [#learn] Google은 다음 세 가지 지표를 기준으로 전반적인 웹사이트 성능을 측정합니다. * [콘텐츠가 포함된 최대 페인트](https://web.dev/articles/lcp) (LCP): 페이지의 기본 콘텐츠를 로드하는 데 걸리는 시간입니다. 예를 들어, 느린 LCP가 있는 웹페이지를 방문하는 사용자에게는 콘텐츠가 나타나기 전에 몇 초 동안 빈 화면이 나타날 수 있습니다. + * INP( [다음 페인트로의 복합복합](https://web.dev/articles/inp) ): 사용자의 복합복합에 페이지가 반응하는 데 걸리는 시간입니다. 예를 들어, 사용자가 버튼을 클릭하면 INP는 클릭 후 다음 페이지가 열리는 데 걸리는 시간을 측정합니다. 높은 INP는 느리고 응답하지 않는 웹페이지 경험을 반영하여 사용자 참여를 방해합니다. + * CLS( [누적 레이아웃 변경](https://web.dev/articles/cls) ): 로드하는 동안 페이지에서 예기치 않은 레이아웃 변경이 발생하는 빈도입니다. 예를 들어, 버튼을 클릭하려는 사용자는 콘텐츠가 화면의 새로운 위치로 이동하여 실수로 다른 항목을 클릭하게 될 수 있습니다. CLS가 높으면 웹페이지가 투박하고 상호작용하기 어렵게 느껴질 수 있습니다. 각 웹 바이탈에는 앱의 성능과 SEO를 추적하는 데 도움이 되는 다음과 같은 임계값이 있습니다. @@ -32,7 +34,7 @@ Google은 다음 세 가지 지표를 기준으로 전반적인 웹사이트 성
+ 良い @@ -114,7 +116,7 @@ Google は、ウェブサイト全体のパフォーマンスを次の 3 つの ### CLS スコアはどのように計算されますか? - 累積レイアウト シフト スコアは 0 から無限大までの単位のない値であり、他のコアウェブバイタルのような時間ベースの測定ではありません。 これは、Web ページの読み込みプロセス中に発生する予期しないレイアウトの変更の影響の合計を反映しています。 CLS スコアの計算方法は次のとおりです。 + 累積レイアウトシフトスコアは、他の CWV のような時間ベースの測定値ではなく、0 から無限大までの単位のない値です。これは、Web ページの読み込みプロセス中に発生する予期しないレイアウトシフトの影響の合計を反映します。CLS スコアの計算方法は次のとおりです。 * レイアウト シフト スコア: これは 2 つの要素を考慮します。 @@ -126,13 +128,13 @@ Google は、ウェブサイト全体のパフォーマンスを次の 3 つの **Good** Web Vitals は、組織のコスト削減と SEO の向上に役立ちます。 **Poor**または**Needs improvement** 、組織に対するユーザーの否定的な認識を反映している可能性があり、顧客の不満やビジネス チャンスの損失につながる可能性があります。 -New Relic は、Google の[`web-vitals` API ライブラリ](https://github.com/GoogleChrome/web-vitals)を活用して、追加の計算を行うことなく、生の状態で Web バイタルを収集します。 コアウェブバイタルが重要な理由とその計算方法の詳細については、web.dev の記事[「ユーザー中心のパフォーマンス メトリクス」を](https://web.dev/articles/user-centric-performance-metrics)参照してください。 +New Relic は、Google の[`web-vitals` API ライブラリ](https://github.com/GoogleChrome/web-vitals)を活用して、追加の計算を導入することなく、生の状態で Web Vitals を収集します。CWV が重要な理由とその計算方法の詳細については、web.dev の記事[「ユーザー中心のパフォーマンス メトリクス」を](https://web.dev/articles/user-centric-performance-metrics)参照してください。 -## New Relic で Web の重要な要素を見つける [#view-data-in-nr] +## New RelicでCWVを見つける [#view-data-in-nr] -コアウェブバイタルは多くのNew Relic機能に組み込まれていますが、Web バイタルを高レベルで表示する最良の方法は次のとおりです。 +CWV は多くの New Relic 機能に組み込まれていますが、Web Vitals を高レベルで表示する最適な方法は次のとおりです。 -1. **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Browser**に移動します。 +1. **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Browser**に移動します。 2. アプリを選択します。 @@ -140,153 +142,56 @@ New Relic は、Google の[`web-vitals` API ライブラリ](https://github.com/ **Web Vitals**ページには、Web サイト全体の Web Vital の平均が表示されます。 このビューから、特定のページまたはメトリクスにドリルダウンして、何がスコアに影響を与えているかを確認できます。 - overview of the web vitals page + overview of the web vitals page ### 特定のページにドリルダウンする [#drill-down] -インサイトを重要なページ (e コマースのチェックアウト ページなど) に含める場合は、 **Page URL**テーブルで見つけます。 コアウェブバイタルに寄与しているものの詳細が表示され、エンドユーザーがサイトのこれらの領域をどのように体験しているかを理解するために使用できます。 たとえば、Chrome ブラウザのパフォーマンス低下のパターンに気付いた場合は、そのユーザー ベースに対する今後の改善策を厳選できます。 +インサイトを重要なページ (e コマースのチェックアウト ページなど) に含める場合は、 **Page URL**テーブルで見つけます。 CWV に寄与している要因の内訳が表示され、これを使用して、エンドユーザーがサイトのその領域をどのように体験しているかを理解できます。たとえば、Chrome ブラウザのパフォーマンスが低いというパターンに気付いた場合は、そのユーザーベースに対する今後の改善策を策定できます。 -Click on a page URL to see page-specific web vitals. +Click on a page URL to see page-specific web vitals.
- **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Browser > (select an app) > Monitor > Web vitals > (click on a page URL)**: 最も影響力のある Web ページのコアバイウェブタルの内訳を表示します。 + **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Browser > (select an app) > Monitor > Web vitals > (click a page URL)**: 最も影響力のある Web ページの CWV の内訳を表示します。
### 主要な属性によるフィルタリング [#key-attributes] -バックエンドの変更やパフォーマンスの問題がコアウェブバイタルにどのような影響を与えたかなど、特定のことを調査したい場合は、 **Filter by**ツールを使用して主要な属性をフィルタリングできます。 +バックエンドの変更やパフォーマンスの問題が CWV にどのような影響を与えたかなど、特定の事柄を調査したい場合は、 **Filter by**ツールを使用して任意のキー属性をフィルタリングできます。 -Filter by key attributes +Filter by key attributes
- **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Browser > (select an app) > Monitor > Web vitals > (add filters)**: フィルタ ツールを使用して、主要な属性によってコアウェブバイタルをフィルタリングします。 + **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Browser > (select an app) > Monitor > Web vitals > (add filters)**: フィルタ ツールを使用して、主要な属性によってコアウェブバイタルをフィルタリングします。
ほぼすべてのキー属性でフィルタリングできますが、役に立つ例をいくつか読んでください。 - - デスクトップとモバイルのパフォーマンスを比較し、コアウェブバイタルが 2 つのプラットフォームでどのように異なるかを比較したいとします。 **Web vitals**でこれを調査するには: - - 1. - **Filter by** - - - フィールドで、 - - - **Attribute** - - - `deviceType`に、 - - - **Value** - - - `desktop`に設定します。 + + デスクトップとモバイルのパフォーマンスを比較し、2 つのプラットフォーム間で CWV がどのように異なるかを調べたいとします。**Web vitals**でこれを調査するには: - 2. 重複したbrowserで、 - - - **Attribute** - - - を `deviceType` に、 - - - **Value** - - - を `mobile` に設定し、結果を比較します。 + 1. **Filter by**フィールドで、 **Attribute** `deviceType`に、 **Value** `desktop`に設定します。 + 2. 重複したbrowserで、**Attribute** を `deviceType` に、**Value** を `mobile` に設定し、結果を比較します。 - + 11 月 1 日の午後 12 時ごろ、エンドユーザーがサイトのチェックアウト ページでパフォーマンスの問題を報告したとします。このユーザーに何が起こったのかを確認したいとします。 **Web vitals**でこれを調査するには: 1. 時間範囲を 11 月 1 日の午前 11 時から午後 1 時までに設定します。 + 2. **Page URL**テーブルで、チェックアウト ページの URL をクリックします。 + 3. **Filter by**フィールドで、 **Attribute** `userID`に、 **Value** `user ID`に設定します。 - 2. - **Page URL** - - - テーブルで、チェックアウト ページの URL をクリックします。 - - 3. - **Filter by** - - - フィールドで、 - - - **Attribute** - - - `userID`に、 - - - **Value** - - - `user ID`に設定します。 - - - `userID` は、 [ブラウザの SPA API](/docs/browser/new-relic-browser/browser-agent-spa-api/setcustomattribute-browser-agent-api/)を使用して設定する必要があるカスタム属性です。`userID`が利用できない場合は、 `username`や`session`などの他のユーザー情報でフィルタリングすることもできます。 - + + `userID` は、 [ブラウザの SPA API](/docs/browser/new-relic-browser/browser-agent-spa-api/setcustomattribute-browser-agent-api/)を使用して設定する必要があるカスタム属性です。`userID`が利用できない場合は、 `username`や`session`などの他のユーザー情報でフィルタリングすることもできます。 + - - たとえば、あなたの組織が最近、11 月 10 日午前 8 時にサイトのホームページの画像を更新し、その変更がコアウェブバイタルに影響を与えたかどうかを確認したいとします。 **Web vitals**でこれを調査するには: + + 組織が最近 11 月 10 日午前 8 時にサイトのホームページの画像を更新し、その変更が CWV に影響したかどうかを確認したいとします。**Web vitals**でこれを調査するには: 1. 時間範囲を 11 月 10 日の午前 7 時から午前 9 時までに設定します。 - - 2. - **Page URL** - - - テーブルで、ホームページ URL をクリックします。 - - 3. - **Filter by** - - - フィールドで、 - - - **Attribute** - - - `elementTagName`に、 - - - **Value** - - - `IMG`に設定します。 + 2. **Page URL**テーブルで、ホームページの URL をクリックします。 + 3. **Filter by**フィールドで、 **Attribute** `elementTagName`に、 **Value** `IMG`に設定します。 @@ -294,43 +199,32 @@ New Relic は、Google の[`web-vitals` API ライブラリ](https://github.com/ New Relic は、特定のページ上のユーザーのセッションに関するデータをキャプチャします。セッション トレースはランダムにサンプリングされ、ユーザーがページ読み込みタイミングの問題、JavaScript イベント、その他のエラーをどのように経験したかを確認できます。 -Session traces in Browser UI lets you look at real user sessions for a given page +Session traces in Browser UI lets you look at real user sessions for a given page -セッション トレースを使用して、さまざまなユーザー セッションにわたるパターンを見つけることをお勧めします。コアの Web Vitals スコアの 1 つを改善できる場合、オプションの 1 つは、セッション トレースを調べて、さまざまなユーザー セッション間でどのような共通属性が共有されているかを確認することです。セッション トレースがサイトの改善にどのように役立つかを示す例を次に示します。 +セッショントレースを使用して、さまざまなユーザー セッション全体のパターンを見つけることをお勧めします。 CWV スコアの 1 つを改善できる場合、オプションの 1 つは、セッション レースを調べて、さまざまなユーザー セッション間でどのような共通のプロパティが共有されているかを確認することです。 ここでは、セッショントレースがサイトの改善にどのように役立つかを示す例を示します。 -1. - **Web vitals** - +1. **Web vitals**タブで、パフォーマンスが低下しているページをクリックします。 上の画像を例として使用すると、サイトの全体的な LCP スコアは良好ですが、個々のページの一部には改善が必要であることがわかります。 +2. **Web vitals**ページの**Page URLs**セクションを見ると、ホームページ URL の LCP スコアが 4 秒を超えていることがわかります。 これはすべてのユーザーに影響するエラーによるものですか、それとも 1 種類のユーザーのみに影響するものですか? たとえば、特定のバージョンの Chrome または特定の OS を使用しているユーザーでページロードタイムが遅いことに気付いた場合、問題の特定の原因をより適切にトラブルシューティングできます。 +3. トラブルシューティングする URL をクリックすると、新しいウィンドウが表示されます。 LCP スコアがサイト全体の LCP スコアよりもはるかに高いことに気づきました。 このページの下部にある**Session traces**セクションまでスクロールすると、実際のユーザー セッションのさまざまなサンプルが表示されます。 これらのセッションでは、ユーザーが AJAX リクエスト、DOM 読み込みに関連する問題、JavaScript イベント、またはその他のエラーをどのように経験したかについて、より詳細な情報を得ることができます。 - タブで、パフォーマンスが低下しているページをクリックします。 上の画像を例として使用すると、サイトの全体的な LCP スコアは良好ですが、個々のページの一部には改善が必要であることがわかります。 +ランダム化されたセッションからのデータは、Web ページとの数百または数千のユーザー操作全体のパターンを見つけるのに役立ちます。このランダムに選択されたデータにパターンが現れた場合、問題を解決するための計画によってページ スコアが向上するという確信が持てます。 -2. - **Web vitals** - +## セッションリプレイで理解を深める [#session-replays] - ページの +不十分な LCP または高い CLS が特定された場合、セッション リプレイは何が起こったかを視覚的に記録し、問題の原因となっている正確な要素やイベントを迅速に特定するのに役立ちます。 - - **Page URLs** - +セッションリプレイがサイトの改善にどのように役立つかを示す例を次に示します。 - セクションを見ると、ホームページ URL の LCP スコアが 4 秒を超えていることがわかります。 これはすべてのユーザーに影響するエラーによるものですか、それとも 1 種類のユーザーのみに影響するものですか? たとえば、特定のバージョンの Chrome または特定の OS を使用しているユーザーでページロードタイムが遅いことに気付いた場合、問題の特定の原因をより適切にトラブルシューティングできます。 +1. パフォーマンスの問題を特定する: **Web vitals**ページで、関連する URL をクリックして詳細なパフォーマンス ビューを開きます。このアクションにより、そのページの Web Vitals 情報の詳細ビューにリダイレクトされます。CWV スコアを調べて、 **Needs improvement**または**Poor**ラベルの付いたスコアを探します。パフォーマンスの問題はプラットフォームによって大きく異なる可能性があるため、デバイスの種類やブラウザで結果をフィルタリングすることもできます。これらの詳細を理解することで、最適化すべき特定の領域を正確に特定することができます。 -3. トラブルシューティングする URL をクリックすると、新しいウィンドウが表示されます。 LCP スコアがサイト全体の LCP スコアよりもはるかに高いことに気づきました。 このページの下部にある +2. 関連するリプレイにアクセスする: 調査しているデータ ポイントの**Session replays**列の番号をクリックします。このアクションにより、リプレイが自動的にフィルタリングされ、特定のパフォーマンスの問題が発生しているセッションが表示されます。たとえば、LCP が低いページのセッション リプレイ数をクリックすると、LCP が遅かったセッションのリストが表示されます。 - - **Session traces** - +3. 視聴と診断: ビデオ録画を視聴して、問題を視覚的に理解します。次のことが発見できるかもしれません: - セクションまでスクロールすると、実際のユーザー セッションのさまざまなサンプルが表示されます。 これらのセッションでは、ユーザーが AJAX リクエスト、DOM 読み込みに関連する問題、JavaScript イベント、またはその他のエラーをどのように経験したかについて、より詳細な情報を得ることができます。 + * LCP の問題: 大きなヒーロー イメージまたはビデオの読み込みが遅く、数秒間画面が空白になる。 + * CLS の問題: 広告またはサードパーティのコンテンツが遅れて読み込まれ、ページ コンテンツが予期せず変更されることがあります。 + * INP の問題: ボタンやインタラクティブ要素の応答が遅いと、イライラすることがあります。 -ランダム化されたセッションからのデータは、Web ページとの数百または数千のユーザー操作全体のパターンを見つけるのに役立ちます。このランダムに選択されたデータにパターンが現れた場合、問題を解決するための計画によってページ スコアが向上するという確信が持てます。 +セッショントレースからの技術データとセッションリプレイのビジュアルコンテキストを組み合わせることで、パフォーマンスの問題を解決し、エンドユーザーエクスペリエンスを大幅に向上させるための包括的な計画を開発できます。 - + \ No newline at end of file diff --git a/src/i18n/content/jp/docs/tutorial-manage-large-log-volume/organize-large-logs.mdx b/src/i18n/content/jp/docs/tutorial-manage-large-log-volume/organize-large-logs.mdx index bf27c31b7cf..07ec06739b7 100644 --- a/src/i18n/content/jp/docs/tutorial-manage-large-log-volume/organize-large-logs.mdx +++ b/src/i18n/content/jp/docs/tutorial-manage-large-log-volume/organize-large-logs.mdx @@ -33,9 +33,9 @@ translationType: machine 事前解析: - ``` + ```json { - "message": "32 4329 store_Portland" + "message": "32 4329 store_Portland" } @@ -45,11 +45,11 @@ translationType: machine 事後解析: - ``` + ```json { - "transaction_total": "32", - "purchase_number": "4329", - "store_location": "store_Portland", + "transaction_total": "32", + "purchase_number": "4329", + "store_location": "store_Portland", } ``` @@ -120,9 +120,9 @@ ACME Corp が今後数か月間で約 2 TB のログを取り込むことが分 このドキュメントの前半で使用した例を使ってみましょう。次のパターンに従うログがあります。 - ``` + ```json { - "message": "32 4329 store_Portland" + "message": "32 4329 store_Portland" } ``` @@ -136,11 +136,11 @@ ACME Corp が今後数か月間で約 2 TB のログを取り込むことが分 上記のパターンで解析ルールが作成されると、次の方法でログが返されます。 - ``` + ```json { - "transaction_total": "32", - "purchase_number": "4329", - "store_location": "store_Portland", + "transaction_total": "32", + "purchase_number": "4329", + "store_location": "store_Portland", } ``` diff --git a/src/i18n/content/kr/docs/apis/nerdgraph/examples/nerdgraph-scorecards-custom-tutorial.mdx b/src/i18n/content/kr/docs/apis/nerdgraph/examples/nerdgraph-scorecards-custom-tutorial.mdx index efc62f38f3f..90acbd18595 100644 --- a/src/i18n/content/kr/docs/apis/nerdgraph/examples/nerdgraph-scorecards-custom-tutorial.mdx +++ b/src/i18n/content/kr/docs/apis/nerdgraph/examples/nerdgraph-scorecards-custom-tutorial.mdx @@ -98,24 +98,23 @@ Scorecards 관리자 사용자 정의 역할을 만들려면 다음이 필요합 #### 샘플 요청 ```graphql - { + { customerAdministration { - permissions(filter: {scope: {eq: "organization"}}) { - items { - feature - category - id - product - } + permissions(filter: { scope: { eq: "organization" } }) { + items { + feature + category + id + product } } } - + } ``` #### 샘플 응답 - ```graphql + ```json { "data": { "customerAdministration": { @@ -174,31 +173,28 @@ Scorecards 관리자 사용자 정의 역할을 만들려면 다음이 필요합 } } } - ``` 다음 기준에 맞는 텍스트 파일에 스코어카드 관련 정보를 복사하여 붙여넣으세요. * `category: MANAGE` - * `"feature"``: "Scorecards"` 또는 `“Scorecards Rules”` + * `"feature"``: "Scorecards"` 또는 `"Scorecards Rules"` 예를 들어, 이전 응답에서 다음은 기준과 일치합니다. - ```graphql - + ```json { - "category": "MANAGE", - "feature": "Scorecards Rules", - "id": "xxxxx", - "product": "New Relic One" - }, + "category": "MANAGE", + "feature": "Scorecards Rules", + "id": "xxxxx", + "product": "New Relic One" + }, { - "category": "MANAGE", - "feature": "Scorecards", - "id": "xxxxx", - "product": "New Relic One" - } - + "category": "MANAGE", + "feature": "Scorecards", + "id": "xxxxx", + "product": "New Relic One" + } ``` @@ -208,19 +204,18 @@ Scorecards 관리자 사용자 정의 역할을 만들려면 다음이 필요합 #### 샘플 요청 ```graphql - { + { actor { organization { id - } } } - + } ``` #### 샘플 응답 - ```graphql + ```json { "data": { "actor": { @@ -230,7 +225,6 @@ Scorecards 관리자 사용자 정의 역할을 만들려면 다음이 필요합 } } } - ``` 조직 ID를 복사하여 따로 보관하여 역할을 생성하세요. @@ -323,11 +317,11 @@ Scorecards 관리자 사용자 정의 역할을 만들려면 다음이 필요합
- `PermissionId` + `permissionIds` - Int + \[Int] @@ -368,10 +362,9 @@ Scorecards 관리자 사용자 정의 역할을 만들려면 다음이 필요합 #### 샘플 요청 ```graphql - mutation { customRoleCreate( - container: {id: "xxx****xxx-xx**00**-xxx-x*x*-xx**XXX**XX", type: "organization"} + container: { id: "xxx****xxx-xx**00**-xxx-x*x*-xx**XXX**XX", type: "organization" } name: "Scorecards manager" permissionIds: [xxxxx, xxxxx] scope: "organization" @@ -379,13 +372,11 @@ Scorecards 관리자 사용자 정의 역할을 만들려면 다음이 필요합 id } } - ``` #### 샘플 응답 - ```graphql - + ```json { "data": { "customRoleCreate": { @@ -393,7 +384,6 @@ Scorecards 관리자 사용자 정의 역할을 만들려면 다음이 필요합 } } } - ``` @@ -485,10 +475,9 @@ Scorecards 관리자 사용자 정의 역할을 만들려면 다음이 필요합 #### 샘플 요청 ```graphql - { customerAdministration { - groups(filter: {organizationId: {eq: "xxx****xxx-xx**00**-xxx-x*x*-xx**XXX**XX"}}) { + groups(filter: { organizationId: { eq: "xxx****xxx-xx**00**-xxx-x*x*-xx**XXX**XX" } }) { nextCursor items { id @@ -503,7 +492,6 @@ Scorecards 관리자 사용자 정의 역할을 만들려면 다음이 필요합 } } } - ``` 표시된 그룹 ID 목록에서 원하는 그룹 ID를 복사하여 앞서 만든 사용자 정의 스코어카드 역할에 연결합니다. @@ -550,11 +538,7 @@ Scorecards 관리자 사용자 정의 역할을 만들려면 다음이 필요합 @@ -583,7 +567,10 @@ Scorecards 관리자 사용자 정의 역할을 만들려면 다음이 필요합 ```graphql mutation { authorizationManagementGrantAccess( - grantAccessOptions: {organizationAccessGrants: {roleId: "99999999"}, groupId: "xxx****xxx-xx**00**-xxx-x*x*-xx**XXX**XX"} + grantAccessOptions: { + organizationAccessGrants: { roleId: "99999999" } + groupId: "xxx****xxx-xx**00**-xxx-x*x*-xx**XXX**XX" + } ) { roles { id @@ -595,12 +582,11 @@ Scorecards 관리자 사용자 정의 역할을 만들려면 다음이 필요합 } } } - ``` #### 샘플 응답 - ```graphql + ```json { "data": { "authorizationManagementGrantAccess": { @@ -617,7 +603,6 @@ Scorecards 관리자 사용자 정의 역할을 만들려면 다음이 필요합 } } } - ``` diff --git a/src/i18n/content/kr/docs/apis/synthetics-rest-api/monitor-examples/manage-synthetics-monitors-rest-api.mdx b/src/i18n/content/kr/docs/apis/synthetics-rest-api/monitor-examples/manage-synthetics-monitors-rest-api.mdx index 33570012a5d..c8a30035414 100644 --- a/src/i18n/content/kr/docs/apis/synthetics-rest-api/monitor-examples/manage-synthetics-monitors-rest-api.mdx +++ b/src/i18n/content/kr/docs/apis/synthetics-rest-api/monitor-examples/manage-synthetics-monitors-rest-api.mdx @@ -351,7 +351,6 @@ https://synthetics.eu.newrelic.com/synthetics/api ```sh scriptPayload='{"scriptText":BASE64 encoded string}' - curl -v -X PUT \ -H "Api-Key:$API_KEY" \ -H 'Content-Type: application/json' \ @@ -394,12 +393,12 @@ https://synthetics.eu.newrelic.com/synthetics/api 이 예에서는 `scriptLocation` 의 비밀번호로 `password` 을 사용합니다. - ``` + ```shell curl -v - -X PUT -H "Api-Key:$API_KEY" - -H 'content-type: application/json' - $API_ENDPOINT/v3/monitors/$MONITOR_ID/script - -d \ + -X PUT -H "Api-Key:$API_KEY" + -H 'content-type: application/json' + $API_ENDPOINT/v3/monitors/$MONITOR_ID/script + -d \ '{ "scriptText": "dmFyIGFzc2VydCA9IHJlcXVpcmUoJ2Fzc2VydCcpOw0KYXNzZXJ0LmVxdWFsKCcxJywgJzEnKTs=", "scriptLocations": [{ @@ -469,7 +468,7 @@ https://synthetics.eu.newrelic.com/synthetics/api 어떤 경우에는 줄 바꿈을 비활성화하는 `-w 0` 를 사용할 수 있습니다. `base64 -w 0 $scriptfile` - ```bash + ```sh #!/bin/bash # API key from your account settings diff --git a/src/i18n/content/kr/docs/apm/agents/java-agent/troubleshooting/ssl-or-connection-errors-java.mdx b/src/i18n/content/kr/docs/apm/agents/java-agent/troubleshooting/ssl-or-connection-errors-java.mdx index 9aec1157ed6..b46b41ad926 100644 --- a/src/i18n/content/kr/docs/apm/agents/java-agent/troubleshooting/ssl-or-connection-errors-java.mdx +++ b/src/i18n/content/kr/docs/apm/agents/java-agent/troubleshooting/ssl-or-connection-errors-java.mdx @@ -35,11 +35,11 @@ Cannot find the specified class com.ibm.websphere.ssl.protocol.SSLSocketFactory 권장 사항: 뉴렐릭의 인증서가 파생된 DigiCert 글로벌 루트 인증 기관(CA)을 신뢰 저장소에 추가하세요. -"기타 루트 인증서" 섹션 아래의 DigiCert에서 [DigiCert 글로벌 루트 CA를](https://www.digicert.com/kb/digicert-root-certificates.htm) 다운로드할 수 있습니다("PEM 다운로드" 옵션 선택). +"기타 루트 인증서" 섹션 아래의 DigiCert에서 [DigiCert 글로벌 루트 CA를](https://www.digicert.com/kb/digicert-root-certificates.htm) 다운로드할 수 있습니다("PEM 다운로드" 옵션 선택). 인증서를 신뢰 저장소로 가져오려면 이 명령을 사용하거나 [keytool에 대한 Oracle의 Java SE 설명서를](https://docs.oracle.com/javase/6/docs/technotes/tools/solaris/keytool.html) 참조하십시오. -``` +```sh keytool -importcert -alias ca_alias -file ca_file.pem -keystore truststore.ts -storepass ts_password ``` @@ -113,4 +113,4 @@ java.security.cert.CertificateException: Could not parse certificate: java.io.IO ### 솔루션 B [#log-exception-solution] -인증서의 머리글과 바닥글에 후행 공백이 없는지 검사하고 확인합니다. 그렇다면 다른 인증서를 편집하거나 사용하십시오. +인증서의 머리글과 바닥글에 후행 공백이 없는지 검사하고 확인합니다. 그렇다면 다른 인증서를 편집하거나 사용하십시오. \ No newline at end of file diff --git a/src/i18n/content/kr/docs/browser/new-relic-browser/browser-apis/addpageaction.mdx b/src/i18n/content/kr/docs/browser/new-relic-browser/browser-apis/addpageaction.mdx index 0bbe25a82c8..33d91f8355b 100644 --- a/src/i18n/content/kr/docs/browser/new-relic-browser/browser-apis/addpageaction.mdx +++ b/src/i18n/content/kr/docs/browser/new-relic-browser/browser-apis/addpageaction.mdx @@ -45,7 +45,7 @@ newrelic.addPageAction(string $name[, JSON object $attributes]) 이 API 호출은 사용자 정의 이름과 선택적 속성,[그리고 몇 가지 기본 속성을](/attribute-dictionary/?event=PageAction) [대시보드](/docs/query-your-data/explore-query-data/dashboards/introduction-new-relic-one-dashboards) 에 포함하는 브라우저 [`PageAction` 이벤트를](/docs/insights/explore-data/custom-events/insert-browser-custom-events-attributes-insights-javascript-api) 전송합니다. 이것은 브라우저 에이전트가 자동으로 추적하지 않는 이벤트(예: **Subscribe** 버튼 클릭이나 튜토리얼 액세스)를 추적하는 데 유용합니다. * `PageAction` 이벤트는 30초마다 전송됩니다. -* 1,000개의 이벤트가 관찰되면 에이전트는 하베스트 처리 간격을 우회하여 버퍼링된 이벤트를 즉시 수집합니다. +* 1,000개의 이벤트가 관찰되거나 수집 페이로드 크기가 16KB보다 큰 경우 에이전트는 하베스트 간격을 우회하여 버퍼링된 이벤트를 즉시 수집합니다. 이전 에이전트 버전에서는 이벤트가 120개 관찰된 후에 삭제되었습니다. 버전 [1.264.0](https://docs.newrelic.com/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.264.0/) 에서는 이벤트 제한이 120에서 1,000으로 늘어났으며 더 이상 삭제되지 않습니다. diff --git a/src/i18n/content/kr/docs/browser/new-relic-browser/browser-apis/recordCustomEvent.mdx b/src/i18n/content/kr/docs/browser/new-relic-browser/browser-apis/recordCustomEvent.mdx index cc22baa64a5..bf1b1cfb87e 100644 --- a/src/i18n/content/kr/docs/browser/new-relic-browser/browser-apis/recordCustomEvent.mdx +++ b/src/i18n/content/kr/docs/browser/new-relic-browser/browser-apis/recordCustomEvent.mdx @@ -45,7 +45,7 @@ newrelic.recordCustomEvent(string $eventType[, JSON object $attributes]) 이 API 호출은 사용자가 정의한 eventType 및 선택적 속성이 포함된 사용자 정의 브라우저 이벤트를 [대시보드](/docs/query-your-data/explore-query-data/dashboards/introduction-new-relic-one-dashboards) 에 전송하고, 사용자 정의 속성에 대해 설정할 수도 있습니다. 이 기능은 브라우저 에이전트가 자동으로 추적하지 않는 모든 이벤트를 추적하는 데 유용하며, 사용자가 제어하는 규칙과 속성을 통해 강화됩니다. * `custom` 이벤트는 30초마다 전송됩니다. -* 1,000개의 이벤트가 관찰되면 에이전트는 하베스트 처리 간격을 우회하여 버퍼링된 이벤트를 즉시 수집합니다. +* 1,000개의 이벤트가 관찰되거나 수집 페이로드 크기가 16KB보다 큰 경우 에이전트는 하베스트 간격을 우회하여 버퍼링된 이벤트를 즉시 수집합니다. ## 매개변수 [#parameters] diff --git a/src/i18n/content/kr/docs/browser/new-relic-browser/page-load-timing-resources/instrumentation-browser-monitoring.mdx b/src/i18n/content/kr/docs/browser/new-relic-browser/page-load-timing-resources/instrumentation-browser-monitoring.mdx index b5c292b032a..2cdd3fe573b 100644 --- a/src/i18n/content/kr/docs/browser/new-relic-browser/page-load-timing-resources/instrumentation-browser-monitoring.mdx +++ b/src/i18n/content/kr/docs/browser/new-relic-browser/page-load-timing-resources/instrumentation-browser-monitoring.mdx @@ -160,7 +160,7 @@ https **and** http 웹페이지 모두 https를 통해 데이터를 diff --git a/src/i18n/content/kr/docs/browser/new-relic-browser/performance-quality/browser-monitoring-performance-impact.mdx b/src/i18n/content/kr/docs/browser/new-relic-browser/performance-quality/browser-monitoring-performance-impact.mdx index c773083c5fe..42701dc1f2e 100644 --- a/src/i18n/content/kr/docs/browser/new-relic-browser/performance-quality/browser-monitoring-performance-impact.mdx +++ b/src/i18n/content/kr/docs/browser/new-relic-browser/performance-quality/browser-monitoring-performance-impact.mdx @@ -162,7 +162,7 @@ JavaScript의 오버헤드는 사용자에 대한 영향과 시스템 성능에 @@ -300,7 +300,7 @@ JavaScript의 오버헤드는 사용자에 대한 영향과 시스템 성능에 diff --git a/src/i18n/content/kr/docs/change-tracking/change-tracking-events.mdx b/src/i18n/content/kr/docs/change-tracking/change-tracking-events.mdx index 5c939e9a2c1..1b5949c7203 100644 --- a/src/i18n/content/kr/docs/change-tracking/change-tracking-events.mdx +++ b/src/i18n/content/kr/docs/change-tracking/change-tracking-events.mdx @@ -29,7 +29,7 @@ translationType: machine 변경 추적 기능을 사용하면 애플리케이션과 인프라 전반의 변경 사항을 캡처, 시각화하고 분석할 수 있습니다. 이 기능은 변경 사항이 시스템과 고객에게 어떤 영향을 미치는지 이해하는 데 도움이 되도록 설계되었습니다. -* **Capture all changes impacting your system:** Send change events for any type of change, including deployments, feature flags changes, configuration changes, and business events. You can also create custom change events tailored to your specific requirements. Use the [`changeTrackingCreateEvent`](#change-tracking-event-mutation) NerdGraph mutation to easily send various types of change events. +* **시스템에 영향을 미치는 모든 변경 사항을 캡처합니다.** 구현, 배포, 기능 플래그 변경, 설정 변경 및 비즈니스 이벤트를 포함한 모든 유형의 변경에 대해 변경 이벤트를 보냅니다. 또한, 특정 요구 사항에 맞춰 사용자 정의 변경 이벤트를 만들 수도 있습니다. [`changeTrackingCreateEvent`](#change-tracking-event-mutation) NerdGraph 뮤테이션을 사용하면 다양한 유형의 변경 이벤트를 쉽게 보낼 수 있습니다. * **시스템 전체의 변경 사항을 관리하기 위한 포괄적인 보기를 확보하세요.** 하나의 통합 인터페이스에서 모든 논문과 계정의 변경 사항을 원활하게 보고 필터링하세요. 팀, 유형, 사용자 정의 속성 및 기타 기준으로 필터링하여 변경 사항을 손쉽게 식별하세요. diff --git a/src/i18n/content/kr/docs/new-relic-control/agent-control/configuration.mdx b/src/i18n/content/kr/docs/new-relic-control/agent-control/configuration.mdx index 6e35e6d6a4c..7f6da8c2af9 100644 --- a/src/i18n/content/kr/docs/new-relic-control/agent-control/configuration.mdx +++ b/src/i18n/content/kr/docs/new-relic-control/agent-control/configuration.mdx @@ -306,21 +306,22 @@ translationType: machine secretName: ca-certs # Configure Flux components to use proxy - flux2: - sourceController: - extraEnv: - # Configure Flux source-controller to proxy all requests - - name: HTTPS_PROXY - value: https://proxy-service:8080 - # Except for in-cluster requests - - name: "NO_PROXY" - value: ".cluster.local.,.cluster.local,cluster.local,.svc,127.0.0.0/8,10.0.0.0/8" - volumeMounts: - # Mount CA certificate bundle to source-controller trust root store. The bundle should contain the - # proxy CA cert. - - mountPath: /etc/ssl/certs/ - name: ca-certs - volumes: + agent-control-cd: + flux2: + sourceController: + extraEnv: + # Configure Flux source-controller to proxy all requests + - name: HTTPS_PROXY + value: https://proxy-service:8080 + # Except for in-cluster requests + - name: "NO_PROXY" + value: ".cluster.local.,.cluster.local,cluster.local,.svc,127.0.0.0/8,10.0.0.0/8" + volumeMounts: + # Mount CA certificate bundle to source-controller trust root store. The bundle should contain the + # proxy CA cert. + - mountPath: /etc/ssl/certs/ + name: ca-certs + volumes: - name: ca-certs secret: secretName: ca-certs @@ -338,20 +339,160 @@ translationType: machine 프록시를 사용하는 경우 각 관리 에이전트에 대한 프록시 설정도 개별적으로 구성해야 합니다. 프록시 설정 옵션은 각 에이전트의 특정 문서를 참조하세요. -## Private repository configuration +## 비밀 관리 -Agent Control supports configuring private Helm repositories to deploy both Agent Control itself and the managed agents. This enables environments where the New Relic Helm charts are not directly accessible. +Agent Control provides a robust mechanism for managing sensitive data, such as passwords and API keys, by retrieving them from dedicated secret providers. This ensures that sensitive information is not hard-coded directly into configuration files. The system currently supports the following secret providers: + +* HashiCorp Vault: referred to as `nr-vault` in configurations. +* Kubernetes Secrets: referred to as `nr-kubesec` in configurations. + +### Defining Secrets in Configuration + +To utilize secrets, define them within your Agent-Control configuration YAML file by following these steps: + +1. **Define the `secrets_providers` section:** Configure your secret providers centrally in this section. Ensure each entry corresponds to a supported provider. +2. **Configure secret sources:** For each provider, specify one or more sources. A source includes the necessary configuration details (e.g., URL, token) for Agent control to connect to and retrieve a group of secrets. +3. **Use placeholders in agent configurations:** Instead of the actual sensitive data, Use a placeholder string within your agent's configuration. Agent control automatically replaces these placeholders with the retrieved secrets during the rendering process. + + + If Agent control fails to retrieve a secret, the configuration rendering will fail, and the agent will not be executed. This is a critical security feature to prevent agents from running with incomplete or incorrect configurations. + + +The following agent-control configuration example demonstrates how to configure for retrieving secrets from two Vault sources within the `secrets_providers` section: + +```yaml +secrets_providers: + vault: + sources: + local-instance: + url: http://localhost:8200/v1/ + token: root + engine: kv2 + remote: + url: http://my-remote-server:8200/v1/ + token: root + engine: kv1 + +fleet_control: + ... + +agents: + ... +``` + +#### Using Secrets in an Agent Configuration + +After the sources are defined, in an agent configuration, you can reference the vault using a specific placeholder syntax with the correct path. Agent control retrieves the secret and uses it to render the final configuration file that the agent is going to use. + +Example of agent configuration using vault placeholders: + +```yaml +config_agent: |+ + enable_process_metrics: true + custom_attributes: + username: "${nr-vault:local-instance:secret:my_secret:username}" + organization: "${nr-vault:remote:my_mount:my_path:organization}" +``` + +이 예에서: + +The placeholder `${nr-vault:local-instance:secret:my_secret:username}` instructs Agent control to retrieve the value associated with the key username from the secret at the path `secret/my_secret` using the local-instance vault source. The placeholder `${nr-vault:remote:my_mount:my_path:organization}` similarly retrieves the value for the organization key from the remote source. + +After successful retrieval, Agent control renders these secrets from the specified source and path, storing the result in a K8s secret or private config file for use by the corresponding agent. + +### 금고 비밀 + +Set up the vault sources with the following settings: + +
- 사용자 정의 - - [역할 섹션에서 생성된 사용자 정의]() - - 역할 ID입니다. + 사용자 정의 역할 섹션에 생성된 사용자 정의 역할 ID입니다.
- 데이터는 초기 페이지 로드 후 10초 후에 전송되고 그 이후에는 30초마다 전송됩니다. + 데이터는 초기 페이지 로드 후 10초 후에 전송되고, 그 이후로는 30초마다 전송됩니다. 수확 페이로드 크기가 16KB보다 크면 데이터가 일찍 전송됩니다.
- `PageViewTiming` 이벤트는 모든 에이전트에서 수집하며 핵심 웹 바이탈 측정과 같은 타이밍 데이터를 포함합니다. 첫 번째 수집은 `load` 페이지 수명 주기 이벤트 후 10초 후에 발생합니다. 보낼 데이터가 있는 경우 필요에 따라 30초마다 추가 수집이 발생합니다. 보고된 이벤트 목록은 [PageViewTiming 문서를](/docs/browser/new-relic-browser/page-load-timing-resources/pageviewtiming-async-or-dynamic-page-details/#interactivity-metrics) 참조하세요. + `PageViewTiming` 이벤트는 모든 에이전트에 의해 수집되며 핵심 웹 중요 지표 측정과 같은 타이밍 데이터가 포함됩니다. 첫 번째 수집은 `load` 페이지 수명 주기 이벤트 후 10초 후에 발생합니다. 전송할 데이터가 있거나 수집 페이로드 크기가 16KB보다 큰 경우 필요에 따라 30초마다 추가 수집이 발생합니다. 보고된 이벤트 목록은 [PageViewTiming 문서를](/docs/browser/new-relic-browser/page-load-timing-resources/pageviewtiming-async-or-dynamic-page-details/#interactivity-metrics) 참조하세요.
- `PageAction` 이벤트는 `load` 페이지 수명 주기 이벤트 후에 수집되며 후속 수집은 30초마다 발생합니다. + `PageAction` 이벤트는 `load` 페이지 수명 주기 이후에 수집됩니다. 이벤트, 이후 수집은 30초마다 또는 수집 페이지 로드 크기가 16KB보다 큰 경우 발생합니다.
+ + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ YAML 키 + + 설명 +
+ `url` + + 데이터를 요청할 URL +
+ `token` + + Used to authenticate to the endpoint. +
+ `engine` + + Specify **`kv1`** or **`kv2`**. +
+ +In the configuration file, each secret stored in Vault can be accessed by setting a placeholder with: + +* **source\_name**: The name of the Vault source defined in `secrets_providers`. +* **mount**: The name of the secrets engine mount. +* **path**: The specific path to the secret. +* **specific key**: The specific key within the secret to be retrieved. + +Example of full placeholder format: + +``` +"${nr-vault:source_name:my_mount:my_path:my_value}" +``` + +### Kubernetes secrets + +If the agent-control pod has permissions, such as through a Service Account and Role-Based Access Control (RBAC), to access the required secrets and namespaces, Agent control can directly access secrets from the Kubernetes API without needing a separate sources configuration. + +In the agent configuration file, retrieve each secret value using a placeholder specifying: + +* **namespace**: The Kubernetes namespace where the secret is located. +* **name**: The name of the Kubernetes secret object. +* **specific key**: The specific key within the secret from which to retrieve the value. + +For example, use the placeholder format: + +``` +"${nr-kubesec:my_namespace:my_secret:my_value}" +``` + +## 비공개 설정 + +Agent Control은 Agent Control 자체와 관리 에이전트 모두에 구현, 배포에 대한 개인 Helm 렌즈 구성을 지원합니다. 이를 통해 Helm 차트에 직접 접근할 수 있습니다. - When using private Helm repositories, the charts need to be compatible and the referenced images within the charts must be reachable. If not, the agents will not work as expected. + 개인 Helm 저장소를 사용하는 경우 차트가 호환되어야 하며 차트 내에서 참조된 이미지에 접근할 수 있어야 합니다. 그렇지 않으면 에이전트가 예상대로 작동하지 않습니다. -### 1. Enable private repositories for agents +### 1. 에이전트에 대한 개인 저장소 활성화 -For security reasons, only explicitly enabled repositories will be allowed in remote configurations. To enable specific repositories, you need to update the Agent Control configuration: +보안상의 이유로, 원격 설정에서는 명시적으로 활성화된만 허용됩니다. 특정 이온을 활성화하려면 에이전트 제어 설정을 업데이트해야 합니다: - + ```yaml # values-newrelic.yaml @@ -371,7 +512,7 @@ For security reasons, only explicitly enabled repositories will be allowed in re -The allowed repository configurations can then be used in your remote configurations within New Relic Control. Example: +그런 다음 허용된 클럽 설정을 뉴렐릭 Control 내의 원격 설정에서 사용할 수 있습니다. 예: ```yaml chart_version: "1.2.3" @@ -380,19 +521,19 @@ chart_repository: name: "my-chart-name" # Optional: use only if the chart name doesn't match New Relic's chart name ``` -Additionally, you need to configure Agent Control's Helm installation to use your private repository if the `agent-control` chart itself is in a private repository. This is separate from the configuration for managed agents. Refer to the `agent-control` Helm chart [values.yaml](https://github.com/newrelic/helm-charts/blob/master/charts/agent-control/values.yaml) to set up the `installationJob` section. Specifically: +또한 `agent-control` 차트 자체가 비공개 위치에 있는 경우 비공개 위치를 사용하도록 에이전트 제어의 Helm 설치를 구성해야 합니다. 이는 관리 에이전트의 설정과는 별개입니다. `installationJob` 섹션을 설정하려면 `agent-control` Helm 차트 [값.yaml](https://github.com/newrelic/helm-charts/blob/master/charts/agent-control/values.yaml) 을 참조하세요. 구체적으로: -* `chartRepositoryUrl` containing your repository URL -* `name` if using a different chart name -* `repositorySecretReferenceName` and `repositoryCertificateSecretReferenceName` for authentication (see the authentication section below for details) +* `chartRepositoryUrl` 저장소 URL이 포함되어 있습니다 +* `name` 다른 차트 이름을 사용하는 경우 +* `repositorySecretReferenceName` 인증을 위한 `repositoryCertificateSecretReferenceName` (자세한 내용은 아래 인증 섹션 참조) -### 2. Set up authentication for private repositories +### 2. 개인 저장소에 대한 인증 설정 -You need to set up additional resources to enable authentication for accessing your private repository: +개인 저장소에 액세스하기 위한 인증을 활성화하려면 추가 리소스를 설정해야 합니다. - To authenticate using basic authentication (username and password), you need to create a secret in the Agent Control namespace containing the expected values in `data.username` and `data.password`. + 기본 인증(사용자 이름 및 비밀번호)을 사용하여 인증하려면 에이전트 제어 네임스페이스에 `data.username` 및 `data.password` 에 예상 값이 포함된 비밀을 생성해야 합니다. 예시: @@ -406,9 +547,9 @@ You need to set up additional resources to enable authentication for accessing y password: "myPassword" ``` - For more details, see the [Flux documentation](https://fluxcd.io/flux/components/source/helmrepositories/#secret-reference). + 자세한 내용은 [Flux 문서를](https://fluxcd.io/flux/components/source/helmrepositories/#secret-reference) 참조하세요. - When using basic authentication, the remote configuration should be configured as follows: + 기본 인증을 사용하는 경우 원격 설정은 다음과 같이 구성해야 합니다. ```yaml chart_repository: @@ -418,13 +559,13 @@ You need to set up additional resources to enable authentication for accessing y ``` - - To authenticate using TLS, you need to create a secret containing: + + TLS를 사용하여 인증하려면 다음이 포함된 비밀을 만들어야 합니다. - * `tls.crt` and `tls.key`: client certificate and private key used for TLS client authentication - * `ca.crt`: CA certificate used to verify the server (required if the server uses a self-signed certificate) + * `tls.crt` 및 `tls.key`: TLS 클라이언트 인증에 사용되는 클라이언트 인증서 및 개인 키 + * `ca.crt`: 서버를 검증하는 데 사용되는 CA 인증서(서버가 자체 서명 인증서를 사용하는 경우 필요) - The Secret should be of type `Opaque` or `kubernetes.io/tls`. All files in the Secret are expected to be PEM-encoded. + 비밀은 `Opaque` 또는 `kubernetes.io/tls` 유형이어야 합니다. Secret에 있는 모든 파일은 PEM으로 인코딩되어야 합니다. 예시: @@ -442,9 +583,9 @@ You need to set up additional resources to enable authentication for accessing y ca.crt: ``` - For more details, see the [Flux documentation](https://fluxcd.io/flux/components/source/helmrepositories/#secret-reference). + 자세한 내용은 [Flux 문서를](https://fluxcd.io/flux/components/source/helmrepositories/#secret-reference) 참조하세요. - When using TLS certificate authentication, the remote configuration should be configured as follows: + TLS 인증서 인증을 사용하는 경우 원격 설정은 다음과 같이 구성해야 합니다. ```yaml chart_repository: diff --git a/src/i18n/content/kr/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx b/src/i18n/content/kr/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx index 5b02da43802..dba14947fac 100644 --- a/src/i18n/content/kr/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx +++ b/src/i18n/content/kr/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx @@ -280,7 +280,7 @@ mutation { pipelineCloudRuleEntity: { description: "Since we only care about MyEvent in staging and production, let's drop all MyEvent data in the test environment", name: "Drop MyEvent in test environment", - nrql: "DELETE FROM MyEvent where environment = 'test'", + nrql: "DELETE FROM MyEvent WHERE environment = 'test'", scope: { id: "your_nr_account_id", type: ACCOUNT @@ -304,7 +304,7 @@ mutation { pipelineCloudRuleEntity: { description: "We don't care about jvmId and targetAttr in the test environment, let's drop those attributes", name: "Drop jvmId and targetAttr from MyEvent in test environment", - nrql: "DELETE jvmId, targetAttr FROM MyEvent where environment = 'test'", + nrql: "DELETE jvmId, targetAttr FROM MyEvent WHERE environment = 'test'", scope: { id: "your_nr_account_id", type: ACCOUNT @@ -529,7 +529,7 @@ mutation { pipelineCloudRuleEntity: { description: "We don't care about targetAttr in the test environment in dimensional metric rolloups, let's drop those attributes", name: "Drop targetAttr from Metric aggregate rollups in test environment", - nrql: "DELETE targetAttr FROM MetricAggregate where environment = 'test'", + nrql: "DELETE targetAttr FROM MetricAggregate WHERE environment = 'test'", scope: { id: "your_nr_account_id", type: ACCOUNT diff --git a/src/i18n/content/kr/docs/new-relic-control/pipeline-control/data-dropping-gateway.mdx b/src/i18n/content/kr/docs/new-relic-control/pipeline-control/data-dropping-gateway.mdx index 6d6e6ae8bf7..84b1dfcf2f8 100644 --- a/src/i18n/content/kr/docs/new-relic-control/pipeline-control/data-dropping-gateway.mdx +++ b/src/i18n/content/kr/docs/new-relic-control/pipeline-control/data-dropping-gateway.mdx @@ -524,7 +524,7 @@ translationType: machine 		- `DELETE FROM SqlTrace WHERE uri = 'Custom\/Simple\/sqlTransaction'` + `DELETE FROM SqlTrace WHERE uri = 'Custom/Simple/sqlTransaction'`
- `DELETE FROM TransactionTrace WHERE uri = 'Custom\/Simple\/sqlTransaction'` + `DELETE FROM TransactionTrace WHERE uri = 'Custom/Simple/sqlTransaction'`
- `DELETE instanceType,inodesTotal NetworkSample WHERE entityKey = 'vagrant'` + `DELETE instanceType, inodesTotal NetworkSample WHERE entityKey = 'vagrant'`
- `DELETE FROM ContainerSample WHERE agentName='ContainerSampleAgent'` + `DELETE FROM ContainerSample WHERE agentName = 'ContainerSampleAgent'`
- diff --git a/src/i18n/content/pt/docs/browser/new-relic-browser/performance-quality/browser-monitoring-performance-impact.mdx b/src/i18n/content/pt/docs/browser/new-relic-browser/performance-quality/browser-monitoring-performance-impact.mdx index d043d1384ae..bbc8cadede3 100644 --- a/src/i18n/content/pt/docs/browser/new-relic-browser/performance-quality/browser-monitoring-performance-impact.mdx +++ b/src/i18n/content/pt/docs/browser/new-relic-browser/performance-quality/browser-monitoring-performance-impact.mdx @@ -162,7 +162,7 @@ O agente consiste em múltiplos scripts para reduzir o tamanho inicial do " @@ -300,7 +300,7 @@ O agente consiste em múltiplos scripts para reduzir o tamanho inicial do " diff --git a/src/i18n/content/pt/docs/cci/configure-cci/general-setting.mdx b/src/i18n/content/pt/docs/cci/configure-cci/general-setting.mdx index 4c2c1c56ce7..b532be6ba3f 100644 --- a/src/i18n/content/pt/docs/cci/configure-cci/general-setting.mdx +++ b/src/i18n/content/pt/docs/cci/configure-cci/general-setting.mdx @@ -43,10 +43,10 @@ A Inteligência de Custos na Nuvem suporta tag personalizada junto com tag padr 1. Para solicitar informações sobre as contas das quais você deseja extrair dados de telemetria para análise de custos, selecione a aba **Telemetry Data** . 2. Para visualizar e gerenciar dados de telemetria para sua análise de custos, na lista **Select accounts for telemetry data** , escolha uma ou mais contas. - - * A estimativa de custos em tempo real é suportada por dados de telemetria. - * A alocação de K8s é suportada por dados de telemetria. - * Reutilizamos o pipeline de telemetria existente para obter a métrica de utilização, e nenhum dado novo é ingerido, exceto a ingestão do arquivo CUR. - + + * A estimativa de custos em tempo real é suportada por dados de telemetria. + * A alocação de K8s é suportada por dados de telemetria. + * Reutilizamos o pipeline de telemetria existente para obter a métrica de utilização, e nenhum dado novo é ingerido, exceto a ingestão do arquivo CUR. + - + \ No newline at end of file diff --git a/src/i18n/content/pt/docs/change-tracking/change-tracking-events.mdx b/src/i18n/content/pt/docs/change-tracking/change-tracking-events.mdx index 443b78c5a00..42098dd3fdd 100644 --- a/src/i18n/content/pt/docs/change-tracking/change-tracking-events.mdx +++ b/src/i18n/content/pt/docs/change-tracking/change-tracking-events.mdx @@ -29,7 +29,7 @@ translationType: machine O recurso Monitoramento de Alterações permite capturar, visualizar e analisar alterações em seu aplicativo e infraestrutura. Este recurso foi criado para ajudar você a entender como as mudanças impactam seu sistema e seus clientes. -* **Capture all changes impacting your system:** Send change events for any type of change, including deployments, feature flags changes, configuration changes, and business events. You can also create custom change events tailored to your specific requirements. Use the [`changeTrackingCreateEvent`](#change-tracking-event-mutation) NerdGraph mutation to easily send various types of change events. +* **Capture todas as alterações que impactam seu sistema:** Envie evento de alteração para qualquer tipo de alteração, incluindo implantação, alterações de bandeiras de recurso, alterações de configuração e evento de negócios. Você também pode criar eventos de mudança personalizados, adaptados às suas necessidades específicas. Use a mutação [`changeTrackingCreateEvent`](#change-tracking-event-mutation) NerdGraph para enviar facilmente vários tipos de eventos de mudança. * **Obtenha uma visão abrangente para gerenciar alterações em todo o sistema:** visualize e filtre facilmente eventos de alteração em toda a sua entidade e contas a partir de uma interface unificada. Identifique alterações sem esforço filtrando por equipe, tipo, atributo personalizado e quaisquer outros critérios. diff --git a/src/i18n/content/pt/docs/new-relic-control/agent-control/configuration.mdx b/src/i18n/content/pt/docs/new-relic-control/agent-control/configuration.mdx index 8832416d1f3..f635461b2a5 100644 --- a/src/i18n/content/pt/docs/new-relic-control/agent-control/configuration.mdx +++ b/src/i18n/content/pt/docs/new-relic-control/agent-control/configuration.mdx @@ -306,21 +306,22 @@ Para configurações de proxy usando autenticação HTTPS com certificados autoa secretName: ca-certs # Configure Flux components to use proxy - flux2: - sourceController: - extraEnv: - # Configure Flux source-controller to proxy all requests - - name: HTTPS_PROXY - value: https://proxy-service:8080 - # Except for in-cluster requests - - name: "NO_PROXY" - value: ".cluster.local.,.cluster.local,cluster.local,.svc,127.0.0.0/8,10.0.0.0/8" - volumeMounts: - # Mount CA certificate bundle to source-controller trust root store. The bundle should contain the - # proxy CA cert. - - mountPath: /etc/ssl/certs/ - name: ca-certs - volumes: + agent-control-cd: + flux2: + sourceController: + extraEnv: + # Configure Flux source-controller to proxy all requests + - name: HTTPS_PROXY + value: https://proxy-service:8080 + # Except for in-cluster requests + - name: "NO_PROXY" + value: ".cluster.local.,.cluster.local,cluster.local,.svc,127.0.0.0/8,10.0.0.0/8" + volumeMounts: + # Mount CA certificate bundle to source-controller trust root store. The bundle should contain the + # proxy CA cert. + - mountPath: /etc/ssl/certs/ + name: ca-certs + volumes: - name: ca-certs secret: secretName: ca-certs @@ -338,20 +339,160 @@ Para configurações de proxy usando autenticação HTTPS com certificados autoa Ao usar um proxy, você também deve configurar as definições de proxy para cada agente gerenciado individualmente. Consulte a documentação específica de cada agente para obter opções de configuração de proxy. -## Private repository configuration +## Gerenciamento de segredos -Agent Control supports configuring private Helm repositories to deploy both Agent Control itself and the managed agents. This enables environments where the New Relic Helm charts are not directly accessible. +Agent Control provides a robust mechanism for managing sensitive data, such as passwords and API keys, by retrieving them from dedicated secret providers. This ensures that sensitive information is not hard-coded directly into configuration files. The system currently supports the following secret providers: + +* HashiCorp Vault: referred to as `nr-vault` in configurations. +* Kubernetes Secrets: referred to as `nr-kubesec` in configurations. + +### Defining Secrets in Configuration + +To utilize secrets, define them within your Agent-Control configuration YAML file by following these steps: + +1. **Define the `secrets_providers` section:** Configure your secret providers centrally in this section. Ensure each entry corresponds to a supported provider. +2. **Configure secret sources:** For each provider, specify one or more sources. A source includes the necessary configuration details (e.g., URL, token) for Agent control to connect to and retrieve a group of secrets. +3. **Use placeholders in agent configurations:** Instead of the actual sensitive data, Use a placeholder string within your agent's configuration. Agent control automatically replaces these placeholders with the retrieved secrets during the rendering process. + + + If Agent control fails to retrieve a secret, the configuration rendering will fail, and the agent will not be executed. This is a critical security feature to prevent agents from running with incomplete or incorrect configurations. + + +The following agent-control configuration example demonstrates how to configure for retrieving secrets from two Vault sources within the `secrets_providers` section: + +```yaml +secrets_providers: + vault: + sources: + local-instance: + url: http://localhost:8200/v1/ + token: root + engine: kv2 + remote: + url: http://my-remote-server:8200/v1/ + token: root + engine: kv1 + +fleet_control: + ... + +agents: + ... +``` + +#### Using Secrets in an Agent Configuration + +After the sources are defined, in an agent configuration, you can reference the vault using a specific placeholder syntax with the correct path. Agent control retrieves the secret and uses it to render the final configuration file that the agent is going to use. + +Example of agent configuration using vault placeholders: + +```yaml +config_agent: |+ + enable_process_metrics: true + custom_attributes: + username: "${nr-vault:local-instance:secret:my_secret:username}" + organization: "${nr-vault:remote:my_mount:my_path:organization}" +``` + +Neste exemplo: + +The placeholder `${nr-vault:local-instance:secret:my_secret:username}` instructs Agent control to retrieve the value associated with the key username from the secret at the path `secret/my_secret` using the local-instance vault source. The placeholder `${nr-vault:remote:my_mount:my_path:organization}` similarly retrieves the value for the organization key from the remote source. + +After successful retrieval, Agent control renders these secrets from the specified source and path, storing the result in a K8s secret or private config file for use by the corresponding agent. + +### Segredos do cofre + +Set up the vault sources with the following settings: + +
+ 도움이 됨 @@ -114,7 +116,7 @@ Google은 다음 세 가지 지표를 기준으로 전반적인 웹사이트 성 ### CLS 점수는 어떻게 계산되나요? - 누적 레이아웃 이동 점수는 다른 코어 웹 바이탈처럼 시간 기반 측정이 아닌 0에서 무한대 사이의 단위 없는 값입니다. 웹페이지 로딩 과정에서 발생하는 예상치 못한 레이아웃 변화의 영향을 합산한 것입니다. CLS 점수 계산 방법은 다음과 같습니다. + 누적 레이아웃 이동 점수는 다른 CWV와 같이 시간에 따른 측정값이 아닌 0과 무한대 사이의 단위 없는 값입니다. 이는 웹페이지 로딩 과정 중에 발생하는 예상치 못한 레이아웃 변화의 영향의 총합을 반영합니다. CLS 점수는 다음과 같이 계산됩니다. * 레이아웃 변경 점수: 이는 두 가지 요소를 고려합니다. @@ -126,13 +128,13 @@ Google은 다음 세 가지 지표를 기준으로 전반적인 웹사이트 성 **Good** 웹 바이탈은 조직이 비용을 절감하고 SEO를 높이는 데 도움이 될 수 있습니다. **Poor** 또는 **Needs improvement** 조직에 대한 사용자의 부정적인 인식을 반영할 수 있으며, 이로 인해 고객이 불만족스럽거나 비즈니스 기회를 잃을 수 있습니다. -뉴렐릭은 Google의 [`web-vitals` API 라이브러리를](https://github.com/GoogleChrome/web-vitals) 활용하여 추가 계산을 도입하지 않고 원시 상태의 웹 바이탈을 수집합니다. 코어 웹 바이탈이 중요한 이유와 계산 방법에 대해 자세히 알아보려면 web.dev 문서 [사용자 중심 성능 지수 를](https://web.dev/articles/user-centric-performance-metrics) 참조하세요. +뉴렐릭은 Google의 [`web-vitals` API 라이브러리를](https://github.com/GoogleChrome/web-vitals) 활용하여 추가 계산을 도입하지 않고 원시 상태의 웹 필수 정보를 수집합니다. CWV가 중요한 이유와 계산 방법에 대해 자세히 알아보려면 web.dev 문서 [사용자 중심 성과 지표를](https://web.dev/articles/user-centric-performance-metrics) 참조하세요. -## New Relic에서 핵심 웹 바이탈 찾기 [#view-data-in-nr] +## 뉴렐릭에서 CWV 찾기 [#view-data-in-nr] -코어 웹 바이탈은 많은 뉴렐릭 기능에 내장되어 있지만 웹 바이탈을 높은 수준에서 보는 가장 좋은 방법은 다음과 같습니다. +CWV는 많은 뉴렐릭 기능에 내장되어 있지만, 웹 바이탈을 높은 수준에서 보는 가장 좋은 방법은 다음과 같습니다. -1. **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Browser** 으)로 이동합니다. +1. **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Browser** 으)로 이동합니다. 2. 앱을 선택하세요. @@ -140,153 +142,56 @@ Google은 다음 세 가지 지표를 기준으로 전반적인 웹사이트 성 **웹 바이탈** 페이지에는 전체 웹사이트에 대한 웹 바이탈 평균이 표시됩니다. 이 보기에서 특정 페이지나 지표를 드릴다운하여 점수에 영향을 미치는 요소를 확인할 수 있습니다. - overview of the web vitals page + overview of the web vitals page ### 특정 페이지로 드릴다운 [#drill-down] -인사이트를 중요한 페이지(예: 전자상거래 결제 페이지)로 이동하려면 **Page URL** 표에서 찾으세요. 최종 사용자가 사이트의 해당 영역을 어떻게 경험하고 있는지 이해하는 데 사용할 수 있는 코어 웹 바이탈에 기여하는 내용에 대한 분석을 볼 수 있습니다. 예를 들어 Chrome 브라우저에서 성능 저하 패턴이 발견되면 해당 사용자 기반에 대한 향후 개선 사항을 선별할 수 있습니다. +인사이트를 중요한 페이지(예: 전자상거래 결제 페이지)로 이동하려면 **Page URL** 테이블에서 찾으세요. 사이트의 특정 영역을 최종 사용자가 어떻게 경험하고 있는지 파악하는 데 도움이 되는 CWV에 기여하는 요소에 대한 세부 정보를 확인할 수 있습니다. 예를 들어 Chrome 브라우저에서 성능 저하 패턴이 발견되면 해당 사용자 기반에 대한 향후 개선 사항을 정리할 수 있습니다. -Click on a page URL to see page-specific web vitals. +Click on a page URL to see page-specific web vitals.
- **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Browser > (select an app) > Monitor > Web vitals > (click on a page URL)**: 가장 영향력 있는 웹페이지에 대한 코어 웹 바이탈 분석을 확인하세요. + **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Browser > (select an app) > Monitor > Web vitals > (click a page URL)**: 가장 영향력 있는 웹페이지의 CWV 분석을 확인하세요.
### 주요 속성으로 필터링 [#key-attributes] -백앤드 변경이나 성능 문제가 코어 웹 바이탈에 어떤 영향을 미치는지와 같은 특정 내용을 조사하려는 경우 **Filter by** 도구를 사용하여 주요 속성을 필터링할 수 있습니다. +백앤드 변경이나 문제가 CWV에 어떤 영향을 미쳤는지 등 특정한 사항을 조사하고 싶다면 **Filter by** 도구를 사용하여 주요 속성을 필터링할 수 있습니다. -Filter by key attributes +Filter by key attributes
- **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Browser > (select an app) > Monitor > Web vitals > (add filters)**: 필터 도구를 사용하여 핵심 속성별로 코어 웹 바이탈을 필터링할 수 있습니다. + **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Browser > (select an app) > Monitor > Web vitals > (add filters)**: 필터 도구를 사용하여 핵심 속성별로 코어 웹 바이탈을 필터링할 수 있습니다.
거의 모든 주요 속성으로 필터링할 수 있지만 몇 가지 유용한 예를 읽으십시오. - - 데스크톱과 모바일 성능을 비교하고 두 플랫폼 간의 코어 웹 바이탈 차이점을 비교하고 싶다고 가정해 보겠습니다. **Web vitals** 에서 이를 조사하려면 다음을 수행하세요. - - 1. - **Filter by** - - - 필드에서 - - - **Attribute** - - - `deviceType` 로 설정하고 - - - **Value** - - - `desktop` 로 설정합니다. + + 데스크톱과 모바일의 성능을 비교하고, 두 플랫폼 간의 CWV가 어떻게 다른지 살펴보겠습니다. **Web vitals** 에서 이를 조사하려면: - 2. 중복 브라우저에서 - - - **Attribute** - - - `deviceType` 로, - - - **Value** - - - `mobile` 로 설정한 다음 결과를 비교합니다. + 1. **Filter by** 필드에서 **Attribute** `deviceType` 로 설정하고 **Value** `desktop` 로 설정합니다. + 2. 중복 브라우저에서 **Attribute** `deviceType` 로, **Value** `mobile` 로 설정한 다음 결과를 비교합니다. - + 최종 사용자가 11월 1일 오후 12시경 사이트 결제 페이지에서 성능 문제를 보고했고 이 사용자에게 어떤 일이 발생했는지 확인하려고 한다고 가정해 보겠습니다. **Web vitals** 에서 이를 조사하려면 다음을 수행하세요. 1. 시간 범위를 11월 1일 오전 11시에서 오후 1시 사이로 설정합니다. + 2. **Page URL** 표에서 결제 페이지 URL을 클릭합니다. + 3. **Filter by** 필드에서 **Attribute** `userID` 로 설정하고 **Value** `user ID` 로 설정합니다. - 2. - **Page URL** - - - 표에서 결제 페이지 URL을 클릭합니다. - - 3. - **Filter by** - - - 필드에서 - - - **Attribute** - - - `userID` 로 설정하고 - - - **Value** - - - `user ID` 로 설정합니다. - - - `userID` [브라우저 SPA API](/docs/browser/new-relic-browser/browser-agent-spa-api/setcustomattribute-browser-agent-api/) 를 사용하여 설정해야 하는 맞춤 속성입니다. `userID` 을(를) 사용할 수 없는 경우 `username` 또는 `session` 와 같은 다른 사용자 정보로 필터링할 수도 있습니다. - + + `userID` [브라우저 SPA API](/docs/browser/new-relic-browser/browser-agent-spa-api/setcustomattribute-browser-agent-api/) 를 사용하여 설정해야 하는 맞춤 속성입니다. `userID` 을(를) 사용할 수 없는 경우 `username` 또는 `session` 와 같은 다른 사용자 정보로 필터링할 수도 있습니다. + - - 귀하의 조직이 최근 11월 10일 오전 8시에 사이트 홈 페이지의 이미지를 업데이트했으며 변경 사항이 코어 웹 바이탈에 영향을 미쳤는지 확인하고 싶다고 가정해 보겠습니다. **Web vitals** 에서 이를 조사하려면 다음을 수행하세요. + + 예를 들어, 귀하의 조직이 11월 10일 오전 8시에 사이트 홈페이지의 이미지를 업데이트했고, 이 변경 사항이 CWV에 영향을 미치는지 보고 싶다고 가정해 보겠습니다. **Web vitals** 에서 이를 조사하려면: 1. 시간 범위를 11월 10일 오전 7시에서 오전 9시 사이로 설정합니다. - - 2. - **Page URL** - - - 테이블에서 홈페이지 URL을 클릭합니다. - - 3. - **Filter by** - - - 필드에서 - - - **Attribute** - - - `elementTagName` 로 설정하고 - - - **Value** - - - `IMG` 로 설정합니다. + 2. **Page URL** 테이블에서 홈페이지 URL을 클릭합니다. + 3. **Filter by** 필드에서 **Attribute** `elementTagName` 로 설정하고 **Value** `IMG` 로 설정합니다. @@ -294,43 +199,32 @@ Google은 다음 세 가지 지표를 기준으로 전반적인 웹사이트 성 New Relic은 주어진 페이지에서 사용자 세션에 대한 데이터를 캡처합니다. 세션 추적은 임의로 샘플링되어 사용자가 페이지 로드 타이밍 문제, JavaScript 이벤트 또는 기타 오류를 경험한 방식을 볼 수 있습니다. -Session traces in Browser UI lets you look at real user sessions for a given page +Session traces in Browser UI lets you look at real user sessions for a given page -세션 추적을 사용하여 여러 사용자 세션에서 패턴을 찾는 것이 좋습니다. 핵심 웹 바이탈 점수 중 하나를 개선할 수 있는 경우 한 가지 옵션은 세션 추적을 살펴보고 여러 사용자 세션에서 공유되는 공통 속성을 확인하는 것입니다. 다음은 세션 추적이 사이트를 개선하는 데 어떻게 도움이 되는지에 대한 예입니다. +다양한 사용자 세션에서 패턴을 찾으려면 세션 트레이스를 사용하는 것이 좋습니다. CWV 점수 중 하나를 개선할 수 있다면, 세션 트레이스를 살펴보고 다양한 사용자 세션에서 공유되는 공통 속성을 확인하는 것이 한 가지 방법입니다. 세션 트레이스가 사이트 개선에 어떻게 도움이 될 수 있는지 보여주는 예는 다음과 같습니다. -1. - **Web vitals** - +1. **Web vitals** 탭에서 실적이 저조한 페이지를 클릭합니다. 위 이미지를 예로 들면 귀하의 사이트는 전반적인 LCP 점수가 좋지만 일부 개별 페이지에는 개선이 필요하다는 것을 알 수 있습니다. +2. **Web vitals** 페이지의 **Page URLs** 섹션을 보면 홈페이지 URL의 LCP 점수가 4초보다 큰 것을 알 수 있습니다. 모든 사용자에게 영향을 미치는 오류로 인한 것입니까, 아니면 한 종류의 사용자에게만 영향을 미치는 것입니까? 예를 들어, 특정 버전의 Chrome 또는 특정 운영 시스템을 사용하는 사용자가 페이지 로드 시간이 느린 것을 발견한 경우 문제의 특정 원인을 더 효과적으로 해결할 수 있습니다. +3. 문제를 해결하려는 URL을 클릭하면 새 창이 열립니다. LCP 점수가 사이트의 전체 LCP 점수보다 훨씬 높다는 것을 알게 되었습니다. 이 페이지 하단의 **Session traces** 섹션으로 스크롤하면 실제 사용자 세션의 다양한 샘플을 볼 수 있습니다. 이러한 세션을 통해 사용자가 AJAX 요청, DOM 로드 관련 문제, JavaScript 이벤트 또는 기타 오류를 경험한 방식에 대한 보다 세부적인 세부 정보를 제공할 수 있습니다. - 탭에서 실적이 저조한 페이지를 클릭합니다. 위 이미지를 예로 들면 귀하의 사이트는 전반적인 LCP 점수가 좋지만 일부 개별 페이지에는 개선이 필요하다는 것을 알 수 있습니다. +무작위 세션의 데이터는 수백 또는 수천 건의 웹 페이지 사용자 상호 작용에서 패턴을 찾는 데 도움이 됩니다. 무작위로 선택된 이 데이터에 패턴이 나타나면 문제 해결 계획이 페이지 점수를 향상시킬 것이라는 확신을 가질 수 있습니다. -2. - **Web vitals** - +## 세션 리플레이로 이해도를 높여보세요 [#session-replays] - 페이지의 +낮은 LCP 또는 높은 CLS가 확인된 경우 세션 리플레이는 발생한 사건에 대한 시각적 기록을 제공하여 문제를 일으키는 정확한 요소나 이벤트를 빠르게 찾아내는 데 도움이 됩니다. - - **Page URLs** - +다음은 세션 리플레이가 사이트 개선에 어떻게 도움이 될 수 있는지에 대한 예입니다. - 섹션을 보면 홈페이지 URL의 LCP 점수가 4초보다 큰 것을 알 수 있습니다. 모든 사용자에게 영향을 미치는 오류로 인한 것입니까, 아니면 한 종류의 사용자에게만 영향을 미치는 것입니까? 예를 들어, 특정 버전의 Chrome 또는 특정 운영 시스템을 사용하는 사용자가 페이지 로드 시간이 느린 것을 발견한 경우 문제의 특정 원인을 더 효과적으로 해결할 수 있습니다. +1. 성능 문제 식별: **Web vitals** 페이지에서 관련 URL을 클릭하여 자세한 성능 보기를 엽니다. 이 작업을 수행하면 해당 페이지의 웹 중요 정보를 자세히 볼 수 있는 페이지로 리디렉션됩니다. CWV 점수를 검토하여 **Needs improvement** 또는 **Poor** 레이블이 있는 점수를 찾아보세요. 플랫폼마다 성능 문제가 상당히 다를 수 있으므로 장치 유형이나 브라우저별로 결과를 필터링할 수도 있습니다. 이러한 세부 사항을 이해하면 최적화가 필요한 특정 영역을 정확히 파악하는 데 도움이 됩니다. -3. 문제를 해결하려는 URL을 클릭하면 새 창이 열립니다. LCP 점수가 사이트의 전체 LCP 점수보다 훨씬 높다는 것을 알게 되었습니다. 이 페이지 하단의 +2. 관련 리플레이에 액세스하려면 조사 중인 데이터 포인트의 **Session replays** 열에 있는 숫자를 클릭하세요. 이 작업을 수행하면 특정 성능 문제가 발생한 세션을 표시하기 위해 리플레이가 자동으로 필터링됩니다. 예를 들어, LCP가 낮은 페이지의 세션 리플레이 수를 클릭하면 LCP가 느렸던 세션 목록이 표시됩니다. - - **Session traces** - +3. 시청하고 진단하세요: 비디오 녹화를 시청하여 문제를 시각적으로 이해하세요. 당신은 다음을 발견할 수 있습니다: - 섹션으로 스크롤하면 실제 사용자 세션의 다양한 샘플을 볼 수 있습니다. 이러한 세션을 통해 사용자가 AJAX 요청, DOM 로드 관련 문제, JavaScript 이벤트 또는 기타 오류를 경험한 방식에 대한 보다 세부적인 세부 정보를 제공할 수 있습니다. + * LCP 문제: 큰 히어로 이미지나 비디오가 느리게 로드되어 몇 초 동안 빈 화면이 나타납니다. + * CLS 문제: 광고나 타사 콘텐츠가 늦게 로드되어 페이지 콘텐츠가 예기치 않게 이동하는 문제입니다. + * INP 문제: 느리게 반응하는 버튼이나 대화형 요소는 좌절감을 유발할 수 있습니다. -무작위 세션의 데이터는 수백 또는 수천 건의 웹 페이지 사용자 상호 작용에서 패턴을 찾는 데 도움이 됩니다. 무작위로 선택된 이 데이터에 패턴이 나타나면 문제 해결 계획이 페이지 점수를 향상시킬 것이라는 확신을 가질 수 있습니다. +세션 트레이스의 기술 데이터를 세션 리플레이의 시각적 컨텍스트와 결합함으로써 성능 문제를 해결하고 최종 사용자 환경을 크게 향상시키는 포괄적인 계획을 개발할 수 있습니다. - + \ No newline at end of file diff --git a/src/i18n/content/kr/docs/tutorial-manage-large-log-volume/organize-large-logs.mdx b/src/i18n/content/kr/docs/tutorial-manage-large-log-volume/organize-large-logs.mdx index 2ee323ff045..41ab8b54db8 100644 --- a/src/i18n/content/kr/docs/tutorial-manage-large-log-volume/organize-large-logs.mdx +++ b/src/i18n/content/kr/docs/tutorial-manage-large-log-volume/organize-large-logs.mdx @@ -33,9 +33,9 @@ translationType: machine 사전 구문 분석: - ``` + ```json { - "message": "32 4329 store_Portland" + "message": "32 4329 store_Portland" } @@ -45,11 +45,11 @@ translationType: machine 구문 분석 후: - ``` + ```json { - "transaction_total": "32", - "purchase_number": "4329", - "store_location": "store_Portland", + "transaction_total": "32", + "purchase_number": "4329", + "store_location": "store_Portland", } ``` @@ -120,9 +120,9 @@ ACME Corp에서 앞으로 몇 달 동안 약 2TB의 로그를 수집할 것임 이 문서의 앞부분에서 사용한 예제로 작업해 보겠습니다. 다음 패턴을 따르는 로그가 있습니다. - ``` + ```json { - "message": "32 4329 store_Portland" + "message": "32 4329 store_Portland" } ``` @@ -136,11 +136,11 @@ ACME Corp에서 앞으로 몇 달 동안 약 2TB의 로그를 수집할 것임 위의 패턴으로 구문 분석 규칙이 생성되면 다음과 같은 방식으로 로그를 반환합니다. - ``` + ```json { - "transaction_total": "32", - "purchase_number": "4329", - "store_location": "store_Portland", + "transaction_total": "32", + "purchase_number": "4329", + "store_location": "store_Portland", } ``` diff --git a/src/i18n/content/pt/docs/apis/nerdgraph/examples/nerdgraph-scorecards-custom-tutorial.mdx b/src/i18n/content/pt/docs/apis/nerdgraph/examples/nerdgraph-scorecards-custom-tutorial.mdx index acbc498ce59..aeaf0a92c25 100644 --- a/src/i18n/content/pt/docs/apis/nerdgraph/examples/nerdgraph-scorecards-custom-tutorial.mdx +++ b/src/i18n/content/pt/docs/apis/nerdgraph/examples/nerdgraph-scorecards-custom-tutorial.mdx @@ -98,24 +98,23 @@ O New Relic fornece várias mutações do NerdGraph para criar funções persona #### Solicitação de amostra ```graphql - { + { customerAdministration { - permissions(filter: {scope: {eq: "organization"}}) { - items { - feature - category - id - product - } + permissions(filter: { scope: { eq: "organization" } }) { + items { + feature + category + id + product } } } - + } ``` #### Resposta de amostra - ```graphql + ```json { "data": { "customerAdministration": { @@ -174,31 +173,28 @@ O New Relic fornece várias mutações do NerdGraph para criar funções persona } } } - ``` Copie e cole as informações relacionadas aos Scorecards em um arquivo de texto que corresponda aos seguintes critérios: * `category: MANAGE` - * `"feature"``: "Scorecards"` ou `“Scorecards Rules”` + * `"feature"``: "Scorecards"` ou `"Scorecards Rules"` Por exemplo, na resposta anterior, o seguinte corresponde aos critérios: - ```graphql - + ```json { - "category": "MANAGE", - "feature": "Scorecards Rules", - "id": "xxxxx", - "product": "New Relic One" - }, + "category": "MANAGE", + "feature": "Scorecards Rules", + "id": "xxxxx", + "product": "New Relic One" + }, { - "category": "MANAGE", - "feature": "Scorecards", - "id": "xxxxx", - "product": "New Relic One" - } - + "category": "MANAGE", + "feature": "Scorecards", + "id": "xxxxx", + "product": "New Relic One" + } ``` @@ -208,19 +204,18 @@ O New Relic fornece várias mutações do NerdGraph para criar funções persona #### Solicitação de amostra ```graphql - { + { actor { organization { id - } } } - + } ``` #### Resposta de amostra - ```graphql + ```json { "data": { "actor": { @@ -230,7 +225,6 @@ O New Relic fornece várias mutações do NerdGraph para criar funções persona } } } - ``` Copie o ID da organização e reserve-o para criar uma função. @@ -323,11 +317,11 @@ O New Relic fornece várias mutações do NerdGraph para criar funções persona
- `PermissionId` + `permissionIds` - Interno + \[Int] @@ -370,10 +364,9 @@ O New Relic fornece várias mutações do NerdGraph para criar funções persona #### Solicitação de amostra ```graphql - mutation { customRoleCreate( - container: {id: "xxx****xxx-xx**00**-xxx-x*x*-xx**XXX**XX", type: "organization"} + container: { id: "xxx****xxx-xx**00**-xxx-x*x*-xx**XXX**XX", type: "organization" } name: "Scorecards manager" permissionIds: [xxxxx, xxxxx] scope: "organization" @@ -381,13 +374,11 @@ O New Relic fornece várias mutações do NerdGraph para criar funções persona id } } - ``` #### Resposta de amostra - ```graphql - + ```json { "data": { "customRoleCreate": { @@ -395,7 +386,6 @@ O New Relic fornece várias mutações do NerdGraph para criar funções persona } } } - ``` @@ -487,10 +477,9 @@ O New Relic fornece várias mutações do NerdGraph para criar funções persona #### Solicitação de amostra ```graphql - { customerAdministration { - groups(filter: {organizationId: {eq: "xxx****xxx-xx**00**-xxx-x*x*-xx**XXX**XX"}}) { + groups(filter: { organizationId: { eq: "xxx****xxx-xx**00**-xxx-x*x*-xx**XXX**XX" } }) { nextCursor items { id @@ -505,7 +494,6 @@ O New Relic fornece várias mutações do NerdGraph para criar funções persona } } } - ``` Na lista de IDs de grupo exibida, copie o ID de grupo desejado para associar a função do Scorecard personalizada que você criou anteriormente. @@ -552,11 +540,7 @@ O New Relic fornece várias mutações do NerdGraph para criar funções persona @@ -585,7 +569,10 @@ O New Relic fornece várias mutações do NerdGraph para criar funções persona ```graphql mutation { authorizationManagementGrantAccess( - grantAccessOptions: {organizationAccessGrants: {roleId: "99999999"}, groupId: "xxx****xxx-xx**00**-xxx-x*x*-xx**XXX**XX"} + grantAccessOptions: { + organizationAccessGrants: { roleId: "99999999" } + groupId: "xxx****xxx-xx**00**-xxx-x*x*-xx**XXX**XX" + } ) { roles { id @@ -597,12 +584,11 @@ O New Relic fornece várias mutações do NerdGraph para criar funções persona } } } - ``` #### Resposta de amostra - ```graphql + ```json { "data": { "authorizationManagementGrantAccess": { @@ -619,7 +605,6 @@ O New Relic fornece várias mutações do NerdGraph para criar funções persona } } } - ``` diff --git a/src/i18n/content/pt/docs/apis/synthetics-rest-api/monitor-examples/manage-synthetics-monitors-rest-api.mdx b/src/i18n/content/pt/docs/apis/synthetics-rest-api/monitor-examples/manage-synthetics-monitors-rest-api.mdx index 582beece6ac..669eda5d8e8 100644 --- a/src/i18n/content/pt/docs/apis/synthetics-rest-api/monitor-examples/manage-synthetics-monitors-rest-api.mdx +++ b/src/i18n/content/pt/docs/apis/synthetics-rest-api/monitor-examples/manage-synthetics-monitors-rest-api.mdx @@ -351,7 +351,6 @@ Além da API geral, existem vários métodos de API para o browser com script (` ```sh scriptPayload='{"scriptText":BASE64 encoded string}' - curl -v -X PUT \ -H "Api-Key:$API_KEY" \ -H 'Content-Type: application/json' \ @@ -394,12 +393,12 @@ Além da API geral, existem vários métodos de API para o browser com script (` Este exemplo usa `password` como senha para `scriptLocation`: - ``` + ```shell curl -v - -X PUT -H "Api-Key:$API_KEY" - -H 'content-type: application/json' - $API_ENDPOINT/v3/monitors/$MONITOR_ID/script - -d \ + -X PUT -H "Api-Key:$API_KEY" + -H 'content-type: application/json' + $API_ENDPOINT/v3/monitors/$MONITOR_ID/script + -d \ '{ "scriptText": "dmFyIGFzc2VydCA9IHJlcXVpcmUoJ2Fzc2VydCcpOw0KYXNzZXJ0LmVxdWFsKCcxJywgJzEnKTs=", "scriptLocations": [{ @@ -469,7 +468,7 @@ Aqui está um exemplo de uso da API REST da New Relic e do script bash para cria Em alguns casos, você pode querer usar `-w 0`, o que desativará a quebra de linha: `base64 -w 0 $scriptfile` - ```bash + ```sh #!/bin/bash # API key from your account settings diff --git a/src/i18n/content/pt/docs/apm/agents/java-agent/troubleshooting/ssl-or-connection-errors-java.mdx b/src/i18n/content/pt/docs/apm/agents/java-agent/troubleshooting/ssl-or-connection-errors-java.mdx index 594ca5eb13a..46c0ac66007 100644 --- a/src/i18n/content/pt/docs/apm/agents/java-agent/troubleshooting/ssl-or-connection-errors-java.mdx +++ b/src/i18n/content/pt/docs/apm/agents/java-agent/troubleshooting/ssl-or-connection-errors-java.mdx @@ -39,7 +39,7 @@ Você pode baixar o [DigiCert Global Root CA](https://www.digicert.com/kb/digice Para importar o certificado para seu armazenamento confiável, use este comando ou consulte [a documentação Java SE da Oracle para keytool](https://docs.oracle.com/javase/6/docs/technotes/tools/solaris/keytool.html): -``` +```sh keytool -importcert -alias ca_alias -file ca_file.pem -keystore truststore.ts -storepass ts_password ``` @@ -113,4 +113,4 @@ Provavelmente, isso está relacionado a esse [problema do JDK](https://bugs.open ### Solução B [#log-exception-solution] -Examine e valide se o cabeçalho e o rodapé dos seus certificados não possuem espaços em branco à direita. Se o fizerem, edite ou use certificados diferentes. +Examine e valide se o cabeçalho e o rodapé dos seus certificados não possuem espaços em branco à direita. Se o fizerem, edite ou use certificados diferentes. \ No newline at end of file diff --git a/src/i18n/content/pt/docs/apm/agents/nodejs-agent/installation-configuration/nodejs-agent-configuration.mdx b/src/i18n/content/pt/docs/apm/agents/nodejs-agent/installation-configuration/nodejs-agent-configuration.mdx index f25487cde5b..9b4a26735d7 100644 --- a/src/i18n/content/pt/docs/apm/agents/nodejs-agent/installation-configuration/nodejs-agent-configuration.mdx +++ b/src/i18n/content/pt/docs/apm/agents/nodejs-agent/installation-configuration/nodejs-agent-configuration.mdx @@ -824,10 +824,20 @@ Esta seção define as variáveis do agente Node.js na ordem em que normalmente
- O ID da função personalizada criado na seção - - [Função personalizada]() - - . + O ID da função personalizada criado na seção Função personalizada.
- Caminho completo para o log do agente New Relic, incluindo o nome do arquivo. O padrão é `filepath: require('path').join(process.cwd(), 'newrelic_agent.log')`. O agente encerrará o processo se não conseguir criar este arquivo. O agente cria um arquivo de log com as mesmas permissões que o processo pai do agente Node.js. + Caminho completo para o log do agente New Relic, incluindo o nome do arquivo. O padrão é `filepath: require('path').join(process.cwd(), 'newrelic_agent.log')`. Se o agente não puder criar o arquivo de log, então ele: + + * Registra o erro `New Relic failed to open log file` usando `console.error`. + * Armazena em buffer todas as mensagens subsequentes do log na memória. + * Quando o buffer de memória atinge seu limite de 128 MiB, o agente descarta qualquer nova mensagem do log e emite o seguinte aviso via `process.emitWarning`: `[NRWARN001] NewRelicWarning: Dropping log message, buffer would overflow.` + + Ao criar o arquivo de log, o agente define as permissões do arquivo como 0o600 (legível/gravável para o proprietário). * Para gravar todos os registros em **stdout**, defina como `stdout`. * Para gravar todos os registros em **stderr**, defina como `stderr`. + + + Em versões do agente anteriores à 7.0.0, o agente encerrava o processo se não conseguisse criar esse arquivo. + diff --git a/src/i18n/content/pt/docs/browser/new-relic-browser/browser-apis/addpageaction.mdx b/src/i18n/content/pt/docs/browser/new-relic-browser/browser-apis/addpageaction.mdx index 61a90cfefd3..ad4d754943d 100644 --- a/src/i18n/content/pt/docs/browser/new-relic-browser/browser-apis/addpageaction.mdx +++ b/src/i18n/content/pt/docs/browser/new-relic-browser/browser-apis/addpageaction.mdx @@ -45,7 +45,7 @@ Relata um evento PageAction do browser junto com um nome e um atributo opcional. Esta chamada de API envia um [evento`PageAction` ](/docs/insights/explore-data/custom-events/insert-browser-custom-events-attributes-insights-javascript-api)do browser com seu nome definido pelo usuário e um atributo opcional para [o dashboard](/docs/query-your-data/explore-query-data/dashboards/introduction-new-relic-one-dashboards), junto com [vários atributo padrão](/attribute-dictionary/?event=PageAction). Isso é útil para rastrear qualquer evento que ainda não tenha sido rastreado automaticamente pelo agente browser, como clicar em um botão **Subscribe** ou acessar um tutorial. * `PageAction` evento são enviados a cada 30 segundos. -* Se 1.000 eventos forem observados, o agente coletará o evento armazenado em buffer imediatamente, ignorando o intervalo do ciclo de coleta. +* Se 1.000 eventos forem observados ou se o tamanho da carga de coleta for maior que 16 KB, o agente coletará o evento em buffer imediatamente, ignorando o intervalo do ciclo de coleta. Em versões anteriores do agente, os eventos eram descartados após 120 serem observados. O limite de eventos foi aumentado de 120 para 1.000 na versão [1.264.0](https://docs.newrelic.com/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.264.0/) e não são mais descartados. diff --git a/src/i18n/content/pt/docs/browser/new-relic-browser/browser-apis/recordCustomEvent.mdx b/src/i18n/content/pt/docs/browser/new-relic-browser/browser-apis/recordCustomEvent.mdx index fa2be84c27a..7d9dde7ce36 100644 --- a/src/i18n/content/pt/docs/browser/new-relic-browser/browser-apis/recordCustomEvent.mdx +++ b/src/i18n/content/pt/docs/browser/new-relic-browser/browser-apis/recordCustomEvent.mdx @@ -45,7 +45,7 @@ Relata um evento de browser personalizado sob um eventType especificado com atri Esta chamada de API envia um evento de browser personalizado com seu eventType definido pelo usuário e atributo opcional para [dashboard](/docs/query-your-data/explore-query-data/dashboards/introduction-new-relic-one-dashboards), junto com qualquer atributo personalizado que você possa ter definido para seu aplicativo. Isso é útil para rastrear qualquer evento que ainda não seja rastreado automaticamente pelo browser do agente, aprimorado pelas regras e atribuições que você controla. * `custom` evento são enviados a cada 30 segundos. -* Se 1.000 eventos forem observados, o agente coletará o evento armazenado em buffer imediatamente, ignorando o intervalo do ciclo de coleta. +* Se 1.000 eventos forem observados ou se o tamanho da carga de coleta for maior que 16 KB, o agente coletará o evento em buffer imediatamente, ignorando o intervalo do ciclo de coleta. ## Parâmetro [#parameters] diff --git a/src/i18n/content/pt/docs/browser/new-relic-browser/page-load-timing-resources/instrumentation-browser-monitoring.mdx b/src/i18n/content/pt/docs/browser/new-relic-browser/page-load-timing-resources/instrumentation-browser-monitoring.mdx index 01d35f12d27..1eb7784e220 100644 --- a/src/i18n/content/pt/docs/browser/new-relic-browser/page-load-timing-resources/instrumentation-browser-monitoring.mdx +++ b/src/i18n/content/pt/docs/browser/new-relic-browser/page-load-timing-resources/instrumentation-browser-monitoring.mdx @@ -160,7 +160,7 @@ Para ambas as páginas https **and** http, transmitimos dados via htt 		- Os dados são enviados 10 segundos após o carregamento inicial da página e, a seguir, a cada 30 segundos. + Os dados são enviados 10 segundos após o carregamento inicial da página e, depois, a cada 30 segundos. Se o tamanho da carga útil da coleta for maior que 16 KB, os dados serão enviados antecipadamente.
- `PageViewTiming` evento são coletados por todos os agentes e incluem dados de tempo, como medições core web vitals . A primeira coleta ocorre 10 segundos após o evento de ciclo de vida da página `load` . Coletas adicionais ocorrem a cada 30 segundos, conforme necessário, quando há dados para enviar. Consulte a [documentação do PageViewTiming](/docs/browser/new-relic-browser/page-load-timing-resources/pageviewtiming-async-or-dynamic-page-details/#interactivity-metrics) para obter uma lista de eventos relatados. + `PageViewTiming` Os eventos são coletados por todos os agentes e incluem dados de tempo, como medições essenciais do web vitals. A primeira colheita ocorre 10 segundos após o evento do ciclo de vida da página `load` . Coletas adicionais ocorrem a cada 30 segundos, conforme necessário, quando há dados para enviar ou se o tamanho da carga útil da coleta for maior que 16 KB. Consulte a [documentação do PageViewTiming](/docs/browser/new-relic-browser/page-load-timing-resources/pageviewtiming-async-or-dynamic-page-details/#interactivity-metrics) para obter uma lista de eventos relatados.
- `PageAction` os eventos são coletados após o evento de ciclo de vida da página `load` . As coletas subsequentes acontecem a cada 30 segundos. + `PageAction` evento são coletados após o ciclo de vida da página `load` evento. Coletas subsequentes ocorrem a cada 30 segundos ou se o tamanho da carga de coleta for maior que 16 KB.
+ + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Chave YAML + + Descrição +
+ `url` + + URL para solicitar dados +
+ `token` + + Used to authenticate to the endpoint. +
+ `engine` + + Specify **`kv1`** or **`kv2`**. +
+ +In the configuration file, each secret stored in Vault can be accessed by setting a placeholder with: + +* **source\_name**: The name of the Vault source defined in `secrets_providers`. +* **mount**: The name of the secrets engine mount. +* **path**: The specific path to the secret. +* **specific key**: The specific key within the secret to be retrieved. + +Example of full placeholder format: + +``` +"${nr-vault:source_name:my_mount:my_path:my_value}" +``` + +### Kubernetes secrets + +If the agent-control pod has permissions, such as through a Service Account and Role-Based Access Control (RBAC), to access the required secrets and namespaces, Agent control can directly access secrets from the Kubernetes API without needing a separate sources configuration. + +In the agent configuration file, retrieve each secret value using a placeholder specifying: + +* **namespace**: The Kubernetes namespace where the secret is located. +* **name**: The name of the Kubernetes secret object. +* **specific key**: The specific key within the secret from which to retrieve the value. + +For example, use the placeholder format: + +``` +"${nr-kubesec:my_namespace:my_secret:my_value}" +``` + +## Configuração de repositório privado + +O agente Control suporta a configuração do repositório Helm privado para implantar o próprio agente Control e o agente gerenciado. Isso permite ambientes onde os gráficos do New Relic Helm não são diretamente acessíveis. - When using private Helm repositories, the charts need to be compatible and the referenced images within the charts must be reachable. If not, the agents will not work as expected. + Ao usar o repositório privado Helm, os gráficos precisam ser compatíveis e as imagens referenciadas dentro dos gráficos devem ser acessíveis. Caso contrário, o agente não trabalhará como esperado. -### 1. Enable private repositories for agents +### 1. Habilite repositório privado para agente -For security reasons, only explicitly enabled repositories will be allowed in remote configurations. To enable specific repositories, you need to update the Agent Control configuration: +Por razões de segurança, somente o repositório explicitamente habilitado será permitido na configuração remota. Para habilitar repositório específico, é necessário atualizar a configuração do agente Control: - + ```yaml # values-newrelic.yaml @@ -371,7 +512,7 @@ For security reasons, only explicitly enabled repositories will be allowed in re -The allowed repository configurations can then be used in your remote configurations within New Relic Control. Example: +A configuração do repositório permitida pode então ser usada em sua configuração remota dentro do New Relic Control. Exemplo: ```yaml chart_version: "1.2.3" @@ -380,19 +521,19 @@ chart_repository: name: "my-chart-name" # Optional: use only if the chart name doesn't match New Relic's chart name ``` -Additionally, you need to configure Agent Control's Helm installation to use your private repository if the `agent-control` chart itself is in a private repository. This is separate from the configuration for managed agents. Refer to the `agent-control` Helm chart [values.yaml](https://github.com/newrelic/helm-charts/blob/master/charts/agent-control/values.yaml) to set up the `installationJob` section. Specifically: +Além disso, você precisa configurar a instalação Helm do agente Control para usar seu repositório privado se o próprio gráfico `agent-control` estiver em um repositório privado. Isso é separado da configuração do agente gerenciado. Consulte `agent-control` Helm chart [values.yaml](https://github.com/newrelic/helm-charts/blob/master/charts/agent-control/values.yaml) para configurar a seção `installationJob`. Especificamente: -* `chartRepositoryUrl` containing your repository URL -* `name` if using a different chart name -* `repositorySecretReferenceName` and `repositoryCertificateSecretReferenceName` for authentication (see the authentication section below for details) +* `chartRepositoryUrl` contendo a URL do seu repositório +* `name` se estiver usando um nome de gráfico diferente +* `repositorySecretReferenceName` e `repositoryCertificateSecretReferenceName` para autenticação (veja a seção de autenticação abaixo para detalhes) -### 2. Set up authentication for private repositories +### 2. Configure autenticação para repositório privado -You need to set up additional resources to enable authentication for accessing your private repository: +Você precisa configurar recursos adicionais para habilitar a autenticação para acessar seu repositório privado: - To authenticate using basic authentication (username and password), you need to create a secret in the Agent Control namespace containing the expected values in `data.username` and `data.password`. + Para autenticar usando autenticação básica (nome de usuário e senha), você precisa criar um segredo no namespace do agente Control contendo os valores esperados em `data.username` e `data.password`. Exemplo: @@ -406,9 +547,9 @@ You need to set up additional resources to enable authentication for accessing y password: "myPassword" ``` - For more details, see the [Flux documentation](https://fluxcd.io/flux/components/source/helmrepositories/#secret-reference). + Para mais detalhes, consulte a [documentação do Flux](https://fluxcd.io/flux/components/source/helmrepositories/#secret-reference). - When using basic authentication, the remote configuration should be configured as follows: + Ao usar a autenticação básica, a configuração remota deve ser definida da seguinte maneira: ```yaml chart_repository: @@ -418,13 +559,13 @@ You need to set up additional resources to enable authentication for accessing y ``` - - To authenticate using TLS, you need to create a secret containing: + + Para autenticar usando TLS, você precisa criar um segredo contendo: - * `tls.crt` and `tls.key`: client certificate and private key used for TLS client authentication - * `ca.crt`: CA certificate used to verify the server (required if the server uses a self-signed certificate) + * `tls.crt` e `tls.key`: certificado do cliente e chave privada usados para autenticação do cliente TLS + * `ca.crt`: Certificado CA usado para verificar o servidor (obrigatório se o servidor usar um certificado autoassinado) - The Secret should be of type `Opaque` or `kubernetes.io/tls`. All files in the Secret are expected to be PEM-encoded. + O segredo deve ser do tipo `Opaque` ou `kubernetes.io/tls`. Espera-se que todos os arquivos no Secret sejam codificados em PEM. Exemplo: @@ -442,9 +583,9 @@ You need to set up additional resources to enable authentication for accessing y ca.crt: ``` - For more details, see the [Flux documentation](https://fluxcd.io/flux/components/source/helmrepositories/#secret-reference). + Para mais detalhes, consulte a [documentação do Flux](https://fluxcd.io/flux/components/source/helmrepositories/#secret-reference). - When using TLS certificate authentication, the remote configuration should be configured as follows: + Ao usar a autenticação de certificado TLS, a configuração remota deve ser definida da seguinte maneira: ```yaml chart_repository: diff --git a/src/i18n/content/pt/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx b/src/i18n/content/pt/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx index f2450b5e41a..515c73e8917 100644 --- a/src/i18n/content/pt/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx +++ b/src/i18n/content/pt/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx @@ -280,7 +280,7 @@ mutation { pipelineCloudRuleEntity: { description: "Since we only care about MyEvent in staging and production, let's drop all MyEvent data in the test environment", name: "Drop MyEvent in test environment", - nrql: "DELETE FROM MyEvent where environment = 'test'", + nrql: "DELETE FROM MyEvent WHERE environment = 'test'", scope: { id: "your_nr_account_id", type: ACCOUNT @@ -304,7 +304,7 @@ mutation { pipelineCloudRuleEntity: { description: "We don't care about jvmId and targetAttr in the test environment, let's drop those attributes", name: "Drop jvmId and targetAttr from MyEvent in test environment", - nrql: "DELETE jvmId, targetAttr FROM MyEvent where environment = 'test'", + nrql: "DELETE jvmId, targetAttr FROM MyEvent WHERE environment = 'test'", scope: { id: "your_nr_account_id", type: ACCOUNT @@ -529,7 +529,7 @@ mutation { pipelineCloudRuleEntity: { description: "We don't care about targetAttr in the test environment in dimensional metric rolloups, let's drop those attributes", name: "Drop targetAttr from Metric aggregate rollups in test environment", - nrql: "DELETE targetAttr FROM MetricAggregate where environment = 'test'", + nrql: "DELETE targetAttr FROM MetricAggregate WHERE environment = 'test'", scope: { id: "your_nr_account_id", type: ACCOUNT diff --git a/src/i18n/content/pt/docs/new-relic-control/pipeline-control/data-dropping-gateway.mdx b/src/i18n/content/pt/docs/new-relic-control/pipeline-control/data-dropping-gateway.mdx index 2509ae0a657..f5b6bb7c762 100644 --- a/src/i18n/content/pt/docs/new-relic-control/pipeline-control/data-dropping-gateway.mdx +++ b/src/i18n/content/pt/docs/new-relic-control/pipeline-control/data-dropping-gateway.mdx @@ -524,7 +524,7 @@ A tabela a seguir lista: - `DELETE FROM SqlTrace WHERE uri = 'Custom\/Simple\/sqlTransaction'` + `DELETE FROM SqlTrace WHERE uri = 'Custom/Simple/sqlTransaction'` @@ -586,7 +586,7 @@ A tabela a seguir lista: - `DELETE FROM TransactionTrace WHERE uri = 'Custom\/Simple\/sqlTransaction'` + `DELETE FROM TransactionTrace WHERE uri = 'Custom/Simple/sqlTransaction'` @@ -730,7 +730,7 @@ A tabela a seguir lista: - `DELETE instanceType,inodesTotal NetworkSample WHERE entityKey = 'vagrant'` + `DELETE instanceType, inodesTotal NetworkSample WHERE entityKey = 'vagrant'` @@ -774,7 +774,7 @@ A tabela a seguir lista: - `DELETE FROM ContainerSample WHERE agentName='ContainerSampleAgent'` + `DELETE FROM ContainerSample WHERE agentName = 'ContainerSampleAgent'` diff --git a/src/i18n/content/pt/docs/new-relic-control/pipeline-control/nrql-functions.mdx b/src/i18n/content/pt/docs/new-relic-control/pipeline-control/nrql-functions.mdx index 5a818c40f0f..8af5aa3e7aa 100644 --- a/src/i18n/content/pt/docs/new-relic-control/pipeline-control/nrql-functions.mdx +++ b/src/i18n/content/pt/docs/new-relic-control/pipeline-control/nrql-functions.mdx @@ -185,8 +185,8 @@ Este documento descreve as funções NRQL suportadas pelo gateway de Pipeline Co Esses exemplos demonstram como você pode combinar várias funções e usá-las em cenários mais complexos para obter filtragem e exclusão de dados precisas. -* `DELETE FROM ContainerSample WHERE state = 'exited' and status LIKE '%Exited%' and status NOT LIKE '%second%' and status not like '%About a minute ago%' and not (status like '%minute%' and numeric(aparse(status,'%Exited (%) * minutes ago%')) < 10)` +* `DELETE FROM ContainerSample WHERE state = 'exited' AND status LIKE '%Exited%' AND status NOT LIKE '%second%' AND status NOT LIKE '%About a minute ago%' AND NOT (status LIKE '%minute%' AND numeric(aparse(status,'%Exited (%) * minutes ago%')) < 10)` * `DELETE FROM Log, LogExtendedRecord WHERE dimensions() LIKE '%collectd%' AND newrelic.logs.customEventType IS NULL` -* `DELETE FROM Log WHERE message LIKE '%lib/ladon/middleware/caching.rb:49 run> terminated with exception%' and floor(timestamp/101) = (timestamp/101)` +* `DELETE FROM Log WHERE message LIKE '%lib/ladon/middleware/caching.rb:49 run> terminated with exception%' AND floor(timestamp/101) = (timestamp/101)` Essas novas funções expandem significativamente os recursos da sua consulta NRQL ao trabalhar com o gateway Controle de Pipeline, permitindo análise e gerenciamento de dados mais precisos. \ No newline at end of file diff --git a/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx b/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx index d7638738c08..6e7bd25354d 100644 --- a/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx +++ b/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx @@ -10,7 +10,7 @@ translationType: machine * Adicionado novo recurso sobre [como depurar problemas de agente New Relic Browser ](/docs/browser/new-relic-browser/troubleshooting/how-to-debug-browser-agent/), incluindo logging detalhado, monitoramento de solicitação de rede e evento de inspeção para melhor resolução de problemas em agentes versões 1.285.0 e superiores. * Adicionado suporte [ao Azure Functions](/docs/serverless-function-monitoring/azure-function-monitoring/introduction-azure-monitoring/) para monitoramento de funções `python` e `.node.js`. * [Otimizador de custos](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/compute-optimizer/) adicionado para insights acionáveis para melhorar a eficiência do computador, com recurso para identificar ineficiências, fornecer recomendações de otimização e estimar economias de CCU na plataforma New Relic. -* Added [Cloud Cost Intelligence](/docs/cci/getting-started/overview), offering tools for visibility and management of cloud costs, including features such as comprehensive cost breakdowns, Kubernetes cost allocation, real-time cost estimation, and cross-account data collection, currently supporting only AWS cloud costs. +* Adicionada [Inteligência de Custos na Nuvem](/docs/cci/getting-started/overview), oferecendo ferramentas para visibilidade e gerenciamento de custos cloud, incluindo recursos como detalhamentos abrangentes de custos, alocação de custos Kubernetes, estimativa de custos em tempo real e coleta de dados entre contas, atualmente suportando apenas custos da Nuvem da AWS. * Adicionada [observabilidade OpenTelemetry para Kubernetes com integração independente de provedor de recursos New Relic](/docs/kubernetes-pixie/k8s-otel/intro/) para monitoramento contínuo do cluster por meio do gráfico Helm, aprimorando os sinais de telemetria para métricas, eventos e logs transmitidos para as ferramentas e o painel do New Relic. * Adicionada [limitação e resolução de problemas para integração Windows](/docs/kubernetes-pixie/kubernetes-integration/troubleshooting/troubleshooting-windows/) * Adicionada integração com AWS via [CloudFormation e CloudWatch Metric Streams](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation/), com suporte à API Polling para serviços não suportados. diff --git a/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx b/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx new file mode 100644 index 00000000000..56fc49bcdf6 --- /dev/null +++ b/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx @@ -0,0 +1,60 @@ +--- +subject: Docs +releaseDate: '2025-08-08' +version: 'August 01 - August 07, 2025' +translationType: machine +--- + +### Novos documentos + +* Adicionado [tutorial do NerdGraph: Criar função personalizada para equipes](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/compute-budgets/overview) para orientar você no uso da API NerdGraph do New Relic para criar e gerenciar funções personalizadas para equipes. + +### Pequenas mudanças + +* Alterado o [limite de eventos de alerta por condição](/docs/alerts/admin/rules-limits-alerts) para 1k por minuto. +* Atualizadas as últimas [versões e requisitos compatíveis do agente .Net](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements) verificados. +* Atualizadas as informações de versão e suporte de versão sobre o service broker para [VMware Tanzu](/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-service-broker-integration). +* Atualizadas as informações de suporte de versão sobre o pacote de integração New Relic NGINX para [VMware Tanzu](/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-nginx-buildpack-integration). +* Atualizadas as informações de versão e suporte de versão sobre o New Relic Nozzle para [VMware Tanzu](/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-firehose-nozzle-integration/#product-snapshot). + +### Notas de versão + +* Confira nossas postagens de Novidades: + + * [Errors Inbox agora está integrada à carga de trabalho](/whats-new/2025/08/whats-new-08-06-workloads-errors-inbox). + +* Fique por dentro dos nossos últimos lançamentos: + + * [Gerenciador de tarefas v452](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-452): + * Melhorias internas adicionadas para tratamento de exceções no processamento de mensagens da fila. + + * [IntegraçãoKubernetes v3.43.3](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-43-3): + * Adicionou um gráfico Helm para implantar a solução de monitoramento Kubernetes da New Relic. + + * [Controle de Pipeline Gateway v1.1.0](/docs/release-notes/pipeline-control-gateway-release-notes/pipeline-control-gateway-25-08-05): + + * Implementou uma nova funcionalidade para descartar seletivamente dados e atributos dos eventos `SqlTrace` e `TransactionTrace` usando regras de descarte. + + * Foram corrigidas vulnerabilidades no pacote `golang.org/x/net`, incluindo um problema de script entre sites e um desvio de proxy HTTP relacionado a IDs de zona IPv6. + + * Atualizado para Go `1.24` e as seguintes dependências foram atualizadas para aumentar a segurança e incorporar correções recentes: + + * `golang.org/x/net to v0.38.0` + * `golang.org/x/sys to v0.31.0` + * `golang.org/x/text to v0.23.0` + + * [Aplicativo móvel para iOS v6.9.11](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6101): + * Reduziu o fluxo de login em duas etapas, armazenando o domínio de autenticação do usuário e redirecionando-o diretamente para sua página de login. + + * [AgenteFlutter v1.1.13](/docs/release-notes/mobile-release-notes/flutter-release-notes/flutter-agent-1113): + + * Agente Android nativo aprimorado e atualizado para a versão 7.6.8 + * Agente iOS nativo aprimorado atualizado para a versão 7.5.8 + + * [Agente .NET MAUI v1.1.11](/docs/release-notes/mobile-release-notes/net-maui-release-notes/net-maui-agent-1111) + + * Agente Android nativo aprimorado e atualizado para a versão 7.6.8 + * Agente iOS nativo aprimorado atualizado para a versão 7.5.8 + + * [agente de infraestrutura v1.65.5](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1655): + * Alterado o suporte para montagens AWS efs em amostras de armazenamento \ No newline at end of file diff --git a/src/i18n/content/pt/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1655.mdx b/src/i18n/content/pt/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1655.mdx index 81b1679501e..e72ddd28114 100644 --- a/src/i18n/content/pt/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1655.mdx +++ b/src/i18n/content/pt/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1655.mdx @@ -6,17 +6,18 @@ translationType: machine --- - **Known issues**: this release has a known issue with diskUsedPercent calculation because of StorageSample containing NFSv4 mount data on Linux hosts having NFSv4 mounts. + **Problemas conhecidos**: esta versão tem um problema conhecido com o cálculo diskUsedPercent devido ao StorageSample conter dados de montagem NFSv4 em hosts Linux com montagens NFSv4. Considere uma destas alternativas: +* Use any version higher than `1.65.5` * Use qualquer versão inferior a `1.65.5` Uma nova versão do agente foi lançada. Siga os procedimentos padrão para [atualizar o agente de infraestrutura](https://docs.newrelic.com/docs/infrastructure/install-configure-manage-infrastructure/update-or-uninstall/update-infrastructure-agent). A New Relic recomenda que você atualize o agente regularmente e, no mínimo, a cada 3 meses. A partir deste lançamento, a versão mais antiga suportada é [agente de infraestrutura 1.51.0](https://docs.newrelic.com/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1510/). ## Mudado -* façanha: suporte a montagens AWS efs em amostras de armazenamento em #2069 +* feat: support AWS EFS mounts in storage samples in #2069 * chore(deps): bump golang.org/x/oauth2 de 0,20,0 a 0,27,0 em #2093 * chore(deps): atualizar a versão do nri-prometheus para v2.27.0 em #2094 \ No newline at end of file diff --git a/src/i18n/content/pt/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5306.mdx b/src/i18n/content/pt/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5306.mdx new file mode 100644 index 00000000000..1dacd6c4dd3 --- /dev/null +++ b/src/i18n/content/pt/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5306.mdx @@ -0,0 +1,11 @@ +--- +subject: Mobile app for Android +releaseDate: '2025-08-07' +version: 5.30.6 +downloadLink: 'https://play.google.com/store/apps/details?id=com.newrelic.rpm' +translationType: machine +--- + +### Melhorias + +* Suporte de senha para SAML e logins sociais \ No newline at end of file diff --git a/src/i18n/content/pt/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx b/src/i18n/content/pt/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx new file mode 100644 index 00000000000..3cf842161b5 --- /dev/null +++ b/src/i18n/content/pt/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx @@ -0,0 +1,39 @@ +--- +subject: Browser agent +releaseDate: '2025-08-04' +version: 1.295.0 +downloadLink: 'https://www.npmjs.com/package/@newrelic/browser-agent' +features: + - Add error cause detection +bugs: + - Add monkey-patching warnings + - Calculate first and last timestamps from raw data +security: [] +translationType: machine +--- + +## v1.295.0 + +### Recurso + +#### Adicionar detecção de causa de erro + +Detecte e relate o atributo de causa no evento JavaScriptError capturado. Se a causa for uma instância de um erro, o stack trace será capturado; caso contrário, o conteúdo em string da causa será relatado. Isso poderá ser consultado no evento JavaScriptError sob o atributo `cause`. + +### Correções de bugs + +#### Adicionar avisos de monkey-patching + +Detecção e avisos adicionados para quando os globais esperados foram corrigidos antes do agente ser executado na página. Isso pode causar comportamentos inesperados e a intenção é informar os clientes sobre esse comportamento. + +#### Calcular o primeiro e o último registro de data e hora a partir de dados brutos + +Certifique-se de que o agente calcule manualmente o primeiro e o último registro de data e hora de uma carga do SessionReplay antes da coleta para ajudar a melhorar a consistência no replayer da interface. + +## Declaração de apoio + +New Relic recomenda que você atualize o agente regularmente para garantir que esteja obtendo os benefícios mais recentes de recursos e desempenho. Versões mais antigas não terão mais suporte quando chegarem [ao fim de sua vida útil](https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/browser-agent-eol-policy/). As datas de lançamento refletem a data de publicação original da versão do agente. + +Novos lançamentos de agente do browser são disponibilizados aos clientes em pequenas etapas ao longo de um período de tempo. Por esse motivo, a data em que o lançamento fica acessível à sua conta pode não corresponder à data de publicação original. Consulte este [dashboard de status](https://newrelic.github.io/newrelic-browser-agent-release/) para obter mais informações. + +De acordo com nossa [política de suporte a navegadores](https://docs.newrelic.com/docs/browser/new-relic-browser/getting-started/compatibility-requirements-browser-monitoring/#browser-types), a versão v1.295.0 do Agente do browser foi criada e testada nesses navegadores e intervalos de versão: Chrome 128-138, Edge 128-138, Safari 17-19 e Firefox 130-140. Para dispositivos móveis, a versão v1.295.0 foi criada e testada para Android OS 16 e iOS Safari 17-26. \ No newline at end of file diff --git a/src/i18n/content/pt/docs/service-architecture-intelligence/github-integration.mdx b/src/i18n/content/pt/docs/service-architecture-intelligence/github-integration.mdx index 89bff46e475..051660e7a05 100644 --- a/src/i18n/content/pt/docs/service-architecture-intelligence/github-integration.mdx +++ b/src/i18n/content/pt/docs/service-architecture-intelligence/github-integration.mdx @@ -53,7 +53,7 @@ Essa integração agiliza o processo de integração de usuários e equipes, sim **Atribuindo repositório às equipes New Relic** -Você pode atribuir automaticamente o repositório do GitHub às suas equipes criando uma propriedade personalizada `teamOwningRepo` no GitHub. +Você pode atribuir automaticamente o repositório do GitHub às suas equipes adicionando `teamOwningRepo` como uma propriedade personalizada no GitHub. 1. Crie a propriedade personalizada no nível da organização e atribua um valor para ela no nível do repositório. Além disso, você pode configurar uma propriedade personalizada para vários repositórios no nível da organização simultaneamente. 2. Em seguida, no New Relic Teams, ative o recurso [Automated Ownership](/docs/service-architecture-intelligence/teams/manage-teams/#assign-ownership), certificando-se de usar `team` como a chave de tag. diff --git a/src/i18n/content/pt/docs/tutorial-improve-site-performance/guide-to-monitoring-core-web-vitals.mdx b/src/i18n/content/pt/docs/tutorial-improve-site-performance/guide-to-monitoring-core-web-vitals.mdx index 139b24c6dbe..b8b4dea80aa 100644 --- a/src/i18n/content/pt/docs/tutorial-improve-site-performance/guide-to-monitoring-core-web-vitals.mdx +++ b/src/i18n/content/pt/docs/tutorial-improve-site-performance/guide-to-monitoring-core-web-vitals.mdx @@ -1,30 +1,32 @@ --- -title: Monitor seus core web vitals +title: Monitore seus Core Web Vitals tags: - Browser - Browser monitoring - Guides -metaDescription: A guide to monitor Google's core web vitals. +metaDescription: A guide to monitor Google's Core Web Vitals. freshnessValidatedDate: '2024-03-21T00:00:00.000Z' translationType: machine --- -Core web vitals são as métricas do Google que medem a experiência geral do usuário. Eles fornecem informações valiosas sobre como o usuário vê seu negócio, o que pode influenciar as classificações de SEO do seu site. Ao ter uma pontuação que captura a experiência do usuário, você pode agir em relação a problemas específicos, em vez de adivinhar o que seu site precisa. +Core Web Vitals (CWV) é uma métrica do Google que mede a experiência geral do usuário. Eles fornecem insights valiosos sobre como os usuários veem seu negócio, o que pode influenciar a classificação de SEO do seu site. Ao ter uma pontuação que captura a experiência do usuário, você pode tomar medidas em relação a problemas específicos em vez de adivinhar o que seu site precisa. ## Objetivos [#objectives] -Este tutorial orienta você no uso do New Relic para analisar seus core web vitals. Ao final do tutorial, você terá estas tarefas concluídas: +Este tutorial mostra como usar o New Relic para dividir seu CWV. Ao final do tutorial, você terá concluído estas tarefas: -* Encontre core web vitals no New Relic. -* Entenda como core web vitals se traduzem no desempenho do site. +* Encontre CWV em New Relic. +* Entenda como o CWV se traduz no desempenho do site. * Explore os dados do New Relic para identificar o que está contribuindo para sua pontuação. -## Saiba mais sobre core web vitals [#learn] +## Saiba mais sobre o CWV [#learn] O Google mede o desempenho geral do site por meio destas três métricas: * [Pintura de maior conteúdo](https://web.dev/articles/lcp) (LCP): quanto tempo leva para o conteúdo principal de uma página carregar. Por exemplo, um usuário que acessa uma página da Web com um LCP lento pode ver uma tela em branco por vários segundos antes de o conteúdo aparecer. + * [interação até a próxima pintura](https://web.dev/articles/inp) (INP): Quanto tempo leva para uma página responder à interação de um usuário. Por exemplo, se um usuário clica em um botão, o INP mede quanto tempo leva entre o clique e a próxima abertura da página. Um INP alto reflete uma experiência de página da web lenta e sem resposta, dificultando o envolvimento do usuário. + * [Mudança cumulativa de layout](https://web.dev/articles/cls) (CLS): com que frequência ocorrem mudanças inesperadas de layout em uma página durante o carregamento. Por exemplo, um usuário que está prestes a clicar em um botão pode descobrir que o conteúdo salta para um novo local na tela, o que pode fazer com que ele clique em outra coisa acidentalmente. Um CLS alto pode fazer com que uma página da web pareça desajeitada e difícil de interagir. Cada web vital tem o seguinte limite para ajudá-lo a monitorar o desempenho e o SEO do seu aplicativo: @@ -32,7 +34,7 @@ Cada web vital tem o seguinte limite para ajudá-lo a monitorar o desempenho e o -
+ Bom @@ -114,7 +116,7 @@ Cada web vital tem o seguinte limite para ajudá-lo a monitorar o desempenho e o ### Como a pontuação CLS é calculada? - A pontuação cumulativa de mudança de layout é um valor sem unidade entre 0 e infinito, e não uma medida baseada no tempo como os outros core web vitals. Reflete a soma do impacto de mudanças inesperadas de layout que ocorrem durante o processo de carregamento de uma página da web. Veja como a pontuação CLS é calculada: + A pontuação cumulativa de mudança de layout é um valor sem unidade entre 0 e infinito, não uma medida baseada em tempo como outros CWVs. Ela reflete a soma do impacto de mudanças inesperadas de layout que ocorrem durante o processo de carregamento de uma página da web. Veja como a pontuação CLS é calculada: * Pontuação de mudança de layout: considera dois fatores: @@ -126,13 +128,13 @@ Cada web vital tem o seguinte limite para ajudá-lo a monitorar o desempenho e o **Good** web vitals pode ajudar sua organização a economizar dinheiro e aumentar o SEO. **Poor** ou **Needs improvement** podem refletir percepções negativas do usuário sobre sua organização, o que pode resultar em clientes insatisfeitos ou perda de oportunidades de negócios. -A New Relic aproveita [a biblioteca de API`web-vitals` ](https://github.com/GoogleChrome/web-vitals)do Google para coletar sinais vitais da Web em seu estado bruto, sem introduzir cálculos adicionais. Para saber mais sobre por que core web vitals são importantes e como são calculados, consulte o artigo web.dev [métrica de desempenho centrada no usuário](https://web.dev/articles/user-centric-performance-metrics). +O New Relic utiliza [a biblioteca de API`web-vitals` ](https://github.com/GoogleChrome/web-vitals)do Google para coletar informações vitais da web em seu estado bruto, sem introduzir cálculos adicionais. Para saber mais sobre a importância dos CWVs e como eles são calculados, consulte o artigo do web.dev [usuário-centric desempenho métrica](https://web.dev/articles/user-centric-performance-metrics). -## Encontre core web vitals no New Relic [#view-data-in-nr] +## Encontre CWVs em New Relic [#view-data-in-nr] -core web vitals estão incorporados em muitos recursos New Relic , mas a melhor maneira de visualizar os sinais vitais da web em alto nível é: +Os CWVs estão incorporados em muitos recursos New Relic, mas a melhor maneira de visualizar os web vitals em alto nível é: -1. Vá para **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Browser**. +1. Vá para **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Browser**. 2. Selecione um aplicativo. @@ -140,163 +142,56 @@ core web vitals estão incorporados em muitos recursos New Relic , mas a melhor A página **Web vitals** mostra as médias vitais da web para todo o seu site. Nessa visualização, você pode detalhar páginas ou métricas específicas para ver o que está impactando as pontuações. - overview of the web vitals page + overview of the web vitals page ### Faça uma busca detalhada em páginas específicas [#drill-down] -Se você quiser insights sobre uma página importante (por exemplo, uma página de checkout de comércio eletrônico), encontre-a na tabela **Page URL** . Você verá um detalhamento do que está contribuindo para core web vitals, que você pode usar para entender como o usuário final está experimentando essas áreas do seu site. Por exemplo, se você notar um padrão de baixo desempenho no Browser Chrome, poderá selecionar quaisquer melhorias futuras para essa base de usuários. +Se você quiser insights sobre uma página importante — por exemplo, uma página de checkout de comércio eletrônico — encontre-a na tabela **Page URL**. Você verá uma análise do que está contribuindo para os CWVs, que pode ser usada para entender como seu usuário final está vivenciando essas áreas do seu site. Por exemplo, se você notar um padrão de desempenho ruim nos navegadores Chrome, você pode selecionar melhorias futuras para essa base de usuários. -Click on a page URL to see page-specific web vitals. +Click on a page URL to see page-specific web vitals.
- **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Browser > (select an app) > Monitor > Web vitals > (click on a page URL)**: veja um detalhamento dos core web vitals para as páginas da web de maior impacto. + **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Browser > (select an app) > Monitor > Web vitals > (click a page URL)**: Veja uma análise dos CWVs para as páginas da web de maior impacto.
### Filtrar por atributo chave [#key-attributes] -Se quiser investigar algo específico, como como uma alteração backend ou um problema de desempenho afetou core web vitals, você pode usar a ferramenta **Filter by** para filtrar qualquer atributo principal. +Se quiser investigar algo específico, como uma alteração no backend ou um problema de desempenho impactou os CWVs, você pode usar a ferramenta **Filter by** para filtrar qualquer atributo-chave. -Filter by key attributes +Filter by key attributes
- **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Browser > (select an app) > Monitor > Web vitals > (add filters)**: Use a ferramenta de filtro para filtrar core web vitals por atributo principal. + **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Browser > (select an app) > Monitor > Web vitals > (add filters)**: Use a ferramenta de filtro para filtrar core web vitals por atributo principal.
Embora você possa filtrar por praticamente qualquer atributo-chave, continue lendo para obter alguns exemplos úteis. - - Digamos que você queira comparar o desempenho do desktop versus o desempenho móvel e como core web vitals diferem entre as duas plataformas. Para investigar isso em **Web vitals**: - - 1. No campo - - - **Filter by** - - - , defina - - - **Attribute** - - - como`deviceType` e - - - **Value** - - - como `desktop`. - - 2. Em um Browser duplicado, defina + + Digamos que você queira comparar o desempenho do desktop com o do celular e como os CWVs diferem entre as duas plataformas. Para investigar isso em **Web vitals**: - - **Attribute** - - - como`deviceType` e - - - **Value** - - - como `mobile` e compare os resultados. + 1. No campo **Filter by** , defina **Attribute** como`deviceType` e **Value** como `desktop`. + 2. Em um Browser duplicado, defina **Attribute** como`deviceType` e **Value** como `mobile` e compare os resultados. - + Digamos que um usuário final relatou problemas de desempenho na página de checkout do seu site no dia 1º de novembro, por volta das 12h, e você deseja ver o que aconteceu com esse usuário. Para investigar isso em **Web vitals**: 1. Defina o intervalo de tempo para 1º de novembro, entre 11h e 13h. + 2. Na tabela **Page URL** , clique no URL da página de checkout. + 3. No campo **Filter by** , defina **Attribute** como `userID` e **Value** como `user ID`. - 2. Na tabela - - - **Page URL** - - - , clique no URL da página de checkout. - - 3. No campo - - - **Filter by** - - - , defina - - - **Attribute** - - - como `userID` e - - - **Value** - - - como `user ID`. - - - `userID` é um atributo personalizado que você precisará definir usando a [API SPA do browser](/docs/browser/new-relic-browser/browser-agent-spa-api/setcustomattribute-browser-agent-api/). Se `userID` não estiver disponível, você também poderá filtrar por outras informações do usuário, como `username` ou `session`. - + + `userID` é um atributo personalizado que você precisará definir usando a [API SPA do browser](/docs/browser/new-relic-browser/browser-agent-spa-api/setcustomattribute-browser-agent-api/). Se `userID` não estiver disponível, você também poderá filtrar por outras informações do usuário, como `username` ou `session`. + - - Digamos que sua organização atualizou recentemente as imagens na página inicial do site em 10 de novembro às 8h e você deseja ver se as alterações afetaram core web vitals. Para investigar isso em **Web vitals**: + + Digamos que sua organização atualizou recentemente as imagens na página inicial do site em 10 de novembro às 8h, e você quer ver se as alterações impactaram os CWVs. Para investigar isso em **Web vitals**: 1. Defina o intervalo de tempo para 10 de novembro, entre 7h e 9h. - - 2. Na tabela - - - **Page URL** - - - , clique no URL da página inicial. - - 3. No campo - - - **Filter by** - - - , defina - - - **Attribute** - - - como `elementTagName` e - - - **Value** - - - como `IMG`. + 2. Na tabela **Page URL**, clique no URL da página inicial. + 3. No campo **Filter by** , defina **Attribute** como `elementTagName` e **Value** como `IMG`. @@ -304,47 +199,32 @@ Embora você possa filtrar por praticamente qualquer atributo-chave, continue le New Relic captura dados sobre a sessão de um usuário em uma determinada página. trace da sessão são amostrados aleatoriamente, permitindo que você visualize como um usuário enfrentou problemas de tempo de carregamento da página, evento de JavaScript ou outros erros. -Session traces in Browser UI lets you look at real user sessions for a given page +Session traces in Browser UI lets you look at real user sessions for a given page -Recomendamos usar o trace da sessão para encontrar padrões em diferentes sessões de usuário. Se uma de suas pontuações core web vitals puder ser melhorada, uma opção é examinar o trace da sessão para ver quais atributos comuns são compartilhados entre diferentes sessões de usuário. Aqui está um exemplo de como o trace da sessão pode ajudá-lo a melhorar seu site: +Recomendamos usar o trace da sessão para encontrar padrões em diferentes sessões de usuário. Se uma das suas pontuações CWVs puder ser melhorada, uma opção é analisar o rastreamento da sessão para ver quais atributos comuns são compartilhados entre diferentes sessões de usuário. Aqui está um exemplo de como o trace da sessão pode ajudar você a melhorar seu site: -1. Na guia +1. Na guia **Web vitals** , clique na página com desempenho insatisfatório. Usando a imagem acima como exemplo, você vê que seu site tem uma boa pontuação geral de LCP, mas também percebe que algumas de suas páginas individuais precisam de melhorias. +2. Observando a seção **Page URLs** da página **Web vitals** , você verá que o URL da sua página inicial tem uma pontuação LCP superior a quatro segundos. Isso se deve a um erro que afeta todos os usuários ou afeta apenas um tipo de usuário? Por exemplo, se você perceber que um usuário com uma versão do Chrome ou um determinado sistema operacional está enfrentando lentidão no carregamento da página, você poderá solucionar melhor a causa específica de um problema. +3. Uma nova janela será preenchida quando você clicar no URL que deseja solucionar. Você percebe que sua pontuação LCP é muito maior do que a pontuação geral de LCP do seu site. Rolando até a seção **Session traces** na parte inferior desta página, você verá vários exemplos de sessões reais de usuários. Essas sessões podem fornecer detalhes mais granulares sobre como o usuário experimentou solicitações AJAX, problemas relacionados ao carregamento do DOM, eventos de JavaScript ou outros erros. - - **Web vitals** - - - , clique na página com desempenho insatisfatório. Usando a imagem acima como exemplo, você vê que seu site tem uma boa pontuação geral de LCP, mas também percebe que algumas de suas páginas individuais precisam de melhorias. - -2. Observando a seção +Os dados de sessões aleatórias ajudam a encontrar padrões em centenas ou milhares de interações do usuário com uma página da web. Se um padrão aparecer nesses dados selecionados aleatoriamente, você poderá ter mais confiança de que seu plano para resolver um problema melhorará a pontuação de sua página. - - **Page URLs** - +## Melhore sua compreensão com o Session Replay [#session-replays] - da página +Se um LCP ruim ou um CLS alto for identificado, o Session Replay fornece um registro visual do que ocorreu, ajudando a localizar rapidamente o elemento ou evento exato que está causando o problema. - - **Web vitals** - +Veja um exemplo de como o Session Replay pode ajudar você a melhorar seu site: - , você verá que o URL da sua página inicial tem uma pontuação LCP superior a quatro segundos. Isso se deve a um erro que afeta todos os usuários ou afeta apenas um tipo de usuário? Por exemplo, se você perceber que um usuário com uma versão do Chrome ou um determinado sistema operacional está enfrentando lentidão no carregamento da página, você poderá solucionar melhor a causa específica de um problema. +1. Identificar um problema de desempenho: Na página **Web vitals**, clique no URL relevante para abrir sua visualização detalhada de desempenho. Esta ação redireciona para uma visualização detalhada das informações vitais da web para aquela página. Examine as pontuações do CWV e procure por qualquer uma com os rótulos **Needs improvement** ou **Poor**. Você também pode filtrar os resultados por tipo de dispositivo ou navegador, pois os problemas de desempenho podem variar significativamente de acordo com a plataforma. Entender esses detalhes ajuda a identificar áreas específicas para otimização. -3. Uma nova janela será preenchida quando você clicar no URL que deseja solucionar. Você percebe que sua pontuação LCP é muito maior do que a pontuação geral de LCP do seu site. Rolando até a seção +2. Acessar replays relevantes: clique no número na coluna **Session replays** do ponto de dados que você está investigando. Esta ação filtra automaticamente os replays para exibir as sessões que apresentaram o problema de desempenho específico. Por exemplo, clicar na contagem de repetição de sessão para uma página com um LCP ruim apresentará uma lista de sessões em que o LCP foi lento. - - **Session traces** - +3. Assista e diagnostique: assista às gravações de vídeo para obter uma compreensão visual do problema. Você pode descobrir: - na parte inferior desta página, você verá vários exemplos de sessões reais de usuários. Essas sessões podem fornecer detalhes mais granulares sobre como o usuário experimentou solicitações AJAX, problemas relacionados ao carregamento do DOM, eventos de JavaScript ou outros erros. + * Problemas de LCP: uma imagem grande de herói ou vídeo que carregava lentamente, causando uma tela em branco por vários segundos. + * Problemas de CLS: um anúncio ou conteúdo de terceiros que carregava com atraso, fazendo com que o conteúdo da página mudasse inesperadamente. + * Problemas de INP: Um botão ou elemento interativo de resposta lenta pode causar frustração. -Os dados de sessões aleatórias ajudam a encontrar padrões em centenas ou milhares de interações do usuário com uma página da web. Se um padrão aparecer nesses dados selecionados aleatoriamente, você poderá ter mais confiança de que seu plano para resolver um problema melhorará a pontuação de sua página. +Ao combinar os dados técnicos do trace da sessão com o contexto visual do Session Replay, você pode desenvolver um plano abrangente para resolver problemas de desempenho e melhorar significativamente sua experiência do usuário final. - + \ No newline at end of file diff --git a/src/i18n/content/pt/docs/tutorial-manage-large-log-volume/organize-large-logs.mdx b/src/i18n/content/pt/docs/tutorial-manage-large-log-volume/organize-large-logs.mdx index a51f5cb8d92..c4fc3d5e86e 100644 --- a/src/i18n/content/pt/docs/tutorial-manage-large-log-volume/organize-large-logs.mdx +++ b/src/i18n/content/pt/docs/tutorial-manage-large-log-volume/organize-large-logs.mdx @@ -33,9 +33,9 @@ Analisar seus logs na ingestão é a melhor maneira de tornar seus dados log mai Pré-análise: - ``` + ```json { - "message": "32 4329 store_Portland" + "message": "32 4329 store_Portland" } @@ -45,11 +45,11 @@ Analisar seus logs na ingestão é a melhor maneira de tornar seus dados log mai Pós-análise: - ``` + ```json { - "transaction_total": "32", - "purchase_number": "4329", - "store_location": "store_Portland", + "transaction_total": "32", + "purchase_number": "4329", + "store_location": "store_Portland", } ``` @@ -120,9 +120,9 @@ Para fazer isso: Vamos trabalhar com o exemplo que usamos anteriormente neste documento. Você tem log que segue este padrão: - ``` + ```json { - "message": "32 4329 store_Portland" + "message": "32 4329 store_Portland" } ``` @@ -136,11 +136,11 @@ Para fazer isso: Depois que a regra de análise for criada com o padrão acima, ela retornará log da seguinte maneira: - ``` + ```json { - "transaction_total": "32", - "purchase_number": "4329", - "store_location": "store_Portland", + "transaction_total": "32", + "purchase_number": "4329", + "store_location": "store_Portland", } ``` From abb98172ff48cfe7f3e2a2a3d4e4add86d988ca0 Mon Sep 17 00:00:00 2001 From: Aashirwad Jain Date: Wed, 13 Aug 2025 14:35:51 +0530 Subject: [PATCH 2/2] Update general-setting.mdx --- .../pt/docs/cci/configure-cci/general-setting.mdx | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/src/i18n/content/pt/docs/cci/configure-cci/general-setting.mdx b/src/i18n/content/pt/docs/cci/configure-cci/general-setting.mdx index b532be6ba3f..4c2c1c56ce7 100644 --- a/src/i18n/content/pt/docs/cci/configure-cci/general-setting.mdx +++ b/src/i18n/content/pt/docs/cci/configure-cci/general-setting.mdx @@ -43,10 +43,10 @@ A Inteligência de Custos na Nuvem suporta tag personalizada junto com tag padr 1. Para solicitar informações sobre as contas das quais você deseja extrair dados de telemetria para análise de custos, selecione a aba **Telemetry Data** . 2. Para visualizar e gerenciar dados de telemetria para sua análise de custos, na lista **Select accounts for telemetry data** , escolha uma ou mais contas. - - * A estimativa de custos em tempo real é suportada por dados de telemetria. - * A alocação de K8s é suportada por dados de telemetria. - * Reutilizamos o pipeline de telemetria existente para obter a métrica de utilização, e nenhum dado novo é ingerido, exceto a ingestão do arquivo CUR. - + + * A estimativa de custos em tempo real é suportada por dados de telemetria. + * A alocação de K8s é suportada por dados de telemetria. + * Reutilizamos o pipeline de telemetria existente para obter a métrica de utilização, e nenhum dado novo é ingerido, exceto a ingestão do arquivo CUR. + - \ No newline at end of file +