diff --git a/src/content/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator.mdx b/src/content/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator.mdx index 707f2b6644f..86495627de2 100644 --- a/src/content/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator.mdx +++ b/src/content/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator.mdx @@ -332,6 +332,28 @@ You've got to specify the APM agent and its version within the instrumentation C [.NET](https://hub.docker.com/repository/docker/newrelic/newrelic-dotnet-init/general) + + + dotnet-windows2022 + + + `newrelic-dotnet-windows2022-init:latest` + + + [.NET on Windows 2022](https://hub.docker.com/repository/docker/newrelic/newrelic-dotnet-windows2022-init/general) + + + + + dotnet-windows2025 + + + `newrelic-dotnet-windows2025-init:latest` + + + [.NET on Windows 2025](https://hub.docker.com/repository/docker/newrelic/newrelic-dotnet-windows2025-init/general) + + java diff --git a/src/content/docs/licenses/license-information/distributed-licenses/new-relic-agent-software-notice.mdx b/src/content/docs/licenses/license-information/distributed-licenses/new-relic-agent-software-notice.mdx index c37795fd177..93adf5c6013 100644 --- a/src/content/docs/licenses/license-information/distributed-licenses/new-relic-agent-software-notice.mdx +++ b/src/content/docs/licenses/license-information/distributed-licenses/new-relic-agent-software-notice.mdx @@ -1,5 +1,5 @@ --- -title: New Relic Agent Software Notice +title: New Relic Software License tags: - Licenses - License information @@ -16,22 +16,35 @@ translate: - fr --- -This software is © 2008-2021 New Relic, Inc. and its licensors. +## Acceptance [#acceptance] -This software is solely for use with New Relic’s proprietary SaaS service (“**New Relic Service**”), so to use the software you must have a valid account for the New Relic Service under a separate agreement with New Relic (“**Subscription Agreement**”). You may only use the software to support your use of the New Relic Service as permitted in the Subscription Agreement. Without a Subscription Agreement, you may not use the software. +This software license applies to the repositories, directories, or files that it has been associated with (referred to here as “the Software”). In order to get any license under these terms, you must agree to them as both strict obligations and conditions to all your licenses. -All other use is prohibited. New Relic and its suppliers retain all right, title and interest (including intellectual property rights) in the software. +## License [#license] -The Subscription Agreement will control in event of a conflict with this notice. Unless otherwise agreed by New Relic in your Subscription Agreement: +New Relic grants you a license for the Software to do everything you might do with the Software that would otherwise infringe the New Relic’s copyrights or patent rights, conditional on only using the Software for Permitted Purposes and compliance with all other Restrictions on Use. All other uses are prohibited. -* You may not use, copy, distribute or sublicense the software, use the software on behalf of third parties, reverse engineer or decompile the software, modify or create derivative works of the software, use the software for competitive analysis or benchmarking, or remove or obscure any proprietary notices in the software. +## Permitted purposes [#permitted-purposes] -* **The software is provided “AS IS” and New Relic disclaims all warranties, whether express, implied, statutory or otherwise, including warranties of merchantability, fitness for a particular purpose, title or noninfringement.** +The Software is solely for use with New Relic’s proprietary SaaS service (“New Relic Service”). To use the Software you must have a valid and active subscription agreement to the New Relic Service. You may not use the Software in conjunction with any other similar service. -* **To the full extent permitted by law, New Relic will have no liability arising from or related to the software or under this notice for any direct, indirect, special, incidental, or consequential damages of any kind, even if advised of their possibility in advance, and regardless of legal theory (whether contract, tort, negligence, strict liability or otherwise).** +## Restrictions on Use [#restrictions] +
    +
  1. The use of the Software is limited to you and your organization. You cannot expose the Software to third parties via the network or use the Software on behalf of anyone else.
    2. +
  2. You cannot modify the Software. You can compile or link the Software into your programs as described in the New Relic documentation, but you cannot otherwise make any derivative works of the Software.
    3. +
  3. You cannot reverse engineer or decompile the Software.
    4. +
  4. You cannot use the Software for competitive analysis, benchmarking, or any purposes that compete with or are intended to compete with New Relic.
    5. +
  5. You cannot remove or obscure any proprietary notices in the Software.
    6. +
  6. You can only copy the Software to the extent needed to use the Software within your organization. You cannot distribute the Software to any third parties.
    7. +
  7. You can only use the New Relic Services and the Software consistent with New Relic’s product documentation and Acceptable Use Policy.
    8. +
-The software may contain third-party open source software (“**OSS**”) as described [here](/docs/licenses/product-or-service-licenses) and at [https://github.com/newrelic](https://github.com/newrelic). To the extent required by the OSS license, that license will apply to the OSS when used on a stand-alone basis. +## Other Terms [#other-terms] +
    +
  1. The Software is provided “AS IS.” New Relic disclaims all warranties, whether express, implied, statutory or otherwise, including warranties of merchantability, fitness for a particular purpose, title, and noninfringement.
    2. -For avoidance of doubt, you may copy and distribute New Relic agents pursuant to your Subscription Agreement for New Relic and New Relic Mobile and as set forth: [Introduction to mobile monitoring](/docs/mobile-monitoring/new-relic-mobile/get-started/introduction-mobile-monitoring/) and [Install the browser agent](/docs/browser/new-relic-browser/installation/install-new-relic-browser-agent) pages. +
  2. To the full extent permitted by law, New Relic will have no liability arising from or related to the Software or from this license for any direct, indirect, special, incidental, or consequential damages of any kind, even if advised of their possibility in advance, and regardless of legal theory (whether contract, tort, negligence, strict liability or otherwise).
    3. + +
  3. The Software may contain third-party software, including open source software (“OSS”). The third party software is governed by its own license and subject to its own terms, disclosed in the provided licensing information associated with the third party components. If a source code disclosure is required under the terms of the license covering any OSS component, the source code can be requested of New Relic by emailing source-request@newrelic.com.
    4. +
-Software versions New Relic makes available under an OSS license (such as Apache 2.0) are governed by the terms of the applicable OSS license. For a current list of New Relic software versions released as OSS please visit [https://opensource.newrelic.com/](https://github.com/newrelic?utf8=%E2%9C%93&q=&type=&language=). diff --git a/src/i18n/content/es/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx b/src/i18n/content/es/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx index e522367690a..e21b822bc72 100644 --- a/src/i18n/content/es/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx +++ b/src/i18n/content/es/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx @@ -36,7 +36,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum - The .NET agent is compatible with .NET Core version 3.1, and .NET 5.0, 6.0, 7.0, 8.0, 9.0, and 10.0. + El agente .NET es compatible con .NET Core versión 3.1 y .NET 5.0, 6.0, 7.0, 8.0, 9.0 y 10.0. El agente solo es totalmente compatible cuando la aplicación instrumentada tiene como objetivo [los tiempos de ejecución .NET actualmente soportados por Microsoft](https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core). Es probable que el agente funcione con los tiempos de ejecución EOL que se enumeran a continuación, pero no probamos nuevas versiones del agente con tiempos de ejecución EOL. @@ -271,7 +271,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum - The .NET agent is compatible with applications targeting .NET Core 3.1, and .NET 5.0, 6.0, 7.0, 8.0, 9.0, and 10.0. You can find the target framework in your `.csproj` file. Agent compatibility varies across different versions of .NET Core. + El agente .NET es compatible con aplicaciones destinadas a .NET Core 3.1 y .NET 5.0, 6.0, 7.0, 8.0, 9.0 y 10.0. Puede encontrar el framework objetivo en su archivo `.csproj`. La compatibilidad del agente varía según las diferentes versiones de .NET Core. Compatible: @@ -319,8 +319,8 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum El agente .NET instrumentó automáticamente este marco de aplicación: - * ASP.NET Core MVC 2.0, 2.1, 2.2, 3.0, 3.1, 5.0, 6.0, 7.0, 8.0, 9.0, and 10.0 (includes Web API) - * ASP.NET Core Razor Pages 6.0, 7.0, 8.0, 9.0, and 10.0 (starting with .NET agent version 10.19.0) + * ASP.NET Core MVC 2.0, 2.1, 2.2, 3.0, 3.1, 5.0, 6.0, 7.0, 8.0, 9.0 y 10.0 (incluye API sitio web) + * ASP.NET Core Razor Pages 6.0, 7.0, 8.0, 9.0 y 10.0 (a partir de la versión 10.19.0 del agente .NET) @@ -357,7 +357,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum El agente .NET `v9.2.0` o superior instrumentó automáticamente la biblioteca [Microsoft.Azure.Cosmos](https://www.nuget.org/packages/Microsoft.Azure.Cosmos) . * Versión mínima admitida: 3.17.0 - * Latest verified compatible version: 3.56.0 + * Última versión compatible verificada: 3.56.0 * Las versiones 3.35.0 y superiores son compatibles a partir del agente .NET v10.32.0 @@ -434,7 +434,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum Utilice [Npgsql](https://www.nuget.org/packages/Npgsql/) * Versión mínima soportada: 4.0.0 - * Latest verified compatible version: 7.0.7 + * Última versión compatible verificada: 7.0.7 También se pueden instrumentar versiones anteriores de Npgsql, pero es posible que haya duplicados y/o faltan métricas. @@ -452,7 +452,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum Versión mínima admitida: 2.3.0 - Latest verified compatible version: 3.5.2 + Última versión compatible verificada: 3.5.2 Versiones 3.0.0 y superiores son compatibles a partir del agente .NET v10.40.0. @@ -570,7 +570,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum * Versión mínima compatible: 3.5.0 - * Latest verified compatible version: 4.0.10.1 + * Última versión compatible verificada: 4.0.10.1 * Versión mínima del agente requerida: 10.33.0 @@ -907,7 +907,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum * Versión mínima soportada: 3.5.2 - * Latest verified compatible version: 7.1.2 + * Última versión compatible verificada: 7.1.2 @@ -921,7 +921,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum * Versión mínima soportada: 7.1.0 - * Latest verified compatible version: 8.5.7 + * Última versión compatible verificada: 8.5.7 @@ -949,7 +949,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum * Versión mínima compatible: 3.7.0 - * Latest verified compatible version: 4.0.7.6 + * Última versión compatible verificada: 4.0.7.6 @@ -963,7 +963,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum * Versión mínima compatible: 3.7.0 - * Latest verified compatible version: 4.0.3.5 + * Última versión compatible verificada: 4.0.3.5 @@ -1343,7 +1343,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum El agente .NET `v9.2.0` o superior instrumenta automáticamente la biblioteca [Microsoft.Azure.Cosmos](https://www.nuget.org/packages/Microsoft.Azure.Cosmos) . * Versión mínima admitida: 3.17.0 - * Latest verified compatible version: 3.56.0 + * Última versión compatible verificada: 3.56.0 * Las versiones 3.35.0 y superiores son compatibles a partir del agente .NET v10.32.0 @@ -1461,7 +1461,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum Versión mínima admitida: 2.3.0 - Latest verified compatible version: 3.5.2 + Última versión compatible verificada: 3.5.2 Versiones 3.0.0 y superiores son compatibles a partir del agente .NET v10.40.0. @@ -1531,7 +1531,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum Utilice [Npgsql](https://www.nuget.org/packages/Npgsql/) * Versión mínima soportada: 4.0.0 - * Latest verified compatible version: 7.0.7 + * Última versión compatible verificada: 7.0.7 También se pueden instrumentar versiones anteriores de Npgsql, pero es posible que haya duplicados y/o faltan métricas. @@ -1629,7 +1629,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum * Versión mínima compatible: 3.5.0 - * Latest verified compatible version: 4.0.10.1 + * Última versión compatible verificada: 4.0.10.1 * Versión mínima del agente requerida: 10.33.0 @@ -1710,7 +1710,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum Versión mínima admitida: 105.2.3 - Latest verified compatible version: 113.0.0 + Última versión compatible verificada: 113.0.0 Versiones incompatibles conocidas: 106.8.0, 106.9.0, 106.10.0, 106.10.1 @@ -2012,7 +2012,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum * Versión mínima soportada: 3.5.2 - * Latest verified compatible version: 6.8.1 + * Última versión compatible verificada: 6.8.1 @@ -2026,7 +2026,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum * Versión mínima soportada: 7.1.0 - * Latest verified compatible version: 8.5.7 + * Última versión compatible verificada: 8.5.7 @@ -2054,7 +2054,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum * Versión mínima compatible: 3.7.0 - * Latest verified compatible version: 4.0.7.6 + * Última versión compatible verificada: 4.0.7.6 @@ -2068,7 +2068,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum * Versión mínima compatible: 3.7.0 - * Latest verified compatible version: 4.0.3.5 + * Última versión compatible verificada: 4.0.3.5 diff --git a/src/i18n/content/es/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx b/src/i18n/content/es/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx index e906e1f367b..899c489e421 100644 --- a/src/i18n/content/es/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx +++ b/src/i18n/content/es/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx @@ -268,32 +268,32 @@ Luego de la instalación, el agente se instrumenta automáticamente con nuestro | Nombre del paquete | Versión mínima admitida | Última versión publicada | Introducido en\* | | --------------------------------- | ----------------------- | ------------------------ | -------------------------------------- | | `@apollo/gateway` | 2.3.0 | 2.12.1 | `@newrelic/apollo-server-plugin@1.0.0` | -| `@apollo/server` | 4.0.0 | 5.1.0 | `@newrelic/apollo-server-plugin@2.1.0` | -| `@aws-sdk/client-bedrock-runtime` | 3.474.0 | 3.934.0 | 11.13.0 | -| `@aws-sdk/client-dynamodb` | 3.0.0 | 3.934.0 | 8.7.1 | -| `@aws-sdk/client-sns` | 3.0.0 | 3.934.0 | 8.7.1 | -| `@aws-sdk/client-sqs` | 3.0.0 | 3.934.0 | 8.7.1 | -| `@aws-sdk/lib-dynamodb` | 3.377.0 | 3.934.0 | 8.7.1 | +| `@apollo/server` | 4.0.0 | 5.2.0 | `@newrelic/apollo-server-plugin@2.1.0` | +| `@aws-sdk/client-bedrock-runtime` | 3.474.0 | 3.943.0 | 11.13.0 | +| `@aws-sdk/client-dynamodb` | 3.0.0 | 3.943.0 | 8.7.1 | +| `@aws-sdk/client-sns` | 3.0.0 | 3.943.0 | 8.7.1 | +| `@aws-sdk/client-sqs` | 3.0.0 | 3.943.0 | 8.7.1 | +| `@aws-sdk/lib-dynamodb` | 3.377.0 | 3.943.0 | 8.7.1 | | `@aws-sdk/smithy-client` | 3.47.0 | 3.374.0 | 8.7.1 | -| `@azure/functions` | 4.7.0 | 4.9.0 | 12.18.0 | +| `@azure/functions` | 4.7.0 | 4.10.0 | 12.18.0 | | `@elastic/elasticsearch` | 7.16.0 | 9.2.0 | 11.9.0 | | `@google/genai` | 1.1.0 | 1.30.0 | 12.21.0 | -| `@grpc/grpc-js` | 1.4.0 | 1.14.1 | 8.17.0 | +| `@grpc/grpc-js` | 1.4.0 | 1.14.2 | 8.17.0 | | `@hapi/hapi` | 20.1.2 | 21.4.4 | 9.0.0 | -| `@koa/router` | 12.0.1 | 14.0.0 | 3.2.0 | -| `@langchain/core` | 0.1.17 | 1.0.6 | 11.13.0 | -| `@modelcontextprotocol/sdk` | 1.13.0 | 1.22.0 | 13.2.0 | -| `@nestjs/cli` | 9.0.0 | 11.0.12 | 10.1.0 | +| `@koa/router` | 12.0.1 | 15.0.0 | 3.2.0 | +| `@langchain/core` | 0.1.17 | 1.1.1 | 11.13.0 | +| `@modelcontextprotocol/sdk` | 1.13.0 | 1.24.1 | 13.2.0 | +| `@nestjs/cli` | 9.0.0 | 11.0.14 | 10.1.0 | | `@opensearch-project/opensearch` | 2.1.0 | 3.5.1 | 12.10.0 | -| `@prisma/client` | 5.0.0 | 7.0.0 | 11.0.0 | -| `@smithy/smithy-client` | 2.0.0 | 4.9.7 | 11.0.0 | +| `@prisma/client` | 5.0.0 | 7.0.1 | 11.0.0 | +| `@smithy/smithy-client` | 2.0.0 | 4.9.9 | 11.0.0 | | `amqplib` | 0.5.0 | 0.10.9 | 2.0.0 | | `aws-sdk` | 2.2.48 | 2.1692.0 | 6.2.0 | | `bluebird` | 2.0.0 | 3.7.2 | 1.27.0 | | `bunyan` | 1.8.12 | 1.8.15 | 9.3.0 | | `cassandra-driver` | 3.4.0 | 4.8.0 | 1.7.1 | | `connect` | 3.0.0 | 3.7.0 | 2.6.0 | -| `express` | 4.15.0 | 5.1.0 | 2.6.0 | +| `express` | 4.15.0 | 5.2.1 | 2.6.0 | | `fastify` | 3.0.0 | 5.6.2 | 8.5.0 | | `generic-pool` | 3.0.0 | 3.9.0 | 0.9.0 | | `ioredis` | 4.0.0 | 5.8.2 | 1.26.2 | @@ -305,13 +305,13 @@ Luego de la instalación, el agente se instrumenta automáticamente con nuestro | `mongodb` | 4.1.4 | 7.0.0 | 1.32.0 | | `mysql` | 2.16.0 | 2.18.1 | 1.32.0 | | `mysql2` | 2.0.0 | 3.15.3 | 1.32.0 | -| `next` | 13.4.19 | 16.0.3 | 12.0.0 | +| `next` | 13.4.19 | 16.0.6 | 12.0.0 | | `openai` | 4.0.0 | 6.9.1 | 11.13.0 | | `pg` | 8.2.0 | 8.16.3 | 9.0.0 | | `pg-native` | 3.0.0 | 3.5.2 | 9.0.0 | | `pino` | 8.0.0 | 10.1.0 | 8.11.0 | | `q` | 1.3.0 | 1.5.1 | 1.26.2 | -| `redis` | 3.1.0 | 5.9.0 | 1.31.0 | +| `redis` | 3.1.0 | 5.10.0 | 1.31.0 | | `restify` | 11.0.0 | 11.1.0 | 2.6.0 | | `superagent` | 3.0.0 | 10.2.3 | 4.9.0 | | `undici` | 5.0.0 | 7.16.0 | 11.1.0 | diff --git a/src/i18n/content/es/docs/query-your-data/explore-query-data/dashboards/share-charts-dashboards-externally.mdx b/src/i18n/content/es/docs/query-your-data/explore-query-data/dashboards/share-charts-dashboards-externally.mdx index 3b97bca8255..6b6ef133141 100644 --- a/src/i18n/content/es/docs/query-your-data/explore-query-data/dashboards/share-charts-dashboards-externally.mdx +++ b/src/i18n/content/es/docs/query-your-data/explore-query-data/dashboards/share-charts-dashboards-externally.mdx @@ -135,16 +135,6 @@ Esta característica incluye múltiples capas y condiciones de seguridad para ga * **Acceso basado en sesiones**: Luego de acceder al dashboard, la sesión permanece activa durante 120 horas. Si intentan acceder al dashboard luego de este periodo, o si la sesión del navegador caduca, se les pedirá la contraseña. Si se restablece la contraseña, la sesión caduca tan pronto como se actualiza el widget. El usuario externo deberá introducir la nueva contraseña. * **Verificación reCAPTCHA**: Si tienen varios intentos fallidos de acceder al dashboard, deberán completar una verificación reCAPTCHA antes de volver a introducir la contraseña. - - ### Precios [#public-dashboard-pricing] - - Al compartir las URL dashboard en tiempo real, es importante comprender los costos asociados y cómo gestionarlos eficazmente. **Public Dashboards** es una característica del producto Calculate avanzado que se ofrece como [complemento](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/add-on-billing) o como parte del modelo de precios de Calculate. [Las CCU](/docs/licenses/license-information/product-definitions/new-relic-one-pricing-definitions/#compute-capacity-unit) avanzadas se consumen cuando se ejecutan consultas desde las visualizaciones dashboard, lo que ocurre en los siguientes casos: - - * Al cargar la página - * En el selector de tiempo cambia - * Acerca de los activadores de frecuencia de actualización - - Puede monitorear sus costos de uso desde **[New Relic Administration](https://one.newrelic.com/admin-portal) > Consumption Management > Advanced capabilities**. Para optimizar sus costos, consulte la sección [de mejores prácticas de gestión de precios](#pricing-management) . @@ -256,6 +246,16 @@ Esta característica incluye múltiples capas y condiciones de seguridad para ga + ### Precios [#public-dashboard-pricing] + + Al compartir las URL dashboard en tiempo real, es importante comprender los costos asociados y cómo gestionarlos eficazmente. **Public Dashboards** es una característica del producto Calculate avanzado que se ofrece como [complemento](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/add-on-billing) o como parte del modelo de precios de Calculate. [Las CCU](/docs/licenses/license-information/product-definitions/new-relic-one-pricing-definitions/#compute-capacity-unit) avanzadas se consumen cuando se ejecutan consultas desde las visualizaciones dashboard, lo que ocurre en los siguientes casos: + + * Al cargar la página + * En el selector de tiempo cambia + * Acerca de los activadores de frecuencia de actualización + + Puede monitorear sus costos de uso desde **[New Relic Administration](https://one.newrelic.com/admin-portal) > Consumption Management > Advanced capabilities**. Para optimizar sus costos, consulte la sección [de mejores prácticas de gestión de precios](#pricing-management) . + ### Mejores practicas [#best-practices] Para gestionar de forma eficiente los precios y la seguridad de las contraseñas relacionadas con dashboard público, siga estas buenas prácticas: diff --git a/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-11-28-2025.mdx b/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-11-28-2025.mdx new file mode 100644 index 00000000000..b61cc979b87 --- /dev/null +++ b/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-11-28-2025.mdx @@ -0,0 +1,72 @@ +--- +subject: Docs +releaseDate: '2025-11-28' +version: 'November 24 - November 28, 2025' +translationType: machine +--- + +### Nuevos documentos + +* Se agregó [soporte de agente PHP para Laravel](/docs/apm/agents/php-agent/frameworks-libraries/laravel) para brindar una guía completa para Laravel transacción sitio web, Laravel Queue Workers y Laravel Horizon Workers. +* Se agregó la guía de resolución de problemas [PHPUnit se queda sin memoria](/docs/apm/agents/php-agent/troubleshooting/phpunit-incompatibility) para problemas de compatibilidad PHPUnit 11+ con el agente PHP New Relic. + +### Cambios importantes + +* Se actualizaron [los conceptos de administración de usuarios](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts) y la documentación RBAC relacionada con una nueva experiencia de creación de roles y concesiones que presenta tres tipos de roles (roles basados en organización, roles basados en cuenta y roles basados en entidad) que se consolidan en la pestaña **Roles**. +* [Canales de alerta](/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-channels) actualizados con métodos y ejemplos de API de integración de Microsoft Teams. +* [Destinos de alerta](/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-destinations) actualizados con soporte de integración con Microsoft Teams. + +### Cambios menores + +* Se actualizaron [los precios y la facturación de New Relic](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing) para aportar claridad a los modelos de precios y las capacidades que ofrece. +* [Configuración de agente .NET](/docs/apm/agents/net-agent/configuration/net-agent-configuration) actualizada con opciones de configuración de instrumentación del navegador. +* [Monitoreo de navegador actualizado con agente .NET](/docs/apm/agents/net-agent/other-features/browser-monitoring-net-agent) con guía de configuración simplificada. +* Se actualizaron [los requisitos de compatibilidad del agente PHP](/docs/apm/agents/php-agent/getting-started/php-agent-compatibility-requirements) con soporte para Laravel Horizon y se eliminó la compatibilidad con Windows de 32 bits. +* [Procesamiento del recolectorOpenTelemetry ](/docs/opentelemetry/get-started/collector-processing/opentelemetry-collector-processing-intro)actualizado con guía de configuración actualizada. +* [Configuración de redes](/docs/new-relic-solutions/get-started/networks) actualizada con dualstack fijo extremo vínculo permanente. +* [Cumplimiento de TISAX](/docs/security/security-privacy/compliance/certificates-standards-regulations/tisax) actualizado con información de cumplimiento actualizada. + +### Notas de la versión + +* Se anunció el 30 de junio de 2026 como la fecha de fin de vida útil para los [gráficos integrados legacy APM con información valiosa previa.](/eol/2025/11/pre-insights/) + +* Mantener actualizado con nuestros últimos lanzamientos: + + * [Integración Kubernetes v3.50.2](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-50-2): + + * Integración actualizada incluida en newrelic-infrastructure-3.55.2 y nri-bundle-6.0.26. + + * [Logs 251120](/docs/release-notes/logs-release-notes/logs-25-11-20): + + * Se corrigió CVE-2025-53643 en lambda de AWS-log-ingestion. + * Biblioteca aiohttp actualizada a 3.13.2 y versión poética a 1.8.3. + + * [Agente React Native v1.5.12](/docs/release-notes/mobile-release-notes/react-native-release-notes/react-native-agent-1512): + + * Agente nativo Android actualizado a la versión 7.6.13. + * Agente nativo de iOS actualizado a la versión 7.6.0. + + * [Agente Capacitor v1.5.12](/docs/release-notes/mobile-release-notes/capacitor-release-notes/capacitor-agent-1512): + + * Agente nativo Android actualizado a la versión 7.6.13. + * Agente nativo de iOS actualizado a la versión 7.6.0. + + * [Agente Flutter v1.1.19](/docs/release-notes/mobile-release-notes/flutter-release-notes/flutter-agent-1119): + + * Agente nativo Android actualizado a la versión 7.6.13. + * Agente nativo de iOS actualizado a la versión 7.6.0. + + * [Agente de Unity v1.4.11](/docs/release-notes/mobile-release-notes/unity-release-notes/unity-agent-1411): + + * Agente nativo Android actualizado a la versión 7.6.13. + * Agente nativo de iOS actualizado a la versión 7.6.0. + + * [Agente Cordova v7.0.11](/docs/release-notes/mobile-release-notes/cordova-release-notes/cordova-agent-711): + + * Agente nativo Android actualizado a la versión 7.6.13. + * Agente nativo de iOS actualizado a la versión 7.6.0. + + * [Agente .NET MAUI v1.1.14](/docs/release-notes/mobile-release-notes/net-maui-release-notes/net-maui-agent-1114): + + * Agente nativo Android actualizado a la versión 7.6.13. + * Agente nativo de iOS actualizado a la versión 7.6.0. \ No newline at end of file diff --git a/src/i18n/content/es/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/compatibility-requirement-lambda-monitoring.mdx b/src/i18n/content/es/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/compatibility-requirement-lambda-monitoring.mdx index e5ee6b8c88f..87f048a61a0 100644 --- a/src/i18n/content/es/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/compatibility-requirement-lambda-monitoring.mdx +++ b/src/i18n/content/es/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/compatibility-requirement-lambda-monitoring.mdx @@ -11,13 +11,17 @@ Antes de [instalar Lambda Monitoreo](/docs/serverless-function-monitoring/aws-la Antes de habilitar el monitoreo sin servidor usando nuestra capa Lambda, necesitará: -1. Una cuenta de New Relic con un [rol de administrador o](/docs/accounts/original-accounts-billing/original-users-roles/users-roles-original-user-model/#roles) que tenga el [rol complementario](/docs/accounts/original-accounts-billing/original-users-roles/users-roles-original-user-model#add-on) **de administrador de infraestructura**. +* Una cuenta de New Relic con un [rol de administrador](/docs/accounts/accounts-billing/new-relic-one-user-management/introduction-managing-users) o que tenga el [rol complementario](/docs/accounts/original-accounts-billing/original-users-roles/users-roles-original-user-model#add-on) de **Infrastructure manager**. -2. Un . +* Un . -3. Una cuenta de AWS con permisos para crear recursos de IAM, secretos administrados y Lambdas. También necesita permisos para crear una pila de CloudFormation y depósitos de S3. +* Una cuenta de AWS con permisos para crear recursos de IAM, secretos administrados y Lambdas. También necesita permisos para crear una pila de CloudFormation y depósitos de S3. -## Tiempos de ejecución admitidos + + New Relic recomienda integrar su cuenta AWS con New Relic usando la [integraciónAWS ](/docs/infrastructure/amazon-integrations/get-started/introduction-aws-integrations/)para descubrir y monitorear automáticamente su función Lambda. Esto le permite aprovechar todo el poder de New Relic APM para su función sin servidor. + + +## Tiempos de ejecución admitidos [#supported-runtimes] Según el tipo de instrumentación, se admiten los siguientes tiempos de ejecución. @@ -58,8 +62,18 @@ Según el tipo de instrumentación, se admiten los siguientes tiempos de ejecuci * Java: La instrumentación en capas y SDK de New Relic Java son compatibles con `com.amazonaws:aws-lambda-java-events` versiones `3.0.0` hasta la más reciente. -## Que sigue +## Artículos relacionados [#related-docs] - Comience con la instrumentación y configuración de su función .LambdaAprenda a emplear New Relic para monitorear su AWS función Lambda. + + Instrumente su función Lambda con el enfoque en capas de New Relic. + + + + Instrumento tu función Lambda usando SDK. + + + + Instrumente su función Lambda con el enfoque contenedorizado de New Relic. + \ No newline at end of file diff --git a/src/i18n/content/es/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/containerized-images.mdx b/src/i18n/content/es/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/containerized-images.mdx index 5a49dc8ef1e..313ed10b4e2 100644 --- a/src/i18n/content/es/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/containerized-images.mdx +++ b/src/i18n/content/es/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/containerized-images.mdx @@ -202,10 +202,34 @@ Aquí hay una guía para agregar nuestra capa prediseñada a su código. * [Instrumentación en capas](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/instrument-your-own/#console) * [Instrumentación basada en SDK](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/enable-serverless-monitoring-aws-lambda-layerless) + + + ### Buscar y utilizar datos [#find-data] + + Luego de instrumentar su función Lambda AWS, puede buscar y usar los datos en la interfaz New Relic APM. Los datos están organizados en varias áreas clave, cada una de las cuales proporciona información valiosa sobre el rendimiento y el estado de su función Lambda. + + En la interfaz APM, puede explorar varios aspectos de su función Lambda, incluido [el rastreo distribuido](https://docs.newrelic.com/docs/distributed-tracing/concepts/introduction-distributed-tracing/), [los mapas de servicios](https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/ui-data/service-maps/service-maps/), [las transacciones](https://docs.newrelic.com/docs/apm/transactions/intro-transactions/transactions-new-relic-apm//) y [el análisis de errores](https://docs.newrelic.com/docs/errors-inbox/getting-started/), y muchos más. Cada una de estas áreas proporciona información detallada y valiosa sobre el rendimiento, la latencia y la tasa de errores de su función Lambda, lo que le permite identificar y resolver problemas rápidamente. + + + La experiencia de Invocación ahora está integrada con APM traza de la transacción. Esto le permite emplear un `AWS RequestId` específico para explorar en profundidad una traza de la transacción de APM para obtener información detallada sobre esa ejecución Lambda en individuo. + + + Para ver su función Lambda en la interfaz New Relic APM : + + 1. Vaya a [https://one.newrelic.com](https://one.newrelic.com) > APM & Services. + 2. Establezca los criterios de búsqueda como `isLambdaFunction = true`. + 3. De la lista mostrada, seleccione su función Lambda para ver los datos. + -## Que sigue +## Artículos relacionados [#related-docs] - Obtenga más información sobre los tiempos de ejecución admitidos y los requisitos previos. Aprenda a usar New Relic para monitorear su función Lambda AWS Aprenda a solucionar problemas relacionados con la instalación. + + Obtenga más información sobre los entornos de ejecución compatibles y los requisitos previos + + + + Aprenda a solucionar problemas relacionados con la instalación + \ No newline at end of file diff --git a/src/i18n/content/es/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda.mdx b/src/i18n/content/es/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda.mdx index fa81b16ab03..20308aa8194 100644 --- a/src/i18n/content/es/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda.mdx +++ b/src/i18n/content/es/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda.mdx @@ -46,7 +46,7 @@ Independientemente de su entorno de ejecución, debe configurar las siguientes v - Especifica el contenedor del controlador empleado para encontrar el controlador real de su función + Especifica el contenedor del controlador empleado para encontrar el controlador real de su función. En el caso de tiempos de ejecución de Go, esta variable no es obligatoria. @@ -60,6 +60,20 @@ Independientemente de su entorno de ejecución, debe configurar las siguientes v + + + `NEW_RELIC_APM_LAMBDA_MODE` + + + + Establezca en + + `true` + + para habilitar el monitoreo APM para su función Lambda + + + `NEW_RELIC_TRUSTED_ACCOUNT_KEY` @@ -1082,6 +1096,22 @@ En función de su entorno de ejecución, puede configurar las siguientes variabl , `DEBUG` + + , + + `TRACE` + + , + + `ERROR` + + , + + `WARN` + + , + + `ALL` @@ -1195,7 +1225,9 @@ En función de su entorno de ejecución, puede configurar las siguientes variabl - Evite las comprobaciones proporcionándolas como valores separados por comas dentro de una cadena. Emplee valores de cadena + **OBSOLETO** + + Omite las comprobaciones suministrándolas como valores separados por comas dentro de una cadena. Emplee valores de cadena `handler` @@ -1227,7 +1259,17 @@ En función de su entorno de ejecución, puede configurar las siguientes variabl - Especifique el nombre de la clave secreta de AWS Secrets Manager que contiene su clave de licencia. Nota: Esto solo se emplea si NEW_RELIC_LICENSE_KEY no está configurado. + Especifique el **nombre** o **ARN** del secreto de AWS Secrets Manager que contiene su clave de licencia de New Relic. + +
+ +
+ + **Notas:** + + * Esto sólo se emplea si `` `NEW_RELIC_LICENSE_KEY` `` no está configurado. + * El secreto debe estar en la misma región de AWS que su función Lambda. + * El rol de ejecución de su función Lambda necesita la licencia `` `secretsmanager:GetSecretValue` `` para este secreto. @@ -1241,7 +1283,31 @@ En función de su entorno de ejecución, puede configurar las siguientes variabl - Especifique el nombre del parámetro SSM del almacén de parámetros de AWS Systems Manager que contiene su clave de licencia. Nota: Esto solo se emplea si NEW_RIC_LICENSE_KEY no está configurado + Especifique el **nombre** o **ARN** del parámetro del almacén de parámetros de AWS Systems Manager que contiene su clave de licencia de New Relic. + +
+ +
+ + **Notas:** + + * Esto sólo se emplea si `` `NEW_RELIC_LICENSE_KEY` `` no está configurado. + * El parámetro SSM debe estar en la misma región de AWS que su función Lambda. + * La función de ejecución de su función Lambda necesita la licencia `` `ssm:GetParameter` `` para este parámetro. + + + + + + `NEW_RELIC_CLOUD_AWS_ACCOUNT_ID` + + + + + + + + Para ayudar New Relic a mapear y mostrar correctamente las relaciones entre las entidades monitoreadas, proporcione el ID de la cuenta de AWS donde se encuentran sus recursos monitoreados, como la base de datos y la función Lambda. diff --git a/src/i18n/content/es/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own.mdx b/src/i18n/content/es/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own.mdx index 5e576147c42..c42c9bd3ec7 100644 --- a/src/i18n/content/es/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own.mdx +++ b/src/i18n/content/es/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own.mdx @@ -1,22 +1,17 @@ --- -title: instrumento tu función Lambda no contenedorizada -metaDescription: Instrument your non-containerized Lambda function +title: Instrumentación en capas +metaDescription: Instrument your Lambda function with the New Relic Lambda layer. freshnessValidatedDate: never translationType: machine --- -Una vez que vinculó con éxito sus cuentas de New Relic y AWS , puede instrumentar su función Lambda AWS no en contenedores agregando la capa New Relic Lambda. Esto integra el agente New Relic, lo que permite el monitoreo automático cada vez que se invocan sus funciones. +Puedes instrumentar tu función Lambda agregando la capa Lambda New Relic. Esto integra el agente New Relic, lo que permite el monitoreo automático cada vez que se invocan sus funciones. -a diagram depicting non-containerized lambda function instrumentation +a diagram depicting non-containerized lambda function instrumentation -## Antes de que empieces [#begin] - -* [Vincula tus cuentas de New Relic y AWS](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda#link) -* [Revise nuestros diferentes métodos de instrumentación](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda#method) + + New Relic recomienda integrar su cuenta AWS con New Relic usando la [integraciónAWS ](/docs/infrastructure/amazon-integrations/get-started/introduction-aws-integrations/)para descubrir y monitorear automáticamente su función Lambda. Esto le permite aprovechar todo el poder de New Relic APM para su función sin servidor. + ## Métodos de instrumentación [#instrumentation] @@ -25,24 +20,22 @@ New Relic ofrece varios métodos para instrumentar su función Lambda AWS para u * **Interfaz de línea de comando (CLI)**: emplee la CLI AWS para agregar rápidamente la capa New Relic a su función Lambda. * **Framework sin servidor**: integre perfectamente la instrumentación New Relic en su despliegue sin servidor. * **CloudFormation/SAM**: incluya la capa New Relic en sus plantillas de infraestructura como código. +* **AWS CDK**: agregue la capa Lambda de New Relic en su código CDK junto con otros recursos de infraestructura. * **Terraform**: gestione fácilmente la instrumentación de New Relic junto con sus otros recursos de infraestructura. * **Instrumentación manual**: agregue directamente la capa New Relic a través de la consola AWS Lambda para un control más granular. Independientemente del método que elija, la capa New Relic agrega el agente New Relic a sus funciones. Este agente instrumenta automáticamente sus funciones tras la invocación, generando una carga, `NR_LAMBDA_MONITORING`, que se envía a New Relic a través de la extensión New Relic Lambda. -Dependiendo de sus necesidades, puede optar por omitir la extensión y solo ver la telemetría en CloudWatch, omitir CloudWatch o usar CloudWatch como alternativa. La sección [CloudWatch](#CloudWatch-only) al final de este documento lo guiará a través de cada opción. +Según sus necesidades, puede elegir omitir la extensión y solo ver la telemetría en CloudWatch, omitir CloudWatch o usar CloudWatch como respaldo. La sección [CloudWatch](#CloudWatch) al final de este documento lo guiará a través de cada opción. - + Puedes instrumentar tu función Lambda con la `newrelic-lambda` CLI inicio rápido. Para instalar o actualizar la capa de instrumentación de New Relic, ejecute este comando: ```shell - newrelic-lambda layers install --nr-account-id YOUR_NR_ACCOUNT_ID --function my-function --upgrade + newrelic-lambda layers install --nr-account-id YOUR_NR_ACCOUNT_ID --function my-function --upgrade --apm ``` Este comando encuentra automáticamente la capa más nueva disponible para la región y el tiempo de ejecución de Lambda. @@ -52,99 +45,162 @@ Dependiendo de sus necesidades, puede optar por omitir la extensión y solo ver Tenga en cuenta que la CLI puede operar en muchas funciones en un lote: use `--function all`, `--function installed` o `--function not-installed` para operar en todas las funciones en una región, o solo aquellas con o sin instrumentación New Relic existente. - + El Serverless Application Model de AWS, o SAM, es una variante de las plantillas de CloudFormation que simplifica la relación de funciones con los recursos de los que dependen y la gestión del ciclo de vida de una aplicación completa. Usamos SAM y CloudFormation para la mayoría de nuestras funciones de ejemplo de Lambda, y muchas otras herramientas se crean sobre las plantillas de CloudFormation, lo que proporciona una capa adicional de abstracción. CloudFormation es un servicio de AWS que simplifica el aprovisionamiento y la gestión de recursos AWS . Al definir el estado deseado de los recursos en plantillas YAML o JSON, CloudFormation maneja automáticamente la API de llamada subyacente para crear, actualizar o eliminar recursos según sea necesario. Este enfoque declarativo automatiza la gestión de la infraestructura, garantizando coherencia y reproducibilidad. - A continuación se muestra un ejemplo de una plantilla de CloudFormation simple para una función Lambda de Node.js: - - ```yaml - AWSTemplateFormatVersion: '2010-09-09' - Transform: AWS::Serverless-2016-10-31 - Description: And example of a simple instrumented Node.js Lambda - - Resources: - NewRelicExample: - Type: AWS::Serverless::Function - Properties: - # In this example, we're using the SAM CLI to package and deploy our lambda. SAM will transform this value during the publish step. - CodeUri: newrelic-example-node/ - # The handler for your function needs to be the one provided by the instrumentation layer, below. - Handler: newrelic-lambda-wrapper.handler - Runtime: nodejs12.x - Environment: - Variables: - # For the instrumentation handler to invoke your real handler, we need this value - NEW_RELIC_LAMBDA_HANDLER: YOUR_PATH_TO_INITIAL_LAMBDA_HANDLER - # Distributed tracing needs your account ID, and your trusted account ID - NEW_RELIC_ACCOUNT_ID: YOUR_ACCOUNT_ID_HERE - # If your New Relic account has a parent account, this value should be that account ID. Otherwise, just - # your account id. - NEW_RELIC_TRUSTED_ACCOUNT_KEY: YOUR_PARENT_ACCOUNT_ID_HERE - Layers: - # This layer includes the New Relic Lambda extension, a sidecar process that sends telemetry, - # as well as the New Relic agent for Node.js, and a handler wrapper that makes integration easy. - - !Sub arn:${AWS::Partition}:lambda:${AWS::Region}:451483290750:layer:NewRelicNodeJS12X:34 - Policies: - # This policy allows the lambda to know the value of the New Relic license key. We need this so - # that we can send telemetry back to New Relic - - AWSSecretsManagerGetSecretValuePolicy: - SecretArn: !ImportValue NewRelicLicenseKeySecret-NewRelic-LicenseKeySecretARN - ``` - - Normalmente, tendrá un archivo llamado `template.yaml` que describe su función y sus recursos. + Para monitorear su función Lambda con New Relic: + + 1. Instalar la [capa Lambda de New Relic](https://layers.newrelic-external.com/). A continuación se muestra un ejemplo de una plantilla simple de CloudFormation para una función Lambda de Node.js: + + ```yaml + AWSTemplateFormatVersion: '2010-09-09' + Transform: AWS::Serverless-2016-10-31 + Description: And example of a simple instrumented Node.js Lambda + + Resources: + NewRelicExample: + Type: AWS::Serverless::Function + Properties: + # In this example, we're using the SAM CLI to package and deploy our lambda. SAM will transform this value during the publish step. + CodeUri: newrelic-example-node/ + # The handler for your function needs to be the one provided by the instrumentation layer, below. + Handler: newrelic-lambda-wrapper.handler + Runtime: nodejs22.x + Environment: + Variables: + # For the instrumentation handler to invoke your real handler, we need this value + NEW_RELIC_LAMBDA_HANDLER: YOUR_PATH_TO_INITIAL_LAMBDA_HANDLER + # Distributed tracing needs your account ID, and your trusted account ID + NEW_RELIC_ACCOUNT_ID: YOUR_ACCOUNT_ID_HERE + # If your New Relic account has a parent account, this value should be that account ID. Otherwise, just + # your account id. + NEW_RELIC_TRUSTED_ACCOUNT_KEY: YOUR_PARENT_ACCOUNT_ID_HERE + NEW_RELIC_APM_LAMBDA_MODE: 'true' + Tags: + # This tag is to enable APM mode. + NR.Apm.Lambda.Mode: true + Layers: + # This layer includes the New Relic Lambda extension, a sidecar process that sends telemetry, + # as well as the New Relic agent for Node.js, and a handler wrapper that makes integration easy. + - !Sub arn:${AWS::Partition}:lambda:${AWS::Region}:451483290750:layer:NewRelicNodeJS16X:103 + Policies: + # This policy allows the lambda to know the value of the New Relic license key. We need this so + # that we can send telemetry back to New Relic + - AWSSecretsManagerGetSecretValuePolicy: + SecretArn: !ImportValue NewRelicLicenseKeySecret-NewRelic-LicenseKeySecretARN + ``` + + Normalmente, tendrá un archivo llamado `template.yaml` que describe su función y sus recursos. + + 2. Configure las [variables de entorno](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) requeridas. + + 3. Despliega tu función Lambda con la configuración actualizada. - + framework sin servidor es una herramienta popular de desarrollo e implementación para aplicaciones sin servidor. Está escrito para AWS en Node.js y actúa principalmente como una abstracción de alto nivel sobre las plantillas de CloudFormation. Funciona bien para funciones de Node, Python, Ruby, Java y .NET. - New Relic ofrece un [complemento framework Serverless](https://github.com/newrelic/serverless-newrelic-lambda-layers) para simplificar la instrumentación de su aplicación framework Serverless. + New Relic proporciona un [complemento de marcoServerless ](https://github.com/newrelic/serverless-newrelic-lambda-layers)para simplificar la instrumentación de su aplicación de marco Serverless. + + **Prerrequisitos:** - Para instalar el complemento, ejecute este comando: + * Una aplicación existente que emplea el marco Serverless. + * [ID de cuenta de New Relic](/docs/accounts/accounts-billing/account-structure/account-id) + * [New Relic Personal clave de API](/docs/apis/intro-apis/new-relic-api-keys) + + **Para instalar y configurar su aplicación Serverless framework con New Relic:** + + 1. Si emplea `npm`, ejecute el siguiente comando: ```bash - npm install --save-dev serverless-newrelic-lambda-layers + npm install --save-dev serverless-newrelic-lambda-layers ``` - O, alternativamente, puede ejecutar este comando: + O, si usa `yarn`, ejecute el siguiente comando: ```bash - yarn add --dev serverless-newrelic-lambda-layers + yarn add --dev serverless-newrelic-lambda-layers ``` - Luego, busque su [New Relic ID](/docs/accounts/install-new-relic/account-setup/account-id) [New Relic de cuenta API](/docs/apis/get-started/intro-apis/types-new-relic-api-keys#personal-api-key) , su clave de personal de + 2. Abra su archivo `serverless.yaml` y agregue la siguiente configuración: - Ahora agregue lo siguiente a su archivo `serverless.yaml` : + 1. Agrega `serverless-newrelic-lambda-layers` a tu lista `plugins`. - ```yaml - plugins: - - serverless-newrelic-lambda-layers - custom: - newRelic: - accountId: your-new-relic-account-id-here - apiKey: your-new-relic-personal-api-key-here - linkedAccount: your-new-relic-integration-account-name-here - ``` + 2. Agregue la siguiente configuración de New Relic en la sección personalizada: + + ```yaml + plugins: + - serverless-newrelic-lambda-layers + custom: + newRelic: + accountId: your-new-relic-account-id-here + apiKey: your-new-relic-personal-api-key-here + linkedAccount: your-new-relic-integration-account-name-here + apm: true + ``` + + 3. Agregue la siguiente etiqueta `NR.Apm.Lambda.Mode: true` en la sección del proveedor: + + ```yaml + provider: + tags: + NR.Apm.Lambda.Mode: true + ``` + + 3. Configure las [variables de entorno](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) requeridas. + + 4. Despliega tu función Lambda con la configuración actualizada. + + + + El kit de desarrollo de nube AWS (AWS CDK) es un framework para definir recursos cloud en código y aprovisionarlos a través de AWS CloudFormation. + + Para emplear New Relic con AWS CDK, siga estos pasos: + + 1. Instalar la [capa Lambda de New Relic](https://layers.newrelic-external.com/). A continuación se muestra un ejemplo de una aplicación CDK básica que implementa un New Relic instrumentado Node.js función Lambda: + + ```ts + import * as cdk from 'aws-cdk-lib'; + import { Construct } from 'constructs'; + import * as lambda from 'aws-cdk-lib/aws-lambda'; + + export class NewRelicExampleCdkStack extends cdk.Stack { + constructor(scope: Construct, id: string, props?: cdk.StackProps) { + super(scope, id, props); + // Add latest New Relic Lambda layer ARN from https://layers.newrelic-external.com + const NewReliclayerArn = 'arn:aws:lambda:us-east-1:451483290750:layer:NewRelicNodeJS22X:38'; + const myFunction = new lambda.Function(this, "NewRelicExampleLambda", { + runtime: lambda.Runtime.NODEJS_20_X, + // Update functions handler to point to the New Relic Lambda wrapper + handler: "newrelic-lambda-wrapper.handler", + code: lambda.Code.fromAsset('lib/lambda-runtime-code'), + layers: [lambda.LayerVersion.fromLayerVersionArn(this, 'NewRelicLayer', NewReliclayerArn)], + environment: { + // Set the NEW_RELIC_LAMBDA_HANDLER environment variable to the path of your initial handler. + NEW_RELIC_LAMBDA_HANDLER: 'index.handler', + NEW_RELIC_APM_LAMBDA_MODE: 'true' + }, + }); + // Add the New Relic APM Lambda Mode tag + cdk.Tags.of(myFunction).add('NR.Apm.Lambda.Mode', 'true'); + } + } + ``` + + 2. Configure las [variables de entorno](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) requeridas. + + 3. Despliega tu función Lambda con la configuración actualizada. - + Terraform es una infraestructura popular de uso general como herramienta de código. Se puede emplear para gestionar recursos de AWS. Ofrecemos [algunos ejemplos](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/terraform) de New Relic instrumentado función Lambda desplegar usando el script Terraform. + + Puede emplear el [proveedor Terraform New Relic ](https://registry.terraform.io/providers/newrelic/newrelic/latest/docs/resources/cloud_aws_integrations)para configurar su integración AWS. Al configurar el proveedor, configure las [variables de entorno](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) requeridas y agregue la etiqueta `NR.Apm.Lambda.Mode: true` a su función Lambda. - + Si bien es más propenso a errores y requiere más mano de obra que los enfoques anteriores, puede modificar manualmente la configuración de una función Lambda para usar New Relic desde la consola AWS Lambda, para Node.js, Python, Ruby y Java. Aquí hay un ejemplo de cómo implementar el monitoreo New Relic Lambda para un tiempo de ejecución Ruby : @@ -157,7 +213,7 @@ Dependiendo de sus necesidades, puede optar por omitir la extensión y solo ver 4. Vaya a **Choose a layer** y seleccione la opción **Specify an ARN** . - 5. Vaya a la [New Relic's list of layers](https://layers.newrelic-external.com/) y use la lista desplegable para seleccionar la región de AWS donde está alojada su función Lambda. Desde allí, ubique el ARN que coincida con la versión y arquitectura de Ruby de su función Lambda. Debería haber dos opciones: X86 y ARM64. Utilice el botón **Copy to clipboard** o copie manualmente la cadena ARN. + 5. Vaya a la [New Relic's list of layers](https://layers.newrelic-external.com/) y use la lista desplegable para seleccionar la región de AWS donde está alojada su función Lambda. Desde allí, ubique el ARN que coincida con la versión y arquitectura de Ruby de su función Lambda. Debería haber dos opciones: X86 y ARM64. Utilice el botón **Copy to clipboard** o copie manualmente la cadena ARN. 6. En la sección **Specify an ARN** del formulario de la consola de AWS, pegue el ARN de la capa New Relic Lambda. @@ -171,21 +227,9 @@ Dependiendo de sus necesidades, puede optar por omitir la extensión y solo ver 11. Cambie a la pestaña de **Configuration** en la página de su función Lambda. - 12. Seleccione la subpestaña **Environment variables** . - - 13. Defina las siguientes variables de entorno: - - * `NEW_RELIC_ACCOUNT_ID`: Establezca su [ID de cuenta](/docs/accounts/install-new-relic/account-setup/account-id) de New Relic . - - * `NEW_RELIC_LAMBDA_HANDLER`: Establezca el valor del controlador original de su función copiado anteriormente. + 12. Seleccione la subpestaña **Environment variables** y, según sus necesidades, defina las [Variables de entorno](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda). - * `NEW_RELIC_LICENSE_KEY`: Configure su clave de licencia de New Relic. - * `NEW_RELIC_LOG_ENDPOINT`: Establezca en [https://log-api.newrelic.com/log/v1](https://log-api.newrelic.com/log/v1). - * `NEW_RELIC_TELEMETRY_ENDPOINT`: Establezca en [https://cloud-collector.newrelic.com/aws/lambda/v1](https://cloud-collector.newrelic.com/aws/lambda/v1). - - 14. Si desea enviar el log de su función Lambda a New Relic, que incluirá todo lo que su función escribe en STDOUT, cerciorar de configurar la variable de entorno `NEW_RELIC_EXTENSION_SEND_FUNCTION_LOGS` en `true`. - - 15. Modifique la función de ejecución para permitir el acceso al secreto de la clave de licencia de New Relic. + 13. Modifique la función de ejecución para permitir el acceso al secreto de la clave de licencia de New Relic. * Busque el ARN del secreto denominado `NEW_RELIC_LICENSE_KEY`. @@ -207,7 +251,11 @@ Dependiendo de sus necesidades, puede optar por omitir la extensión y solo ver La capa New Relic entregará automáticamente el agente Ruby de New Relic y se cargará a través de Ruby `require` antes de la invocación de su función Lambda. Para evitar conflictos, no incluya una copia del agente Ruby en ningún otro lugar. Sentir libre de realizar cualquier llamada API del agente New Relic Ruby que desee dentro de su función para aprovechar la presencia del agente. - Los tiempos de ejecución de Java, Python, Node.js y .Net seguirán el mismo flujo de instrumentación que Ruby, pero con algunos controladores diferentes. A continuación se explica cómo actualizar el controlador de su función para que apunte a la capa recién anexa en la consola para su función: + 14. En su consola de administración AWS, en la pestaña de configuración, agregue la etiqueta `NR.Apm.Lambda.Mode: true` a su función Lambda. + + 15. Despliega tu función Lambda con la configuración actualizada. + + Los tiempos de ejecución de Java, Python, Node.js y .Net seguirán el mismo flujo de instrumentación que Ruby, pero con algunos controladores diferentes. A continuación se explica cómo actualizar el controlador de su función para que apunte a la capa recién anexa en la consola para su función: * Java: @@ -216,39 +264,43 @@ Dependiendo de sus necesidades, puede optar por omitir la extensión y solo ver * Python: `newrelic_lambda_wrapper.handler` (guiones bajos). - * Nodo: `newrelic-lambda-wrapper.handler` (guiones). + * Nodo: + + * CommonJS: `newrelic-lambda-wrapper.handler` (guiones). + * ESM: `/opt/nodejs/node_modules/newrelic-esm-lambda-wrapper/index.handler` (guiones). * Para .Net no es necesario configurar el controlador. - Tenga en cuenta que para Go, debe realizar cambios en el código fuente de su función Lambda para implementarla. Los cambios de configuración no son suficientes. + Tenga en cuenta que para Go, debe realizar cambios en el código fuente de su función Lambda para implementarla. Los cambios de configuración no son suficientes. -## Métodos de envío +## Buscar y utilizar datos [#find-data] - - - Cada capa de agente también contiene una extensión para enviar logs y carga a New Relic, sin pasar por CloudWatch. Esto puede ayudar a reducir la latencia y los costos. Sin embargo, existe el riesgo de afectar el rendimiento y la confiabilidad de su función. +Luego de instrumentar su función Lambda AWS, puede buscar y usar los datos en la interfaz New Relic APM. Los datos están organizados en varias áreas clave, cada una de las cuales proporciona información valiosa sobre el rendimiento y el estado de su función Lambda. - Luego de agregar una capa New Relic Lambda, la extensión está habilitada y tiene el envío log deshabilitado de forma predeterminada. +En la interfaz APM, puede explorar varios aspectos de su función Lambda, incluido [el rastreo distribuido](/docs/distributed-tracing/concepts/introduction-distributed-tracing/), [los mapas de servicios](/docs/new-relic-solutions/new-relic-one/ui-data/service-maps/service-maps/), [las transacciones](/docs/apm/transactions/intro-transactions/transactions-new-relic-apm/) y [el análisis de errores](/docs/errors-inbox/getting-started/), y muchos más. Cada una de estas áreas proporciona información detallada y valiosa sobre el rendimiento, la latencia y la tasa de errores de su función Lambda, lo que le permite identificar y resolver problemas rápidamente. - Si desea ver el log de funciones en New Relic, deberá habilitar el envío de extensión del log de funciones con una variable de entorno. + + La experiencia de Invocación ahora está integrada con APM traza de la transacción. Esto le permite emplear un `AWS RequestId` específico para explorar en profundidad una traza de la transacción de APM para obtener información detallada sobre esa ejecución Lambda en individuo. + - Es importante tener en cuenta que el log de función es solo el log registrado por la función durante su invocación. La extensión no enviará logs de tiempo de ejecución de Lambda como líneas `START`, `END` y `REPORT` . - +Para ver su función Lambda en la interfaz New Relic APM : - - Puede optar por enviar datos solo a CloudWatch o como respaldo. Para obtener más información, consulte nuestra [documentación de respaldo de CloudWatch](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/cloudwatch-fallback). - - +1. Vaya a [https://one.newrelic.com](https://one.newrelic.com) > APM & Services. + +2. Establezca los criterios de búsqueda como `isLambdaFunction = true`. + +3. De la lista mostrada, seleccione su función Lambda para ver los datos. + +## Artículos relacionados [#related-docs] -## ¿Que sigue? [#find-data] + + + Obtenga más información sobre los entornos de ejecución compatibles y los requisitos previos + -* Luego de completar estos pasos, podrá ver reportes de datos en la [UIde monitoreo de Lambda](/docs/lambda-monitoring-ui). -* Si tiene problemas para encontrar sus datos, consulte [Lambda habilitar resolución de problemas](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda#troubleshoot). + + Aprenda a solucionar problemas relacionados con la instalación + + \ No newline at end of file diff --git a/src/i18n/content/es/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda.mdx b/src/i18n/content/es/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda.mdx index ebcf5aec7c5..12696ef260f 100644 --- a/src/i18n/content/es/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda.mdx +++ b/src/i18n/content/es/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda.mdx @@ -7,40 +7,155 @@ translationType: machine La instrumentación de New Relic para AWS Lambda ofrece una visibilidad profunda del funcionamiento interno de sus funciones. Al agregar el agente New Relic a su función, cada invocación es monitoreada por New Relic. Esto le permite rastrear la duración de las invocaciones de funciones, monitorear errores y registrar detalles sobre el evento de origen y las respuestas de su función. -new-relic-lambda-entities-screenshot.png +\* AWS Lambda proporciona un servicio de cálculo altamente escalable y basado en eventos, que le permite crear y ejecutar aplicaciones y servicios backend sin la necesidad de aprovisionar o gestionar servidores. A medida que su arquitectura sin servidor en Lambda crece en sofisticación y asume roles críticos para el negocio, lograr una visibilidad integral de su rendimiento, salud operativa e interacción dentro de su ecosistema de aplicaciones más amplio se vuelve esencial para mantener la confiabilidad y la eficiencia. Su aplicación moderna depende en gran medida de numerosas funciones Lambda AWS que interactúan con varios otros microservicios, bases de datos y API de terceros. En entornos tan complejos, es posible que se enfrente a varios desafíos de observabilidad: \* \*\*Dificultad para identificar las causas raíz:\*\* Cuando ocurren problemas de rendimiento como ralentizaciones intermitentes o fallan transacciones críticas que involucran la función Lambda, identificar la función exacta que falla o la fuente del problema puede ser un rompecabezas complejo. \* \*\*Vistas de monitoreo en aislamiento:\*\* Es posible que se encuentre navegando entre una UI de monitoreo de servidor dedicada y sus vistas tradicionales de monitoreo del rendimiento de aplicaciones (APM), lo que dificulta obtener una imagen única y unificada del rendimiento. \*\*Correlación de datos ineficaz:\*\* Puede resultar complicado correlacionar eficazmente datos de rendimiento y eventos cuando la información reside en sistemas de monitoreo APM y sin servidor separados. \* \*\*Seguimiento incompleto de extremo a extremo:\*\* Es posible que enfrente desafíos para rastrear sin problemas una sola solicitud de extremo a extremo a medida que atraviesa la función Lambda y otros servicios dentro de su entorno distribuido. \*\*Monitoreo limitado para Lambda:\*\* A menudo existe una incapacidad para aplicar todo el poder de diagnóstico y el flujo de trabajo familiar de las herramientas APM directamente a su función Lambda. \*\*Esfuerzo manual para obtener información valiosa:\*\* Con frecuencia se requiere un esfuerzo manual significativo para juntar información dispar de varias fuentes para comprender el contexto completo de un problema que involucra Lambda. Para abordar estos desafíos de observabilidad y brindar una experiencia de monitoreo verdaderamente unificada, New Relic está mejorando la forma en que las funciones Lambda AWS se integran en nuestra plataforma. Esta iniciativa lleva sus funciones sin servidor directamente a la experiencia New Relic APM, tratándolas como ciudadanos de primera clase junto con sus otros servicios instrumentados. Nuestro objetivo es proporcionar telemetría rica y basada en aplicaciones para su función Lambda, haciendo que sea más fácil que nunca comprender su rendimiento en contexto completo. \*/ -## Métodos de envío para telemetría Lambda [#shipping-methods] +## Característica clave [#key-features] -Hay tres métodos principales para enviar telemetry data desde AWS Lambda a New Relic, cada uno con sus propias consideraciones de costo y confiabilidad: +* **Obtenga una vista unificada:** monitoree su función Lambda dentro de la misma interfaz APM que emplea para sus otros servicios. Vea la telemetría sin servidor, incluido el rendimiento métrico, las trazas, los logs (cuando estén configurados) y los errores, todo correlacionado en un solo lugar, lo que elimina la necesidad de cambiar entre diferentes UI. -* **Método rentable**: emplee las capas de New Relic, incluida la extensión Lambda, que evita enviar datos a AWS CloudWatch de forma predeterminada. -* **Método centrado en la confiabilidad**: deshabilite la extensión Lambda de New Relic y use CloudWatch exclusivamente para enviar datos, lo que reduce la sobrecarga de la función Lambda. -* **Método híbrido**: combine la extensión con CloudWatch como alternativa, equilibrando la rentabilidad con la confiabilidad. +* **Aproveche todo el poder de APM:** aplique el conjunto completo de funciones New Relic APM directamente a su función Lambda. Esto incluye rastreo distribuido avanzado, análisis de errores detallado con Bandeja de entrada de errores, mapas de servicios que incorporan su función Lambda, dashboards y más. Para obtener más información, consulte la [documentación de APM](https://docs.newrelic.com/docs/apm/new-relic-apm/getting-started/introduction-apm/). -## Consideración de costos [#costs] +* **Consiga un seguimiento completo de solicitudes de extremo a extremo:** rastree sin problemas requests a medida que fluyen desde sus servicios frontend u otros microservicios, a través de su función Lambda AWS y hacia cualquier componente conectado. Esto proporciona una imagen clara e ininterrumpida de la latencia y dependencia de las solicitudes en toda la arquitectura. Para obtener más información, consulte la [documentación de rastreo distribuido](https://docs.newrelic.com/docs/distributed-tracing/concepts/introduction-distributed-tracing/). -La implementación de monitoreo sin servidor (serverless) para AWS Lambda puede generar cargos adicionales de AWS. La función Lambda `newrelic-log-ingestion`, que informa datos a New Relic, se considera un servicio de terceros y cualquier cargo de AWS asociado es responsabilidad del usuario. +* **Simplifique el análisis de causa raíz:** al consolidar los datos sin servidor con el resto de la telemetría de su aplicación en APM, puede identificar y diagnosticar rápidamente los problemas, ya sea que se originen dentro de una función Lambda o en un servicio ascendente/descendente. -Si emplea nuestra [extensión newrelic-lambda](https://github.com/newrelic/newrelic-lambda-extension) incluida en nuestras [capas New Relic Lambda](https://github.com/newrelic/newrelic-lambda-layers), puede evitar enviar los logs y telemetría a través de CloudWatch y la función [newrelic-log-ingestion](https://github.com/newrelic/aws-log-ingestion). También es posible configurar la función [newrelic-log-ingestion](https://github.com/newrelic/aws-log-ingestion) como un método [de respaldo de CloudWatch](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/cloud-watch-fallback/) para funciones que requieren alta disponibilidad de datos de observabilidad. +* **Comprenda mejor el impacto sin servidor:** vea claramente cómo su función Lambda contribuye a la salud general y al rendimiento de su aplicación y transacciones comerciales clave, brindando información más profunda y valiosa sobre su rol dentro de sus servicios digitales. + +New Relic Lambda Entities in APM + +## ¿Cómo puedes configurar la monitorización AWS Lambda ? [#config] + +Para monitorear su AWS Lambda con New Relic, puede configurar la instrumentación en diferentes entornos, tiempos de ejecución y métodos de implementación. Los siguientes pasos le guiarán a través del proceso de configuración: + + + + ### Compatibilidad y requisitos [#req] + + Cerciorar de que su AWS Lambda cumpla con nuestros [requisitos y compatibilidad](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/compatibility-requirement-lambda-monitoring). + + + + ### (Opcional) Vincula tu cuenta de AWS a New Relic [#link] + + Al vincular cuentas, le otorga licencia a New Relic para crear un inventario de su cuenta AWS y recopilar automáticamente métricas de CloudWatch para su función Lambda. Una vez que vinculó las cuentas, los recursos en su cuenta AWS aparecerán como entidad en el [explorador de entidades](/docs/new-relic-solutions/new-relic-one/core-concepts/new-relic-explorer-view-performance-across-apps-services-hosts/#find). La función Lambda entidad se encontrará en la vista sin servidor de funciones. + + Puede vincular su cuenta de AWS y New Relic mediante uno de los siguientes métodos de integración. + + + + Sondeo de API de AWS Metric Streams (recomendado) + + + + + Para que New Relic monitoree su función Lambda, necesita configurar una integración entre New Relic y AWS. Recomendamos emplear [Metric Streams](/install/aws-cloudwatch) para ayudar a reducir la latencia y evitar la limitación de nuestras requests de sondeo. + + + + Si no está empleando una integración de Streams métrica, puede optar por configurar una integración [API Polling](/docs/infrastructure/amazon-integrations/connect/set-up-aws-api-polling) en su lugar. De forma predeterminada, una integración de sondeo de API con el servicio Lambda habilitado sondeará cada 5 minutos las métricas de CloudWatch. + + Puede emplear [newrelic-lambda-cli](https://github.com/newrelic/newrelic-lambda-cli) para configurar una integración API Polling, pero no una integración de métrica Streams. + + ```sh + newrelic-lambda integrations install --nr-account-id YOUR_NR_ACCOUNT_ID \ + --nr-api-key YOUR_NEW_RELIC_USER_KEY + ``` + + Un paso en el [comando de instalación de integración](https://github.com/newrelic/newrelic-lambda-cli?tab=readme-ov-file#aws-lambda-integration) creará un secreto `NEW_RELIC_LICENSE_KEY` en [AWS Secrets Manager](https://aws.amazon.com/secrets-manager/) para mejorar la seguridad. Esto se puede configurar con un indicador `--disable-license-key-secret` , junto con otras opciones e indicadores. + + + + + + + ### instrumento su función AWS Lambda [#instrument] + + Para instrumentar su función Lambda, necesita un agente y una extensión. Estos componentes están agrupados en la [capa Lambda](https://github.com/newrelic/newrelic-lambda-layers) de New Relic. Si usar capas Lambda no es una opción para usted, puede incorporar manualmente el agente y la extensión a su función. Según los requisitos de su función Lambda, seleccione uno de los siguientes métodos de instrumentación: + + + + Instrumentación en capas Instrumentación basada en SDK Instrumentación en contenedores + + + + + Emplee este método si su función Lambda está empaquetada como un archivo Zip y puede agregar capas. Las capas son un mecanismo de distribución para bibliotecas, tiempos de ejecución personalizados y otras dependencias. Para obtener más información, consulte la documentación [de instrumentación en capas](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own/) . + + + + Emplee este método si su función Lambda no puede emplear capas, garantizando una implementación rápida sin la necesidad de modificar capas. Para obtener más información, consulte la documentación [de instrumentación basada en SDK](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/sdk-based-instrumentation/) . + + + + Emplee este método si su función Lambda se ejecuta dentro de un contenedor. contenedor proporciona un entorno de ejecución consistente y aislado para su aplicación. New Relic proporciona una imagen de Docker prediseñada que incluye la capa Lambda de New Relic, la extensión Lambda de New Relic y el agente de New Relic. Para obtener más información, consulte la documentación [de instrumentación en contenedores](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/containerized-images/). + + + + + + + ### Configurar variables de entorno [#env-variables] + + + * Cuando instrumenta la capa Lambda de New Relic con la CLI de New Relic, sus variables de entorno obligatorias se configuran automáticamente. Sin embargo, es posible que desee cambiar algunas de las configuraciones predeterminadas y configurar su función Lambda con las variables de entorno que coincidan con sus necesidades de monitoreo. + * Si está empleando la extensión Lambda de New Relic, deberá configurar las variables de entorno manualmente. + + + [Las variables de entorno](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) se emplean para configurar el agente New Relic y la extensión Lambda. Es importante configurar estas variables correctamente para garantizar que sus funciones Lambda se monitoreen correctamente. + + + + ### Encuentra tus datos en New Relic [#data] + + Luego de instrumentar su función Lambda AWS, puede buscar y usar los datos en la interfaz New Relic APM. Los datos están organizados en varias áreas clave, cada una de las cuales proporciona información valiosa sobre el rendimiento y el estado de su función Lambda. + + + +## Pruebe nuestras funciones de ejemplo [#example] + +Luego de instrumentar la capa Lambda de New Relic, le recomendamos encarecidamente que pruebe nuestras funciones de ejemplo. Estos ejemplos de trabajo deben emplear como punto de partida para instrumentar su propia función serverless. El uso de estos ejemplos puede ayudarlo a familiarizar con la capa New Relic Lambda, probar el enlace de la cuenta y pueden usar como referencia para su propia instrumentación. Cada ejemplo demuestra cómo agregar licencias, técnicas específicas del tiempo de ejecución para empaquetar su controlador, gestionar la retención log de funciones en CloudWatch y más. + +Si bien hay muchas formas de gestionar y desplegar la función Lambda, AWS CloudFormation es el mecanismo que empleamos para nuestros ejemplos. + +Nuestros ejemplos se publican, junto con la extensión New Relic Lambda, en este [repositorio de GitHub](https://github.com/newrelic/newrelic-lambda-extension). Hay uno para cada tiempo de ejecución de Lambda que admite New Relic: + +* [Node.js](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/sam/node) +* [Python](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/sam/python) +* [Go](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/sam/go) +* [Java](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/sam/java) +* [Ruby](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/sam/ruby) +* [.NET](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/sam/dotnet) + +También puedes aprender a emplear el instrumento rastreo distribuido en una aplicación sin servidor no trivial en nuestro [ejemplo de rastreo distribuido](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/sam/distributedtracing). Ilustra la propagación manual de trazas para SQS y SNS, dos de los servicios más populares que pueden invocar la función Lambda, con funciones de Node, Python, Ruby y Java. - Independientemente del método de envío que se emplee, la carga útil y la experiencia en New Relic siguen siendo las mismas. + Al realizar pruebas manualmente, telemetry data pueden retrasar. Recomendamos esperar siete segundos antes de volver a invocar la función, lo que permitirá que se entregue cualquier telemetría almacenada en el búfer. -Habilitar el monitoreo sin servidor para AWS Lambda puede generar cargos por Amazon Sitio web Services. Nuestra `newrelic-log-ingestion` función Lambda, que nos informa sus datos Lambda, se considera un [Servicio de terceros](/docs/licenses/license-information/acceptable-use-policy/acceptable-use-policy): los cargos AWS resultantes de su uso son su responsabilidad. +## Consideración de costos [#costs] + +La implementación de monitoreo sin servidor para AWS Lambda puede generar cargos adicionales de AWS. La función Lambda `newrelic-log-ingestion`, que informa datos a New Relic, se considera un servicio de terceros y cualquier cargo de AWS asociado es responsabilidad del usuario. Al usar [`newrelic-lambda-extension`](https://github.com/newrelic/newrelic-lambda-extension) incluido en [las capas Lambda New Relic ](https://github.com/newrelic/newrelic-lambda-layers), puede evitar enviar logs y telemetry data a través de CloudWatch, aunque es posible configurar la función `newrelic-log-ingestion` como respaldo de CloudWatch para necesidades de alta disponibilidad. + +Habilitar la supervisión del servidor para AWS Lambda puede resultar en cargos de Amazon Sitio web Services. Nuestra función Lambda `newrelic-log-ingestion`, que nos informa sus datos Lambda, se considera un [servicio de terceros](/docs/licenses/license-information/general-usage-licenses/acceptable-use-policy): los cargos de AWS resultantes de su uso son su responsabilidad. + +Si emplea nuestra [extensión newrelic-lambda](https://github.com/newrelic/newrelic-lambda-extension) incluida en nuestras [capas New Relic Lambda](https://github.com/newrelic/newrelic-lambda-layers), puede evitar enviar los logs y telemetría a través de CloudWatch y la función [newrelic-log-ingestion](https://github.com/newrelic/aws-log-ingestion). También es posible configurar la función [newrelic-log-ingestion](https://github.com/newrelic/aws-log-ingestion) como un método [de respaldo de CloudWatch](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/cloud-watch-fallback/) para funciones que requieren alta disponibilidad de datos de observabilidad. + +## Precios [#pricing] + +Su uso de New Relic APM + Serverless Convergence se factura como una entidad APM de acuerdo con su pedido. Para obtener más detalles sobre los precios, comunicar con nuestro equipo de ventas o consulte su pedido. -## Que sigue +## Artículos relacionados [#related-docs] - - Obtenga más información sobre los entornos de ejecución compatibles y los requisitos previos + + Instrumente su función Lambda con el enfoque en capas de New Relic. - - Comience con la instrumentación y configuración de su función Lambda + + Instrumento tu función Lambda usando SDK. - - Aprenda a usar New Relic para monitorear su función Lambda AWS + + Instrumente su función Lambda con el enfoque contenedorizado de New Relic. \ No newline at end of file diff --git a/src/i18n/content/es/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/sdk-based-instrumentation.mdx b/src/i18n/content/es/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/sdk-based-instrumentation.mdx index 363e377b541..201e283c750 100644 --- a/src/i18n/content/es/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/sdk-based-instrumentation.mdx +++ b/src/i18n/content/es/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/sdk-based-instrumentation.mdx @@ -67,9 +67,11 @@ Seleccione su tiempo de ejecución a continuación y siga las instrucciones de c - 5. Para habilitar [el rastreo distribuido](/docs/apm/distributed-tracing/getting-started/introduction-distributed-tracing) y configurar las variables ambientales, consulte la documentación [de variables ambientales](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) . + 5. Configurar las [variables de entorno](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda). - 6. Invoque Lambda al menos una vez. Esto crea un grupo log de CloudWatch, que debe estar presente para que funcione el siguiente paso. + 6. En su consola de administración AWS, en la pestaña de configuración, agregue la etiqueta `NR.Apm.Lambda.Mode: true` a su función Lambda. + + 7. Invoque Lambda al menos una vez. Esto crea un grupo log de CloudWatch, que debe estar presente para que funcione el siguiente paso. Nuestro contenedor recopila datos sobre la ejecución de Lambda, genera un mensaje JSON y lo registra en el log de CloudWatch. A continuación, [configurará CloudWatch para enviar esos logs a New Relic](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/instrument-your-own/#manual-stream-logs). @@ -130,9 +132,11 @@ Seleccione su tiempo de ejecución a continuación y siga las instrucciones de c 6. En la consola de AWS Lambda, configure el controlador. Para el [ejemplo Java Lambda](https://github.com/newrelic/newrelic-lambda-tracer-java#usage), el controlador sería `com.handler.example.MyLambdaHandler::handleRequest`. Como se supone `handleRequest` , también puedes usar `com.handler.example.MyLambdaHandler`. - 7. Para habilitar [el rastreo distribuido](/docs/apm/distributed-tracing/getting-started/introduction-distributed-tracing) y configurar las variables ambientales, consulte la documentación [de variables ambientales](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) . + 7. Configurar las [variables de entorno](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda). + + 8. En su consola de administración AWS, en la pestaña de configuración, agregue la etiqueta `NR.Apm.Lambda.Mode: true` a su función Lambda. - 8. Invoque Lambda al menos una vez. Esto crea un grupo log de CloudWatch, que debe estar presente para que funcione el siguiente paso. + 9. Invoque Lambda al menos una vez. Esto crea un grupo log de CloudWatch, que debe estar presente para que funcione el siguiente paso. Nuestro contenedor recopila datos sobre la ejecución de Lambda, genera un mensaje JSON y lo registra en el log de CloudWatch. A continuación, [configurará CloudWatch para enviar esos logs a New Relic](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/instrument-your-own/#manual-stream-logs). @@ -211,9 +215,11 @@ Seleccione su tiempo de ejecución a continuación y siga las instrucciones de c 5. Cargue el archivo comprimido en su cuenta de AWS Lambda. - 6. Para habilitar [el rastreo distribuido](/docs/apm/distributed-tracing/getting-started/introduction-distributed-tracing) y configurar las variables ambientales, consulte la documentación [de variables ambientales](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) . + 6. Configurar las [variables de entorno](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda). + + 7. En su consola de administración AWS, en la pestaña de configuración, agregue la etiqueta `NR.Apm.Lambda.Mode: true` a su función Lambda. - 7. Para completar la instrumentación, siga uno de los siguientes pasos para enviar los telemetry data a New Relic: + 8. Para completar la instrumentación, siga uno de los siguientes pasos para enviar los telemetry data a New Relic: * Emplee la New Relic Lambda `Extension layer`. Puede obtener la última capa arn [(NewRelicLambdaExtension)](https://layers.newrelic-external.com/) . Puede emplear AWS CLI para instalar la capa o agregarla manualmente a su Lambda. @@ -269,9 +275,11 @@ Seleccione su tiempo de ejecución a continuación y siga las instrucciones de c 6. Cargue el archivo comprimido en su cuenta de AWS Lambda. - 7. Para habilitar [el rastreo distribuido](/docs/apm/distributed-tracing/getting-started/introduction-distributed-tracing) y configurar las variables ambientales, consulte la documentación [de variables ambientales](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) . + 7. Configurar las [variables de entorno](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda). - 8. Invoque Lambda al menos una vez. Esto crea un grupo log de CloudWatch, que debe estar presente para que funcione el siguiente paso. + 8. En su consola de administración AWS, en la pestaña de configuración, agregue la etiqueta `NR.Apm.Lambda.Mode: true` a su función Lambda. + + 9. Invoque Lambda al menos una vez. Esto crea un grupo log de CloudWatch, que debe estar presente para que funcione el siguiente paso. El decorador de New Relic recopila datos sobre la ejecución de Lambda, genera un mensaje JSON y lo registra en el log de CloudWatch. A continuación, [configure CloudWatch para enviar esos logs a New Relic](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/instrument-your-own/#manual-stream-logs). @@ -282,25 +290,38 @@ Seleccione su tiempo de ejecución a continuación y siga las instrucciones de c Para instrumentar su .NET Lambda: 1. Agregue el [paquete nuget NewRelic.Agente](https://www.nuget.org/packages/NewRelic.Agent) a su proyecto AWS Lambda . Para obtener más información, consulte nuestra [guía de instalación](/docs/apm/agents/net-agent/install-guides/install-net-agent-using-nuget/). - 2. Para habilitar [el rastreo distribuido](/docs/apm/distributed-tracing/getting-started/introduction-distributed-tracing) y configurar las variables ambientales, consulte la documentación [de variables ambientales](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) . - 3. Publique el proyecto en su cuenta de AWS Lambda. - 4. [Configure](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/account-linking/) la extensión New Relic Lambda o la lambda `newrelic-log-ingestion` . - 5. Invoque Lambda al menos una vez para comprobar si hay errores y cerciorar de que los datos sean visibles en la New Relic UI. + 2. Configurar las [variables de entorno](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda). + 3. En su consola de administración AWS, en la pestaña de configuración, agregue la etiqueta `NR.Apm.Lambda.Mode: true` a su función Lambda. + 4. Publique el proyecto en su cuenta de AWS Lambda. + 5. [Configure](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/account-linking/) la extensión New Relic Lambda o la lambda `newrelic-log-ingestion` . + 6. Invoque Lambda al menos una vez para comprobar si hay errores y cerciorar de que los datos sean visibles en la New Relic UI. -## Que sigue +## Buscar y utilizar datos [#find-data] + +Luego de instrumentar su función Lambda AWS, puede buscar y usar los datos en la interfaz New Relic APM. Los datos están organizados en varias áreas clave, cada una de las cuales proporciona información valiosa sobre el rendimiento y el estado de su función Lambda. + +En la interfaz APM, puede explorar varios aspectos de su función Lambda, incluido [el rastreo distribuido](/docs/distributed-tracing/concepts/introduction-distributed-tracing/), [los mapas de servicios](/docs/new-relic-solutions/new-relic-one/ui-data/service-maps/service-maps/), [las transacciones](docs/apm/transactions/intro-transactions/transactions-new-relic-apm//) y [el análisis de errores](docs/errors-inbox/getting-started/), y muchos más. Cada una de estas áreas proporciona información detallada y valiosa sobre el rendimiento, la latencia y la tasa de errores de su función Lambda, lo que le permite identificar y resolver problemas rápidamente. + + + La experiencia de Invocación ahora está integrada con APM traza de la transacción. Esto le permite emplear un `AWS RequestId` específico para explorar en profundidad una traza de la transacción de APM para obtener información detallada sobre esa ejecución Lambda en individuo. + + +Para ver su función Lambda en la interfaz New Relic APM : + +1. Vaya a [https://one.newrelic.com](https://one.newrelic.com) > APM & Services. +2. Establezca los criterios de búsqueda como `isLambdaFunction = true`. +3. De la lista mostrada, seleccione su función Lambda para ver los datos. + +## Artículos relacionados [#related-docs] Obtenga más información sobre los entornos de ejecución compatibles y los requisitos previos - - Aprenda a usar New Relic para monitorear su función Lambda AWS - - - + Aprenda a solucionar problemas relacionados con la instalación \ No newline at end of file diff --git a/src/i18n/content/es/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/update-lambda-monitoring.mdx b/src/i18n/content/es/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/update-lambda-monitoring.mdx index 6162249a868..1d2d76d51b5 100644 --- a/src/i18n/content/es/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/update-lambda-monitoring.mdx +++ b/src/i18n/content/es/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/update-lambda-monitoring.mdx @@ -5,7 +5,7 @@ freshnessValidatedDate: never translationType: machine --- -Después de [habilitar nuestro monitoreo para AWS Lambda](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/enable-new-relic-monitoring-aws-lambda), ocasionalmente debe actualizar nuestra función Lambda que se utiliza para informar datos log de AWS: `newrelic-log-ingestion`. +Luego de [habilitar nuestro monitoreo para AWS Lambda](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda/#link), ocasionalmente debe actualizar nuestra función Lambda que se emplea para informar los datos de logs de AWS: `newrelic-log-ingestion`. Hay dos maneras de hacer esto: @@ -13,7 +13,7 @@ Hay dos maneras de hacer esto: * [Actualización a través del AWS Serverless Application Repository](#update-sar): utilice esto si lo habilitó mediante el [procedimiento manual](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/enable-new-relic-monitoring-aws-lambda#manual-nr-lambda). - Estos procedimientos de actualización se aplican a nuestro [monitoreo serverless para AWS Lambda](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/introduction-new-relic-monitoring-aws-lambda) y no a nuestro [monitoreo de infraestructura para la integración de AWS Lambda](/docs/integrations/amazon-integrations/aws-integrations-list/aws-lambda-monitoring-integration). + Estos procedimientos de actualización se aplican a nuestro [monitoreo sin servidor para AWS Lambda](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda), y no a nuestro [monitoreo de infraestructura para la integración de AWS Lambda](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-lambda-monitoring-integration). ## Actualice nuestra integración Lambda a través de CLI [#update-cli] @@ -60,6 +60,7 @@ Esta sección describe cómo actualizar la capa de su función si la instaló co --function installed \ --nr-account-id NR_ACCOUNT_ID \ --upgrade + --apm ``` ## Actualizar una instalación manual del repositorio de aplicaciones Serverless [#update-sar] diff --git a/src/i18n/content/es/docs/serverless-function-monitoring/aws-lambda-monitoring/troubleshooting/troubleshoot-enabling-serverless-monitoring-aws-lambda.mdx b/src/i18n/content/es/docs/serverless-function-monitoring/aws-lambda-monitoring/troubleshooting/troubleshoot-enabling-serverless-monitoring-aws-lambda.mdx index 810dba3f4b3..94621279b3b 100644 --- a/src/i18n/content/es/docs/serverless-function-monitoring/aws-lambda-monitoring/troubleshooting/troubleshoot-enabling-serverless-monitoring-aws-lambda.mdx +++ b/src/i18n/content/es/docs/serverless-function-monitoring/aws-lambda-monitoring/troubleshooting/troubleshoot-enabling-serverless-monitoring-aws-lambda.mdx @@ -1,5 +1,5 @@ --- -title: Solucionar problemas al habilitar el monitoreo serverless de AWS Lambda +title: Resolución de problemas de monitoreo Lambda type: troubleshooting tags: - Serverless function monitoring @@ -12,22 +12,22 @@ translationType: machine ## Problema -Está intentando habilitar [el monitoreo serverless para AWS Lambda](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/introduction-new-relic-monitoring-aws-lambda) y tiene un problema o error. +Está intentando habilitar [la supervisión sin servidor para AWS Lambda](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda) y tiene un problema o error. ## Solución -Hay dos problemas comunes relacionados con no completar todos los [procedimientos de habilitación](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/enable-new-relic-monitoring-aws-lambda): +Existen dos problemas comunes relacionados con no completar todos los [procedimientos de habilitación](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda/#link): -* No veo datos en la página UI **CloudWatch metrics**. Esto significa que el [paso de integración de AWS](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/enable-new-relic-monitoring-aws-lambda#connect-aws) no se completó. -* No veo datos en **Troubleshooting** páginas UI de categoría. Si no ve datos en las pestañas UI **Distributed tracing**, **Errors** y **Invocations**, esto significa que el [paso de instrumentación del agente APM](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/enable-new-relic-monitoring-aws-lambda#instrument-lambda) no se completó. +* No se ven datos en la página UI **Lambda metrics**. Esto significa que el [paso de integración de AWS](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda/#link) no se completó. +* No se ven datos en las páginas UI de la categoría **Troubleshooting**. Si no ve datos en las pestañas UI **Distributed tracing**, **Errors** y **Invocations**, esto significa que el [paso de instrumentación del agente deAPM ](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda/#instrument)no se completó. Además de estos problemas de habilitación básicos, existen algunos problemas adicionales que pueden causar un problema: -* Error de CloudWatch "Error HTTP 401: no autorizado". Esto se debe a una clave API incorrecta. El argumento `--nr-api-key`en el [paso de habilitación de Configurar AWS](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/enable-new-relic-monitoring-aws-lambda#connect-aws) toma su . +* Error de CloudWatch "Error HTTP 401: no autorizado". Esto se debe a una clave de API incorrecta. El argumento `--nr-api-key`en el [paso de habilitación de Configurar AWS](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda/#link) toma su . * Faltan métricas personalizadas. El monitoreo lambda no es compatible con nuestra [métrica personalizada](/docs/agents/manage-apm-agents/agent-data/collect-custom-metrics). Utilice [un atributo personalizado](/docs/agents/manage-apm-agents/agent-data/collect-custom-attributes) para agregar metadatos. -* Faltan invocaciones. Para ver los detalles del desglose de la invocación, se debe habilitar rastreo distribuido como parte del [paso de instrumentación de Lambda](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/enable-new-relic-monitoring-aws-lambda#instrument-lambda). Se requiere rastreo distribuido para que los detalles del tramo se puedan mostrar en el panel de detalles de la invocación. +* Falta la pestaña de invocaciones. Con APM + Serverless Convergence, cada invocación Lambda corresponde a la traza de la transacción en APM. Para ver los detalles del desglose de la invocación, consulte la [traza de la transacción](/docs/apm/apm-ui-pages/monitoring/transactions-page-find-specific-performance-problems). * Ha completado correctamente los pasos de instalación, integración e instrumentación y su función es enviar el log a CloudWatch, pero no ve la traza para una dependencia específica (o ninguna traza) en la UI. Esto puede resultar del orden de fusión de capas (si está utilizando nuestras capas Lambda) o del orden de importación (si está instrumentado manualmente): diff --git a/src/i18n/content/es/docs/serverless-function-monitoring/aws-lambda-monitoring/troubleshooting/troubleshoot-no-data-appears.mdx b/src/i18n/content/es/docs/serverless-function-monitoring/aws-lambda-monitoring/troubleshooting/troubleshoot-no-data-appears.mdx index 290dda38921..221554d8379 100644 --- a/src/i18n/content/es/docs/serverless-function-monitoring/aws-lambda-monitoring/troubleshooting/troubleshoot-no-data-appears.mdx +++ b/src/i18n/content/es/docs/serverless-function-monitoring/aws-lambda-monitoring/troubleshooting/troubleshoot-no-data-appears.mdx @@ -10,12 +10,22 @@ freshnessValidatedDate: never translationType: machine --- -## Problema +## Problema [#problem] Luego de generar tráfico para su AWS función Lambda y esperar cinco minutos, ninguno de los datos de su función aparece en la New Relic UI. No hay ningún error en el registro ni `NRIntegrationErrors` ni `NRIntegrationWarnings` en la New Relic UI. -## Solución +## Solución [#solution] + +### Verifique la clave de licencia y el ID de la cuenta [#check-license] La razón más común por la que no aparecen datos ni errores es que la [clave de licencia y el ID de cuenta](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/account-linking/) son de cuentas diferentes. En caso de discrepancia, la [extensiónNew Relic Lambda](https://github.com/newrelic/newrelic-lambda-extension) o [lambda que procesa el registro de vigilancia en la nube](/docs/infrastructure/amazon-integrations/connect/aws-metric-stream/) informa los datos correctamente, pero los elimina silenciosamente ya que el ID de la cuenta no coincide. Esto no genera errores ni advertencias. Para resolver este problema, cerciorar de que la clave de licencia y el ID de cuenta sean de la misma cuenta. Se recomienda emplear la [CLINew Relic Lambda](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/account-linking/#rec) para habilitar el monitoreo del servidor para minimizar este tipo de problemas. Puede actualizar la clave de licencia en AWS Secrets Manager. Para el ID de cuenta y la configuración que no emplean AWS Secrets Manager, puede actualizar las [variables de entorno](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/account-linking/#env-var) con la clave de licencia o el ID de cuenta correctos para corregir el problema. + +### Comprobar variables de entorno [#check-env-vars] + +Cerciorar de que las [variables de entorno](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) necesarias estén configuradas correctamente en su función Lambda AWS. Esto incluye `NEW_RELIC_APM_LAMBDA_MODE`, `NEW_RELIC_ACCOUNT_ID`, `NEW_RELIC_LICENSE_KEY` y cualquier otra variable relevante. Si estas variables no están configuradas o son incorrectas, es posible que no se envíen datos a New Relic. Para obtener más información, consulte [Variables de entorno](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda). + +### Verifique la etiqueta en la consola de administración AWS [#check-tags] + +Cerciorar de agregar la etiqueta `NR.Apm.Lambda.Mode: true` a su función Lambda desde la Consola de administración de AWS. Esta etiqueta es esencial para permitir el monitoreo y garantizar que los datos se envíen a New Relic. \ No newline at end of file diff --git a/src/i18n/content/fr/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx b/src/i18n/content/fr/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx index e34349f3f19..d52475f87eb 100644 --- a/src/i18n/content/fr/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx +++ b/src/i18n/content/fr/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx @@ -36,7 +36,7 @@ Vous souhaitez tester notre agent .NET ? [Créez un compte New Relic](https://ne - The .NET agent is compatible with .NET Core version 3.1, and .NET 5.0, 6.0, 7.0, 8.0, 9.0, and 10.0. + L'agent .NET est compatible avec .NET Core version 3.1 et .NET 5.0, 6.0, 7.0, 8.0, 9.0 et 10.0. L'agent n'est entièrement pris en charge que lorsque l'application instrumentée cible [les runtimes .NET actuellement pris en charge par Microsoft](https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core). Il est probable que l'agent fonctionne avec les runtimes EOL répertoriés ci-dessous, mais nous ne testons pas les nouvelles versions de l'agent avec les runtimes EOL. @@ -271,7 +271,7 @@ Vous souhaitez tester notre agent .NET ? [Créez un compte New Relic](https://ne - The .NET agent is compatible with applications targeting .NET Core 3.1, and .NET 5.0, 6.0, 7.0, 8.0, 9.0, and 10.0. You can find the target framework in your `.csproj` file. Agent compatibility varies across different versions of .NET Core. + L'agent .NET est compatible avec les applications ciblant .NET Core 3.1 et .NET 5.0, 6.0, 7.0, 8.0, 9.0 et 10.0. Vous pouvez trouver le framework cible dans votre fichier `.csproj`. la compatibilité d'agent varie selon les différentes versions de .NET Core. Compatible: @@ -319,8 +319,8 @@ Vous souhaitez tester notre agent .NET ? [Créez un compte New Relic](https://ne L'agent .NET instrumente automatiquement ces frameworks application : - * ASP.NET Core MVC 2.0, 2.1, 2.2, 3.0, 3.1, 5.0, 6.0, 7.0, 8.0, 9.0, and 10.0 (includes Web API) - * ASP.NET Core Razor Pages 6.0, 7.0, 8.0, 9.0, and 10.0 (starting with .NET agent version 10.19.0) + * ASP.NET Core MVC 2.0, 2.1, 2.2, 3.0, 3.1, 5.0, 6.0, 7.0, 8.0, 9.0 et 10.0 (y compris l'API Web) + * ASP.NET Core Razor Pages 6.0, 7.0, 8.0, 9.0 et 10.0 (à partir de la version 10.19.0 de l'agent .NET) @@ -357,7 +357,7 @@ Vous souhaitez tester notre agent .NET ? [Créez un compte New Relic](https://ne L'agent .NET `v9.2.0` ou supérieur instrumente automatiquement la bibliothèque [Microsoft Azure.Cosmos](https://www.nuget.org/packages/Microsoft.Azure.Cosmos). * Version minimale prise en charge : 3.17.0 - * Latest verified compatible version: 3.56.0 + * Dernière version compatible vérifiée : 3.56.0 * Les versions 3.35.0 et supérieures sont prises en charge à partir de l'agent .NET v10.32.0 @@ -434,7 +434,7 @@ Vous souhaitez tester notre agent .NET ? [Créez un compte New Relic](https://ne Utiliser [Npgsql](https://www.nuget.org/packages/Npgsql/) * Version minimale prise en charge : 4.0.0 - * Latest verified compatible version: 7.0.7 + * Dernière version compatible vérifiée : 7.0.7 Les versions antérieures de Npgsql peuvent également être instrumentées, mais des métriques en double et/ou manquantes sont possibles. @@ -452,7 +452,7 @@ Vous souhaitez tester notre agent .NET ? [Créez un compte New Relic](https://ne Version minimale prise en charge : 2.3.0 - Latest verified compatible version: 3.5.2 + Dernière version compatible vérifiée : 3.5.2 Versions 3.0.0 et les versions supérieures sont prises en charge à partir de l'agent .NET v10.40.0. @@ -570,7 +570,7 @@ Vous souhaitez tester notre agent .NET ? [Créez un compte New Relic](https://ne * Version minimale prise en charge : 3.5.0 - * Latest verified compatible version: 4.0.10.1 + * Dernière version compatible vérifiée : 4.0.10.1 * Version minimale de l'agent requise : 10.33.0 @@ -907,7 +907,7 @@ Vous souhaitez tester notre agent .NET ? [Créez un compte New Relic](https://ne * Version minimale prise en charge : 3.5.2 - * Latest verified compatible version: 7.1.2 + * Dernière version compatible vérifiée : 7.1.2 @@ -921,7 +921,7 @@ Vous souhaitez tester notre agent .NET ? [Créez un compte New Relic](https://ne * Version minimale prise en charge : 7.1.0 - * Latest verified compatible version: 8.5.7 + * Dernière version compatible vérifiée : 8.5.7 @@ -949,7 +949,7 @@ Vous souhaitez tester notre agent .NET ? [Créez un compte New Relic](https://ne * Version minimale prise en charge : 3.7.0 - * Latest verified compatible version: 4.0.7.6 + * Dernière version compatible vérifiée : 4.0.7.6 @@ -963,7 +963,7 @@ Vous souhaitez tester notre agent .NET ? [Créez un compte New Relic](https://ne * Version minimale prise en charge : 3.7.0 - * Latest verified compatible version: 4.0.3.5 + * Dernière version compatible vérifiée : 4.0.3.5 @@ -1343,7 +1343,7 @@ Vous souhaitez tester notre agent .NET ? [Créez un compte New Relic](https://ne L'agent .NET `v9.2.0` ou supérieur instrumente automatiquement la bibliothèque [Microsoft Azure.Cosmos](https://www.nuget.org/packages/Microsoft.Azure.Cosmos). * Version minimale prise en charge : 3.17.0 - * Latest verified compatible version: 3.56.0 + * Dernière version compatible vérifiée : 3.56.0 * Les versions 3.35.0 et supérieures sont prises en charge à partir de l'agent .NET v10.32.0 @@ -1461,7 +1461,7 @@ Vous souhaitez tester notre agent .NET ? [Créez un compte New Relic](https://ne Version minimale prise en charge : 2.3.0 - Latest verified compatible version: 3.5.2 + Dernière version compatible vérifiée : 3.5.2 Versions 3.0.0 et les versions supérieures sont prises en charge à partir de l'agent .NET v10.40.0. @@ -1531,7 +1531,7 @@ Vous souhaitez tester notre agent .NET ? [Créez un compte New Relic](https://ne Utiliser [Npgsql](https://www.nuget.org/packages/Npgsql/) * Version minimale prise en charge : 4.0.0 - * Latest verified compatible version: 7.0.7 + * Dernière version compatible vérifiée : 7.0.7 Les versions antérieures de Npgsql peuvent également être instrumentées, mais des métriques en double et/ou manquantes sont possibles. @@ -1629,7 +1629,7 @@ Vous souhaitez tester notre agent .NET ? [Créez un compte New Relic](https://ne * Version minimale prise en charge : 3.5.0 - * Latest verified compatible version: 4.0.10.1 + * Dernière version compatible vérifiée : 4.0.10.1 * Version minimale de l'agent requise : 10.33.0 @@ -1710,7 +1710,7 @@ Vous souhaitez tester notre agent .NET ? [Créez un compte New Relic](https://ne Version minimale prise en charge : 105.2.3 - Latest verified compatible version: 113.0.0 + Dernière version compatible vérifiée : 113.0.0 Versions incompatibles connues : 106.8.0, 106.9.0, 106.10.0, 106.10.1 @@ -2012,7 +2012,7 @@ Vous souhaitez tester notre agent .NET ? [Créez un compte New Relic](https://ne * Version minimale prise en charge : 3.5.2 - * Latest verified compatible version: 6.8.1 + * Dernière version compatible vérifiée : 6.8.1 @@ -2026,7 +2026,7 @@ Vous souhaitez tester notre agent .NET ? [Créez un compte New Relic](https://ne * Version minimale prise en charge : 7.1.0 - * Latest verified compatible version: 8.5.7 + * Dernière version compatible vérifiée : 8.5.7 @@ -2054,7 +2054,7 @@ Vous souhaitez tester notre agent .NET ? [Créez un compte New Relic](https://ne * Version minimale prise en charge : 3.7.0 - * Latest verified compatible version: 4.0.7.6 + * Dernière version compatible vérifiée : 4.0.7.6 @@ -2068,7 +2068,7 @@ Vous souhaitez tester notre agent .NET ? [Créez un compte New Relic](https://ne * Version minimale prise en charge : 3.7.0 - * Latest verified compatible version: 4.0.3.5 + * Dernière version compatible vérifiée : 4.0.3.5 diff --git a/src/i18n/content/fr/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx b/src/i18n/content/fr/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx index 4894fd8b0f2..00c526c9a22 100644 --- a/src/i18n/content/fr/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx +++ b/src/i18n/content/fr/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx @@ -268,32 +268,32 @@ Après installation, l' agent s'instrumente automatiquement avec notre | nom du paquet | Version minimale prise en charge | Dernière version publiée | Introduit en\* | | --------------------------------- | -------------------------------- | ------------------------ | -------------------------------------- | | `@apollo/gateway` | 2.3.0 | 2.12.1 | `@newrelic/apollo-server-plugin@1.0.0` | -| `@apollo/server` | 4.0.0 | 5.1.0 | `@newrelic/apollo-server-plugin@2.1.0` | -| `@aws-sdk/client-bedrock-runtime` | 3.474.0 | 3.934.0 | 11.13.0 | -| `@aws-sdk/client-dynamodb` | 3.0.0 | 3.934.0 | 8.7.1 | -| `@aws-sdk/client-sns` | 3.0.0 | 3.934.0 | 8.7.1 | -| `@aws-sdk/client-sqs` | 3.0.0 | 3.934.0 | 8.7.1 | -| `@aws-sdk/lib-dynamodb` | 3.377.0 | 3.934.0 | 8.7.1 | +| `@apollo/server` | 4.0.0 | 5.2.0 | `@newrelic/apollo-server-plugin@2.1.0` | +| `@aws-sdk/client-bedrock-runtime` | 3.474.0 | 3.943.0 | 11.13.0 | +| `@aws-sdk/client-dynamodb` | 3.0.0 | 3.943.0 | 8.7.1 | +| `@aws-sdk/client-sns` | 3.0.0 | 3.943.0 | 8.7.1 | +| `@aws-sdk/client-sqs` | 3.0.0 | 3.943.0 | 8.7.1 | +| `@aws-sdk/lib-dynamodb` | 3.377.0 | 3.943.0 | 8.7.1 | | `@aws-sdk/smithy-client` | 3.47.0 | 3.374.0 | 8.7.1 | -| `@azure/functions` | 4.7.0 | 4.9.0 | 12.18.0 | +| `@azure/functions` | 4.7.0 | 4.10.0 | 12.18.0 | | `@elastic/elasticsearch` | 7.16.0 | 9.2.0 | 11.9.0 | | `@google/genai` | 1.1.0 | 1.30.0 | 12.21.0 | -| `@grpc/grpc-js` | 1.4.0 | 1.14.1 | 8.17.0 | +| `@grpc/grpc-js` | 1.4.0 | 1.14.2 | 8.17.0 | | `@hapi/hapi` | 20.1.2 | 21.4.4 | 9.0.0 | -| `@koa/router` | 12.0.1 | 14.0.0 | 3.2.0 | -| `@langchain/core` | 0.1.17 | 1.0.6 | 11.13.0 | -| `@modelcontextprotocol/sdk` | 1.13.0 | 1.22.0 | 13.2.0 | -| `@nestjs/cli` | 9.0.0 | 11.0.12 | 10.1.0 | +| `@koa/router` | 12.0.1 | 15.0.0 | 3.2.0 | +| `@langchain/core` | 0.1.17 | 1.1.1 | 11.13.0 | +| `@modelcontextprotocol/sdk` | 1.13.0 | 1.24.1 | 13.2.0 | +| `@nestjs/cli` | 9.0.0 | 11.0.14 | 10.1.0 | | `@opensearch-project/opensearch` | 2.1.0 | 3.5.1 | 12.10.0 | -| `@prisma/client` | 5.0.0 | 7.0.0 | 11.0.0 | -| `@smithy/smithy-client` | 2.0.0 | 4.9.7 | 11.0.0 | +| `@prisma/client` | 5.0.0 | 7.0.1 | 11.0.0 | +| `@smithy/smithy-client` | 2.0.0 | 4.9.9 | 11.0.0 | | `amqplib` | 0.5.0 | 0.10.9 | 2.0.0 | | `aws-sdk` | 2.2.48 | 2.1692.0 | 6.2.0 | | `bluebird` | 2.0.0 | 3.7.2 | 1.27.0 | | `bunyan` | 1.8.12 | 1.8.15 | 9.3.0 | | `cassandra-driver` | 3.4.0 | 4.8.0 | 1.7.1 | | `connect` | 3.0.0 | 3.7.0 | 2.6.0 | -| `express` | 4.15.0 | 5.1.0 | 2.6.0 | +| `express` | 4.15.0 | 5.2.1 | 2.6.0 | | `fastify` | 3.0.0 | 5.6.2 | 8.5.0 | | `generic-pool` | 3.0.0 | 3.9.0 | 0.9.0 | | `ioredis` | 4.0.0 | 5.8.2 | 1.26.2 | @@ -305,13 +305,13 @@ Après installation, l' agent s'instrumente automatiquement avec notre | `mongodb` | 4.1.4 | 7.0.0 | 1.32.0 | | `mysql` | 2.16.0 | 2.18.1 | 1.32.0 | | `mysql2` | 2.0.0 | 3.15.3 | 1.32.0 | -| `next` | 13.4.19 | 16.0.3 | 12.0.0 | +| `next` | 13.4.19 | 16.0.6 | 12.0.0 | | `openai` | 4.0.0 | 6.9.1 | 11.13.0 | | `pg` | 8.2.0 | 8.16.3 | 9.0.0 | | `pg-native` | 3.0.0 | 3.5.2 | 9.0.0 | | `pino` | 8.0.0 | 10.1.0 | 8.11.0 | | `q` | 1.3.0 | 1.5.1 | 1.26.2 | -| `redis` | 3.1.0 | 5.9.0 | 1.31.0 | +| `redis` | 3.1.0 | 5.10.0 | 1.31.0 | | `restify` | 11.0.0 | 11.1.0 | 2.6.0 | | `superagent` | 3.0.0 | 10.2.3 | 4.9.0 | | `undici` | 5.0.0 | 7.16.0 | 11.1.0 | diff --git a/src/i18n/content/fr/docs/query-your-data/explore-query-data/dashboards/share-charts-dashboards-externally.mdx b/src/i18n/content/fr/docs/query-your-data/explore-query-data/dashboards/share-charts-dashboards-externally.mdx index 304e6b3526a..54f57cddd96 100644 --- a/src/i18n/content/fr/docs/query-your-data/explore-query-data/dashboards/share-charts-dashboards-externally.mdx +++ b/src/i18n/content/fr/docs/query-your-data/explore-query-data/dashboards/share-charts-dashboards-externally.mdx @@ -135,16 +135,6 @@ Cette fonctionnalité comprend plusieurs niveaux et conditions de sécurité afi * **Accès par session**: Après avoir accédé au dashboard, la session reste active pendant 120 heures. S’ils tentent d’accéder au dashboard après ce délai, ou si la session du navigateur expire, le mot de passe leur est demandé. En cas de réinitialisation du mot de passe, la session expire dès que le widget est actualisé. L'utilisateur externe doit saisir le nouveau mot de passe. * **Vérification reCAPTCHA**: Si plusieurs tentatives d’accès au dashboard ont échoué, une vérification reCAPTCHA est nécessaire avant de pouvoir saisir à nouveau le mot de passe. - - ### Tarifs [#public-dashboard-pricing] - - Lorsqu'on partage des URL dashboard en direct, il est important de comprendre les coûts associés et de savoir comment les gérer efficacement. **Public Dashboards** est une fonctionnalité de produit Advanced Compute proposée en tant que [module complémentaire](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/add-on-billing) ou dans le cadre du modèle de tarification de calcul. [Les unités de calcul avancées (CCU)](/docs/licenses/license-information/product-definitions/new-relic-one-pricing-definitions/#compute-capacity-unit) sont consommées lorsque des requêtes sont exécutées à partir des visualisations dashboard, ce qui se produit dans les cas suivants : - - * Au chargement de la page - * On sélecteur d'intervalle de temps change - * À propos des déclencheurs de taux de rafraîchissement - - Vous pouvez suivre vos coûts d'utilisation depuis **[New Relic Administration](https://one.newrelic.com/admin-portal) > Consumption Management > Advanced capabilities**. Pour optimiser vos coûts, reportez-vous à la section [sur les bonnes pratiques de gestion des prix](#pricing-management) . @@ -256,6 +246,16 @@ Cette fonctionnalité comprend plusieurs niveaux et conditions de sécurité afi + ### Tarifs [#public-dashboard-pricing] + + Lorsqu'on partage des URL dashboard en direct, il est important de comprendre les coûts associés et de savoir comment les gérer efficacement. **Public Dashboards** est une fonctionnalité de produit Advanced Compute proposée en tant que [module complémentaire](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/add-on-billing) ou dans le cadre du modèle de tarification de calcul. [Les unités de calcul avancées (CCU)](/docs/licenses/license-information/product-definitions/new-relic-one-pricing-definitions/#compute-capacity-unit) sont consommées lorsque des requêtes sont exécutées à partir des visualisations dashboard, ce qui se produit dans les cas suivants : + + * Au chargement de la page + * On sélecteur d'intervalle de temps change + * À propos des déclencheurs de taux de rafraîchissement + + Vous pouvez suivre vos coûts d'utilisation depuis **[New Relic Administration](https://one.newrelic.com/admin-portal) > Consumption Management > Advanced capabilities**. Pour optimiser vos coûts, reportez-vous à la section [sur les bonnes pratiques de gestion des prix](#pricing-management) . + ### Meilleures pratiques [#best-practices] Pour gérer efficacement la tarification et la sécurité des mots de passe liées dashboard public, suivez ces bonnes pratiques : diff --git a/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-11-28-2025.mdx b/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-11-28-2025.mdx new file mode 100644 index 00000000000..ed99d286a5d --- /dev/null +++ b/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-11-28-2025.mdx @@ -0,0 +1,72 @@ +--- +subject: Docs +releaseDate: '2025-11-28' +version: 'November 24 - November 28, 2025' +translationType: machine +--- + +### Nouveaux documents + +* Ajout d'une [prise en charge de l'agent PHP pour Laravel](/docs/apm/agents/php-agent/frameworks-libraries/laravel) afin de fournir des instructions complètes pour Laravel transaction web, Laravel Queue Workers et Laravel Horizon Workers. +* Ajout [d'un guide de dépannage en cas de problème de mémoire insuffisante avec PHPUnit](/docs/apm/agents/php-agent/troubleshooting/phpunit-incompatibility) pour les problèmes de compatibilité de PHPUnit 11+ avec l'agent PHP New Relic. + +### Changements majeurs + +* [Concepts de gestion des utilisateurs](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts) mis à jour et documentation RBAC associée avec une nouvelle expérience de création d'autorisations et de rôles introduisant trois types de rôles (rôles basés sur l'organisation, rôles basés sur le compte et rôles basés sur l'entité). Consolider sous l'onglet **Roles**. +* Mise à jour [des canaux d'alerte](/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-channels) avec les méthodes et exemples d'intégration de l'API Microsoft Teams. +* [Destinations d'alerte](/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-destinations) mises à jour avec prise en charge de l'intégration à Microsoft Teams. + +### Modifications mineures + +* Mise à jour [des tarifs et de la facturation de New Relic](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing) afin de clarifier les modèles de tarification et les fonctionnalités offertes. +* [Configuration de l'agent .NET](/docs/apm/agents/net-agent/configuration/net-agent-configuration) mise à jour avec des options de configuration d'instrumentation du navigateur. +* Mise à jour [monitoring des navigateurs avec l'agent .NET](/docs/apm/agents/net-agent/other-features/browser-monitoring-net-agent) et instructions configuration simplifiées. +* Mise à jour [des exigences de compatibilité PHP de d'agent](/docs/apm/agents/php-agent/getting-started/php-agent-compatibility-requirements) avec la prise en charge Laravel Horizon et suppression de la prise en charge Windows 32 bits. +* [Traitement du collecteur OpenTelemetry](/docs/opentelemetry/get-started/collector-processing/opentelemetry-collector-processing-intro) mis à jour avec des instructions de configuration actualisées. +* [configurationréseau](/docs/new-relic-solutions/get-started/networks) mise à jour avec point de terminaison double pile fixe permanent. +* Mise à jour [de la conformité TISAX](/docs/security/security-privacy/compliance/certificates-standards-regulations/tisax) avec des informations de conformité actualisées. + +### Notes de version + +* Annoncée le 30 juin 2026 comme date de fin de vie des [graphiques intégrés APM détaillés legacy.](/eol/2025/11/pre-insights/) + +* Restez au courant de nos dernières sorties : + + * [Intégration Kubernetes v3.50.2](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-50-2): + + * Intégration mise à jour incluse dans newrelic-infrastructure-3.55.2 et nri-bundle-6.0.26. + + * [Logs 251120](/docs/release-notes/logs-release-notes/logs-25-11-20): + + * Correction de la vulnérabilité CVE-2025-53643 dans la fonction lambda aws-log-ingestion. + * Mise à jour de la bibliothèque aiohttp vers la version 3.13.2 et la version poésie pour la version 1.8.3. + + * [Agent React Native v1.5.12](/docs/release-notes/mobile-release-notes/react-native-release-notes/react-native-agent-1512): + + * Agent Android natif mis à jour vers la version 7.6.13. + * Agent iOS natif mis à jour vers la version 7.6.0. + + * [Agent Capacitor v1.5.12](/docs/release-notes/mobile-release-notes/capacitor-release-notes/capacitor-agent-1512): + + * Agent Android natif mis à jour vers la version 7.6.13. + * Agent iOS natif mis à jour vers la version 7.6.0. + + * [Agent Flutter v1.1.19](/docs/release-notes/mobile-release-notes/flutter-release-notes/flutter-agent-1119): + + * Agent Android natif mis à jour vers la version 7.6.13. + * Agent iOS natif mis à jour vers la version 7.6.0. + + * [Agent Unity v1.4.11](/docs/release-notes/mobile-release-notes/unity-release-notes/unity-agent-1411): + + * Agent Android natif mis à jour vers la version 7.6.13. + * Agent iOS natif mis à jour vers la version 7.6.0. + + * [Agent Cordova v7.0.11](/docs/release-notes/mobile-release-notes/cordova-release-notes/cordova-agent-711): + + * Agent Android natif mis à jour vers la version 7.6.13. + * Agent iOS natif mis à jour vers la version 7.6.0. + + * [Agent .NET MAUI v1.1.14](/docs/release-notes/mobile-release-notes/net-maui-release-notes/net-maui-agent-1114): + + * Agent Android natif mis à jour vers la version 7.6.13. + * Agent iOS natif mis à jour vers la version 7.6.0. \ No newline at end of file diff --git a/src/i18n/content/fr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/compatibility-requirement-lambda-monitoring.mdx b/src/i18n/content/fr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/compatibility-requirement-lambda-monitoring.mdx index a471cc71e26..92505ef8d10 100644 --- a/src/i18n/content/fr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/compatibility-requirement-lambda-monitoring.mdx +++ b/src/i18n/content/fr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/compatibility-requirement-lambda-monitoring.mdx @@ -11,13 +11,17 @@ Avant d'[installer le monitoring Lambda](/docs/serverless-function-monitori Avant d'activer monitoring sans serveur à l'aide de notre couche Lambda , vous aurez besoin de : -1. Un compte New Relic avec un [rôle d'administrateur](/docs/accounts/original-accounts-billing/original-users-roles/users-roles-original-user-model/#roles) ou avec le [rôle complémentaire](/docs/accounts/original-accounts-billing/original-users-roles/users-roles-original-user-model#add-on) de **gestionnaire d'infrastructure**. +* Un compte New Relic avec un [rôle d'administrateur](/docs/accounts/accounts-billing/new-relic-one-user-management/introduction-managing-users) ou le [rôle complémentaire](/docs/accounts/original-accounts-billing/original-users-roles/users-roles-original-user-model#add-on) de **Infrastructure manager**. -2. Un . +* Un . -3. Un compte AWS avec des autorisations pour créer des ressources IAM, des secrets gérés et des Lambdas. Vous avez également besoin d’autorisations pour créer une pile CloudFormation et des buckets S3. +* Un compte AWS avec des autorisations pour créer des ressources IAM, des secrets gérés et des Lambdas. Vous avez également besoin d’autorisations pour créer une pile CloudFormation et des buckets S3. -## Exécutions prises en charge + + New Relic recommande d'intégrer votre compte AWS à New Relic en utilisant l' [intégration AWS](/docs/infrastructure/amazon-integrations/get-started/introduction-aws-integrations/) pour découvrir et monitorer automatiquement votre fonction Lambda. Cela vous permet d'exploiter pleinement la puissance de New Relic APM pour votre serveur de fonctions. + + +## Exécutions prises en charge [#supported-runtimes] En fonction du type d'instrumentation, les durées d'exécution suivantes sont prises en charge. @@ -58,8 +62,18 @@ En fonction du type d'instrumentation, les durées d'exécution suivan * Java : l'instrumentation en couches et SDK de New Relic Java est compatible avec les versions `com.amazonaws:aws-lambda-java-events` `3.0.0` les plus récentes. -## Et ensuite ? +## Articles connexes [#related-docs] - Commencez à utiliser instrumentation et configuration de votre fonction Lambda. Découvrez comment utiliser New Relic pour monitorer votre fonction AWS Lambda. + + Instrumentez votre fonction Lambda avec l'approche par couches de New Relic. + + + + Instrumentez votre fonction Lambda à l'aide du SDK. + + + + Instrumentez votre fonction Lambda avec l'approche conteneurisée de New Relic. + \ No newline at end of file diff --git a/src/i18n/content/fr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/containerized-images.mdx b/src/i18n/content/fr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/containerized-images.mdx index 67e724b4c0c..47d6842c98f 100644 --- a/src/i18n/content/fr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/containerized-images.mdx +++ b/src/i18n/content/fr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/containerized-images.mdx @@ -202,10 +202,34 @@ Voici un guide pour ajouter notre couche prédéfinie à votre code. * [Instrumentation en couches](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/instrument-your-own/#console) * [Instrumentation basée sur le SDK](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/enable-serverless-monitoring-aws-lambda-layerless) + + + ### Rechercher et utiliser des données [#find-data] + + Une fois votre fonction AWS Lambda instrumentée, vous pouvez trouver et utiliser les données dans l'interface New Relic APM. Les données sont organisées en plusieurs domaines clés, chacun fournissant des informations différentes détaillées sur les performances et l'état de votre fonction Lambda. + + Dans l'interface APM, vous pouvez explorer différents aspects de votre fonction Lambda, notamment [le tracing distribué](https://docs.newrelic.com/docs/distributed-tracing/concepts/introduction-distributed-tracing/), [les cartes de services](https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/ui-data/service-maps/service-maps/), [les transactions](https://docs.newrelic.com/docs/apm/transactions/intro-transactions/transactions-new-relic-apm//), [l'analyse des erreurs](https://docs.newrelic.com/docs/errors-inbox/getting-started/) et bien plus encore. Chacune de ces zones fournit des informations détaillées sur les performances, la latence et le taux d'erreur de votre fonction Lambda, vous permettant d'identifier et de résoudre rapidement les problèmes. + + + L'expérience d'invocation est désormais intégrée à la trace de transaction APM. Cela vous permet d'utiliser un `AWS RequestId` spécifique pour explorer en détail une trace de transaction APM afin d'obtenir des informations détaillées sur cette exécution Lambda particulière. + + + Pour afficher votre fonction Lambda dans l'interface New Relic APM : + + 1. Allez à [https://one.newrelic.com](https://one.newrelic.com) > APM & Services. + 2. Définissez les critères de recherche comme `isLambdaFunction = true`. + 3. Dans la liste affichée, sélectionnez votre fonction Lambda pour visualiser les données. + -## Et ensuite ? +## Articles connexes [#related-docs] - En savoir plus sur les environnements d'exécution pris en charge et les prérequis Apprenez à utiliser New Relic pour monitorer votre fonction AWS Lambda Apprenez à résoudre les problèmes liés à l'installation + + En savoir plus sur les environnements d'exécution pris en charge et les prérequis + + + + Apprenez à résoudre les problèmes liés à l'installation + \ No newline at end of file diff --git a/src/i18n/content/fr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda.mdx b/src/i18n/content/fr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda.mdx index 677e8d4904f..a829d682f6b 100644 --- a/src/i18n/content/fr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda.mdx +++ b/src/i18n/content/fr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda.mdx @@ -46,7 +46,7 @@ Quel que soit votre environnement d'exécution, vous devez définir les var - Spécifie le wrapper de gestionnaire utilisé pour trouver le gestionnaire réel de votre fonction + Spécifie le wrapper de gestionnaire utilisé pour trouver le gestionnaire réel de votre fonction. Dans le cas des environnements d'exécution Go, cette variable n'est pas obligatoire. @@ -60,6 +60,20 @@ Quel que soit votre environnement d'exécution, vous devez définir les var + + + `NEW_RELIC_APM_LAMBDA_MODE` + + + + Définissez la valeur sur + + `true` + + pour activer monitoring APM de votre fonction Lambda + + + `NEW_RELIC_TRUSTED_ACCOUNT_KEY` @@ -1082,6 +1096,22 @@ En fonction de votre environnement d'exécution, vous pouvez définir les v , `DEBUG` + + , + + `TRACE` + + , + + `ERROR` + + , + + `WARN` + + , + + `ALL` @@ -1195,7 +1225,9 @@ En fonction de votre environnement d'exécution, vous pouvez définir les v - Contournez les vérifications en les fournissant sous forme de valeurs séparées par des virgules dans une chaîne. Utilisez les valeurs de chaîne + **DÉPRÉCIÉ** + + Contournez les vérifications en les fournissant sous forme de valeurs séparées par des virgules dans une chaîne. Utilisez les valeurs de chaîne `handler` @@ -1227,7 +1259,17 @@ En fonction de votre environnement d'exécution, vous pouvez définir les v - Spécifiez le nom de la clé secrète d’AWS Secrets Manager qui contient votre clé de licence. Remarque : ceci n'est utilisé que si NEW_RELIC_LICENSE_KEY n'est pas défini. + Spécifiez le **nom** ou l'**ARN** du secret d'AWS Secrets Manager qui contient votre clé de licence New Relic. + +
+ +
+ + **Remarques :** + + * Ceci n'est utilisé que si `` `NEW_RELIC_LICENSE_KEY` `` n'est pas défini. + * Le secret doit se trouver dans la même région AWS que votre fonction Lambda. + * Le rôle d'exécution de votre fonction Lambda a besoin de l'autorisation `` `secretsmanager:GetSecretValue` `` pour ce secret. @@ -1241,7 +1283,31 @@ En fonction de votre environnement d'exécution, vous pouvez définir les v - Spécifiez le nom du paramètre SSM à partir du magasin de paramètres AWS système Manager qui contient votre clé de licence. Remarque : ceci n'est utilisé que si NEW_RIC_LICENSE_KEY n'est pas défini + Spécifiez le **nom** ou l'**ARN** du paramètre du magasin de paramètres AWS Systems Manager qui contient votre clé de licence New Relic. + +
+ +
+ + **Remarques :** + + * Ceci n'est utilisé que si `` `NEW_RELIC_LICENSE_KEY` `` n'est pas défini. + * Le paramètre SSM doit se trouver dans la même région AWS que votre fonction Lambda. + * Le rôle d'exécution de votre fonction Lambda nécessite l'autorisation `` `ssm:GetParameter` `` pour ce paramètre. + + + + + + `NEW_RELIC_CLOUD_AWS_ACCOUNT_ID` + + + + + + + + Pour aider New Relic à cartographier et afficher correctement les relations entre votre entité de monitoring, fournissez l'ID du compte AWS où se trouvent vos ressources monitorées, telles que la base de données et la fonction Lambda. diff --git a/src/i18n/content/fr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own.mdx b/src/i18n/content/fr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own.mdx index ed69acbcccf..821d7e3ee60 100644 --- a/src/i18n/content/fr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own.mdx +++ b/src/i18n/content/fr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own.mdx @@ -5,14 +5,13 @@ freshnessValidatedDate: never translationType: machine --- -Une fois que vous avez lié avec succès vos comptes New Relic et AWS, vous pouvez instrumenter votre fonction Lambda en ajoutant la couche New Relic Lambda . Cela intègre l'agent New Relic, permettant monitoring automatique chaque fois que vos fonctions sont invoquées. +Vous pouvez instrument votre fonction Lambda en ajoutant la couche New Relic Lambda. Cela intègre l'agent New Relic, permettant monitoring automatique à chaque fois que vos fonctions sont invoquées. a diagram depicting non-containerized lambda function instrumentation -## Avant de commencer [#begin] - -* [Associez vos comptes New Relic et AWS](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda#link) -* [Consultez nos différentes méthodes d'instrumentation](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda#method) + + New Relic recommande d'intégrer votre compte AWS à New Relic en utilisant l' [intégration AWS](/docs/infrastructure/amazon-integrations/get-started/introduction-aws-integrations/) pour découvrir et monitorer automatiquement votre fonction Lambda. Cela vous permet d'exploiter pleinement la puissance de New Relic APM pour votre serveur de fonctions. + ## Méthodes d'instrumentation [#instrumentation] @@ -36,7 +35,7 @@ Selon vos besoins, vous pouvez choisir de contourner l'extension et de voir Pour installer ou mettre à niveau la couche d'instrumentation New Relic, exécutez cette commande : ```shell - newrelic-lambda layers install --nr-account-id YOUR_NR_ACCOUNT_ID --function my-function --upgrade + newrelic-lambda layers install --nr-account-id YOUR_NR_ACCOUNT_ID --function my-function --upgrade --apm ``` Cette commande recherche automatiquement la couche la plus récente disponible pour la région et l'environnement d'exécution de votre Lambda. @@ -51,112 +50,154 @@ Selon vos besoins, vous pouvez choisir de contourner l'extension et de voir CloudFormation est un service AWS qui simplifie l'approvisionnement et la gestion des ressources AWS. En définissant l'état souhaité des ressources dans les modèles YAML ou JSON, CloudFormation gère automatiquement l'appel d'API sous-jacent pour créer, mettre à jour ou supprimer des ressources selon les besoins. Cette approche déclarative automatise la gestion de l’infrastructure, garantissant cohérence et reproductibilité. - Voici un exemple de modèle CloudFormation simple pour une fonction Lambda Node.js : - - ```yaml - AWSTemplateFormatVersion: '2010-09-09' - Transform: AWS::Serverless-2016-10-31 - Description: And example of a simple instrumented Node.js Lambda - - Resources: - NewRelicExample: - Type: AWS::Serverless::Function - Properties: - # In this example, we're using the SAM CLI to package and deploy our lambda. SAM will transform this value during the publish step. - CodeUri: newrelic-example-node/ - # The handler for your function needs to be the one provided by the instrumentation layer, below. - Handler: newrelic-lambda-wrapper.handler - Runtime: nodejs12.x - Environment: - Variables: - # For the instrumentation handler to invoke your real handler, we need this value - NEW_RELIC_LAMBDA_HANDLER: YOUR_PATH_TO_INITIAL_LAMBDA_HANDLER - # Distributed tracing needs your account ID, and your trusted account ID - NEW_RELIC_ACCOUNT_ID: YOUR_ACCOUNT_ID_HERE - # If your New Relic account has a parent account, this value should be that account ID. Otherwise, just - # your account id. - NEW_RELIC_TRUSTED_ACCOUNT_KEY: YOUR_PARENT_ACCOUNT_ID_HERE - Layers: - # This layer includes the New Relic Lambda extension, a sidecar process that sends telemetry, - # as well as the New Relic agent for Node.js, and a handler wrapper that makes integration easy. - - !Sub arn:${AWS::Partition}:lambda:${AWS::Region}:451483290750:layer:NewRelicNodeJS12X:34 - Policies: - # This policy allows the lambda to know the value of the New Relic license key. We need this so - # that we can send telemetry back to New Relic - - AWSSecretsManagerGetSecretValuePolicy: - SecretArn: !ImportValue NewRelicLicenseKeySecret-NewRelic-LicenseKeySecretARN - ``` - - En règle générale, vous disposerez d’un fichier nommé `template.yaml` qui décrit votre fonction et ses ressources. + Pour monitorer votre fonction Lambda avec New Relic : + + 1. Installez la [couche Lambda de New Relic](https://layers.newrelic-external.com/). Voici un exemple de modèle CloudFormation simple pour une fonction Lambda Node.js : + + ```yaml + AWSTemplateFormatVersion: '2010-09-09' + Transform: AWS::Serverless-2016-10-31 + Description: And example of a simple instrumented Node.js Lambda + + Resources: + NewRelicExample: + Type: AWS::Serverless::Function + Properties: + # In this example, we're using the SAM CLI to package and deploy our lambda. SAM will transform this value during the publish step. + CodeUri: newrelic-example-node/ + # The handler for your function needs to be the one provided by the instrumentation layer, below. + Handler: newrelic-lambda-wrapper.handler + Runtime: nodejs22.x + Environment: + Variables: + # For the instrumentation handler to invoke your real handler, we need this value + NEW_RELIC_LAMBDA_HANDLER: YOUR_PATH_TO_INITIAL_LAMBDA_HANDLER + # Distributed tracing needs your account ID, and your trusted account ID + NEW_RELIC_ACCOUNT_ID: YOUR_ACCOUNT_ID_HERE + # If your New Relic account has a parent account, this value should be that account ID. Otherwise, just + # your account id. + NEW_RELIC_TRUSTED_ACCOUNT_KEY: YOUR_PARENT_ACCOUNT_ID_HERE + NEW_RELIC_APM_LAMBDA_MODE: 'true' + Tags: + # This tag is to enable APM mode. + NR.Apm.Lambda.Mode: true + Layers: + # This layer includes the New Relic Lambda extension, a sidecar process that sends telemetry, + # as well as the New Relic agent for Node.js, and a handler wrapper that makes integration easy. + - !Sub arn:${AWS::Partition}:lambda:${AWS::Region}:451483290750:layer:NewRelicNodeJS16X:103 + Policies: + # This policy allows the lambda to know the value of the New Relic license key. We need this so + # that we can send telemetry back to New Relic + - AWSSecretsManagerGetSecretValuePolicy: + SecretArn: !ImportValue NewRelicLicenseKeySecret-NewRelic-LicenseKeySecretARN + ``` + + En règle générale, vous disposerez d’un fichier nommé `template.yaml` qui décrit votre fonction et ses ressources. + + 2. Configurez les [variables d'environnement](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) requises. + + 3. Déployez votre fonction Lambda avec la configuration mise à jour. Serverless Framework est un outil de développement et de résolution de problèmes populaire pour les applications sans serveur. Il est écrit pour AWS en Node.js et agit principalement comme une abstraction de haut niveau sur les modèles CloudFormation. Il fonctionne bien pour les fonctions Node, Python, Ruby, Java et .NET. - New Relic propose un [plugin de Framework Serverless ](https://github.com/newrelic/serverless-newrelic-lambda-layers)pour simplifier l'instrumentation de votre application de framework Serverless . + New Relic propose un [plug-in pour frameworkServerless ](https://github.com/newrelic/serverless-newrelic-lambda-layers)afin de simplifier l'instrumentation de votre application Serverless. + + **Prérequis :** + + * Une application existante qui utilise le framework Serverless. + * [ID de compte New Relic](/docs/accounts/accounts-billing/account-structure/account-id) + * [API de clé personnelle New Relic](/docs/apis/intro-apis/new-relic-api-keys) + + **Pour installer et configurer votre application Serverless avec New Relic :** - Pour installer le plugin, exécutez cette commande : + 1. Si vous utilisez `npm`, exécutez la commande suivante : ```bash - npm install --save-dev serverless-newrelic-lambda-layers + npm install --save-dev serverless-newrelic-lambda-layers ``` - Ou, alternativement, vous pouvez exécuter cette commande : + OU, si vous utilisez `yarn`, exécutez la commande suivante : ```bash - yarn add --dev serverless-newrelic-lambda-layers + yarn add --dev serverless-newrelic-lambda-layers ``` - Ensuite, recherchez votre [identifiant de compte New Relic](/docs/accounts/install-new-relic/account-setup/account-id), votre [clé API personnelle New Relic](/docs/apis/get-started/intro-apis/types-new-relic-api-keys#personal-api-key) + 2. Ouvrez votre fichier `serverless.yaml` et ajoutez la configuration suivante : - Ajoutez maintenant ce qui suit à votre fichier `serverless.yaml` : + 1. Ajoutez `serverless-newrelic-lambda-layers` à votre liste `plugins`. - ```yaml - plugins: - - serverless-newrelic-lambda-layers - custom: - newRelic: - accountId: your-new-relic-account-id-here - apiKey: your-new-relic-personal-api-key-here - linkedAccount: your-new-relic-integration-account-name-here - ``` + 2. Ajoutez la configuration New Relic suivante dans la section personnalisée : + + ```yaml + plugins: + - serverless-newrelic-lambda-layers + custom: + newRelic: + accountId: your-new-relic-account-id-here + apiKey: your-new-relic-personal-api-key-here + linkedAccount: your-new-relic-integration-account-name-here + apm: true + ``` + + 3. Ajoutez la tag `NR.Apm.Lambda.Mode: true` suivante dans la section du fournisseur : + + ```yaml + provider: + tags: + NR.Apm.Lambda.Mode: true + ``` + + 3. Configurez les [variables d'environnement](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) requises. + + 4. Déployez votre fonction Lambda avec la configuration mise à jour. Le kit de développement cloud AWS (AWS CDK) est un framework permettant de définir des ressources cloud dans le code et de les provisionner via AWS CloudFormation. - Vous trouverez ci-dessous un exemple d'application CDK de base qui déploie une fonction instrumentée par New Relic Node.js Lambda: - - ```ts - import * as cdk from 'aws-cdk-lib'; - import { Construct } from 'constructs'; - import * as lambda from 'aws-cdk-lib/aws-lambda'; - - export class NewRelicExampleCdkStack extends cdk.Stack { - constructor(scope: Construct, id: string, props?: cdk.StackProps) { - super(scope, id, props); - // Add latest New Relic Lambda layer ARN from https://layers.newrelic-external.com - const NewReliclayerArn = 'arn:aws:lambda:us-east-1:451483290750:layer:NewRelicNodeJS20X:39'; - const myFunction = new lambda.Function(this, "NewRelicExampleLambda", { - runtime: lambda.Runtime.NODEJS_20_X, - // Update functions handler to point to the New Relic Lambda wrapper - handler: "newrelic-lambda-wrapper.handler", - code: lambda.Code.fromAsset('lib/lambda-runtime-code'), - layers: [lambda.LayerVersion.fromLayerVersionArn(this, 'NewRelicLayer', NewReliclayerArn)], - environment: { - // Set the NEW_RELIC_LAMBDA_HANDLER environment variable to the path of your initial handler. - NEW_RELIC_LAMBDA_HANDLER: 'index.handler', - }, - }); - } - } - ``` + Pour utiliser New Relic avec AWS CDK, suivez ces étapes : + + 1. Installez la [couche Lambda de New Relic](https://layers.newrelic-external.com/). Voici un exemple d'application CDK de base qui déploie une fonction Lambda Node.js instrumentée New Relic : + + ```ts + import * as cdk from 'aws-cdk-lib'; + import { Construct } from 'constructs'; + import * as lambda from 'aws-cdk-lib/aws-lambda'; + + export class NewRelicExampleCdkStack extends cdk.Stack { + constructor(scope: Construct, id: string, props?: cdk.StackProps) { + super(scope, id, props); + // Add latest New Relic Lambda layer ARN from https://layers.newrelic-external.com + const NewReliclayerArn = 'arn:aws:lambda:us-east-1:451483290750:layer:NewRelicNodeJS22X:38'; + const myFunction = new lambda.Function(this, "NewRelicExampleLambda", { + runtime: lambda.Runtime.NODEJS_20_X, + // Update functions handler to point to the New Relic Lambda wrapper + handler: "newrelic-lambda-wrapper.handler", + code: lambda.Code.fromAsset('lib/lambda-runtime-code'), + layers: [lambda.LayerVersion.fromLayerVersionArn(this, 'NewRelicLayer', NewReliclayerArn)], + environment: { + // Set the NEW_RELIC_LAMBDA_HANDLER environment variable to the path of your initial handler. + NEW_RELIC_LAMBDA_HANDLER: 'index.handler', + NEW_RELIC_APM_LAMBDA_MODE: 'true' + }, + }); + // Add the New Relic APM Lambda Mode tag + cdk.Tags.of(myFunction).add('NR.Apm.Lambda.Mode', 'true'); + } + } + ``` + + 2. Configurez les [variables d'environnement](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) requises. + + 3. Déployez votre fonction Lambda avec la configuration mise à jour. Terraform est un outil d'infrastructure en tant que code à usage général populaire. Il peut être utilisé pour gérer les ressources AWS. Nous proposons [quelques exemples](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/terraform) de New Relic instrumenté fonction Lambda déployée en utilisant le script Terraform. - Vous pouvez utiliser le [fournisseur New Relic Terraform](https://registry.terraform.io/providers/newrelic/newrelic/latest/docs/resources/cloud_aws_integrations) pour configurer votre intégration AWS. + Vous pouvez utiliser le [fournisseur New Relic Terraform](https://registry.terraform.io/providers/newrelic/newrelic/latest/docs/resources/cloud_aws_integrations) pour configurer votre intégration AWS. Lors de la configuration du fournisseur, configurez les [variables d'environnement](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) requises et ajoutez la tag `NR.Apm.Lambda.Mode: true` à votre fonction Lambda. @@ -210,6 +251,10 @@ Selon vos besoins, vous pouvez choisir de contourner l'extension et de voir La couche New Relic fournira automatiquement l'agent New Relic Ruby et sera chargée via un Ruby `require` avant l'appel de votre fonction Lambda. Pour éviter les conflits, n'incluez pas de copie de l'agent Ruby ailleurs. N'hésitez pas à effectuer tous les appels d'agent API New Relic Ruby souhaités au sein de votre fonction pour profiter de la présence de l'agent. + 14. Dans votre console de gestion AWS, dans l'onglet configuration, ajoutez la tag `NR.Apm.Lambda.Mode: true` à votre fonction Lambda. + + 15. Déployez votre fonction Lambda avec la configuration mise à jour. + Les environnements d'exécution Java, Python, Node.js et .Net suivront le même flux d'instrumentation que Ruby, mais avec des gestionnaires différents. Voici comment mettre à jour le gestionnaire de votre fonction pour qu'il pointe vers la couche nouvellement attachée dans la console pour votre fonction : * Java: @@ -230,26 +275,32 @@ Selon vos besoins, vous pouvez choisir de contourner l'extension et de voir -## Méthodes d'expédition +## Rechercher et utiliser des données [#find-data] - - - Chaque couche d'agent contient également une extension pour envoyer les logs et les frais à New Relic, en contournant CloudWatch. Cela peut aider à réduire la latence et les coûts. Cependant, cela comporte le risque d’impacter les performances et la fiabilité de votre fonction. +Une fois votre fonction AWS Lambda instrumentée, vous pouvez trouver et utiliser les données dans l'interface New Relic APM. Les données sont organisées en plusieurs domaines clés, chacun fournissant des informations différentes détaillées sur les performances et l'état de votre fonction Lambda. - Après avoir ajouté une couche New Relic Lambda , l'extension est activée et l'expédition log est désactivée par défaut. +Dans l'interface APM, vous pouvez explorer différents aspects de votre fonction Lambda, notamment [le tracing distribué](/docs/distributed-tracing/concepts/introduction-distributed-tracing/), [les cartes de services](/docs/new-relic-solutions/new-relic-one/ui-data/service-maps/service-maps/), [les transactions](/docs/apm/transactions/intro-transactions/transactions-new-relic-apm/), [l'analyse des erreurs](/docs/errors-inbox/getting-started/) et bien plus encore. Chacune de ces zones fournit des informations détaillées sur les performances, la latence et le taux d'erreur de votre fonction Lambda, vous permettant d'identifier et de résoudre rapidement les problèmes. - Si vous souhaitez voir les logs des fonctions dans New Relic, vous devrez activer l'envoi d'extension des logs des fonctions avec une variable d'environnement. + + L'expérience d'invocation est désormais intégrée à la trace de transaction APM. Cela vous permet d'utiliser un `AWS RequestId` spécifique pour explorer en détail une trace de transaction APM afin d'obtenir des informations détaillées sur cette exécution Lambda particulière. + - Il est important de noter que les logs de fonction ne sont pas que les logs enregistrés par la fonction lors de son appel. L'extension n'enverra pas de logs d'exécution Lambda comme les lignes `START`, `END` et `REPORT`. - +Pour afficher votre fonction Lambda dans l'interface New Relic APM : - - Vous pouvez choisir d'envoyer des données à CloudWatch uniquement ou en tant que solution de secours. Pour en savoir plus, veuillez consulter notre [documentation de secours CloudWatch](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/cloud-watch-fallback). - - +1. Allez à [https://one.newrelic.com](https://one.newrelic.com) > APM & Services. -## Et ensuite ? +2. Définissez les critères de recherche comme `isLambdaFunction = true`. + +3. Dans la liste affichée, sélectionnez votre fonction Lambda pour visualiser les données. + +## Articles connexes [#related-docs] - En savoir plus sur les environnements d'exécution pris en charge et les prérequis Apprenez à utiliser New Relic pour monitorer votre fonction AWS Lambda Apprenez à résoudre les problèmes liés à l'installation + + En savoir plus sur les environnements d'exécution pris en charge et les prérequis + + + + Apprenez à résoudre les problèmes liés à l'installation + \ No newline at end of file diff --git a/src/i18n/content/fr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda.mdx b/src/i18n/content/fr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda.mdx index 92ac8b29090..b253b607e9a 100644 --- a/src/i18n/content/fr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda.mdx +++ b/src/i18n/content/fr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda.mdx @@ -7,40 +7,155 @@ translationType: machine L'instrumentation de New Relic pour AWS Lambda offre une visibilité approfondie sur le fonctionnement interne de vos fonctions. En ajoutant l'agent New Relic à votre fonction, chaque invocation est monitorée par New Relic. Cela vous permet de suivre la durée des appels de fonction, les erreurs du moniteur et d'enregistrer les détails sur l'événement source et les réponses de votre fonction. -new-relic-lambda-entities-screenshot.png +/\* AWS Lambda fournit un service de calcul hautement évolutif et piloté par les événements, vous permettant de créer et d'exécuter des applications et des services backend sans avoir besoin de provisionner ou de gérer des serveurs. À mesure que vos architectures sans serveur sur Lambda gagnent en sophistication et assument des rôles critiques pour l'entreprise, il devient essentiel d'obtenir une visibilité complète sur leurs performances, leur état opérationnel et leur interaction au sein de votre écosystème d'applications plus large afin de maintenir leur fiabilité et leur efficacité. Votre application moderne repose fortement sur de nombreuses fonctions AWS Lambda interagissant avec divers autres microservices, bases de données et API tierces. Dans de tels environnements complexes, vous pourriez rencontrer plusieurs défis d'observabilité : \* \*\*Difficulté à identifier les causes profondes :\*\* Lorsque des problèmes de performance tels que des ralentissements intermittents surviennent ou que des transactions critiques impliquant une fonction Lambda échouent, identifier la fonction défaillante exacte ou la source du problème peut s'avérer un casse-tête complexe. \* \*\*Vues monitoring cloisonnées :\*\* Vous pouvez vous retrouver à naviguer entre une interface utilisateur monitoring sans serveur dédiée et vos vues traditionnelles de monitoring des performances des applications (APM), ce qui rend difficile l'obtention d'une image unique et unifiée des performances. \* \*\*Corrélation de données inefficace :\*\* Il peut être difficile de corréler efficacement les données de performance et les événements lorsque les informations résident dans des systèmes monitoring sans serveur et APM distincts. \* \*\*Tracing de bout en bout incomplet :\*\* Vous pourriez rencontrer des difficultés pour suivre de manière transparente une seule requête de bout en bout lorsqu’elle traverse la fonction Lambda et d’autres services au sein de votre environnement distribué. \* \*\* Monitoring limitée pour Lambda:\*\* Il est souvent impossible d'appliquer directement à votre fonction Lambda toute la puissance de diagnostic et le flux de travail familier des outils APM. \* \*\*Effort manuel pour les informations détaillées :\*\* Un effort manuel important est souvent nécessaire pour rassembler des informations disparates provenant de diverses sources afin de comprendre le contexte complet d'un problème impliquant Lambda. Pour relever ces défis en matière d'observabilité et offrir une expérience monitoring véritablement unifiée, New Relic améliore l'intégration des fonctions AWS Lambda dans sa plateforme. Cette initiative intègre directement vos fonctions serverless dans l'expérience New Relic APM, en les traitant comme des éléments de première classe au même titre que vos autres services instrumentés. Notre objectif est de fournir une télémétrie riche et adaptée aux applications pour votre fonction Lambda, facilitant ainsi la compréhension de ses performances dans leur contexte complet. \*/ -## Méthodes d'expédition pour la télémétrie Lambda [#shipping-methods] +## Fonctionnalité clé [#key-features] -Il existe trois méthodes principales pour envoyer des données télémétriques d'AWS Lambda vers New Relic, chacune avec ses propres considérations de coût et de fiabilité : +* **Bénéficiez d'une vue unifiée :** monitorez votre fonction Lambda au sein de la même interface APM que celle utilisée pour vos autres services. Visualisez la télémétrie sans serveur, y compris les indicateurs de performance, les traces, les logs (lorsqu'ils sont configurés) et les erreurs, le tout corrélé en un seul endroit, éliminant ainsi le besoin de basculer entre différentes interfaces utilisateur. -* **Méthode rentable**: utilisez les couches de New Relic, y compris l'extension Lambda, qui évite d'envoyer des données à AWS CloudWatch par défaut. -* **Méthode axée sur la fiabilité**: désactivez l’extension New Relic Lambda et utilisez CloudWatch exclusivement pour expédier des données, réduisant ainsi la surcharge de la fonction Lambda. -* **Méthode hybride**: combinez l'extension avec CloudWatch comme solution de secours, en équilibrant efficacité des coûts et fiabilité. +* **Exploitez toute la puissance de l'APM :** appliquez la suite complète de fonctionnalités New Relic APM directement à votre fonction Lambda. Cela inclut le tracing avancé distribué, une analyse détaillée des erreurs avec la boîte de réception des erreurs, des cartes de service qui intègrent votre fonction Lambda, des dashboards, et plus encore. Pour plus d'informations, consultez la [documentation APM](https://docs.newrelic.com/docs/apm/new-relic-apm/getting-started/introduction-apm/). -## Considération des coûts [#costs] +* **Bénéficiez d'un suivi complet des requêtes de bout en bout :** trace en toute transparence requests depuis vos services frontaux ou autres microservices, en passant par votre fonction AWS Lambda, jusqu'aux composants connectés. Cela permet d'obtenir une image claire et continue de la latence des requêtes et des dépendances sur l'ensemble de votre architecture. Pour plus d'informations, reportez-vous à la [documentation sur le tracing distribué](https://docs.newrelic.com/docs/distributed-tracing/concepts/introduction-distributed-tracing/). -La mise en œuvre du monitoring de serverless pour AWS Lambda peut entraîner des frais AWS supplémentaires. La fonction Lambda `newrelic-log-ingestion`, qui transmet des données à New Relic, est considérée comme un service tiers et tous les frais AWS associés sont à la charge de l'utilisateur. +* **Simplifiez l'analyse des causes profondes :** en consolidant les données sans serveur avec le reste de votre télémétrie applicative dans APM, vous pouvez rapidement identifier et diagnostiquer les problèmes, qu'ils proviennent d'une fonction Lambda ou d'un service en amont/en aval. -Si vous utilisez notre [extension newrelic-lambda](https://github.com/newrelic/newrelic-lambda-extension) fournie dans nos [couches New Relic Lambda ](https://github.com/newrelic/newrelic-lambda-layers), vous pouvez éviter d'envoyer des logs et des données de télémétrie via CloudWatch et la fonction [d'ingestion newrelic-log](https://github.com/newrelic/aws-log-ingestion) . Il est également possible de configurer la fonction [newrelic-log-ingestion](https://github.com/newrelic/aws-log-ingestion) comme méthode [de secours CloudWatch](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/cloud-watch-fallback/) pour les fonctions qui nécessitent une haute disponibilité des données d'observabilité. +* **Comprenez mieux l'impact du serverless :** visualisez clairement comment votre fonction Lambda contribue à la santé et aux performances globales de vos applications et de vos transactions commerciales clés, en fournissant des informations plus détaillées sur son rôle au sein de vos services numériques. + +New Relic Lambda Entities in APM + +## Comment configurer monitoring AWS Lambda ? [#config] + +Pour monitorer votre AWS Lambda avec New Relic, vous pouvez configurer l'instrumentation dans différents environnements, temps d'exécution et méthodes de déploiement. Les étapes suivantes vous guideront tout au long du processus de configuration : + + + + ### Compatibilité et exigences [#req] + + Assurez-vous que votre instance AWS Lambda répond à nos [exigences de compatibilité](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/compatibility-requirement-lambda-monitoring). + + + + ### (Facultatif) Liez votre compte AWS à New Relic [#link] + + En liant des comptes, vous accordez à New Relic l'autorisation de créer un inventaire de votre compte AWS et de collecter automatiquement les métriques CloudWatch pour votre fonction Lambda. Une fois que vous avez lié des comptes, les ressources de votre compte AWS apparaissent sous forme d'entité dans l'[explorateur d'entités](/docs/new-relic-solutions/new-relic-one/core-concepts/new-relic-explorer-view-performance-across-apps-services-hosts/#find). L'entité fonction Lambda se trouvera dans la vue fonction serverless. + + Vous pouvez lier votre compte AWS et New Relic par l’une des méthodes d’intégration suivantes. + + + + flux de métriques AWS(recommended) API Polling + + + + + Pour que New Relic puisse monitorer votre fonction Lambda, vous devez configurer une intégration entre New Relic et AWS. Nous recommandons l'utilisation de [Metric Streams](/install/aws-cloudwatch) pour aider à réduire la latence et éviter la limitation de nos requests d'interrogation. + + + + Si vous n'utilisez pas d'intégration métrique Streams, vous pouvez choisir de configurer une intégration [d'interrogation API](/docs/infrastructure/amazon-integrations/connect/set-up-aws-api-polling) à la place. Par défaut, une intégration d'interrogation d'API avec le service Lambda activé interrogera toutes les 5 minutes pour obtenir les métriques CloudWatch. + + Vous pouvez utiliser [newrelic-lambda-cli](https://github.com/newrelic/newrelic-lambda-cli) pour configurer une intégration d'interrogation API, mais pas une intégration de flux métrique. + + ```sh + newrelic-lambda integrations install --nr-account-id YOUR_NR_ACCOUNT_ID \ + --nr-api-key YOUR_NEW_RELIC_USER_KEY + ``` + + Une étape de la [commande d’installation d’intégration](https://github.com/newrelic/newrelic-lambda-cli?tab=readme-ov-file#aws-lambda-integration) créera un secret `NEW_RELIC_LICENSE_KEY` dans [AWS Secrets Manager](https://aws.amazon.com/secrets-manager/) pour une sécurité améliorée. Ceci est configurable avec un indicateur `--disable-license-key-secret` , ainsi que d'autres options et indicateurs. + + + + + + + ### instrumentez votre fonction AWS Lambda [#instrument] + + Pour instrumenter votre fonction Lambda, vous avez besoin d'un agent et d'une extension. Ces composants sont regroupés dans la [couche New Relic Lambda](https://github.com/newrelic/newrelic-lambda-layers). Si l’utilisation de couches Lambda n’est pas une option pour vous, vous pouvez incorporer manuellement l’agent et l’extension dans votre fonction. En fonction des exigences de votre fonction Lambda, sélectionnez l’une des méthodes d’instrumentation suivantes : + + + + Instrumentation en couches Instrumentation basée sur un SDK Instrumentation conteneurisée + + + + + Utilisez cette méthode si votre fonction Lambda est packagée sous forme de fichier Zip et que vous pouvez ajouter des calques. Les couches sont un mécanisme de distribution pour la bibliothèque, les environnements d'exécution personnalisés et d'autres dépendances. Pour plus d'informations, reportez-vous à la documentation [de l'instrumentation en couches](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own/) . + + + + Utilisez cette méthode si votre fonction Lambda ne peut pas utiliser de couches, garantissant un déploiement rapide sans qu'il soit nécessaire de modifier les couches. Pour plus d'informations, reportez-vous à la documentation [de l'instrumentation basée sur le SDK](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/sdk-based-instrumentation/) . + + + + Utilisez cette méthode si votre fonction Lambda s'exécute dans un conteneur. Les conteneurs offrent un environnement d'exécution cohérent et isolé pour vos applications. New Relic fournit une image Docker préconfigurée qui inclut la couche New Relic Lambda, l'extension New Relic Lambda et l'agent New Relic. Pour plus d'informations, veuillez consulter la documentation [sur l'instrumentation conteneurisée](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/containerized-images/). + + + + + + + ### Configurer les variables d’environnement [#env-variables] + + + * Lorsque vous instrumentez la couche Lambda de New Relic avec la CLI New Relic, vos variables d'environnement obligatoires sont configurées automatiquement. Cependant, vous souhaiterez peut-être modifier certains des paramètres par défaut et configurer votre fonction Lambda avec les variables d'environnement qui correspondent à vos besoins monitoring . + * Si vous utilisez l’extension New Relic Lambda, vous devez configurer les variables d’environnement manuellement. + + + [Les variables d’environnement](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) sont utilisées pour configurer l’agent New Relic et l’extension Lambda. Il est important de définir correctement ces variables pour garantir que vos fonctions Lambda sont correctement monitorées. + + + + ### Retrouvez vos données dans New Relic [#data] + + Une fois votre fonction AWS Lambda instrumentée, vous pouvez trouver et utiliser les données dans l'interface New Relic APM. Les données sont organisées en plusieurs domaines clés, chacun fournissant des informations différentes détaillées sur les performances et l'état de votre fonction Lambda. + + + +## Essayez nos exemples de fonctions [#example] + +Après avoir instrumenté la couche Lambda de New Relic, nous vous recommandons vivement d'essayer nos exemples de fonctions. Ces exemples de travail doivent être utilisés comme point de départ pour instrumenter votre propre fonction serverless. L’utilisation de ces exemples peut vous aider à vous familiariser avec la couche New Relic Lambda, à tester le lien de compte, et ils peuvent être utilisés comme référence pour votre propre instrumentation. Chaque exemple illustre l'ajout d'autorisations, des techniques spécifiques à l'exécution pour encapsuler votre gestionnaire, la gestion de la conservation log des fonctions dans CloudWatch, et bien plus encore. + +Bien qu'il existe de nombreuses façons de gérer et d'utiliser la fonction Lambda, AWS CloudFormation est le mécanisme que nous utilisons pour nos exemples. + +Nos exemples sont publiés, aux côtés de l'extension New Relic Lambda, dans ce [référentiel GitHub](https://github.com/newrelic/newrelic-lambda-extension). Il y en a un pour chaque runtime Lambda pris en charge par New Relic : + +* [Node.js](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/sam/node) +* [Python](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/sam/python) +* [Go](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/sam/go) +* [Java](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/sam/java) +* [Ruby](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/sam/ruby) +* [.NET](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/sam/dotnet) + +Vous pouvez également apprendre comment instrumenter le tracing distribué dans une application sans serveur non triviale dans notre [exemple de tracing distribué](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/sam/distributedtracing). Il illustre la propagation manuelle trace pour SQS et SNS, deux des services les plus populaires susceptibles d'invoquer la fonction Lambda, avec les fonctions Node, Python, Ruby et Java . - Quelle que soit la méthode d'expédition utilisée, la charge utile et l'expérience dans New Relic restent les mêmes. + Lors de tests manuels, les données télémétriques peuvent être retardées. Nous vous recommandons d'attendre sept secondes avant d'appeler à nouveau la fonction, ce qui permet à toute télémétrie mise en mémoire tampon d'être transmise. -L'activation monitoring sans serveur pour AWS Lambda peut entraîner des frais Amazon Web Services. Notre fonction `newrelic-log-ingestion` Lambda, qui nous rapporte vos données Lambda , est considérée comme un [service tiers](/docs/licenses/license-information/acceptable-use-policy/acceptable-use-policy): les frais AWS résultant de votre utilisation de celui-ci sont à votre charge. +## Considération des coûts [#costs] + +La mise en œuvre d'un serveur monitoring sans serveur pour AWS Lambda peut entraîner des frais AWS supplémentaires. La fonction Lambda `newrelic-log-ingestion` , qui transmet des données à New Relic, est considérée comme un service tiers et tous les frais AWS associés sont à la charge de l'utilisateur. En utilisant les [`newrelic-lambda-extension`](https://github.com/newrelic/newrelic-lambda-extension) inclus dans [les couches Lambda New Relic](https://github.com/newrelic/newrelic-lambda-layers), vous pouvez éviter d'envoyer des logs et des données télémétriques via CloudWatch, bien que la configuration de la fonction `newrelic-log-ingestion` comme solution de secours CloudWatch soit possible pour les besoins de haute disponibilité. + +L'activation monitoring sans serveur pour AWS Lambda peut entraîner des frais Amazon Web Services. Notre fonction Lambda `newrelic-log-ingestion`, qui nous transmet vos données Lambda, est considérée comme un [service tiers](/docs/licenses/license-information/general-usage-licenses/acceptable-use-policy): les frais AWS résultant de son utilisation sont à votre charge. + +Si vous utilisez notre [extension newrelic-lambda](https://github.com/newrelic/newrelic-lambda-extension) fournie dans nos [couches New Relic Lambda ](https://github.com/newrelic/newrelic-lambda-layers), vous pouvez éviter d'envoyer des logs et des données de télémétrie via CloudWatch et la fonction [d'ingestion newrelic-log](https://github.com/newrelic/aws-log-ingestion) . Il est également possible de configurer la fonction [newrelic-log-ingestion](https://github.com/newrelic/aws-log-ingestion) comme méthode [de secours CloudWatch](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/cloud-watch-fallback/) pour les fonctions qui nécessitent une haute disponibilité des données d'observabilité. + +## Tarifs [#pricing] + +Votre utilisation de New Relic APM + Serverless Convergence est facturée comme une entité APM conformément à votre commande. Pour plus de détails sur les prix, veuillez contacter notre équipe commerciale ou vous référer à votre commande. -## Et ensuite ? +## Articles connexes [#related-docs] - - En savoir plus sur les environnements d'exécution pris en charge et les prérequis + + Instrumentez votre fonction Lambda avec l'approche par couches de New Relic. - - Démarrez avec l'instrumentation et configuration de votre fonction Lambda + + Instrumentez votre fonction Lambda à l'aide du SDK. - - Apprenez à utiliser New Relic pour surveiller votre fonction AWS Lambda + + Instrumentez votre fonction Lambda avec l'approche conteneurisée de New Relic. \ No newline at end of file diff --git a/src/i18n/content/fr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/sdk-based-instrumentation.mdx b/src/i18n/content/fr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/sdk-based-instrumentation.mdx index bd8da11956f..83806e67e44 100644 --- a/src/i18n/content/fr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/sdk-based-instrumentation.mdx +++ b/src/i18n/content/fr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/sdk-based-instrumentation.mdx @@ -67,9 +67,11 @@ Sélectionnez votre runtime ci-dessous et suivez les instructions de configurati - 5. Pour activer [le tracing distribué](/docs/apm/distributed-tracing/getting-started/introduction-distributed-tracing) et configurer les variables d'environnement, reportez-vous à la documentation [des variables d'environnement](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) . + 5. Configurez les [variables d'environnement](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda). - 6. Invoquez le Lambda au moins une fois. Cela crée un CloudWatch log groupe , qui doit être présent pour que l’étape suivante fonctionne. + 6. Dans votre console de gestion AWS, dans l'onglet configuration, ajoutez la tag `NR.Apm.Lambda.Mode: true` à votre fonction Lambda. + + 7. Invoquez le Lambda au moins une fois. Cela crée un CloudWatch log groupe , qui doit être présent pour que l’étape suivante fonctionne. Notre wrapper collecte des données sur l'exécution Lambda , génère un message JSON et l'enregistre dans les logs CloudWatch . Ensuite, vous [configurerez CloudWatch pour envoyer ces logs à New Relic](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/instrument-your-own/#manual-stream-logs). @@ -130,9 +132,11 @@ Sélectionnez votre runtime ci-dessous et suivez les instructions de configurati 6. Dans la console AWS Lambda, définissez le gestionnaire. Pour l'[exemple Java Lambda](https://github.com/newrelic/newrelic-lambda-tracer-java#usage), le gestionnaire serait `com.handler.example.MyLambdaHandler::handleRequest`. Étant donné que `handleRequest` est supposé, vous pouvez également utiliser `com.handler.example.MyLambdaHandler`. - 7. Pour activer [le tracing distribué](/docs/apm/distributed-tracing/getting-started/introduction-distributed-tracing) et configurer les variables d'environnement, reportez-vous à la documentation [des variables d'environnement](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) . + 7. Configurez les [variables d'environnement](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda). + + 8. Dans votre console de gestion AWS, dans l'onglet configuration, ajoutez la tag `NR.Apm.Lambda.Mode: true` à votre fonction Lambda. - 8. Invoquez le Lambda au moins une fois. Cela crée un CloudWatch log groupe , qui doit être présent pour que l’étape suivante fonctionne. + 9. Invoquez le Lambda au moins une fois. Cela crée un CloudWatch log groupe , qui doit être présent pour que l’étape suivante fonctionne. Notre wrapper collecte des données sur l'exécution Lambda , génère un message JSON et l'enregistre dans les logs CloudWatch . Ensuite, vous [configurerez CloudWatch pour envoyer ces logs à New Relic](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/instrument-your-own/#manual-stream-logs). @@ -211,9 +215,11 @@ Sélectionnez votre runtime ci-dessous et suivez les instructions de configurati 5. Téléchargez le fichier zippé sur votre compte AWS Lambda. - 6. Pour activer [le tracing distribué](/docs/apm/distributed-tracing/getting-started/introduction-distributed-tracing) et configurer les variables d'environnement, reportez-vous à la documentation [des variables d'environnement](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) . + 6. Configurez les [variables d'environnement](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda). + + 7. Dans votre console de gestion AWS, dans l'onglet configuration, ajoutez la tag `NR.Apm.Lambda.Mode: true` à votre fonction Lambda. - 7. Pour compléter l'instrumentation, suivez l'une des étapes suivantes pour envoyer les données télémétriques à New Relic : + 8. Pour compléter l'instrumentation, suivez l'une des étapes suivantes pour envoyer les données télémétriques à New Relic : * Utilisez le New Relic Lambda `Extension layer`. Vous pouvez obtenir la dernière couche arn [(NewRelicLambdaExtension)](https://layers.newrelic-external.com/) . Vous pouvez soit utiliser AWS CLI pour installer la couche, soit l'ajouter manuellement à votre Lambda. @@ -269,9 +275,11 @@ Sélectionnez votre runtime ci-dessous et suivez les instructions de configurati 6. Téléchargez le fichier zippé sur votre compte AWS Lambda. - 7. Pour activer [le tracing distribué](/docs/apm/distributed-tracing/getting-started/introduction-distributed-tracing) et configurer les variables d'environnement, reportez-vous à la documentation [des variables d'environnement](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) . + 7. Configurez les [variables d'environnement](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda). - 8. Invoquez le Lambda au moins une fois. Cela crée un CloudWatch log groupe , qui doit être présent pour que l’étape suivante fonctionne. + 8. Dans votre console de gestion AWS, dans l'onglet configuration, ajoutez la tag `NR.Apm.Lambda.Mode: true` à votre fonction Lambda. + + 9. Invoquez le Lambda au moins une fois. Cela crée un CloudWatch log groupe , qui doit être présent pour que l’étape suivante fonctionne. Le décorateur New Relic collecte des données sur l'exécution Lambda , génère un message JSON et l'enregistre dans les logs CloudWatch . Ensuite, [configurez CloudWatch pour envoyer ces logs à New Relic](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/instrument-your-own/#manual-stream-logs). @@ -282,25 +290,38 @@ Sélectionnez votre runtime ci-dessous et suivez les instructions de configurati Pour instrumenter votre Lambda en langage .NET : 1. Ajoutez le [package nuget NewRelic.Agent](https://www.nuget.org/packages/NewRelic.Agent) à votre projet AWS Lambda. Pour plus d'informations, consultez notre [guide d'installation](/docs/apm/agents/net-agent/install-guides/install-net-agent-using-nuget/). - 2. Pour activer [le tracing distribué](/docs/apm/distributed-tracing/getting-started/introduction-distributed-tracing) et configurer les variables d'environnement, reportez-vous à la documentation [des variables d'environnement](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) . - 3. Publiez le projet sur votre compte AWS Lambda. - 4. [Configurez](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/account-linking/) soit l’extension New Relic Lambda, soit le lambda `newrelic-log-ingestion` . - 5. Appelez le Lambda au moins une fois pour vérifier les erreurs et vous assurer que les données sont visibles dans l'interface utilisateur de New Relic. + 2. Configurez les [variables d'environnement](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda). + 3. Dans votre console de gestion AWS, dans l'onglet configuration, ajoutez la tag `NR.Apm.Lambda.Mode: true` à votre fonction Lambda. + 4. Publiez le projet sur votre compte AWS Lambda. + 5. [Configurez](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/account-linking/) soit l’extension New Relic Lambda, soit le lambda `newrelic-log-ingestion` . + 6. Appelez le Lambda au moins une fois pour vérifier les erreurs et vous assurer que les données sont visibles dans l'interface utilisateur de New Relic. -## Et ensuite ? +## Rechercher et utiliser des données [#find-data] + +Une fois votre fonction AWS Lambda instrumentée, vous pouvez trouver et utiliser les données dans l'interface New Relic APM. Les données sont organisées en plusieurs domaines clés, chacun fournissant des informations différentes détaillées sur les performances et l'état de votre fonction Lambda. + +Dans l'interface APM, vous pouvez explorer différents aspects de votre fonction Lambda, notamment [le tracing distribué](/docs/distributed-tracing/concepts/introduction-distributed-tracing/), [les cartes de services](/docs/new-relic-solutions/new-relic-one/ui-data/service-maps/service-maps/), [les transactions](docs/apm/transactions/intro-transactions/transactions-new-relic-apm//), [l'analyse des erreurs](docs/errors-inbox/getting-started/) et bien plus encore. Chacune de ces zones fournit des informations détaillées sur les performances, la latence et le taux d'erreur de votre fonction Lambda, vous permettant d'identifier et de résoudre rapidement les problèmes. + + + L'expérience d'invocation est désormais intégrée à la trace de transaction APM. Cela vous permet d'utiliser un `AWS RequestId` spécifique pour explorer en détail une trace de transaction APM afin d'obtenir des informations détaillées sur cette exécution Lambda particulière. + + +Pour afficher votre fonction Lambda dans l'interface New Relic APM : + +1. Allez à [https://one.newrelic.com](https://one.newrelic.com) > APM & Services. +2. Définissez les critères de recherche comme `isLambdaFunction = true`. +3. Dans la liste affichée, sélectionnez votre fonction Lambda pour visualiser les données. + +## Articles connexes [#related-docs] En savoir plus sur les environnements d'exécution pris en charge et les prérequis - - Apprenez à utiliser New Relic pour surveiller votre fonction AWS Lambda - - - + Apprenez à résoudre les problèmes liés à l'installation \ No newline at end of file diff --git a/src/i18n/content/fr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/update-lambda-monitoring.mdx b/src/i18n/content/fr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/update-lambda-monitoring.mdx index 807ca875905..954f1f4497f 100644 --- a/src/i18n/content/fr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/update-lambda-monitoring.mdx +++ b/src/i18n/content/fr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/update-lambda-monitoring.mdx @@ -5,7 +5,7 @@ freshnessValidatedDate: never translationType: machine --- -Après [avoir activé notre monitoring pour AWS Lambda](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/enable-new-relic-monitoring-aws-lambda), vous devez occasionnellement mettre à jour notre fonction Lambda utilisée pour signaler les données log AWS : `newrelic-log-ingestion`. +Après [avoir activé notre monitoring pour AWS Lambda](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda/#link), vous devez occasionnellement mettre à jour notre fonction Lambda qui est utilisée pour signaler les données log AWS : `newrelic-log-ingestion`. Il y a deux façons de procéder : @@ -13,7 +13,7 @@ Il y a deux façons de procéder : * [Mise à jour via l'application AWS Serverless référentiel](#update-sar): utilisez ceci si vous avez activé à l'aide de la [procédure manuelle](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/enable-new-relic-monitoring-aws-lambda#manual-nr-lambda). - Ces procédures de mise à jour s'appliquent à notre [monitoring serveur sans serveur pour AWS Lambda](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/introduction-new-relic-monitoring-aws-lambda), et non à notre [monitoring deinfrastructure pour AWS Lambda l'intégration](/docs/integrations/amazon-integrations/aws-integrations-list/aws-lambda-monitoring-integration). + Ces procédures de mise à jour s'appliquent à notre [monitoring sans serveur pour AWS Lambda](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda), et non à notre [monitoring d'infrastructure pour l'intégration AWS Lambda ](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-lambda-monitoring-integration). ## Mettre à jour notre intégration Lambda via CLI [#update-cli] @@ -60,6 +60,7 @@ Cette section décrit comment mettre à jour la couche de votre fonction si vous --function installed \ --nr-account-id NR_ACCOUNT_ID \ --upgrade + --apm ``` ## Mettre à jour une installation manuelle du référentiel d'application Serverless [#update-sar] diff --git a/src/i18n/content/fr/docs/serverless-function-monitoring/aws-lambda-monitoring/troubleshooting/troubleshoot-enabling-serverless-monitoring-aws-lambda.mdx b/src/i18n/content/fr/docs/serverless-function-monitoring/aws-lambda-monitoring/troubleshooting/troubleshoot-enabling-serverless-monitoring-aws-lambda.mdx index 7a414f9cd1f..269b5077cd9 100644 --- a/src/i18n/content/fr/docs/serverless-function-monitoring/aws-lambda-monitoring/troubleshooting/troubleshoot-enabling-serverless-monitoring-aws-lambda.mdx +++ b/src/i18n/content/fr/docs/serverless-function-monitoring/aws-lambda-monitoring/troubleshooting/troubleshoot-enabling-serverless-monitoring-aws-lambda.mdx @@ -1,5 +1,5 @@ --- -title: Dépannage de l'activation monitoring sans serveur d'AWS Lambda +title: Dépannage du monitoring Lambda type: troubleshooting tags: - Serverless function monitoring @@ -12,22 +12,22 @@ translationType: machine ## Problème -Vous essayez d'activer [monitoring sans serveur pour AWS Lambda](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/introduction-new-relic-monitoring-aws-lambda) et rencontrez un problème ou une erreur. +Vous tentez d'activer [monitoring sans serveur pour AWS Lambda](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda) et vous rencontrez un problème ou une erreur. ## Solution -Il existe deux problèmes courants liés au fait de ne pas terminer toutes les [procédures d'activation](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/enable-new-relic-monitoring-aws-lambda): +Deux problèmes courants sont liés au fait de ne pas avoir terminé toutes les [procédures d'activation](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda/#link): -* Aucune donnée ne s'affiche sur la page d'interface utilisateur **CloudWatch metrics** . Cela signifie que l’ [étape d’intégration AWS](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/enable-new-relic-monitoring-aws-lambda#connect-aws) n’a pas été terminée. -* Les données ne s'affichent pas sur les pages de l'interface utilisateur de la catégorie **Troubleshooting** . Si vous ne voyez pas de données dans les onglets d'interface utilisateur **Distributed tracing**, **Errors** et **Invocations** , cela signifie que l'[étape d'instrumentation de l'agent APM](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/enable-new-relic-monitoring-aws-lambda#instrument-lambda) n'a pas été terminée. +* Aucune donnée n'apparaît sur la page d'interface utilisateur **Lambda metrics**. Cela signifie que l' [étape d'intégration AWS](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda/#link) n'a pas été terminée. +* Aucune donnée n'est visible sur les pages d'interface utilisateur de la catégorie **Troubleshooting**. Si vous ne voyez pas de données sur les onglets d'interface utilisateur **Distributed tracing**, **Errors** et **Invocations**, cela signifie que l' [étape d'agent d'instrumentation APM](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda/#instrument) n'a pas été terminée. Outre ces problèmes d'activation de base, certains problèmes supplémentaires peuvent entraîner un problème : -* Erreur CloudWatch « Erreur HTTP 401 : non autorisée ». Cela est dû à une clé API incorrecte. L'argument `--nr-api-key`dans l'[étape Configurer AWS enable](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/enable-new-relic-monitoring-aws-lambda#connect-aws) prend votre . +* Erreur CloudWatch « Erreur HTTP 401 : non autorisé. » Cela est dû à une clé API incorrecte. L'argument `--nr-api-key`dans l' [étape Configure AWS enable](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda/#link) prend votre . * Les métriques personnalisées sont manquantes. Lambda monitoring n'est pas compatible avec nos [métriques personnalisées](/docs/agents/manage-apm-agents/agent-data/collect-custom-metrics). Utilisez [l'attribut personnalisé](/docs/agents/manage-apm-agents/agent-data/collect-custom-attributes) pour ajouter des métadonnées. -* Invocations manquantes. Pour voir les détails de la répartition des appels, le tracing distribué doit être activé dans le cadre de l’ [étape d’instrumentation Lambda ](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/enable-new-relic-monitoring-aws-lambda#instrument-lambda). Le tracing distribué est requis pour que les détails de l'étendue puissent être affichés dans le volet des détails de l'invocation. +* Onglet « Invocations » manquant. Avec APM + Serverless Convergence, chaque invocation Lambda correspond à la trace de transaction dans APM. Pour voir les détails de l'invocation, reportez-vous à la [trace de transaction](/docs/apm/apm-ui-pages/monitoring/transactions-page-find-specific-performance-problems). * Vous avez terminé correctement les étapes d'installation, d'intégration et d'instrumentation, et votre fonction envoie les logs à CloudWatch mais vous ne voyez pas de trace pour une dépendance spécifique (ou aucune trace) dans l'interface utilisateur. Cela peut résulter de l'ordre de fusion des couches (si vous utilisez nos couches Lambda ) ou de l'ordre d'importation (si vous êtes instrumenté manuellement) : diff --git a/src/i18n/content/fr/docs/serverless-function-monitoring/aws-lambda-monitoring/troubleshooting/troubleshoot-no-data-appears.mdx b/src/i18n/content/fr/docs/serverless-function-monitoring/aws-lambda-monitoring/troubleshooting/troubleshoot-no-data-appears.mdx index c5d77b6ccd4..ce2d21b8578 100644 --- a/src/i18n/content/fr/docs/serverless-function-monitoring/aws-lambda-monitoring/troubleshooting/troubleshoot-no-data-appears.mdx +++ b/src/i18n/content/fr/docs/serverless-function-monitoring/aws-lambda-monitoring/troubleshooting/troubleshoot-no-data-appears.mdx @@ -10,12 +10,22 @@ freshnessValidatedDate: never translationType: machine --- -## Problème +## Problème [#problem] Après avoir généré du trafic pour votre fonction AWS Lambda et attendu cinq minutes, aucune de vos données de fonction n'apparaît dans l'interface utilisateur de New Relic. Il n'y a aucune erreur dans les logs, et aucun `NRIntegrationErrors` ou `NRIntegrationWarnings` dans l'interface utilisateur de New Relic. -## Solution +## Solution [#solution] + +### Vérifiez la clé de licence et l'identifiant du compte. [#check-license] La raison la plus courante pour laquelle aucune donnée n'apparaît et aucune erreur n'apparaît est que la [clé de licence et l'ID de compte](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/account-linking/) proviennent de comptes différents. En cas d'incompatibilité, l'[extension New Relic Lambda ](https://github.com/newrelic/newrelic-lambda-extension)ou [lambda qui traite les logs de monitoring cloud ](/docs/infrastructure/amazon-integrations/connect/aws-metric-stream/)signale les données avec succès, mais les supprime silencieusement car l'ID de compte ne correspond pas. Cela n’entraîne aucune erreur ni aucun avertissement. -Pour résoudre ce problème, assurez-vous que la clé de licence et l’ID de compte proviennent du même compte. Il est recommandé d’utiliser l’ [interface de ligne de commande New Relic Lambda ](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/account-linking/#rec)pour activer monitoring sans serveur afin de minimiser ces types de problèmes. Vous pouvez mettre à jour la clé de licence dans AWS Secrets Manager. Pour l'ID de compte et la configuration n'utilisant pas AWS Secrets Manager, vous pouvez mettre à jour les [variables d'environnement](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/account-linking/#env-var) avec la clé de licence ou l'ID de compte correct pour corriger le problème. \ No newline at end of file +Pour résoudre ce problème, assurez-vous que la clé de licence et l’ID de compte proviennent du même compte. Il est recommandé d’utiliser l’ [interface de ligne de commande New Relic Lambda ](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/account-linking/#rec)pour activer monitoring sans serveur afin de minimiser ces types de problèmes. Vous pouvez mettre à jour la clé de licence dans AWS Secrets Manager. Pour l'ID de compte et la configuration n'utilisant pas AWS Secrets Manager, vous pouvez mettre à jour les [variables d'environnement](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/account-linking/#env-var) avec la clé de licence ou l'ID de compte correct pour corriger le problème. + +### Vérifier les variables d'environnement [#check-env-vars] + +Assurez-vous que les [variables d'environnement](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) nécessaires sont correctement définies dans votre fonction AWS Lambda. Cela inclut les variables `NEW_RELIC_APM_LAMBDA_MODE`, `NEW_RELIC_ACCOUNT_ID`, `NEW_RELIC_LICENSE_KEY` et toutes autres variables pertinentes. Si ces variables ne sont pas définies ou sont incorrectes, cela peut empêcher l'envoi des données à New Relic. Pour plus d'informations, consultez la section sur [les variables d'environnement](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda). + +### Recherchez l'étiquette sur la console de gestion AWS. [#check-tags] + +Assurez-vous d'avoir ajouté la tag `NR.Apm.Lambda.Mode: true` à votre fonction Lambda depuis la console de gestion AWS. Cette tag est essentielle pour activer monitoring et garantir l'envoi des données à New Relic. \ No newline at end of file diff --git a/src/i18n/content/jp/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx b/src/i18n/content/jp/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx index 724eab69dd7..acdfcca1437 100644 --- a/src/i18n/content/jp/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx +++ b/src/i18n/content/jp/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx @@ -36,7 +36,7 @@ New Relicの .NET エージェントは、.NET フレームワークと .NET Cor - The .NET agent is compatible with .NET Core version 3.1, and .NET 5.0, 6.0, 7.0, 8.0, 9.0, and 10.0. + .NET エージェントは、.NET Core バージョン 3.1、および .NET 5.0、6.0、7.0、8.0、9.0、10.0 と互換性があります。 エージェントは[、現在 Microsoft によってサポートされている対象.NET ランタイムを対象と](https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core)するインストゥルメントされたアプリケーションの場合にのみ完全にサポートされます。 エージェントは、以下にリストされている EOL されたランタイムでも動作する可能性がありますが、EOL されたランタイムではエージェントの新しいバージョンはテストされません。 @@ -271,7 +271,7 @@ New Relicの .NET エージェントは、.NET フレームワークと .NET Cor - The .NET agent is compatible with applications targeting .NET Core 3.1, and .NET 5.0, 6.0, 7.0, 8.0, 9.0, and 10.0. You can find the target framework in your `.csproj` file. Agent compatibility varies across different versions of .NET Core. + .NET エージェントは、.NET Core 3.1、.NET 5.0、6.0、7.0、8.0、9.0、10.0 を対象とするアプリケーションと互換性があります。ターゲット フレームワークは`.csproj`ファイルにあります。エージェントの互換性は、.NET Core のバージョンによって異なります。 互換： @@ -319,8 +319,8 @@ New Relicの .NET エージェントは、.NET フレームワークと .NET Cor .NET Coreエージェントは、以下のアプリケーションを自動的にインストゥルメントします。 - * ASP.NET Core MVC 2.0, 2.1, 2.2, 3.0, 3.1, 5.0, 6.0, 7.0, 8.0, 9.0, and 10.0 (includes Web API) - * ASP.NET Core Razor Pages 6.0, 7.0, 8.0, 9.0, and 10.0 (starting with .NET agent version 10.19.0) + * ASP..NET Core MVC 2.0、2.1、2.2、3.0、3.1、5.0、6.0、7.0、8.0、9.0、および 10.0 (Web APIを含む) + * ASP..NET Core Razor Pages 6.0、7.0、8.0、9.0、および 10.0 (.NET エージェント バージョン 10.19.0 以降) @@ -357,7 +357,7 @@ New Relicの .NET エージェントは、.NET フレームワークと .NET Cor .NETエージェント`v9.2.0`以降では、[Microsoft.Azure.Cosmos](https://www.nuget.org/packages/Microsoft.Azure.Cosmos)ライブラリを自動的にインストゥルメントします。 * サポートされている最小バージョン：3.17.0 - * Latest verified compatible version: 3.56.0 + * 最新の検証済み互換バージョン: 3.56.0 * バージョン 3.35.0 以降は、.NET エージェント v10.32.0 以降でサポートされます。 @@ -434,7 +434,7 @@ New Relicの .NET エージェントは、.NET フレームワークと .NET Cor [Npgsql](https://www.nuget.org/packages/Npgsql/)の使用 * サポートされている最小バージョン：4.0.0 - * Latest verified compatible version: 7.0.7 + * 最新の検証済み互換バージョン: 7.0.7 Npgsqlの旧バージョンもインストゥルメントできますが、重複および/または不足メトリクスが発生する場合があります。 @@ -452,7 +452,7 @@ New Relicの .NET エージェントは、.NET フレームワークと .NET Cor サポートされている最小バージョン：2.3.0 - Latest verified compatible version: 3.5.2 + 最新の検証済み互換バージョン: 3.5.2 バージョン 3.0.0.NET エージェント v10.40.0 以降では、バージョン 10.40.0 以降がサポートされます。 @@ -570,7 +570,7 @@ New Relicの .NET エージェントは、.NET フレームワークと .NET Cor * サポートされる最小バージョン: 3.5.0 - * Latest verified compatible version: 4.0.10.1 + * 最新の検証済み互換バージョン: 4.0.10.1 * 必要なエージェントの最小バージョン: 10.33.0 @@ -907,7 +907,7 @@ New Relicの .NET エージェントは、.NET フレームワークと .NET Cor * サポートされている最小バージョン：3.5.2 - * Latest verified compatible version: 7.1.2 + * 最新の検証済み互換バージョン: 7.1.2 @@ -921,7 +921,7 @@ New Relicの .NET エージェントは、.NET フレームワークと .NET Cor * サポートされている最小バージョン：7.1.0 - * Latest verified compatible version: 8.5.7 + * 最新の検証済み互換バージョン: 8.5.7 @@ -949,7 +949,7 @@ New Relicの .NET エージェントは、.NET フレームワークと .NET Cor * サポートされる最小バージョン: 3.7.0 - * Latest verified compatible version: 4.0.7.6 + * 最新の検証済み互換バージョン: 4.0.7.6 @@ -963,7 +963,7 @@ New Relicの .NET エージェントは、.NET フレームワークと .NET Cor * サポートされる最小バージョン: 3.7.0 - * Latest verified compatible version: 4.0.3.5 + * 最新の検証済み互換バージョン: 4.0.3.5 @@ -1343,7 +1343,7 @@ New Relicの .NET エージェントは、.NET フレームワークと .NET Cor .NETエージェント`v9.2.0`以降では、[Microsoft.Azure.Cosmos](https://www.nuget.org/packages/Microsoft.Azure.Cosmos)ライブラリを自動的にインストゥルメントします。 * サポートされている最小バージョン：3.17.0 - * Latest verified compatible version: 3.56.0 + * 最新の検証済み互換バージョン: 3.56.0 * バージョン 3.35.0 以降は、.NET エージェント v10.32.0 以降でサポートされます。 @@ -1461,7 +1461,7 @@ New Relicの .NET エージェントは、.NET フレームワークと .NET Cor サポートされている最小バージョン：2.3.0 - Latest verified compatible version: 3.5.2 + 最新の検証済み互換バージョン: 3.5.2 バージョン 3.0.0.NET エージェント v10.40.0 以降では、バージョン 10.40.0 以降がサポートされます。 @@ -1531,7 +1531,7 @@ New Relicの .NET エージェントは、.NET フレームワークと .NET Cor [Npgsql](https://www.nuget.org/packages/Npgsql/)の使用 * サポートされている最小バージョン：4.0.0 - * Latest verified compatible version: 7.0.7 + * 最新の検証済み互換バージョン: 7.0.7 Npgsqlの旧バージョンもインストゥルメントできますが、重複および/または不足メトリクスが発生する場合があります。 @@ -1629,7 +1629,7 @@ New Relicの .NET エージェントは、.NET フレームワークと .NET Cor * サポートされる最小バージョン: 3.5.0 - * Latest verified compatible version: 4.0.10.1 + * 最新の検証済み互換バージョン: 4.0.10.1 * 必要なエージェントの最小バージョン: 10.33.0 @@ -1710,7 +1710,7 @@ New Relicの .NET エージェントは、.NET フレームワークと .NET Cor サポートされている最小バージョン：105.2.3 - Latest verified compatible version: 113.0.0 + 最新の検証済み互換バージョン: 113.0.0 互換性のない既知のバージョン：106.8.0、106.9.0、106.10.0、106.10.1 @@ -2012,7 +2012,7 @@ New Relicの .NET エージェントは、.NET フレームワークと .NET Cor * サポートされている最小バージョン：3.5.2 - * Latest verified compatible version: 6.8.1 + * 最新の検証済み互換バージョン: 6.8.1 @@ -2026,7 +2026,7 @@ New Relicの .NET エージェントは、.NET フレームワークと .NET Cor * サポートされている最小バージョン：7.1.0 - * Latest verified compatible version: 8.5.7 + * 最新の検証済み互換バージョン: 8.5.7 @@ -2054,7 +2054,7 @@ New Relicの .NET エージェントは、.NET フレームワークと .NET Cor * サポートされる最小バージョン: 3.7.0 - * Latest verified compatible version: 4.0.7.6 + * 最新の検証済み互換バージョン: 4.0.7.6 @@ -2068,7 +2068,7 @@ New Relicの .NET エージェントは、.NET フレームワークと .NET Cor * サポートされる最小バージョン: 3.7.0 - * Latest verified compatible version: 4.0.3.5 + * 最新の検証済み互換バージョン: 4.0.3.5 diff --git a/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-11-28-2025.mdx b/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-11-28-2025.mdx new file mode 100644 index 00000000000..9bc03cc538d --- /dev/null +++ b/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-11-28-2025.mdx @@ -0,0 +1,72 @@ +--- +subject: Docs +releaseDate: '2025-11-28' +version: 'November 24 - November 28, 2025' +translationType: machine +--- + +### 新しいドキュメント + +* [Laravelの PHP エージェントサポート](/docs/apm/agents/php-agent/frameworks-libraries/laravel)を追加して、 Laravelウェブサイト、 Laravel Queue Workers、およびLaravel Horizon Workers に対する包括的なガイダンスを提供します。 +* New Relic PHPエージェントとのPHPUnit 11 以降の互換性問題に関する[メモリトラブルシューティング ガイドに、 PHPUnit実行が](/docs/apm/agents/php-agent/troubleshooting/phpunit-incompatibility)追加されました。 + +### 主な変更点 + +* [ユーザー管理の概念](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts)と関連する RBAC ドキュメントが更新され、新しい付与およびロール作成エクスペリエンスが導入され、 **Roles**タブに統合された 3 つのロール タイプ (組織ベースのロール、アカウント ベースのロール、エンティティ ベースのロール) が導入されました。 +* Microsoft Teams 統合APIメソッドと例を含む[一連のチャネル](/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-channels)を更新しました。 +* Microsoft Teams 統合サポートにより、[一連の宛先](/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-destinations)が更新されました。 + +### マイナーチェンジ + +* [New Relic の価格設定と課金](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing)が更新され、提供される価格設定モデルと機能が明確になりました。 +* [.NETエージェント設定](/docs/apm/agents/net-agent/configuration/net-agent-configuration)とブラウザ計装設定オプションを更新しました。 +* 簡素化された設定ガイダンスを備えた[.NET エージェントを使用したブラウザ監視](/docs/apm/agents/net-agent/other-features/browser-monitoring-net-agent)を更新しました。 +* [PHP エージェントの互換性要件が](/docs/apm/agents/php-agent/getting-started/php-agent-compatibility-requirements)Laravel Horizon サポートに更新され、Windows 32 ビット サポートが削除されました。 +* 設定ガイダンスが更新され、 [OpenTelemetryコレクターの処理が](/docs/opentelemetry/get-started/collector-processing/opentelemetry-collector-processing-intro)更新されました。 +* デュアルスタック エンドポイント パーマリンクを修正して[ネットワーク設定を](/docs/new-relic-solutions/get-started/networks)更新しました。 +* コンプライアンス情報を更新し、 [TISAX コンプライアンス](/docs/security/security-privacy/compliance/certificates-standards-regulations/tisax)を更新しました。 + +### リリースノート + +* [プレインサイト APM レガシー埋め込みチャートのサポート終了日を 2026 年 6 月 30 日と発表しました。](/eol/2025/11/pre-insights/) + +* 弊社の最新リリース情報を常に把握してください: + + * [Kubernetesインテグレーション v3.50.2](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-50-2) : + + * newrelic-インフラストラクチャ-3.55.2 および nri-bundle-6.0.26 に含まれる統合を更新しました。 + + * [ログ 251120](/docs/release-notes/logs-release-notes/logs-25-11-20) : + + * AWS-log-ingestion ラムダの CVE-2025-53643 を修正しました。 + * aiohttpライブラリを3.13.2に更新しました そして詩のバージョンを 1.8.3 にしました。 + + * [React Nativeエージェント v1.5.12](/docs/release-notes/mobile-release-notes/react-native-release-notes/react-native-agent-1512) : + + * ネイティブ Android エージェントをバージョン 7.6.13 に更新しました。 + * ネイティブ iOS エージェントをバージョン 7.6.0 に更新しました。 + + * [Capacitor v1.5.12](/docs/release-notes/mobile-release-notes/capacitor-release-notes/capacitor-agent-1512) : + + * ネイティブ Android エージェントをバージョン 7.6.13 に更新しました。 + * ネイティブ iOS エージェントをバージョン 7.6.0 に更新しました。 + + * [Flutter v1.1.19](/docs/release-notes/mobile-release-notes/flutter-release-notes/flutter-agent-1119) : + + * ネイティブ Android エージェントをバージョン 7.6.13 に更新しました。 + * ネイティブ iOS エージェントをバージョン 7.6.0 に更新しました。 + + * [Unity エージェント v1.4.11](/docs/release-notes/mobile-release-notes/unity-release-notes/unity-agent-1411) : + + * ネイティブ Android エージェントをバージョン 7.6.13 に更新しました。 + * ネイティブ iOS エージェントをバージョン 7.6.0 に更新しました。 + + * [Cordovaエージェント v7.0.11](/docs/release-notes/mobile-release-notes/cordova-release-notes/cordova-agent-711) : + + * ネイティブ Android エージェントをバージョン 7.6.13 に更新しました。 + * ネイティブ iOS エージェントをバージョン 7.6.0 に更新しました。 + + * [.NET MAUI エージェント v1.1.14](/docs/release-notes/mobile-release-notes/net-maui-release-notes/net-maui-agent-1114) : + + * ネイティブ Android エージェントをバージョン 7.6.13 に更新しました。 + * ネイティブ iOS エージェントをバージョン 7.6.0 に更新しました。 \ No newline at end of file diff --git a/src/i18n/content/jp/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/compatibility-requirement-lambda-monitoring.mdx b/src/i18n/content/jp/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/compatibility-requirement-lambda-monitoring.mdx index f2db650b4d8..0a648fc65d8 100644 --- a/src/i18n/content/jp/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/compatibility-requirement-lambda-monitoring.mdx +++ b/src/i18n/content/jp/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/compatibility-requirement-lambda-monitoring.mdx @@ -11,13 +11,17 @@ translationType: machine Lambda レイヤーを使用してサーバーレス監視を有効にする前に、次のものが必要です。 -1. [管理者ロール](/docs/accounts/original-accounts-billing/original-users-roles/users-roles-original-user-model/#roles)または**インフラストラクチャ マネージャー**[アドオン ロール](/docs/accounts/original-accounts-billing/original-users-roles/users-roles-original-user-model#add-on)を持つ New Relic アカウント。 +* [管理者ロール](/docs/accounts/accounts-billing/new-relic-one-user-management/introduction-managing-users)を持つか、**Infrastructure manager** \[インフラストラクチャ マネージャー] [アドオン ロール](/docs/accounts/original-accounts-billing/original-users-roles/users-roles-original-user-model#add-on)を持つ New Relic アカウント。 -2. 。 +* 。 -3. IAMリソース、マネージドシークレット、Lambdasを作成するパーミッションを持つAWSアカウント。また、CloudFormationスタックやS3バケットを作成するための権限も必要です。 +* IAMリソース、マネージドシークレット、Lambdasを作成するパーミッションを持つAWSアカウント。また、CloudFormationスタックやS3バケットを作成するための権限も必要です。 -## サポートされているランタイム + + New Relic [、 AWS](/docs/infrastructure/amazon-integrations/get-started/introduction-aws-integrations/)インテグレーションを使用してAWSアカウントをNew Relicに統合し、 Lambda関数を自動的に検出して監視することをお勧めします。 これにより、サーバーレス機能に New Relic APM の全機能を活用できるようになります。 + + +## サポートされているランタイム [#supported-runtimes] インストゥルメンテーションのタイプに基づいて、次のランタイムがサポートされます。 @@ -58,8 +62,18 @@ Lambda レイヤーを使用してサーバーレス監視を有効にする前 * Java : New Relic Javaの階層化および SDK インストゥルメンテーションは、`com.amazonaws:aws-lambda-java-events` バージョン `3.0.0` から最新のものまで互換性があります。 -## 次のステップ +## 関連記事 [#related-docs] - Lambda関数のインストゥルメンテーションと設定を始めましょう。 New Relic を使用してAWS Lambda関数を監視する方法を学びます。 + + New Relicの階層化アプローチを使用してLambda関数を計装します。 + + + + SDK を使用してLambda関数を計装します。 + + + + New Relicのコンテナ化アプローチを使用してLambda関数を計装します。 + \ No newline at end of file diff --git a/src/i18n/content/jp/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/containerized-images.mdx b/src/i18n/content/jp/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/containerized-images.mdx index 6633308511b..bb8afdeddda 100644 --- a/src/i18n/content/jp/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/containerized-images.mdx +++ b/src/i18n/content/jp/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/containerized-images.mdx @@ -202,10 +202,34 @@ Lambda関数のコンテナ化されたイメージを使用していて、ア * [階層化されたインストゥルメンテーション](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/instrument-your-own/#console) * [SDKベースのインストゥルメンテーション](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/enable-serverless-monitoring-aws-lambda-layerless) + + + ### データを見つけて使用する [#find-data] + + AWS Lambda 関数をセットアップしたら、 New Relic APMインターフェースでデータを検索して使用できるようになります。 データはいくつかの主要な領域に編成されており、それぞれがLambda関数のパフォーマンスと状態に異なるインサイトを提供します。 + + APMインターフェイスでは、 [ディストリビューティッド（分散）ト](https://docs.newrelic.com/docs/distributed-tracing/concepts/introduction-distributed-tracing/)レーシング、 [サービス マップ](https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/ui-data/service-maps/service-maps/)、 [トランザクション](https://docs.newrelic.com/docs/apm/transactions/intro-transactions/transactions-new-relic-apm//)、[エラー分析](https://docs.newrelic.com/docs/errors-inbox/getting-started/)など、 Lambda関数のさまざまな側面を探索できます。 これらの各領域では、 Lambda関数のパフォーマンス、レイテンシ、エラー率に関する詳細なインサイトが提供され、問題を迅速に特定して解決できるようになります。 + + + 呼び出しエクスペリエンスは、 APM対話トレースと統合されました。 これにより、特定の`AWS RequestId`を使用してAPMマッカーサー トレースにドリルダウンし、特定のLambda実行に関する詳細情報を得ることができます。 + + + New Relic APMインターフェースでLambda関数を表示するには: + + 1. [https://one.newrelic.com](https://one.newrelic.com) > APM & Servicesに移動します。 + 2. 検索条件を`isLambdaFunction = true`に設定します。 + 3. 表示されたリストから、 Lambda関数を選択してデータを表示します。 + -## 次のステップ +## 関連記事 [#related-docs] - サポートされているランタイムと前提条件について詳しく学ぶNew Relic を使用してAWS Lambda 関数を監視する方法について学ぶ インストレーション関連の問題のトラブルシューティング方法を学ぶ + + サポートされているランタイムと前提条件の詳細 + + + + インストール関連の問題のトラブルシューティング方法を学ぶ + \ No newline at end of file diff --git a/src/i18n/content/jp/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda.mdx b/src/i18n/content/jp/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda.mdx index 10028f60383..560e5f6c2ae 100644 --- a/src/i18n/content/jp/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda.mdx +++ b/src/i18n/content/jp/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda.mdx @@ -46,7 +46,7 @@ translationType: machine - 関数の実際のハンドラを見つけるために使用するハンドララッパーを指定します + 関数の実際のハンドラーを検索するために使用されるハンドラー ラッパーを指定します。Go ランタイムの場合、この変数は必須ではありません。 @@ -60,6 +60,20 @@ translationType: machine + + + `NEW_RELIC_APM_LAMBDA_MODE` + + + + Lambda関数のAPM監視を有効にするには、 + + `true` + + に設定します。 + + + `NEW_RELIC_TRUSTED_ACCOUNT_KEY` @@ -1079,9 +1093,25 @@ translationType: machine `INFO` - , + 、 `DEBUG` + + 、 + + `TRACE` + + 、 + + `ERROR` + + 、 + + `WARN` + + 、 + + `ALL` @@ -1193,7 +1223,9 @@ translationType: machine - 文字列内でコンマ区切りの値として指定することで、チェックをバイパスします。 + **非推奨** + + 文字列内にコンマ区切りの値として指定することでチェックをバイパスします。 `handler` @@ -1227,7 +1259,17 @@ translationType: machine - ライセンスキーが含まれている AWS Secrets Manager のシークレットキーの名前を指定します。注: これは、NEW_RELIC_LICENSE_KEY が設定されていない場合にのみ使用されます。 + New Relic ライセンスキーが含まれている AWS Secrets Manager のシークレットの**名前**または**ARN**を指定します。 + +
+ +
+ + **メモ：** + + * これは、 `` `NEW_RELIC_LICENSE_KEY` ``が設定されていない場合にのみ使用されます。 + * シークレットは、 Lambda関数と同じAWSリージョンに存在する必要があります。 + * Lambda関数の実行ロールには、このシークレットに対する`` `secretsmanager:GetSecretValue` ``権限が必要です。 @@ -1241,7 +1283,31 @@ translationType: machine - ライセンスキーを含むAWS Systems Manager 権利ストアから SSM 権利名を指定します。 注: これはNEW_RIC_LICENSE_KEYが設定されていない場合にのみ使用されます + New Relicライセンスキーを含むAWS Systems Manager 権利ストアからの**名前**または**ARN** を指定します。 + +
+ +
+ + **メモ：** + + * これは、 `` `NEW_RELIC_LICENSE_KEY` ``が設定されていない場合にのみ使用されます。 + * SSM はLambda関数と同じAWSリージョンに存在する必要があります。 + * Lambda関数の実行ロールには、このに対する`` `ssm:GetParameter` ``権限が必要です。 + + + + + + `NEW_RELIC_CLOUD_AWS_ACCOUNT_ID` + + + + + + + + New Relicモニター エンティティ間の関係を正しくマッピングして表示できるようにするには、データベースやLambda関数などのモニター リソースが存在するAWSアカウント ID を指定します。 diff --git a/src/i18n/content/jp/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own.mdx b/src/i18n/content/jp/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own.mdx index 7793f79d134..b2bc8b46077 100644 --- a/src/i18n/content/jp/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own.mdx +++ b/src/i18n/content/jp/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own.mdx @@ -5,14 +5,13 @@ freshnessValidatedDate: never translationType: machine --- -New Relic アカウントとAWSアカウントを正常にリンクしたら、New Relic Lambdaレイヤーを追加してLambda関数を実装できます。 これにより、New Relic エージェントが統合され、関数が呼び出されるたびに自動監視が可能になります。 +New Relic Lambdaレイヤーを追加することで、 Lambda関数を計装できます。 これにより、New Relic エージェントが統合され、関数が呼び出されるたびに自動監視が可能になります。 a diagram depicting non-containerized lambda function instrumentation -## あなたが始める前に [#begin] - -* [New RelicとAWSアカウントをリンクする](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda#link) -* [さまざまなインストゥルメンテーション方法を確認する](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda#method) + + New Relic [、 AWS](/docs/infrastructure/amazon-integrations/get-started/introduction-aws-integrations/)インテグレーションを使用してAWSアカウントをNew Relicに統合し、 Lambda関数を自動的に検出して監視することをお勧めします。 これにより、サーバーレス機能に New Relic APM の全機能を活用できるようになります。 + ## インストゥルメンテーション方法 [#instrumentation] @@ -36,7 +35,7 @@ New Relic包括的な監視のためにAWS Lambda 関数をプランニングす New Relicインストゥルメンテーション レイヤーをインストールまたはアップグレードするには、次のコマンドを実行します。 ```shell - newrelic-lambda layers install --nr-account-id YOUR_NR_ACCOUNT_ID --function my-function --upgrade + newrelic-lambda layers install --nr-account-id YOUR_NR_ACCOUNT_ID --function my-function --upgrade --apm ``` このコマンドは、Lambdaのリージョンとランタイムに合わせて、利用可能な最新のレイヤーを自動的に見つけます。 @@ -51,112 +50,154 @@ New Relic包括的な監視のためにAWS Lambda 関数をプランニングす CloudFormation は、 AWSリソースのプロビジョニングと管理を簡素化するAWSサービスです。 YAML または JSON テンプレートでリソースの望ましい状態を定義することにより、CloudFormation は基盤となるAPIコールを自動的に処理し、必要に応じてリソースを作成、更新、または削除します。 この宣言型アプローチにより、インフラストラクチャ管理が自動化され、一貫性と再現性が確保されます。 - Node.jsLambda関数の単純なCloudFormationテンプレートの例を次に示します。 - - ```yaml - AWSTemplateFormatVersion: '2010-09-09' - Transform: AWS::Serverless-2016-10-31 - Description: And example of a simple instrumented Node.js Lambda - - Resources: - NewRelicExample: - Type: AWS::Serverless::Function - Properties: - # In this example, we're using the SAM CLI to package and deploy our lambda. SAM will transform this value during the publish step. - CodeUri: newrelic-example-node/ - # The handler for your function needs to be the one provided by the instrumentation layer, below. - Handler: newrelic-lambda-wrapper.handler - Runtime: nodejs12.x - Environment: - Variables: - # For the instrumentation handler to invoke your real handler, we need this value - NEW_RELIC_LAMBDA_HANDLER: YOUR_PATH_TO_INITIAL_LAMBDA_HANDLER - # Distributed tracing needs your account ID, and your trusted account ID - NEW_RELIC_ACCOUNT_ID: YOUR_ACCOUNT_ID_HERE - # If your New Relic account has a parent account, this value should be that account ID. Otherwise, just - # your account id. - NEW_RELIC_TRUSTED_ACCOUNT_KEY: YOUR_PARENT_ACCOUNT_ID_HERE - Layers: - # This layer includes the New Relic Lambda extension, a sidecar process that sends telemetry, - # as well as the New Relic agent for Node.js, and a handler wrapper that makes integration easy. - - !Sub arn:${AWS::Partition}:lambda:${AWS::Region}:451483290750:layer:NewRelicNodeJS12X:34 - Policies: - # This policy allows the lambda to know the value of the New Relic license key. We need this so - # that we can send telemetry back to New Relic - - AWSSecretsManagerGetSecretValuePolicy: - SecretArn: !ImportValue NewRelicLicenseKeySecret-NewRelic-LicenseKeySecretARN - ``` - - 通常、関数とそのリソースを記述する`template.yaml`という名前のファイルがあります。 + New RelicでLambda関数を監視するには: + + 1. [New Relic Lambda レイヤー](https://layers.newrelic-external.com/)をインストールします。以下は、 Node.js Lambda関数の単純な CloudFormation テンプレートの例です。 + + ```yaml + AWSTemplateFormatVersion: '2010-09-09' + Transform: AWS::Serverless-2016-10-31 + Description: And example of a simple instrumented Node.js Lambda + + Resources: + NewRelicExample: + Type: AWS::Serverless::Function + Properties: + # In this example, we're using the SAM CLI to package and deploy our lambda. SAM will transform this value during the publish step. + CodeUri: newrelic-example-node/ + # The handler for your function needs to be the one provided by the instrumentation layer, below. + Handler: newrelic-lambda-wrapper.handler + Runtime: nodejs22.x + Environment: + Variables: + # For the instrumentation handler to invoke your real handler, we need this value + NEW_RELIC_LAMBDA_HANDLER: YOUR_PATH_TO_INITIAL_LAMBDA_HANDLER + # Distributed tracing needs your account ID, and your trusted account ID + NEW_RELIC_ACCOUNT_ID: YOUR_ACCOUNT_ID_HERE + # If your New Relic account has a parent account, this value should be that account ID. Otherwise, just + # your account id. + NEW_RELIC_TRUSTED_ACCOUNT_KEY: YOUR_PARENT_ACCOUNT_ID_HERE + NEW_RELIC_APM_LAMBDA_MODE: 'true' + Tags: + # This tag is to enable APM mode. + NR.Apm.Lambda.Mode: true + Layers: + # This layer includes the New Relic Lambda extension, a sidecar process that sends telemetry, + # as well as the New Relic agent for Node.js, and a handler wrapper that makes integration easy. + - !Sub arn:${AWS::Partition}:lambda:${AWS::Region}:451483290750:layer:NewRelicNodeJS16X:103 + Policies: + # This policy allows the lambda to know the value of the New Relic license key. We need this so + # that we can send telemetry back to New Relic + - AWSSecretsManagerGetSecretValuePolicy: + SecretArn: !ImportValue NewRelicLicenseKeySecret-NewRelic-LicenseKeySecretARN + ``` + + 通常、関数とそのリソースを記述する`template.yaml`という名前のファイルがあります。 + + 2. 必要な[環境変数](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda)を設定します。 + + 3. 更新された設定を使用してLambda関数をデプロイします。 Serverless フレームワークは、サーバーレス アプリケーション向けの人気のある開発およびデプロイメント ツールです。 これは AWS 向けに Node.js で記述されており、主に CloudFormation テンプレート上の高レベルの抽象化として機能します。 Node、Python、Ruby、Java、.NET 関数に適しています。 - New Relic では、Serverless Framework アプリケーションのインスツルメンテーションを簡素化するために、 [Serverless Framework Plugin](https://github.com/newrelic/serverless-newrelic-lambda-layers) を提供しています。 + New RelicサーバーServerlessワーク アプリケーションの計装を簡素化する[Serverlessフレームワーク プラグイン](https://github.com/newrelic/serverless-newrelic-lambda-layers)を提供します。 + + **前提条件:** + + * Serverlessフレームワークを利用した既存のアプリケーション。 + * [New Relic アカウント ID](/docs/accounts/accounts-billing/account-structure/account-id) + * [New RelicパーソナルAPIキー](/docs/apis/intro-apis/new-relic-api-keys) + + **New Relicを使用してServerlessフレームワーク アプリケーションをインストールして設定するには:** - プラグインをインストールするには、次のコマンドを実行します。 + 1. `npm`を使用する場合は、次のコマンドを実行します。 ```bash - npm install --save-dev serverless-newrelic-lambda-layers + npm install --save-dev serverless-newrelic-lambda-layers ``` - または、代わりに次のコマンドを実行することもできます。 + または、 `yarn`を使用する場合は、次のコマンドを実行します。 ```bash - yarn add --dev serverless-newrelic-lambda-layers + yarn add --dev serverless-newrelic-lambda-layers ``` - 次に、 [New RelicアカウントID](/docs/accounts/install-new-relic/account-setup/account-id)と[New Relic個人APIキー](/docs/apis/get-started/intro-apis/types-new-relic-api-keys#personal-api-key)を見つけます。 + 2. `serverless.yaml`ファイルを開き、次の設定を追加します。 - 次に、 `serverless.yaml`ファイルに次のコードを追加します。 + 1. `serverless-newrelic-lambda-layers` `plugins`リストに追加します。 - ```yaml - plugins: - - serverless-newrelic-lambda-layers - custom: - newRelic: - accountId: your-new-relic-account-id-here - apiKey: your-new-relic-personal-api-key-here - linkedAccount: your-new-relic-integration-account-name-here - ``` + 2. カスタム セクションに次のNew Relic設定を追加します。 + + ```yaml + plugins: + - serverless-newrelic-lambda-layers + custom: + newRelic: + accountId: your-new-relic-account-id-here + apiKey: your-new-relic-personal-api-key-here + linkedAccount: your-new-relic-integration-account-name-here + apm: true + ``` + + 3. プロバイダー セクションに次の`NR.Apm.Lambda.Mode: true`タグを追加します。 + + ```yaml + provider: + tags: + NR.Apm.Lambda.Mode: true + ``` + + 3. 必要な[環境変数](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda)を設定します。 + + 4. 更新された設定を使用してLambda関数をデプロイします。 AWSクラウド開発キット ( AWS CDK) は、クラウド リソースをコードで定義し、 AWS CloudFormation を通じてプロビジョニングするためのフレームワークです。 - 以下は、 New Relicインストゥルメントで行われた Node.js Lambda関数をデプロイする基本的な CDK アプリの例です。 - - ```ts - import * as cdk from 'aws-cdk-lib'; - import { Construct } from 'constructs'; - import * as lambda from 'aws-cdk-lib/aws-lambda'; - - export class NewRelicExampleCdkStack extends cdk.Stack { - constructor(scope: Construct, id: string, props?: cdk.StackProps) { - super(scope, id, props); - // Add latest New Relic Lambda layer ARN from https://layers.newrelic-external.com - const NewReliclayerArn = 'arn:aws:lambda:us-east-1:451483290750:layer:NewRelicNodeJS20X:39'; - const myFunction = new lambda.Function(this, "NewRelicExampleLambda", { - runtime: lambda.Runtime.NODEJS_20_X, - // Update functions handler to point to the New Relic Lambda wrapper - handler: "newrelic-lambda-wrapper.handler", - code: lambda.Code.fromAsset('lib/lambda-runtime-code'), - layers: [lambda.LayerVersion.fromLayerVersionArn(this, 'NewRelicLayer', NewReliclayerArn)], - environment: { - // Set the NEW_RELIC_LAMBDA_HANDLER environment variable to the path of your initial handler. - NEW_RELIC_LAMBDA_HANDLER: 'index.handler', - }, - }); - } - } - ``` + AWS CDK で New Relic を使用するには、次の手順に従います。 + + 1. [New Relic Lambda レイヤー](https://layers.newrelic-external.com/)をインストールします。以下は、 New Relicインストゥルメントと言われたNode.js Lambda関数をデプロイする基本的な CDK アプリの例です。 + + ```ts + import * as cdk from 'aws-cdk-lib'; + import { Construct } from 'constructs'; + import * as lambda from 'aws-cdk-lib/aws-lambda'; + + export class NewRelicExampleCdkStack extends cdk.Stack { + constructor(scope: Construct, id: string, props?: cdk.StackProps) { + super(scope, id, props); + // Add latest New Relic Lambda layer ARN from https://layers.newrelic-external.com + const NewReliclayerArn = 'arn:aws:lambda:us-east-1:451483290750:layer:NewRelicNodeJS22X:38'; + const myFunction = new lambda.Function(this, "NewRelicExampleLambda", { + runtime: lambda.Runtime.NODEJS_20_X, + // Update functions handler to point to the New Relic Lambda wrapper + handler: "newrelic-lambda-wrapper.handler", + code: lambda.Code.fromAsset('lib/lambda-runtime-code'), + layers: [lambda.LayerVersion.fromLayerVersionArn(this, 'NewRelicLayer', NewReliclayerArn)], + environment: { + // Set the NEW_RELIC_LAMBDA_HANDLER environment variable to the path of your initial handler. + NEW_RELIC_LAMBDA_HANDLER: 'index.handler', + NEW_RELIC_APM_LAMBDA_MODE: 'true' + }, + }); + // Add the New Relic APM Lambda Mode tag + cdk.Tags.of(myFunction).add('NR.Apm.Lambda.Mode', 'true'); + } + } + ``` + + 2. 必要な[環境変数](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda)を設定します。 + + 3. 更新された設定を使用してLambda関数をデプロイします。 Terraform は、コード ツールとしての一般的なインフラストラクチャとして人気の高いツールです。 AWS リソースの管理に使用できます。 Terraform スクリプトを使用して インストゥルメントされた Lambda 関数のデプロイの [例をいくつか](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/terraform) 紹介します。New Relic - [New Relic Terraform プロバイダーを](https://registry.terraform.io/providers/newrelic/newrelic/latest/docs/resources/cloud_aws_integrations)使用して、 AWSインテグレーションをセットアップできます。 + [New Relic Terraform プロバイダーを](https://registry.terraform.io/providers/newrelic/newrelic/latest/docs/resources/cloud_aws_integrations)使用して、 AWSインテグレーションをセットアップできます。 プロバイダーをセットアップしたら、必要な[環境変数](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda)を設定し、 Lambda関数に`NR.Apm.Lambda.Mode: true`タグを追加します。 @@ -210,6 +251,10 @@ New Relic包括的な監視のためにAWS Lambda 関数をプランニングす New Relicレイヤーは、 New Relic Rubyエージェントを自動的に配信し、Lambda 関数の呼び出し前にRuby `require` を介してロードされます。 競合を避けるため、Ruby エージェントのコピーを他の場所に含めないでください。 エージェントの存在を活用するために、関数内で必要なNew Relic RubyエージェントAPI呼び出しを自由に実行してください。 + 14. AWSマネジメント コンソールの Configuration \[設定] タブで、 Lambda関数に`NR.Apm.Lambda.Mode: true`タグを追加します。 + + 15. 更新された設定を使用してLambda関数をデプロイします。 + Java、Python、Node.js、および .Net ランタイムは、 Rubyと同じインストゥルメンテーション フローに従いますが、ハンドラーがいくつか異なります。 関数のコンソールで新しくアタッチされたレイヤーを指すように関数のハンドラーを更新する方法は次のとおりです。 * Javaです。 @@ -230,26 +275,32 @@ New Relic包括的な監視のためにAWS Lambda 関数をプランニングす -## 輸送方法 +## データを見つけて使用する [#find-data] - - - 各エージェント レイヤーには、CloudWatch をバイパスしてログとペイロードを New Relic に送信するための拡張機能も含まれています。 これにより、レイテンシとコストを削減できます。 ただし、関数のパフォーマンスと信頼性に影響を及ぼすリスクがあります。 +AWS Lambda 関数をセットアップしたら、 New Relic APMインターフェースでデータを検索して使用できるようになります。 データはいくつかの主要な領域に編成されており、それぞれがLambda関数のパフォーマンスと状態に異なるインサイトを提供します。 - New Relic Lambda レイヤーを追加すると、拡張機能が有効になり、ログ配布はデフォルトで無効になります。 +APMインターフェイスでは、[ディストリビューティッド（分散）ト](/docs/distributed-tracing/concepts/introduction-distributed-tracing/)レーシング、[サービス マップ](/docs/new-relic-solutions/new-relic-one/ui-data/service-maps/service-maps/)、[トランザクション](/docs/apm/transactions/intro-transactions/transactions-new-relic-apm/)、[エラー分析](/docs/errors-inbox/getting-started/)など、 Lambda関数のさまざまな側面を探索できます。 これらの各エリアでは、 Lambda関数のパフォーマンス、レイテンシ、エラー率に関する詳細なインサイトが提供され、問題を迅速に特定して解決できるようになります。 - New Relic で関数ログを表示する場合は、環境変数を使用して関数ログの拡張機能の送信を有効にする必要があります。 + + 呼び出しエクスペリエンスは、 APM対話トレースと統合されました。 これにより、特定の`AWS RequestId`を使用してAPMマッカーサー トレースにドリルダウンし、特定のLambda実行に関する詳細情報を得ることができます。 + - 関数ログは、関数の呼び出し中に関数によって記録されたログにすぎないことに注意することが重要です。 拡張機能は、 `START` 、 `END` 、 `REPORT`行などの Lambda ランタイム ログを送信しません。 - +New Relic APMインターフェースでLambda関数を表示するには: - - データを CloudWatch のみに送信するか、フォールバックとして送信するかを選択できます。詳細については、 [CloudWatch フォールバックのドキュメント](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/cloud-watch-fallback)をご覧ください。 - - +1. [https://one.newrelic.com](https://one.newrelic.com) > APM & Servicesに移動します。 -## 次のステップ +2. 検索条件を`isLambdaFunction = true`に設定します。 + +3. 表示されたリストから、 Lambda関数を選択してデータを表示します。 + +## 関連記事 [#related-docs] - サポートされているランタイムと前提条件について詳しく学ぶNew Relic を使用してAWS Lambda 関数を監視する方法について学ぶ インストレーション関連の問題のトラブルシューティング方法を学ぶ + + サポートされているランタイムと前提条件の詳細 + + + + インストール関連の問題のトラブルシューティング方法を学ぶ + \ No newline at end of file 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 e907cac6df2..7293f174411 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 @@ -7,40 +7,155 @@ translationType: machine New Relic のAWS Lambda向けインストゥルメンテーションは、関数の内部動作を詳細に可視化します。 New Relic エージェントを関数に追加すると、各呼び出しが New Relic によって監視されます。 これにより、関数呼び出しの継続時間、エラーの監視、ソース イベントと関数の応答に関する詳細の記録が可能になります。 -new-relic-lambda-entities-screenshot.png +/\* AWS Lambda 、拡張性の高いイベント主導の計算サービスを提供し、サーバーのプロビジョニングや管理を必要とせずに、アプリケーションとバックエンド サービスを構築して実行できるようにします。 Lambda上のサーバーレスアーキテクチャーが洗練され、ビジネスクリティカルな役割を担うようになると、より広範なアプリケーションエコシステム内でそのパフォーマンス、運用の健全性、およびインターラクションに対する包括的な可視性を実現することが、信頼性と効率性を維持するために不可欠になります。 最新のアプリケーションは、他のさまざまなマイクロサービス、データベース、サードパーティ API と対話する多数のAWS Lambda関数に大きく依存しています。 このような複雑な環境では、観察に関するいくつかの課題に遭遇する可能性があります。 \* \*\*根本原因の特定が難しい:\*\* 断続的な速度低下などのパフォーマンスの問題が発生したり、 Lambda関数に関連する重要なトランザクションが失敗したりした場合、失敗している関数や問題の原因を正確に特定することは、複雑なパズルになる可能性があります。 \* \*\*サイロ化された監視ビュー:\*\* 専用サーバー レス監視UIと従来のアプリケーション パフォーマンス監視 ( APM ) ビューの間を行き来することになり、パフォーマンスの単一の統一された画像を取得することが困難になる場合があります。 \* \*\*非効率的なデータの関連付け:\*\* 情報が別々のサーバーレス システムとAPM監視システムに存在する場合、パフォーマンス データとイベントを効果的に関連付けることは困難になる可能性があります。 \* \*\*不完全なエンドツーエンドのトレース:\*\* 分散環境内のLambda関数やその他のサービスを通過する単一のリクエストをエンドツーエンドでシームレスにトレースする際に、課題に直面する可能性があります。 \* \*\* Lambdaの限定的な監視 :\*\* APMツールの完全な診断機能と使い慣れたワークフローをLambda関数に直接適用できないことがよくあります。 \* \*\*インサイトの手作業:\*\* Lambdaに関連する問題のコンテキスト全体を理解するには、さまざまなソースからのさまざまな情報をまとめるのに、かなりの手作業が必要になることがよくあります。 これらの観察可能性の課題に対処し、真に統合された監視エクスペリエンスを提供するために、 New Relic AWS Lambda関数を当社のプラットフォームに統合する方法を強化しています。 この取り組みにより、サーバーレス機能がNew Relic APMエクスペリエンスに直接組み込まれ、他のインストゥルメント サービスと並んでサーバーレス機能が第一級住民として扱われます。 私たちの目標は、 Lambda関数に豊富なアプリケーション対応テレメトリーを提供し、完全なコンテキストでパフォーマンスをこれまでより簡単に理解できるようにすることです。 \*/ -## Lambdaテレメトリーの配送方法 [#shipping-methods] +## 主な特徴 [#key-features] -テレメトリーデータをAWS Lambdaから New Relic に送信するには主に 3 つの方法があり、それぞれに独自のコストと信頼性に関する考慮事項があります。 +* **統合されたビューを取得します。**他のサービスに使用しているのと同じAPMインターフェイス内でLambda関数を監視します。 パフォーマンス メトリクス、トレース、ログ (構成時)、エラーなどのサーバーレス テレメトリーを表示し、すべて 1 か所で関連付けられるため、異なる UI を切り替える必要がなくなります。 -* **コスト効率の高い方法**: デフォルトで AWS CloudWatch へのデータ送信を回避する Lambda 拡張機能を含む New Relic のレイヤーを活用します。 -* **信頼性重視の方法**: New Relic Lambda拡張機能を無効にし、データの送信に CloudWatch のみを使用して、 Lambda関数のオーバーヘッドを削減します。 -* **ハイブリッド方式**: 拡張機能をフォールバックとして CloudWatch と組み合わせ、コスト効率と信頼性のバランスをとります。 +* **APMのパワーを最大限に活用:** New Relic APM機能の包括的なスイートをLambda関数に直接適用します。 これには、高度なディストリビューティッド（分散）トレーシング、Errors Inbox による詳細なエラー分析、 Lambda関数を組み込んだサービス マップ、迷ダッシュボードなどが含まれます。 詳細については、 [APM のドキュメント](https://docs.newrelic.com/docs/apm/new-relic-apm/getting-started/introduction-apm/)を参照してください。 -## コストの考慮 [#costs] +* **完全なエンドツーエンドのリクエスト トレースを実現します。**リクエストがフロントエンド サービスまたは他のマイクロサービスからAWS Lambda関数を介して接続されたコンポーネントに流れる際に、 requestsシームレスにトレースします。 これにより、アーキテクチャー全体にわたるリクエストのレイテンシと依存関係の明確で中断のない全体像が得られます。 詳細については、 [ディストリビューティッド（分散）トレーシングのドキュメント](https://docs.newrelic.com/docs/distributed-tracing/concepts/introduction-distributed-tracing/)を参照してください。 -AWS Lambda のサーバーレス監視を実装すると、追加の AWS 料金が発生する場合があります。New Relicにデータを報告する`newrelic-log-ingestion` Lambda関数はサードパーティのサービスとみなされ、関連するAWS料金はユーザーの責任となります。 +* **根本原因分析の簡素化:**サーバーレス データをAPMのアプリケーション テレメトリーの残りの部分と統合することにより、 Lambda関数内で発生したのか、アップストリーム/ダウンストリーム サービスで発生したのかに関係なく、問題を迅速に特定して診断できます。 -[New RelicLambda](https://github.com/newrelic/newrelic-lambda-layers) Layers にバンドルされている[ newrelic-lambda-extension](https://github.com/newrelic/newrelic-lambda-extension) を使用すると、CloudWatch および[ newrelic-log-ingestion](https://github.com/newrelic/aws-log-ingestion) 関数を介したログとテレメトリーの送信を回避できます。オブザーバビリティデータの高可用性を必要とする機能の[ CloudWatch](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/cloud-watch-fallback/) フォールバック メソッドとして newrelic-log-ingestion[ 関数を設定することもできます。](https://github.com/newrelic/aws-log-ingestion) +* **サーバーレスの影響をより深く理解する:** Lambda関数がアプリケーションおよび主要なビジネス トランザクションの全体的な健全性とパフォーマンスにどのように貢献しているかを明確に確認し、インサイトをデジタル サービス内での役割に深く反映します。 + +New Relic Lambda Entities in APM + +## AWS Lambda監視はどのように設定できますか? [#config] + +New Relicを使用してAWS Lambda監視するには、さまざまな環境、ランタイム、デプロイメント メソッドにわたって計装を構成できます。 設定プロセスについては、次の手順で説明します。 + + + + ### 互換性と要件 [#req] + + AWS Lambda が当社の[互換性と要件](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/compatibility-requirement-lambda-monitoring)を満たしていることを確認してください。 + + + + ### （オプション）AWSアカウントをNew Relicにリンクする [#link] + + アカウントをリンクすると、 AWSアカウントのインベントリを作成し、 Lambda関数の CloudWatchメトリクスを自動的に収集する権限を New Relic に付与することになります。 アカウントをリンクすると、 AWSアカウントのリソースが[エンティティ エクスプローラー](/docs/new-relic-solutions/new-relic-one/core-concepts/new-relic-explorer-view-performance-across-apps-services-hosts/#find)にエンティティとして表示されます。 Lambda関数 エンティティはサーバーレス機能ビューにあります。 + + 次の統合方法のいずれかで、 AWSと New Relic アカウントをリンクできます。 + + + + AWSメトリクスストリーム(推奨) APIポーリング + + + + + New RelicがLambda関数を監視するには、 New RelicとAWS間の統合をセットアップする必要があります。 レイテンシを削減し、ポーリングrequestsのスロットルを回避するには、[メトリクス ストリームを](/install/aws-cloudwatch)使用することをお勧めします。 + + + + メトリクス Streams インテグレーションを使用していない場合は、代わりに[APIポーリング インテグレーション](/docs/infrastructure/amazon-integrations/connect/set-up-aws-api-polling)をセットアップすることを選択できます。 デフォルトでは、 Lambdaサービスが有効になっているAPIポーリング統合は、CloudWatchメトリクスに対して 5 分ごとにポーリングを行います。 + + [newrelic-lambda-cli](https://github.com/newrelic/newrelic-lambda-cli)を使用してAPIポーリング統合をセットアップすることはできますが、メトリクス Streams 統合はセットアップできません。 + + ```sh + newrelic-lambda integrations install --nr-account-id YOUR_NR_ACCOUNT_ID \ + --nr-api-key YOUR_NEW_RELIC_USER_KEY + ``` + + [統合インストール コマンド](https://github.com/newrelic/newrelic-lambda-cli?tab=readme-ov-file#aws-lambda-integration)の 1 つのステップで、 [AWS Secrets Manager](https://aws.amazon.com/secrets-manager/)に `NEW_RELIC_LICENSE_KEY` シークレットが作成され、セキュリティが向上します。 これは、他のオプションやフラグとともに、 `--disable-license-key-secret`フラグを使用して構成できます。 + + + + + + + ### AWS Lambda関数を計装する [#instrument] + + Lambda関数を計装するには、エージェントと拡張機能が必要です。 これらのコンポーネントは、New Relic [Lambda レイヤー](https://github.com/newrelic/newrelic-lambda-layers)にまとめられています。 Lambda レイヤーを使用できない場合は、エージェントと拡張機能を関数に手動で組み込むことができます。 Lambda関数の要件に基づいて、次のいずれかのインストルメンテーション方法を選択します。 + + + + 階層化されたインストゥルメンテーションSDK ベースのインストゥルメンテーションコンテナ化されたインストゥルメンテーション + + + + + Lambda関数がZipファイルとしてパッケージ化されており、レイヤーを追加できる場合は、この方法を使用します。 レイヤーは、ライブラリ、カスタム ランタイム、およびその他の依存関係の配布メカニズムです。 詳細については、 [Layered インストゥルメンテーションの](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own/)ドキュメントを参照してください。 + + + + Lambda関数がレイヤーを使用できない場合はこのメソッドを使用すると、レイヤーを変更する必要がなく、迅速なデプロイメントが保証されます。 詳細については、 [SDK ベースのインストゥルメンテーションの](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/sdk-based-instrumentation/)ドキュメントを参照してください。 + + + + Lambda関数がコンテナ内で実行される場合は、このメソッドを使用します。 コンテナは、アプリケーションに対して一貫性のある分離された実行環境を提供します。New Relic は、New Relic Lambda レイヤー、New Relic Lambda 拡張機能、および New Relic エージェントを含む、事前に構築された Docker イメージを提供します。詳細については、 [Containerized コンテナの](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/containerized-images/)ドキュメントを参照してください。 + + + + + + + ### 環境変数を設定する [#env-variables] + + + * New Relic CLI を使用して New Relic のLambdaレイヤーをセットアップすると、必須の環境変数が自動的に構成されます。 ただし、デフォルト設定の一部を変更し、監視のニーズに合った環境変数を使用してLambda関数を構成する必要がある場合があります。 + * New Relic Lambda 拡張機能を使用している場合は、環境変数を手動で設定する必要があります。 + + + [環境変数は](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda)、New Relic エージェントと Lambda 拡張機能を構成するために使用されます。 Lambda関数が正しく監視されるようにするには、これらの変数を正しく設定することが重要です。 + + + + ### New Relicでデータを探す [#data] + + AWS Lambda 関数をセットアップしたら、 New Relic APMインターフェースでデータを検索して使用できるようになります。 データはいくつかの主要な領域に編成されており、それぞれがLambda関数のパフォーマンスと状態に異なるインサイトを提供します。 + + + +## サンプル関数をお試しください [#example] + +New Relicの Lambda レイヤーをインストゥルメントした後は、サンプル関数を試してみることを強くお勧めします。 これらの実用的な例は、独自のサーバーレス機能を開始するための出発点として使用する必要があります。 これらの例を使用すると、 New Relic Lambda レイヤーやアカウント リンクのテストに慣れることができ、独自のインストゥルメンテーションのリファレンスとしても使用できます。 各例では、権限の追加、ハンドラーをラップするためのランタイム固有の手法、CloudWatch での関数ログ保持の管理などを示します。 + +Lambda 関数を管理およびデプロイする方法は多数ありますが、この例ではAWS CloudFormation というメカニズムを使用しています。 + +私たちの例は、New Relic Lambda Extension とともに、この[GitHub リポジトリ](https://github.com/newrelic/newrelic-lambda-extension)で公開されています。 New Relic がサポートする Lambda ランタイムごとに 1 つあります。 + +* [Node.js](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/sam/node) +* [Python](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/sam/python) +* [Go](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/sam/go) +* [Java](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/sam/java) +* [Ruby](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/sam/ruby) +* [.NET](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/sam/dotnet) + +また、ディストリビューティッド（分散）トレーシングの例で、ディストリビュー[ティッド（分散）トレーシングを](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/sam/distributedtracing)非自明なサーバーレス アプリケーションに組み込む方法を学ぶこともできます。 これは、Node、Python、 Ruby 、Java 関数を使用して、Lambda 関数を呼び出す可能性のある 2 つの一般的なサービスである SQS と SNS の手動トレース伝播を示しています。 - どの配送方法を使用しても、New Relic のペイロードとエクスペリエンスは同じままです。 + 手動でテストする場合、テレメトリーデータが遅延する可能性があります。 バッファリングされたテレメトリが配信されるように、関数を再度呼び出す前に 7 秒待つことをお勧めします。 -AWS Lambda のサーバーレス監視を有効にすると、Amazon Web Services の料金が発生する可能性があります。 お客様の Lambda データを当社に報告する `newrelic-log-ingestion` Lambda 関数は[サードパーティサービス](/docs/licenses/license-information/acceptable-use-policy/acceptable-use-policy)とみなされます。このサービスの使用によって発生するAWS料金はお客様の責任となります。 +## コストの考慮 [#costs] + +AWS Lambda のサーバーレス監視を実装すると、追加の AWS 料金が発生する場合があります。 New Relic にデータを報告する `newrelic-log-ingestion` Lambda関数はサードパーティのサービスとみなされ、関連するAWS料金はユーザーの責任となります。 [`newrelic-lambda-extension`](https://github.com/newrelic/newrelic-lambda-extension)[New RelicLambda ](https://github.com/newrelic/newrelic-lambda-layers)レイヤー に含まれる を使用すると、ログとテレメトリデータを CloudWatch`newrelic-log-ingestion` 経由で送信することを回避できますが、高可用性のニーズに合わせて 関数を CloudWatch フォールバックとして構成することも可能です。 + +AWS Lambda のサーバーレス監視を有効にすると、Amazon Web Services の料金が発生する可能性があります。お客様のLambdaデータを当社に報告する`newrelic-log-ingestion` Lambda関数は[サードパーティサービス](/docs/licenses/license-information/general-usage-licenses/acceptable-use-policy)とみなされます。このサービスの使用によって発生するAWS料金はお客様の責任となります。 + +[New RelicLambda](https://github.com/newrelic/newrelic-lambda-layers) Layers にバンドルされている[ newrelic-lambda-extension](https://github.com/newrelic/newrelic-lambda-extension) を使用すると、CloudWatch および[ newrelic-log-ingestion](https://github.com/newrelic/aws-log-ingestion) 関数を介したログとテレメトリーの送信を回避できます。オブザーバビリティデータの高可用性を必要とする機能の[ CloudWatch](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/cloud-watch-fallback/) フォールバック メソッドとして newrelic-log-ingestion[ 関数を設定することもできます。](https://github.com/newrelic/aws-log-ingestion) + +## 価格 [#pricing] + +New Relic APM + Serverless Convergence の使用は、注文に従って APM エンティティとして請求されます。価格に関する詳細については、弊社の営業チームにお問い合わせいただくか、ご注文を参照してください。 -## 次のステップ +## 関連記事 [#related-docs] - - サポートされているランタイムと前提条件の詳細 + + New Relicの階層化アプローチを使用してLambda関数を計装します。 - - Lambda関数の計装と設定を始めましょう + + SDK を使用してLambda関数を計装します。 - - New Relicを使用してAWS Lambda関数を監視する方法を学びます + + New Relicのコンテナ化アプローチを使用してLambda関数を計装します。 \ No newline at end of file diff --git a/src/i18n/content/jp/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/sdk-based-instrumentation.mdx b/src/i18n/content/jp/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/sdk-based-instrumentation.mdx index 20d508023ef..438b07747e1 100644 --- a/src/i18n/content/jp/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/sdk-based-instrumentation.mdx +++ b/src/i18n/content/jp/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/sdk-based-instrumentation.mdx @@ -67,9 +67,11 @@ SDK ベースのインストゥルメンテーションでは、選択したラ - 5. [ディストリビューティッド（分散）トレーシング](/docs/apm/distributed-tracing/getting-started/introduction-distributed-tracing)を有効にして環境変数を設定するには、 [環境変数の](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda)ドキュメントを参照してください。 + 5. [環境変数](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda)を設定します。 - 6. 少なくとも1回Lambdaを呼び出します。これにより、CloudWatchロググループが作成されます。次のステップではこのグループが必要です。 + 6. AWSマネジメント コンソールの Configuration \[設定] タブで、 Lambda関数に`NR.Apm.Lambda.Mode: true`タグを追加します。 + + 7. 少なくとも1回Lambdaを呼び出します。これにより、CloudWatchロググループが作成されます。次のステップではこのグループが必要です。 ラッパーはLambda実行についてのデータを収集し、JSONメッセージを生成し、CloudWatchログにログ記録します。次に、[CloudWatchを設定してそのログをNew Relicに送信します](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/instrument-your-own/#manual-stream-logs)。 @@ -130,9 +132,11 @@ SDK ベースのインストゥルメンテーションでは、選択したラ 6. AWS Lambdaコンソールで、ハンドラーを設定します。 [Java Lambdaの例](https://github.com/newrelic/newrelic-lambda-tracer-java#usage)では、ハンドラーは`com.handler.example.MyLambdaHandler::handleRequest`になります。 `handleRequest`が想定されているため、 `com.handler.example.MyLambdaHandler`を使用することもできます。 - 7. [ディストリビューティッド（分散）トレーシング](/docs/apm/distributed-tracing/getting-started/introduction-distributed-tracing)を有効にして環境変数を設定するには、 [環境変数の](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda)ドキュメントを参照してください。 + 7. [環境変数](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda)を設定します。 + + 8. AWSマネジメント コンソールの Configuration \[設定] タブで、 Lambda関数に`NR.Apm.Lambda.Mode: true`タグを追加します。 - 8. 少なくとも1回Lambdaを呼び出します。これにより、CloudWatchロググループが作成されます。次のステップではこのグループが必要です。 + 9. 少なくとも1回Lambdaを呼び出します。これにより、CloudWatchロググループが作成されます。次のステップではこのグループが必要です。 ラッパーはLambda実行についてのデータを収集し、JSONメッセージを生成し、CloudWatchログにログ記録します。次に、[CloudWatchを設定してそのログをNew Relicに送信します](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/instrument-your-own/#manual-stream-logs)。 @@ -211,9 +215,11 @@ SDK ベースのインストゥルメンテーションでは、選択したラ 5. 圧縮したファイルを、AWS Lambdaアカウントにアップロードします。 - 6. [ディストリビューティッド（分散）トレーシング](/docs/apm/distributed-tracing/getting-started/introduction-distributed-tracing)を有効にして環境変数を設定するには、 [環境変数の](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda)ドキュメントを参照してください。 + 6. [環境変数](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda)を設定します。 + + 7. AWSマネジメント コンソールの Configuration \[設定] タブで、 Lambda関数に`NR.Apm.Lambda.Mode: true`タグを追加します。 - 7. インストゥルメンテーションを完了するには、次のいずれかの手順に従ってテレメトリーデータをNew Relicに送信します。 + 8. インストゥルメンテーションを完了するには、次のいずれかの手順に従ってテレメトリーデータをNew Relicに送信します。 * New Relic Lambda `Extension layer`を使用します。 最新の[（NewRelicLambdaExtension）](https://layers.newrelic-external.com/)レイヤーarnを取得できます。 AWS CLI を使用してレイヤーをインストールするか、手動で Lambda に追加することができます。 @@ -269,9 +275,11 @@ SDK ベースのインストゥルメンテーションでは、選択したラ 6. 圧縮したファイルを、AWS Lambdaアカウントにアップロードします。 - 7. [ディストリビューティッド（分散）トレーシング](/docs/apm/distributed-tracing/getting-started/introduction-distributed-tracing)を有効にして環境変数を設定するには、 [環境変数の](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda)ドキュメントを参照してください。 + 7. [環境変数](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda)を設定します。 - 8. 少なくとも1回Lambdaを呼び出します。これにより、CloudWatchロググループが作成されます。次のステップではこのグループが必要です。 + 8. AWSマネジメント コンソールの Configuration \[設定] タブで、 Lambda関数に`NR.Apm.Lambda.Mode: true`タグを追加します。 + + 9. 少なくとも1回Lambdaを呼び出します。これにより、CloudWatchロググループが作成されます。次のステップではこのグループが必要です。 New Relicデコレーターは、Lambda実行についてのデータを収集し、JSONメッセージを生成し、CloudWatchログに記録します。次に、[CloudWatchを設定してそのログをNew Relicに送信します](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/instrument-your-own/#manual-stream-logs)。 @@ -282,25 +290,38 @@ SDK ベースのインストゥルメンテーションでは、選択したラ .NET Lambda をセットアップするには: 1. [NewRelic.agent nuget パッケージを](https://www.nuget.org/packages/NewRelic.Agent)AWS Lambdaプロジェクトに追加します。 詳細については、[インストレーション ガイドを](/docs/apm/agents/net-agent/install-guides/install-net-agent-using-nuget/)ご覧ください。 - 2. [ディストリビューティッド（分散）トレーシング](/docs/apm/distributed-tracing/getting-started/introduction-distributed-tracing)を有効にして環境変数を設定するには、 [環境変数の](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda)ドキュメントを参照してください。 - 3. プロジェクトを AWS Lambda アカウントに公開します。 - 4. New Relic Lambda Extension または`newrelic-log-ingestion`ラムダのいずれか[を構成します](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/account-linking/)。 - 5. Lambda を少なくとも 1 回呼び出してエラーをチェックし、データが New Relic UI に表示されることを確認します。 + 2. [環境変数](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda)を設定します。 + 3. AWSマネジメント コンソールの Configuration \[設定] タブで、 Lambda関数に`NR.Apm.Lambda.Mode: true`タグを追加します。 + 4. プロジェクトを AWS Lambda アカウントに公開します。 + 5. New Relic Lambda Extension または`newrelic-log-ingestion`ラムダのいずれか[を構成します](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/account-linking/)。 + 6. Lambda を少なくとも 1 回呼び出してエラーをチェックし、データが New Relic UI に表示されることを確認します。 -## 次のステップ +## データを見つけて使用する [#find-data] + +AWS Lambda 関数をセットアップしたら、 New Relic APMインターフェースでデータを検索して使用できるようになります。 データはいくつかの主要な領域に編成されており、それぞれがLambda関数のパフォーマンスと状態に異なるインサイトを提供します。 + +APMインターフェイスでは、[ディストリビューティッド（分散）ト](/docs/distributed-tracing/concepts/introduction-distributed-tracing/)レーシング、[サービス マップ](/docs/new-relic-solutions/new-relic-one/ui-data/service-maps/service-maps/)、[トランザクション](docs/apm/transactions/intro-transactions/transactions-new-relic-apm//)、[エラー分析](docs/errors-inbox/getting-started/)など、 Lambda関数のさまざまな側面を探索できます。 これらの各領域では、 Lambda関数のパフォーマンス、レイテンシ、エラー率に関する詳細なインサイトが提供され、問題を迅速に特定して解決できるようになります。 + + + 呼び出しエクスペリエンスは、 APM対話トレースと統合されました。 これにより、特定の`AWS RequestId`を使用してAPMマッカーサー トレースにドリルダウンし、特定のLambda実行に関する詳細情報を得ることができます。 + + +New Relic APMインターフェースでLambda関数を表示するには: + +1. [https://one.newrelic.com](https://one.newrelic.com) > APM & Servicesに移動します。 +2. 検索条件を`isLambdaFunction = true`に設定します。 +3. 表示されたリストから、 Lambda関数を選択してデータを表示します。 + +## 関連記事 [#related-docs] サポートされているランタイムと前提条件の詳細 - - New Relicを使用してAWS Lambda関数を監視する方法を学びます - - - + インストール関連の問題のトラブルシューティング方法を学ぶ \ No newline at end of file diff --git a/src/i18n/content/jp/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/update-lambda-monitoring.mdx b/src/i18n/content/jp/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/update-lambda-monitoring.mdx index c3d2c243e79..a55bbe8ee56 100644 --- a/src/i18n/content/jp/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/update-lambda-monitoring.mdx +++ b/src/i18n/content/jp/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/update-lambda-monitoring.mdx @@ -5,7 +5,7 @@ freshnessValidatedDate: never translationType: machine --- -[AWS Lambda のモニタリングを有効にし](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/enable-new-relic-monitoring-aws-lambda)た後、AWS ログ データのレポートに使用される Lambda 関数`newrelic-log-ingestion`を時々更新する必要があります。 +[AWS Lambdaの監視を有効にした](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda/#link)後、 AWSログ データのレポートに使用されるLambda関数を時々更新する必要があります: `newrelic-log-ingestion` 。 これには2つの方法があります。 @@ -13,7 +13,7 @@ translationType: machine * [AWS Serverless Application Repository経由でのアップデート](#update-sar): [手動での手順を有効にした場合に使用します](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/enable-new-relic-monitoring-aws-lambda#manual-nr-lambda). - これらの更新手順は、当社の [AWS Lambda 用サーバーレス監視](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/introduction-new-relic-monitoring-aws-lambda) に適用され、当社の [AWS Lambda 統合用インフラ監視](/docs/integrations/amazon-integrations/aws-integrations-list/aws-lambda-monitoring-integration) には適用されません。 + これらの更新手順は[AWS Lambdaのサーバーレス監視](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda)に適用され、 [AWS Lambdaインテグレーションのインフラストラクチャ監視](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-lambda-monitoring-integration)には適用されません。 ## CLIによるLambdaインテグレーションの更新 [#update-cli] @@ -60,6 +60,7 @@ translationType: machine --function installed \ --nr-account-id NR_ACCOUNT_ID \ --upgrade + --apm ``` ## 手動のServerlessアプリケーションリポジトリのインストールを更新する [#update-sar] diff --git a/src/i18n/content/jp/docs/serverless-function-monitoring/aws-lambda-monitoring/troubleshooting/troubleshoot-enabling-serverless-monitoring-aws-lambda.mdx b/src/i18n/content/jp/docs/serverless-function-monitoring/aws-lambda-monitoring/troubleshooting/troubleshoot-enabling-serverless-monitoring-aws-lambda.mdx index a53fd0b7aa2..74ba5baf849 100644 --- a/src/i18n/content/jp/docs/serverless-function-monitoring/aws-lambda-monitoring/troubleshooting/troubleshoot-enabling-serverless-monitoring-aws-lambda.mdx +++ b/src/i18n/content/jp/docs/serverless-function-monitoring/aws-lambda-monitoring/troubleshooting/troubleshoot-enabling-serverless-monitoring-aws-lambda.mdx @@ -1,5 +1,5 @@ --- -title: AWS Lambdaのサーバーレス監視を可能にするためのトラブルシューティング +title: Lambda監視のトラブルシューティング type: troubleshooting tags: - Serverless function monitoring @@ -12,22 +12,22 @@ translationType: machine ## 問題 -[AWS Lambdaのサーバーレスモニタリング](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/introduction-new-relic-monitoring-aws-lambda)を有効にしようとしていますが、問題またはエラーが発生しています。 +[AWS Lambda のサーバーレス監視](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda)を有効にしようとしていますが、問題またはエラーが発生しています。 ## 解決 -[イネーブルメント手順](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/enable-new-relic-monitoring-aws-lambda) のすべてを完了しないことに関連して、2つの一般的な問題があります。 +すべての[有効化手順](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda/#link)を完了していないことに関連する一般的な問題が 2 つあります。 -* **CloudWatch metrics** UI ページにデータが表示されません。これは[、 AWSインテグレーションのステップ](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/enable-new-relic-monitoring-aws-lambda#connect-aws)が完了していないことを意味します。 -* **Troubleshooting**カテゴリの UI ページにデータが表示されません。**Distributed tracing**、**Errors**、および **Invocations** UIタブにデータが表示されない場合は、 [APMエージェントインストゥルメンテーションのステップ](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/enable-new-relic-monitoring-aws-lambda#instrument-lambda)が完了していないことを意味します。 +* **Lambda metrics** UI ページにデータが表示されません。これは[、 AWSインテグレーションのステップ](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda/#link)が完了していないことを意味します。 +* **Troubleshooting**カテゴリ UI ページにデータが表示されません。**Distributed tracing** 、 **Errors** 、および**Invocations** UIタブにデータが表示されない場合は、 [APMエージェントインストゥルメンテーション ステップが](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda/#instrument)完了していないことを意味します。 このような基本的なイネーブルメントの問題以外にも、問題を引き起こす可能性のある問題がいくつかあります。 -* CloudWatch エラー「HTTP エラー 401: 権限がありません。」これはAPIキーが正しくないことが原因です。 [AWS 有効化の設定手順](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/enable-new-relic-monitoring-aws-lambda#connect-aws)の`--nr-api-key`引数は受け取ります。 +* CloudWatch エラー「HTTP エラー 401: 権限がありません。」これはAPIキーが正しくないことが原因です。 [AWS 有効化設定ステップ](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda/#link)の`--nr-api-key`引数はを使用します。 * カスタムメトリクスが不足しています。Lambdaのモニタリングは、 [カスタムメトリクス](/docs/agents/manage-apm-agents/agent-data/collect-custom-metrics) と互換性がありません。 [カスタムアトリビュート](/docs/agents/manage-apm-agents/agent-data/collect-custom-attributes) を使用して、メタデータを追加してください。 -* Invocations missing.呼び出しの内訳の詳細を表示するには、 [Lambda instrumentation step](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/enable-new-relic-monitoring-aws-lambda#instrument-lambda) の一部として分散トレースを有効にする必要があります。分散トレーシングは、スパンの詳細をinvocation detailsペインに表示するために必要です。 +* 呼び出しタブがありません。APM + Serverless Convergence では、各Lambda呼び出しはAPMの段階トレースに対応します。 呼び出しの内訳の詳細を確認するには、 [「継続トレース」](/docs/apm/apm-ui-pages/monitoring/transactions-page-find-specific-performance-problems)を参照してください。 * インストール、統合、インスツルメンテーションの手順が正しく完了し、機能がCloudWatchにログを送信していますが、UIに特定の依存関係のトレース（または任意のトレース）が表示されていません。これは、レイヤーのマージの順番（Lambdaレイヤーを使用している場合）や、インポートの順番（手動でインスツルメンテーションを行っている場合）に起因している可能性があります。 diff --git a/src/i18n/content/jp/docs/serverless-function-monitoring/aws-lambda-monitoring/troubleshooting/troubleshoot-no-data-appears.mdx b/src/i18n/content/jp/docs/serverless-function-monitoring/aws-lambda-monitoring/troubleshooting/troubleshoot-no-data-appears.mdx index 4303d567efa..775ff8cda00 100644 --- a/src/i18n/content/jp/docs/serverless-function-monitoring/aws-lambda-monitoring/troubleshooting/troubleshoot-no-data-appears.mdx +++ b/src/i18n/content/jp/docs/serverless-function-monitoring/aws-lambda-monitoring/troubleshooting/troubleshoot-no-data-appears.mdx @@ -10,12 +10,22 @@ freshnessValidatedDate: never translationType: machine --- -## 問題 +## 問題 [#problem] AWS Lambda関数のトラフィックを生成し、5分待っても、関数データがNew Relic UIに表示されません。 ログにはエラーはなく、New Relic UI には`NRIntegrationErrors`または`NRIntegrationWarnings`はありません。 -## 解決 +## 解決 [#solution] + +### ライセンスキーとアカウントIDを確認する [#check-license] データが表示されず、エラーも発生しない最も一般的な理由は[、ライセンスキーとアカウント ID](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/account-linking/)が異なるアカウントのものであることです。 不一致の場合、[ クラウド ウォッチ ログを処理する New Relic Lambda 拡張機能](https://github.com/newrelic/newrelic-lambda-extension) または[ lambda](/docs/infrastructure/amazon-integrations/connect/aws-metric-stream/) はデータを正常に報告しますが、アカウント ID が一致しないため、データを黙ってドロップします。これにより、エラーや警告は発生しません。 この問題を解決するには、ライセンスキーとアカウント ID が同じアカウントのものであることを確認してください。 このような問題を最小限に抑えるには、 [New Relic Lambda CLI](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/account-linking/#rec)を使用してサーバーレス監視を有効にすることをお勧めします。 AWS Secrets Manager でライセンスキーを更新できます。 AWS Secrets Manager を使用していないアカウント ID と設定の場合、正しいライセンスキーまたはアカウント ID を使用して[環境変数を](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/account-linking/#env-var)更新することで問題を修正できます。 + +### 環境変数を確認する [#check-env-vars] + +AWS Lambda関数で必要な[環境変数](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda)が正しく設定されていることを確認します。 これには、 `NEW_RELIC_APM_LAMBDA_MODE` 、 `NEW_RELIC_ACCOUNT_ID` 、 `NEW_RELIC_LICENSE_KEY` 、およびその他の関連する変数が含まれます。これらの変数が設定されていないか正しくない場合、データが New Relic に送信されない可能性があります。詳細については、 [環境変数](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda)を参照してください。 + +### AWSマネジメントコンソールでタグを確認する [#check-tags] + +AWSマネジメントコンソールからLambda関数に`NR.Apm.Lambda.Mode: true`タグを追加したことを確認してください。 このタグは、監視を有効にし、データが New Relic に送信されることを確認するために不可欠です。 \ No newline at end of file diff --git a/src/i18n/content/kr/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx b/src/i18n/content/kr/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx index da505ee12ee..96741ae2040 100644 --- a/src/i18n/content/kr/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx +++ b/src/i18n/content/kr/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx @@ -36,7 +36,7 @@ translationType: machine - The .NET agent is compatible with .NET Core version 3.1, and .NET 5.0, 6.0, 7.0, 8.0, 9.0, and 10.0. + .NET 에이전트는 .NET Core 버전 3.1, .NET 5.0, 6.0, 7.0, 8.0, 9.0, 10.0과 호환됩니다. 에이전트는 [현재 Microsoft에서 지원하는 목표 .NET 런타임이 있는](https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core) 경우에만 완전히 지원됩니다. 해당 에이전트는 아래 나열된 EOL 런타임에서 작동할 가능성이 있지만, EOL 런타임에서 새 버전의 에이전트를 테스트하지는 않습니다. @@ -271,7 +271,7 @@ translationType: machine - The .NET agent is compatible with applications targeting .NET Core 3.1, and .NET 5.0, 6.0, 7.0, 8.0, 9.0, and 10.0. You can find the target framework in your `.csproj` file. Agent compatibility varies across different versions of .NET Core. + .NET 에이전트는 .NET Core 3.1, .NET 5.0, 6.0, 7.0, 8.0, 9.0, 10.0을 타겟으로 하는 애플리케이션과 호환됩니다. `.csproj` 파일에서 쿠, 목표 프레임워크를 찾을 수 있습니다. 에이전트 호환성은 .NET Core 버전마다 다릅니다. 호환 가능: @@ -319,8 +319,8 @@ translationType: machine .NET 에이전트는 다음 애플리케이션 프레임워크를 자동으로 계측합니다. - * ASP.NET Core MVC 2.0, 2.1, 2.2, 3.0, 3.1, 5.0, 6.0, 7.0, 8.0, 9.0, and 10.0 (includes Web API) - * ASP.NET Core Razor Pages 6.0, 7.0, 8.0, 9.0, and 10.0 (starting with .NET agent version 10.19.0) + * ASP..NET Core MVC 2.0, 2.1, 2.2, 3.0, 3.1, 5.0, 6.0, 7.0, 8.0, 9.0 및 10.0(Web API 포함) + * ASP..NET Core Razor Pages 6.0, 7.0, 8.0, 9.0 및 10.0(.NET 에이전트 버전 10.19.0부터 시작) @@ -357,7 +357,7 @@ translationType: machine .NET 에이전트 `v9.2.0` 이상은 [Microsoft.Azure.Cosmos](https://www.nuget.org/packages/Microsoft.Azure.Cosmos) 라이브러리를 자동으로 계측합니다. * 지원되는 최소 버전: 3.17.0 - * Latest verified compatible version: 3.56.0 + * 최신 검증된 호환 버전: 3.56.0 * .NET 에이전트 v10.32.0부터 버전 3.35.0 이상이 지원됩니다. @@ -434,7 +434,7 @@ translationType: machine [Npgsql](https://www.nuget.org/packages/Npgsql/) 사용 * 지원되는 최소 버전: 4.0.0 - * Latest verified compatible version: 7.0.7 + * 최신 검증된 호환 버전: 7.0.7 이전 버전의 Npgsql도 계측될 수 있지만 중복 및/또는 누락된 메트릭이 가능합니다. @@ -452,7 +452,7 @@ translationType: machine 지원되는 최소 버전: 2.3.0 - Latest verified compatible version: 3.5.2 + 최신 검증된 호환 버전: 3.5.2 버전 3.0.0 .NET 에이전트 v10.40.0부터 더 높은 버전이 지원됩니다. @@ -570,7 +570,7 @@ translationType: machine * 최소 지원 버전: 3.5.0 - * Latest verified compatible version: 4.0.10.1 + * 최신 검증된 호환 버전: 4.0.10.1 * 필요한 최소 에이전트 버전: 10.33.0 @@ -907,7 +907,7 @@ translationType: machine * 지원되는 최소 버전: 3.5.2 - * Latest verified compatible version: 7.1.2 + * 최신 검증된 호환 버전: 7.1.2 @@ -921,7 +921,7 @@ translationType: machine * 최소 지원 버전: 7.1.0 - * Latest verified compatible version: 8.5.7 + * 최신 검증된 호환 버전: 8.5.7 @@ -949,7 +949,7 @@ translationType: machine * 최소 지원 버전: 3.7.0 - * Latest verified compatible version: 4.0.7.6 + * 최신 검증된 호환 버전: 4.0.7.6 @@ -963,7 +963,7 @@ translationType: machine * 최소 지원 버전: 3.7.0 - * Latest verified compatible version: 4.0.3.5 + * 최신 검증된 호환 버전: 4.0.3.5 @@ -1343,7 +1343,7 @@ translationType: machine .NET 에이전트 `v9.2.0` 이상은 [Microsoft.Azure.Cosmos](https://www.nuget.org/packages/Microsoft.Azure.Cosmos) 라이브러리를 자동으로 계측합니다. * 지원되는 최소 버전: 3.17.0 - * Latest verified compatible version: 3.56.0 + * 최신 검증된 호환 버전: 3.56.0 * .NET 에이전트 v10.32.0부터 버전 3.35.0 이상이 지원됩니다. @@ -1461,7 +1461,7 @@ translationType: machine 지원되는 최소 버전: 2.3.0 - Latest verified compatible version: 3.5.2 + 최신 검증된 호환 버전: 3.5.2 버전 3.0.0 .NET 에이전트 v10.40.0부터 더 높은 버전이 지원됩니다. @@ -1531,7 +1531,7 @@ translationType: machine [Npgsql](https://www.nuget.org/packages/Npgsql/) 사용 * 지원되는 최소 버전: 4.0.0 - * Latest verified compatible version: 7.0.7 + * 최신 검증된 호환 버전: 7.0.7 이전 버전의 Npgsql도 계측될 수 있지만 중복 및/또는 누락된 메트릭이 가능합니다. @@ -1629,7 +1629,7 @@ translationType: machine * 최소 지원 버전: 3.5.0 - * Latest verified compatible version: 4.0.10.1 + * 최신 검증된 호환 버전: 4.0.10.1 * 필요한 최소 에이전트 버전: 10.33.0 @@ -1710,7 +1710,7 @@ translationType: machine 지원되는 최소 버전: 105.2.3 - Latest verified compatible version: 113.0.0 + 최신 검증된 호환 버전: 113.0.0 알려진 비호환 버전: 106.8.0, 106.9.0, 106.10.0, 106.10.1 @@ -2012,7 +2012,7 @@ translationType: machine * 지원되는 최소 버전: 3.5.2 - * Latest verified compatible version: 6.8.1 + * 최신 검증된 호환 버전: 6.8.1 @@ -2026,7 +2026,7 @@ translationType: machine * 최소 지원 버전: 7.1.0 - * Latest verified compatible version: 8.5.7 + * 최신 검증된 호환 버전: 8.5.7 @@ -2054,7 +2054,7 @@ translationType: machine * 최소 지원 버전: 3.7.0 - * Latest verified compatible version: 4.0.7.6 + * 최신 검증된 호환 버전: 4.0.7.6 @@ -2068,7 +2068,7 @@ translationType: machine * 최소 지원 버전: 3.7.0 - * Latest verified compatible version: 4.0.3.5 + * 최신 검증된 호환 버전: 4.0.3.5 diff --git a/src/i18n/content/kr/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx b/src/i18n/content/kr/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx index dcbc295b90d..53903ff0a00 100644 --- a/src/i18n/content/kr/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx +++ b/src/i18n/content/kr/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx @@ -268,32 +268,32 @@ Node.js 에이전트는 [npm(Node Package Manager) 저장소](https://npmjs.org/ | 패키지 이름 | 지원되는 최소 버전 | 최신 게시 버전 | \*에서 소개됨 | | --------------------------------- | ---------- | -------- | -------------------------------------- | | `@apollo/gateway` | 2.3.0 | 2.12.1 | `@newrelic/apollo-server-plugin@1.0.0` | -| `@apollo/server` | 4.0.0 | 5.1.0 | `@newrelic/apollo-server-plugin@2.1.0` | -| `@aws-sdk/client-bedrock-runtime` | 3.474.0 | 3.934.0 | 11.13.0 | -| `@aws-sdk/client-dynamodb` | 3.0.0 | 3.934.0 | 8.7.1 | -| `@aws-sdk/client-sns` | 3.0.0 | 3.934.0 | 8.7.1 | -| `@aws-sdk/client-sqs` | 3.0.0 | 3.934.0 | 8.7.1 | -| `@aws-sdk/lib-dynamodb` | 3.377.0 | 3.934.0 | 8.7.1 | +| `@apollo/server` | 4.0.0 | 5.2.0 | `@newrelic/apollo-server-plugin@2.1.0` | +| `@aws-sdk/client-bedrock-runtime` | 3.474.0 | 3.943.0 | 11.13.0 | +| `@aws-sdk/client-dynamodb` | 3.0.0 | 3.943.0 | 8.7.1 | +| `@aws-sdk/client-sns` | 3.0.0 | 3.943.0 | 8.7.1 | +| `@aws-sdk/client-sqs` | 3.0.0 | 3.943.0 | 8.7.1 | +| `@aws-sdk/lib-dynamodb` | 3.377.0 | 3.943.0 | 8.7.1 | | `@aws-sdk/smithy-client` | 3.47.0 | 3.374.0 | 8.7.1 | -| `@azure/functions` | 4.7.0 | 4.9.0 | 12.18.0 | +| `@azure/functions` | 4.7.0 | 4.10.0 | 12.18.0 | | `@elastic/elasticsearch` | 7.16.0 | 9.2.0 | 11.9.0 | | `@google/genai` | 1.1.0 | 1.30.0 | 12.21.0 | -| `@grpc/grpc-js` | 1.4.0 | 1.14.1 | 8.17.0 | +| `@grpc/grpc-js` | 1.4.0 | 1.14.2 | 8.17.0 | | `@hapi/hapi` | 20.1.2 | 21.4.4 | 9.0.0 | -| `@koa/router` | 12.0.1 | 14.0.0 | 3.2.0 | -| `@langchain/core` | 0.1.17 | 1.0.6 | 11.13.0 | -| `@modelcontextprotocol/sdk` | 1.13.0 | 1.22.0 | 13.2.0 | -| `@nestjs/cli` | 9.0.0 | 11.0.12 | 10.1.0 | +| `@koa/router` | 12.0.1 | 15.0.0 | 3.2.0 | +| `@langchain/core` | 0.1.17 | 1.1.1 | 11.13.0 | +| `@modelcontextprotocol/sdk` | 1.13.0 | 1.24.1 | 13.2.0 | +| `@nestjs/cli` | 9.0.0 | 11.0.14 | 10.1.0 | | `@opensearch-project/opensearch` | 2.1.0 | 3.5.1 | 12.10.0 | -| `@prisma/client` | 5.0.0 | 7.0.0 | 11.0.0 | -| `@smithy/smithy-client` | 2.0.0 | 4.9.7 | 11.0.0 | +| `@prisma/client` | 5.0.0 | 7.0.1 | 11.0.0 | +| `@smithy/smithy-client` | 2.0.0 | 4.9.9 | 11.0.0 | | `amqplib` | 0.5.0 | 0.10.9 | 2.0.0 | | `aws-sdk` | 2.2.48 | 2.1692.0 | 6.2.0 | | `bluebird` | 2.0.0 | 3.7.2 | 1.27.0 | | `bunyan` | 1.8.12 | 1.8.15 | 9.3.0 | | `cassandra-driver` | 3.4.0 | 4.8.0 | 1.7.1 | | `connect` | 3.0.0 | 3.7.0 | 2.6.0 | -| `express` | 4.15.0 | 5.1.0 | 2.6.0 | +| `express` | 4.15.0 | 5.2.1 | 2.6.0 | | `fastify` | 3.0.0 | 5.6.2 | 8.5.0 | | `generic-pool` | 3.0.0 | 3.9.0 | 0.9.0 | | `ioredis` | 4.0.0 | 5.8.2 | 1.26.2 | @@ -305,13 +305,13 @@ Node.js 에이전트는 [npm(Node Package Manager) 저장소](https://npmjs.org/ | `mongodb` | 4.1.4 | 7.0.0 | 1.32.0 | | `mysql` | 2.16.0 | 2.18.1 | 1.32.0 | | `mysql2` | 2.0.0 | 3.15.3 | 1.32.0 | -| `next` | 13.4.19 | 16.0.3 | 12.0.0 | +| `next` | 13.4.19 | 16.0.6 | 12.0.0 | | `openai` | 4.0.0 | 6.9.1 | 11.13.0 | | `pg` | 8.2.0 | 8.16.3 | 9.0.0 | | `pg-native` | 3.0.0 | 3.5.2 | 9.0.0 | | `pino` | 8.0.0 | 10.1.0 | 8.11.0 | | `q` | 1.3.0 | 1.5.1 | 1.26.2 | -| `redis` | 3.1.0 | 5.9.0 | 1.31.0 | +| `redis` | 3.1.0 | 5.10.0 | 1.31.0 | | `restify` | 11.0.0 | 11.1.0 | 2.6.0 | | `superagent` | 3.0.0 | 10.2.3 | 4.9.0 | | `undici` | 5.0.0 | 7.16.0 | 11.1.0 | diff --git a/src/i18n/content/kr/docs/query-your-data/explore-query-data/dashboards/share-charts-dashboards-externally.mdx b/src/i18n/content/kr/docs/query-your-data/explore-query-data/dashboards/share-charts-dashboards-externally.mdx index 4f1493f0652..c14dbd5b240 100644 --- a/src/i18n/content/kr/docs/query-your-data/explore-query-data/dashboards/share-charts-dashboards-externally.mdx +++ b/src/i18n/content/kr/docs/query-your-data/explore-query-data/dashboards/share-charts-dashboards-externally.mdx @@ -135,16 +135,6 @@ translationType: machine * **세션 기반 액세스**: 대시보드에 액세스한 후 세션은 120시간 동안 활성 상태로 유지됩니다. 이 기간 이후에에 접속을 시도하거나 브라우저 세션이 만료되면 비밀번호를 요구합니다. 비밀번호 재설정이 있는 경우 위젯이 새로 고쳐지면 세션이 만료됩니다. 외부 사용자는 새로운 비밀번호를 입력해야 합니다. * **reCAPTCHA 확인**: 대시보드에 접근하려는 시도가 여러 번 실패한 경우, 비밀번호를 다시 입력하기 전에 reCAPTCHA 확인을 완료해야 합니다. - - ### 가격 [#public-dashboard-pricing] - - 라이브 대시보드 URL을 공유할 때는 관련 비용을 이해하고 이를 효과적으로 관리하는 방법을 아는 것이 중요합니다. **Public Dashboards** 은 [추가 기능](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/add-on-billing) 또는 컴퓨터 가격 모델의 일부로 제공되는 고급 컴퓨터 제품 기능입니다. 대시보드 시각화에서 쿼리를 실행할 때 고급 [CCU가](/docs/licenses/license-information/product-definitions/new-relic-one-pricing-definitions/#compute-capacity-unit) 소모되는데, 이는 다음과 같은 경우에 발생합니다. - - * 페이지 로드 시 - * 레이더 피커 변경에 대하여 - * 새로 고침 빈도 트리거에 대해 - - **[New Relic Administration](https://one.newrelic.com/admin-portal) > Consumption Management > Advanced capabilities** 에서 사용 비용을 모니터링할 수 있습니다. 비용을 최적화하려면 [가격 관리 모범 사례](#pricing-management) 섹션을 참조하세요. @@ -256,6 +246,16 @@ translationType: machine + ### 가격 [#public-dashboard-pricing] + + 라이브 대시보드 URL을 공유할 때는 관련 비용을 이해하고 이를 효과적으로 관리하는 방법을 아는 것이 중요합니다. **Public Dashboards** 은 [추가 기능](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/add-on-billing) 또는 컴퓨터 가격 모델의 일부로 제공되는 고급 컴퓨터 제품 기능입니다. 대시보드 시각화에서 쿼리를 실행할 때 고급 [CCU가](/docs/licenses/license-information/product-definitions/new-relic-one-pricing-definitions/#compute-capacity-unit) 소모되는데, 이는 다음과 같은 경우에 발생합니다. + + * 페이지 로드 시 + * 레이더 피커 변경에 대하여 + * 새로 고침 빈도 트리거에 대해 + + **[New Relic Administration](https://one.newrelic.com/admin-portal) > Consumption Management > Advanced capabilities** 에서 사용 비용을 모니터링할 수 있습니다. 비용을 최적화하려면 [가격 관리 모범 사례](#pricing-management) 섹션을 참조하세요. + ### 모범 사례 [#best-practices] 공개 대시보드 관련 가격 책정 및 비밀번호 보안을 효율적으로 관리하려면 다음 모범 사례를 따르세요. diff --git a/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-11-28-2025.mdx b/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-11-28-2025.mdx new file mode 100644 index 00000000000..e20800fa0e1 --- /dev/null +++ b/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-11-28-2025.mdx @@ -0,0 +1,72 @@ +--- +subject: Docs +releaseDate: '2025-11-28' +version: 'November 24 - November 28, 2025' +translationType: machine +--- + +### 새로운 문서 + +* 라라벨 웹 프로세서, 라라벨 Queue Workers 및 라라벨 Horizon Workers에 대한 포괄적인 지침을 제공하기 위해 라 [라벨에 대한 PHP 에이전트 지원이](/docs/apm/agents/php-agent/frameworks-libraries/laravel) 추가되었습니다. +* [PHPUnit 실행 시 메모리](/docs/apm/agents/php-agent/troubleshooting/phpunit-incompatibility) 문제 해결, 뉴렐릭 PHP 에이전트와의 PHPUnit 11+ 호환성 문제 해결 가이드가 추가되었습니다. + +### 주요 변경 사항 + +* 새로운 권한 부여 및 역할 생성 환경을 도입하여 [사용자 관리 개념](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts) 과 관련 RBAC 문서를 업데이트했습니다. 이 문서에서는 세 가지 역할 유형(조직 기반 역할, 계정 기반 역할, 상황 기반 역할)을 통합하여 **Roles** 탭 아래에 표시합니다. +* Microsoft Teams 통합 API 메서드와 예제를 통해 [공지 채널을](/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-channels) 업데이트했습니다. +* Microsoft Teams 통합 지원으로 [공지 대상이](/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-destinations) 업데이트되었습니다. + +### 사소한 변경 사항 + +* 가격 모델과 제공되는 기능에 대한 명확성을 높이기 위해 [새로운 가격 책정 및 청구 방식을](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing) 업데이트했습니다. +* 브라우저 측정, 로그 설정 옵션으로 [.NET 에이전트 설정을](/docs/apm/agents/net-agent/configuration/net-agent-configuration) 업데이트했습니다. +* 단순화된 설정 지침을 갖춘 [.NET 에이전트로 업데이트된 로그 모니터링](/docs/apm/agents/net-agent/other-features/browser-monitoring-net-agent) 입니다. +* 라라벨 Horizon 지원으로 [PHP 대응 호환성 요구 사항을](/docs/apm/agents/php-agent/getting-started/php-agent-compatibility-requirements) 업데이트하고 Windows 32비트 지원을 제거했습니다. +* 업데이트된 설정 지침으로 [OpenTelemetry 수집기 처리가](/docs/opentelemetry/get-started/collector-processing/opentelemetry-collector-processing-intro) 업데이트되었습니다. +* 고정 듀얼스택 엔드포인트 영구 링크로 [네트워크 설정이](/docs/new-relic-solutions/get-started/networks) 업데이트되었습니다. +* 최신 규정 준수 정보를 통해 [TISAX 규정 준수 사항을](/docs/security/security-privacy/compliance/certificates-standards-regulations/tisax) 업데이트했습니다. + +### 릴리즈 정보 + +* [인사이트 이전 APM 구형 내장 차트의 수명 종료 날짜를 2026년 6월 30일로 발표했습니다.](/eol/2025/11/pre-insights/) + +* 최신 릴리스에 대한 최신 정보를 받아보세요. + + * [Kubernetes 통합 v3.50.2](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-50-2): + + * newrelic-인프라-3.55.2 및 nri-bundle-6.0.26에 포함된 통합이 업데이트되었습니다. + + * [로그 251120](/docs/release-notes/logs-release-notes/logs-25-11-20): + + * AWS-log-ingestion 람다의 CVE-2025-53643을 수정했습니다. + * aiohttp 라이브러리를 3.13.2로 업데이트했습니다. 그리고 시 버전은 1.8.3입니다. + + * [리액트 작용 에이전트 v1.5.12](/docs/release-notes/mobile-release-notes/react-native-release-notes/react-native-agent-1512): + + * 네이티브 안드로이드 에이전트를 7.6.13 버전으로 업데이트했습니다. + * 네이티브 iOS 에이전트를 7.6.0 버전으로 업데이트했습니다. + + * [Capacitor 에이전트 v1.5.12](/docs/release-notes/mobile-release-notes/capacitor-release-notes/capacitor-agent-1512): + + * 네이티브 안드로이드 에이전트를 7.6.13 버전으로 업데이트했습니다. + * 네이티브 iOS 에이전트를 7.6.0 버전으로 업데이트했습니다. + + * [플러터 에이전트 v1.1.19](/docs/release-notes/mobile-release-notes/flutter-release-notes/flutter-agent-1119): + + * 네이티브 안드로이드 에이전트를 7.6.13 버전으로 업데이트했습니다. + * 네이티브 iOS 에이전트를 7.6.0 버전으로 업데이트했습니다. + + * [유니티 에이전트 v1.4.11](/docs/release-notes/mobile-release-notes/unity-release-notes/unity-agent-1411): + + * 네이티브 안드로이드 에이전트를 7.6.13 버전으로 업데이트했습니다. + * 네이티브 iOS 에이전트를 7.6.0 버전으로 업데이트했습니다. + + * [코도바 에이전트 v7.0.11](/docs/release-notes/mobile-release-notes/cordova-release-notes/cordova-agent-711): + + * 네이티브 안드로이드 에이전트를 7.6.13 버전으로 업데이트했습니다. + * 네이티브 iOS 에이전트를 7.6.0 버전으로 업데이트했습니다. + + * [.NET MAUI 에이전트 v1.1.14](/docs/release-notes/mobile-release-notes/net-maui-release-notes/net-maui-agent-1114): + + * 네이티브 안드로이드 에이전트를 7.6.13 버전으로 업데이트했습니다. + * 네이티브 iOS 에이전트를 7.6.0 버전으로 업데이트했습니다. \ No newline at end of file diff --git a/src/i18n/content/kr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/compatibility-requirement-lambda-monitoring.mdx b/src/i18n/content/kr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/compatibility-requirement-lambda-monitoring.mdx index d491e764ab9..35549b7d41e 100644 --- a/src/i18n/content/kr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/compatibility-requirement-lambda-monitoring.mdx +++ b/src/i18n/content/kr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/compatibility-requirement-lambda-monitoring.mdx @@ -11,13 +11,17 @@ translationType: machine Lambda 계층을 사용하여 서버리스 모니터링을 활성화하려면 다음이 필요합니다. -1. [관리자 역할이](/docs/accounts/original-accounts-billing/original-users-roles/users-roles-original-user-model/#roles) 있거나 **분석 관리자** [추가 역할이](/docs/accounts/original-accounts-billing/original-users-roles/users-roles-original-user-model#add-on) 있는 뉴렐릭 계정입니다. +* [관리자 역할](/docs/accounts/accounts-billing/new-relic-one-user-management/introduction-managing-users)이 있거나 **Infrastructure manager** \[인프라 관리자] [추가 역할](/docs/accounts/original-accounts-billing/original-users-roles/users-roles-original-user-model#add-on)이 있는 New Relic 계정. -2. . +* . -3. IAM 리소스, 관리형 암호 및 Lambda를 생성할 수 있는 권한이 있는 AWS 계정. CloudFormation 스택 및 S3 버킷을 생성하기 위한 권한도 필요합니다. +* IAM 리소스, 관리형 암호 및 Lambda를 생성할 수 있는 권한이 있는 AWS 계정. CloudFormation 스택 및 S3 버킷을 생성하기 위한 권한도 필요합니다. -## 지원되는 런타임 + + 뉴렐릭은 [AWS 통합을](/docs/infrastructure/amazon-integrations/get-started/introduction-aws-integrations/) 사용하여AWS 계정을 뉴렐릭과 통합하여 Lambda 함수를 자동으로 검색하고 모니터링할 것을 권장합니다. 이를 통해 서버리스 기능에 뉴렐릭 APM 의 모든 기능을 활용할 수 있습니다. + + +## 지원되는 런타임 [#supported-runtimes] 측정 유형에 따라 다음과 같은 런타임이 지원됩니다. @@ -58,8 +62,18 @@ Lambda 계층을 사용하여 서버리스 모니터링을 활성화하려면 * 열대: 뉴렐릭 컨테이너의 계층화 및 SDK 측정, 로그는 `com.amazonaws:aws-lambda-java-events` 버전 `3.0.0` 부터 최신 버전과 호환됩니다. -## 무엇 향후 계획 +## 관련 기사 [#related-docs] - Lambda 함수에 대한 측정, 로그 및 설정을 시작하세요. 뉴렐릭를 사용하여 AWS Lambda 함수를 모니터링하는 방법을 알아보세요. + + 뉴렐릭의 계층적 접근 방식을 사용하여 Lambda 함수를 호출하세요. + + + + SDK를 사용하여 Lambda 함수를 코딩하세요. + + + + 뉴렐릭의 컨테이너화된 접근 방식으로 Lambda 함수를 호출하세요. + \ No newline at end of file diff --git a/src/i18n/content/kr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/containerized-images.mdx b/src/i18n/content/kr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/containerized-images.mdx index 3e3b77b7c66..84f9d1f281a 100644 --- a/src/i18n/content/kr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/containerized-images.mdx +++ b/src/i18n/content/kr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/containerized-images.mdx @@ -202,10 +202,34 @@ Lambda 함수에 컨테이너화된 이미지를 사용하고 런타임을 모 * [계층적 측정, 시각](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/instrument-your-own/#console) * [SDK 기반 측정, 물리](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/enable-serverless-monitoring-aws-lambda-layerless) + + + ### 데이터 찾기 및 사용 [#find-data] + + AWS Lambda 함수를 로그아웃한 후 뉴렐릭 APM 인터페이스에서 데이터를 찾아 사용할 수 있습니다. 데이터는 여러 주요 영역으로 구성되며, 각 영역은 Lambda 함수의 성능과 상태에 대한 다양한 정보를 제공합니다. + + APM 인터페이스에서는 [분산 추적](https://docs.newrelic.com/docs/distributed-tracing/concepts/introduction-distributed-tracing/), [서비스 맵](https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/ui-data/service-maps/service-maps/), [트랜잭션](https://docs.newrelic.com/docs/apm/transactions/intro-transactions/transactions-new-relic-apm//), [오류 분석](https://docs.newrelic.com/docs/errors-inbox/getting-started/) 등 Lambda 함수의 다양한 측면을 살펴볼 수 있습니다. 이러한 각 영역에서는 Lambda 함수의 성능, 지연 시간 및 오류율에 대한 자세한 내용을 제공하므로 문제를 신속하게 식별하고 해결할 수 있습니다. + + + 이제 호출 환경이 APM 프로세서 트레이스와 통합되었습니다. 이를 통해 특정 `AWS RequestId` 사용하여 APM 트레이스를 드릴다운하여 특정 Lambda 실행에 대한 자세한 정보를 얻을 수 있습니다. + + + 뉴렐릭 APM 인터페이스에서 Lambda 함수를 보려면: + + 1. [https://one.newrelic.com](https://one.newrelic.com) > APM & Services 으)로 이동합니다. + 2. 검색 기준을 `isLambdaFunction = true` 으로 설정합니다. + 3. 표시된 목록에서 Lambda 함수를 선택하여 데이터를 확인하세요. + -## 무엇 향후 계획 +## 관련 기사 [#related-docs] - 지원되는 런타임 및 필수 구성 요소에 대해 자세히 알아보세요. AWS Lambda 함수를 모니터링하는 데 뉴렐릭을 사용하는 방법을 알아보세요. 설치 관련 문제를 해결하는 방법을 알아보세요. + + 지원되는 런타임 및 필수 구성 요소에 대해 자세히 알아보세요. + + + + 설치 관련 문제를 해결하는 방법을 알아보세요 + \ No newline at end of file diff --git a/src/i18n/content/kr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda.mdx b/src/i18n/content/kr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda.mdx index 10ab9b09606..66a3cefa251 100644 --- a/src/i18n/content/kr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda.mdx +++ b/src/i18n/content/kr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda.mdx @@ -46,7 +46,7 @@ translationType: machine - 함수의 실제 핸들러를 찾는 데 사용되는 핸들러 래퍼를 지정합니다. + 함수의 실제 핸들러를 찾는 데 사용되는 핸들러 래퍼를 지정합니다. Go 런타임의 경우 이 변수는 필수가 아닙니다. @@ -60,6 +60,20 @@ translationType: machine + + + `NEW_RELIC_APM_LAMBDA_MODE` + + + + Lambda 함수에 대한 APM 모니터링을 활성화하려면 + + `true` + + 으로 설정하세요. + + + `NEW_RELIC_TRUSTED_ACCOUNT_KEY` @@ -1080,6 +1094,22 @@ translationType: machine , `DEBUG` + + , + + `TRACE` + + , + + `ERROR` + + , + + `WARN` + + , + + `ALL` @@ -1191,7 +1221,9 @@ translationType: machine - 문자열 내에 쉼표로 구분된 값을 제공하여 검사를 우회합니다. + **더 이상 사용되지 않습니다.** + + 문자열 내에서 쉼표로 구분된 값을 제공하여 검사를 우회합니다. `handler` @@ -1225,7 +1257,17 @@ translationType: machine - 라이선스 키가 포함된 AWS Secrets Manager의 비밀 키 이름을 지정합니다. 참고: 이것은 NEW_RELIC_LICENSE_KEY가 설정되지 않은 경우에만 사용됩니다. + AWS Secrets Manager에서 새 암호가 포함된 비밀의 **이름** 이나 **ARN을** 지정하세요. + +
+ +
+ + **메모:** + + * `` `NEW_RELIC_LICENSE_KEY` `` 이 설정되지 않은 경우에만 사용됩니다. + * 비밀번호는 Lambda 함수와 동일한 AWS 지역에 있어야 합니다. + * Lambda 함수의 실행 역할에는 이 비밀에 대한 `` `secretsmanager:GetSecretValue` `` 권한이 필요합니다. @@ -1239,7 +1281,31 @@ translationType: machine - 인스턴스 키가 포함된 AWS Systems Manager 시위 저장소에서 SSM 시위 이름을 지정합니다. 참고: 이것은 NEW_RIC_LICENSE_KEY가 설정되지 않은 경우에만 사용됩니다. + 사용자의 뉴렐릭 클러스터 키가 포함된 AWS Systems Manager 레지스트리 스토어에서 시위의 **이름** 또는 **ARN을** 지정합니다. + +
+ +
+ + **메모:** + + * `` `NEW_RELIC_LICENSE_KEY` `` 이 설정되지 않은 경우에만 사용됩니다. + * SSM 참가자는 Lambda 함수와 동일한 AWS 지역에 있어야 합니다. + * 귀하의 Lambda 함수 실행 역할에는 이 보고서에 대한 `` `ssm:GetParameter` `` 권한이 필요합니다. + + + + + + `NEW_RELIC_CLOUD_AWS_ACCOUNT_ID` + + + + + + + + 뉴렐릭가 모니터 부분 간의 관계를 올바르게 매핑하고 표시할 수 있도록 하려면 데이터베이스 및 Lambda 함수와 같은 모니터 리소스가 있는 AWS 계정 ID를 제공하세요. diff --git a/src/i18n/content/kr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own.mdx b/src/i18n/content/kr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own.mdx index db297bd7d77..55c0c3c5d2a 100644 --- a/src/i18n/content/kr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own.mdx +++ b/src/i18n/content/kr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own.mdx @@ -5,14 +5,13 @@ freshnessValidatedDate: never translationType: machine --- -뉴렐릭과 AWS 계정을 성공적으로 연결한 후에는 뉴렐릭 Lambda 계층을 추가하여 Lambda 함수를 호출할 수 있습니다. 이는 뉴렐릭 에이전트를 통합하여 함수가 호출될 때마다 자동 모니터링을 가능하게 합니다. +뉴렐릭 Lambda 레이어를 추가하여 Lambda 함수를 로그아웃할 수 있습니다. 이는 뉴렐릭 에이전트를 통합하여 함수가 호출될 때마다 자동 모니터링을 가능하게 합니다. a diagram depicting non-containerized lambda function instrumentation -## 시작하기 전에 [#begin] - -* [뉴렐릭와 AWS 계정을 연결하세요](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda#link) -* [다양한 계측 방법 검토](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda#method) + + 뉴렐릭은 [AWS 통합을](/docs/infrastructure/amazon-integrations/get-started/introduction-aws-integrations/) 사용하여AWS 계정을 뉴렐릭과 통합하여 Lambda 함수를 자동으로 검색하고 모니터링할 것을 권장합니다. 이를 통해 서버리스 기능에 뉴렐릭 APM 의 모든 기능을 활용할 수 있습니다. + ## 계측 방법 [#instrumentation] @@ -36,7 +35,7 @@ translationType: machine 뉴렐릭 레이어를 설치하거나 업그레이드하려면 다음 명령을 실행하세요. ```shell - newrelic-lambda layers install --nr-account-id YOUR_NR_ACCOUNT_ID --function my-function --upgrade + newrelic-lambda layers install --nr-account-id YOUR_NR_ACCOUNT_ID --function my-function --upgrade --apm ``` 이 명령은 Lambda의 리전 및 런타임에 대해 사용 가능한 최신 계층을 자동으로 찾습니다. @@ -51,112 +50,154 @@ translationType: machine CloudFormation은 AWS 리소스의 프로비저닝 및 관리를 단순화하는 AWS 서비스입니다. YAML 또는 JSON 템플릿에서 원하는 리소스 상태를 정의함으로써 CloudFormation은 기본 API 호출을 자동으로 처리하여 필요에 따라 리소스를 생성, 업데이트 또는 삭제합니다. 이 선언적 접근 방식은 인프라 관리를 자동화하여 일관성과 재현성을 보장합니다. - 다음은 Node.js Lambda 함수에 대한 간단한 CloudFormation 템플릿의 예입니다. - - ```yaml - AWSTemplateFormatVersion: '2010-09-09' - Transform: AWS::Serverless-2016-10-31 - Description: And example of a simple instrumented Node.js Lambda - - Resources: - NewRelicExample: - Type: AWS::Serverless::Function - Properties: - # In this example, we're using the SAM CLI to package and deploy our lambda. SAM will transform this value during the publish step. - CodeUri: newrelic-example-node/ - # The handler for your function needs to be the one provided by the instrumentation layer, below. - Handler: newrelic-lambda-wrapper.handler - Runtime: nodejs12.x - Environment: - Variables: - # For the instrumentation handler to invoke your real handler, we need this value - NEW_RELIC_LAMBDA_HANDLER: YOUR_PATH_TO_INITIAL_LAMBDA_HANDLER - # Distributed tracing needs your account ID, and your trusted account ID - NEW_RELIC_ACCOUNT_ID: YOUR_ACCOUNT_ID_HERE - # If your New Relic account has a parent account, this value should be that account ID. Otherwise, just - # your account id. - NEW_RELIC_TRUSTED_ACCOUNT_KEY: YOUR_PARENT_ACCOUNT_ID_HERE - Layers: - # This layer includes the New Relic Lambda extension, a sidecar process that sends telemetry, - # as well as the New Relic agent for Node.js, and a handler wrapper that makes integration easy. - - !Sub arn:${AWS::Partition}:lambda:${AWS::Region}:451483290750:layer:NewRelicNodeJS12X:34 - Policies: - # This policy allows the lambda to know the value of the New Relic license key. We need this so - # that we can send telemetry back to New Relic - - AWSSecretsManagerGetSecretValuePolicy: - SecretArn: !ImportValue NewRelicLicenseKeySecret-NewRelic-LicenseKeySecretARN - ``` - - 일반적으로 함수와 해당 리소스를 설명하는 `template.yaml` 이라는 파일이 있습니다. + 뉴렐릭으로 Lambda 함수를 모니터링하려면: + + 1. [뉴렐릭 Lambda 레이어를](https://layers.newrelic-external.com/) 설치합니다. 다음은 Node.js Lambda 함수에 대한 간단한 CloudFormation 템플릿의 예입니다. + + ```yaml + AWSTemplateFormatVersion: '2010-09-09' + Transform: AWS::Serverless-2016-10-31 + Description: And example of a simple instrumented Node.js Lambda + + Resources: + NewRelicExample: + Type: AWS::Serverless::Function + Properties: + # In this example, we're using the SAM CLI to package and deploy our lambda. SAM will transform this value during the publish step. + CodeUri: newrelic-example-node/ + # The handler for your function needs to be the one provided by the instrumentation layer, below. + Handler: newrelic-lambda-wrapper.handler + Runtime: nodejs22.x + Environment: + Variables: + # For the instrumentation handler to invoke your real handler, we need this value + NEW_RELIC_LAMBDA_HANDLER: YOUR_PATH_TO_INITIAL_LAMBDA_HANDLER + # Distributed tracing needs your account ID, and your trusted account ID + NEW_RELIC_ACCOUNT_ID: YOUR_ACCOUNT_ID_HERE + # If your New Relic account has a parent account, this value should be that account ID. Otherwise, just + # your account id. + NEW_RELIC_TRUSTED_ACCOUNT_KEY: YOUR_PARENT_ACCOUNT_ID_HERE + NEW_RELIC_APM_LAMBDA_MODE: 'true' + Tags: + # This tag is to enable APM mode. + NR.Apm.Lambda.Mode: true + Layers: + # This layer includes the New Relic Lambda extension, a sidecar process that sends telemetry, + # as well as the New Relic agent for Node.js, and a handler wrapper that makes integration easy. + - !Sub arn:${AWS::Partition}:lambda:${AWS::Region}:451483290750:layer:NewRelicNodeJS16X:103 + Policies: + # This policy allows the lambda to know the value of the New Relic license key. We need this so + # that we can send telemetry back to New Relic + - AWSSecretsManagerGetSecretValuePolicy: + SecretArn: !ImportValue NewRelicLicenseKeySecret-NewRelic-LicenseKeySecretARN + ``` + + 일반적으로 함수와 해당 리소스를 설명하는 `template.yaml` 이라는 파일이 있습니다. + + 2. 필요한 [환경 변수를](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) 구성합니다. + + 3. 업데이트된 설정으로 Lambda 함수를 구현하고 배포합니다. 서버리스 프레임워크는 서버리스 애플리케이션을 위한 널리 사용되는 개발 및 배포 도구입니다. Node.js에서 AWS용으로 작성되었으며 대부분 CloudFormation 템플릿 위에서 높은 수준의 추상화 역할을 합니다. Node, Python, Ruby, Java 및 .NET 함수에 적합합니다. - New Relic은 Serverless Framework 애플리케이션의 계측을 단순화하기 위해 [Serverless Framework 플러그인](https://github.com/newrelic/serverless-newrelic-lambda-layers) 을 제공합니다. + 뉴렐릭은 서버리스 프레임워크의 축소, 렌더링을 단순화하기 위한 서버Serverless [Serverless 워크 기능을](https://github.com/newrelic/serverless-newrelic-lambda-layers) 제공합니다. + + **필수 조건:** + + * Serverless 프레임워크를 사용하는 기존의 창작물입니다. + * [New Relic 계정 아이디](/docs/accounts/accounts-billing/account-structure/account-id) + * [뉴렐릭 개인 API 키](/docs/apis/intro-apis/new-relic-api-keys) + + **뉴렐릭을 사용하여 Serverless 프레임워크를 설치하고 구성하려면:** - 플러그인을 설치하려면 다음 명령을 실행하세요. + 1. `npm` 사용하는 경우 다음 명령을 실행하세요. ```bash - npm install --save-dev serverless-newrelic-lambda-layers + npm install --save-dev serverless-newrelic-lambda-layers ``` - 또는 다음 명령을 실행할 수도 있습니다. + 또는 `yarn` 사용하는 경우 다음 명령을 실행합니다. ```bash - yarn add --dev serverless-newrelic-lambda-layers + yarn add --dev serverless-newrelic-lambda-layers ``` - 그런 다음, [뉴렐릭 계정 ID](/docs/accounts/install-new-relic/account-setup/account-id), [뉴렐릭 개인 API 키를](/docs/apis/get-started/intro-apis/types-new-relic-api-keys#personal-api-key)찾으세요. + 2. `serverless.yaml` 파일을 열고 다음 설정을 추가하세요. - 이제 `serverless.yaml` 파일에 다음을 추가합니다. + 1. `plugins` 목록에 `serverless-newrelic-lambda-layers` 추가합니다. - ```yaml - plugins: - - serverless-newrelic-lambda-layers - custom: - newRelic: - accountId: your-new-relic-account-id-here - apiKey: your-new-relic-personal-api-key-here - linkedAccount: your-new-relic-integration-account-name-here - ``` + 2. 사용자 정의 섹션에 다음 뉴렐릭 설정을 추가하세요: + + ```yaml + plugins: + - serverless-newrelic-lambda-layers + custom: + newRelic: + accountId: your-new-relic-account-id-here + apiKey: your-new-relic-personal-api-key-here + linkedAccount: your-new-relic-integration-account-name-here + apm: true + ``` + + 3. 공급자 섹션에 다음 `NR.Apm.Lambda.Mode: true` 태그를 추가합니다. + + ```yaml + provider: + tags: + NR.Apm.Lambda.Mode: true + ``` + + 3. 필요한 [환경 변수를](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) 구성합니다. + + 4. 업데이트된 설정으로 Lambda 함수를 구현하고 배포합니다. AWS 클라우드 개발 키트(AWS CDK)는 코드로 클라우드 리소스를 정의하고 AWS CloudFormation을 통해 프로비저닝하기 위한 프레임워크입니다. - 다음은 Node.js Lambda 함수를 구현하고 배포하는 기본 CDK 앱의 예입니다. - - ```ts - import * as cdk from 'aws-cdk-lib'; - import { Construct } from 'constructs'; - import * as lambda from 'aws-cdk-lib/aws-lambda'; - - export class NewRelicExampleCdkStack extends cdk.Stack { - constructor(scope: Construct, id: string, props?: cdk.StackProps) { - super(scope, id, props); - // Add latest New Relic Lambda layer ARN from https://layers.newrelic-external.com - const NewReliclayerArn = 'arn:aws:lambda:us-east-1:451483290750:layer:NewRelicNodeJS20X:39'; - const myFunction = new lambda.Function(this, "NewRelicExampleLambda", { - runtime: lambda.Runtime.NODEJS_20_X, - // Update functions handler to point to the New Relic Lambda wrapper - handler: "newrelic-lambda-wrapper.handler", - code: lambda.Code.fromAsset('lib/lambda-runtime-code'), - layers: [lambda.LayerVersion.fromLayerVersionArn(this, 'NewRelicLayer', NewReliclayerArn)], - environment: { - // Set the NEW_RELIC_LAMBDA_HANDLER environment variable to the path of your initial handler. - NEW_RELIC_LAMBDA_HANDLER: 'index.handler', - }, - }); - } - } - ``` + AWS CDK에서 뉴렐릭을 사용하려면 다음 단계를 따르세요. + + 1. [뉴렐릭 Lambda 레이어를](https://layers.newrelic-external.com/) 설치합니다. 다음은 Node.js Lambda 함수를 구현하고 배포하는 기본 CDK 앱의 예입니다. + + ```ts + import * as cdk from 'aws-cdk-lib'; + import { Construct } from 'constructs'; + import * as lambda from 'aws-cdk-lib/aws-lambda'; + + export class NewRelicExampleCdkStack extends cdk.Stack { + constructor(scope: Construct, id: string, props?: cdk.StackProps) { + super(scope, id, props); + // Add latest New Relic Lambda layer ARN from https://layers.newrelic-external.com + const NewReliclayerArn = 'arn:aws:lambda:us-east-1:451483290750:layer:NewRelicNodeJS22X:38'; + const myFunction = new lambda.Function(this, "NewRelicExampleLambda", { + runtime: lambda.Runtime.NODEJS_20_X, + // Update functions handler to point to the New Relic Lambda wrapper + handler: "newrelic-lambda-wrapper.handler", + code: lambda.Code.fromAsset('lib/lambda-runtime-code'), + layers: [lambda.LayerVersion.fromLayerVersionArn(this, 'NewRelicLayer', NewReliclayerArn)], + environment: { + // Set the NEW_RELIC_LAMBDA_HANDLER environment variable to the path of your initial handler. + NEW_RELIC_LAMBDA_HANDLER: 'index.handler', + NEW_RELIC_APM_LAMBDA_MODE: 'true' + }, + }); + // Add the New Relic APM Lambda Mode tag + cdk.Tags.of(myFunction).add('NR.Apm.Lambda.Mode', 'true'); + } + } + ``` + + 2. 필요한 [환경 변수를](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) 구성합니다. + + 3. 업데이트된 설정으로 Lambda 함수를 구현하고 배포합니다. Terraform은 코드 도구로서 널리 사용되는 범용 인프라입니다. AWS 리소스를 관리하는 데 사용할 수 있습니다. 우리는 Terraform 펼쳐보기를 사용하여 뉴렐릭 권한이 있는 Lambda 함수 구현, 배포의 [몇 가지 예를](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/terraform) 제공합니다. - [뉴렐릭 Terraform 공급자를](https://registry.terraform.io/providers/newrelic/newrelic/latest/docs/resources/cloud_aws_integrations) 사용하여 AWS 통합을 설정할 수 있습니다. + [새로운 Terraform 공급자를](https://registry.terraform.io/providers/newrelic/newrelic/latest/docs/resources/cloud_aws_integrations) 사용하여 AWS 통합을 설정할 수 있습니다. 공급자를 설정한 후 필요한 [환경 변수를](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) 구성하고 Lambda 함수에 `NR.Apm.Lambda.Mode: true` 태그를 추가합니다. @@ -210,6 +251,10 @@ translationType: machine 뉴렐릭 레이어는 뉴렐릭 루비 에이전트를 자동으로 전달하고 Lambda 함수 호출 전에 루비 `require` 를 통해 로드됩니다. 충돌을 피하려면 다른 곳에 루비 에이전트 사본을 포함하지 마세요. 에이전트의 존재를 활용하려면 함수 내에서 원하는 뉴렐릭 루비 에이전트 API 호출을 자유롭게 수행하세요. + 14. AWS Management Console의 설정 탭에서 Lambda 함수에 `NR.Apm.Lambda.Mode: true` 태그를 추가하세요. + + 15. 업데이트된 설정으로 Lambda 함수를 구현하고 배포합니다. + Java, Python, Node.js 및 .Net 런타임은 루비와 동일한 소비 흐름을 따르지만 일부 다른 핸들러를 사용합니다. 함수 콘솔에서 새로 연결된 레이어를 가리키도록 함수 핸들러를 업데이트하는 방법은 다음과 같습니다. * 자바: @@ -230,26 +275,32 @@ translationType: machine -## 배송 방법 +## 데이터 찾기 및 사용 [#find-data] - - - 모든 에이전트 레이어에는 CloudWatch를 우회하여 로그인 및 페이로드를 뉴렐릭으로 보내기 위한 확장 기능도 포함되어 있습니다. 이는 지연 시간과 비용을 줄이는 데 도움이 될 수 있습니다. 그러나 기능의 성능과 안정성에 영향을 미칠 위험이 있습니다. +AWS Lambda 함수를 로그아웃한 후 뉴렐릭 APM 인터페이스에서 데이터를 찾아 사용할 수 있습니다. 데이터는 여러 주요 영역으로 구성되며, 각 영역은 Lambda 함수의 성능과 상태에 대한 다양한 정보를 제공합니다. - 뉴렐릭 Lambda 레이어를 추가하면 확장 기능이 활성화되고 기본적으로 로그 전달이 비활성화됩니다. +APM 인터페이스에서는 [분산 추적](/docs/distributed-tracing/concepts/introduction-distributed-tracing/), [서비스 맵](/docs/new-relic-solutions/new-relic-one/ui-data/service-maps/service-maps/), [트랜잭션](/docs/apm/transactions/intro-transactions/transactions-new-relic-apm/), [오류 분석](/docs/errors-inbox/getting-started/) 등 Lambda 함수의 다양한 측면을 살펴볼 수 있습니다. 이러한 각 영역에서는 Lambda 함수의 성능, 지연 시간 및 오류율에 대한 자세한 정보를 제공하므로 문제를 신속하게 식별하고 해결할 수 있습니다. - 뉴렐릭에서 함수 로그를 보려면 환경 변수를 사용하여 함수 로그의 확장 전송을 활성화해야 합니다. + + 이제 호출 환경이 APM 프로세서 트레이스와 통합되었습니다. 이를 통해 특정 `AWS RequestId` 사용하여 APM 트레이스를 드릴다운하여 특정 Lambda 실행에 대한 자세한 정보를 얻을 수 있습니다. + - 함수 로그는 함수가 호출되는 동안 기록된 로그일 뿐이라는 점을 기억하는 것이 중요합니다. 확장 프로그램은 `START`, `END` 및 `REPORT` 줄과 같은 Lambda 런타임 로그를 보내지 않습니다. - +뉴렐릭 APM 인터페이스에서 Lambda 함수를 보려면: - - CloudWatch에만 데이터를 보내거나 대체 수단으로 보낼 수 있습니다. 자세한 내용은 [CloudWatch 대체 설명서를](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/cloud-watch-fallback) 참조하세요. - - +1. [https://one.newrelic.com](https://one.newrelic.com) > APM & Services 으)로 이동합니다. -## 무엇 향후 계획 +2. 검색 기준을 `isLambdaFunction = true` 으로 설정합니다. + +3. 표시된 목록에서 Lambda 함수를 선택하여 데이터를 확인하세요. + +## 관련 기사 [#related-docs] - 지원되는 런타임 및 필수 구성 요소에 대해 자세히 알아보세요. AWS Lambda 함수를 모니터링하는 데 뉴렐릭을 사용하는 방법을 알아보세요. 설치 관련 문제를 해결하는 방법을 알아보세요. + + 지원되는 런타임 및 필수 구성 요소에 대해 자세히 알아보세요. + + + + 설치 관련 문제를 해결하는 방법을 알아보세요 + \ No newline at end of file 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 e9edb835356..b7f57acfa3c 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 @@ -7,40 +7,155 @@ translationType: machine 뉴렐릭의 측정, AWS Lambda 용 리뷰는 함수의 내부 작동에 대한 심층적인 가시성을 제공합니다. 뉴렐릭 에이전트를 함수에 추가하면 각 호출이 뉴렐릭의 모니터가 됩니다. 이를 통해 함수 호출 기간을 추적하고, 오류를 모니터링하고, 소스 이벤트와 함수 응답에 대한 세부 정보를 기록할 수 있습니다. -new-relic-lambda-entities-screenshot.png +/\* AWS Lambda 확장성이 뛰어난 이벤트 중심 컴퓨트 서비스를 제공하므로 서버를 프로비저닝하거나 관리할 필요 없이 디버그 및 백앤드 서비스를 구축하고 실행할 수 있습니다. Lambda 기반 서버리스 프레임워크가 정교해지고 비즈니스에 중요한 역할을 수행함에 따라 더 광범위한 애플리케이션 생태계 내에서 성능, 운영 상태 및 전략에 대한 포괄적인 가시성을 확보하는 것이 안정성과 효율성을 유지하는 데 필수적입니다. 최신 애플리케이션은 다양한 다른 마이크로서비스, 데이터베이스 및 타사 API와 상호 작용하는 수많은 AWS Lambda 함수에 크게 의존합니다. 이처럼 복잡한 환경에서는 다음과 같은 여러 가지 문제에 직면할 수 있습니다. \* \*\*근본 원인 파악의 어려움:\*\* 성능 간헐적인 속도 저하와 같은 문제가 발생하거나 Lambda 함수와 관련된 중요한 트랜잭션이 실패하는 경우, 오류가 발생한 정확한 함수나 문제의 근원을 식별하는 것은 복잡한 퍼즐이 될 수 있습니다. \* \*\*사일로화된 모니터링 뷰:\*\* 전용 서버리스 모니터링 UI와 기존 애플리케이션 성능 모니터링(APM) 뷰 사이를 이동해야 할 수 있으며, 이로 인해 성능에 대한 단일하고 통합된 그림을 얻기 어려울 수 있습니다. \* \*\*효과적이지 않은 데이터 상관 관계:\*\* 정보가 별도의 서버리스 및 APM 모니터링 시스템에 있는 경우 성능 데이터와 이벤트를 효과적으로 상관시키는 것이 어려울 수 있습니다. \* \*\*완전하지 않은 엔드투엔드 추적:\*\* 분산 환경 내의 Lambda 함수와 다른 서비스를 통과하면서 단일 요청을 엔드투엔드로 원활하게 추적하는 데 어려움이 있을 수 있습니다. \* \*\* Lambda 에 대한 제한된 모니터링:\*\* APM 도구의 전체 진단 기능과 익숙한 기능을 Lambda 함수에 직접 적용할 수 없는 경우가 많습니다. \* \*\*인사이트에 대한 수동 작업:\*\* Lambda 와 관련된 문제의 전체 맥락을 이해하기 위해 다양한 출처의 서로 다른 정보를 조각해 모으려면 상당한 수동 작업이 필요한 경우가 많습니다. 이러한 옵저빌리버티 과제를 해결하고 진정한 통합 모니터링 경험을 제공하기 위해 뉴렐릭은 AWS Lambda 함수가 우리 플랫폼에 통합되는 방식을 개선하고 있습니다. 이 이니셔티브는 귀하의 서버리스 기능을 뉴렐릭 APM 환경으로 직접 가져와 다른 계측된 서비스와 함께 일류 시민으로 취급합니다. 우리의 목표는 Lambda 함수에 대한 풍부한 기능 인식 함수를 제공하여 전체 상황에서 성능을 그 어느 때보다 쉽게 이해할 수 있도록 하는 것입니다. \*/ -## Lambda 텔레메트리의 배송 방법 [#shipping-methods] +## 주요 특징들 [#key-features] -AWS Lambda 에서 뉴렐릭으로 텔레메트리 데이터를 배송하는 세 가지 주요 방법이 있으며, 각 방법마다 비용과 안정성 고려 사항이 다릅니다. +* **통합된 뷰 확보:** 다른 서비스에 사용하는 것과 동일한 APM 인터페이스 내에서 Lambda 함수를 모니터링하세요. 성능 지표, 트레이스, 로그(구성된 경우) 및 오류를 포함한 서버리스 텔레메트리를 모두 한 곳에서 상호 연관시켜 서로 다른 UI 간에 전환할 필요가 없도록 합니다. -* **비용 효율적인 방법**: Lambda 확장을 포함하여 뉴렐릭의 계층을 활용하면 기본적으로 AWS CloudWatch로 데이터를 전송하지 않아도 됩니다. -* **안정성 중심 방법**: Lambda 확장 기능을 비활성화하고 CloudWatch를 독점적으로 사용하여 데이터를 전송하여 Lambda 함수의 오버헤드를 줄입니다. -* **하이브리드 방식**: 확장 기능을 CloudWatch와 폴백으로 결합하여 비용 효율성과 안정성의 균형을 맞춥니다. +* **APM 의 모든 기능을 활용하세요.** 포괄적인 뉴렐릭 APM 기능 모음을 Lambda 함수에 직접 적용하세요. 여기에는 고급 거부 추적, 마우스 인박스(errors inbox)를 통한 상세한 오류 분석, Lambda 데칼, 소니 대시보드 등을 통합한 서비스 맵이 포함됩니다. 자세한 내용은 [APM 설명서를](https://docs.newrelic.com/docs/apm/new-relic-apm/getting-started/introduction-apm/) 참조하세요. -## 비용 고려 [#costs] +* **완벽한 엔드투엔드 요청 추적 달성:** 프런트엔드 서비스 또는 기타 마이크로서비스에서 AWS Lambda 함수를 통해 연결된 구성 요소로 전달되는 requests 원활하게 트레이스합니다. 이는 전체에 걸쳐 요청 지연 시간 및 의존성/종속성에 대한 명확하고 중단 없는 그림을 제공합니다. 자세한 내용은 [분산 추적 문서를](https://docs.newrelic.com/docs/distributed-tracing/concepts/introduction-distributed-tracing/) 참조하세요. -AWS Lambda에 대한 서버리스 모니터링을 구현하면 추가 AWS 요금이 발생할 수 있습니다. 데이터를 뉴렐릭에 보고하는 `newrelic-log-ingestion` Lambda 함수는 타사 서비스로 간주되며, 관련된 모든 AWS 요금은 사용자가 책임져야 합니다. +* **근본 원인 분석 간소화:** APM 에서 서버리스 데이터를 나머지 애플리케이션 데이터와 통합하면 Lambda 함수 또는 업스트림/다운스트림 서비스에서 발생한 문제를 신속하게 식별하고 진단할 수 있습니다. -[뉴렐릭 Lambda](https://github.com/newrelic/newrelic-lambda-layers) Layers 에 포함된 [newrelic-lambda-extension을 사용하면](https://github.com/newrelic/newrelic-lambda-extension) [CloudWatch와 newrelic-log-ingestion](https://github.com/newrelic/aws-log-ingestion) 함수를 통해 로그와 텔레메트리를 전송하지 않아도 됩니다. 옵저버빌리티 데이터의 고가용성이 필요한 함수에 대한 [CloudWatch 대체](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/cloud-watch-fallback/) [방법으로 newrelic-log-ingestion](https://github.com/newrelic/aws-log-ingestion) 함수를 구성하는 것도 가능합니다. +* **서버리스의 영향을 더 잘 이해하세요.** Lambda 함수가 애플리케이션 및 주요 비즈니스 거래의 전반적인 상태와 성능에 어떻게 기여하는지 명확하게 파악하여 디지털 서비스 내에서 해당 함수의 역할을 더 깊이 있게 이해하세요. + +New Relic Lambda Entities in APM + +## AWS Lambda 모니터링을 어떻게 구성할 수 있나요? [#config] + +뉴렐릭으로 AWS Lambda 모니터링하려면 다양한 환경, 런타임, 구현, 배포 메서드 전반에 걸쳐 측정, 리소스를 구성할 수 있습니다. 다음 단계는 설정 과정을 안내합니다. + + + + ### 호환성 및 요구 사항 [#req] + + AWS Lambda가 [호환성과 요구 사항을](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/compatibility-requirement-lambda-monitoring) 충족하는지 확인하세요. + + + + ### (선택 사항) AWS 계정을 뉴렐릭에 연결하세요 [#link] + + 계정을 연결하면 AWS 계정 인벤토리를 생성하고 Lambda 함수에 대한 CloudWatch 지표를 자동으로 수집할 수 있는 권한이 부여됩니다. 계정을 연결한 후에는 AWS 계정의 리소스가 [저널 탐색기](/docs/new-relic-solutions/new-relic-one/core-concepts/new-relic-explorer-view-performance-across-apps-services-hosts/#find) 에 저널로 표시됩니다. Lambda 부분 부분은 서버리스 기능 보기에서 찾을 수 있습니다. + + 다음 통합 방법 중 하나를 사용하여 AWS 와 뉴럴릭 계정을 연결할 수 있습니다. + + + + AWS Metric Streams(권장) API 폴링 + + + + + 뉴렐릭이 Lambda 함수를 모니터링하려면 뉴렐릭과 AWS 간의 통합을 설정해야 합니다. 지연시간을 줄이고 폴링 requests 제한을 방지하려면 [지표 스트림을](/install/aws-cloudwatch) 사용하는 것이 좋습니다. + + + + 지표 스트림 통합을 사용하지 않는 경우 대신 [API 폴링](/docs/infrastructure/amazon-integrations/connect/set-up-aws-api-polling) 통합을 설정할 수 있습니다. 기본적으로 Lambda 서비스와 API 폴링 통합을 활성화하면 5분마다 CloudWatch 지표를 폴링합니다. + + [newrelic-lambda-cli를](https://github.com/newrelic/newrelic-lambda-cli) 사용하면 API 폴링 통합을 설정할 수 있지만 지표 스트림 통합은 설정할 수 없습니다. + + ```sh + newrelic-lambda integrations install --nr-account-id YOUR_NR_ACCOUNT_ID \ + --nr-api-key YOUR_NEW_RELIC_USER_KEY + ``` + + [통합 설치 명령](https://github.com/newrelic/newrelic-lambda-cli?tab=readme-ov-file#aws-lambda-integration) 의 한 단계는 보안을 강화하기 위해 [AWS Secrets Manager](https://aws.amazon.com/secrets-manager/) 에 `NEW_RELIC_LICENSE_KEY` 비밀을 생성합니다. 이것은 다른 옵션 및 플래그와 함께 `--disable-license-key-secret` 플래그로 구성할 수 있습니다. + + + + + + + ### AWS Lambda 함수를 호출하세요 [#instrument] + + Lambda 함수를 사용하려면 에이전트와 확장 기능이 필요합니다. 이러한 구성 요소는 뉴렐릭 [Lambda 계층](https://github.com/newrelic/newrelic-lambda-layers) 에 함께 묶여 있습니다. Lambda 계층을 사용할 수 없는 경우 에이전트와 확장 기능을 수동으로 함수에 통합할 수 있습니다. Lambda 함수의 요구 사항에 따라 다음 계측 방법 중 하나를 선택하세요. + + + + 계층화된 측정, 로그아웃 SDK 기반 측정, 컨테이너화된 측정, 리소스 + + + + + Lambda 함수가 Zip 파일로 패키징되어 있고 레이어를 추가할 수 있는 경우 이 방법을 사용하세요. 레이어는 라이브러리, 사용자 정의 런타임 및 기타 의존성/종속성을 위한 배포 메커니즘입니다. 자세한 내용은 [Layered 측정, 로그](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own/) 문서를 참조하세요. + + + + Lambda 함수에서 레이어를 사용할 수 없는 경우 이 방법을 사용하면 레이어를 수정할 필요 없이 빠르게 구현하고 배포할 수 있습니다. 자세한 내용은 [SDK 기반 측정, 로그](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/sdk-based-instrumentation/) 문서를 참조하세요. + + + + Lambda 함수가 컨테이너 내부에서 실행되는 경우 이 방법을 사용하세요. 컨테이너는 애플리케이션에 일관되고 격리된 실행 환경을 제공합니다. 뉴렐릭은 뉴렐릭 Lambda 레이어, 뉴렐릭 Lambda 확장 프로그램 및 뉴렐릭 에이전트를 포함하는 사전 구축된 도커 이미지를 제공합니다. 자세한 내용은 [컨테이너화된 측정, 계측](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/containerized-images/) 문서를 참조하세요. + + + + + + + ### 환경 변수 구성 [#env-variables] + + + * CLI를 사용하여 Lambda 계층을 계측하는 경우, 필수 환경 변수가 자동으로 구성됩니다. 그러나 일부 기본 설정을 변경하고 모니터링 요구 사항에 맞는 환경 변수로 Lambda 함수를 구성하고 싶을 수도 있습니다. + * New Relic Lambda 확장 프로그램을 사용하는 경우 환경 변수를 수동으로 구성해야 합니다. + + + [환경 변수는](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) 뉴렐릭 에이전트 및 Lambda 확장을 구성하는 데 사용됩니다. Lambda 함수가 올바르게 모니터링되도록 하려면 이러한 변수를 올바르게 설정하는 것이 중요합니다. + + + + ### 뉴렐릭에서 데이터 찾기 [#data] + + AWS Lambda 함수를 로그아웃한 후 뉴렐릭 APM 인터페이스에서 데이터를 찾아 사용할 수 있습니다. 데이터는 여러 주요 영역으로 구성되며, 각 영역은 Lambda 함수의 성능과 상태에 대한 다양한 정보를 제공합니다. + + + +## 예제 함수를 사용해 보세요 [#example] + +로그된 뉴렐릭의 Lambda 레이어를 사용한 후에는 예제 함수를 시험해 볼 것을 강력히 권장합니다. 이러한 작업 예제는 사용자 서버리스 기능의 시작점으로 사용되어야 합니다. 이러한 예제를 사용하면 뉴렐릭 Lambda 레이어에 익숙해지고 계정 링크를 테스트하는 데 도움이 될 수 있으며 자체 로그에 대한 참조로 사용할 수 있습니다. 각 예에서는 권한 추가, 핸들러 래핑을 위한 런타임별 기술, CloudWatch에서 함수 로그 보존 관리 등을 보여줍니다. + +배포하다 Lambda 함수를 관리하고 구현하는 방법에는 여러 가지가 있지만, AWS CloudFormation은 예제에 사용하는 메커니즘입니다. + +우리의 예제는 뉴렐릭 Lambda Extension과 함께 이 [GitHub](https://github.com/newrelic/newrelic-lambda-extension) 에 게시되어 있습니다. 뉴렐릭이 지원하는 각 Lambda 런타임마다 하나씩 있습니다. + +* [노드.js](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/sam/node) +* [파이썬](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/sam/python) +* [가다](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/sam/go) +* [자바](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/sam/java) +* [루비](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/sam/ruby) +* [.그물](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/sam/dotnet) + +또한 우리의 [수신 거부 예제](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/sam/distributedtracing) 에서 서버리스 서버리스로 작업을 수행하는 방법을 배울 수 있습니다. Node, Python, Ruby 및 Java 기능을 사용하여 Lambda 함수를 호출할 수 있는 가장 인기 있는 두 가지 서비스인 SQS 및 SNS에 대한 수동 트레이스 전파를 보여줍니다. - 어떤 배송 방법을 사용하시든, 뉴렐릭의 페이로드와 경험은 동일하게 유지됩니다. + 수동으로 테스트하는 경우 텔레메트리 데이터가 지연될 수 있습니다. 함수를 다시 호출하기 전에 7초 동안 기다려서 버퍼링된 모든 텔레메트리가 전달될 수 있도록 하는 것이 좋습니다. -AWS Lambda에 대한 서버리스 모니터링을 활성화하면 Amazon Web Services 요금이 발생할 수 있습니다. 귀하의 Lambda 데이터를 당사에 보고하는 당사의 `newrelic-log-ingestion` Lambda 함수는 [제3자 서비스](/docs/licenses/license-information/acceptable-use-policy/acceptable-use-policy) 로 간주됩니다. 귀하가 이를 사용하여 발생하는 AWS 요금은 귀하의 책임입니다. +## 비용 고려 [#costs] + +AWS Lambda에 대한 서버리스 모니터링을 구현하면 추가 AWS 요금이 발생할 수 있습니다. 데이터를 뉴렐릭에 보고하는 `newrelic-log-ingestion` Lambda 함수는 타사 서비스로 간주되며, 관련된 모든 AWS 요금은 사용자의 책임입니다. [뉴렐릭 Lambda 계층 에](https://github.com/newrelic/newrelic-lambda-layers) [`newrelic-lambda-extension`](https://github.com/newrelic/newrelic-lambda-extension) 포함된 을 사용하면 CloudWatch를 통해 로그 및 텔레메트리데이터를 전송하지 않아도 되지만, 고가용성 `newrelic-log-ingestion` 요구 사항에 맞게 함수를 CloudWatch 폴백으로 구성하는 것도 가능합니다. + +AWS Lambda에 대한 서버리스 모니터링을 활성화하면 Amazon Web Services 요금이 부과될 수 있습니다. 귀하의 Lambda 데이터를 당사에 보고하는 당사의 `newrelic-log-ingestion` Lambda 함수는 [제3자 서비스](/docs/licenses/license-information/general-usage-licenses/acceptable-use-policy) 로 간주됩니다. 귀하가 해당 함수를 사용함으로써 발생하는 AWS 요금은 귀하의 책임입니다. + +[뉴렐릭 Lambda](https://github.com/newrelic/newrelic-lambda-layers) Layers 에 포함된 [newrelic-lambda-extension을 사용하면](https://github.com/newrelic/newrelic-lambda-extension) [CloudWatch와 newrelic-log-ingestion](https://github.com/newrelic/aws-log-ingestion) 함수를 통해 로그와 텔레메트리를 전송하지 않아도 됩니다. 옵저버빌리티 데이터의 고가용성이 필요한 함수에 대한 [CloudWatch 대체](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/cloud-watch-fallback/) [방법으로 newrelic-log-ingestion](https://github.com/newrelic/aws-log-ingestion) 함수를 구성하는 것도 가능합니다. + +## 가격 [#pricing] + +뉴렐릭 APM + Serverless Convergence 사용은 주문에 따라 APM 으로 청구됩니다. 가격에 대한 자세한 내용은 당사 영업팀에 문의하시거나 주문서를 참조하세요. -## 무엇 향후 계획 +## 관련 기사 [#related-docs] - - 지원되는 런타임 및 필수 구성 요소에 대해 자세히 알아보세요. + + 뉴렐릭의 계층적 접근 방식을 사용하여 Lambda 함수를 호출하세요. - - Lambda 함수에 대한 측정, 로그 및 설정 시작하기 + + SDK를 사용하여 Lambda 함수를 코딩하세요. - - 뉴렐릭을 사용하여 AWS Lambda 함수를 모니터링하는 방법을 알아보세요. + + 뉴렐릭의 컨테이너화된 접근 방식으로 Lambda 함수를 호출하세요. \ No newline at end of file diff --git a/src/i18n/content/kr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/sdk-based-instrumentation.mdx b/src/i18n/content/kr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/sdk-based-instrumentation.mdx index 2df8d1b5c50..78a621dfcf1 100644 --- a/src/i18n/content/kr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/sdk-based-instrumentation.mdx +++ b/src/i18n/content/kr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/sdk-based-instrumentation.mdx @@ -67,9 +67,11 @@ SDK 기반 측정을 수행하려면 선택한 런타임에 대한 SDK로 뉴렐 - 5. [분산 추적을](/docs/apm/distributed-tracing/getting-started/introduction-distributed-tracing) 활성화하고 환경 변수를 구성하려면 [환경 변수](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) 설명서를 참조하세요. + 5. [환경 변수를](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) 구성합니다. - 6. Lambda를 한 번 이상 호출합니다. 그러면 다음 단계가 작동하기 위해 있어야 하는 CloudWatch 로그 그룹이 생성됩니다. + 6. AWS Management Console의 설정 탭에서 Lambda 함수에 `NR.Apm.Lambda.Mode: true` 태그를 추가하세요. + + 7. Lambda를 한 번 이상 호출합니다. 그러면 다음 단계가 작동하기 위해 있어야 하는 CloudWatch 로그 그룹이 생성됩니다. 래퍼는 Lambda 실행에 대한 데이터를 수집하고 JSON 메시지를 생성하여 CloudWatch Logs에 기록합니다. 그런 다음 [해당 로그를 New Relic 으로 보내도록 CloudWatch를 구성합니다](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/instrument-your-own/#manual-stream-logs) . @@ -130,9 +132,11 @@ SDK 기반 측정을 수행하려면 선택한 런타임에 대한 SDK로 뉴렐 6. AWS Lambda 콘솔에서 핸들러를 설정합니다. [예제 Java Lambda](https://github.com/newrelic/newrelic-lambda-tracer-java#usage) 의 경우 핸들러는 `com.handler.example.MyLambdaHandler::handleRequest` 입니다. `handleRequest` 이 가정되기 때문에 `com.handler.example.MyLambdaHandler` 를 사용할 수도 있습니다. - 7. [분산 추적을](/docs/apm/distributed-tracing/getting-started/introduction-distributed-tracing) 활성화하고 환경 변수를 구성하려면 [환경 변수](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) 설명서를 참조하세요. + 7. [환경 변수를](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) 구성합니다. + + 8. AWS Management Console의 설정 탭에서 Lambda 함수에 `NR.Apm.Lambda.Mode: true` 태그를 추가하세요. - 8. Lambda를 한 번 이상 호출합니다. 그러면 다음 단계가 작동하기 위해 있어야 하는 CloudWatch 로그 그룹이 생성됩니다. + 9. Lambda를 한 번 이상 호출합니다. 그러면 다음 단계가 작동하기 위해 있어야 하는 CloudWatch 로그 그룹이 생성됩니다. 래퍼는 Lambda 실행에 대한 데이터를 수집하고 JSON 메시지를 생성하여 CloudWatch Logs에 기록합니다. 그런 다음 [해당 로그를 New Relic 으로 보내도록 CloudWatch를 구성합니다](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/instrument-your-own/#manual-stream-logs) . @@ -211,9 +215,11 @@ SDK 기반 측정을 수행하려면 선택한 런타임에 대한 SDK로 뉴렐 5. 압축된 파일을 AWS Lambda 계정에 업로드합니다. - 6. [분산 추적을](/docs/apm/distributed-tracing/getting-started/introduction-distributed-tracing) 활성화하고 환경 변수를 구성하려면 [환경 변수](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) 설명서를 참조하세요. + 6. [환경 변수를](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) 구성합니다. + + 7. AWS Management Console의 설정 탭에서 Lambda 함수에 `NR.Apm.Lambda.Mode: true` 태그를 추가하세요. - 7. HTML을 완료하려면 다음 단계 중 하나를 수행하여 스프레드시트 데이터를 뉴렐릭으로 보내세요. + 8. HTML을 완료하려면 다음 단계 중 하나를 수행하여 스프레드시트 데이터를 뉴렐릭으로 보내세요. * 뉴렐릭 Lambda `Extension layer` 를 사용하세요. 최신 [(NewRelicLambdaExtension)](https://layers.newrelic-external.com/) 레이어 arn을 가져올 수 있습니다. AWS CLI를 사용하여 계층을 설치하거나 Lambda에 수동으로 추가할 수 있습니다. @@ -269,9 +275,11 @@ SDK 기반 측정을 수행하려면 선택한 런타임에 대한 SDK로 뉴렐 6. 압축된 파일을 AWS Lambda 계정에 업로드합니다. - 7. [분산 추적을](/docs/apm/distributed-tracing/getting-started/introduction-distributed-tracing) 활성화하고 환경 변수를 구성하려면 [환경 변수](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) 설명서를 참조하세요. + 7. [환경 변수를](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) 구성합니다. - 8. Lambda를 한 번 이상 호출합니다. 그러면 다음 단계가 작동하기 위해 있어야 하는 CloudWatch 로그 그룹이 생성됩니다. + 8. AWS Management Console의 설정 탭에서 Lambda 함수에 `NR.Apm.Lambda.Mode: true` 태그를 추가하세요. + + 9. Lambda를 한 번 이상 호출합니다. 그러면 다음 단계가 작동하기 위해 있어야 하는 CloudWatch 로그 그룹이 생성됩니다. New Relic 데코레이터는 Lambda 실행에 대한 데이터를 수집하고 JSON 메시지를 생성하여 CloudWatch Logs에 기록합니다. 그런 다음 [해당 로그를 New Relic 으로 보내도록 CloudWatch를 구성합니다](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/instrument-your-own/#manual-stream-logs) . @@ -282,25 +290,38 @@ SDK 기반 측정을 수행하려면 선택한 런타임에 대한 SDK로 뉴렐 .NET Lambda를 리뷰하려면: 1. [프로젝트에 NewRelic.에이전트 nuget 패키지를](https://www.nuget.org/packages/NewRelic.Agent) AWS Lambda 추가합니다. 자세한 내용은 [설치 가이드를](/docs/apm/agents/net-agent/install-guides/install-net-agent-using-nuget/) 참조하세요. - 2. [분산 추적을](/docs/apm/distributed-tracing/getting-started/introduction-distributed-tracing) 활성화하고 환경 변수를 구성하려면 [환경 변수](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) 설명서를 참조하세요. - 3. 프로젝트를 AWS Lambda 계정에 게시합니다. - 4. 뉴렐릭 Lambda 확장 또는 `newrelic-log-ingestion` 람다를 [구성합니다](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/account-linking/) . - 5. Lambda를 한 번 이상 호출하여 오류를 확인하고 뉴렐릭 UI 에 데이터가 표시되는지 확인하세요. + 2. [환경 변수를](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) 구성합니다. + 3. AWS Management Console의 설정 탭에서 Lambda 함수에 `NR.Apm.Lambda.Mode: true` 태그를 추가하세요. + 4. 프로젝트를 AWS Lambda 계정에 게시합니다. + 5. 뉴렐릭 Lambda 확장 또는 `newrelic-log-ingestion` 람다를 [구성합니다](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/account-linking/) . + 6. Lambda를 한 번 이상 호출하여 오류를 확인하고 뉴렐릭 UI 에 데이터가 표시되는지 확인하세요. -## 무엇 향후 계획 +## 데이터 찾기 및 사용 [#find-data] + +AWS Lambda 함수를 로그아웃한 후 뉴렐릭 APM 인터페이스에서 데이터를 찾아 사용할 수 있습니다. 데이터는 여러 주요 영역으로 구성되며, 각 영역은 Lambda 함수의 성능과 상태에 대한 다양한 정보를 제공합니다. + +APM 인터페이스에서는 [분산 추적](/docs/distributed-tracing/concepts/introduction-distributed-tracing/), [서비스 맵](/docs/new-relic-solutions/new-relic-one/ui-data/service-maps/service-maps/), [트랜잭션](docs/apm/transactions/intro-transactions/transactions-new-relic-apm//), [오류 분석](docs/errors-inbox/getting-started/) 등 Lambda 함수의 다양한 측면을 살펴볼 수 있습니다. 이러한 각 영역에서는 Lambda 함수의 성능, 지연 시간 및 오류율에 대한 자세한 내용을 제공하므로 문제를 신속하게 식별하고 해결할 수 있습니다. + + + 이제 호출 환경이 APM 프로세서 트레이스와 통합되었습니다. 이를 통해 특정 `AWS RequestId` 사용하여 APM 트레이스를 드릴다운하여 특정 Lambda 실행에 대한 자세한 정보를 얻을 수 있습니다. + + +뉴렐릭 APM 인터페이스에서 Lambda 함수를 보려면: + +1. [https://one.newrelic.com](https://one.newrelic.com) > APM & Services 으)로 이동합니다. +2. 검색 기준을 `isLambdaFunction = true` 으로 설정합니다. +3. 표시된 목록에서 Lambda 함수를 선택하여 데이터를 확인하세요. + +## 관련 기사 [#related-docs] 지원되는 런타임 및 필수 구성 요소에 대해 자세히 알아보세요. - - 뉴렐릭을 사용하여 AWS Lambda 함수를 모니터링하는 방법을 알아보세요. - - - + 설치 관련 문제를 해결하는 방법을 알아보세요 \ No newline at end of file diff --git a/src/i18n/content/kr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/update-lambda-monitoring.mdx b/src/i18n/content/kr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/update-lambda-monitoring.mdx index 2b665f5d6b8..95d59b80d5e 100644 --- a/src/i18n/content/kr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/update-lambda-monitoring.mdx +++ b/src/i18n/content/kr/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/update-lambda-monitoring.mdx @@ -5,7 +5,7 @@ freshnessValidatedDate: never translationType: machine --- -[AWS Lambda에 대한 모니터링을 활성화](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/enable-new-relic-monitoring-aws-lambda) 한 후 AWS 로그 데이터를 보고하는 데 사용되는 Lambda 함수를 가끔 업데이트해야 합니다. `newrelic-log-ingestion` . +[AWS Lambda에 대한 모니터링을 활성화한](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda/#link) 후에는 AWS 로그 데이터를 보고하는 데 사용되는 Lambda 함수 `newrelic-log-ingestion` 를 가끔 업데이트해야 합니다. 두 가지 방법이 있습니다. @@ -13,7 +13,7 @@ translationType: machine * [AWS Serverless Application Repository를 통한 업데이트](#update-sar) : [수동 절차](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/enable-new-relic-monitoring-aws-lambda#manual-nr-lambda) 를 사용하여 활성화한 경우 사용합니다. - 이러한 업데이트 절차는 AWS Lambda에 [대한 서버리스 모니터링에](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/introduction-new-relic-monitoring-aws-lambda) 적용되며 [AWS Lambda 통합에 대한 인프라 모니터링에는](/docs/integrations/amazon-integrations/aws-integrations-list/aws-lambda-monitoring-integration) 적용되지 않습니다. + 이러한 업데이트 절차는 [AWS Lambda에 대한 서버리스 모니터링](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda) 에는 적용되며, [AWS Lambda 통합에 대한 인프라 모니터링](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-lambda-monitoring-integration) 에는 적용되지 않습니다. ## CLI를 통해 Lambda 통합 업데이트 [#update-cli] @@ -60,6 +60,7 @@ translationType: machine --function installed \ --nr-account-id NR_ACCOUNT_ID \ --upgrade + --apm ``` ## 수동 서버리스 애플리케이션 리포지토리 설치 업데이트 [#update-sar] diff --git a/src/i18n/content/kr/docs/serverless-function-monitoring/aws-lambda-monitoring/troubleshooting/troubleshoot-enabling-serverless-monitoring-aws-lambda.mdx b/src/i18n/content/kr/docs/serverless-function-monitoring/aws-lambda-monitoring/troubleshooting/troubleshoot-enabling-serverless-monitoring-aws-lambda.mdx index 0aa739f154b..15f282858ce 100644 --- a/src/i18n/content/kr/docs/serverless-function-monitoring/aws-lambda-monitoring/troubleshooting/troubleshoot-enabling-serverless-monitoring-aws-lambda.mdx +++ b/src/i18n/content/kr/docs/serverless-function-monitoring/aws-lambda-monitoring/troubleshooting/troubleshoot-enabling-serverless-monitoring-aws-lambda.mdx @@ -1,5 +1,5 @@ --- -title: AWS Lambda의 서버리스 모니터링 활성화 문제 해결 +title: Lambda 모니터링 문제 해결 type: troubleshooting tags: - Serverless function monitoring @@ -12,22 +12,22 @@ translationType: machine ## 문제 -[AWS Lambda에 대한 서버리스 모니터링](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/introduction-new-relic-monitoring-aws-lambda) 을 활성화하려고 하는데 문제 또는 오류가 있습니다. +[AWS Lambda에 대한 서버리스 모니터링을](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda) 활성화하려고 시도했지만 문제나 오류가 발생했습니다. ## 해결책 -[활성화 절차](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/enable-new-relic-monitoring-aws-lambda) 를 모두 완료하지 않는 것과 관련된 두 가지 일반적인 문제가 있습니다. +모든 [활성화 절차를](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda/#link) 완료하지 않으면 두 가지 일반적인 문제가 발생합니다. -* **CloudWatch metrics** UI 페이지에서 데이터가 보이지 않습니다. 이는 [AWS 통합 단계가](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/enable-new-relic-monitoring-aws-lambda#connect-aws) 완료되지 않았음을 의미합니다. -* **Troubleshooting** 카테고리 UI 페이지에서 데이터가 보이지 않습니다. **Distributed tracing**, **Errors**, **Invocations** UI 탭에 데이터가 표시되지 않는 경우 [APM 에이전트 측정 단계가](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/enable-new-relic-monitoring-aws-lambda#instrument-lambda) 완료되지 않았음을 의미합니다. +* **Lambda metrics** UI 페이지에서 데이터가 보이지 않습니다. 이는 [AWS 통합 단계가](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda/#link) 완료되지 않았음을 의미합니다. +* **Troubleshooting** 카테고리 UI 페이지에서 데이터가 보이지 않습니다. **Distributed tracing**, **Errors**, **Invocations** UI 탭에 데이터가 표시되지 않는 경우 [APM 에이전트 측정 단계가](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda/#instrument) 완료되지 않았음을 의미합니다. 이러한 기본 활성화 문제 외에도 문제를 일으킬 수 있는 몇 가지 추가 문제가 있습니다. -* CloudWatch 오류 "HTTP 오류 401: 인증되지 않았습니다." 이는 잘못된 API 키로 인해 발생합니다. [AWS 활성화 구성 단계](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/enable-new-relic-monitoring-aws-lambda#connect-aws) 의 `--nr-api-key`인수는 사용합니다. +* CloudWatch 오류 "HTTP 오류 401: 권한이 없습니다." 이는 잘못된 API 키로 인해 발생합니다. [AWS 구성 활성화 단계](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda/#link) 의 `--nr-api-key`인수는 을 사용합니다. * 맞춤 측정항목이 없습니다. Lambda 모니터링은 [사용자 지정 지표](/docs/agents/manage-apm-agents/agent-data/collect-custom-metrics) 와 호환되지 않습니다. [사용자 정의 속성](/docs/agents/manage-apm-agents/agent-data/collect-custom-attributes) 을 사용하여 메타데이터를 추가합니다. -* 호출이 누락되었습니다. 호출 분석 세부 정보를 보려면 [Lambda 계측 단계](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/enable-new-relic-monitoring-aws-lambda#instrument-lambda) 의 일부로 분산 추적을 활성화해야 합니다. 호출 세부 정보 창에 범위 세부 정보를 표시할 수 있도록 분산 추적이 필요합니다. +* 호출 탭이 없습니다. APM + Serverless Convergence를 사용하면 각 Lambda 호출은 APM 의 프로세서 트레이스에 해당합니다. 호출 분석 세부 정보를 보려면 [프로세서 트레이스를](/docs/apm/apm-ui-pages/monitoring/transactions-page-find-specific-performance-problems) 참조하세요. * 설치, 통합 및 계측 단계를 올바르게 완료했으며 함수가 CloudWatch에 로그를 전송하지만 UI에서 특정 종속성(또는 모든 추적)에 대한 추적을 볼 수 없습니다. 이는 레이어 병합 순서(Lambda 레이어를 사용하는 경우) 또는 가져오기 순서(수동으로 계측하는 경우)로 인해 발생할 수 있습니다. diff --git a/src/i18n/content/kr/docs/serverless-function-monitoring/aws-lambda-monitoring/troubleshooting/troubleshoot-no-data-appears.mdx b/src/i18n/content/kr/docs/serverless-function-monitoring/aws-lambda-monitoring/troubleshooting/troubleshoot-no-data-appears.mdx index 18ffaa8ffce..c5c85b68aa1 100644 --- a/src/i18n/content/kr/docs/serverless-function-monitoring/aws-lambda-monitoring/troubleshooting/troubleshoot-no-data-appears.mdx +++ b/src/i18n/content/kr/docs/serverless-function-monitoring/aws-lambda-monitoring/troubleshooting/troubleshoot-no-data-appears.mdx @@ -10,12 +10,22 @@ freshnessValidatedDate: never translationType: machine --- -## 문제 +## 문제 [#problem] AWS Lambda 함수에 대한 트래픽을 생성하고 5분을 기다린 후에는 뉴렐릭 UI 에 함수 데이터가 전혀 표시되지 않습니다. 로그에는 오류가 없으며 뉴렐릭 UI 에는 `NRIntegrationErrors` 또는 `NRIntegrationWarnings` 이 없습니다. -## 해결책 +## 해결책 [#solution] + +### 역대 기록 및 계정 ID 확인 [#check-license] 데이터가 표시되지 않고 오류가 발생하지 않는 가장 일반적인 이유는 [라이선스 키와 계정 ID가](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/account-linking/) 다른 계정에 속해 있기 때문입니다. 불일치가 발생하는 경우 [](https://github.com/newrelic/newrelic-lambda-extension)[클라우드 워치 로그를 처리하는](/docs/infrastructure/amazon-integrations/connect/aws-metric-stream/) 뉴렐릭 Lambda 확장 프로그램 또는 람다가 데이터를 성공적으로 보고하지만 계정 ID가 일치하지 않기 때문에 자동으로 삭제됩니다. 이로 인해 오류나 경고가 발생하지 않습니다. 이 문제를 해결하려면 라이선스 키와 계정 ID가 동일한 계정에 속해 있는지 확인하세요. 이러한 유형의 문제를 최소화하려면 [뉴렐릭 Lambda CLI를](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/account-linking/#rec) 사용하여 서버리스 모니터링을 활성화하는 것이 좋습니다. AWS Secrets Manager에서 라이선스 키를 업데이트할 수 있습니다. AWS Secrets Manager를 사용하지 않는 계정 ID 및 설정의 경우 올바른 인스턴스 키 또는 계정 ID로 [환경 변수를](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/account-linking/#env-var) 업데이트하여 문제를 해결할 수 있습니다. + +### 환경 변수 확인 [#check-env-vars] + +AWS Lambda 함수에 필요한 [환경 변수가](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) 올바르게 설정되었는지 확인하세요. 여기에는 `NEW_RELIC_APM_LAMBDA_MODE`, `NEW_RELIC_ACCOUNT_ID`, `NEW_RELIC_LICENSE_KEY` 및 기타 관련 변수가 포함됩니다. 이러한 변수가 설정되지 않았거나 올바르지 않으면 데이터가 뉴렐릭으로 전송되지 않을 수 있습니다. 자세한 내용은 [환경 변수를](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) 참조하세요. + +### AWS Management Console에서 태그 확인 [#check-tags] + +AWS Management Console에서 Lambda 함수에 `NR.Apm.Lambda.Mode: true` 태그를 추가했는지 확인하세요. 이 태그는 모델링을 활성화하고 데이터가 뉴렐릭으로 전송되는지 확인하는 데 필수적입니다. \ No newline at end of file diff --git a/src/i18n/content/pt/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx b/src/i18n/content/pt/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx index d6f4e79ca5f..60f1d8b2be7 100644 --- a/src/i18n/content/pt/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx +++ b/src/i18n/content/pt/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx @@ -36,7 +36,7 @@ Quer experimentar nosso agente .NET? [Crie uma conta New Relic](https://newrelic - The .NET agent is compatible with .NET Core version 3.1, and .NET 5.0, 6.0, 7.0, 8.0, 9.0, and 10.0. + O agente .NET é compatível com o .NET Core versão 3.1 e com o .NET 5.0, 6.0, 7.0, 8.0, 9.0 e 10.0. O agente só é totalmente suportado quando instrumentado aplicativo que tem como destino [os tempos de execução .NET atualmente suportados pela Microsoft](https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core). É provável que o agente funcione com os tempos de execução EOL listados abaixo, mas não testamos novas versões do agente com tempos de execução EOL. @@ -271,7 +271,7 @@ Quer experimentar nosso agente .NET? [Crie uma conta New Relic](https://newrelic - The .NET agent is compatible with applications targeting .NET Core 3.1, and .NET 5.0, 6.0, 7.0, 8.0, 9.0, and 10.0. You can find the target framework in your `.csproj` file. Agent compatibility varies across different versions of .NET Core. + O agente .NET é compatível com aplicativos direcionados ao .NET Core 3.1 e ao .NET 5.0, 6.0, 7.0, 8.0, 9.0 e 10.0. Você pode encontrar o framework destino no seu arquivo `.csproj`. A compatibilidade do agente varia entre as diferentes versões do .NET Core. Compatível: @@ -319,8 +319,8 @@ Quer experimentar nosso agente .NET? [Crie uma conta New Relic](https://newrelic O agente .NET utiliza automaticamente esta estrutura de aplicativos: - * ASP.NET Core MVC 2.0, 2.1, 2.2, 3.0, 3.1, 5.0, 6.0, 7.0, 8.0, 9.0, and 10.0 (includes Web API) - * ASP.NET Core Razor Pages 6.0, 7.0, 8.0, 9.0, and 10.0 (starting with .NET agent version 10.19.0) + * ASP.NET Core MVC 2.0, 2.1, 2.2, 3.0, 3.1, 5.0, 6.0, 7.0, 8.0, 9.0 e 10.0 (incluindo Web API) + * ASP.NET Core Razor Pages 6.0, 7.0, 8.0, 9.0 e 10.0 (a partir da versão 10.19.0 do agente .NET) @@ -357,7 +357,7 @@ Quer experimentar nosso agente .NET? [Crie uma conta New Relic](https://newrelic O agente .NET `v9.2.0` ou superior utiliza automaticamente a biblioteca [Microsoft.Azure.Cosmos](https://www.nuget.org/packages/Microsoft.Azure.Cosmos) . * Versão mínima suportada: 3.17.0 - * Latest verified compatible version: 3.56.0 + * Última versão compatível verificada: 3.56.0 * As versões 3.35.0 e superiores são suportadas a partir do agente .NET v10.32.0 @@ -434,7 +434,7 @@ Quer experimentar nosso agente .NET? [Crie uma conta New Relic](https://newrelic Usar [Npgsql](https://www.nuget.org/packages/Npgsql/) * Versão mínima suportada: 4.0.0 - * Latest verified compatible version: 7.0.7 + * Última versão compatível verificada: 7.0.7 Versões anteriores do Npgsql também podem ser instrumentadas, mas métricas duplicadas e/ou ausentes são possíveis. @@ -452,7 +452,7 @@ Quer experimentar nosso agente .NET? [Crie uma conta New Relic](https://newrelic Versão mínima suportada: 2.3.0 - Latest verified compatible version: 3.5.2 + Última versão compatível verificada: 3.5.2 Versões 3.0.0 e versões superiores são suportadas a partir do agente .NET v10.40.0. @@ -570,7 +570,7 @@ Quer experimentar nosso agente .NET? [Crie uma conta New Relic](https://newrelic * Versão mínima suportada: 3.5.0 - * Latest verified compatible version: 4.0.10.1 + * Última versão compatível verificada: 4.0.10.1 * Versão mínima do agente necessária: 10.33.0 @@ -907,7 +907,7 @@ Quer experimentar nosso agente .NET? [Crie uma conta New Relic](https://newrelic * Versão mínima suportada: 3.5.2 - * Latest verified compatible version: 7.1.2 + * Última versão compatível verificada: 7.1.2 @@ -921,7 +921,7 @@ Quer experimentar nosso agente .NET? [Crie uma conta New Relic](https://newrelic * Versão mínima suportada: 7.1.0 - * Latest verified compatible version: 8.5.7 + * Última versão compatível verificada: 8.5.7 @@ -949,7 +949,7 @@ Quer experimentar nosso agente .NET? [Crie uma conta New Relic](https://newrelic * Versão mínima suportada: 3.7.0 - * Latest verified compatible version: 4.0.7.6 + * Última versão compatível verificada: 4.0.7.6 @@ -963,7 +963,7 @@ Quer experimentar nosso agente .NET? [Crie uma conta New Relic](https://newrelic * Versão mínima suportada: 3.7.0 - * Latest verified compatible version: 4.0.3.5 + * Última versão compatível verificada: 4.0.3.5 @@ -1343,7 +1343,7 @@ Quer experimentar nosso agente .NET? [Crie uma conta New Relic](https://newrelic O agente .NET `v9.2.0` ou superior utiliza automaticamente a biblioteca [Microsoft.Azure.Cosmos](https://www.nuget.org/packages/Microsoft.Azure.Cosmos) . * Versão mínima suportada: 3.17.0 - * Latest verified compatible version: 3.56.0 + * Última versão compatível verificada: 3.56.0 * As versões 3.35.0 e superiores são suportadas a partir do agente .NET v10.32.0 @@ -1461,7 +1461,7 @@ Quer experimentar nosso agente .NET? [Crie uma conta New Relic](https://newrelic Versão mínima suportada: 2.3.0 - Latest verified compatible version: 3.5.2 + Última versão compatível verificada: 3.5.2 Versões 3.0.0 e versões superiores são suportadas a partir do agente .NET v10.40.0. @@ -1531,7 +1531,7 @@ Quer experimentar nosso agente .NET? [Crie uma conta New Relic](https://newrelic Usar [Npgsql](https://www.nuget.org/packages/Npgsql/) * Versão mínima suportada: 4.0.0 - * Latest verified compatible version: 7.0.7 + * Última versão compatível verificada: 7.0.7 Versões anteriores do Npgsql também podem ser instrumentadas, mas métricas duplicadas e/ou ausentes são possíveis. @@ -1629,7 +1629,7 @@ Quer experimentar nosso agente .NET? [Crie uma conta New Relic](https://newrelic * Versão mínima suportada: 3.5.0 - * Latest verified compatible version: 4.0.10.1 + * Última versão compatível verificada: 4.0.10.1 * Versão mínima do agente necessária: 10.33.0 @@ -1710,7 +1710,7 @@ Quer experimentar nosso agente .NET? [Crie uma conta New Relic](https://newrelic Versão mínima suportada: 105.2.3 - Latest verified compatible version: 113.0.0 + Última versão compatível verificada: 113.0.0 Versões incompatíveis conhecidas: 106.8.0, 106.9.0, 106.10.0, 106.10.1 @@ -2012,7 +2012,7 @@ Quer experimentar nosso agente .NET? [Crie uma conta New Relic](https://newrelic * Versão mínima suportada: 3.5.2 - * Latest verified compatible version: 6.8.1 + * Última versão compatível verificada: 6.8.1 @@ -2026,7 +2026,7 @@ Quer experimentar nosso agente .NET? [Crie uma conta New Relic](https://newrelic * Versão mínima suportada: 7.1.0 - * Latest verified compatible version: 8.5.7 + * Última versão compatível verificada: 8.5.7 @@ -2054,7 +2054,7 @@ Quer experimentar nosso agente .NET? [Crie uma conta New Relic](https://newrelic * Versão mínima suportada: 3.7.0 - * Latest verified compatible version: 4.0.7.6 + * Última versão compatível verificada: 4.0.7.6 @@ -2068,7 +2068,7 @@ Quer experimentar nosso agente .NET? [Crie uma conta New Relic](https://newrelic * Versão mínima suportada: 3.7.0 - * Latest verified compatible version: 4.0.3.5 + * Última versão compatível verificada: 4.0.3.5 diff --git a/src/i18n/content/pt/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx b/src/i18n/content/pt/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx index f0f14c1ca0a..3923951a1d9 100644 --- a/src/i18n/content/pt/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx +++ b/src/i18n/content/pt/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx @@ -268,32 +268,32 @@ Após a instalação, o agente automaticamente instrumento com nosso catálogo d | Nome do pacote | Versão mínima suportada | Última versão publicada | Introduzido em\* | | --------------------------------- | ----------------------- | ----------------------- | -------------------------------------- | | `@apollo/gateway` | 2.3.0 | 2.12.1 | `@newrelic/apollo-server-plugin@1.0.0` | -| `@apollo/server` | 4.0.0 | 5.1.0 | `@newrelic/apollo-server-plugin@2.1.0` | -| `@aws-sdk/client-bedrock-runtime` | 3.474.0 | 3.934.0 | 11.13.0 | -| `@aws-sdk/client-dynamodb` | 3.0.0 | 3.934.0 | 8.7.1 | -| `@aws-sdk/client-sns` | 3.0.0 | 3.934.0 | 8.7.1 | -| `@aws-sdk/client-sqs` | 3.0.0 | 3.934.0 | 8.7.1 | -| `@aws-sdk/lib-dynamodb` | 3.377.0 | 3.934.0 | 8.7.1 | +| `@apollo/server` | 4.0.0 | 5.2.0 | `@newrelic/apollo-server-plugin@2.1.0` | +| `@aws-sdk/client-bedrock-runtime` | 3.474.0 | 3.943.0 | 11.13.0 | +| `@aws-sdk/client-dynamodb` | 3.0.0 | 3.943.0 | 8.7.1 | +| `@aws-sdk/client-sns` | 3.0.0 | 3.943.0 | 8.7.1 | +| `@aws-sdk/client-sqs` | 3.0.0 | 3.943.0 | 8.7.1 | +| `@aws-sdk/lib-dynamodb` | 3.377.0 | 3.943.0 | 8.7.1 | | `@aws-sdk/smithy-client` | 3.47.0 | 3.374.0 | 8.7.1 | -| `@azure/functions` | 4.7.0 | 4.9.0 | 12.18.0 | +| `@azure/functions` | 4.7.0 | 4.10.0 | 12.18.0 | | `@elastic/elasticsearch` | 7.16.0 | 9.2.0 | 11.9.0 | | `@google/genai` | 1.1.0 | 1.30.0 | 12.21.0 | -| `@grpc/grpc-js` | 1.4.0 | 1.14.1 | 8.17.0 | +| `@grpc/grpc-js` | 1.4.0 | 1.14.2 | 8.17.0 | | `@hapi/hapi` | 20.1.2 | 21.4.4 | 9.0.0 | -| `@koa/router` | 12.0.1 | 14.0.0 | 3.2.0 | -| `@langchain/core` | 0.1.17 | 1.0.6 | 11.13.0 | -| `@modelcontextprotocol/sdk` | 1.13.0 | 1.22.0 | 13.2.0 | -| `@nestjs/cli` | 9.0.0 | 11.0.12 | 10.1.0 | +| `@koa/router` | 12.0.1 | 15.0.0 | 3.2.0 | +| `@langchain/core` | 0.1.17 | 1.1.1 | 11.13.0 | +| `@modelcontextprotocol/sdk` | 1.13.0 | 1.24.1 | 13.2.0 | +| `@nestjs/cli` | 9.0.0 | 11.0.14 | 10.1.0 | | `@opensearch-project/opensearch` | 2.1.0 | 3.5.1 | 12.10.0 | -| `@prisma/client` | 5.0.0 | 7.0.0 | 11.0.0 | -| `@smithy/smithy-client` | 2.0.0 | 4.9.7 | 11.0.0 | +| `@prisma/client` | 5.0.0 | 7.0.1 | 11.0.0 | +| `@smithy/smithy-client` | 2.0.0 | 4.9.9 | 11.0.0 | | `amqplib` | 0.5.0 | 0,10,9 | 2.0.0 | | `aws-sdk` | 2.2.48 | 2.1692.0 | 6.2.0 | | `bluebird` | 2.0.0 | 3.7.2 | 1.27.0 | | `bunyan` | 1.8.12 | 1.8.15 | 9.3.0 | | `cassandra-driver` | 3.4.0 | 4.8.0 | 1.7.1 | | `connect` | 3.0.0 | 3.7.0 | 2.6.0 | -| `express` | 4.15.0 | 5.1.0 | 2.6.0 | +| `express` | 4.15.0 | 5.2.1 | 2.6.0 | | `fastify` | 3.0.0 | 5.6.2 | 8.5.0 | | `generic-pool` | 3.0.0 | 3.9.0 | 0.9.0 | | `ioredis` | 4.0.0 | 5.8.2 | 1.26.2 | @@ -305,13 +305,13 @@ Após a instalação, o agente automaticamente instrumento com nosso catálogo d | `mongodb` | 4.1.4 | 7.0.0 | 1.32.0 | | `mysql` | 2.16.0 | 2.18.1 | 1.32.0 | | `mysql2` | 2.0.0 | 3.15.3 | 1.32.0 | -| `next` | 13.4.19 | 16.0.3 | 12.0.0 | +| `next` | 13.4.19 | 16.0.6 | 12.0.0 | | `openai` | 4.0.0 | 6.9.1 | 11.13.0 | | `pg` | 8.2.0 | 8.16.3 | 9.0.0 | | `pg-native` | 3.0.0 | 3.5.2 | 9.0.0 | | `pino` | 8.0.0 | 10.1.0 | 8.11.0 | | `q` | 1.3.0 | 1.5.1 | 1.26.2 | -| `redis` | 3.1.0 | 5.9.0 | 1.31.0 | +| `redis` | 3.1.0 | 5.10.0 | 1.31.0 | | `restify` | 11.0.0 | 11.1.0 | 2.6.0 | | `superagent` | 3.0.0 | 10.2.3 | 4.9.0 | | `undici` | 5.0.0 | 7.16.0 | 11.1.0 | diff --git a/src/i18n/content/pt/docs/query-your-data/explore-query-data/dashboards/share-charts-dashboards-externally.mdx b/src/i18n/content/pt/docs/query-your-data/explore-query-data/dashboards/share-charts-dashboards-externally.mdx index 75b328be9ca..02892183062 100644 --- a/src/i18n/content/pt/docs/query-your-data/explore-query-data/dashboards/share-charts-dashboards-externally.mdx +++ b/src/i18n/content/pt/docs/query-your-data/explore-query-data/dashboards/share-charts-dashboards-externally.mdx @@ -135,16 +135,6 @@ Este recurso inclui múltiplas camadas e condições de segurança para garantir * **Acesso baseado em sessão**: Após acessar o dashboard, a sessão permanece ativa por 120 horas. Se tentarem acessar o dashboard após esse período, ou se a sessão do navegador expirar, será solicitada a senha. Caso haja uma redefinição de senha, a sessão expira assim que o widget for atualizado. O usuário externo precisa inserir a nova senha. * **Verificação reCAPTCHA**: Se o usuário tiver várias tentativas falhas de acesso ao dashboard, precisará concluir uma verificação reCAPTCHA antes de inserir a senha novamente. - - ### Preços [#public-dashboard-pricing] - - Ao compartilhar URLs dashboard em tempo real, é importante entender os custos associados e como gerenciá-los de forma eficaz. **Public Dashboards** é um recurso de produto de informática avançado oferecido como um [complemento](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/add-on-billing) ou como parte do modelo de preços do computador. [Os CCUs](/docs/licenses/license-information/product-definitions/new-relic-one-pricing-definitions/#compute-capacity-unit) avançados são consumidos quando as consultas são executadas a partir das visualizações dashboard, o que ocorre nos seguintes casos: - - * No carregamento da página - * No seletor de hora muda - * Sobre gatilhos de taxa de atualização - - Você pode monitorar seus custos de uso em **[New Relic Administration](https://one.newrelic.com/admin-portal) > Consumption Management > Advanced capabilities**. Para otimizar seus custos, consulte a seção [práticas recomendadas de gestão de preços](#pricing-management) . @@ -256,6 +246,16 @@ Este recurso inclui múltiplas camadas e condições de segurança para garantir + ### Preços [#public-dashboard-pricing] + + Ao compartilhar URLs dashboard em tempo real, é importante entender os custos associados e como gerenciá-los de forma eficaz. **Public Dashboards** é um recurso de produto de informática avançado oferecido como um [complemento](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/add-on-billing) ou como parte do modelo de preços do computador. [Os CCUs](/docs/licenses/license-information/product-definitions/new-relic-one-pricing-definitions/#compute-capacity-unit) avançados são consumidos quando as consultas são executadas a partir das visualizações dashboard, o que ocorre nos seguintes casos: + + * No carregamento da página + * No seletor de hora muda + * Sobre gatilhos de taxa de atualização + + Você pode monitorar seus custos de uso em **[New Relic Administration](https://one.newrelic.com/admin-portal) > Consumption Management > Advanced capabilities**. Para otimizar seus custos, consulte a seção [práticas recomendadas de gestão de preços](#pricing-management) . + ### Práticas medidas [#best-practices] Para gerenciar com eficiência os preços e a segurança de senhas relacionados dashboard público, siga estas práticas recomendadas: diff --git a/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-11-28-2025.mdx b/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-11-28-2025.mdx new file mode 100644 index 00000000000..ca596d8aefb --- /dev/null +++ b/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-11-28-2025.mdx @@ -0,0 +1,72 @@ +--- +subject: Docs +releaseDate: '2025-11-28' +version: 'November 24 - November 28, 2025' +translationType: machine +--- + +### Novos documentos + +* Adicionado [suporte ao agente PHP para Laravel](/docs/apm/agents/php-agent/frameworks-libraries/laravel), a fim de fornecer orientações abrangentes para transações web Laravel, Laravel Queue Workers e Laravel Horizon Workers. +* Adicionado guia [PHPUnit fica sem memória](/docs/apm/agents/php-agent/troubleshooting/phpunit-incompatibility) resolução de problemas para problemas de compatibilidade PHPUnit 11+ com o agente PHP New Relic. + +### Grandes mudanças + +* [Conceitos de gerenciamento de usuários](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts) atualizados e documentação RBAC relacionada com nova experiência de criação de concessão e função, introduzindo três tipos de função (funções baseadas na organização, funções baseadas na conta e funções baseadas na entidade) consolidados na aba **Roles**. +* [Canais de alerta](/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-channels) atualizados com métodos e exemplos da API de integração do Microsoft Teams. +* [Destinos de alerta](/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-destinations) atualizados com suporte para integração com o Microsoft Teams. + +### Pequenas mudanças + +* Atualizamos [os preços e a cobrança do New Relic](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing) para trazer mais clareza aos modelos de preços e aos recursos oferecidos. +* [Configuração de agente .NET](/docs/apm/agents/net-agent/configuration/net-agent-configuration) atualizada com opções de configuração de instrumentação do navegador. +* Atualizado [monitoramento de Browser com agente .NET](/docs/apm/agents/net-agent/other-features/browser-monitoring-net-agent) com orientação de configuração simplificada. +* Atualização [dos requisitos de compatibilidade do agente PHP](/docs/apm/agents/php-agent/getting-started/php-agent-compatibility-requirements) com o Laravel Horizon e remoção do suporte ao Windows de 32 bits. +* [Processamento atualizado do coletor OpenTelemetry](/docs/opentelemetry/get-started/collector-processing/opentelemetry-collector-processing-intro) com orientações de configuração atualizadas. +* [Configuração de rede](/docs/new-relic-solutions/get-started/networks) atualizada com link permanente fixo endpoint pilha dupla. +* Atualização [da conformidade com o TISAX](/docs/security/security-privacy/compliance/certificates-standards-regulations/tisax), incluindo informações atualizadas sobre a conformidade. + +### Notas de versão + +* Anunciado o dia 30 de junho de 2026 como a data de fim de vida útil dos [gráficos incorporados legados APM anteriores insights.](/eol/2025/11/pre-insights/) + +* Fique por dentro dos nossos últimos lançamentos: + + * [Integração Kubernetes v3.50.2](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-50-2): + + * Integração atualizada incluída em newrelic-infrastructure-3.55.2 e nri-bundle-6.0.26. + + * [Logs 251120](/docs/release-notes/logs-release-notes/logs-25-11-20): + + * Corrigida a vulnerabilidade CVE-2025-53643 na função Lambda de aws-log-ingestion. + * Biblioteca aiohttp atualizada para a versão 3.13.2. e versão de poesia para 1.8.3. + + * [Agente React Native v1.5.12](/docs/release-notes/mobile-release-notes/react-native-release-notes/react-native-agent-1512): + + * Agente nativo Android atualizado para a versão 7.6.13. + * Agente nativo do iOS atualizado para a versão 7.6.0. + + * [Agente Capacitor v1.5.12](/docs/release-notes/mobile-release-notes/capacitor-release-notes/capacitor-agent-1512): + + * Agente nativo Android atualizado para a versão 7.6.13. + * Agente nativo do iOS atualizado para a versão 7.6.0. + + * [Agente Flutter v1.1.19](/docs/release-notes/mobile-release-notes/flutter-release-notes/flutter-agent-1119): + + * Agente nativo Android atualizado para a versão 7.6.13. + * Agente nativo do iOS atualizado para a versão 7.6.0. + + * [Agente Unity v1.4.11](/docs/release-notes/mobile-release-notes/unity-release-notes/unity-agent-1411): + + * Agente nativo Android atualizado para a versão 7.6.13. + * Agente nativo do iOS atualizado para a versão 7.6.0. + + * [Agente Cordova v7.0.11](/docs/release-notes/mobile-release-notes/cordova-release-notes/cordova-agent-711): + + * Agente nativo Android atualizado para a versão 7.6.13. + * Agente nativo do iOS atualizado para a versão 7.6.0. + + * [Agente .NET MAUI v1.1.14](/docs/release-notes/mobile-release-notes/net-maui-release-notes/net-maui-agent-1114): + + * Agente nativo Android atualizado para a versão 7.6.13. + * Agente nativo do iOS atualizado para a versão 7.6.0. \ No newline at end of file diff --git a/src/i18n/content/pt/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/compatibility-requirement-lambda-monitoring.mdx b/src/i18n/content/pt/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/compatibility-requirement-lambda-monitoring.mdx index 89e9b99731f..46de9b15448 100644 --- a/src/i18n/content/pt/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/compatibility-requirement-lambda-monitoring.mdx +++ b/src/i18n/content/pt/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/compatibility-requirement-lambda-monitoring.mdx @@ -11,13 +11,17 @@ Antes de [instalar o monitoramento Lambda](/docs/serverless-function-monitoring/ Antes de habilitar o monitoramento Serverless usando nossa camada Lambda, você precisará de: -1. Uma conta New Relic com [função de](/docs/accounts/original-accounts-billing/original-users-roles/users-roles-original-user-model/#roles) administrador ou com a [função complementar](/docs/accounts/original-accounts-billing/original-users-roles/users-roles-original-user-model#add-on) **de gerente de** infraestrutura . +* Uma conta New Relic com uma função de [administrador](/docs/accounts/accounts-billing/new-relic-one-user-management/introduction-managing-users) ou com a função de **Infrastructure manager** [adjunto](/docs/accounts/original-accounts-billing/original-users-roles/users-roles-original-user-model#add-on). -2. Um . +* Um . -3. Uma conta AWS com permissões para criar recursos IAM, segredos gerenciados e Lambdas. Você também precisa de permissões para criar pilha do CloudFormation e buckets S3. +* Uma conta AWS com permissões para criar recursos IAM, segredos gerenciados e Lambdas. Você também precisa de permissões para criar pilha do CloudFormation e buckets S3. -## Tempos de execução suportados + + New Relic recomenda integrar sua conta AWS com a New Relic usando a [integraçãoAWS ](/docs/infrastructure/amazon-integrations/get-started/introduction-aws-integrations/)para descobrir e monitorar automaticamente sua função do Lambda. Isso permite que você aproveite todo o poder do New Relic APM para sua função serverless. + + +## Tempos de execução suportados [#supported-runtimes] Com base no tipo de instrumentação, os seguintes tempos de execução são suportados. @@ -58,8 +62,18 @@ Com base no tipo de instrumentação, os seguintes tempos de execução são sup * Java: A instrumentação em camadas e o SDK do New Relic Java são compatíveis com `com.amazonaws:aws-lambda-java-events` versões `3.0.0` até a mais recente. -## Qual é o próximo +## Artigos relacionados [#related-docs] - Comece com instrumentação e configuração para sua função do Lambda. Aprenda como usar o New Relic para monitorar sua função AWS do Lambda. + + instrumento sua função do Lambda com a abordagem em camadas do New Relic. + + + + instrumento sua função do Lambda usando SDK. + + + + instrumento sua função do Lambda com a abordagem conteinerizada da New Relic. + \ No newline at end of file diff --git a/src/i18n/content/pt/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/containerized-images.mdx b/src/i18n/content/pt/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/containerized-images.mdx index a209ab0d1d4..88e159c3e70 100644 --- a/src/i18n/content/pt/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/containerized-images.mdx +++ b/src/i18n/content/pt/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/containerized-images.mdx @@ -202,10 +202,34 @@ Aqui está um guia para adicionar nossa camada pré-construída ao seu código. * [Instrumentação em camadas](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/instrument-your-own/#console) * [Instrumentação baseada em SDK](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/enable-serverless-monitoring-aws-lambda-layerless) + + + ### Encontre e use dados [#find-data] + + Após instrumentar sua função AWS do Lambda, você poderá encontrar e usar os dados na interface do New Relic APM. Os dados estão organizados em diversas áreas principais, cada uma fornecendo diferentes insights sobre o desempenho e a saúde da sua função Lambda. + + Na interface APM, você pode explorar vários aspectos da sua função Lambda, incluindo [distributed tracing](https://docs.newrelic.com/docs/distributed-tracing/concepts/introduction-distributed-tracing/), [mapas de serviço](https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/ui-data/service-maps/service-maps/), [transações](https://docs.newrelic.com/docs/apm/transactions/intro-transactions/transactions-new-relic-apm//), [análise de erros](https://docs.newrelic.com/docs/errors-inbox/getting-started/) e muito mais. Cada uma dessas áreas fornece insights detalhadas sobre o desempenho, a latência e a taxa de erros da sua função Lambda, permitindo que você identifique e resolva problemas rapidamente. + + + A experiência de invocação agora está integrada ao rastreamento de transações do APM. Isso permite que você use um `AWS RequestId` específico para detalhar um trace APM de transação para obter informações detalhadas sobre aquela execução Lambda específica. + + + Para visualizar sua função Lambda na interface do New Relic APM : + + 1. Vá para [https://one.newrelic.com](https://one.newrelic.com) > APM & Services. + 2. Defina os critérios de pesquisa como `isLambdaFunction = true`. + 3. Na lista exibida, selecione sua função Lambda para visualizar os dados. + -## Qual é o próximo +## Artigos relacionados [#related-docs] - Saiba mais sobre os tempos de execução suportados e pré-requisitos Aprenda a usar o New Relic para monitorar sua função do Lambda na AWS Aprenda a solucionar problemas relacionados à instalação + + Saiba mais sobre os tempos de execução e pré-requisitos suportados + + + + Aprenda a solucionar problemas relacionados à instalação + \ No newline at end of file diff --git a/src/i18n/content/pt/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda.mdx b/src/i18n/content/pt/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda.mdx index 5c8a106e139..d1e3eea393c 100644 --- a/src/i18n/content/pt/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda.mdx +++ b/src/i18n/content/pt/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda.mdx @@ -46,7 +46,7 @@ Independentemente do seu tempo de execução, você deve definir as seguintes va - Especifica o wrapper do manipulador usado para encontrar o manipulador real da sua função + Especifica o wrapper do manipulador usado para encontrar o manipulador real da sua função. No caso de ambientes de execução Go, essa variável não é obrigatória. @@ -60,6 +60,20 @@ Independentemente do seu tempo de execução, você deve definir as seguintes va + + + `NEW_RELIC_APM_LAMBDA_MODE` + + + + Defina como + + `true` + + para ativar o monitoramento APM para sua função do Lambda + + + `NEW_RELIC_TRUSTED_ACCOUNT_KEY` @@ -1082,6 +1096,22 @@ Com base no seu tempo de execução, você pode definir as seguintes variáveis , `DEBUG` + + , + + `TRACE` + + , + + `ERROR` + + , + + `WARN` + + , + + `ALL` @@ -1195,7 +1225,9 @@ Com base no seu tempo de execução, você pode definir as seguintes variáveis - Ignore as verificações fornecendo-as como valores separados por vírgula dentro de uma string. Use valores de string + **OBSOLETO. Ignore** + + as verificações fornecendo-as como valores separados por vírgula dentro de uma string. Use os valores de string `handler` @@ -1227,7 +1259,17 @@ Com base no seu tempo de execução, você pode definir as seguintes variáveis - Especifique o nome da chave secreta do AWS Secrets Manager que contém sua chave de licença. Observação: isso só será usado se NEW_RELIC_LICENSE_KEY não estiver definido. + Especifique o **nome** ou o **ARN** do segredo do AWS Secrets Manager que contém sua chave de licença do New Relic. + +
+ +
+ + **Notas:** + + * Isso só é usado se `` `NEW_RELIC_LICENSE_KEY` `` não estiver definido. + * O segredo deve estar na mesma região AWS que sua função Lambda. + * A função de execução do Lambda precisa da permissão `` `secretsmanager:GetSecretValue` `` para este segredo. @@ -1241,7 +1283,31 @@ Com base no seu tempo de execução, você pode definir as seguintes variáveis - Especifique o nome do parâmetro SSM no parâmetro Store do AWS Systems Manager que contém sua chave de licença. Nota: Isto só é usado se NEW_RIC_LICENSE_KEY não estiver definido + Especifique o **nome** ou **ARN** do parâmetro do AWS Systems Manager Parameter Store que contém sua chave de licença New Relic. + +
+ +
+ + **Notas:** + + * Isso só é usado se `` `NEW_RELIC_LICENSE_KEY` `` não estiver definido. + * O parâmetro SSM deve estar na mesma região AWS que sua função do Lambda. + * A função de execução da sua função do Lambda precisa da permissão `` `ssm:GetParameter` `` para este parâmetro. + + + + + + `NEW_RELIC_CLOUD_AWS_ACCOUNT_ID` + + + + + + + + Para ajudar New Relic a mapear e exibir corretamente os relacionamentos entre as entidades monitoradas, forneça o ID da conta AWS onde seus recursos monitorados, como banco de dados e função Lambda, estão localizados. diff --git a/src/i18n/content/pt/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own.mdx b/src/i18n/content/pt/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own.mdx index 06e4cf02fcf..4217eb6f9d8 100644 --- a/src/i18n/content/pt/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own.mdx +++ b/src/i18n/content/pt/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own.mdx @@ -5,14 +5,13 @@ freshnessValidatedDate: never translationType: machine --- -Depois de vincular com sucesso suas contas do New Relic e AWS você pode instrumentar sua função do Lambda adicionando a camada do New Relic Lambda . Isso integra o agente New Relic, permitindo o monitoramento automático sempre que suas funções forem invocadas. +Você pode instrumentar sua função Lambda adicionando a camada Lambda New Relic. Isso integra o agente New Relic, permitindo o monitoramento automático sempre que suas funções forem invocadas. a diagram depicting non-containerized lambda function instrumentation -## Antes de você começar [#begin] - -* [Vincule suas contas New Relic e AWS](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda#link) -* [Revise nossos diferentes métodos de instrumentação](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda#method) + + New Relic recomenda integrar sua conta AWS com a New Relic usando a [integraçãoAWS ](/docs/infrastructure/amazon-integrations/get-started/introduction-aws-integrations/)para descobrir e monitorar automaticamente sua função do Lambda. Isso permite que você aproveite todo o poder do New Relic APM para sua função serverless. + ## Métodos de instrumentação [#instrumentation] @@ -36,7 +35,7 @@ Dependendo de suas necessidades, você pode optar por ignorar a extensão e ver Para instalar ou atualizar a camada de instrumentação New Relic, execute este comando: ```shell - newrelic-lambda layers install --nr-account-id YOUR_NR_ACCOUNT_ID --function my-function --upgrade + newrelic-lambda layers install --nr-account-id YOUR_NR_ACCOUNT_ID --function my-function --upgrade --apm ``` Este comando encontra automaticamente a camada disponível mais recente para a região e o tempo de execução do seu Lambda. @@ -51,112 +50,154 @@ Dependendo de suas necessidades, você pode optar por ignorar a extensão e ver CloudFormation é um serviço da AWS que simplifica o provisionamento e gerenciamento de recursos AWS . Ao definir o estado desejado dos recursos em modelos YAML ou JSON, o CloudFormation lida automaticamente com a chamada de API subjacente para criar, atualizar ou excluir recursos conforme necessário. Esta abordagem declarativa automatiza o gerenciamento da infraestrutura, garantindo consistência e reprodutibilidade. - Aqui está um exemplo de um modelo simples do CloudFormation para uma função do Lambda do Node.js: - - ```yaml - AWSTemplateFormatVersion: '2010-09-09' - Transform: AWS::Serverless-2016-10-31 - Description: And example of a simple instrumented Node.js Lambda - - Resources: - NewRelicExample: - Type: AWS::Serverless::Function - Properties: - # In this example, we're using the SAM CLI to package and deploy our lambda. SAM will transform this value during the publish step. - CodeUri: newrelic-example-node/ - # The handler for your function needs to be the one provided by the instrumentation layer, below. - Handler: newrelic-lambda-wrapper.handler - Runtime: nodejs12.x - Environment: - Variables: - # For the instrumentation handler to invoke your real handler, we need this value - NEW_RELIC_LAMBDA_HANDLER: YOUR_PATH_TO_INITIAL_LAMBDA_HANDLER - # Distributed tracing needs your account ID, and your trusted account ID - NEW_RELIC_ACCOUNT_ID: YOUR_ACCOUNT_ID_HERE - # If your New Relic account has a parent account, this value should be that account ID. Otherwise, just - # your account id. - NEW_RELIC_TRUSTED_ACCOUNT_KEY: YOUR_PARENT_ACCOUNT_ID_HERE - Layers: - # This layer includes the New Relic Lambda extension, a sidecar process that sends telemetry, - # as well as the New Relic agent for Node.js, and a handler wrapper that makes integration easy. - - !Sub arn:${AWS::Partition}:lambda:${AWS::Region}:451483290750:layer:NewRelicNodeJS12X:34 - Policies: - # This policy allows the lambda to know the value of the New Relic license key. We need this so - # that we can send telemetry back to New Relic - - AWSSecretsManagerGetSecretValuePolicy: - SecretArn: !ImportValue NewRelicLicenseKeySecret-NewRelic-LicenseKeySecretARN - ``` - - Normalmente, você terá um arquivo chamado `template.yaml` que descreve sua função e seus recursos. + Para monitorar sua função Lambda com New Relic: + + 1. Instale a [camada Lambda do New Relic](https://layers.newrelic-external.com/). Aqui está um exemplo de um modelo simples do CloudFormation para uma função do Lambda do Node.js : + + ```yaml + AWSTemplateFormatVersion: '2010-09-09' + Transform: AWS::Serverless-2016-10-31 + Description: And example of a simple instrumented Node.js Lambda + + Resources: + NewRelicExample: + Type: AWS::Serverless::Function + Properties: + # In this example, we're using the SAM CLI to package and deploy our lambda. SAM will transform this value during the publish step. + CodeUri: newrelic-example-node/ + # The handler for your function needs to be the one provided by the instrumentation layer, below. + Handler: newrelic-lambda-wrapper.handler + Runtime: nodejs22.x + Environment: + Variables: + # For the instrumentation handler to invoke your real handler, we need this value + NEW_RELIC_LAMBDA_HANDLER: YOUR_PATH_TO_INITIAL_LAMBDA_HANDLER + # Distributed tracing needs your account ID, and your trusted account ID + NEW_RELIC_ACCOUNT_ID: YOUR_ACCOUNT_ID_HERE + # If your New Relic account has a parent account, this value should be that account ID. Otherwise, just + # your account id. + NEW_RELIC_TRUSTED_ACCOUNT_KEY: YOUR_PARENT_ACCOUNT_ID_HERE + NEW_RELIC_APM_LAMBDA_MODE: 'true' + Tags: + # This tag is to enable APM mode. + NR.Apm.Lambda.Mode: true + Layers: + # This layer includes the New Relic Lambda extension, a sidecar process that sends telemetry, + # as well as the New Relic agent for Node.js, and a handler wrapper that makes integration easy. + - !Sub arn:${AWS::Partition}:lambda:${AWS::Region}:451483290750:layer:NewRelicNodeJS16X:103 + Policies: + # This policy allows the lambda to know the value of the New Relic license key. We need this so + # that we can send telemetry back to New Relic + - AWSSecretsManagerGetSecretValuePolicy: + SecretArn: !ImportValue NewRelicLicenseKeySecret-NewRelic-LicenseKeySecretARN + ``` + + Normalmente, você terá um arquivo chamado `template.yaml` que descreve sua função e seus recursos. + + 2. Configure as [variáveis de ambiente](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) necessárias. + + 3. implante sua função do Lambda com a configuração atualizada. framework sem servidor é uma ferramenta popular de desenvolvimento e implantação de aplicativos sem servidor. Ele foi escrito para AWS em Node.js e atua principalmente como uma abstração de alto nível sobre modelos CloudFormation. Funciona bem para funções Node, Python, Ruby, Java e .NET. - A New Relic oferece um [plug-in framework Serverless](https://github.com/newrelic/serverless-newrelic-lambda-layers) para simplificar a instrumentação de seu aplicativo framework Serverless. + New Relic oferece um [plug-in para frameworkServerless ](https://github.com/newrelic/serverless-newrelic-lambda-layers)que simplifica a instrumentação da sua aplicação Serverless. + + **Pré-requisitos:** + + * Um aplicativo já existente que utiliza o framework Serverless. + * [ID da conta New Relic](/docs/accounts/accounts-billing/account-structure/account-id) + * [Chave pessoal de APINew Relic](/docs/apis/intro-apis/new-relic-api-keys) + + **Para instalar e configurar seu aplicativo Serverless Framework com New Relic:** - Para instalar o plug-in, execute este comando: + 1. Se você usar `npm`, execute o seguinte comando: ```bash - npm install --save-dev serverless-newrelic-lambda-layers + npm install --save-dev serverless-newrelic-lambda-layers ``` - Ou, alternativamente, você pode executar este comando: + OU, se você usar `yarn`, execute o seguinte comando: ```bash - yarn add --dev serverless-newrelic-lambda-layers + yarn add --dev serverless-newrelic-lambda-layers ``` - Em seguida, encontre seu [ID de conta New Relic](/docs/accounts/install-new-relic/account-setup/account-id), sua [chave de API pessoal New Relic](/docs/apis/get-started/intro-apis/types-new-relic-api-keys#personal-api-key) + 2. Abra o seu arquivo `serverless.yaml` e adicione a seguinte configuração: - Agora adicione o seguinte ao seu arquivo `serverless.yaml` : + 1. Adicione `serverless-newrelic-lambda-layers` à sua lista `plugins`. - ```yaml - plugins: - - serverless-newrelic-lambda-layers - custom: - newRelic: - accountId: your-new-relic-account-id-here - apiKey: your-new-relic-personal-api-key-here - linkedAccount: your-new-relic-integration-account-name-here - ``` + 2. Adicione a seguinte configuração do New Relic na seção personalizada: + + ```yaml + plugins: + - serverless-newrelic-lambda-layers + custom: + newRelic: + accountId: your-new-relic-account-id-here + apiKey: your-new-relic-personal-api-key-here + linkedAccount: your-new-relic-integration-account-name-here + apm: true + ``` + + 3. Adicione a seguinte tag `NR.Apm.Lambda.Mode: true` na seção do provedor: + + ```yaml + provider: + tags: + NR.Apm.Lambda.Mode: true + ``` + + 3. Configure as [variáveis de ambiente](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) necessárias. + + 4. implante sua função do Lambda com a configuração atualizada. O Nuvem da AWS Development Kit (AWS CDK) é um framework para definir recursos de nuvem em código e provisioná-los por meio do AWS CloudFormation. - Abaixo está um exemplo de um aplicativo CDK básico que implanta uma função New Relic instrumentada Node.js do Lambda: - - ```ts - import * as cdk from 'aws-cdk-lib'; - import { Construct } from 'constructs'; - import * as lambda from 'aws-cdk-lib/aws-lambda'; - - export class NewRelicExampleCdkStack extends cdk.Stack { - constructor(scope: Construct, id: string, props?: cdk.StackProps) { - super(scope, id, props); - // Add latest New Relic Lambda layer ARN from https://layers.newrelic-external.com - const NewReliclayerArn = 'arn:aws:lambda:us-east-1:451483290750:layer:NewRelicNodeJS20X:39'; - const myFunction = new lambda.Function(this, "NewRelicExampleLambda", { - runtime: lambda.Runtime.NODEJS_20_X, - // Update functions handler to point to the New Relic Lambda wrapper - handler: "newrelic-lambda-wrapper.handler", - code: lambda.Code.fromAsset('lib/lambda-runtime-code'), - layers: [lambda.LayerVersion.fromLayerVersionArn(this, 'NewRelicLayer', NewReliclayerArn)], - environment: { - // Set the NEW_RELIC_LAMBDA_HANDLER environment variable to the path of your initial handler. - NEW_RELIC_LAMBDA_HANDLER: 'index.handler', - }, - }); - } - } - ``` + Para usar o New Relic com o AWS CDK, siga estes passos: + + 1. Instale a [camada Lambda do New Relic](https://layers.newrelic-external.com/). Abaixo está um exemplo de um aplicativo CDK básico que implanta uma função New Relic instrumentada Node.js do Lambda: + + ```ts + import * as cdk from 'aws-cdk-lib'; + import { Construct } from 'constructs'; + import * as lambda from 'aws-cdk-lib/aws-lambda'; + + export class NewRelicExampleCdkStack extends cdk.Stack { + constructor(scope: Construct, id: string, props?: cdk.StackProps) { + super(scope, id, props); + // Add latest New Relic Lambda layer ARN from https://layers.newrelic-external.com + const NewReliclayerArn = 'arn:aws:lambda:us-east-1:451483290750:layer:NewRelicNodeJS22X:38'; + const myFunction = new lambda.Function(this, "NewRelicExampleLambda", { + runtime: lambda.Runtime.NODEJS_20_X, + // Update functions handler to point to the New Relic Lambda wrapper + handler: "newrelic-lambda-wrapper.handler", + code: lambda.Code.fromAsset('lib/lambda-runtime-code'), + layers: [lambda.LayerVersion.fromLayerVersionArn(this, 'NewRelicLayer', NewReliclayerArn)], + environment: { + // Set the NEW_RELIC_LAMBDA_HANDLER environment variable to the path of your initial handler. + NEW_RELIC_LAMBDA_HANDLER: 'index.handler', + NEW_RELIC_APM_LAMBDA_MODE: 'true' + }, + }); + // Add the New Relic APM Lambda Mode tag + cdk.Tags.of(myFunction).add('NR.Apm.Lambda.Mode', 'true'); + } + } + ``` + + 2. Configure as [variáveis de ambiente](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) necessárias. + + 3. implante sua função do Lambda com a configuração atualizada. Terraform é uma infraestrutura popular de uso geral como ferramenta de código. Ele pode ser usado para gerenciar recursos da AWS. Oferecemos [alguns exemplos](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/terraform) de New Relic instrumentado com função de implantação Lambda usando script Terraform. - Você pode usar o [provedor New Relic Terraform](https://registry.terraform.io/providers/newrelic/newrelic/latest/docs/resources/cloud_aws_integrations) para configurar sua integração AWS . + Você pode usar o [provedor Terraform New Relic ](https://registry.terraform.io/providers/newrelic/newrelic/latest/docs/resources/cloud_aws_integrations)para configurar sua integração AWS. Após configurar o provedor, configure as [variáveis de ambiente](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) necessárias e adicione a tag `NR.Apm.Lambda.Mode: true` à sua função do Lambda. @@ -210,6 +251,10 @@ Dependendo de suas necessidades, você pode optar por ignorar a extensão e ver A camada New Relic entregará automaticamente o agente New Relic Ruby e será carregada por meio de um Ruby `require` antes da invocação da sua função do Lambda. Para evitar conflitos, não inclua uma cópia do agente Ruby em nenhum outro lugar. Sinta-se à vontade para realizar qualquer chamada de API do agente New Relic Ruby desejada em sua função para aproveitar a presença do agente. + 14. No seu Console de Gerenciamento AWS, na guia de configuração, adicione a tag `NR.Apm.Lambda.Mode: true` à sua função do Lambda. + + 15. implante sua função do Lambda com a configuração atualizada. + Os tempos de execução Java, Python, Node.js e .Net seguirão o mesmo fluxo de instrumentação do Ruby, mas com alguns manipuladores diferentes. Veja como atualizar o manipulador da sua função para apontar para a camada recém-anexada no console da sua função: * Java: @@ -230,26 +275,32 @@ Dependendo de suas necessidades, você pode optar por ignorar a extensão e ver -## Métodos de Envio +## Encontre e use dados [#find-data] - - - Cada camada de agente também contém uma extensão para enviar log e carga para o New Relic, ignorando o CloudWatch. Isso pode ajudar a reduzir a latência e os custos. No entanto, corre o risco de afetar o desempenho e a confiabilidade de sua função. +Após instrumentar sua função AWS do Lambda, você poderá encontrar e usar os dados na interface do New Relic APM. Os dados estão organizados em diversas áreas principais, cada uma fornecendo diferentes insights sobre o desempenho e a saúde da sua função Lambda. - Depois de adicionar uma camada New Relic Lambda, a extensão é habilitada e tem o envio de log desabilitado por padrão. +Na interface APM, você pode explorar vários aspectos da sua função Lambda, incluindo [distributed tracing](/docs/distributed-tracing/concepts/introduction-distributed-tracing/), [mapas de serviço](/docs/new-relic-solutions/new-relic-one/ui-data/service-maps/service-maps/), [transações](/docs/apm/transactions/intro-transactions/transactions-new-relic-apm/), [análise de erros](/docs/errors-inbox/getting-started/) e muito mais. Cada uma dessas áreas fornece insights detalhadas sobre o desempenho, a latência e a taxa de erros da sua função Lambda, permitindo que você identifique e resolva problemas rapidamente. - Se quiser ver o log de funções no New Relic, você precisará habilitar o envio de extensão do log de funções com uma variável de ambiente. + + A experiência de invocação agora está integrada ao rastreamento de transações do APM. Isso permite que você use um `AWS RequestId` específico para detalhar um trace APM de transação para obter informações detalhadas sobre aquela execução Lambda específica. + - É importante observar que o log da função é apenas o log registrado pela função durante sua invocação. A extensão não enviará log de tempo de execução do Lambda como `START`, `END` e `REPORT` linhas. - +Para visualizar sua função Lambda na interface do New Relic APM : - - Você pode escolher enviar dados somente para o CloudWatch ou como fallback. Para saber mais, consulte nossa [documentação de fallback do CloudWatch](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/cloud-watch-fallback). - - +1. Vá para [https://one.newrelic.com](https://one.newrelic.com) > APM & Services. -## Qual é o próximo +2. Defina os critérios de pesquisa como `isLambdaFunction = true`. + +3. Na lista exibida, selecione sua função Lambda para visualizar os dados. + +## Artigos relacionados [#related-docs] - Saiba mais sobre os tempos de execução suportados e pré-requisitos Aprenda a usar o New Relic para monitorar sua função do Lambda na AWS Aprenda a solucionar problemas relacionados à instalação + + Saiba mais sobre os tempos de execução e pré-requisitos suportados + + + + Aprenda a solucionar problemas relacionados à instalação + \ No newline at end of file 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 281538726e1..5bdad35c76b 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 @@ -7,40 +7,155 @@ translationType: machine A instrumentação da New Relic para AWS Lambda oferece visibilidade profunda do funcionamento interno de suas funções. Ao adicionar o agente New Relic à sua função, cada invocação é monitorada pelo New Relic. Isso permite que você rastreie a duração das invocações de funções, monitore erros e registre detalhes sobre o evento de origem e as respostas da sua função. -new-relic-lambda-entities-screenshot.png +/\* AWS Lambda fornece um serviço de computação altamente escalável e orientado a eventos, permitindo que você crie e execute aplicativos e serviços backend sem a necessidade de provisionar ou gerenciar servidores. À medida que sua arquitetura sem servidor no Lambda se torna mais sofisticada e assume funções críticas para os negócios, obter visibilidade abrangente de seu desempenho, saúde operacional e interação dentro de seu ecossistema de aplicativos mais amplo torna-se essencial para manter a confiabilidade e a eficiência. Seu aplicativo moderno depende fortemente de inúmeras funções do Lambda da AWS interagindo com vários outros microsserviços, banco de dados e APIs de terceiros. Em ambientes tão complexos, você pode encontrar diversos desafios de observabilidade: \* \*\*Dificuldade em identificar as causas raiz:\*\* Quando ocorrem problemas de desempenho, como lentidão intermitente, ou quando transações críticas envolvendo funções Lambda falham, identificar a função com falha ou a origem do problema pode ser um quebra-cabeça complexo. \* \*\*Visualizações de monitoramento isoladas:\*\* Você pode se encontrar navegando entre uma interface dedicada de monitoramento Serverless e suas visualizações tradicionais de monitoramento de desempenho de aplicativos (APM), dificultando a obtenção de uma visão única e unificada do desempenho. \* \*\*Correlação de dados ineficaz:\*\* Pode ser difícil correlacionar efetivamente dados de desempenho e eventos quando as informações residem em sistemas separados de monitoramento serverless e APM. \* \*\*Rastreamento ponta a ponta incompleto:\*\* Você pode enfrentar desafios ao rastrear perfeitamente uma única solicitação de ponta a ponta, à medida que ela percorre a função do Lambda e outros serviços em seu ambiente distribuído. \* \*\*Monitoramento limitado para Lambda:\*\* Muitas vezes, não é possível aplicar todo o poder de diagnóstico e o fluxo de trabalho familiar das ferramentas APM diretamente à sua função Lambda. \* \*\*Esforço manual para obter insights:\*\* Frequentemente, é necessário um esforço manual significativo para reunir informações dispersas de várias fontes para entender o contexto completo de um problema envolvendo o Lambda. Para lidar com esses desafios de observabilidade e proporcionar uma experiência de monitoramento verdadeiramente unificada, New Relic está aprimorando a forma como as funções Lambda da AWS são integradas à nossa plataforma. Essa iniciativa integra sua função serverless diretamente à experiência New Relic APM, tratando-a como um recurso de primeira classe, juntamente com seus outros serviços instrumentados. Nosso objetivo é fornecer telemetria completa e adaptada ao aplicativo para sua função Lambda, tornando mais fácil do que nunca entender seu desempenho em seu contexto total. \*/ -## Métodos de envio para telemetria Lambda [#shipping-methods] +## Recurso chave [#key-features] -Existem três métodos principais para enviar dados de telemetria do AWS Lambda para o New Relic, cada um com suas próprias considerações de custo e confiabilidade: +* **Obtenha uma visão unificada:** Monitore sua função Lambda na mesma interface APM que você usa para seus outros serviços. Visualize a telemetria sem servidor, incluindo métricas de desempenho, rastreamento, logs (quando configurados) e erros — tudo correlacionado em um só lugar, eliminando a necessidade de alternar entre diferentes interfaces. -* **Método econômico**: utilize as camadas do New Relic, incluindo a extensão Lambda, que evita o envio de dados para o AWS CloudWatch por padrão. -* **Método focado em confiabilidade**: desabilite a extensão Lambda do New Relic e use o CloudWatch exclusivamente para enviar dados, reduzindo a sobrecarga da função do Lambda. -* **Método híbrido**: combine a extensão com o CloudWatch como fallback, equilibrando eficiência de custos com confiabilidade. +* **Aproveite todo o poder do APM:** Aplique o conjunto abrangente de recursos do New Relic APM diretamente à sua função Lambda. Isso inclui distributed tracing avançado, análise detalhada de erros com a Caixa de Entrada de Erros, mapas de serviço que incorporam sua função Lambda, dashboards e muito mais. Para obter mais informações, consulte a [documentação do APM](https://docs.newrelic.com/docs/apm/new-relic-apm/getting-started/introduction-apm/). -## Consideração de custos [#costs] +* **Obtenha rastreamento completo de ponta a ponta das solicitações:** trace perfeitamente requests à medida que fluem de seus serviços de front-end ou outros microsserviços, passando por sua função AWS Lambda e chegando a quaisquer componentes conectados. Isso fornece uma imagem clara e ininterrupta da latência e dependência da solicitação em toda a sua arquitetura. Para obter mais informações, consulte a [documentação distributed tracing ](https://docs.newrelic.com/docs/distributed-tracing/concepts/introduction-distributed-tracing/). -A implementação do monitoramento Serverless para AWS Lambda pode incorrer em cobranças adicionais AWS. A função `newrelic-log-ingestion` do Lambda, que reporta dados ao New Relic, é considerada um serviço de terceiros, e quaisquer cobranças associadas AWS são de responsabilidade do usuário. +* **Simplifique a análise da causa raiz:** Ao consolidar os dados serverless com o restante da telemetria do seu aplicativo no APM, você pode identificar e diagnosticar rapidamente os problemas, independentemente de sua origem em uma função Lambda ou em um serviço upstream/downstream. -Se você usar nossa [extensão newrelic-lambda](https://github.com/newrelic/newrelic-lambda-extension) incluída em nossas [Camadas LambdaNew Relic ](https://github.com/newrelic/newrelic-lambda-layers), poderá evitar o envio de log e telemetria via CloudWatch e a função [newrelic-log-ingestion](https://github.com/newrelic/aws-log-ingestion) . Também é possível configurar a função [newrelic-log-ingestion](https://github.com/newrelic/aws-log-ingestion) como um método [de fallback do CloudWatch](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/cloud-watch-fallback/) para funções que exigem alta disponibilidade de dados de observabilidade. +* **Entenda melhor o impacto da computação sem servidor:** veja claramente como suas funções Lambda contribuem para a saúde e o desempenho geral do seu aplicativo e para as principais transações comerciais, fornecendo insights mais profundos sobre seu papel em seus serviços digitais. + +New Relic Lambda Entities in APM + +## Como configurar o monitoramento do AWS Lambda? [#config] + +Para monitorar sua função AWS Lambda com o New Relic, você pode configurar a instrumentação em diferentes ambientes, tempos de execução e métodos de implantação. Os passos a seguir orientam você durante o processo de configuração: + + + + ### Compatibilidade e requisitos [#req] + + Certifique-se de que sua função AWS Lambda atenda aos nossos [requisitos e à nossa compatibilidade](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/compatibility-requirement-lambda-monitoring). + + + + ### (Opcional) Vincule sua conta da AWS ao New Relic. [#link] + + Ao vincular contas, você concede à New Relic permissão para criar um inventário da sua conta AWS e coletar automaticamente métricas do CloudWatch para sua função do Lambda. Depois de vincular contas, os recursos na sua conta AWS aparecem como entidade no [explorador de entidades](/docs/new-relic-solutions/new-relic-one/core-concepts/new-relic-explorer-view-performance-across-apps-services-hosts/#find). A função do Lambda entidade será encontrada na visualização sem servidor. + + Você pode vincular sua conta da AWS e da New Relic por um dos seguintes métodos de integração. + + + + AWS Metric Streams (recomendado) API Polling + + + + + Para que New Relic monitore sua função Lambda, você precisa configurar uma integração entre New Relic e AWS. Recomendamos o uso do [Metric Streams](/install/aws-cloudwatch) para ajudar a reduzir a latência e evitar a limitação de nossas requests de polling. + + + + Se você não estiver usando uma integração com o Métrica Streams, pode optar por configurar uma integração [API Polling](/docs/infrastructure/amazon-integrations/connect/set-up-aws-api-polling). Por padrão, uma integração de API Polling com o serviço Lambda ativado coletará métricas do CloudWatch a cada 5 minutos. + + Você pode usar o [newrelic-lambda-cli](https://github.com/newrelic/newrelic-lambda-cli) para configurar uma integração API Polling, mas não uma integração métrica de Streams. + + ```sh + newrelic-lambda integrations install --nr-account-id YOUR_NR_ACCOUNT_ID \ + --nr-api-key YOUR_NEW_RELIC_USER_KEY + ``` + + Uma etapa no [comando integração install](https://github.com/newrelic/newrelic-lambda-cli?tab=readme-ov-file#aws-lambda-integration) criará um segredo `NEW_RELIC_LICENSE_KEY` no [AWS Secrets Manager](https://aws.amazon.com/secrets-manager/) para maior segurança. Isso é configurável com um sinalizador `--disable-license-key-secret` , juntamente com outras opções e sinalizadores. + + + + + + + ### Instrumento sua função AWS do Lambda [#instrument] + + Para instrumentalizar sua função do Lambda, você precisa de um agente e de uma extensão. Esses componentes são agrupados na [camada Lambda](https://github.com/newrelic/newrelic-lambda-layers) do New Relic. Se usar camadas Lambda não for uma opção para você, você pode incorporar manualmente o agente e a extensão em sua função. Com base no requisito da sua função do Lambda, selecione um dos seguintes métodos de instrumentação: + + + + Instrumentação em camadas Instrumentação baseada em SDK Instrumentação em contêiner + + + + + Use este método se sua função do Lambda estiver empacotada como um arquivo Zip e você puder adicionar camadas. Camadas são mecanismos de distribuição para biblioteca, tempos de execução personalizados e outras dependências. Para obter mais informações, consulte a documentação [de instrumentação em camadas](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/instrument-your-own/) . + + + + Utilize este método caso sua função do Lambda não possa utilizar camadas, garantindo uma implantação rápida sem a necessidade de modificar camadas. Para obter mais informações, consulte a documentação [de instrumentação baseada em SDK](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/sdk-based-instrumentation/) . + + + + Use este método se sua função do Lambda for executada dentro de um contêiner. A tela fornece um ambiente de execução consistente e isolado para seu aplicativo. A New Relic fornece uma imagem Docker pré-configurada que inclui a camada New Relic Lambda, a extensão New Relic Lambda e o agente New Relic. Para obter mais informações, consulte a documentação [sobre instrumentação em contêineres](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/containerized-images/). + + + + + + + ### Configurar variáveis de ambiente [#env-variables] + + + * Quando você instrumenta a camada Lambda do New Relic com o New Relic CLI, suas variáveis de ambiente obrigatórias são configuradas automaticamente. No entanto, você pode querer alterar algumas das configurações padrão e configurar sua função do Lambda com as variáveis de ambiente que correspondem às suas necessidades de monitoramento. + * Se estiver usando a extensão Lambda do New Relic, você precisará configurar as variáveis de ambiente manualmente. + + + [Variáveis de ambiente](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) são usadas para configurar o agente New Relic e a extensão Lambda. É importante definir essas variáveis corretamente para garantir que sua função do Lambda seja monitorada corretamente. + + + + ### Encontre seus dados no New Relic [#data] + + Após instrumentar sua função AWS do Lambda, você poderá encontrar e usar os dados na interface do New Relic APM. Os dados estão organizados em diversas áreas principais, cada uma fornecendo diferentes insights sobre o desempenho e a saúde da sua função Lambda. + + + +## Experimente nossas funções de exemplo [#example] + +Depois de instrumentar a camada Lambda do New Relic, recomendamos fortemente experimentar nossas funções de exemplo. Esses exemplos de trabalho devem ser usados como ponto de partida para instrumentar sua própria função serverless. O uso desses exemplos pode ajudá-lo a se familiarizar com a camada New Relic Lambda, testando o link da conta, e eles podem ser usados como referência para sua própria instrumentação. Each example demonstrates adding permissions, runtime-specific techniques for wrapping your handler, managing function log retention in CloudWatch, and more. + +Embora existam muitas maneiras de gerenciar e implantar a função do Lambda, AWS CloudFormation é o mecanismo que usamos em nossos exemplos. + +Nossos exemplos são publicados, juntamente com a extensão New Relic Lambda, neste [repositório GitHub](https://github.com/newrelic/newrelic-lambda-extension). Há um para cada tempo de execução do Lambda que o New Relic suporta: + +* [Node.js](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/sam/node) +* [Python](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/sam/python) +* [Go](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/sam/go) +* [Java](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/sam/java) +* [Ruby](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/sam/ruby) +* [.NET](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/sam/dotnet) + +Você também pode aprender como transformar distributed tracing em um aplicativo sem servidor não trivial em nosso [exemplodistributed tracing ](https://github.com/newrelic/newrelic-lambda-extension/tree/main/examples/sam/distributedtracing). Ele ilustra a propagação manual trace para SQS e SNS, dois dos serviços mais populares que podem invocar a função do Lambda, com funções Node, Python, Ruby e Java. - Não importa qual método de envio seja usado, a carga e a experiência no New Relic permanecem as mesmas. + Ao testar manualmente, os dados de telemetria podem ser atrasados. Recomendamos aguardar sete segundos antes de invocar a função novamente, permitindo que qualquer telemetria armazenada em buffer seja entregue. -Ativar o monitoramento Serverless para AWS Lambda pode resultar em cobranças da Amazon Web Services. Nossa `newrelic-log-ingestion` função do Lambda, que nos reporta seus dados Lambda, é considerada um [serviço de terceiros](/docs/licenses/license-information/acceptable-use-policy/acceptable-use-policy): as cobranças AWS resultantes de seu uso são de sua responsabilidade. +## Consideração de custos [#costs] + +A implementação do monitoramento Serverless para AWS Lambda pode incorrer em cobranças adicionais AWS . A função `newrelic-log-ingestion` do Lambda, que reporta dados ao New Relic, é considerada um serviço de terceiros, e quaisquer cobranças associadas AWS são de responsabilidade do usuário. Ao usar o [`newrelic-lambda-extension`](https://github.com/newrelic/newrelic-lambda-extension) incluído nas [camadas do New Relic Lambda](https://github.com/newrelic/newrelic-lambda-layers), você pode evitar o envio de logs e dados de telemetria via CloudWatch, embora seja possível configurar a função `newrelic-log-ingestion` como um fallback do CloudWatch para necessidades de alta disponibilidade. + +Habilitar o monitoramento Serverless para AWS Lambda pode resultar em cobranças da Amazon Web Services. Nossa função `newrelic-log-ingestion` do Lambda, que nos envia seus dados Lambda, é considerada um [Serviço de Terceiros](/docs/licenses/license-information/general-usage-licenses/acceptable-use-policy): as taxas AWS resultantes do seu uso são de sua responsabilidade. + +Se você usar nossa [extensão newrelic-lambda](https://github.com/newrelic/newrelic-lambda-extension) incluída em nossas [Camadas LambdaNew Relic ](https://github.com/newrelic/newrelic-lambda-layers), poderá evitar o envio de log e telemetria via CloudWatch e a função [newrelic-log-ingestion](https://github.com/newrelic/aws-log-ingestion) . Também é possível configurar a função [newrelic-log-ingestion](https://github.com/newrelic/aws-log-ingestion) como um método [de fallback do CloudWatch](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/cloud-watch-fallback/) para funções que exigem alta disponibilidade de dados de observabilidade. + +## Preços [#pricing] + +O uso do New Relic APM + Serverless Convergence por você será cobrado como uma entidade APM, de acordo com o seu pedido. Para obter mais detalhes sobre preços, entre em contato com nossa equipe de vendas ou consulte seu pedido. -## Qual é o próximo +## Artigos relacionados [#related-docs] - - Saiba mais sobre os tempos de execução e pré-requisitos suportados + + instrumento sua função do Lambda com a abordagem em camadas do New Relic. - - Comece com instrumentação e configuração para sua função do Lambda + + instrumento sua função do Lambda usando SDK. - - Aprenda como usar New Relic para monitorar sua função do Lambda AWS + + instrumento sua função do Lambda com a abordagem conteinerizada da New Relic. \ No newline at end of file diff --git a/src/i18n/content/pt/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/sdk-based-instrumentation.mdx b/src/i18n/content/pt/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/sdk-based-instrumentation.mdx index 1e267315b02..5fa2ecb6a51 100644 --- a/src/i18n/content/pt/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/sdk-based-instrumentation.mdx +++ b/src/i18n/content/pt/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/sdk-based-instrumentation.mdx @@ -67,9 +67,11 @@ Selecione seu tempo de execução abaixo e siga as instruções de configuraçã - 5. Para habilitar [distributed tracing](/docs/apm/distributed-tracing/getting-started/introduction-distributed-tracing) e configurar variáveis de ambiente, consulte a documentação [das variáveis de ambiente](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) . + 5. Configure as [variáveis de ambiente](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda). - 6. Invoque o Lambda pelo menos uma vez. Isso cria um grupo log do CloudWatch, que deve estar presente para que a próxima etapa funcione. + 6. No seu Console de Gerenciamento AWS, na guia de configuração, adicione a tag `NR.Apm.Lambda.Mode: true` à sua função do Lambda. + + 7. Invoque o Lambda pelo menos uma vez. Isso cria um grupo log do CloudWatch, que deve estar presente para que a próxima etapa funcione. Nosso wrapper coleta dados sobre a execução do Lambda, gera uma mensagem JSON e registra-a no log do CloudWatch. A seguir, você [configurará o CloudWatch para enviar esses logs para o New Relic](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/instrument-your-own/#manual-stream-logs). @@ -130,9 +132,11 @@ Selecione seu tempo de execução abaixo e siga as instruções de configuraçã 6. No console do AWS Lambda, defina o manipulador. Para o [exemplo Java Lambda](https://github.com/newrelic/newrelic-lambda-tracer-java#usage), o manipulador seria `com.handler.example.MyLambdaHandler::handleRequest`. Como `handleRequest` é assumido, você também pode usar `com.handler.example.MyLambdaHandler`. - 7. Para habilitar [distributed tracing](/docs/apm/distributed-tracing/getting-started/introduction-distributed-tracing) e configurar variáveis de ambiente, consulte a documentação [das variáveis de ambiente](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) . + 7. Configure as [variáveis de ambiente](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda). + + 8. No seu Console de Gerenciamento AWS, na guia de configuração, adicione a tag `NR.Apm.Lambda.Mode: true` à sua função do Lambda. - 8. Invoque o Lambda pelo menos uma vez. Isso cria um grupo log do CloudWatch, que deve estar presente para que a próxima etapa funcione. + 9. Invoque o Lambda pelo menos uma vez. Isso cria um grupo log do CloudWatch, que deve estar presente para que a próxima etapa funcione. Nosso wrapper coleta dados sobre a execução do Lambda, gera uma mensagem JSON e registra-a no log do CloudWatch. A seguir, você [configurará o CloudWatch para enviar esses logs para o New Relic](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/instrument-your-own/#manual-stream-logs). @@ -211,9 +215,11 @@ Selecione seu tempo de execução abaixo e siga as instruções de configuraçã 5. Carregue o arquivo compactado em sua conta do AWS Lambda. - 6. Para habilitar [distributed tracing](/docs/apm/distributed-tracing/getting-started/introduction-distributed-tracing) e configurar variáveis de ambiente, consulte a documentação [das variáveis de ambiente](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) . + 6. Configure as [variáveis de ambiente](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda). + + 7. No seu Console de Gerenciamento AWS, na guia de configuração, adicione a tag `NR.Apm.Lambda.Mode: true` à sua função do Lambda. - 7. Para concluir a instrumentação, siga uma das seguintes etapas para enviar os dados de telemetria para o New Relic: + 8. Para concluir a instrumentação, siga uma das seguintes etapas para enviar os dados de telemetria para o New Relic: * Use o Lambda New Relic `Extension layer`. Você pode obter a camada mais recente [(NewRelicLambdaExtension)](https://layers.newrelic-external.com/) arn. Você pode usar a AWS CLI para instalar a camada ou adicioná-la manualmente ao seu Lambda. @@ -269,9 +275,11 @@ Selecione seu tempo de execução abaixo e siga as instruções de configuraçã 6. Carregue o arquivo compactado em sua conta do AWS Lambda. - 7. Para habilitar [distributed tracing](/docs/apm/distributed-tracing/getting-started/introduction-distributed-tracing) e configurar variáveis de ambiente, consulte a documentação [das variáveis de ambiente](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) . + 7. Configure as [variáveis de ambiente](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda). - 8. Invoque o Lambda pelo menos uma vez. Isso cria um grupo log do CloudWatch, que deve estar presente para que a próxima etapa funcione. + 8. No seu Console de Gerenciamento AWS, na guia de configuração, adicione a tag `NR.Apm.Lambda.Mode: true` à sua função do Lambda. + + 9. Invoque o Lambda pelo menos uma vez. Isso cria um grupo log do CloudWatch, que deve estar presente para que a próxima etapa funcione. O decorador New Relic coleta dados sobre a execução do Lambda, gera uma mensagem JSON e registra-a no log do CloudWatch. Em seguida, [configure o CloudWatch para enviar esses logs para o New Relic](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/instrument-your-own/#manual-stream-logs). @@ -282,25 +290,38 @@ Selecione seu tempo de execução abaixo e siga as instruções de configuraçã Para instrumentar seu .NET Lambda: 1. Adicione o [pacote nuget NewRelic.Agente](https://www.nuget.org/packages/NewRelic.Agent) ao seu projeto AWS Lambda . Para obter mais informações, consulte nosso [guia de instalação](/docs/apm/agents/net-agent/install-guides/install-net-agent-using-nuget/). - 2. Para habilitar [distributed tracing](/docs/apm/distributed-tracing/getting-started/introduction-distributed-tracing) e configurar variáveis de ambiente, consulte a documentação [das variáveis de ambiente](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) . - 3. Publique o projeto em sua conta do AWS Lambda. - 4. [Configure](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/account-linking/) a extensão New Relic Lambda ou o lambda `newrelic-log-ingestion` . - 5. Invoque o Lambda pelo menos uma vez para verificar se há erros e garantir que os dados estejam visíveis na interface New Relic . + 2. Configure as [variáveis de ambiente](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda). + 3. No seu Console de Gerenciamento AWS, na guia de configuração, adicione a tag `NR.Apm.Lambda.Mode: true` à sua função do Lambda. + 4. Publique o projeto em sua conta do AWS Lambda. + 5. [Configure](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/account-linking/) a extensão New Relic Lambda ou o lambda `newrelic-log-ingestion` . + 6. Invoque o Lambda pelo menos uma vez para verificar se há erros e garantir que os dados estejam visíveis na interface New Relic . -## Qual é o próximo +## Encontre e use dados [#find-data] + +Após instrumentar sua função AWS do Lambda, você poderá encontrar e usar os dados na interface do New Relic APM. Os dados estão organizados em diversas áreas principais, cada uma fornecendo diferentes insights sobre o desempenho e a saúde da sua função Lambda. + +Na interface APM, você pode explorar vários aspectos da sua função Lambda, incluindo [distributed tracing](/docs/distributed-tracing/concepts/introduction-distributed-tracing/), [mapas de serviço](/docs/new-relic-solutions/new-relic-one/ui-data/service-maps/service-maps/), [transações](docs/apm/transactions/intro-transactions/transactions-new-relic-apm//), [análise de erros](docs/errors-inbox/getting-started/) e muito mais. Cada uma dessas áreas fornece insights detalhadas sobre o desempenho, a latência e a taxa de erros da sua função Lambda, permitindo que você identifique e resolva problemas rapidamente. + + + A experiência de invocação agora está integrada ao rastreamento de transações do APM. Isso permite que você use um `AWS RequestId` específico para detalhar um trace APM de transação para obter informações detalhadas sobre aquela execução Lambda específica. + + +Para visualizar sua função Lambda na interface do New Relic APM : + +1. Vá para [https://one.newrelic.com](https://one.newrelic.com) > APM & Services. +2. Defina os critérios de pesquisa como `isLambdaFunction = true`. +3. Na lista exibida, selecione sua função Lambda para visualizar os dados. + +## Artigos relacionados [#related-docs] Saiba mais sobre os tempos de execução e pré-requisitos suportados - - Aprenda como usar New Relic para monitorar sua função do Lambda AWS - - - + Aprenda a solucionar problemas relacionados à instalação \ No newline at end of file diff --git a/src/i18n/content/pt/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/update-lambda-monitoring.mdx b/src/i18n/content/pt/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/update-lambda-monitoring.mdx index 11f97935736..05518a0c752 100644 --- a/src/i18n/content/pt/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/update-lambda-monitoring.mdx +++ b/src/i18n/content/pt/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/update-lambda-monitoring.mdx @@ -5,7 +5,7 @@ freshnessValidatedDate: never translationType: machine --- -Depois [de ativar nosso monitoramento para AWS Lambda](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/enable-new-relic-monitoring-aws-lambda), você deve atualizar ocasionalmente nossa função do Lambda que é usada para relatar dados de log da AWS: `newrelic-log-ingestion`. +Após [habilitar nosso monitoramento para AWS Lambda](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda/#link), você deve atualizar ocasionalmente nossa função do Lambda que é usada para relatar dados de log AWS : `newrelic-log-ingestion`. Existem duas maneiras de fazer isso: @@ -13,7 +13,7 @@ Existem duas maneiras de fazer isso: * [Atualização via AWS Serverless Application Repository](#update-sar): Use isto se você habilitou usando o [procedimento manual](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/enable-new-relic-monitoring-aws-lambda#manual-nr-lambda). - Esses procedimentos de atualização se aplicam ao nosso [monitoramento Serverless para AWS Lambda](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/introduction-new-relic-monitoring-aws-lambda), e não ao nosso [monitoramento de infraestrutura para integração do AWS Lambda](/docs/integrations/amazon-integrations/aws-integrations-list/aws-lambda-monitoring-integration). + Esses procedimentos de atualização se aplicam ao nosso [monitoramento Serverless para AWS Lambda](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda), e não ao nosso [monitoramento de infraestrutura para integração AWS Lambda ](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-lambda-monitoring-integration). ## Atualize nossa integração Lambda via CLI [#update-cli] @@ -60,6 +60,7 @@ Esta seção descreve como atualizar a camada da sua função se você a instalo --function installed \ --nr-account-id NR_ACCOUNT_ID \ --upgrade + --apm ``` ## Atualizar uma instalação manual do repositório de aplicativos Serverless [#update-sar] diff --git a/src/i18n/content/pt/docs/serverless-function-monitoring/aws-lambda-monitoring/troubleshooting/troubleshoot-enabling-serverless-monitoring-aws-lambda.mdx b/src/i18n/content/pt/docs/serverless-function-monitoring/aws-lambda-monitoring/troubleshooting/troubleshoot-enabling-serverless-monitoring-aws-lambda.mdx index b532f3d9323..401f9a3ea0c 100644 --- a/src/i18n/content/pt/docs/serverless-function-monitoring/aws-lambda-monitoring/troubleshooting/troubleshoot-enabling-serverless-monitoring-aws-lambda.mdx +++ b/src/i18n/content/pt/docs/serverless-function-monitoring/aws-lambda-monitoring/troubleshooting/troubleshoot-enabling-serverless-monitoring-aws-lambda.mdx @@ -1,5 +1,5 @@ --- -title: Solucionar problemas de habilitação do monitoramento Serverless do AWS Lambda +title: Resolução de problemas do monitoramento de Lambda type: troubleshooting tags: - Serverless function monitoring @@ -12,22 +12,22 @@ translationType: machine ## Problema -Você está tentando habilitar [o monitoramento Serverless para AWS Lambda](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/introduction-new-relic-monitoring-aws-lambda) e está tendo um problema ou erro. +Você está tentando habilitar [o monitoramento Serverless para AWS Lambda](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda) e está enfrentando um problema ou erro. ## Solução -Existem dois problemas comuns relacionados à não conclusão de todos os [procedimentos de habilitação](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/enable-new-relic-monitoring-aws-lambda): +Existem dois problemas comuns relacionados à não conclusão de todos os [procedimentos de habilitação](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda/#link): -* Não estou vendo dados na página da interface do usuário **CloudWatch metrics** . Isso significa que a [etapa de integração da AWS](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/enable-new-relic-monitoring-aws-lambda#connect-aws) não foi concluída. -* Não vejo dados em **Troubleshooting** páginas de interface de categoria. Se você não estiver vendo dados nas guias de interface **Distributed tracing**, **Errors** e **Invocations** , isso significa que a [etapa de instrumentação de agente do APM](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/enable-new-relic-monitoring-aws-lambda#instrument-lambda) não foi concluída. +* Não consigo visualizar os dados na página da interface do usuário **Lambda metrics**. Isso significa que a [etapa de integração com a AWS](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda/#link) não foi concluída. +* Não consigo visualizar dados nas páginas da interface do usuário da categoria **Troubleshooting**. Se você não estiver vendo dados nas guias de interface **Distributed tracing**, **Errors** e **Invocations**, isso significa que a [etapa de instrumentação de agenteAPM ](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda/#instrument)não foi concluída. Além desses problemas básicos de ativação, existem alguns problemas adicionais que podem causar problemas: -* Erro do CloudWatch "Erro HTTP 401: não autorizado". Isso ocorre devido a uma chave de API incorreta. O argumento `--nr-api-key`na [etapa Configurar ativação da AWS](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/enable-new-relic-monitoring-aws-lambda#connect-aws) pega seu . +* Erro do CloudWatch: "Erro HTTP 401: não autorizado". Isso ocorre devido a uma chave de API incorreta. O argumento `--nr-api-key`na [etapa Configure AWS enable](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/introduction-lambda/#link) usa seu . * Faltam métricas personalizadas. A monitorização lambda não é compatível com a nossa [métrica personalizada](/docs/agents/manage-apm-agents/agent-data/collect-custom-metrics). Use [atributo personalizado](/docs/agents/manage-apm-agents/agent-data/collect-custom-attributes) para adicionar metadados. -* Faltam invocações. Para ver os detalhes do detalhamento da invocação, distributed tracing deve ser habilitado como parte da [etapa de instrumentação do Lambda](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/enable-new-relic-monitoring-aws-lambda#instrument-lambda). distributed tracing é necessário para que os detalhes do intervalo possam ser exibidos no painel de detalhes da chamada. +* Aba de invocações ausente. Com APM + Serverless Convergence, cada invocação Lambda corresponde ao trace da transação no APM. Para ver detalhes da decomposição da invocação, consulte [trace da transação](/docs/apm/apm-ui-pages/monitoring/transactions-page-find-specific-performance-problems). * Você concluiu as etapas de instalação, integração e instrumentação corretamente e sua função está enviando log para o CloudWatch, mas você não está vendo rastreamento de dependência específica (ou qualquer rastreamento) na interface. Isso pode resultar da ordem de fusão das camadas (se você estiver usando nossas camadas Lambda) ou da ordem de importação (se você estiver usando o instrumento manualmente): diff --git a/src/i18n/content/pt/docs/serverless-function-monitoring/aws-lambda-monitoring/troubleshooting/troubleshoot-no-data-appears.mdx b/src/i18n/content/pt/docs/serverless-function-monitoring/aws-lambda-monitoring/troubleshooting/troubleshoot-no-data-appears.mdx index 2f6554d86f4..805519a8ded 100644 --- a/src/i18n/content/pt/docs/serverless-function-monitoring/aws-lambda-monitoring/troubleshooting/troubleshoot-no-data-appears.mdx +++ b/src/i18n/content/pt/docs/serverless-function-monitoring/aws-lambda-monitoring/troubleshooting/troubleshoot-no-data-appears.mdx @@ -10,12 +10,22 @@ freshnessValidatedDate: never translationType: machine --- -## Problema +## Problema [#problem] Depois de gerar tráfego para sua função do Lambda AWS e esperar cinco minutos, nenhum dado de sua função aparece na interface do New Relic . Não há erros no log nem `NRIntegrationErrors` ou `NRIntegrationWarnings` na interface do New Relic . -## Solução +## Solução [#solution] + +### Verifique a chave de licença e o ID da conta. [#check-license] O motivo mais comum para nenhum dado aparecer e nenhum erro é que a [chave de licença e o ID da conta](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/account-linking/) são de contas diferentes. No caso de incompatibilidade, a [extensãoNew Relic Lambda](https://github.com/newrelic/newrelic-lambda-extension) ou [lambda que processa o log de observação da nuvem](/docs/infrastructure/amazon-integrations/connect/aws-metric-stream/) relata os dados com êxito, mas os descarta silenciosamente, pois o ID da conta não corresponde. Isso não resulta em erros ou avisos. Para resolver esse problema, certifique-se de que a chave de licença e o ID da conta sejam da mesma conta. O uso da [CLI Lambda daNew Relic ](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/account-linking/#rec)para habilitar o monitoramento Serverless é recomendado para minimizar esses tipos de problemas. Você pode atualizar a chave de licença no AWS Secrets Manager. Para o ID da conta e configuração que não usa o AWS Secrets Manager, você pode atualizar as [variáveis de ambiente](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/account-linking/#env-var) com a chave de licença ou ID da conta correta para corrigir o problema. + +### Verificar variáveis de ambiente [#check-env-vars] + +Certifique-se de que as [variáveis de ambiente](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) necessárias estejam configuradas corretamente em sua função Lambda da AWS. Isso inclui `NEW_RELIC_APM_LAMBDA_MODE`, `NEW_RELIC_ACCOUNT_ID`, `NEW_RELIC_LICENSE_KEY` e quaisquer outras variáveis relevantes. Se essas variáveis não estiverem definidas ou estiverem incorretas, isso pode impedir o envio de dados para o New Relic. Para obter mais informações, consulte as [variáveis de ambiente](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda). + +### Verifique a tag no Console de Gerenciamento AWS [#check-tags] + +Certifique-se de ter adicionado a tag `NR.Apm.Lambda.Mode: true` à sua função Lambda no Console de Gerenciamento AWS. Essa tag é essencial para habilitar o monitoramento e garantir que os dados sejam enviados para o New Relic. \ No newline at end of file