diff --git a/src/i18n/content/es/docs/infrastructure/infrastructure-agent/configuration/configure-infrastructure-agent.mdx b/src/i18n/content/es/docs/infrastructure/infrastructure-agent/configuration/configure-infrastructure-agent.mdx index 21aad9b577c..073467f7916 100644 --- a/src/i18n/content/es/docs/infrastructure/infrastructure-agent/configuration/configure-infrastructure-agent.mdx +++ b/src/i18n/content/es/docs/infrastructure/infrastructure-agent/configuration/configure-infrastructure-agent.mdx @@ -62,6 +62,10 @@ Aquí hay descripciones detalladas de cada método de configuración: ```yml license_key: {{MY_LICENSE_KEY}} ``` + + + A menudo, el agente de infraestructura se ejecuta como un servicio del sistema en el host, gestionado globalmente (por ejemplo, `systemd` para Linux, servicios de Windows, `launchd` para macOS, etc.). Para aplicar cambios de configuración con variables de entorno en esta configuración, dichas variables de entorno deben configurar y hacer visibles para el contexto aislado donde se ejecuta el servicio del agente de infraestructura. La forma de hacer esto depende de la plataforma; consulte la documentación del administrador de servicios de su plataforma para saber cómo agregar variables de entorno a los servicios del sistema. + diff --git a/src/i18n/content/es/docs/infrastructure/infrastructure-agent/configuration/infrastructure-agent-configuration-settings.mdx b/src/i18n/content/es/docs/infrastructure/infrastructure-agent/configuration/infrastructure-agent-configuration-settings.mdx index f37cf72810f..6c65d84c9e2 100644 --- a/src/i18n/content/es/docs/infrastructure/infrastructure-agent/configuration/infrastructure-agent-configuration-settings.mdx +++ b/src/i18n/content/es/docs/infrastructure/infrastructure-agent/configuration/infrastructure-agent-configuration-settings.mdx @@ -30,6 +30,14 @@ El [`license_key`](#license-key) es la única configuración requerida. Para ver un ejemplo de cómo se pueden usar todas estas variables, consulte nuestra [plantilla de configuración de muestra en GitHub](https://github.com/newrelic/infrastructure-agent/blob/master/assets/examples/infrastructure/newrelic-infra-template.yml.example). +## Variables de entorno + +Muchas de las opciones de configuración enumeradas también admiten el uso de variables de entorno para establecer valores, que tienen prioridad sobre la configuración YAML. + + + A menudo, el agente de infraestructura se ejecuta como un servicio del sistema en el host, gestionado globalmente (por ejemplo, `systemd` para Linux, servicios de Windows, `launchd` para macOS, etc.). Para aplicar cambios de configuración con variables de entorno en esta configuración, dichas variables de entorno deben configurar y hacer visibles para el contexto aislado donde se ejecuta el servicio del agente de infraestructura. La forma de hacer esto depende de la plataforma; consulte la documentación del administrador de servicios de su plataforma para saber cómo agregar variables de entorno a los servicios del sistema. + + ## Variables del agente [#agent-variables] diff --git a/src/i18n/content/es/docs/mobile-monitoring/mobile-monitoring-ui/mobile-logs.mdx b/src/i18n/content/es/docs/mobile-monitoring/mobile-monitoring-ui/mobile-logs.mdx index b3c0be99901..1ae9a0fd788 100644 --- a/src/i18n/content/es/docs/mobile-monitoring/mobile-monitoring-ui/mobile-logs.mdx +++ b/src/i18n/content/es/docs/mobile-monitoring/mobile-monitoring-ui/mobile-logs.mdx @@ -440,6 +440,7 @@ Tenga en cuenta que cuando emplee la API de logging, solo debe emplear el nivel CrossNewRelic.Current.LogAttributes(new Dictionary() { + { "level","info"}, { "BreadNumValue", 12.3 }, { "BreadStrValue", "MAUIBread" }, { "BreadBoolValue", true }, @@ -489,14 +490,16 @@ Tenga en cuenta que cuando emplee la API de logging, solo debe emplear el nivel "BreadNumValue": 12.3, "BreadStrValue": "FlutterBread", "BreadBoolValue": true, - "message": "This is a message with attributes" + "message": "This is a message with attributes", + "level":"info" }); NewrelicMobile.instance.logAttributes({ "BreadNumValue": 12.3, "BreadStrValue": "FlutterBread", "BreadBoolValue": true, - "message": "This is a message with attributes" + "message": "This is a message with attributes", + "level":"info" }); ``` @@ -590,6 +593,7 @@ Tenga en cuenta que cuando emplee la API de logging, solo debe emplear el nivel CrossNewRelicClient.Current.LogAttributes(new Dictionary() { + {"level", "info"}, { "BreadNumValue", 12.3 }, { "BreadStrValue", "XamBread" }, { "BreadBoolValue", true }, @@ -635,6 +639,7 @@ Tenga en cuenta que cuando emplee la API de logging, solo debe emplear el nivel NewRelicAgent.LogAttributes(new Dictionary() { + {"level", "info"}, {"BreadNumValue", 12.3 }, {"BreadStrValue", "UnityBread" }, {"BreadBoolValue", true }, diff --git a/src/i18n/content/es/docs/new-relic-solutions/new-relic-one/introduction-new-relic-platform.mdx b/src/i18n/content/es/docs/new-relic-solutions/new-relic-one/introduction-new-relic-platform.mdx index 417d69c3e75..a0d4f5bf430 100644 --- a/src/i18n/content/es/docs/new-relic-solutions/new-relic-one/introduction-new-relic-platform.mdx +++ b/src/i18n/content/es/docs/new-relic-solutions/new-relic-one/introduction-new-relic-platform.mdx @@ -276,7 +276,7 @@ A continuación se muestran algunas opciones para compartir visualizaciones y p - Para compartir una página completa UI de New Relic, use el ícono de vínculo permanente cerca de la parte superior de la plataforma. Tenga en cuenta que estos enlaces caducan si no se utilizan en un período de seis meses. + Para compartir una página completa UI de New Relic, usa el ícono de vínculo permanente cerca de la parte superior de la plataforma. diff --git a/src/i18n/content/es/docs/query-your-data/explore-query-data/dashboards/dashboards-charts-import-export-data.mdx b/src/i18n/content/es/docs/query-your-data/explore-query-data/dashboards/dashboards-charts-import-export-data.mdx index 0ce6958b792..988f93abbc0 100644 --- a/src/i18n/content/es/docs/query-your-data/explore-query-data/dashboards/dashboards-charts-import-export-data.mdx +++ b/src/i18n/content/es/docs/query-your-data/explore-query-data/dashboards/dashboards-charts-import-export-data.mdx @@ -74,7 +74,7 @@ Si bien es poderoso, exportar como CSV tiene limitaciones. Un par de cosas a ten Desde cualquier dashboard, compártelo con una de estas opciones: -* Copie el vínculo permanente del dashboard haciendo clic en el ícono de enlace en la parte superior derecha del dashboard. vínculo permanente comparte un enlace directo al dashboard. Tenga en cuenta que estos enlaces caducan si no se utilizan en un período de seis meses. +* Copie el vínculo permanente del dashboard haciendo clic en el ícono de enlace en la parte superior derecha del dashboard. vínculo permanente comparte un enlace directo al dashboard. * Copie su dashboard **as JSON** y agréguelo al portapapeles haciendo clic en el botón **...** en la parte superior derecha y seleccionando **Copy JSON to clipboard**. También puedes [duplicar tu dashboard](/docs/query-your-data/explore-query-data/dashboards/introduction-dashboards/#dashboards-clone). diff --git a/src/i18n/content/jp/docs/infrastructure/infrastructure-agent/configuration/configure-infrastructure-agent.mdx b/src/i18n/content/jp/docs/infrastructure/infrastructure-agent/configuration/configure-infrastructure-agent.mdx index 7b7b09d33dd..44d1f218e59 100644 --- a/src/i18n/content/jp/docs/infrastructure/infrastructure-agent/configuration/configure-infrastructure-agent.mdx +++ b/src/i18n/content/jp/docs/infrastructure/infrastructure-agent/configuration/configure-infrastructure-agent.mdx @@ -62,6 +62,10 @@ translationType: machine ```yml license_key: {{MY_LICENSE_KEY}} ``` + + + 多くの場合、インフラストラクチャエージェントはホスト内のシステムサービスとして実行され、グローバルに管理されます（例： `systemd` (Linux、Windows サービスの場合)、 `launchd` (macOS の場合) など。 このセットアップで環境変数を使用して設定の変更を適用するには、これらの環境変数を設定し、infrastructureagent サービスが実行されている分離されたコンテキストに表示できるようにする必要があります。 これを行う方法はプラットフォームによって異なります。システム サービスに環境変数を追加する方法については、プラットフォームのサービス マネージャーのドキュメントを確認してください。 + diff --git a/src/i18n/content/jp/docs/infrastructure/infrastructure-agent/configuration/infrastructure-agent-configuration-settings.mdx b/src/i18n/content/jp/docs/infrastructure/infrastructure-agent/configuration/infrastructure-agent-configuration-settings.mdx index d5bb1427c8e..00adfad63eb 100644 --- a/src/i18n/content/jp/docs/infrastructure/infrastructure-agent/configuration/infrastructure-agent-configuration-settings.mdx +++ b/src/i18n/content/jp/docs/infrastructure/infrastructure-agent/configuration/infrastructure-agent-configuration-settings.mdx @@ -30,6 +30,14 @@ translationType: machine これらすべての変数の使用方法の例については、 [GitHub のサンプル構成テンプレートを](https://github.com/newrelic/infrastructure-agent/blob/master/assets/examples/infrastructure/newrelic-infra-template.yml.example)参照してください。 +## 環境変数 + +リストされている設定オプションの多くは、環境変数を使用して値を設定することもできます。環境変数は YAML 設定よりも優先されます。 + + + 多くの場合、インフラストラクチャエージェントはホスト内のシステムサービスとして実行され、グローバルに管理されます（例： `systemd` (Linux、Windows サービスの場合)、 `launchd` (macOS の場合) など。 このセットアップで環境変数を使用して設定の変更を適用するには、これらの環境変数を設定し、infrastructureagent サービスが実行されている分離されたコンテキストに表示できるようにする必要があります。 これを行う方法はプラットフォームによって異なります。システム サービスに環境変数を追加する方法については、プラットフォームのサービス マネージャーのドキュメントを確認してください。 + + ## エージェント変数 [#agent-variables] diff --git a/src/i18n/content/jp/docs/mobile-monitoring/mobile-monitoring-ui/mobile-logs.mdx b/src/i18n/content/jp/docs/mobile-monitoring/mobile-monitoring-ui/mobile-logs.mdx index f3fea3ea617..02727e8bd94 100644 --- a/src/i18n/content/jp/docs/mobile-monitoring/mobile-monitoring-ui/mobile-logs.mdx +++ b/src/i18n/content/jp/docs/mobile-monitoring/mobile-monitoring-ui/mobile-logs.mdx @@ -440,6 +440,7 @@ UI でログを表示するには: CrossNewRelic.Current.LogAttributes(new Dictionary() { + { "level","info"}, { "BreadNumValue", 12.3 }, { "BreadStrValue", "MAUIBread" }, { "BreadBoolValue", true }, @@ -489,14 +490,16 @@ UI でログを表示するには: "BreadNumValue": 12.3, "BreadStrValue": "FlutterBread", "BreadBoolValue": true, - "message": "This is a message with attributes" + "message": "This is a message with attributes", + "level":"info" }); NewrelicMobile.instance.logAttributes({ "BreadNumValue": 12.3, "BreadStrValue": "FlutterBread", "BreadBoolValue": true, - "message": "This is a message with attributes" + "message": "This is a message with attributes", + "level":"info" }); ``` @@ -590,6 +593,7 @@ UI でログを表示するには: CrossNewRelicClient.Current.LogAttributes(new Dictionary() { + {"level", "info"}, { "BreadNumValue", 12.3 }, { "BreadStrValue", "XamBread" }, { "BreadBoolValue", true }, @@ -635,6 +639,7 @@ UI でログを表示するには: NewRelicAgent.LogAttributes(new Dictionary() { + {"level", "info"}, {"BreadNumValue", 12.3 }, {"BreadStrValue", "UnityBread" }, {"BreadBoolValue", true }, diff --git a/src/i18n/content/jp/docs/query-your-data/explore-query-data/dashboards/dashboards-charts-import-export-data.mdx b/src/i18n/content/jp/docs/query-your-data/explore-query-data/dashboards/dashboards-charts-import-export-data.mdx index 91c545c6cca..648cc819aba 100644 --- a/src/i18n/content/jp/docs/query-your-data/explore-query-data/dashboards/dashboards-charts-import-export-data.mdx +++ b/src/i18n/content/jp/docs/query-your-data/explore-query-data/dashboards/dashboards-charts-import-export-data.mdx @@ -74,7 +74,7 @@ CSV としてのエクスポートは強力ですが、制限があります。 どのダッシュボードからでも、以下のいずれかの方法で共有することができます。 -* ダッシュボードの右上にあるリンク アイコンをクリックして、ダッシュボードのパーマリンクをコピーします。 パーマリンクは、ダッシュボードへの直接リンクを共有します。 これらのリンクは 6 か月以内に使用されないと期限切れになることに注意してください。 +* ダッシュボードの右上にあるリンク アイコンをクリックして、ダッシュボードのパーマリンクをコピーします。パーマリンクは、ダッシュボードへの直接リンクを共有します。 * ダッシュボード**as JSON**をコピーし、右上の**...**ボタンをクリックして**Copy JSON to clipboard**を選択し、クリップボードに追加します。 また、 [ダッシュボードを複製することもできます](/docs/query-your-data/explore-query-data/dashboards/introduction-dashboards/#dashboards-clone) 。 diff --git a/src/i18n/content/jp/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda.mdx b/src/i18n/content/jp/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda.mdx index 24d89792ea8..8bd75c378e2 100644 --- a/src/i18n/content/jp/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda.mdx +++ b/src/i18n/content/jp/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda.mdx @@ -128,7 +128,7 @@ CLI について詳しく知りたい場合は、 [CLI リポジトリ](https:// 以下のランタイムをお勧めします。 * Node.js： `nodejs16.x` 、 `nodejs18.x` 、 `nodejs20.x` -* Python: `python3.8` 、 `python3.9` 、 `python3.10` 、 `python3.11` 、 `python3.12` +* Python: `python3.8` 、 `python3.9` 、 `python3.10` 、 `python3.11` 、 `python3.12` 、 `python3.13` * Go： `provided.al2` 、 `provided.al2023` * Java: `java8.al2` 、 `java11` 、 `java17` 、 `java21` * Ruby : `ruby3.2`, `ruby3.3` diff --git a/src/i18n/content/kr/docs/apm/agents/java-agent/getting-started/compatibility-requirements-java-agent.mdx b/src/i18n/content/kr/docs/apm/agents/java-agent/getting-started/compatibility-requirements-java-agent.mdx index 606f679a401..25de597e744 100644 --- a/src/i18n/content/kr/docs/apm/agents/java-agent/getting-started/compatibility-requirements-java-agent.mdx +++ b/src/i18n/content/kr/docs/apm/agents/java-agent/getting-started/compatibility-requirements-java-agent.mdx @@ -130,7 +130,7 @@ Java 에이전트를 설치하기 전에 시스템이 다음 요구 사항을 * 스프레이 캔 1.3.1 최신 버전 * Tomcat 7.0.0-최신 버전 * TomEE 1.5-최신 버전 - * WebLogic 12.1.2.1 - 12.2.x + * WebLogic 12.1.2.1 - 14.1.1 * WebSphere 8.5.x - 9.x * 최신 버전의 WebSphere Liberty Profile 8.5 * WildFly 8.0.0.최종에서 최신으로 diff --git a/src/i18n/content/kr/docs/infrastructure/infrastructure-agent/configuration/configure-infrastructure-agent.mdx b/src/i18n/content/kr/docs/infrastructure/infrastructure-agent/configuration/configure-infrastructure-agent.mdx index e00e7894ec4..d0b3d11c632 100644 --- a/src/i18n/content/kr/docs/infrastructure/infrastructure-agent/configuration/configure-infrastructure-agent.mdx +++ b/src/i18n/content/kr/docs/infrastructure/infrastructure-agent/configuration/configure-infrastructure-agent.mdx @@ -62,6 +62,10 @@ translationType: machine ```yml license_key: {{MY_LICENSE_KEY}} ``` + + + 종종 인프라 에이전트는 호스트의 시스템 서비스로 실행되며 전역적으로 관리됩니다(예: Linux의 경우 `systemd` , Windows 서비스의 경우 `launchd` 등). 이 설정에서 환경 변수를 사용하여 구성 변경 사항을 적용하려면 이러한 환경 변수를 설정하고 인프라 에이전트 서비스가 실행 중인 격리된 컨텍스트에서 볼 수 있도록 해야 합니다. 이 작업을 수행하는 방법은 플랫폼에 따라 다르므로 플랫폼의 서비스 관리자 설명서를 확인하여 시스템 서비스에 환경 변수를 추가하는 방법을 알아보세요. + diff --git a/src/i18n/content/kr/docs/mobile-monitoring/mobile-monitoring-ui/mobile-logs.mdx b/src/i18n/content/kr/docs/mobile-monitoring/mobile-monitoring-ui/mobile-logs.mdx index 184a0c1bff6..7684712ef9e 100644 --- a/src/i18n/content/kr/docs/mobile-monitoring/mobile-monitoring-ui/mobile-logs.mdx +++ b/src/i18n/content/kr/docs/mobile-monitoring/mobile-monitoring-ui/mobile-logs.mdx @@ -440,6 +440,7 @@ UI에서 로그를 보려면: CrossNewRelic.Current.LogAttributes(new Dictionary() { + { "level","info"}, { "BreadNumValue", 12.3 }, { "BreadStrValue", "MAUIBread" }, { "BreadBoolValue", true }, @@ -489,14 +490,16 @@ UI에서 로그를 보려면: "BreadNumValue": 12.3, "BreadStrValue": "FlutterBread", "BreadBoolValue": true, - "message": "This is a message with attributes" + "message": "This is a message with attributes", + "level":"info" }); NewrelicMobile.instance.logAttributes({ "BreadNumValue": 12.3, "BreadStrValue": "FlutterBread", "BreadBoolValue": true, - "message": "This is a message with attributes" + "message": "This is a message with attributes", + "level":"info" }); ``` @@ -590,6 +593,7 @@ UI에서 로그를 보려면: CrossNewRelicClient.Current.LogAttributes(new Dictionary() { + {"level", "info"}, { "BreadNumValue", 12.3 }, { "BreadStrValue", "XamBread" }, { "BreadBoolValue", true }, @@ -635,6 +639,7 @@ UI에서 로그를 보려면: NewRelicAgent.LogAttributes(new Dictionary() { + {"level", "info"}, {"BreadNumValue", 12.3 }, {"BreadStrValue", "UnityBread" }, {"BreadBoolValue", true }, diff --git a/src/i18n/content/kr/docs/new-relic-solutions/new-relic-one/introduction-new-relic-platform.mdx b/src/i18n/content/kr/docs/new-relic-solutions/new-relic-one/introduction-new-relic-platform.mdx index 998ea99a0ca..2482764bd97 100644 --- a/src/i18n/content/kr/docs/new-relic-solutions/new-relic-one/introduction-new-relic-platform.mdx +++ b/src/i18n/content/kr/docs/new-relic-solutions/new-relic-one/introduction-new-relic-platform.mdx @@ -276,7 +276,7 @@ New Relic 플랫폼에 대한 소개는 [New Relic 알아보기 를](/docs/new-r - 전체 New Relic UI 페이지를 공유하려면 플랫폼 상단 근처에 있는 영구 링크 아이콘을 사용하세요. 이러한 링크는 6개월 동안 사용하지 않으면 만료된다는 점에 유의하세요. + 전체 New Relic UI 페이지를 공유하려면 플랫폼 상단에 있는 영구 링크 아이콘을 사용하세요. diff --git a/src/i18n/content/kr/docs/query-your-data/explore-query-data/dashboards/dashboards-charts-import-export-data.mdx b/src/i18n/content/kr/docs/query-your-data/explore-query-data/dashboards/dashboards-charts-import-export-data.mdx index 2e5b214669a..88332541206 100644 --- a/src/i18n/content/kr/docs/query-your-data/explore-query-data/dashboards/dashboards-charts-import-export-data.mdx +++ b/src/i18n/content/kr/docs/query-your-data/explore-query-data/dashboards/dashboards-charts-import-export-data.mdx @@ -74,7 +74,7 @@ CSV로 내보내는 것은 강력하지만 제한이 있습니다. 명심해야 모든 대시보드에서 다음 옵션 중 하나로 공유합니다. -* 대시보드 오른쪽 상단의 링크 아이콘을 클릭하여 대시보드의 영구 링크를 복사하세요. 영구 링크는 대시보드에 대한 직접 링크를 공유합니다. 이러한 링크는 6개월 동안 사용하지 않으면 만료된다는 점에 유의하세요. +* 대시보드 오른쪽 상단에 있는 링크 아이콘을 클릭하여 대시보드의 고유 링크를 복사하세요. 영구 링크는 대시보드에 대한 직접 링크를 공유합니다. * 대시보드 **as JSON** 를 복사하고 오른쪽 상단의 **...** 버튼을 클릭하고 **Copy JSON to clipboard** 선택하여 클립보드에 추가합니다. [대시보드를 복제](/docs/query-your-data/explore-query-data/dashboards/introduction-dashboards/#dashboards-clone) 할 수도 있습니다. diff --git a/src/i18n/content/kr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda.mdx b/src/i18n/content/kr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda.mdx index 41ac89cc5d9..b1e406f994e 100644 --- a/src/i18n/content/kr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda.mdx +++ b/src/i18n/content/kr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda.mdx @@ -128,7 +128,7 @@ CLI에 대해 자세히 알아보려면 [CLI 리포지터리를](https://github. 다음 런타임을 권장합니다. * Node.js: `nodejs16.x` , `nodejs18.x` , `nodejs20.x` -* 파이썬: `python3.8`, `python3.9`, `python3.10`, `python3.11`, `python3.12` +* Python: `python3.8`, `python3.9`, `python3.10`, `python3.11`, `python3.12`, `python3.13` * 이동: `provided.al2` , `provided.al2023` * 자바: `java8.al2`, `java11`, `java17`, `java21` * 루비: `ruby3.2`, `ruby3.3` diff --git a/src/i18n/content/pt/docs/apm/agents/java-agent/getting-started/compatibility-requirements-java-agent.mdx b/src/i18n/content/pt/docs/apm/agents/java-agent/getting-started/compatibility-requirements-java-agent.mdx index 65c962b6d14..f248b1aa23b 100644 --- a/src/i18n/content/pt/docs/apm/agents/java-agent/getting-started/compatibility-requirements-java-agent.mdx +++ b/src/i18n/content/pt/docs/apm/agents/java-agent/getting-started/compatibility-requirements-java-agent.mdx @@ -130,7 +130,7 @@ O agente automaticamente utiliza estes frameworks e bibliotecas: * Lata de spray 1.3.1 até a mais recente * Tomcat 7.0.0 até o mais recente * TomEE 1.5 até o mais recente - * WebLogic 12.1.2.1 a 12.2.x + * WebLogic 12.1.2.1 a 14.1.1 * WebSphere 8.5.x a 9.x * WebSphere Liberty Profile 8.5 até o mais recente * WildFly 8.0.0.Final até o mais recente diff --git a/src/i18n/content/pt/docs/infrastructure/infrastructure-agent/configuration/configure-infrastructure-agent.mdx b/src/i18n/content/pt/docs/infrastructure/infrastructure-agent/configuration/configure-infrastructure-agent.mdx index 407118d0878..f133fc5d94d 100644 --- a/src/i18n/content/pt/docs/infrastructure/infrastructure-agent/configuration/configure-infrastructure-agent.mdx +++ b/src/i18n/content/pt/docs/infrastructure/infrastructure-agent/configuration/configure-infrastructure-agent.mdx @@ -62,6 +62,10 @@ Aqui estão descrições detalhadas de cada método de configuração: ```yml license_key: {{MY_LICENSE_KEY}} ``` + + + Frequentemente, o agente de infraestrutura é executado como um serviço de sistema no host, gerenciado globalmente (por exemplo, `systemd` para Linux, serviços do Windows, `launchd` para macOS, etc.). Para aplicar alterações de configuração com variáveis de ambiente nesta configuração, essas variáveis de ambiente precisam ser definidas e tornadas visíveis para o contexto isolado onde o serviço do agente de infraestrutura está sendo executado. A maneira de fazer isso depende da plataforma. Verifique a documentação do gerenciador de serviços da sua plataforma para saber como adicionar variáveis de ambiente aos serviços do sistema. + diff --git a/src/i18n/content/pt/docs/infrastructure/infrastructure-agent/configuration/infrastructure-agent-configuration-settings.mdx b/src/i18n/content/pt/docs/infrastructure/infrastructure-agent/configuration/infrastructure-agent-configuration-settings.mdx index 24c5a73070c..84d78d4b4f8 100644 --- a/src/i18n/content/pt/docs/infrastructure/infrastructure-agent/configuration/infrastructure-agent-configuration-settings.mdx +++ b/src/i18n/content/pt/docs/infrastructure/infrastructure-agent/configuration/infrastructure-agent-configuration-settings.mdx @@ -30,6 +30,14 @@ O [`license_key`](#license-key) é a única configuração necessária. Para obter um exemplo de como todas essas variáveis podem ser usadas, consulte nosso [modelo de configuração de exemplo no GitHub](https://github.com/newrelic/infrastructure-agent/blob/master/assets/examples/infrastructure/newrelic-infra-template.yml.example). +## Variáveis ambientais + +Muitas das opções de configuração listadas também admitem o uso de variáveis de ambiente para definir valores, que têm precedência sobre a configuração YAML. + + + Frequentemente, o agente de infraestrutura é executado como um serviço de sistema no host, gerenciado globalmente (por exemplo, `systemd` para Linux, serviços do Windows, `launchd` para macOS, etc.). Para aplicar alterações de configuração com variáveis de ambiente nesta configuração, essas variáveis de ambiente precisam ser definidas e tornadas visíveis para o contexto isolado onde o serviço do agente de infraestrutura está sendo executado. A maneira de fazer isso depende da plataforma. Verifique a documentação do gerenciador de serviços da sua plataforma para saber como adicionar variáveis de ambiente aos serviços do sistema. + + ## Variáveis de agente [#agent-variables] diff --git a/src/i18n/content/pt/docs/mobile-monitoring/mobile-monitoring-ui/mobile-logs.mdx b/src/i18n/content/pt/docs/mobile-monitoring/mobile-monitoring-ui/mobile-logs.mdx index 8cea1ff1b7b..a0a09535227 100644 --- a/src/i18n/content/pt/docs/mobile-monitoring/mobile-monitoring-ui/mobile-logs.mdx +++ b/src/i18n/content/pt/docs/mobile-monitoring/mobile-monitoring-ui/mobile-logs.mdx @@ -440,6 +440,7 @@ Lembre-se de que ao usar a API de logging, você só deve usar o nível de log d CrossNewRelic.Current.LogAttributes(new Dictionary() { + { "level","info"}, { "BreadNumValue", 12.3 }, { "BreadStrValue", "MAUIBread" }, { "BreadBoolValue", true }, @@ -489,14 +490,16 @@ Lembre-se de que ao usar a API de logging, você só deve usar o nível de log d "BreadNumValue": 12.3, "BreadStrValue": "FlutterBread", "BreadBoolValue": true, - "message": "This is a message with attributes" + "message": "This is a message with attributes", + "level":"info" }); NewrelicMobile.instance.logAttributes({ "BreadNumValue": 12.3, "BreadStrValue": "FlutterBread", "BreadBoolValue": true, - "message": "This is a message with attributes" + "message": "This is a message with attributes", + "level":"info" }); ``` @@ -590,6 +593,7 @@ Lembre-se de que ao usar a API de logging, você só deve usar o nível de log d CrossNewRelicClient.Current.LogAttributes(new Dictionary() { + {"level", "info"}, { "BreadNumValue", 12.3 }, { "BreadStrValue", "XamBread" }, { "BreadBoolValue", true }, @@ -635,6 +639,7 @@ Lembre-se de que ao usar a API de logging, você só deve usar o nível de log d NewRelicAgent.LogAttributes(new Dictionary() { + {"level", "info"}, {"BreadNumValue", 12.3 }, {"BreadStrValue", "UnityBread" }, {"BreadBoolValue", true }, diff --git a/src/i18n/content/pt/docs/new-relic-solutions/new-relic-one/introduction-new-relic-platform.mdx b/src/i18n/content/pt/docs/new-relic-solutions/new-relic-one/introduction-new-relic-platform.mdx index 164768662ea..01bc982aca6 100644 --- a/src/i18n/content/pt/docs/new-relic-solutions/new-relic-one/introduction-new-relic-platform.mdx +++ b/src/i18n/content/pt/docs/new-relic-solutions/new-relic-one/introduction-new-relic-platform.mdx @@ -276,7 +276,7 @@ Aqui estão algumas opções para compartilhar páginas e visualizações da int - Para compartilhar uma página inteira da interface do New Relic, use o ícone do link permanente próximo ao topo da plataforma. Lembre-se de que esses links expiram se não forem usados em um período de seis meses. + Para compartilhar uma página inteira da interface do New Relic, use o ícone de link permanente próximo ao topo da plataforma. diff --git a/src/i18n/content/pt/docs/query-your-data/explore-query-data/dashboards/dashboards-charts-import-export-data.mdx b/src/i18n/content/pt/docs/query-your-data/explore-query-data/dashboards/dashboards-charts-import-export-data.mdx index dbd497a9653..dd75211a57b 100644 --- a/src/i18n/content/pt/docs/query-your-data/explore-query-data/dashboards/dashboards-charts-import-export-data.mdx +++ b/src/i18n/content/pt/docs/query-your-data/explore-query-data/dashboards/dashboards-charts-import-export-data.mdx @@ -74,7 +74,7 @@ Embora poderosa, a exportação como CSV tem limitações. Algumas coisas para m Em qualquer dashboard, compartilhe-o com uma destas opções: -* Copie o link permanente do dashboard clicando no ícone do link no canto superior direito do dashboard. link permanente compartilhe um link direto para o dashboard. Lembre-se de que esses links expiram se não forem usados em um período de seis meses. +* Copie o link permanente do dashboard clicando no ícone de link no canto superior direito de um dashboard. link permanente compartilhe um link direto para o dashboard. * Copie seu dashboard **as JSON** e adicione-o à área de transferência clicando no botão **...** no canto superior direito e selecionando **Copy JSON to clipboard**. Você também pode [duplicar seu dashboard](/docs/query-your-data/explore-query-data/dashboards/introduction-dashboards/#dashboards-clone). diff --git a/src/i18n/content/pt/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda.mdx b/src/i18n/content/pt/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda.mdx index a874a8e8a8c..98ef8890ffa 100644 --- a/src/i18n/content/pt/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda.mdx +++ b/src/i18n/content/pt/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda.mdx @@ -128,7 +128,7 @@ Se quiser saber mais sobre nossa CLI, consulte [nosso repositório CLI](https:// Recomendamos os seguintes tempos de execução: * Node.js: `nodejs16.x`, `nodejs18.x`, `nodejs20.x` -* Python: `python3.8`, `python3.9`, `python3.10`, `python3.11`, `python3.12` +* Python: `python3.8`, `python3.9`, `python3.10`, `python3.11`, `python3.12`, `python3.13` * Vá: `provided.al2`, `provided.al2023` * Java: `java8.al2`, `java11`, `java17`, `java21` * Ruby: `ruby3.2`, `ruby3.3`