From 648372cc39604b2ed6d575abafcb5bd1b68075d9 Mon Sep 17 00:00:00 2001 From: svc-docs-eng-opensource-bot Date: Sat, 11 Jan 2025 12:04:00 +0000 Subject: [PATCH 1/2] chore: add translations --- .../content/es/docs/logs/ui-data/parsing.mdx | 141 ++ .../mobile-sdk/test-crash-reporting.mdx | 60 + .../diagnostics-beginner-guide.mdx | 62 +- ...tibility-requirement-lambda-monitoring.mdx | 2 - .../containerized-images.mdx | 6 +- .../env-variables-lambda.mdx | 24 +- ...atibility-requirement-azure-monitoring.mdx | 54 + .../env-variables-azure.mdx | 221 +++ .../install-serverless-azure-monitoring.mdx | 242 ++++ .../introduction-azure-monitoring.mdx | 20 + .../overview.mdx | 8 +- .../service-level-management/create-slm.mdx | 33 +- .../temporal-cloud-integration.mdx | 349 ++--- .../mobile-sdk/test-crash-reporting.mdx | 60 + .../diagnostics-beginner-guide.mdx | 62 +- ...tibility-requirement-lambda-monitoring.mdx | 2 - .../containerized-images.mdx | 6 +- .../env-variables-lambda.mdx | 24 +- ...atibility-requirement-azure-monitoring.mdx | 54 + .../env-variables-azure.mdx | 221 +++ .../install-serverless-azure-monitoring.mdx | 242 ++++ .../introduction-azure-monitoring.mdx | 20 + .../overview.mdx | 8 +- .../service-level-management/create-slm.mdx | 33 +- ...ompatibility-requirements-nodejs-agent.mdx | 1188 ++++++++++++++++- .../temporal-cloud-integration.mdx | 349 ++--- .../mobile-sdk/test-crash-reporting.mdx | 60 + .../diagnostics-beginner-guide.mdx | 62 +- ...tibility-requirement-lambda-monitoring.mdx | 2 - .../containerized-images.mdx | 6 +- .../env-variables-lambda.mdx | 24 +- ...atibility-requirement-azure-monitoring.mdx | 54 + .../env-variables-azure.mdx | 221 +++ .../install-serverless-azure-monitoring.mdx | 242 ++++ .../introduction-azure-monitoring.mdx | 20 + .../overview.mdx | 8 +- .../service-level-management/create-slm.mdx | 33 +- ...ompatibility-requirements-nodejs-agent.mdx | 1188 ++++++++++++++++- .../temporal-cloud-integration.mdx | 349 ++--- .../content/pt/docs/logs/ui-data/parsing.mdx | 141 ++ .../mobile-sdk/test-crash-reporting.mdx | 60 + .../diagnostics-beginner-guide.mdx | 62 +- ...tibility-requirement-lambda-monitoring.mdx | 2 - .../containerized-images.mdx | 6 +- .../env-variables-lambda.mdx | 24 +- ...atibility-requirement-azure-monitoring.mdx | 54 + .../env-variables-azure.mdx | 221 +++ .../install-serverless-azure-monitoring.mdx | 242 ++++ .../introduction-azure-monitoring.mdx | 20 + .../overview.mdx | 8 +- .../service-level-management/create-slm.mdx | 33 +- 51 files changed, 5746 insertions(+), 887 deletions(-) create mode 100644 src/i18n/content/es/docs/serverless-function-monitoring/azure-function-monitoring/compatibility-requirement-azure-monitoring.mdx create mode 100644 src/i18n/content/es/docs/serverless-function-monitoring/azure-function-monitoring/env-variables-azure.mdx create mode 100644 src/i18n/content/es/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx create mode 100644 src/i18n/content/es/docs/serverless-function-monitoring/azure-function-monitoring/introduction-azure-monitoring.mdx create mode 100644 src/i18n/content/jp/docs/serverless-function-monitoring/azure-function-monitoring/compatibility-requirement-azure-monitoring.mdx create mode 100644 src/i18n/content/jp/docs/serverless-function-monitoring/azure-function-monitoring/env-variables-azure.mdx create mode 100644 src/i18n/content/jp/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx create mode 100644 src/i18n/content/jp/docs/serverless-function-monitoring/azure-function-monitoring/introduction-azure-monitoring.mdx create mode 100644 src/i18n/content/kr/docs/serverless-function-monitoring/azure-function-monitoring/compatibility-requirement-azure-monitoring.mdx create mode 100644 src/i18n/content/kr/docs/serverless-function-monitoring/azure-function-monitoring/env-variables-azure.mdx create mode 100644 src/i18n/content/kr/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx create mode 100644 src/i18n/content/kr/docs/serverless-function-monitoring/azure-function-monitoring/introduction-azure-monitoring.mdx create mode 100644 src/i18n/content/pt/docs/serverless-function-monitoring/azure-function-monitoring/compatibility-requirement-azure-monitoring.mdx create mode 100644 src/i18n/content/pt/docs/serverless-function-monitoring/azure-function-monitoring/env-variables-azure.mdx create mode 100644 src/i18n/content/pt/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx create mode 100644 src/i18n/content/pt/docs/serverless-function-monitoring/azure-function-monitoring/introduction-azure-monitoring.mdx diff --git a/src/i18n/content/es/docs/logs/ui-data/parsing.mdx b/src/i18n/content/es/docs/logs/ui-data/parsing.mdx index 4807caa8853..ac604b4360e 100644 --- a/src/i18n/content/es/docs/logs/ui-data/parsing.mdx +++ b/src/i18n/content/es/docs/logs/ui-data/parsing.mdx @@ -306,6 +306,16 @@ Tenga en cuenta que los nombres de las variables deben establecerse explícitame Ubicación geográfica a partir de direcciones IP. Consulte [Geolocalización de direcciones IP (GeoIP)](#geo) para obtener más información. + + + + `key value pairs` + + + + valor principal Par . Consulte [Análisis de pares de valores principales](#parsing-key-value-pairs) para obtener más información. + + @@ -490,6 +500,137 @@ Tenga en cuenta que los nombres de las variables deben establecerse explícitame * **region**: Abreviatura de estado, provincia o territorio * **regionName**: Nombre del estado, provincia o territorio + + + La canalización de logs de New Relic analiza su mensaje de log de manera predeterminada, pero a veces tiene mensajes de log que están formateados como pares principales de valores. En esta situación, es posible que desees poder analizarlos y luego filtrarlos empleando el atributo valor principal. + + Si ese es el caso, puedes usar el [tipo grok](#grok-syntax) `key value pairs` , que analizará los pares principales de valor capturados por el patrón grok. Este formato se basa en tres partes principales: la sintaxis de grok, el prefijo que desea asignar al atributo valor principal analizado y el [tipo de grok](#grok-syntax) `key value pairs` . Al emplear el [tipo grok](#grok-syntax) `key value pairs` , puede extraer y analizar pares principales de valor de logs que no tienen el formato correcto; por ejemplo, si sus logs tienen como prefijo una cadena de fecha y hora: + + ```json + 2015-05-13T23:39:43.945958Z key1=value1,key2=value2,key3=value3 + ``` + + Para extraer y analizar los datos principales de valor de este formato de log, cree la siguiente expresión de Grok: + + ``` + %{TIMESTAMP_ISO8601:containerTimestamp} %{GREEDYDATA:my_attribute_prefix:keyvalue()} + ``` + + El log resultante es: + + ``` + containerTimestamp: "2015-05-13T23:39:43.945958Z" + my_attribute_prefix.key1: "value1" + my_attribute_prefix.key2: "value2" + my_attribute_prefix.key3: "value3" + ``` + + También puede definir el delimitador y separador personalizados para extraer los pares principales de valores requeridos. + + ```json + 2015-05-13T23:39:43.945958Z event:TestRequest request:bar + ``` + + Por ejemplo, con la siguiente expresión de Grok: + + ``` + %{TIMESTAMP_ISO8601:containerTimestamp} %{GREEDYDATA:my_attribute_prefix:keyvalue({"delimiter": " ", "keyValueSeparator": ":"})} + ``` + + El log resultante es: + + ``` + containerTimestamp: "2015-05-13T23:39:43.945958Z" + my_attribute_prefix.event: "TestRequest" + my_attribute_prefix.request: "bar" + ``` + + Si desea omitir el prefijo `my_attribute_prefix` , puede incluir el `"noPrefix": true` en la configuración. + + ``` + %{TIMESTAMP_ISO8601:containerTimestamp} %{GREEDYDATA:my_attribute_prefix:keyValue({"noPrefix": true})} + ``` + + El log resultante es: + + ``` + containerTimestamp: "2015-05-13T23:39:43.945958Z" + event: "TestRequest" + request: "bar" + ``` + + Si desea configurar su prefijo de carácter de comillas personalizado, puede incluir "quoteChar": en la configuración. + + ```json + 2015-05-13T23:39:43.945958Z nbn_demo='INFO',message='This message contains information with spaces ,sessionId='abc123' + ``` + + ``` + %{TIMESTAMP_ISO8601:containerTimestamp} %{GREEDYDATA:my_attribute_prefix:keyValue({"quoteChar": "'"})} + ``` + + El log resultante es: + + ``` + "my_attribute_prefix.message": "'This message contains information with spaces", + "my_attribute_prefix.nbn_demo": "INFO", + "my_attribute_prefix.sessionId": "abc123" + ``` + + ### Parrilla con patrón Grok + + Puede personalizar el comportamiento de análisis con las siguientes opciones para adaptarlo a sus formatos de log: + + * **delimitador** + + * **Descripción:** Cadena que separa cada par principal de valores. + + * **Valor predeterminado:** `,` (coma) + + * **Anular:** establezca el campo `delimiter` para cambiar este comportamiento. + + * **separador de valor-clave** + + * **Descripción:** Cadena empleada para asignar valores a las claves. + * **Valor predeterminado:** `=` + * **Anulación:** establezca el campo `keyValueSeparator` para el uso del separador personalizado. + + * **Cita Char** + + * **Descripción:** Carácter empleado para encerrar valores con espacios o caracteres especiales. + * **Valor predeterminado:** `"` (comillas dobles) + * **Anulación:** define un carácter personalizado empleando `quoteChar`. + + * **soltarOriginal** + + * **Descripción:** Elimina el mensaje de log original luego del análisis. Útil para reducir el almacenamiento de logs. + * **Valor predeterminado:** `true` + * **Anulación:** Establezca `dropOriginal` en `false` para conservar el mensaje de log original. + + * **Sin prefijo** + + * **Descripción:** Cuando `true`, excluye el nombre del campo Grok como prefijo en el objeto resultante. + * **Valor predeterminado:** `false` + * **Anulación:** habilítelo estableciendo `noPrefix` en `true`. + + * **escapeChar** + + * **Descripción:** Define un carácter de escape personalizado para manejar caracteres de log especiales. + * **Valor predeterminado:** "" (barra invertida) + * **Anular:** Personalizar con `escapeChar`. + + * **valores de recorte** + + * **Descripción:** Permite recortar valores que contienen espacios en blanco. + * **Valor predeterminado:** `false` + * **Anulación:** Establezca `trimValues` en `true` para activar el recorte. + + * **Teclas de ajuste** + + * **Descripción:** Permite recortar teclas que contienen espacios en blanco. + * **Valor predeterminado:** `true` + * **Anulación:** Establezca `trimKeys` en `true` para activar el recorte. + ## Organizar por tipo de registro [#type] diff --git a/src/i18n/content/es/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/test-crash-reporting.mdx b/src/i18n/content/es/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/test-crash-reporting.mdx index 88c7703ae12..cf15efbab81 100644 --- a/src/i18n/content/es/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/test-crash-reporting.mdx +++ b/src/i18n/content/es/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/test-crash-reporting.mdx @@ -37,6 +37,10 @@ translationType: machine React Native + + Flutter + + Unidad @@ -250,6 +254,62 @@ translationType: machine ``` + + ## Sintaxis [#syntax] + + ```dart + crashNow({String name}) : void ; + ``` + + ## Descripción [#description] + + Lanza una excepción de tiempo de ejecución de demostración en Android/iOS para probar los informes de fallas de New Relic. + + ## Parámetros [#parameters] + + + + + + + + + + + + + + + + + + + + + +
+ Parámetro + + Tipo + + Descripción +
+ `name` + + `string` + + Opcional. Un mensaje adjunto a la excepción. +
+ + ## Ejemplo [#example] + + ```dart + NewrelicMobile.instance.crashNow(name: "This is a crash"); + NewrelicMobile.instance.crashNow(); + + ``` + + ## Sintaxis [#syntax] diff --git a/src/i18n/content/es/docs/new-relic-solutions/observability-maturity/uptime-performance-reliability/diagnostics-beginner-guide.mdx b/src/i18n/content/es/docs/new-relic-solutions/observability-maturity/uptime-performance-reliability/diagnostics-beginner-guide.mdx index dbf303af14c..81975e6d1ce 100644 --- a/src/i18n/content/es/docs/new-relic-solutions/observability-maturity/uptime-performance-reliability/diagnostics-beginner-guide.mdx +++ b/src/i18n/content/es/docs/new-relic-solutions/observability-maturity/uptime-performance-reliability/diagnostics-beginner-guide.mdx @@ -251,7 +251,67 @@ Las fuentes de los problemas están ordenadas según su frecuencia, siendo las m Esta tabla es una matriz de problemas ordenada por puntos de datos de salud: -| Punto de datos | Capacidad de New Relic | Fuentes de problemas comunes | | ---------- | --------------------- | ----------------------------------------------------------------------------------------------------------------------- | | Salida | APM, infraestructura, logs, NPM | aplicación, fuentes de datos, cambio de configuración de hardware, infraestructura, red interna, proveedor externo (AWS, GCP) | | Entrada | Sintético, logs | Enrutamiento externo (CDN, puertas de enlace, etc.), enrutamiento interno, cosas en el Internet (ISP, etc.) | | Cliente | navegador, móvil | código de navegador o móvil | + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Punto de datos + + New Relic + + Fuentes de problemas comunes +
+ Producción + + APM, infraestructura, log, NPM + + Aplicación, fuentes de datos, cambio de configuración de hardware, infraestructura, redes internas, proveedor externo (AWS, GCP) +
+ Aporte + + Sintético, log + + Enrutamiento externo (CDN, gateways, etc.), enrutamiento interno, cosas en Internet (ISP, etc.) +
+ Cliente + + Browser, móvil + + Código browser o móvil +
Los problemas tienden a agravarse, pero el objetivo es "encontrar la fuente" y luego determinar "qué cambió" para restaurar rápidamente el nivel de servicio. 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 f72e4d513ed..3237a97338b 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 @@ -17,8 +17,6 @@ Antes de habilitar el monitoreo sin servidor usando nuestra capa Lambda, necesit 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. -/\* Luego deberá completar lo siguiente: 1. Instalar \[AWS CLI v2]\(https://docs.aws.amazon.com/cli/latest/userguide/install-cliv2.html) configurar usando \`AWS configure\`. Necesitará una ID de clave de acceso de AWS y una clave de acceso secreta de AWS. 2. Instale \[Python]\(https://www.python.org/downloads/) versión 3.3 o superior. 3. Instale la \[CLI\`newrelic-lambda\`]\(https://github.com/newrelic/newrelic-lambda-cli#installation). Para instalarlo, ejecute este comando: \`\`\`bash pip3 install newrelic-lambda-cli \`\`\` 4. De forma predeterminada, empleamos la política gestionada de AWS \`ReadOnlyAccess\`. Esto permite que la integración de infraestructura vea todos los recursos de su cuenta, en lugar de solo su función Lambda y las métricas de CloudWatch. New Relic recomienda este valor predeterminado, pero entendemos que algunas organizaciones prefieren una postura de seguridad estricta para la integración de terceros. Si desea limitar el acceso de New Relic, se puede otorgar el rol de IAM con un mínimo de estas licencias: \`\`\`yaml Recurso: "\*" Acción: - "cloudwatch:GetMetricStatistics" - "cloudwatch:ListMetrics" - "cloudwatch:GetMetricData" - "lambda:GetAccountSettings" - "lambda:ListFunctions" - "lambda:ListAliases" - "lambda:ListTags" - "lambda:ListEventSourceMappings" \`\`\` 5. Antes de ejecutar la CLI, deberá otorgarle a New Relic un mínimo de estas licencias en AWS: \`\`\`json \{ "Version": "2012-10-17", "Statement": \[ \{ "Sid": "CLIAccessPolicy", "Action": \[ "cloudformation:CreateChangeSet", "cloudformation:CreateStack", "cloudformation:DescribeStacks", "cloudformation:ExecuteChangeSet", "iam:AttachRolePolicy", "iam:CreateRole", "iam:GetRole", "iam:PassRole", "lambda:AddPermission", "lambda:CreateFunction", "lambda:GetFunction", "logs:DeleteSubscriptionFilter", "logs:DescribeSubscriptionFilters", "logs:PutSubscriptionFilter", "s3:GetObject", "serverlessrepo:CreateCloudFormationChangeSet", "secretsmanager:CreateSecret" ], "Efecto": "Permitir", "Recurso": "\*" }, \{ "Sid": "NRLogAccessPolicy", "Efecto": "Permitir", "Acción": \[ "serverlessrepo:CreateCloudFormationTemplate", "serverlessrepo:GetCloudFormationTemplate" ], "Recurso": "arn:AWS:serverlessrepo:us-east-1:463657938898:aplicación/NewRelic-log-ingestion" } ] } \`\`\` Si desea obtener más información sobre nuestra CLI, consulte \[nuestro repositorio de CLI]\(https://github.com/newrelic/newrelic-lambda-cli#installation). \*/ - ## Tiempos de ejecución admitidos Según el tipo de instrumentación, se admiten los siguientes tiempos de ejecución. 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 e4f27f08415..54a32dcb845 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 @@ -193,12 +193,12 @@ Aquí hay una guía para agregar nuestra capa prediseñada a su código. ### Configure su función Lambda - 2. Configure la función Lambda con la misma configuración que su función original, pero cerciorar de agregar las variables de entorno necesarias para el monitoreo de New Relic Lambda. Consulte nuestras [variables de entorno](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/configure-serverless-monitoring-aws-lambda/#environment) para obtener más información. + 2. Configure la función Lambda con la misma configuración que su función original, pero cerciorar de agregar todas las variables de entorno necesarias para el monitoreo Lambda de New Relic. Consulte nuestras [variables de entorno](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) para obtener más información. 3. Actualice el controlador de su función para que apunte a la capa recién anexa en la anulación `cmd` para su función. Puede hacerlo siguiendo las instrucciones de estos dos documentos: - * [Configuración UI de la consola Lambda](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/instrument-your-own/#console) - * [Instrumentación sin capas para monitorización Lambda](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/enable-serverless-monitoring-aws-lambda-layerless) + * [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) 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 f37e614efbc..04a3951db11 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 @@ -149,9 +149,7 @@ En función de su entorno de ejecución, puede configurar las siguientes variabl - Deshabilite el rastreo distribuido configurando esto en - - `false` + Generar traza habilitando rastreo distribución @@ -349,9 +347,7 @@ En función de su entorno de ejecución, puede configurar las siguientes variabl - Deshabilite el rastreo distribuido configurando esto en - - `false` + Generar traza habilitando rastreo distribución @@ -543,9 +539,7 @@ En función de su entorno de ejecución, puede configurar las siguientes variabl - Deshabilite el rastreo distribuido configurando esto en - - `false` + Generar traza habilitando rastreo distribución @@ -631,9 +625,7 @@ En función de su entorno de ejecución, puede configurar las siguientes variabl - Deshabilite el rastreo distribuido configurando esto en - - `false` + Generar traza habilitando rastreo distribución @@ -681,9 +673,7 @@ En función de su entorno de ejecución, puede configurar las siguientes variabl - Deshabilite el rastreo distribuido configurando esto en - - `false` + Generar traza habilitando rastreo distribución @@ -823,9 +813,7 @@ En función de su entorno de ejecución, puede configurar las siguientes variabl - Deshabilite el rastreo distribuido configurando esto en - - `false` + Generar traza habilitando rastreo distribución diff --git a/src/i18n/content/es/docs/serverless-function-monitoring/azure-function-monitoring/compatibility-requirement-azure-monitoring.mdx b/src/i18n/content/es/docs/serverless-function-monitoring/azure-function-monitoring/compatibility-requirement-azure-monitoring.mdx new file mode 100644 index 00000000000..04ddd556dc2 --- /dev/null +++ b/src/i18n/content/es/docs/serverless-function-monitoring/azure-function-monitoring/compatibility-requirement-azure-monitoring.mdx @@ -0,0 +1,54 @@ +--- +title: Compatibilidad y requisitos para funciones Azure instrumentadas +metaDescription: Azure function monitoring agent compatibility and requirements. +freshnessValidatedDate: never +translationType: machine +--- + +Antes de [instrumentar Azure Functions](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/configure-serverless-aws-monitoring), cerciorar de que su sistema cumpla con los siguientes requisitos. + +## Requerimientos básicos [#requirements] + +* Azure Functions alojadas en [un plan de consumo](https://learn.microsoft.com/en-us/azure/azure-functions/consumption-plan) o [un plan dedicado](https://learn.microsoft.com/en-us/azure/azure-functions/dedicated-plan). + +* Debe tener el [licencia requerida para acceder al servicio kudu](https://learn.microsoft.com/en-us/azure/app-service/resources-kudu#access-kudu-for-your-app). + +* Una cuenta de New Relic con un [rol de administrador](/docs/accounts/original-accounts-billing/original-users-roles/users-roles-original-user-model/#roles) o de [administrador de infraestructura](/docs/accounts/original-accounts-billing/original-users-roles/users-roles-original-user-model#add-on). + +* Un . + +* Agente .NET versión 10.30 o superior. + + + El rastreo distribuido de extremo a extremo solo se admite para solicitudes HTTP. Además, siguen disponibles las trazas para llamadas a servicios externos, como base de datos y Service Bus. + + +## Tiempos de ejecución admitidos + +Según su entorno de alojamiento, se admiten los siguientes tiempos de ejecución. + + + + Funciones en contenedores de Linux y Windows + + + + + * .NET: `dotnet6.0`, `dotnet8.0` + + + + * .NET: `dotnet6.0`, `dotnet8.0` + + + + * .NET: `dotnet6.0`, `dotnet8.0` + + + + +## Que sigue + + + Comience a emplear la instrumentación y configuración de Azure Functions + \ No newline at end of file diff --git a/src/i18n/content/es/docs/serverless-function-monitoring/azure-function-monitoring/env-variables-azure.mdx b/src/i18n/content/es/docs/serverless-function-monitoring/azure-function-monitoring/env-variables-azure.mdx new file mode 100644 index 00000000000..73bb22f7e5f --- /dev/null +++ b/src/i18n/content/es/docs/serverless-function-monitoring/azure-function-monitoring/env-variables-azure.mdx @@ -0,0 +1,221 @@ +--- +title: Variables de entorno para la monitorización Azure Functions +metaDescription: Configure environment variables to monitor your Azure functions with New Relic +freshnessValidatedDate: never +tags: + - AWS Lambda + - Environment Variables + - Configuration + - Secrets Management +translationType: machine +--- + +Las variables de entorno son una forma de almacenar configuraciones y secretos fuera de su código. Las siguientes tablas muestran las variables obligatorias y las variables específicas del tiempo de ejecución que puede configurar para monitorear sus Azure Functions con New Relic. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Variable ambiental + + Valor por defecto + + Opciones + + Descripción +
+ `CORECLR_ENABLE_PROFILING` + + `0` + + `0` + + , + + `1` + + **Requerido** + + . Habilite la creación de perfiles estableciendo esto en + + `1` + + . +
+ `CORECLR_PROFILER` + + + + + + **Requerido** + + . Configure esto para habilitar el agente .NET. +
+ `CORECLR_NEWRELIC_HOME` + + + + + + **Requerido** + + . Configure esto para habilitar el agente .NET. +
+ `CORECLR_PROFILER_PATH` + + + + + + **Requerido** + + . Configure esto para habilitar el agente .NET. +
+ `NEW_RELIC_DISTRIBUTED_TRACING_ENABLED` + + `true` + + `true` + + , + + `false` + + Generar traza habilitando rastreo distribución. +
+ `NEW_RELIC_APP_NAME` + + + + + + Establece el nombre de la aplicación, aunque no se emplee en la UI de New Relic. +
+ `NEW_RELIC_AZURE_FUNCTION_MODE_ENABLED` + + `1` + + `1` + + , + + `0` + + Deshabilite el modo Azure Functions estableciendo el valor en + + `0` + + . +
+ `NEW_RELIC_LOG_DIRECTORY` + + + + + + Modifique la ubicación donde desea almacenar los logs del agente y del generador de perfiles. +
+ `NEW_RELIC_LOG_LEVEL` + + `info` + + `info` + + , + + `debug` + + , + + `finest` + + Establecer el nivel de agente de logs. +
+ +## Que sigue + + + Comience a emplear la instrumentación y configuración de Azure Functions + \ No newline at end of file diff --git a/src/i18n/content/es/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx b/src/i18n/content/es/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx new file mode 100644 index 00000000000..de2f5935e33 --- /dev/null +++ b/src/i18n/content/es/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx @@ -0,0 +1,242 @@ +--- +title: Instalar y configurar la supervisión Azure Functions en New Relic +metaDescription: Configure your Azure Functions with New Relic +freshnessValidatedDate: never +translationType: machine +--- + +## Antes de que empieces [#begin] + +Cerciorar de que sus Azure Functions cumplan con nuestros [requisitos y compatibilidad](/docs/serverless-function-monitoring/azure-function-monitoring/compatibility-requirement-azure-monitoring). + + + + ## Vincula tu cuenta de Azure a New Relic + + Puede vincular su cuenta Azure a New Relic configurando el sondeo de monitoreo métrico de Azure . Esto le permite ver la métrica en la UI de New Relic. Para obtener más información, consulte [IntegraciónAzure ](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-functions-monitoring-integration/#polling). + + + + ## Instrumente sus Azure Functions con el agente New Relic .NET + + Según sus necesidades, seleccione una de las siguientes opciones para instrumentar sus Azure Functions con el agente New Relic .NET. + + + + Funciones en contenedores de Linux y Windows + + + + + 1. Agregue el paquete NuGet `NewRelic.Agent` a su proyecto de aplicación. + + * En el editor de código de Visual Studio, use el administrador de paquetes de NuGet para buscar y agregar la última versión de `NewRelic.Agent` a su aplicación. + * Si está empleando otros entornos de desarrollo, puede agregar el paquete con `dotnet add packages NewRelic.Agent`. + + 2. Emplee su mecanismo de publicación preferido para implementar su aplicación actualizada en Azure. Esto incluye el agente New Relic, que está instalado en la carpeta `/home/site/www/newrelic` . + + + + Vaya a la página de servicio de Kudu y haga lo siguiente: + + 1. En el portal de Azure, navegue hasta su aplicación de función. + 2. Haga clic en la sección **Development tools** y seleccione **Advanced Tools > Go**. + 3. Para ver las extensiones de sitio disponibles, haga clic en la pestaña **Site extensions** . + 4. Para instalar la extensión, busque `New Relic .NET Agent` y haga clic en **+**. + + + + Para instalar el agente New Relic .NET, en la etapa final de su Dockerfile, agregue las siguientes líneas: + + ```dockerfile + # install the latest New Relic .NET agent using the apt-get package manager + RUN apt-get update && apt-get install -y wget ca-certificates gnupg \ + && echo 'deb http://apt.newrelic.com/debian/ newrelic non-free' | tee /etc/apt/sources.list.d/newrelic.list \ + && wget https://download.newrelic.com/548C16BF.gpg \ + && apt-key add 548C16BF.gpg \ + && apt-get update \ + && apt-get install -y newrelic-dotnet-agent \ + && rm -rf /var/lib/apt/lists/* + + ``` + + + + + + + ## Configurar las variables de entorno + + Luego de instrumentar sus Azure Functions con el agente New Relic .NET, haga lo siguiente para configurar las [variables de entorno](/docs/serverless-function-monitoring/azure-function-monitoring/env-variables-azure) para enviar los datos a New Relic. + + 1. Vaya a sus Azure Functions en el portal Azure , en **Settings**, haga clic en **Environment variables** y luego en **Advanced edit**. + + 2. Según los requisitos de su aplicación, pegue los siguientes valores. + + + Cerciorar de agregar una coma al final de la última línea existente y actualice su clave de licencia y el nombre de la aplicación en la siguiente configuración. + + + + + Funciones en contenedores de Linux y Windows + + + + + ```json + { + "name": "CORECLR_ENABLE_PROFILING", + "value": "1", + "slotSetting": false + }, + { + "name": "CORECLR_NEWRELIC_HOME", + "value": "/home/site/wwwroot/newrelic", + "slotSetting": false + }, + { + "name": "CORECLR_PROFILER", + "value": "{36032161-FFC0-4B61-B559-F6C5D41BAE5A}", + "slotSetting": false + }, + { + "name": "CORECLR_PROFILER_PATH", + "value": "/home/site/wwwroot/newrelic/libNewRelicProfiler.so", + "slotSetting": false + }, + { + "name": "NEW_RELIC_AZURE_FUNCTION_MODE_ENABLED", + "value": "1", + "slotSetting": false + }, + { + "name": "NEW_RELIC_LICENSE_KEY", + "value": "", + "slotSetting": false + }, + { + "name": "NEWRELIC_LOG_DIRECTORY", + "value": "/home/LogFiles/NewRelic", + "slotSetting": false + }, + { + "name": "NEWRELIC_LOG_LEVEL", + "value": "info", + "slotSetting": false + }, + + + ``` + + + + ```json + { + "name": "CORECLR_PROFILER_PATH", + "value": "C:\\home\\NewRelicAgent\\Core\\NewRelic.Profiler.dll", + "slotSetting": false + }, + { + "name": "CORECLR_NEWRELIC_HOME", + "value": "C:\\home\\NewRelicAgent\\Core", + "slotSetting": false + }, + { + "name": "NEWRELIC_LOG_DIRECTORY", + "value": "C:\\home\\LogFiles\\NewRelic", + "slotSetting": false + }, + { + "name": "NEW_RELIC_AZURE_FUNCTION_MODE_ENABLED", + "value": "1", + "slotSetting": false + }, + { + "name": "CORECLR_ENABLE_PROFILING", + "value": "1", + "slotSetting": false + }, + { + "name": "CORECLR_PROFILER", + "value": "{36032161-FFC0-4B61-B559-F6C5D41BAE5A}", + "slotSetting": false + }, + { + "name": "NEW_RELIC_LICENSE_KEY", + "value": "", + "slotSetting": false + }, + { + "name": "NEWRELIC_LOG_LEVEL", + "value": "info", + "slotSetting": false + }, + { + "name": "NEW_RELIC_APP_NAME", + "value": "", + "slotSetting": false + }, + + ``` + + + + ```json + { + "name": "CORECLR_ENABLE_PROFILING", + "value": "1", + "slotSetting": false + }, + { + "name": "CORECLR_NEWRELIC_HOME", + "value": "/usr/local/newrelic-dotnet-agent", + "slotSetting": false + }, + { + "name": "CORECLR_PROFILER", + "value": "{36032161-FFC0-4B61-B559-F6C5D41BAE5A}", + "slotSetting": false + }, + { + "name": "CORECLR_PROFILER_PATH", + "value": "/usr/local/newrelic-dotnet-agent/libNewRelicProfiler.so", + "slotSetting": false + }, + { + "name": "NEW_RELIC_AZURE_FUNCTION_MODE_ENABLED", + "value": "1", + "slotSetting": false + }, + { + "name": "NEW_RELIC_LICENSE_KEY", + "value": "", + "slotSetting": false + }, + { + "name": "NEWRELIC_LOG_DIRECTORY", + "value": "/home/LogFiles/NewRelic", + "slotSetting": false + }, + { + "name": "NEWRELIC_LOG_LEVEL", + "value": "info", + "slotSetting": false + }, + + ``` + + + + + + + ## Resetear tus Azure Functions + + Luego de agregar las variables de entorno, resetear Azure Functions para aplicar los cambios. + + + +## Que sigue + +Luego de completar los pasos de instalación y configuración, envíe tráfico a sus Azure Functions para ver la métrica en el de New Relic.UI dashboard \ No newline at end of file diff --git a/src/i18n/content/es/docs/serverless-function-monitoring/azure-function-monitoring/introduction-azure-monitoring.mdx b/src/i18n/content/es/docs/serverless-function-monitoring/azure-function-monitoring/introduction-azure-monitoring.mdx new file mode 100644 index 00000000000..0e1aab116b4 --- /dev/null +++ b/src/i18n/content/es/docs/serverless-function-monitoring/azure-function-monitoring/introduction-azure-monitoring.mdx @@ -0,0 +1,20 @@ +--- +title: Introducción a la monitorización Azure Functions +metaDescription: This provides an overview of New Relic's AWS Lambda monitoring and details how to link your accounts. +freshnessValidatedDate: never +translationType: machine +--- + +La instrumentación de New Relic para Azure Functions 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, ver el rastreo distribuido y registrar detalles sobre el evento de origen y las respuestas de su función. + + + Para Azure Functions, el agente informa datos como el rastreo distribuido y los logs, que están disponibles en 'Servicios - APM' como una entidad APM . Sin embargo, todavía existe una entidad separada (proporcionada por monitoreo de infraestructura) para Azure Functions . + + +new-relic-azure-function-monitoring.gif + +## Que sigue + + + Obtenga más información sobre los tiempos de ejecución y requisitos previos admitidos Comience con la instrumentación y configuración para sus Azure Functions + \ No newline at end of file diff --git a/src/i18n/content/es/docs/serverless-function-monitoring/overview.mdx b/src/i18n/content/es/docs/serverless-function-monitoring/overview.mdx index d7124cdcb96..bc73bed50d4 100644 --- a/src/i18n/content/es/docs/serverless-function-monitoring/overview.mdx +++ b/src/i18n/content/es/docs/serverless-function-monitoring/overview.mdx @@ -1,12 +1,12 @@ --- -title: Función de monitoreo sin servidor +title: Monitoreo sin servidor freshnessValidatedDate: never translationType: machine --- -Las funciones sin servidor son una forma de ejecutar código en la nube sin preocupar por gestionar servidores. En lugar de configurar y mantener servidores, el proveedor de la nube se encarga de todo por usted. Esto significa que los desarrolladores pueden centrar en escribir código que responda a eventos específicos, como cuando un usuario hace clic en un botón, sin ocupar de los detalles técnicos de la gestión del servidor. Al aprovechar las capacidades de monitoreo sin servidor de New Relic, las organizaciones pueden mejorar su eficiencia operativa, mejorar el rendimiento de la aplicación y garantizar una experiencia de usuario perfecta. +Las funciones sin servidor son una forma de ejecutar código en la nube sin preocupar por gestionar servidores. En lugar de configurar y mantener servidores, el proveedor de la nube se encarga de todo por usted. Esto significa que los desarrolladores pueden centrar en escribir código que responda a eventos específicos, como cuando un usuario hace clic en un botón, sin ocupar de los detalles técnicos de la gestión del servidor. Al aprovechar las capacidades de monitoreo sin servidor de New Relic, la organización puede mejorar su eficiencia operativa, mejorar el rendimiento de la aplicación y garantizar una experiencia de usuario perfecta. -A continuación se presentan algunos de los beneficios clave de usar New Relic para la supervisión de funciones sin servidor: +A continuación se presentan algunos de los beneficios clave de usar New Relic para monitorear servidores: * **Monitoreo unificado:** Visualice todas sus funciones sin servidor en un único dashboard, independientemente del proveedor de la nube, simplificando la gestión y el monitoreo de funciones en diferentes entornos. @@ -21,7 +21,7 @@ Seleccione el proveedor de nube que está empleando para obtener más informaci - + \ No newline at end of file diff --git a/src/i18n/content/es/docs/service-level-management/create-slm.mdx b/src/i18n/content/es/docs/service-level-management/create-slm.mdx index 54948cba5bd..9776d83ec71 100644 --- a/src/i18n/content/es/docs/service-level-management/create-slm.mdx +++ b/src/i18n/content/es/docs/service-level-management/create-slm.mdx @@ -129,7 +129,8 @@ Según `Transaction` evento, estos SLI son los más comunes para servicios basad Para seleccionar un valor apropiado para la condición de duración, una práctica típica es seleccionar la duración del percentil 95 de las respuestas de los últimos 7 o 15 días. Encuentre este umbral de duración usando el [generador de consultas](/docs/query-your-data/explore-query-data/query-builder/introduction-query-builder/) y utilícelo para determinar cuál considera que es un buen evento para su SLI: ```sql - SELECT percentile(duration, 95) FROM Transaction WHERE entityGuid = '{entityGuid}' SINCE 7 days ago LIMIT MAX + SELECT percentile(duration, 95) FROM Transaction + WHERE entityGuid = '{entityGuid}' SINCE 7 days ago LIMIT MAX ``` @@ -171,7 +172,8 @@ Según los intervalos de OpenTelemetry, estos SLI son los más comunes para serv ```sql FROM Span - WHERE entity.guid = '{entityGuid}' AND (span.kind IN ('server', 'consumer') OR kind IN ('server', 'consumer')) + WHERE entity.guid = '{entityGuid}' AND (span.kind IN ('server', 'consumer') + OR kind IN ('server', 'consumer')) ``` Donde `{entityGuid}` es el GUID del servicio. @@ -182,7 +184,8 @@ Según los intervalos de OpenTelemetry, estos SLI son los más comunes para serv ```sql FROM Span - WHERE entity.guid = '{entityGuid}' AND (span.kind IN ('server', 'consumer') OR kind IN ('server', 'consumer')) AND otel.status_code = 'ERROR' + WHERE entity.guid = '{entityGuid}' AND (span.kind IN ('server', 'consumer') + OR kind IN ('server', 'consumer')) AND otel.status_code = 'ERROR' ``` Donde `{entityGuid}` es el GUID del servicio. @@ -196,7 +199,9 @@ Según los intervalos de OpenTelemetry, estos SLI son los más comunes para serv Para seleccionar un valor apropiado para la condición de duración, una práctica típica es seleccionar la duración del percentil 95 de las respuestas de los últimos 7 o 15 días. Encuentre este umbral de duración usando el [generador de consultas](/docs/query-your-data/explore-query-data/query-builder/introduction-query-builder/) y utilícelo para determinar cuál considera que es un buen evento para su SLI: ```sql - SELECT percentile(duration.ms, 95) FROM Span WHERE entityGuid = '{entityGuid}' AND (span.kind IN ('server', 'consumer') OR kind IN ('server', 'consumer')) SINCE 7 days ago LIMIT MAX + SELECT percentile(duration.ms, 95) FROM Span + WHERE entityGuid = '{entityGuid}' AND (span.kind IN ('server', 'consumer') + OR kind IN ('server', 'consumer')) SINCE 7 days ago LIMIT MAX ``` @@ -205,7 +210,8 @@ Según los intervalos de OpenTelemetry, estos SLI son los más comunes para serv ```sql FROM Span - WHERE entity.guid = '{entityGuid}' AND (span.kind IN ('server', 'consumer') OR kind IN ('server', 'consumer')) + WHERE entity.guid = '{entityGuid}' AND (span.kind IN ('server', 'consumer') + OR kind IN ('server', 'consumer')) ``` Donde `{entityGuid}` es el GUID del servicio. @@ -216,7 +222,8 @@ Según los intervalos de OpenTelemetry, estos SLI son los más comunes para serv ```sql FROM Span - WHERE entity.guid = '{entityGuid}' AND (span.kind IN ('server', 'consumer') OR kind IN ('server', 'consumer')) AND duration.ms < {duration} + WHERE entity.guid = '{entityGuid}' AND (span.kind IN ('server', 'consumer') + OR kind IN ('server', 'consumer')) AND duration.ms < {duration} ``` * Donde `{entityGuid}` es el GUID del servicio. @@ -407,8 +414,8 @@ Los siguientes SLI se basan en las Métricas web principales del browser de Goog Si desea crear SLI independientes para realizar un seguimiento de CLS en dispositivos móviles y de escritorio por separado, agregue una de estas cláusulas al final del campo: - * `and deviceType = 'Mobile'` - * `and deviceType = 'Desktop'` + * `AND deviceType = 'Mobile'` + * `AND deviceType = 'Desktop'` **Good events fields** @@ -425,14 +432,14 @@ Los siguientes SLI se basan en las Métricas web principales del browser de Goog Si decidió crear SLI independientes para realizar un seguimiento de CLS en dispositivos móviles y de escritorio por separado cuando definió la consulta de evento válida, agregue esta cláusula al final del campo: - * `and deviceType = 'Mobile'` - * `and deviceType = 'Desktop'` + * `AND deviceType = 'Mobile'` + * `AND deviceType = 'Desktop'` Para determinar un número realista para seleccionar `{cumulativeLayoutShift}` en su entorno, una práctica típica es seleccionar el percentil 75 de cargas de página durante los últimos 7 o 15 días, segmentado entre dispositivos móviles y de escritorio. Encuéntrelo usando el generador de consultas: ```sql SELECT percentile(cumulativeLayoutShift, 95) FROM PageViewTiming - WHERE entityGuid = '{entityGuid}' since 7 days ago limit max facet deviceType + WHERE entityGuid = '{entityGuid}' SINCE 7 days ago LIMIT MAX FACET deviceType ``` @@ -562,10 +569,10 @@ Para crear un nivel de servicio, siga estos pasos: ```sql FROM Metric - SELECT getField(`newrelic.goldenmetrics.synth.monitor.medianDurationS`, count) as 'Valid' + SELECT getField(`newrelic.goldenmetrics.synth.monitor.medianDurationS`, count) AS 'Valid' FROM Metric - SELECT getCdfCount(`newrelic.goldenmetrics.synth.monitor.medianDurationS`, 0.5) as 'Good' + SELECT getCdfCount(`newrelic.goldenmetrics.synth.monitor.medianDurationS`, 0.5) AS 'Good' ``` También puedes utilizar comodines en tu consulta SLI, aquí tienes un ejemplo: diff --git a/src/i18n/content/jp/docs/infrastructure/host-integrations/host-integrations-list/temporal-cloud-integration.mdx b/src/i18n/content/jp/docs/infrastructure/host-integrations/host-integrations-list/temporal-cloud-integration.mdx index 22887d2bb09..4c9f654473a 100644 --- a/src/i18n/content/jp/docs/infrastructure/host-integrations/host-integrations-list/temporal-cloud-integration.mdx +++ b/src/i18n/content/jp/docs/infrastructure/host-integrations/host-integrations-list/temporal-cloud-integration.mdx @@ -51,241 +51,120 @@ translationType: machine ```yml integrations: - - name: nri-flex - config: - name: temporalCloudIntegration - apis: - - event_type: temporalCloudFrontendServiceError - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_frontend_service_error_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudFrontendServiceRequest - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_frontend_service_request_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudPollSuccess - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_poll_success_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudPollSuccessSync - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_poll_success_sync_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudPollTimeout - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_poll_timeout_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudResourceExhaustedErrors - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_resource_exhausted_error_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudScheduleActionSuccess - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_schedule_action_success_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudScheduleBufferOverruns - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_schedule_buffer_overruns_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudScheduleMissedCatchupWindow - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_schedule_missed_catchup_window_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudScheduleRateLimited - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_schedule_rate_limited_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudServiceLatencyBucket - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_service_latency_bucket - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudServiceLatencyCount - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_service_latency_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudServiceLatencySum - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_service_latency_sum - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudStateTransition - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_state_transition_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudTotalAction - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_total_action_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudWorkflowCancel - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_workflow_cancel_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudWorkflowContinued - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_workflow_continued_as_new_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudWorkflowFailed - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_workflow_failed_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudWorkflowSuccess - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_workflow_success_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudWorkflowTerminate - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_workflow_terminate_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudWorkflowTimeout - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_workflow_timeout_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem + - name: nri-flex + config: + name: temporalCloudIntegration + global: + base_url: https://.tmprl.cloud/prometheus/api/v1/ + headers: + accept: application/json + tls_config: + enable: true + key: /certs/client.key + cert: /certs/client.pem + interval: 60s + timeout: 55s + apis: + - event_type: temporalCloudFrontendServiceError + # sum(increase(temporal_cloud_v0_frontend_service_error_count[1m])) by (temporal_namespace,operation) + url: query?query=sum%28increase%28temporal_cloud_v0_frontend_service_error_count%5B1m%5D%29%29%20by%20%28temporal_namespace%2Coperation%29 + split_array: true + leaf_array: true + - event_type: temporalCloudFrontendServiceRequest + # sum(increase(temporal_cloud_v0_frontend_service_request_count[1m])) by (temporal_namespace,operation) + url: query?query=sum%28increase%28temporal_cloud_v0_frontend_service_request_count%5B1m%5D%29%29%20by%20%28temporal_namespace%2Coperation%29 + split_array: true + leaf_array: true + - event_type: temporalCloudPollSuccess + # sum(increase(temporal_cloud_v0_poll_success_count[1m])) by (temporal_namespace,operation,task_type) + url: query?query=sum%28increase%28temporal_cloud_v0_poll_success_count%5B1m%5D%29%29%20by%20%28temporal_namespace%2Coperation%2Ctask_type%29 + split_array: true + leaf_array: true + - event_type: temporalCloudPollSuccessSync + # sum(increase(temporal_cloud_v0_poll_success_sync_count[1m])) by (temporal_namespace,operation,task_type) + url: query?query=sum%28increase%28temporal_cloud_v0_poll_success_sync_count%5B1m%5D%29%29%20by%20%28temporal_namespace%2Coperation%2Ctask_type%29 + split_array: true + leaf_array: true + - event_type: temporalCloudPollTimeout + # sum(increase(temporal_cloud_v0_poll_timeout_count[1m])) by (temporal_namespace,operation,task_type) + url: query?query=sum%28increase%28temporal_cloud_v0_poll_timeout_count%5B1m%5D%29%29%20by%20%28temporal_namespace%2Coperation%2Ctask_type%29 + split_array: true + leaf_array: true + - event_type: temporalCloudResourceExhaustedErrors + # sum(increase(temporal_cloud_v0_resource_exhausted_error_count[1m])) by (temporal_namespace,resource_exhausted_cause) + url: query?query=sum%28increase%28temporal_cloud_v0_resource_exhausted_error_count%5B1m%5D%29%29%20by%20%28temporal_namespace%2Cresource_exhausted_cause%29 + split_array: true + leaf_array: true + - event_type: temporalCloudScheduleActionSuccess + # sum(increase(temporal_cloud_v0_schedule_action_success_count[1m])) by (temporal_namespace) + url: query?query=sum%28increase%28temporal_cloud_v0_schedule_action_success_count%5B1m%5D%29%29%20by%20%28temporal_namespace%29 + split_array: true + leaf_array: true + - event_type: temporalCloudScheduleBufferOverruns + # sum(increase(temporal_cloud_v0_schedule_buffer_overruns_count[1m])) by (temporal_namespace) + url: query?query=sum%28increase%28temporal_cloud_v0_schedule_buffer_overruns_count%5B1m%5D%29%29%20by%20%28temporal_namespace%29 + split_array: true + leaf_array: true + - event_type: temporalCloudScheduleMissedCatchupWindow + # sum(increase(temporal_cloud_v0_schedule_missed_catchup_window_count[1m])) by (temporal_namespace) + url: query?query=sum%28increase%28temporal_cloud_v0_schedule_missed_catchup_window_count%5B1m%5D%29%29%20by%20%28temporal_namespace%29 + split_array: true + leaf_array: true + - event_type: temporalCloudScheduleRateLimited + # sum(increase(temporal_cloud_v0_schedule_rate_limited_count[1m])) by (temporal_namespace) + url: query?query=sum%28increase%28temporal_cloud_v0_schedule_rate_limited_count%5B1m%5D%29%29%20by%20%28temporal_namespace%29 + split_array: true + leaf_array: true + - event_type: temporalCloudStateTransition + # sum(increase(temporal_cloud_v0_state_transition_count[1m])) by (temporal_namespace) + url: query?query=sum%28increase%28temporal_cloud_v0_state_transition_count%5B1m%5D%29%29%20by%20%28temporal_namespace%29 + split_array: true + leaf_array: true + - event_type: temporalCloudTotalAction + # sum(increase(temporal_cloud_v0_total_action_count[1m])) by (temporal_namespace, namespace_mode) + url: query?query=sum%28increase%28temporal_cloud_v0_total_action_count%5B1m%5D%29%29%20by%20%28temporal_namespace%2C%20namespace_mode%29 + split_array: true + leaf_array: true + - event_type: temporalCloudWorkflowCancel + # sum(increase(temporal_cloud_v0_workflow_cancel_count[1m])) by (temporal_namespace, operation) + url: query?query=sum%28increase%28temporal_cloud_v0_workflow_cancel_count%5B1m%5D%29%29%20by%20%28temporal_namespace%2C%20operation%29 + split_array: true + leaf_array: true + - event_type: temporalCloudWorkflowContinued + # sum(increase(temporal_cloud_v0_workflow_continued_as_new_count[1m])) by (temporal_namespace, operation) + url: query?query=sum%28increase%28temporal_cloud_v0_workflow_continued_as_new_count%5B1m%5D%29%29%20by%20%28temporal_namespace%2C%20operation%29 + split_array: true + leaf_array: true + - event_type: temporalCloudWorkflowFailed + # sum(increase(temporal_cloud_v0_workflow_failed_count[1m])) by (temporal_namespace, operation) + url: query?query=sum%28increase%28temporal_cloud_v0_workflow_failed_count%5B1m%5D%29%29%20by%20%28temporal_namespace%2C%20operation%29 + split_array: true + leaf_array: true + - event_type: temporalCloudWorkflowSuccess + # sum(increase(temporal_cloud_v0_workflow_success_count[1m])) by (temporal_namespace, operation) + url: query?query=sum%28increase%28temporal_cloud_v0_workflow_success_count%5B1m%5D%29%29%20by%20%28temporal_namespace%2C%20operation%29 + split_array: true + leaf_array: true + - event_type: temporalCloudWorkflowTerminate + # sum(increase(temporal_cloud_v0_workflow_terminate_count[1m])) by (temporal_namespace, operation) + url: query?query=sum%28increase%28temporal_cloud_v0_workflow_terminate_count%5B1m%5D%29%29%20by%20%28temporal_namespace%2C%20operation%29 + split_array: true + leaf_array: true + - event_type: temporalCloudWorkflowTimeout + # sum(increase(temporal_cloud_v0_workflow_timeout_count[1m])) by (temporal_namespace, operation) + url: query?query=sum%28increase%28temporal_cloud_v0_workflow_timeout_count%5B1m%5D%29%29%20by%20%28temporal_namespace%2C%20operation%29 + split_array: true + leaf_array: true + - event_type: temporalCloudWorkflowExecutionLatencySecP95 + # histogram_quantile(0.95, sum(rate(temporal_cloud_v0_service_latency_bucket[1m] offset 1m)) by (temporal_namespace, operation, le)) + url: query?query=histogram_quantile%280.95%2C%20sum%28rate%28temporal_cloud_v0_service_latency_bucket%5B1m%5D%20offset%201m%29%29%20by%20%28temporal_namespace%2C%20operation%2C%20le%29%29 + split_array: true + leaf_array: true + - event_type: temporalCloudReplicationLagSecP95 + # histogram_quantile(0.95, sum(rate(temporal_cloud_v0_replication_lag_bucket[1m] offset 1m)) by (temporal_namespace, le)) + url: query?query=histogram_quantile%280.95%2C%20sum%28rate%28temporal_cloud_v0_replication_lag_bucket%5B1m%5D%20offset%201m%29%29%20by%20%28temporal_namespace%2C%20le%29%29 + split_array: true + leaf_array: true ``` 3. 以下の手順[に従って、インフラストラクチャ エージェントを再起動してください。](/docs/infrastructure/install-infrastructure-agent/manage-your-agent/start-stop-restart-infrastructure-agent/) diff --git a/src/i18n/content/jp/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/test-crash-reporting.mdx b/src/i18n/content/jp/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/test-crash-reporting.mdx index 208d067f659..094df004419 100644 --- a/src/i18n/content/jp/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/test-crash-reporting.mdx +++ b/src/i18n/content/jp/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/test-crash-reporting.mdx @@ -37,6 +37,10 @@ translationType: machine リアクトネイティブ + + フラッター + + Unity @@ -250,6 +254,62 @@ translationType: machine ``` + + ## 構文 [#syntax] + + ```dart + crashNow({String name}) : void ; + ``` + + ## 説明 [#description] + + Android/iOS でデモのランタイム例外をスローして、New Relic のクラッシュ レポートをテストします。 + + ## パラメーター [#parameters] + + + + + + + + + + + + + + + + + + + + + +
+ パラメータ + + タイプ + + 説明 +
+ `name` + + `string` + + オプションです。例外に添付されるメッセージ。 +
+ + ## 例 [#example] + + ```dart + NewrelicMobile.instance.crashNow(name: "This is a crash"); + NewrelicMobile.instance.crashNow(); + + ``` + + ## 構文 [#syntax] diff --git a/src/i18n/content/jp/docs/new-relic-solutions/observability-maturity/uptime-performance-reliability/diagnostics-beginner-guide.mdx b/src/i18n/content/jp/docs/new-relic-solutions/observability-maturity/uptime-performance-reliability/diagnostics-beginner-guide.mdx index 0282af4025a..835696f1ae0 100644 --- a/src/i18n/content/jp/docs/new-relic-solutions/observability-maturity/uptime-performance-reliability/diagnostics-beginner-guide.mdx +++ b/src/i18n/content/jp/docs/new-relic-solutions/observability-maturity/uptime-performance-reliability/diagnostics-beginner-guide.mdx @@ -251,7 +251,67 @@ IT における一般的な変更の例は次のとおりです。 この表は、健康データ ポイントごとに並べ替えられた問題マトリックスです。 -|データポイント | New Relic機能 |一般的な問題の原因 | | ---------- | --------------------- | -------------------------------------------------- -------------------------------------------------- ------------------- | |出力 | APM 、インフラ、ログ、NPM | アプリケーション、データ ソース、ハードウェア構成変更、インフラストラクチャ、内部ネットワーキング、サードパーティ プロバイダー ( AWS 、GCP) | |入力 | 外形監視、ログ |外部ルーティング (CDN、ゲートウェイなど)、内部ルーティング、インターネット上のもの (ISP など) | |クライアント |ブラウザ、モバイル |ブラウザまたはモバイル コード | + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ データポイント + + New Relic の機能 + + 一般的な問題の原因 +
+ 出力 + + APM、インフラ、ログ、NPM + + アプリケーション、データ ソース、ハードウェア構成の変更、インフラストラクチャ、内部ネットワーク、サード パーティ プロバイダー (AWS、GCP) +
+ 入力 + + 合成、ログ + + 外部ルーティング (CDN、ゲートウェイなど)、内部ルーティング、インターネット上のもの (ISP など) +
+ クライアント + + ブラウザ、モバイル + + ブラウザまたはモバイル コード +
問題は複雑化する傾向がありますが、サービス レベルを迅速に回復するために、「原因を突き止め」、「何が変化したか」を特定することが目標です。 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 e96683c9fcf..07a20c8c00c 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 @@ -17,8 +17,6 @@ Lambda レイヤーを使用してサーバーレス監視を有効にする前 3. IAMリソース、マネージドシークレット、Lambdasを作成するパーミッションを持つAWSアカウント。また、CloudFormationスタックやS3バケットを作成するための権限も必要です。 -/\* 次に、次の手順を完了する必要があります。1. \[AWS CLI v2]\(https://docs.aws.amazon.com/cli/latest/userguide/install-cliv2.html) をインストールします。 \` AWS configure\` を使用して設定します。 AWS アクセスキー ID と AWS シークレットアクセスキーが必要になります。2. \[Python]\(https://www.python.org/downloads/) をインストールします。 バージョン3.3以上。 3. \[\`newrelic-lambda\` CLI]\(https://github.com/newrelic/newrelic-lambda-cli#installation)をインストールします。 インストールするには、次のコマンドを実行します: \`\`\`bash pip3 install newrelic-lambda-cli \`\`\` 4. デフォルトでは、AWS 管理ポリシー \`ReadOnlyAccess\` を使用します。 これにより、インフラストラクチャ統合は、 Lambda関数とCloudWatchメトリクスだけでなく、アカウント内のすべてのリソースを確認できるようになります。 New Relic はこのデフォルトを推奨していますが、一部の組織はサードパーティ統合のために厳格なセキュリティ体制を好むことを理解しています。 New Relic のアクセスを制限したい場合は、IAM ロールに最低限以下の権限を付与することができます: \`\`\`yaml リソース: "\*" アクション: - "cloudwatch:GetMetricStatistics" - "cloudwatch:ListMetrics" - "cloudwatch:GetMetricData" - "lambda:GetAccountSettings" - "lambda:ListFunctions" - "lambda:ListAliases" - "lambda:ListTags" - "lambda:ListEventSourceMappings" \`\`\` 5. CLI を実行する前に、 AWSで New Relic に最低限以下の権限を付与する必要があります: \`\`\`json \{ "Version": "2012-10-17", "Statement": \[ \{ "Sid": "CLIAccessPolicy", "Action": \[ "cloudformation:CreateChangeSet", "cloudformation:CreateStack", "cloudformation:DescribeStacks", "cloudformation:ExecuteChangeSet", "iam:AttachRolePolicy", "iam:CreateRole", "iam:GetRole", "iam:PassRole", "lambda:AddPermission", "lambda:CreateFunction", "lambda:GetFunction", "ログ:DeleteSubscriptionFilter", "ログ:DescribeSubscriptionFilters", "ログ:PutSubscriptionFilter", "s3:GetObject", "serverlessrepo:CreateCloudFormationChangeSet", "secretsmanager:CreateSecret" ], "Effect": "Allow", "Resource": "\*" }, \{ "Sid": "NRLogAccessPolicy", "Effect": "Allow", "Action": \[ "serverlessrepo:CreateCloudFormationTemplate", "serverlessrepo:GetCloudFormationTemplate" ], "Resource": "arn: AWS :serverlessrepo:us-east-1:463657938898: application/NewRelic-log-ingestion" } ] } \`\`\` CLI について詳しく知りたい場合は、\[CLI リポジトリ]\(https://github.com/newrelic/newrelic-lambda-cli#installation) を参照してください。 \*/ - ## サポートされているランタイム インストゥルメンテーションのタイプに基づいて、次のランタイムがサポートされます。 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 6fa2805a49b..5e1fd5caff9 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 @@ -193,12 +193,12 @@ Lambda関数のコンテナ化されたイメージを使用していて、ア ### Lambda関数を設定する - 2. Lambda 関数を元の関数と同じ設定で構成しますが、 New Relic Lambda 監視 に必要な環境変数を必ず追加してください。 詳細については、 [環境変数を](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/configure-serverless-monitoring-aws-lambda/#environment)参照してください。 + 2. Lambda関数を元の関数と同じ設定で構成しますが、New Relic Lambda監視に必要な環境変数を必ず追加してください。 詳細については、 [環境変数](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda)を参照してください。 3. 関数のハンドラーを更新して、関数の`cmd`オーバーライドで新しくアタッチされたレイヤーを指すようにします。 次の 2 つのドキュメントの指示に従ってそれを実行できます。 - * [ラムダコンソールのUI設定](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/instrument-your-own/#console) - * [Lambda 監視のためのレイヤーレス インストゥルメンテーション](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/enable-serverless-monitoring-aws-lambda-layerless) + * [階層化されたインストゥルメンテーション](/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) 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 2839589d0d1..b8c47d9fa25 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 @@ -149,9 +149,7 @@ translationType: machine - これを次のように設定して、ディストリビューティッド（分散）トレーシングを無効にします。 - - `false` + ディストリビューティッド（分散）トレーシングを有効にしてトレースを生成する @@ -349,9 +347,7 @@ translationType: machine - これを次のように設定して、ディストリビューティッド（分散）トレーシングを無効にします。 - - `false` + ディストリビューティッド（分散）トレーシングを有効にしてトレースを生成する @@ -543,9 +539,7 @@ translationType: machine - これを次のように設定して、ディストリビューティッド（分散）トレーシングを無効にします。 - - `false` + ディストリビューティッド（分散）トレーシングを有効にしてトレースを生成する @@ -631,9 +625,7 @@ translationType: machine - これを次のように設定して、ディストリビューティッド（分散）トレーシングを無効にします。 - - `false` + ディストリビューティッド（分散）トレーシングを有効にしてトレースを生成する @@ -681,9 +673,7 @@ translationType: machine - これを次のように設定して、ディストリビューティッド（分散）トレーシングを無効にします。 - - `false` + ディストリビューティッド（分散）トレーシングを有効にしてトレースを生成する @@ -823,9 +813,7 @@ translationType: machine - これを次のように設定して、ディストリビューティッド（分散）トレーシングを無効にします。 - - `false` + ディストリビューティッド（分散）トレーシングを有効にしてトレースを生成する diff --git a/src/i18n/content/jp/docs/serverless-function-monitoring/azure-function-monitoring/compatibility-requirement-azure-monitoring.mdx b/src/i18n/content/jp/docs/serverless-function-monitoring/azure-function-monitoring/compatibility-requirement-azure-monitoring.mdx new file mode 100644 index 00000000000..6b451752cb4 --- /dev/null +++ b/src/i18n/content/jp/docs/serverless-function-monitoring/azure-function-monitoring/compatibility-requirement-azure-monitoring.mdx @@ -0,0 +1,54 @@ +--- +title: インストゥルメント化されたAzure関数の互換性と要件 +metaDescription: Azure function monitoring agent compatibility and requirements. +freshnessValidatedDate: never +translationType: machine +--- + +[Azure Functionsプランニングする](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/configure-serverless-aws-monitoring)前に、システムが次の要件を満たしていることを確認してください。 + +## 基本要件 [#requirements] + +* [従量課金プラン](https://learn.microsoft.com/en-us/azure/azure-functions/consumption-plan)または[専用プラン](https://learn.microsoft.com/en-us/azure/azure-functions/dedicated-plan)でホストされる Azure Functions。 + +* [Kudu サービスにアクセスするには、必要な権限](https://learn.microsoft.com/en-us/azure/app-service/resources-kudu#access-kudu-for-your-app)が必要です。 + +* [管理者ロール](/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 アカウント。 + +* 。 + +* .NET エージェント バージョン 10.30 以上。 + + + エンドツーエンドのディストリビューティッド（分散）トレーシングは、HTTP リクエストに対してのみサポートされます。 さらに、データベースやサービス バスなどの外部サービスへの呼び出しのトレースも引き続き利用できます。 + + +## サポートされているランタイム + +ホスティング環境に基づいて、次のランタイムがサポートされます。 + + + + Linux Windows コンテナ化された機能 + + + + + * .NET: `dotnet6.0` 、 `dotnet8.0` + + + + * .NET: `dotnet6.0` 、 `dotnet8.0` + + + + * .NET: `dotnet6.0` 、 `dotnet8.0` + + + + +## 次のステップ + + + Azure Functionsのインストゥルメンテーションと設定を始めましょう + \ No newline at end of file diff --git a/src/i18n/content/jp/docs/serverless-function-monitoring/azure-function-monitoring/env-variables-azure.mdx b/src/i18n/content/jp/docs/serverless-function-monitoring/azure-function-monitoring/env-variables-azure.mdx new file mode 100644 index 00000000000..bb356023a0a --- /dev/null +++ b/src/i18n/content/jp/docs/serverless-function-monitoring/azure-function-monitoring/env-variables-azure.mdx @@ -0,0 +1,221 @@ +--- +title: Azure Functions の環境変数 監視 +metaDescription: Configure environment variables to monitor your Azure functions with New Relic +freshnessValidatedDate: never +tags: + - AWS Lambda + - Environment Variables + - Configuration + - Secrets Management +translationType: machine +--- + +環境変数は、コードの外部に設定と秘密を保存する方法です。 次の表には、New Relic を使用してAzure Functions を監視するために設定できる必須変数とランタイム固有の変数が表示されます。 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ 環境変数 + + デフォルト値 + + オプション + + 説明 +
+ `CORECLR_ENABLE_PROFILING` + + `0` + + `0` + + , + + `1` + + **必須** + + 。 これを + + `1` + + に設定してプロファイリングを有効にします。 +
+ `CORECLR_PROFILER` + + + + + + **必須** + + 。 .NET エージェントを有効にするにはこれを設定します。 +
+ `CORECLR_NEWRELIC_HOME` + + + + + + **必須** + + 。 .NET エージェントを有効にするにはこれを設定します。 +
+ `CORECLR_PROFILER_PATH` + + + + + + **必須** + + 。 .NET エージェントを有効にするにはこれを設定します。 +
+ `NEW_RELIC_DISTRIBUTED_TRACING_ENABLED` + + `true` + + `true` + + , + + `false` + + ディストリビューティッド（分散）トレースを有効にしてトレースを生成します。 +
+ `NEW_RELIC_APP_NAME` + + + + + + アプリケーション名を設定します。ただし、New Relic UI では使用されません。 +
+ `NEW_RELIC_AZURE_FUNCTION_MODE_ENABLED` + + `1` + + `1` + + , + + `0` + + 値を + + `0` + + に設定して、Azure Functions モードを無効にします。 +
+ `NEW_RELIC_LOG_DIRECTORY` + + + + + + エージェントとプロファイラーのログを保存する場所を変更します。 +
+ `NEW_RELIC_LOG_LEVEL` + + `info` + + `info` + + 、 + + `debug` + + 、 + + `finest` + + エージェントログレベルを設定します。 +
+ +## 次のステップ + + + Azure Functionsのインストゥルメンテーションと設定を始めましょう + \ No newline at end of file diff --git a/src/i18n/content/jp/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx b/src/i18n/content/jp/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx new file mode 100644 index 00000000000..ca5f255b16e --- /dev/null +++ b/src/i18n/content/jp/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx @@ -0,0 +1,242 @@ +--- +title: New Relic に Azure Functions 監視をインストールして構成する +metaDescription: Configure your Azure Functions with New Relic +freshnessValidatedDate: never +translationType: machine +--- + +## あなたが始める前に [#begin] + +Azure Functions が[互換性と要件を](/docs/serverless-function-monitoring/azure-function-monitoring/compatibility-requirement-azure-monitoring)満たしていることを確認します。 + + + + ## AzureアカウントをNew Relicにリンクする + + Azure Monitor メトリクスのポーリングを構成することで、 Azureアカウントを New Relic にリンクできます。 これにより、New Relic UIでメトリクスを確認できるようになります。 詳細については、 [Azureインテグレーション」](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-functions-monitoring-integration/#polling)を参照してください。 + + + + ## New Relic .NETエージェントを使用してAzure Functions計装する + + 要件に基づいて、次のいずれかのオプションを選択して、New Relic .NET エージェントを使用してAzure Functions計測します。 + + + + Linux Windows コンテナ化された機能 + + + + + 1. `NewRelic.Agent` NuGet パッケージをアプリケーション プロジェクトに追加します。 + + * Visual Studio コード エディターで、NuGet パッケージマネージャを使用して、最新バージョンの`NewRelic.Agent`を検索し、アプリケーションに追加します。 + * 他の開発環境を使用している場合は、 `dotnet add packages NewRelic.Agent`を使用してパッケージを追加できます。 + + 2. 好みの公開メカニズムを使用して、更新されたアプリケーションを Azure にデプロイします。 これには、 `/home/site/www/newrelic`フォルダーにインストールされている New Relic エージェントが含まれます。 + + + + Kudu サービス ページに移動し、次の操作を実行します。 + + 1. Azure ポータルで、関数アプリに移動します。 + 2. **Development tools**セクションをクリックし、 **Advanced Tools > Go**を選択します。 + 3. 利用可能なサイト拡張機能を表示するには、 **Site extensions**タブをクリックします。 + 4. 拡張機能をインストールするには、 `New Relic .NET Agent`を検索し、 **+**をクリックします。 + + + + New Relic .NET エージェントをインストールするには、Dockerfile の最終段階で次の行を追加します。 + + ```dockerfile + # install the latest New Relic .NET agent using the apt-get package manager + RUN apt-get update && apt-get install -y wget ca-certificates gnupg \ + && echo 'deb http://apt.newrelic.com/debian/ newrelic non-free' | tee /etc/apt/sources.list.d/newrelic.list \ + && wget https://download.newrelic.com/548C16BF.gpg \ + && apt-key add 548C16BF.gpg \ + && apt-get update \ + && apt-get install -y newrelic-dotnet-agent \ + && rm -rf /var/lib/apt/lists/* + + ``` + + + + + + + ## 環境変数を設定する + + New Relic .NETエージェントを使用してAzure Functionsインストゥルメントした後、次の手順を実行してNew Relicにデータを送信するように[環境変数](/docs/serverless-function-monitoring/azure-function-monitoring/env-variables-azure)を構成します。 + + 1. Azure ポータルで Azure Functions に移動し、 **Settings** \[設定]の下にある**Environment variables** \[環境変数] をクリックして、 **Advanced edit** \[詳細編集] をクリックします。 + + 2. アプリケーションの要件に基づいて、次の値を貼り付けます。 + + + 既存の最後の行の末尾に必ずカンマを追加し、次の設定でライセンスキーとアプリ名を更新してください。 + + + + + Linux Windows コンテナ化された機能 + + + + + ```json + { + "name": "CORECLR_ENABLE_PROFILING", + "value": "1", + "slotSetting": false + }, + { + "name": "CORECLR_NEWRELIC_HOME", + "value": "/home/site/wwwroot/newrelic", + "slotSetting": false + }, + { + "name": "CORECLR_PROFILER", + "value": "{36032161-FFC0-4B61-B559-F6C5D41BAE5A}", + "slotSetting": false + }, + { + "name": "CORECLR_PROFILER_PATH", + "value": "/home/site/wwwroot/newrelic/libNewRelicProfiler.so", + "slotSetting": false + }, + { + "name": "NEW_RELIC_AZURE_FUNCTION_MODE_ENABLED", + "value": "1", + "slotSetting": false + }, + { + "name": "NEW_RELIC_LICENSE_KEY", + "value": "", + "slotSetting": false + }, + { + "name": "NEWRELIC_LOG_DIRECTORY", + "value": "/home/LogFiles/NewRelic", + "slotSetting": false + }, + { + "name": "NEWRELIC_LOG_LEVEL", + "value": "info", + "slotSetting": false + }, + + + ``` + + + + ```json + { + "name": "CORECLR_PROFILER_PATH", + "value": "C:\\home\\NewRelicAgent\\Core\\NewRelic.Profiler.dll", + "slotSetting": false + }, + { + "name": "CORECLR_NEWRELIC_HOME", + "value": "C:\\home\\NewRelicAgent\\Core", + "slotSetting": false + }, + { + "name": "NEWRELIC_LOG_DIRECTORY", + "value": "C:\\home\\LogFiles\\NewRelic", + "slotSetting": false + }, + { + "name": "NEW_RELIC_AZURE_FUNCTION_MODE_ENABLED", + "value": "1", + "slotSetting": false + }, + { + "name": "CORECLR_ENABLE_PROFILING", + "value": "1", + "slotSetting": false + }, + { + "name": "CORECLR_PROFILER", + "value": "{36032161-FFC0-4B61-B559-F6C5D41BAE5A}", + "slotSetting": false + }, + { + "name": "NEW_RELIC_LICENSE_KEY", + "value": "", + "slotSetting": false + }, + { + "name": "NEWRELIC_LOG_LEVEL", + "value": "info", + "slotSetting": false + }, + { + "name": "NEW_RELIC_APP_NAME", + "value": "", + "slotSetting": false + }, + + ``` + + + + ```json + { + "name": "CORECLR_ENABLE_PROFILING", + "value": "1", + "slotSetting": false + }, + { + "name": "CORECLR_NEWRELIC_HOME", + "value": "/usr/local/newrelic-dotnet-agent", + "slotSetting": false + }, + { + "name": "CORECLR_PROFILER", + "value": "{36032161-FFC0-4B61-B559-F6C5D41BAE5A}", + "slotSetting": false + }, + { + "name": "CORECLR_PROFILER_PATH", + "value": "/usr/local/newrelic-dotnet-agent/libNewRelicProfiler.so", + "slotSetting": false + }, + { + "name": "NEW_RELIC_AZURE_FUNCTION_MODE_ENABLED", + "value": "1", + "slotSetting": false + }, + { + "name": "NEW_RELIC_LICENSE_KEY", + "value": "", + "slotSetting": false + }, + { + "name": "NEWRELIC_LOG_DIRECTORY", + "value": "/home/LogFiles/NewRelic", + "slotSetting": false + }, + { + "name": "NEWRELIC_LOG_LEVEL", + "value": "info", + "slotSetting": false + }, + + ``` + + + + + + + ## Azure Functionsを再起動します + + 環境変数を追加したら、Azure Functions を再起動して変更を適用します。 + + + +## 次のステップ + +インストールと設定の手順が完了したら、 Azure Functionsにトラフィックを送信して、New Relic UIダッシュボードでメトリクスを確認します。 \ No newline at end of file diff --git a/src/i18n/content/jp/docs/serverless-function-monitoring/azure-function-monitoring/introduction-azure-monitoring.mdx b/src/i18n/content/jp/docs/serverless-function-monitoring/azure-function-monitoring/introduction-azure-monitoring.mdx new file mode 100644 index 00000000000..70cff65732e --- /dev/null +++ b/src/i18n/content/jp/docs/serverless-function-monitoring/azure-function-monitoring/introduction-azure-monitoring.mdx @@ -0,0 +1,20 @@ +--- +title: Azure Functions 監視の概要 +metaDescription: This provides an overview of New Relic's AWS Lambda monitoring and details how to link your accounts. +freshnessValidatedDate: never +translationType: machine +--- + +New Relic のAzure Functions向けインストゥルメンテーションは、関数の内部動作を詳細に可視化します。 New Relic エージェントを関数に追加すると、各呼び出しが New Relic によって監視されます。 これにより、関数呼び出しの継続時間、エラーの監視、ディストリビューティッド（分散）トレーシングの確認、ソース イベントと関数の応答に関する詳細の記録が可能になります。 + + + Azure Functionsの場合、エージェントはディストリビューティッド（分散）トレーシングやログなどのデータをレポートします。これらのデータは、「サービス - APM 」でAPMとして利用できます。 ただし、 Azure Functions用の別のエンティティ (インフラストラクチャ監視によって提供される) がまだ存在します。 + + +new-relic-azure-function-monitoring.gif + +## 次のステップ + + + サポートされているランタイムと前提条件の詳細については、こちらをご覧ください。 Azure Functionsのインストゥルメンテーションと設定を始めましょう + \ No newline at end of file diff --git a/src/i18n/content/jp/docs/serverless-function-monitoring/overview.mdx b/src/i18n/content/jp/docs/serverless-function-monitoring/overview.mdx index 171bd3058bf..3a4497fc74d 100644 --- a/src/i18n/content/jp/docs/serverless-function-monitoring/overview.mdx +++ b/src/i18n/content/jp/docs/serverless-function-monitoring/overview.mdx @@ -1,12 +1,12 @@ --- -title: サーバーレス機能の監視 +title: サーバーレスのモニタリング freshnessValidatedDate: never translationType: machine --- -サーバーレス機能は、サーバーの管理を気にせずにクラウドでコードを実行する方法です。 サーバーのセットアップと保守の代わりに、クラウド プロバイダーがすべての処理を行います。 つまり、開発者はサーバー管理の技術的な詳細を扱うことなく、ユーザーがボタンをクリックするなどの特定のイベントに応答するコードの作成に集中できます。 New Relic のサーバー レス機能監視機能を活用することで、組織は運用効率を向上させ、アプリケーションのパフォーマンスを向上させ、シームレスなユーザー エクスペリエンスを確保できます。 +サーバーレス機能は、サーバーの管理を気にせずにクラウドでコードを実行する方法です。 サーバーのセットアップと保守の代わりに、クラウド プロバイダーがすべての処理を行います。 つまり、開発者はサーバー管理の技術的な詳細を扱うことなく、ユーザーがボタンをクリックするなどの特定のイベントに応答するコードの作成に集中できます。 New Relic のサーバーレス監視機能を活用することで、組織は運用効率を向上させ、アプリケーションのパフォーマンスを向上させ、シームレスなユーザー エクスペリエンスを確保できます。 -以下は、サーバーレス機能監視に New Relic を使用する主な利点の一部です。 +サーバーレス監視に New Relic を使用する主な利点は次のとおりです。 * **統合監視:**クラウド プロバイダーに関係なく、すべてのサーバー レス機能を 1 つのダッシュ ボードで視覚化し、さまざまな環境にわたる機能の管理と監視を簡素化します。 @@ -21,7 +21,7 @@ New Relic がサーバー レス機能の監視にどのように役立つかに - + \ No newline at end of file diff --git a/src/i18n/content/jp/docs/service-level-management/create-slm.mdx b/src/i18n/content/jp/docs/service-level-management/create-slm.mdx index 8f15ea85923..b26c2e9e04e 100644 --- a/src/i18n/content/jp/docs/service-level-management/create-slm.mdx +++ b/src/i18n/content/jp/docs/service-level-management/create-slm.mdx @@ -129,7 +129,8 @@ SLIは、有効なリクエストの総数のうち、良いレスポンスの 継続時間の条件に適切な値を選択するために、1 つの典型的な方法は、過去 7 日間または 15 日間の回答の 95 パーセンタイルの継続時間を選択することです。 [クエリビルダー](/docs/query-your-data/explore-query-data/query-builder/introduction-query-builder/) を使用してこの継続時間のしきい値を見つけ、それを使用して SLI にとって良いイベントと思われるものを決定します。 ```sql - SELECT percentile(duration, 95) FROM Transaction WHERE entityGuid = '{entityGuid}' SINCE 7 days ago LIMIT MAX + SELECT percentile(duration, 95) FROM Transaction + WHERE entityGuid = '{entityGuid}' SINCE 7 days ago LIMIT MAX ``` @@ -171,7 +172,8 @@ OpenTelemetryのスパンに基づくと、これらのSLIはリクエストド ```sql FROM Span - WHERE entity.guid = '{entityGuid}' AND (span.kind IN ('server', 'consumer') OR kind IN ('server', 'consumer')) + WHERE entity.guid = '{entityGuid}' AND (span.kind IN ('server', 'consumer') + OR kind IN ('server', 'consumer')) ``` ここで、 `{entityGuid}`はサービスのGUIDです。 @@ -182,7 +184,8 @@ OpenTelemetryのスパンに基づくと、これらのSLIはリクエストド ```sql FROM Span - WHERE entity.guid = '{entityGuid}' AND (span.kind IN ('server', 'consumer') OR kind IN ('server', 'consumer')) AND otel.status_code = 'ERROR' + WHERE entity.guid = '{entityGuid}' AND (span.kind IN ('server', 'consumer') + OR kind IN ('server', 'consumer')) AND otel.status_code = 'ERROR' ``` ここで、 `{entityGuid}`はサービスのGUIDです。 @@ -196,7 +199,9 @@ OpenTelemetryのスパンに基づくと、これらのSLIはリクエストド 継続時間の条件に適切な値を選択するために、1 つの典型的な方法は、過去 7 日間または 15 日間の回答の 95 パーセンタイルの継続時間を選択することです。 [クエリビルダー](/docs/query-your-data/explore-query-data/query-builder/introduction-query-builder/) を使用してこの継続時間のしきい値を見つけ、それを使用して SLI にとって良いイベントと思われるものを決定します。 ```sql - SELECT percentile(duration.ms, 95) FROM Span WHERE entityGuid = '{entityGuid}' AND (span.kind IN ('server', 'consumer') OR kind IN ('server', 'consumer')) SINCE 7 days ago LIMIT MAX + SELECT percentile(duration.ms, 95) FROM Span + WHERE entityGuid = '{entityGuid}' AND (span.kind IN ('server', 'consumer') + OR kind IN ('server', 'consumer')) SINCE 7 days ago LIMIT MAX ``` @@ -205,7 +210,8 @@ OpenTelemetryのスパンに基づくと、これらのSLIはリクエストド ```sql FROM Span - WHERE entity.guid = '{entityGuid}' AND (span.kind IN ('server', 'consumer') OR kind IN ('server', 'consumer')) + WHERE entity.guid = '{entityGuid}' AND (span.kind IN ('server', 'consumer') + OR kind IN ('server', 'consumer')) ``` ここで、 `{entityGuid}`はサービスのGUIDです。 @@ -216,7 +222,8 @@ OpenTelemetryのスパンに基づくと、これらのSLIはリクエストド ```sql FROM Span - WHERE entity.guid = '{entityGuid}' AND (span.kind IN ('server', 'consumer') OR kind IN ('server', 'consumer')) AND duration.ms < {duration} + WHERE entity.guid = '{entityGuid}' AND (span.kind IN ('server', 'consumer') + OR kind IN ('server', 'consumer')) AND duration.ms < {duration} ``` * ここで、 `{entityGuid}`はサービスのGUIDです。 @@ -407,8 +414,8 @@ APM メトリクスは[タイムスライス データ](https://docs.newrelic.co デスクトップとモバイルデバイスのCLSを別々に追跡するために、別々のSLIを作成したい場合は、フィールドの最後にこれらの条項のいずれかを追加してください。 - * `and deviceType = 'Mobile'` - * `and deviceType = 'Desktop'` + * `AND deviceType = 'Mobile'` + * `AND deviceType = 'Desktop'` **Good events fields** @@ -425,14 +432,14 @@ APM メトリクスは[タイムスライス データ](https://docs.newrelic.co valid eventsクエリを定義した際に、デスクトップとモバイルデバイスのCLSを別々に追跡するために、別々のSLIを作成することにした場合は、フィールドの最後にこの句を追加します。 - * `and deviceType = 'Mobile'` - * `and deviceType = 'Desktop'` + * `AND deviceType = 'Mobile'` + * `AND deviceType = 'Desktop'` ご使用の環境で`{cumulativeLayoutShift}`に選択する現実的な数を決定するための一般的な方法のひとつは、モバイルデバイスとデスクトップデバイスに分割された、過去7日間または15日間のページ読み込みの75パーセンタイルを選択することです。クエリビルダーを使用して検索します。 ```sql SELECT percentile(cumulativeLayoutShift, 95) FROM PageViewTiming - WHERE entityGuid = '{entityGuid}' since 7 days ago limit max facet deviceType + WHERE entityGuid = '{entityGuid}' SINCE 7 days ago LIMIT MAX FACET deviceType ``` @@ -562,10 +569,10 @@ SLI の作成後、すぐにデータが表示されるわけではありませ ```sql FROM Metric - SELECT getField(`newrelic.goldenmetrics.synth.monitor.medianDurationS`, count) as 'Valid' + SELECT getField(`newrelic.goldenmetrics.synth.monitor.medianDurationS`, count) AS 'Valid' FROM Metric - SELECT getCdfCount(`newrelic.goldenmetrics.synth.monitor.medianDurationS`, 0.5) as 'Good' + SELECT getCdfCount(`newrelic.goldenmetrics.synth.monitor.medianDurationS`, 0.5) AS 'Good' ``` SLI クエリでワイルドカードを使用することもできます。例を次に示します。 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 318bdaecd81..d4017969700 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 @@ -243,15 +243,899 @@ Node.js 에이전트는 [npm(Node Package Manager) 저장소](https://npmjs.org/ -/\* 시작: 호환 테이블 \*/ +## 모듈화된 모듈 + +이후에는 지원되는 Node.js 라이브러리 및 프레임워크 카탈로그와 함께 자동으로 에이전트가 작동됩니다. 이를 통해 웹 앱 및 서버와 관련된 세부 정보에 즉시 액세스할 수 있습니다. 지원되지 않는 프레임워크 또는 라이브러리의 경우 [Node.js 에이전트 API를](https://newrelic.github.io/node-newrelic/API.html) 사용하여 에이전트를 직접 해야 합니다. + +**참고**: 지원되는 최신 버전은 지원되는 최신 버전을 반영하지 않을 수 있습니다. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + -## 모듈화된 모듈 + + -이후에는 지원되는 Node.js 라이브러리 및 프레임워크 카탈로그와 함께 자동으로 에이전트가 작동됩니다. 이를 통해 웹 앱 및 서버와 관련된 세부 정보에 즉시 액세스할 수 있습니다. 지원되지 않는 프레임워크 또는 라이브러리의 경우 [Node.js 에이전트 API를](https://newrelic.github.io/node-newrelic/API.html) 사용하여 에이전트를 직접 해야 합니다. + -**참고**: 지원되는 최신 버전은 지원되는 최신 버전을 반영하지 않을 수 있습니다. + + + + -| 패키지 이름 | 최소 지원 버전 | 최신 지원 버전 | 도입된 버전\* | | --- | --- | --- | --- | | `@apollo/gateway` | 2.3.0 | 2.9.3 | `@newrelic/apollo-server-plugin@1.0.0` | | `@apollo/server` | 4.0.0 | 4.11.2 | `@newrelic/apollo-server-plugin@2.1.0` | | `@aws-sdk/client-bedrock-runtime` | 3.474.0 | 3.716.0 | 11.13.0 | | `@aws-sdk/client-dynamodb` | 3.0.0 | 3.716.0 | 8.7.1 | | `@aws-sdk/client-sns` | 3.0.0 | 3.716.0 | 8.7.1 | | `@aws-sdk/client-sqs` | 3.0.0 | 3.716.0 | 8.7.1 | | `@aws-sdk/lib-dynamodb` | 3.377.0 | 3.716.0 | 8.7.1 | | `@aws-sdk/smithy-client` | 3.47.0 | 3.374.0 | 8.7.1 | | `@elastic/elasticsearch` | 7.16.0 | 8.17.0 | 11.9.0 | | `@grpc/grpc-js` | 1.4.0 | 1.12.5 | 8.17.0 | | `@hapi/hapi` | 20.1.2 | 21.3.12 | 9.0.0 | | `@koa/router` | 11.0.2 | 13.1.0 | 3.2.0 | | `@langchain/core` | 0.1.17 | 0.3.27 | 11.13.0 | | `@nestjs/cli` | 9.0.0 | 10.4.9 | 10.1.0 | | `@opensearch-project/opensearch` | 2.1.0 | 2.13.0 | 12.10.0 | | `@prisma/client` | 5.0.0 | 6.1.0 | 11.0.0 | | `@smithy/smithy-client` | 2.0.0 | 3.5.2 | 11.0.0 | | `amqplib` | 0.5.0 | 0.10.5 | 2.0.0 | | `apollo-server` | 3.0.0 | 3.13.0 | `@newrelic/apollo-server-plugin@1.0.0` | | `apollo-server-express` | 3.0.0 | 3.13.0 | `@newrelic/apollo-server-plugin@1.0.0` | | `aws-sdk` | 2.2.48 | 2.1692.0 | 6.2.0 | | `bluebird` | 2.0.0 | 3.7.2 | 1.27.0 | | `bunyan` | 1.8.12 | 1.8.15 | 9.3.0 | | `cassandra-driver` | 3.4.0 | 4.7.2 | 1.7.1 | | `connect` | 3.0.0 | 3.7.0 | 2.6.0 | | `express` | 4.6.0 | 4.21.2 | 2.6.0 | | `fastify` | 2.0.0 | 5.2.0 | 8.5.0 | | `generic-pool` | 3.0.0 | 3.9.0 | 0.9.0 | | `ioredis` | 4.0.0 | 5.4.2 | 1.26.2 | | `kafkajs` | 2.0.0 | 2.2.4 | 11.19.0 | | `koa` | 2.0.0 | 2.15.3 | 3.2.0 | | `koa-route` | 3.0.0 | 4.0.1 | 3.2.0 | | `koa-router` | 11.0.2 | 13.0.1 | 3.2.0 | | `memcached` | 2.2.0 | 2.2.2 | 1.26.2 | | `mongodb` | 4.1.4 | 6.12.0 | 1.32.0 | | `mysql` | 2.2.0 | 2.18.1 | 1.32.0 | | `mysql2` | 2.0.0 | 3.12.0 | 1.32.0 | | `next` | 13.4.19 | 15.1.3 | 12.0.0 | | `openai` | 4.0.0 | 4.77.0 | 11.13.0 | | `pg` | 8.2.0 | 8.13.1 | 9.0.0 | | `pg-native` | 3.0.0 | 3.2.0 | 9.0.0 | | `pino` | 7.0.0 | 9.6.0 | 8.11.0 | | `q` | 1.3.0 | 1.5.1 | 1.26.2 | | `redis` | 3.1.0 | 4.7.0 | 1.31.0 | | `restify` | 11.0.0 | 11.1.0 | 2.6.0 | | `superagent` | 3.0.0 | 10.1.1 | 4.9.0 | | `undici` | 5.0.0 | 7.2.0 | 11.1.0 | | `when` | 3.7.0 | 3.7.8 | 1.26.2 | | `winston` | 3.0.0 | 3.17.0 | 8.11.0 | + + + + + + + + + + +
+ 패키지 이름 + + 지원되는 최소 버전 + + 최신 지원 버전 + + *에서 소개됨 +
+ `@apollo/gateway` + + 2.3.0 + + 2.8.4 + + `@newrelic/apollo-server-plugin@1.0.0` +
+ `@apollo/server` + + 4.0.0 + + 4.11.0 + + `@newrelic/apollo-server-plugin@2.1.0` +
+ `@aws-sdk/client-bedrock-runtime` + + 3.474.0 + + 3.629.0 + + 11.13.0 +
+ `@aws-sdk/client-dynamodb` + + 3.0.0 + + 3.629.0 + + 8.7.1 +
+ `@aws-sdk/client-sns` + + 3.0.0 + + 3.624.0 + + 8.7.1 +
+ `@aws-sdk/client-sqs` + + 3.0.0 + + 3.624.0 + + 8.7.1 +
+ `@aws-sdk/lib-dynamodb` + + 3.377.0 + + 3.624.0 + + 8.7.1 +
+ `@aws-sdk/smithy-client` + + 3.47.0 + + 3.374.0 + + 8.7.1 +
+ `@elastic/elasticsearch` + + 7.16.0 + + 8.15.0 + + 11.9.0 +
+ `@grpc/grpc-js` + + 1.4.0 + + 1.11.1 + + 8.17.0 +
+ `@hapi/hapi` + + 20.1.2 + + 21.3.10 + + 9.0.0 +
+ `@koa/router` + + 11.0.2 + + 12.0.1 + + 3.2.0 +
+ `@langchain/core` + + 0.1.17 + + 0.2.23 + + 11.13.0 +
+ `@nestjs/cli` + + 9.0.0 + + 10.4.4 + + 10.1.0 +
+ `@prisma/client` + + 5.0.0 + + 5.18.0 + + 11.0.0 +
+ `@smithy/smithy-client` + + 2.0.0 + + 3.1.12 + + 11.0.0 +
+ `amqplib` + + 0.5.0 + + 0.10.4 + + 2.0.0 +
+ `apollo-server` + + 3.0.0 + + 3.13.0 + + `@newrelic/apollo-server-plugin@1.0.0` +
+ `apollo-server-express` + + 3.0.0 + + 3.13.0 + + `@newrelic/apollo-server-plugin@1.0.0` +
+ `aws-sdk` + + 2.2.48 + + 2.1673.0 + + 6.2.0 +
+ `bluebird` + + 2.0.0 + + 3.7.2 + + 1.27.0 +
+ `bunyan` + + 1.8.12 + + 1.8.15 + + 9.3.0 +
+ `cassandra-driver` + + 3.4.0 + + 4.7.2 + + 1.7.1 +
+ `connect` + + 3.0.0 + + 3.7.0 + + 2.6.0 +
+ `express` + + 4.6.0 + + 4.19.2 + + 2.6.0 +
+ `fastify` + + 2.0.0 + + 4.28.1 + + 8.5.0 +
+ `generic-pool` + + 3.0.0 + + 3.9.0 + + 0.9.0 +
+ `ioredis` + + 4.0.0 + + 5.4.1 + + 1.26.2 +
+ `kafkajs` + + 2.0.0 + + 2.2.4 + + 11.19.0 +
+ `koa` + + 2.0.0 + + 2.15.3 + + 3.2.0 +
+ `koa-route` + + 3.0.0 + + 4.0.1 + + 3.2.0 +
+ `koa-router` + + 11.0.2 + + 12.0.1 + + 3.2.0 +
+ `memcached` + + 2.2.0 + + 2.2.2 + + 1.26.2 +
+ `mongodb` + + 4.1.4 + + 6.8.0 + + 1.32.0 +
+ `mysql` + + 2.2.0 + + 2.18.1 + + 1.32.0 +
+ `mysql2` + + 2.0.0 + + 3.11.0 + + 1.32.0 +
+ `next` + + 13.4.19 + + 14.2.5 + + 12.0.0 +
+ `openai` + + 4.0.0 + + 4.55.4 + + 11.13.0 +
+ `pg` + + 8.2.0 + + 8.12.0 + + 9.0.0 +
+ `pg-native` + + 2.0.0 + + 3.1.0 + + 9.0.0 +
+ `pino` + + 7.0.0 + + 9.3.2 + + 8.11.0 +
+ `q` + + 1.3.0 + + 1.5.1 + + 1.26.2 +
+ `redis` + + 3.1.0 + + 4.7.0 + + 1.31.0 +
+ `restify` + + 11.0.0 + + 11.1.0 + + 2.6.0 +
+ `superagent` + + 3.0.0 + + 10.0.0 + + 4.9.0 +
+ `undici` + + 5.0.0 + + 6.19.7 + + 11.1.0 +
+ `when` + + 3.7.0 + + 3.7.8 + + 1.26.2 +
+ `winston` + + 3.0.0 + + 3.14.1 + + 8.11.0 +
\*패키지를 지정하지 않으면 `newrelic` 패키지 내에서 지원됩니다. @@ -263,7 +1147,137 @@ Node.js 에이전트는 다음 AI 플랫폼 및 통합을 지원합니다. `@aws-sdk/client-bedrock-runtime` 모듈을 통해 다음을 지원합니다. -| 모델 | 이미지 | 텍스트 | 비전 | | --- | --- | --- | --- | | AI21 연구소 쥬라기-2 | ❌ | ✅ | - | | 아마존 타이탄 | ❌ | ✅ | - | | 인류학 클로드 | ❌ | ✅ | ❌ | | 코히어 | ❌ | ✅ | - | | 메타 라마2 | ❌ | ✅ | - | | 메타 라마3 | ❌ | ✅ | - | + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ 모델 + + 영상 + + 텍스트 + + 비전 +
+ AI21 연구소 쥬라기-2 + + ❌ + + ✅ + + \- +
+ 아마존 타이탄 + + ❌ + + ✅ + + \- +
+ 인류애적인 클로드 + + ❌ + + ✅ + + ❌ +
+ 코히어 + + ❌ + + ✅ + + \- +
+ 메타 라마2 + + ❌ + + ✅ + + \- +
+ 메타라마3 + + ❌ + + ✅ + + \- +
참고: 모델이 스트리밍을 지원하는 경우 스트리밍 변형도 소비합니다. @@ -271,17 +1285,173 @@ Node.js 에이전트는 다음 AI 플랫폼 및 통합을 지원합니다. LangChain 의 다음과 같은 일반 기능이 지원됩니다. -| 에이전트 | 체인 | 도구 | 벡터스토어 | | --- | --- | --- | --- | | ✅ | ✅ | ✅ | ✅ | + + + + + + + + + + + + + + + + + + + + + + + + +
+ 에이전트 + + 동전 + + 도구 + + 벡터스토어 +
+ ✅ + + ✅ + + ✅ + + ✅ +
모델/공급자는 일반적으로 공급자 모듈의 계측을 통해 전이적으로 지원됩니다. -| 공급자 | 지원됨 | 전이적으로 | | --- | --- | --- | | Azure OpenAI | ❌ | ❌ | | 아마존 기반암 | ❌ | ❌ | | 오픈AI | ✅ | ✅ | + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ 공급자 + + 지원 + + 전이적으로 +
+ Azure OpenAI + + ❌ + + ❌ +
+ 아마존 기반암 + + ❌ + + ❌ +
+ 오픈AI + + ✅ + + ✅ +
### 오픈AI `openai` 모듈을 통해 다음을 지원합니다. -| 오디오 | 채팅 | 완료 | 임베딩 | 파일 | 이미지 | | --- | --- | --- | --- | --- | --- | | ❌ | ✅ | ✅ | ✅ | ❌ | ❌ | + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ 오디오 + + 채팅 + + 완료 + + 임베딩 + + 파일 + + 이미지 +
+ ❌ + + ✅ + + ✅ + + ✅ + + ❌ + + ❌ +
/\* 끝: 호환 테이블 \*/ diff --git a/src/i18n/content/kr/docs/infrastructure/host-integrations/host-integrations-list/temporal-cloud-integration.mdx b/src/i18n/content/kr/docs/infrastructure/host-integrations/host-integrations-list/temporal-cloud-integration.mdx index 924285c75ec..7e89de24914 100644 --- a/src/i18n/content/kr/docs/infrastructure/host-integrations/host-integrations-list/temporal-cloud-integration.mdx +++ b/src/i18n/content/kr/docs/infrastructure/host-integrations/host-integrations-list/temporal-cloud-integration.mdx @@ -51,241 +51,120 @@ Temporal 클라우드 통합은 Temporal Cloud 데이터의 성능을 모니터 ```yml integrations: - - name: nri-flex - config: - name: temporalCloudIntegration - apis: - - event_type: temporalCloudFrontendServiceError - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_frontend_service_error_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudFrontendServiceRequest - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_frontend_service_request_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudPollSuccess - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_poll_success_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudPollSuccessSync - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_poll_success_sync_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudPollTimeout - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_poll_timeout_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudResourceExhaustedErrors - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_resource_exhausted_error_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudScheduleActionSuccess - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_schedule_action_success_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudScheduleBufferOverruns - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_schedule_buffer_overruns_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudScheduleMissedCatchupWindow - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_schedule_missed_catchup_window_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudScheduleRateLimited - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_schedule_rate_limited_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudServiceLatencyBucket - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_service_latency_bucket - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudServiceLatencyCount - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_service_latency_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudServiceLatencySum - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_service_latency_sum - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudStateTransition - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_state_transition_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudTotalAction - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_total_action_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudWorkflowCancel - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_workflow_cancel_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudWorkflowContinued - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_workflow_continued_as_new_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudWorkflowFailed - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_workflow_failed_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudWorkflowSuccess - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_workflow_success_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudWorkflowTerminate - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_workflow_terminate_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudWorkflowTimeout - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_workflow_timeout_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem + - name: nri-flex + config: + name: temporalCloudIntegration + global: + base_url: https://.tmprl.cloud/prometheus/api/v1/ + headers: + accept: application/json + tls_config: + enable: true + key: /certs/client.key + cert: /certs/client.pem + interval: 60s + timeout: 55s + apis: + - event_type: temporalCloudFrontendServiceError + # sum(increase(temporal_cloud_v0_frontend_service_error_count[1m])) by (temporal_namespace,operation) + url: query?query=sum%28increase%28temporal_cloud_v0_frontend_service_error_count%5B1m%5D%29%29%20by%20%28temporal_namespace%2Coperation%29 + split_array: true + leaf_array: true + - event_type: temporalCloudFrontendServiceRequest + # sum(increase(temporal_cloud_v0_frontend_service_request_count[1m])) by (temporal_namespace,operation) + url: query?query=sum%28increase%28temporal_cloud_v0_frontend_service_request_count%5B1m%5D%29%29%20by%20%28temporal_namespace%2Coperation%29 + split_array: true + leaf_array: true + - event_type: temporalCloudPollSuccess + # sum(increase(temporal_cloud_v0_poll_success_count[1m])) by (temporal_namespace,operation,task_type) + url: query?query=sum%28increase%28temporal_cloud_v0_poll_success_count%5B1m%5D%29%29%20by%20%28temporal_namespace%2Coperation%2Ctask_type%29 + split_array: true + leaf_array: true + - event_type: temporalCloudPollSuccessSync + # sum(increase(temporal_cloud_v0_poll_success_sync_count[1m])) by (temporal_namespace,operation,task_type) + url: query?query=sum%28increase%28temporal_cloud_v0_poll_success_sync_count%5B1m%5D%29%29%20by%20%28temporal_namespace%2Coperation%2Ctask_type%29 + split_array: true + leaf_array: true + - event_type: temporalCloudPollTimeout + # sum(increase(temporal_cloud_v0_poll_timeout_count[1m])) by (temporal_namespace,operation,task_type) + url: query?query=sum%28increase%28temporal_cloud_v0_poll_timeout_count%5B1m%5D%29%29%20by%20%28temporal_namespace%2Coperation%2Ctask_type%29 + split_array: true + leaf_array: true + - event_type: temporalCloudResourceExhaustedErrors + # sum(increase(temporal_cloud_v0_resource_exhausted_error_count[1m])) by (temporal_namespace,resource_exhausted_cause) + url: query?query=sum%28increase%28temporal_cloud_v0_resource_exhausted_error_count%5B1m%5D%29%29%20by%20%28temporal_namespace%2Cresource_exhausted_cause%29 + split_array: true + leaf_array: true + - event_type: temporalCloudScheduleActionSuccess + # sum(increase(temporal_cloud_v0_schedule_action_success_count[1m])) by (temporal_namespace) + url: query?query=sum%28increase%28temporal_cloud_v0_schedule_action_success_count%5B1m%5D%29%29%20by%20%28temporal_namespace%29 + split_array: true + leaf_array: true + - event_type: temporalCloudScheduleBufferOverruns + # sum(increase(temporal_cloud_v0_schedule_buffer_overruns_count[1m])) by (temporal_namespace) + url: query?query=sum%28increase%28temporal_cloud_v0_schedule_buffer_overruns_count%5B1m%5D%29%29%20by%20%28temporal_namespace%29 + split_array: true + leaf_array: true + - event_type: temporalCloudScheduleMissedCatchupWindow + # sum(increase(temporal_cloud_v0_schedule_missed_catchup_window_count[1m])) by (temporal_namespace) + url: query?query=sum%28increase%28temporal_cloud_v0_schedule_missed_catchup_window_count%5B1m%5D%29%29%20by%20%28temporal_namespace%29 + split_array: true + leaf_array: true + - event_type: temporalCloudScheduleRateLimited + # sum(increase(temporal_cloud_v0_schedule_rate_limited_count[1m])) by (temporal_namespace) + url: query?query=sum%28increase%28temporal_cloud_v0_schedule_rate_limited_count%5B1m%5D%29%29%20by%20%28temporal_namespace%29 + split_array: true + leaf_array: true + - event_type: temporalCloudStateTransition + # sum(increase(temporal_cloud_v0_state_transition_count[1m])) by (temporal_namespace) + url: query?query=sum%28increase%28temporal_cloud_v0_state_transition_count%5B1m%5D%29%29%20by%20%28temporal_namespace%29 + split_array: true + leaf_array: true + - event_type: temporalCloudTotalAction + # sum(increase(temporal_cloud_v0_total_action_count[1m])) by (temporal_namespace, namespace_mode) + url: query?query=sum%28increase%28temporal_cloud_v0_total_action_count%5B1m%5D%29%29%20by%20%28temporal_namespace%2C%20namespace_mode%29 + split_array: true + leaf_array: true + - event_type: temporalCloudWorkflowCancel + # sum(increase(temporal_cloud_v0_workflow_cancel_count[1m])) by (temporal_namespace, operation) + url: query?query=sum%28increase%28temporal_cloud_v0_workflow_cancel_count%5B1m%5D%29%29%20by%20%28temporal_namespace%2C%20operation%29 + split_array: true + leaf_array: true + - event_type: temporalCloudWorkflowContinued + # sum(increase(temporal_cloud_v0_workflow_continued_as_new_count[1m])) by (temporal_namespace, operation) + url: query?query=sum%28increase%28temporal_cloud_v0_workflow_continued_as_new_count%5B1m%5D%29%29%20by%20%28temporal_namespace%2C%20operation%29 + split_array: true + leaf_array: true + - event_type: temporalCloudWorkflowFailed + # sum(increase(temporal_cloud_v0_workflow_failed_count[1m])) by (temporal_namespace, operation) + url: query?query=sum%28increase%28temporal_cloud_v0_workflow_failed_count%5B1m%5D%29%29%20by%20%28temporal_namespace%2C%20operation%29 + split_array: true + leaf_array: true + - event_type: temporalCloudWorkflowSuccess + # sum(increase(temporal_cloud_v0_workflow_success_count[1m])) by (temporal_namespace, operation) + url: query?query=sum%28increase%28temporal_cloud_v0_workflow_success_count%5B1m%5D%29%29%20by%20%28temporal_namespace%2C%20operation%29 + split_array: true + leaf_array: true + - event_type: temporalCloudWorkflowTerminate + # sum(increase(temporal_cloud_v0_workflow_terminate_count[1m])) by (temporal_namespace, operation) + url: query?query=sum%28increase%28temporal_cloud_v0_workflow_terminate_count%5B1m%5D%29%29%20by%20%28temporal_namespace%2C%20operation%29 + split_array: true + leaf_array: true + - event_type: temporalCloudWorkflowTimeout + # sum(increase(temporal_cloud_v0_workflow_timeout_count[1m])) by (temporal_namespace, operation) + url: query?query=sum%28increase%28temporal_cloud_v0_workflow_timeout_count%5B1m%5D%29%29%20by%20%28temporal_namespace%2C%20operation%29 + split_array: true + leaf_array: true + - event_type: temporalCloudWorkflowExecutionLatencySecP95 + # histogram_quantile(0.95, sum(rate(temporal_cloud_v0_service_latency_bucket[1m] offset 1m)) by (temporal_namespace, operation, le)) + url: query?query=histogram_quantile%280.95%2C%20sum%28rate%28temporal_cloud_v0_service_latency_bucket%5B1m%5D%20offset%201m%29%29%20by%20%28temporal_namespace%2C%20operation%2C%20le%29%29 + split_array: true + leaf_array: true + - event_type: temporalCloudReplicationLagSecP95 + # histogram_quantile(0.95, sum(rate(temporal_cloud_v0_replication_lag_bucket[1m] offset 1m)) by (temporal_namespace, le)) + url: query?query=histogram_quantile%280.95%2C%20sum%28rate%28temporal_cloud_v0_replication_lag_bucket%5B1m%5D%20offset%201m%29%29%20by%20%28temporal_namespace%2C%20le%29%29 + split_array: true + leaf_array: true ``` 3. 지침에 [따라 인프라 에이전트를 다시 시작하세요](/docs/infrastructure/install-infrastructure-agent/manage-your-agent/start-stop-restart-infrastructure-agent/). diff --git a/src/i18n/content/kr/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/test-crash-reporting.mdx b/src/i18n/content/kr/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/test-crash-reporting.mdx index 34e0bc1934b..87a07a1afaa 100644 --- a/src/i18n/content/kr/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/test-crash-reporting.mdx +++ b/src/i18n/content/kr/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/test-crash-reporting.mdx @@ -37,6 +37,10 @@ translationType: machine 네이티브 반응 + + 실룩 거리다 + + 단일성 @@ -250,6 +254,62 @@ translationType: machine ``` + + ## 통사론 [#syntax] + + ```dart + crashNow({String name}) : void ; + ``` + + ## 설명 [#description] + + New Relic 충돌 보고를 테스트하기 위해 Android/iOS에서 데모 런타임 예외를 발생시킵니다. + + ## 매개변수 [#parameters] + + + + + + + + + + + + + + + + + + + + + +
+ 매개변수 + + 유형 + + 설명 +
+ `name` + + `string` + + 선택 과목. 예외에 첨부된 메시지입니다. +
+ + ## 예시 [#example] + + ```dart + NewrelicMobile.instance.crashNow(name: "This is a crash"); + NewrelicMobile.instance.crashNow(); + + ``` + + ## 통사론 [#syntax] diff --git a/src/i18n/content/kr/docs/new-relic-solutions/observability-maturity/uptime-performance-reliability/diagnostics-beginner-guide.mdx b/src/i18n/content/kr/docs/new-relic-solutions/observability-maturity/uptime-performance-reliability/diagnostics-beginner-guide.mdx index 9e6869fdb34..9160caa13c7 100644 --- a/src/i18n/content/kr/docs/new-relic-solutions/observability-maturity/uptime-performance-reliability/diagnostics-beginner-guide.mdx +++ b/src/i18n/content/kr/docs/new-relic-solutions/observability-maturity/uptime-performance-reliability/diagnostics-beginner-guide.mdx @@ -251,7 +251,67 @@ IT의 일반적인 변경 사항의 예는 다음과 같습니다. 이 테이블은 건강 데이터 포인트별로 정렬된 문제 매트릭스입니다. -| 데이터 포인트 | 뉴렐릭 능력 | 일반적인 문제 원인 | | ---------- | -------- | ------------------------------------- ------------------------------------- ------ | | 출력 | APM, 인프라, 로그인, NPM | 도면, 데이터 소스, 하드웨어 구성 변경, 도면, 내부 네트워킹, 타사 공급자(AWS, GCP) | | 입력 | 신세틱스, 로그인 | 외부 라우팅(CDN, 게이트웨이 등), 내부 라우팅, 인터넷상의 사물(ISP 등) | | 클라이언트 | 브라우저, 모바일 | 브라우저 또는 모바일 코드 | + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ 데이터 포인트 + + New Relic 기능 + + 일반적인 문제 소스 +
+ 산출 + + APM, 인프라, 로그, NPM + + 애플리케이션, 데이터 소스, 하드웨어 구성 변경, 인프라, 내부 네트워킹, 타사 공급자(AWS, GCP) +
+ 입력 + + 합성, 통나무 + + 외부 라우팅(CDN, 게이트웨이 등), 내부 라우팅, 인터넷 상의 사물(ISP 등) +
+ 고객 + + 브라우저, 모바일 + + 브라우저 또는 모바일 코드 +
문제는 복잡해지는 경향이 있지만 목표는 서비스 수준을 신속하게 복원하기 위해 "원인을 찾고" "변경된 사항"을 파악하는 것입니다. 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 8129a80ce32..22371215c75 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 @@ -17,8 +17,6 @@ Lambda 계층을 사용하여 서버리스 모니터링을 활성화하려면 3. IAM 리소스, 관리형 암호 및 Lambda를 생성할 수 있는 권한이 있는 AWS 계정. CloudFormation 스택 및 S3 버킷을 생성하기 위한 권한도 필요합니다. -/\* 그런 다음 다음을 완료해야 합니다. 1. \[AWS CLI v2]\(https://docs.aws.amazon.com/cli/latest/userguide/install-cliv2.html)를 설치합니다. \`AWS configure\`를 사용하여 구성합니다. AWS Access Key ID와 AWS Secret Access Key가 필요합니다. 2. \[파이썬]\(https://www.python.org/downloads/)을 설치합니다. 버전 3.3 이상. 3. \[\`newrelic-lambda\` CLI]\(https://github.com/newrelic/newrelic-lambda-cli#installation)를 설치합니다. 설치하려면 다음 명령을 실행하세요. \`\`\`bash pip3 install newrelic-lambda-cli \`\`\` 4. 기본적으로 AWS 관리 정책인 \`ReadOnlyAccess\`를 사용합니다. 이를 통해 인프라 통합을 통해 Lambda 함수와 CloudWatch 지표뿐만 아니라 계정의 모든 리소스를 볼 수 있습니다. 뉴렐릭은 이 기본값을 권장하지만, 일부 조직은 제3자 통합에 대해 엄격한 보안 태세를 선호한다는 점을 알고 있습니다. 뉴렐릭의 접근을 제한하고 싶다면 최소한 다음 권한으로 IAM 역할을 부여할 수 있습니다. \`\`\`yaml Resource: "\*" Action: - "cloudwatch:GetMetricStatistics" - "cloudwatch:ListMetrics" - "cloudwatch:GetMetricData" - "lambda:GetAccountSettings" - "lambda:ListFunctions" - "lambda:ListAliases" - "lambda:ListTags" - "lambda:ListEventSourceMappings" \`\`\` 5. CLI를 실행하기 전에 AWS 에서 최소한 다음 권한을 뉴렐릭에 부여해야 합니다. \`\`\`json \{ "Version": "2012-10-17", "Statement": \[ \{ "Sid": "CLIAccessPolicy", "Action": \[ "cloudformation:CreateChangeSet", "cloudformation:CreateStack", "클라우드포메이션:DescribeStacks", "클라우드포메이션:ExecuteChangeSet", "iam:AttachRolePolicy", "iam:CreateRole", "iam:GetRole", "iam:PassRole", "람다:AddPermission", "람다:CreateFunction", "람다:GetFunction", "로그:DeleteSubscriptionFilter", "로그:DescribeSubscriptionFilters", "로그:PutSubscriptionFilter", "s3:GetObject", "serverlessrepo:CreateCloudFormationChangeSet", "secretsmanager:CreateSecret" ], "효과": "허용", "리소스": "\*" }, \{ "Sid": "NRLogAccessPolicy", "효과": "허용", "작업": \[ "serverlessrepo:CreateCloudFormationTemplate", "serverlessrepo:GetCloudFormationTemplate" ], "Resource": "arn:AWS:serverlessrepo:us-east-1:463657938898:애플리케이션/NewRelic-log-ingestion" } ] } \`\`\` CLI에 대해 자세히 알아보려면 \[CLI를 참조하세요. 리포지터리]\(https://github.com/newrelic/newrelic-lambda-cli#installation). \*/ - ## 지원되는 런타임 측정 유형에 따라 다음과 같은 런타임이 지원됩니다. 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 c225f364731..bdd0adc17cf 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 @@ -193,12 +193,12 @@ Lambda 함수에 컨테이너화된 이미지를 사용하고 런타임을 모 ### Lambda 함수 구성 - 2. 원본 함수와 동일한 설정으로 Lambda 함수를 구성하되, New Relic Lambda 모니터링에 필요한 환경 변수를 추가했는지 확인하세요. 자세한 내용은 [환경 변수를](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/configure-serverless-monitoring-aws-lambda/#environment) 참조하세요. + 2. 원래 함수와 동일한 설정으로 Lambda 함수를 구성하지만 Lambda 모니터링에 필요한 환경 변수를 추가해야 합니다. 자세한 내용은 [환경 변수를](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) 참조하세요. 3. 함수의 `cmd` 재정의에서 새로 연결된 레이어를 가리키도록 함수 핸들러를 업데이트합니다. 다음 두 문서의 지침을 사용하여 그렇게 할 수 있습니다. - * [Lambda 콘솔 UI 구성](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/instrument-your-own/#console) - * [레이어 없는 측정, Lambda 모니터링을 위한 로그](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/enable-serverless-monitoring-aws-lambda-layerless) + * [계층적 측정, 시각](/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) 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 0ebb1da0483..64e69baa146 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 @@ -149,9 +149,7 @@ translationType: machine - 이것을 설정하여 분산 추적을 비활성화합니다. - - `false` + 내보내는 추적을 활성화하여 트레이스를 생성합니다. @@ -347,9 +345,7 @@ translationType: machine - 이것을 설정하여 분산 추적을 비활성화합니다. - - `false` + 내보내는 추적을 활성화하여 트레이스를 생성합니다. @@ -541,9 +537,7 @@ translationType: machine - 이것을 설정하여 분산 추적을 비활성화합니다. - - `false` + 내보내는 추적을 활성화하여 트레이스를 생성합니다. @@ -629,9 +623,7 @@ translationType: machine - 이것을 설정하여 분산 추적을 비활성화합니다. - - `false` + 내보내는 추적을 활성화하여 트레이스를 생성합니다. @@ -679,9 +671,7 @@ translationType: machine - 이것을 설정하여 분산 추적을 비활성화합니다. - - `false` + 내보내는 추적을 활성화하여 트레이스를 생성합니다. @@ -821,9 +811,7 @@ translationType: machine - 이것을 설정하여 분산 추적을 비활성화합니다. - - `false` + 내보내는 추적을 활성화하여 트레이스를 생성합니다. diff --git a/src/i18n/content/kr/docs/serverless-function-monitoring/azure-function-monitoring/compatibility-requirement-azure-monitoring.mdx b/src/i18n/content/kr/docs/serverless-function-monitoring/azure-function-monitoring/compatibility-requirement-azure-monitoring.mdx new file mode 100644 index 00000000000..a8d3c496159 --- /dev/null +++ b/src/i18n/content/kr/docs/serverless-function-monitoring/azure-function-monitoring/compatibility-requirement-azure-monitoring.mdx @@ -0,0 +1,54 @@ +--- +title: 계측화된 Azure Functions에 대한 호환성 및 요구 사항 +metaDescription: Azure function monitoring agent compatibility and requirements. +freshnessValidatedDate: never +translationType: machine +--- + +[Azure Functions모니터하기](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/configure-serverless-aws-monitoring) 전에 시스템이 다음 요구 사항을 충족하는지 확인하세요. + +## 기본 요구 사항 [#requirements] + +* [소비 계획](https://learn.microsoft.com/en-us/azure/azure-functions/consumption-plan) 또는 [전용 계획](https://learn.microsoft.com/en-us/azure/azure-functions/dedicated-plan) 에서 호스팅되는 Azure Functions. + +* [Kudu 서비스에 접속하려면 필요한 권한이](https://learn.microsoft.com/en-us/azure/app-service/resources-kudu#access-kudu-for-your-app) 있어야 합니다. + +* [관리자 역할](/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) 이 있는 뉴렐릭 계정. + +* . + +* .NET 에이전트 버전 10.30 이상. + + + 엔드투엔드 분산 추적은 HTTP 요청에 대해서만 지원됩니다. 또한 데이터베이스 및 Service Bus와 같은 외부 서비스에 대한 호출을 위한 트레이스를 계속 사용할 수 있습니다. + + +## 지원되는 런타임 + +호스팅 환경에 따라 다음과 같은 런타임이 지원됩니다. + + + + Linux Windows 컨테이너화된 기능 + + + + + * .NET: `dotnet6.0`, `dotnet8.0` + + + + * .NET: `dotnet6.0`, `dotnet8.0` + + + + * .NET: `dotnet6.0`, `dotnet8.0` + + + + +## 무엇 향후 계획 + + + Azure Functions에 대한 측정, 로그 및 설정 시작하기 + \ No newline at end of file diff --git a/src/i18n/content/kr/docs/serverless-function-monitoring/azure-function-monitoring/env-variables-azure.mdx b/src/i18n/content/kr/docs/serverless-function-monitoring/azure-function-monitoring/env-variables-azure.mdx new file mode 100644 index 00000000000..07475fe703f --- /dev/null +++ b/src/i18n/content/kr/docs/serverless-function-monitoring/azure-function-monitoring/env-variables-azure.mdx @@ -0,0 +1,221 @@ +--- +title: Azure Functions 모니터링을 위한 환경 변수 +metaDescription: Configure environment variables to monitor your Azure functions with New Relic +freshnessValidatedDate: never +tags: + - AWS Lambda + - Environment Variables + - Configuration + - Secrets Management +translationType: machine +--- + +환경 변수는 코드 외부에 설정과 비밀을 저장하는 방법입니다. 다음 표에서는 Azure Functions를 뉴렐릭으로 모니터링하기 위해 설정할 수 있는 필수 변수와 런타임별 변수를 보여줍니다. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ 환경 변수 + + 기본값 + + 옵션 + + 설명 +
+ `CORECLR_ENABLE_PROFILING` + + `0` + + `0` + + , + + `1` + + **필수의** + + . + + `1` + + 로 설정하여 프로파일링을 활성화하세요. +
+ `CORECLR_PROFILER` + + + + + + **필수의** + + . .NET 에이전트를 활성화하려면 이것을 설정합니다. +
+ `CORECLR_NEWRELIC_HOME` + + + + + + **필수의** + + . .NET 에이전트를 활성화하려면 이것을 설정합니다. +
+ `CORECLR_PROFILER_PATH` + + + + + + **필수의** + + . .NET 에이전트를 활성화하려면 이것을 설정합니다. +
+ `NEW_RELIC_DISTRIBUTED_TRACING_ENABLED` + + `true` + + `true` + + , + + `false` + + 배신 추적을 활성화하여 추적을 생성합니다. +
+ `NEW_RELIC_APP_NAME` + + + + + + 뉴렐릭 UI 에서는 사용되지 않는 기능 이름을 설정합니다. +
+ `NEW_RELIC_AZURE_FUNCTION_MODE_ENABLED` + + `1` + + `1` + + , + + `0` + + 값을 + + `0` + + 로 설정하여 Azure Functions 모드를 비활성화합니다. +
+ `NEW_RELIC_LOG_DIRECTORY` + + + + + + 에이전트 및 프로파일러 로그를 저장할 위치를 수정합니다. +
+ `NEW_RELIC_LOG_LEVEL` + + `info` + + `info` + + , + + `debug` + + , + + `finest` + + 에이전트 로그 레벨을 설정합니다. +
+ +## 무엇 향후 계획 + + + Azure Functions에 대한 측정, 로그 및 설정 시작하기 + \ No newline at end of file diff --git a/src/i18n/content/kr/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx b/src/i18n/content/kr/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx new file mode 100644 index 00000000000..19f13f56c37 --- /dev/null +++ b/src/i18n/content/kr/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx @@ -0,0 +1,242 @@ +--- +title: 뉴렐릭에서 Azure Functions 모니터링 설치 및 구성 +metaDescription: Configure your Azure Functions with New Relic +freshnessValidatedDate: never +translationType: machine +--- + +## 시작하기 전에 [#begin] + +Azure Functions가 [호환성 및 요구 사항을](/docs/serverless-function-monitoring/azure-function-monitoring/compatibility-requirement-azure-monitoring) 충족하는지 확인하세요. + + + + ## Azure 계정을 뉴렐릭에 연결하세요 + + Azure Monitor 지표의 폴링을 구성하여 Azure 계정을 뉴렐릭에 연결할 수 있습니다. 이렇게 하면 뉴렐릭 UI 에서 테크닉을 볼 수 있습니다. 자세한 내용은 [Azure 통합을](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-functions-monitoring-integration/#polling) 참조하세요. + + + + ## 뉴렐릭 .NET 에이전트를 사용하여 Azure Functions 배포합니다. + + 귀하의 요구 사항에 따라 다음 옵션 중 하나를 선택하여 새로운 .NET 에이전트로 Azure Functions 관리하세요. + + + + Linux Windows 컨테이너화된 기능 + + + + + 1. 애플리케이션 프로젝트에 `NewRelic.Agent` NuGet 패키지를 추가합니다. + + * Visual Studio 코드 편집기에서 NuGet 패키지 매니저를 사용하여 `NewRelic.Agent` 의 최신 버전을 검색하고 디버그에 추가하세요. + * 다른 개발 환경을 사용하는 경우 `dotnet add packages NewRelic.Agent` 를 사용하여 패키지를 추가할 수 있습니다. + + 2. 선호하는 게시 메커니즘을 사용하여 업데이트된 Azure 를 구현, 배포합니다. 여기에는 `/home/site/www/newrelic` 폴더에 설치된 뉴렐릭 에이전트가 포함됩니다. + + + + Kudu 서비스 페이지로 이동하여 다음을 수행하세요. + + 1. Azure Portal에서 함수 앱으로 이동합니다. + 2. **Development tools** 섹션을 클릭하고 **Advanced Tools > Go** 선택하세요. + 3. 사용 가능한 사이트 확장 프로그램을 보려면 **Site extensions** 탭을 클릭하세요. + 4. 확장 프로그램을 설치하려면 `New Relic .NET Agent` 을 검색하고 **+** 클릭하세요. + + + + 뉴렐릭 .NET 에이전트를 설치하려면 Dockerfile의 마지막 단계에서 다음 행을 추가합니다. + + ```dockerfile + # install the latest New Relic .NET agent using the apt-get package manager + RUN apt-get update && apt-get install -y wget ca-certificates gnupg \ + && echo 'deb http://apt.newrelic.com/debian/ newrelic non-free' | tee /etc/apt/sources.list.d/newrelic.list \ + && wget https://download.newrelic.com/548C16BF.gpg \ + && apt-key add 548C16BF.gpg \ + && apt-get update \ + && apt-get install -y newrelic-dotnet-agent \ + && rm -rf /var/lib/apt/lists/* + + ``` + + + + + + + ## 환경 변수 구성 + + .NET 에이전트를 사용하여 Azure Functions 계측한 후 다음을 수행하여 데이터를 .NET 에이전트로 전송하기 위한 [환경 변수를](/docs/serverless-function-monitoring/azure-function-monitoring/env-variables-azure) 구성합니다. + + 1. Azure Portal에서 Azure Functions로 이동하여 **Settings** \[설정] 아래에서 **Environment variables** \[환경 변수를] 클릭한 다음 **Advanced edit** \[고급 편집을] 클릭합니다. + + 2. 귀하의 제작 요구 사항에 따라 다음 값을 붙여넣습니다. + + + 마지막 줄의 끝에 쉼표를 추가하고 다음 설정에서 라이선스 키와 앱 이름을 업데이트하세요. + + + + + Linux Windows 컨테이너화된 기능 + + + + + ```json + { + "name": "CORECLR_ENABLE_PROFILING", + "value": "1", + "slotSetting": false + }, + { + "name": "CORECLR_NEWRELIC_HOME", + "value": "/home/site/wwwroot/newrelic", + "slotSetting": false + }, + { + "name": "CORECLR_PROFILER", + "value": "{36032161-FFC0-4B61-B559-F6C5D41BAE5A}", + "slotSetting": false + }, + { + "name": "CORECLR_PROFILER_PATH", + "value": "/home/site/wwwroot/newrelic/libNewRelicProfiler.so", + "slotSetting": false + }, + { + "name": "NEW_RELIC_AZURE_FUNCTION_MODE_ENABLED", + "value": "1", + "slotSetting": false + }, + { + "name": "NEW_RELIC_LICENSE_KEY", + "value": "", + "slotSetting": false + }, + { + "name": "NEWRELIC_LOG_DIRECTORY", + "value": "/home/LogFiles/NewRelic", + "slotSetting": false + }, + { + "name": "NEWRELIC_LOG_LEVEL", + "value": "info", + "slotSetting": false + }, + + + ``` + + + + ```json + { + "name": "CORECLR_PROFILER_PATH", + "value": "C:\\home\\NewRelicAgent\\Core\\NewRelic.Profiler.dll", + "slotSetting": false + }, + { + "name": "CORECLR_NEWRELIC_HOME", + "value": "C:\\home\\NewRelicAgent\\Core", + "slotSetting": false + }, + { + "name": "NEWRELIC_LOG_DIRECTORY", + "value": "C:\\home\\LogFiles\\NewRelic", + "slotSetting": false + }, + { + "name": "NEW_RELIC_AZURE_FUNCTION_MODE_ENABLED", + "value": "1", + "slotSetting": false + }, + { + "name": "CORECLR_ENABLE_PROFILING", + "value": "1", + "slotSetting": false + }, + { + "name": "CORECLR_PROFILER", + "value": "{36032161-FFC0-4B61-B559-F6C5D41BAE5A}", + "slotSetting": false + }, + { + "name": "NEW_RELIC_LICENSE_KEY", + "value": "", + "slotSetting": false + }, + { + "name": "NEWRELIC_LOG_LEVEL", + "value": "info", + "slotSetting": false + }, + { + "name": "NEW_RELIC_APP_NAME", + "value": "", + "slotSetting": false + }, + + ``` + + + + ```json + { + "name": "CORECLR_ENABLE_PROFILING", + "value": "1", + "slotSetting": false + }, + { + "name": "CORECLR_NEWRELIC_HOME", + "value": "/usr/local/newrelic-dotnet-agent", + "slotSetting": false + }, + { + "name": "CORECLR_PROFILER", + "value": "{36032161-FFC0-4B61-B559-F6C5D41BAE5A}", + "slotSetting": false + }, + { + "name": "CORECLR_PROFILER_PATH", + "value": "/usr/local/newrelic-dotnet-agent/libNewRelicProfiler.so", + "slotSetting": false + }, + { + "name": "NEW_RELIC_AZURE_FUNCTION_MODE_ENABLED", + "value": "1", + "slotSetting": false + }, + { + "name": "NEW_RELIC_LICENSE_KEY", + "value": "", + "slotSetting": false + }, + { + "name": "NEWRELIC_LOG_DIRECTORY", + "value": "/home/LogFiles/NewRelic", + "slotSetting": false + }, + { + "name": "NEWRELIC_LOG_LEVEL", + "value": "info", + "slotSetting": false + }, + + ``` + + + + + + + ## Azure Functions 다시 시작 + + 환경 변수를 추가한 후 Azure Functions를 다시 시작하여 변경 사항을 적용합니다. + + + +## 무엇 향후 계획 + +설치 및 설정 단계를 완료한 후 Azure Functions 로 트래픽을 보내 뉴렐릭 UI 대시보드에서 지표를 확인하세요. \ No newline at end of file diff --git a/src/i18n/content/kr/docs/serverless-function-monitoring/azure-function-monitoring/introduction-azure-monitoring.mdx b/src/i18n/content/kr/docs/serverless-function-monitoring/azure-function-monitoring/introduction-azure-monitoring.mdx new file mode 100644 index 00000000000..2d673e08d93 --- /dev/null +++ b/src/i18n/content/kr/docs/serverless-function-monitoring/azure-function-monitoring/introduction-azure-monitoring.mdx @@ -0,0 +1,20 @@ +--- +title: Azure Functions 모니터링 소개 +metaDescription: This provides an overview of New Relic's AWS Lambda monitoring and details how to link your accounts. +freshnessValidatedDate: never +translationType: machine +--- + +뉴렐릭의 Azure Functions 용 계측, 계산기는 함수의 내부 작동에 대한 심층적인 가시성을 제공합니다. 뉴렐릭 에이전트를 함수에 추가하면 각 호출이 뉴렐릭의 모니터가 됩니다. 이를 통해 함수 호출 기간을 추적하고, 오류를 모니터링하고, 분산 추적을 확인하고, 소스 이벤트와 함수의 응답에 대한 세부 정보를 기록할 수 있습니다. + + + Azure Functions 의 경우 에이전트는 '서비스 - APM '에서 APM 으로 사용할 수 있는 출력 트레이스 및 로그와 같은 데이터를 보고합니다. 그러나 Azure Functions 에 대한 별도의 부품(제어에서 제공)은 여전히 존재합니다. + + +new-relic-azure-function-monitoring.gif + +## 무엇 향후 계획 + + + 지원되는 런타임 및 필수 구성 요소에 대해 자세히 알아보기 Azure Functions에 대한 측정, 계측 및 설정을 시작하세요. + \ No newline at end of file diff --git a/src/i18n/content/kr/docs/serverless-function-monitoring/overview.mdx b/src/i18n/content/kr/docs/serverless-function-monitoring/overview.mdx index 59d647042e0..b2be20a1ffd 100644 --- a/src/i18n/content/kr/docs/serverless-function-monitoring/overview.mdx +++ b/src/i18n/content/kr/docs/serverless-function-monitoring/overview.mdx @@ -1,12 +1,12 @@ --- -title: 서버리스 기능 모니터링 +title: 서버리스 모니터링 freshnessValidatedDate: never translationType: machine --- -서버리스 기능은 서버 관리에 대한 걱정 없이 클라우드에서 코드를 실행하는 방법입니다. 클라우드 서비스 제공업체가 서버를 설정하고 유지 관리하는 대신 모든 것을 처리합니다. 즉, 개발자는 서버 관리의 기술적 세부 사항을 다루지 않고도 사용자가 버튼을 클릭하는 등의 특정 이벤트에 응답하는 코드 작성에 집중할 수 있습니다. 뉴렐릭의 서버리스 모니터링 기능을 활용함으로써 조직은 운영 효율성을 향상하고 성능을 개선하며 원활한 사용자 경험을 보장할 수 있습니다. +서버리스 기능은 서버 관리에 대한 걱정 없이 클라우드에서 코드를 실행하는 방법입니다. 클라우드 서비스 제공업체가 서버를 설정하고 유지 관리하는 대신 모든 것을 처리합니다. 즉, 개발자는 서버 관리의 기술적 세부 사항을 다루지 않고도 사용자가 버튼을 클릭하는 등의 특정 이벤트에 응답하는 코드 작성에 집중할 수 있습니다. 뉴렐릭의 서버리스 모니터링 기능을 활용함으로써 조직은 운영 효율성을 향상하고 성능을 향상하며 원활한 사용자 경험을 보장할 수 있습니다. -다음은 서버리스 기능 모니터링에 뉴렐릭을 사용할 때 얻을 수 있는 주요 이점 중 일부입니다. +다음은 서버리스 모니터링에 뉴렐릭을 사용할 때 얻을 수 있는 주요 이점 중 일부입니다. * **통합 모니터링:** 클라우드 공급자에 관계없이 단일 대시보드에서 모든 서버리스 기능을 시각화하여 다양한 환경에서 기능의 관리 및 모니터링을 간소화합니다. @@ -21,7 +21,7 @@ translationType: machine - + \ No newline at end of file diff --git a/src/i18n/content/kr/docs/service-level-management/create-slm.mdx b/src/i18n/content/kr/docs/service-level-management/create-slm.mdx index d388901f5de..be7abbba80d 100644 --- a/src/i18n/content/kr/docs/service-level-management/create-slm.mdx +++ b/src/i18n/content/kr/docs/service-level-management/create-slm.mdx @@ -129,7 +129,8 @@ SLI는 유효한 요청의 총 수에서 좋은 응답의 비율로 정의됩니 기간 조건에 대한 적절한 값을 선택하기 위해 한 가지 일반적인 방법은 지난 7일 또는 15일 동안 응답의 95 백분위수 기간을 선택하는 것입니다. [쿼리 빌더](/docs/query-your-data/explore-query-data/query-builder/introduction-query-builder/) 를 사용하여 이 기간 임계값을 찾고 이를 사용하여 SLI에 좋은 이벤트로 간주되는 이벤트를 결정합니다. ```sql - SELECT percentile(duration, 95) FROM Transaction WHERE entityGuid = '{entityGuid}' SINCE 7 days ago LIMIT MAX + SELECT percentile(duration, 95) FROM Transaction + WHERE entityGuid = '{entityGuid}' SINCE 7 days ago LIMIT MAX ``` @@ -171,7 +172,8 @@ OpenTelemetry 범위를 기반으로 하는 이러한 SLI는 요청 기반 서 ```sql FROM Span - WHERE entity.guid = '{entityGuid}' AND (span.kind IN ('server', 'consumer') OR kind IN ('server', 'consumer')) + WHERE entity.guid = '{entityGuid}' AND (span.kind IN ('server', 'consumer') + OR kind IN ('server', 'consumer')) ``` 여기서 `{entityGuid}` 은 서비스의 GUID입니다. @@ -182,7 +184,8 @@ OpenTelemetry 범위를 기반으로 하는 이러한 SLI는 요청 기반 서 ```sql FROM Span - WHERE entity.guid = '{entityGuid}' AND (span.kind IN ('server', 'consumer') OR kind IN ('server', 'consumer')) AND otel.status_code = 'ERROR' + WHERE entity.guid = '{entityGuid}' AND (span.kind IN ('server', 'consumer') + OR kind IN ('server', 'consumer')) AND otel.status_code = 'ERROR' ``` 여기서 `{entityGuid}` 은 서비스의 GUID입니다. @@ -196,7 +199,9 @@ OpenTelemetry 범위를 기반으로 하는 이러한 SLI는 요청 기반 서 기간 조건에 대한 적절한 값을 선택하기 위해 한 가지 일반적인 방법은 지난 7일 또는 15일 동안 응답의 95 백분위수 기간을 선택하는 것입니다. [쿼리 빌더](/docs/query-your-data/explore-query-data/query-builder/introduction-query-builder/) 를 사용하여 이 기간 임계값을 찾고 이를 사용하여 SLI에 좋은 이벤트로 간주되는 이벤트를 결정합니다. ```sql - SELECT percentile(duration.ms, 95) FROM Span WHERE entityGuid = '{entityGuid}' AND (span.kind IN ('server', 'consumer') OR kind IN ('server', 'consumer')) SINCE 7 days ago LIMIT MAX + SELECT percentile(duration.ms, 95) FROM Span + WHERE entityGuid = '{entityGuid}' AND (span.kind IN ('server', 'consumer') + OR kind IN ('server', 'consumer')) SINCE 7 days ago LIMIT MAX ``` @@ -205,7 +210,8 @@ OpenTelemetry 범위를 기반으로 하는 이러한 SLI는 요청 기반 서 ```sql FROM Span - WHERE entity.guid = '{entityGuid}' AND (span.kind IN ('server', 'consumer') OR kind IN ('server', 'consumer')) + WHERE entity.guid = '{entityGuid}' AND (span.kind IN ('server', 'consumer') + OR kind IN ('server', 'consumer')) ``` 여기서 `{entityGuid}` 은 서비스의 GUID입니다. @@ -216,7 +222,8 @@ OpenTelemetry 범위를 기반으로 하는 이러한 SLI는 요청 기반 서 ```sql FROM Span - WHERE entity.guid = '{entityGuid}' AND (span.kind IN ('server', 'consumer') OR kind IN ('server', 'consumer')) AND duration.ms < {duration} + WHERE entity.guid = '{entityGuid}' AND (span.kind IN ('server', 'consumer') + OR kind IN ('server', 'consumer')) AND duration.ms < {duration} ``` * 여기서 `{entityGuid}` 은 서비스의 GUID입니다. @@ -407,8 +414,8 @@ APM 지표는 [타임슬라이스 데이터](https://docs.newrelic.com/docs/data 데스크톱 및 모바일 장치에서 별도로 CLS를 추적하기 위해 별도의 SLI를 만들려면 필드 끝에 다음 절 중 하나를 추가합니다. - * `and deviceType = 'Mobile'` - * `and deviceType = 'Desktop'` + * `AND deviceType = 'Mobile'` + * `AND deviceType = 'Desktop'` **Good events fields** @@ -425,14 +432,14 @@ APM 지표는 [타임슬라이스 데이터](https://docs.newrelic.com/docs/data 유효한 이벤트 쿼리를 정의할 때 데스크톱 및 모바일 장치에서 별도로 CLS를 추적하기 위해 별도의 SLI를 만들기로 결정한 경우 필드 끝에 다음 절을 추가합니다. - * `and deviceType = 'Mobile'` - * `and deviceType = 'Desktop'` + * `AND deviceType = 'Mobile'` + * `AND deviceType = 'Desktop'` 환경에서 `{cumulativeLayoutShift}` 에 대해 선택할 현실적인 숫자를 결정하기 위해 일반적인 방법 중 하나는 모바일 및 데스크톱 기기에 걸쳐 분류된 지난 7일 또는 15일 동안 페이지 로드의 75번째 백분위수를 선택하는 것입니다. 쿼리 빌더를 사용하여 찾습니다. ```sql SELECT percentile(cumulativeLayoutShift, 95) FROM PageViewTiming - WHERE entityGuid = '{entityGuid}' since 7 days ago limit max facet deviceType + WHERE entityGuid = '{entityGuid}' SINCE 7 days ago LIMIT MAX FACET deviceType ``` @@ -562,10 +569,10 @@ SLI를 생성한 후 데이터가 바로 표시되지 않습니다. 첫 번째 S ```sql FROM Metric - SELECT getField(`newrelic.goldenmetrics.synth.monitor.medianDurationS`, count) as 'Valid' + SELECT getField(`newrelic.goldenmetrics.synth.monitor.medianDurationS`, count) AS 'Valid' FROM Metric - SELECT getCdfCount(`newrelic.goldenmetrics.synth.monitor.medianDurationS`, 0.5) as 'Good' + SELECT getCdfCount(`newrelic.goldenmetrics.synth.monitor.medianDurationS`, 0.5) AS 'Good' ``` SLI 쿼리에 와일드카드를 사용할 수도 있습니다. 예를 들면 다음과 같습니다. 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 a89766f4599..d71b9f63370 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 @@ -243,15 +243,899 @@ Antes de [instalar o agente](/docs/apm/agents/nodejs-agent/installation-configur -/\* begin: compat-table \*/ +## Módulos instrumentados + +Após a instalação, o agente automaticamente instrumento com nosso catálogo de bibliotecas e frameworks Node.js suportados. Isso lhe dá acesso imediato a informações granulares específicas de seus aplicativos e servidores da web. Para estruturas ou bibliotecas não suportadas, você mesmo precisará instrumentar o agente usando a [API Node.js do agente](https://newrelic.github.io/node-newrelic/API.html). + +**Nota**: A versão suportada mais recente pode não refletir a versão suportada mais recente. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + -## Módulos instrumentados + + -Após a instalação, o agente automaticamente instrumento com nosso catálogo de bibliotecas e frameworks Node.js suportados. Isso lhe dá acesso imediato a informações granulares específicas de seus aplicativos e servidores da web. Para estruturas ou bibliotecas não suportadas, você mesmo precisará instrumentar o agente usando a [API Node.js do agente](https://newrelic.github.io/node-newrelic/API.html). + -**Nota**: A versão suportada mais recente pode não refletir a versão suportada mais recente. + + + + -| Nome do pacote | Versão mínima suportada | Última versão suportada | Introduzido em\* | | --- | --- | --- | --- | | `@apollo/gateway` | 2.3.0 | 2.9.3 | `@newrelic/apollo-server-plugin@1.0.0` | | `@apollo/server` | 4.0.0 | 4.11.2 | `@newrelic/apollo-server-plugin@2.1.0` | | `@aws-sdk/client-bedrock-runtime` | 3.474.0 | 3.716.0 | 11.13.0 | | `@aws-sdk/client-dynamodb` | 3.0.0 | 3.716.0 | 8.7.1 | | `@aws-sdk/client-sns` | 3.0.0 | 3.716.0 | 8.7.1 | | `@aws-sdk/client-sqs` | 3.0.0 | 3.716.0 | 8.7.1 | | `@aws-sdk/lib-dynamodb` | 3.377.0 | 3.716.0 | 8.7.1 | | `@aws-sdk/smithy-client` | 3.47.0 | 3.374.0 | 8.7.1 | | `@elastic/elasticsearch` | 7.16.0 | 8.17.0 | 11.9.0 | | `@grpc/grpc-js` | 1.4.0 | 1.12.5 | 8.17.0 | | `@hapi/hapi` | 20.1.2 | 21.3.12 | 9.0.0 | | `@koa/router` | 11.0.2 | 13.1.0 | 3.2.0 | | `@langchain/core` | 0.1.17 | 0.3.27 | 11.13.0 | | `@nestjs/cli` | 9.0.0 | 10.4.9 | 10.1.0 | | `@opensearch-project/opensearch` | 2.1.0 | 2.13.0 | 12.10.0 | | `@prisma/client` | 5.0.0 | 6.1.0 | 11.0.0 | | `@smithy/smithy-client` | 2.0.0 | 3.5.2 | 11.0.0 | | `amqplib` | 0.5.0 | 0.10.5 | 2.0.0 | | `apollo-server` | 3.0.0 | 3.13.0 | `@newrelic/apollo-server-plugin@1.0.0` | | `apollo-server-express` | 3.0.0 | 3.13.0 | `@newrelic/apollo-server-plugin@1.0.0` | | `aws-sdk` | 2.2.48 | 2.1692.0 | 6.2.0 | | `bluebird` | 2.0.0 | 3.7.2 | 1.27.0 | | `bunyan` | 1.8.12 | 1.8.15 | 9.3.0 | | `cassandra-driver` | 3.4.0 | 4.7.2 | 1.7.1 | | `connect` | 3.0.0 | 3.7.0 | 2.6.0 | | `express` | 4.6.0 | 4.21.2 | 2.6.0 | | `fastify` | 2.0.0 | 5.2.0 | 8.5.0 | | `generic-pool` | 3.0.0 | 3.9.0 | 0.9.0 | | `ioredis` | 4.0.0 | 5.4.2 | 1.26.2 | | `kafkajs` | 2.0.0 | 2.2.4 | 11.19.0 | | `koa` | 2.0.0 | 2.15.3 | 3.2.0 | | `koa-route` | 3.0.0 | 4.0.1 | 3.2.0 | | `koa-router` | 11.0.2 | 13.0.1 | 3.2.0 | | `memcached` | 2.2.0 | 2.2.2 | 1.26.2 | | `mongodb` | 4.1.4 | 6.12.0 | 1.32.0 | | `mysql` | 2.2.0 | 2.18.1 | 1.32.0 | | `mysql2` | 2.0.0 | 3.12.0 | 1.32.0 | | `next` | 13.4.19 | 15.1.3 | 12.0.0 | | `openai` | 4.0.0 | 4.77.0 | 11.13.0 | | `pg` | 8.2.0 | 8.13.1 | 9.0.0 | | `pg-native` | 3.0.0 | 3.2.0 | 9.0.0 | | `pino` | 7.0.0 | 9.6.0 | 8.11.0 | | `q` | 1.3.0 | 1.5.1 | 1.26.2 | | `redis` | 3.1.0 | 4.7.0 | 1.31.0 | | `restify` | 11.0.0 | 11.1.0 | 2.6.0 | | `superagent` | 3.0.0 | 10.1.1 | 4.9.0 | | `undici` | 5.0.0 | 7.2.0 | 11.1.0 | | `when` | 3.7.0 | 3.7.8 | 1.26.2 | | `winston` | 3.0.0 | 3.17.0 | 8.11.0 | + + + + + + + + + + +
+ Nome do pacote + + Versão mínima suportada + + Última versão suportada + + Introduzido em* +
+ `@apollo/gateway` + + 2.3.0 + + 2.8.4 + + `@newrelic/apollo-server-plugin@1.0.0` +
+ `@apollo/server` + + 4.0.0 + + 4.11.0 + + `@newrelic/apollo-server-plugin@2.1.0` +
+ `@aws-sdk/client-bedrock-runtime` + + 3.474.0 + + 3.629.0 + + 11.13.0 +
+ `@aws-sdk/client-dynamodb` + + 3.0.0 + + 3.629.0 + + 8.7.1 +
+ `@aws-sdk/client-sns` + + 3.0.0 + + 3.624.0 + + 8.7.1 +
+ `@aws-sdk/client-sqs` + + 3.0.0 + + 3.624.0 + + 8.7.1 +
+ `@aws-sdk/lib-dynamodb` + + 3.377.0 + + 3.624.0 + + 8.7.1 +
+ `@aws-sdk/smithy-client` + + 3.47.0 + + 3.374.0 + + 8.7.1 +
+ `@elastic/elasticsearch` + + 7.16.0 + + 8.15.0 + + 11.9.0 +
+ `@grpc/grpc-js` + + 1.4.0 + + 1.11.1 + + 8.17.0 +
+ `@hapi/hapi` + + 20.1.2 + + 21.3.10 + + 9.0.0 +
+ `@koa/router` + + 11.0.2 + + 12.0.1 + + 3.2.0 +
+ `@langchain/core` + + 0.1.17 + + 0.2.23 + + 11.13.0 +
+ `@nestjs/cli` + + 9.0.0 + + 10.4.4 + + 10.1.0 +
+ `@prisma/client` + + 5.0.0 + + 5.18.0 + + 11.0.0 +
+ `@smithy/smithy-client` + + 2.0.0 + + 3.1.12 + + 11.0.0 +
+ `amqplib` + + 0.5.0 + + 0.10.4 + + 2.0.0 +
+ `apollo-server` + + 3.0.0 + + 3.13.0 + + `@newrelic/apollo-server-plugin@1.0.0` +
+ `apollo-server-express` + + 3.0.0 + + 3.13.0 + + `@newrelic/apollo-server-plugin@1.0.0` +
+ `aws-sdk` + + 2.2.48 + + 2.1673.0 + + 6.2.0 +
+ `bluebird` + + 2.0.0 + + 3.7.2 + + 1.27.0 +
+ `bunyan` + + 1.8.12 + + 1.8.15 + + 9.3.0 +
+ `cassandra-driver` + + 3.4.0 + + 4.7.2 + + 1.7.1 +
+ `connect` + + 3.0.0 + + 3.7.0 + + 2.6.0 +
+ `express` + + 4.6.0 + + 4.19.2 + + 2.6.0 +
+ `fastify` + + 2.0.0 + + 4.28.1 + + 8.5.0 +
+ `generic-pool` + + 3.0.0 + + 3.9.0 + + 0.9.0 +
+ `ioredis` + + 4.0.0 + + 5.4.1 + + 1.26.2 +
+ `kafkajs` + + 2.0.0 + + 2.2.4 + + 11.19.0 +
+ `koa` + + 2.0.0 + + 2.15.3 + + 3.2.0 +
+ `koa-route` + + 3.0.0 + + 4.0.1 + + 3.2.0 +
+ `koa-router` + + 11.0.2 + + 12.0.1 + + 3.2.0 +
+ `memcached` + + 2.2.0 + + 2.2.2 + + 1.26.2 +
+ `mongodb` + + 4.1.4 + + 6.8.0 + + 1.32.0 +
+ `mysql` + + 2.2.0 + + 2.18.1 + + 1.32.0 +
+ `mysql2` + + 2.0.0 + + 3.11.0 + + 1.32.0 +
+ `next` + + 13.4.19 + + 14.2.5 + + 12.0.0 +
+ `openai` + + 4.0.0 + + 4.55.4 + + 11.13.0 +
+ `pg` + + 8.2.0 + + 8.12.0 + + 9.0.0 +
+ `pg-native` + + 2.0.0 + + 3.1.0 + + 9.0.0 +
+ `pino` + + 7.0.0 + + 9.3.2 + + 8.11.0 +
+ `q` + + 1.3.0 + + 1.5.1 + + 1.26.2 +
+ `redis` + + 3.1.0 + + 4.7.0 + + 1.31.0 +
+ `restify` + + 11.0.0 + + 11.1.0 + + 2.6.0 +
+ `superagent` + + 3.0.0 + + 10.0.0 + + 4.9.0 +
+ `undici` + + 5.0.0 + + 6.19.7 + + 11.1.0 +
+ `when` + + 3.7.0 + + 3.7.8 + + 1.26.2 +
+ `winston` + + 3.0.0 + + 3.14.1 + + 8.11.0 +
\*Quando o pacote não é especificado, o suporte está dentro do pacote `newrelic` . @@ -263,7 +1147,137 @@ O agente Node.js oferece suporte à seguinte plataforma e integração de IA. Através do módulo `@aws-sdk/client-bedrock-runtime` , oferecemos suporte a: -| Modelo | Imagem | Texto | Visão | | --- | --- | --- | --- | | Laboratórios AI21 Jurássico-2 | ❌ | ✅ | - | | Amazona Titã | ❌ | ✅ | - | | Claude Antrópico | ❌ | ✅ | ❌ | | Coerente | ❌ | ✅ | - | | Meta Lhama2 | ❌ | ✅ | - | | Meta Lhama3 | ❌ | ✅ | - | + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Modelo + + Imagem + + Texto + + Visão +
+ AI21 Labs Jurassic-2 + + ❌ + + ✅ + + \- +
+ Amazon Titan + + ❌ + + ✅ + + \- +
+ Anthropic Claude + + ❌ + + ✅ + + ❌ +
+ Cohere + + ❌ + + ✅ + + \- +
+ Meta Lhama2 + + ❌ + + ✅ + + \- +
+ Meta Lhama3 + + ❌ + + ✅ + + \- +
Nota: se um modelo suportar streaming, também instrumentamos a variante de streaming. @@ -271,17 +1285,173 @@ Nota: se um modelo suportar streaming, também instrumentamos a variante de stre Os seguintes recursos gerais do Langchain são suportados: -| Agente | Cadeia | Ferramentas | Lojas de vetores | | --- | --- | --- | --- | | ✅ | ✅ | ✅ | ✅ | + + + + + + + + + + + + + + + + + + + + + + + + +
+ Agentes + + Chains + + Ferramentas + + Vectorstores +
+ ✅ + + ✅ + + ✅ + + ✅ +
Modelos/provedores são geralmente suportados transitivamente pela nossa instrumentação do módulo do provedor. -| Provedor | Suportado | Transitivamente | | --- | --- | --- | | Azure OpenAI | ❌ | ❌ | | Base Amazônica | ❌ | ❌ | | OpenAI | ✅ | ✅ | + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Fornecedor + + Suportado + + Transitivamente +
+ Azure OpenAI + + ❌ + + ❌ +
+ Amazon Bedrock + + ❌ + + ❌ +
+ OpenAI + + ✅ + + ✅ +
### OpenAI Através do módulo `openai` , oferecemos suporte a: -| Áudio | Bate-papo | Conclusões | Incorporações | Arquivos | Imagens | | --- | --- | --- | --- | --- | --- | | ❌ | ✅ | ✅ | ✅ | ❌ | ❌ | + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Áudio + + Bater papo + + Conclusões + + Incorporações + + Arquivos + + Imagens +
+ ❌ + + ✅ + + ✅ + + ✅ + + ❌ + + ❌ +
/\* end: compat-table \*/ diff --git a/src/i18n/content/pt/docs/infrastructure/host-integrations/host-integrations-list/temporal-cloud-integration.mdx b/src/i18n/content/pt/docs/infrastructure/host-integrations/host-integrations-list/temporal-cloud-integration.mdx index 33a7a6b118c..80c1f5d600a 100644 --- a/src/i18n/content/pt/docs/infrastructure/host-integrations/host-integrations-list/temporal-cloud-integration.mdx +++ b/src/i18n/content/pt/docs/infrastructure/host-integrations/host-integrations-list/temporal-cloud-integration.mdx @@ -51,241 +51,120 @@ Nossa integração Temporal na nuvem monitora o desempenho dos dados da sua Nuve ```yml integrations: - - name: nri-flex - config: - name: temporalCloudIntegration - apis: - - event_type: temporalCloudFrontendServiceError - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_frontend_service_error_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudFrontendServiceRequest - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_frontend_service_request_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudPollSuccess - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_poll_success_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudPollSuccessSync - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_poll_success_sync_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudPollTimeout - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_poll_timeout_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudResourceExhaustedErrors - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_resource_exhausted_error_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudScheduleActionSuccess - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_schedule_action_success_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudScheduleBufferOverruns - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_schedule_buffer_overruns_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudScheduleMissedCatchupWindow - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_schedule_missed_catchup_window_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudScheduleRateLimited - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_schedule_rate_limited_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudServiceLatencyBucket - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_service_latency_bucket - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudServiceLatencyCount - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_service_latency_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudServiceLatencySum - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_service_latency_sum - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudStateTransition - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_state_transition_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudTotalAction - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_total_action_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudWorkflowCancel - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_workflow_cancel_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudWorkflowContinued - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_workflow_continued_as_new_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudWorkflowFailed - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_workflow_failed_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudWorkflowSuccess - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_workflow_success_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudWorkflowTerminate - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_workflow_terminate_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem - - event_type: temporalCloudWorkflowTimeout - url: https://.tmprl.cloud/prometheus/api/v1/query?query=temporal_cloud_v0_workflow_timeout_count - headers: - accept: application/json - split_array: true - leaf_array: true - tls_config: - enable: true - ca: /ca-certificates.crt - key: /ca.key - cert: /ca.pem + - name: nri-flex + config: + name: temporalCloudIntegration + global: + base_url: https://.tmprl.cloud/prometheus/api/v1/ + headers: + accept: application/json + tls_config: + enable: true + key: /certs/client.key + cert: /certs/client.pem + interval: 60s + timeout: 55s + apis: + - event_type: temporalCloudFrontendServiceError + # sum(increase(temporal_cloud_v0_frontend_service_error_count[1m])) by (temporal_namespace,operation) + url: query?query=sum%28increase%28temporal_cloud_v0_frontend_service_error_count%5B1m%5D%29%29%20by%20%28temporal_namespace%2Coperation%29 + split_array: true + leaf_array: true + - event_type: temporalCloudFrontendServiceRequest + # sum(increase(temporal_cloud_v0_frontend_service_request_count[1m])) by (temporal_namespace,operation) + url: query?query=sum%28increase%28temporal_cloud_v0_frontend_service_request_count%5B1m%5D%29%29%20by%20%28temporal_namespace%2Coperation%29 + split_array: true + leaf_array: true + - event_type: temporalCloudPollSuccess + # sum(increase(temporal_cloud_v0_poll_success_count[1m])) by (temporal_namespace,operation,task_type) + url: query?query=sum%28increase%28temporal_cloud_v0_poll_success_count%5B1m%5D%29%29%20by%20%28temporal_namespace%2Coperation%2Ctask_type%29 + split_array: true + leaf_array: true + - event_type: temporalCloudPollSuccessSync + # sum(increase(temporal_cloud_v0_poll_success_sync_count[1m])) by (temporal_namespace,operation,task_type) + url: query?query=sum%28increase%28temporal_cloud_v0_poll_success_sync_count%5B1m%5D%29%29%20by%20%28temporal_namespace%2Coperation%2Ctask_type%29 + split_array: true + leaf_array: true + - event_type: temporalCloudPollTimeout + # sum(increase(temporal_cloud_v0_poll_timeout_count[1m])) by (temporal_namespace,operation,task_type) + url: query?query=sum%28increase%28temporal_cloud_v0_poll_timeout_count%5B1m%5D%29%29%20by%20%28temporal_namespace%2Coperation%2Ctask_type%29 + split_array: true + leaf_array: true + - event_type: temporalCloudResourceExhaustedErrors + # sum(increase(temporal_cloud_v0_resource_exhausted_error_count[1m])) by (temporal_namespace,resource_exhausted_cause) + url: query?query=sum%28increase%28temporal_cloud_v0_resource_exhausted_error_count%5B1m%5D%29%29%20by%20%28temporal_namespace%2Cresource_exhausted_cause%29 + split_array: true + leaf_array: true + - event_type: temporalCloudScheduleActionSuccess + # sum(increase(temporal_cloud_v0_schedule_action_success_count[1m])) by (temporal_namespace) + url: query?query=sum%28increase%28temporal_cloud_v0_schedule_action_success_count%5B1m%5D%29%29%20by%20%28temporal_namespace%29 + split_array: true + leaf_array: true + - event_type: temporalCloudScheduleBufferOverruns + # sum(increase(temporal_cloud_v0_schedule_buffer_overruns_count[1m])) by (temporal_namespace) + url: query?query=sum%28increase%28temporal_cloud_v0_schedule_buffer_overruns_count%5B1m%5D%29%29%20by%20%28temporal_namespace%29 + split_array: true + leaf_array: true + - event_type: temporalCloudScheduleMissedCatchupWindow + # sum(increase(temporal_cloud_v0_schedule_missed_catchup_window_count[1m])) by (temporal_namespace) + url: query?query=sum%28increase%28temporal_cloud_v0_schedule_missed_catchup_window_count%5B1m%5D%29%29%20by%20%28temporal_namespace%29 + split_array: true + leaf_array: true + - event_type: temporalCloudScheduleRateLimited + # sum(increase(temporal_cloud_v0_schedule_rate_limited_count[1m])) by (temporal_namespace) + url: query?query=sum%28increase%28temporal_cloud_v0_schedule_rate_limited_count%5B1m%5D%29%29%20by%20%28temporal_namespace%29 + split_array: true + leaf_array: true + - event_type: temporalCloudStateTransition + # sum(increase(temporal_cloud_v0_state_transition_count[1m])) by (temporal_namespace) + url: query?query=sum%28increase%28temporal_cloud_v0_state_transition_count%5B1m%5D%29%29%20by%20%28temporal_namespace%29 + split_array: true + leaf_array: true + - event_type: temporalCloudTotalAction + # sum(increase(temporal_cloud_v0_total_action_count[1m])) by (temporal_namespace, namespace_mode) + url: query?query=sum%28increase%28temporal_cloud_v0_total_action_count%5B1m%5D%29%29%20by%20%28temporal_namespace%2C%20namespace_mode%29 + split_array: true + leaf_array: true + - event_type: temporalCloudWorkflowCancel + # sum(increase(temporal_cloud_v0_workflow_cancel_count[1m])) by (temporal_namespace, operation) + url: query?query=sum%28increase%28temporal_cloud_v0_workflow_cancel_count%5B1m%5D%29%29%20by%20%28temporal_namespace%2C%20operation%29 + split_array: true + leaf_array: true + - event_type: temporalCloudWorkflowContinued + # sum(increase(temporal_cloud_v0_workflow_continued_as_new_count[1m])) by (temporal_namespace, operation) + url: query?query=sum%28increase%28temporal_cloud_v0_workflow_continued_as_new_count%5B1m%5D%29%29%20by%20%28temporal_namespace%2C%20operation%29 + split_array: true + leaf_array: true + - event_type: temporalCloudWorkflowFailed + # sum(increase(temporal_cloud_v0_workflow_failed_count[1m])) by (temporal_namespace, operation) + url: query?query=sum%28increase%28temporal_cloud_v0_workflow_failed_count%5B1m%5D%29%29%20by%20%28temporal_namespace%2C%20operation%29 + split_array: true + leaf_array: true + - event_type: temporalCloudWorkflowSuccess + # sum(increase(temporal_cloud_v0_workflow_success_count[1m])) by (temporal_namespace, operation) + url: query?query=sum%28increase%28temporal_cloud_v0_workflow_success_count%5B1m%5D%29%29%20by%20%28temporal_namespace%2C%20operation%29 + split_array: true + leaf_array: true + - event_type: temporalCloudWorkflowTerminate + # sum(increase(temporal_cloud_v0_workflow_terminate_count[1m])) by (temporal_namespace, operation) + url: query?query=sum%28increase%28temporal_cloud_v0_workflow_terminate_count%5B1m%5D%29%29%20by%20%28temporal_namespace%2C%20operation%29 + split_array: true + leaf_array: true + - event_type: temporalCloudWorkflowTimeout + # sum(increase(temporal_cloud_v0_workflow_timeout_count[1m])) by (temporal_namespace, operation) + url: query?query=sum%28increase%28temporal_cloud_v0_workflow_timeout_count%5B1m%5D%29%29%20by%20%28temporal_namespace%2C%20operation%29 + split_array: true + leaf_array: true + - event_type: temporalCloudWorkflowExecutionLatencySecP95 + # histogram_quantile(0.95, sum(rate(temporal_cloud_v0_service_latency_bucket[1m] offset 1m)) by (temporal_namespace, operation, le)) + url: query?query=histogram_quantile%280.95%2C%20sum%28rate%28temporal_cloud_v0_service_latency_bucket%5B1m%5D%20offset%201m%29%29%20by%20%28temporal_namespace%2C%20operation%2C%20le%29%29 + split_array: true + leaf_array: true + - event_type: temporalCloudReplicationLagSecP95 + # histogram_quantile(0.95, sum(rate(temporal_cloud_v0_replication_lag_bucket[1m] offset 1m)) by (temporal_namespace, le)) + url: query?query=histogram_quantile%280.95%2C%20sum%28rate%28temporal_cloud_v0_replication_lag_bucket%5B1m%5D%20offset%201m%29%29%20by%20%28temporal_namespace%2C%20le%29%29 + split_array: true + leaf_array: true ``` 3. Use nossas instruções [para reiniciar seu agente de infraestrutura](/docs/infrastructure/install-infrastructure-agent/manage-your-agent/start-stop-restart-infrastructure-agent/): diff --git a/src/i18n/content/pt/docs/logs/ui-data/parsing.mdx b/src/i18n/content/pt/docs/logs/ui-data/parsing.mdx index 1982cd07e53..fcc6c814528 100644 --- a/src/i18n/content/pt/docs/logs/ui-data/parsing.mdx +++ b/src/i18n/content/pt/docs/logs/ui-data/parsing.mdx @@ -306,6 +306,16 @@ Observe que os nomes das variáveis devem ser definidos explicitamente e estar e Localização geográfica de endereços IP. Consulte [Localização geográfica de endereços IP (GeoIP)](#geo) para obter mais informações. + + + + `key value pairs` + + + + valor principal Par . Veja [Análise de pares de valor principal](#parsing-key-value-pairs) para mais informações. + + @@ -490,6 +500,137 @@ Observe que os nomes das variáveis devem ser definidos explicitamente e estar e * **region**: Abreviatura de estado, província ou território * **regionName**: Nome do estado, província ou território + + + O pipeline do New Relic Logs analisa seu mensagem do log por padrão, mas às vezes você tem mensagem do log que são formatados como pares valor principal. Nessa situação, talvez você queira analisá-los e depois filtrar usando o atributo valor principal. + + Se for esse o caso, você pode usar o [tipo grok](#grok-syntax) `key value pairs` , que analisará os pares de valor principal capturados pelo padrão grok. Este formato depende de 3 partes principais: a sintaxe grok, o prefixo que você gostaria de atribuir ao atributo principal valor analisado e o [tipo grok](#grok-syntax) `key value pairs` . Usando o [tipo grok](#grok-syntax) `key value pairs` , você pode extrair e analisar pares valor principal de logs que não estão formatados corretamente; por exemplo, se seus logs forem prefixados com uma string de data/hora: + + ```json + 2015-05-13T23:39:43.945958Z key1=value1,key2=value2,key3=value3 + ``` + + Para extrair e analisar os dados principais do valor deste formato de log, crie a seguinte expressão Grok: + + ``` + %{TIMESTAMP_ISO8601:containerTimestamp} %{GREEDYDATA:my_attribute_prefix:keyvalue()} + ``` + + O log resultante é: + + ``` + containerTimestamp: "2015-05-13T23:39:43.945958Z" + my_attribute_prefix.key1: "value1" + my_attribute_prefix.key2: "value2" + my_attribute_prefix.key3: "value3" + ``` + + Você também pode definir o delimitador e o separador personalizados para extrair os pares de valor principal necessários. + + ```json + 2015-05-13T23:39:43.945958Z event:TestRequest request:bar + ``` + + Por exemplo, com a seguinte expressão Grok: + + ``` + %{TIMESTAMP_ISO8601:containerTimestamp} %{GREEDYDATA:my_attribute_prefix:keyvalue({"delimiter": " ", "keyValueSeparator": ":"})} + ``` + + O log resultante é: + + ``` + containerTimestamp: "2015-05-13T23:39:43.945958Z" + my_attribute_prefix.event: "TestRequest" + my_attribute_prefix.request: "bar" + ``` + + Se quiser omitir o prefixo `my_attribute_prefix` , você poderá incluir `"noPrefix": true` na configuração. + + ``` + %{TIMESTAMP_ISO8601:containerTimestamp} %{GREEDYDATA:my_attribute_prefix:keyValue({"noPrefix": true})} + ``` + + O log resultante é: + + ``` + containerTimestamp: "2015-05-13T23:39:43.945958Z" + event: "TestRequest" + request: "bar" + ``` + + Se você quiser definir seu prefixo de caractere de aspas personalizado, você pode incluir "quoteChar": na configuração. + + ```json + 2015-05-13T23:39:43.945958Z nbn_demo='INFO',message='This message contains information with spaces ,sessionId='abc123' + ``` + + ``` + %{TIMESTAMP_ISO8601:containerTimestamp} %{GREEDYDATA:my_attribute_prefix:keyValue({"quoteChar": "'"})} + ``` + + O log resultante é: + + ``` + "my_attribute_prefix.message": "'This message contains information with spaces", + "my_attribute_prefix.nbn_demo": "INFO", + "my_attribute_prefix.sessionId": "abc123" + ``` + + ### Parâmetro Grok Pattern + + Você pode personalizar o comportamento de análise com as seguintes opções para se adequar aos seus formatos de log: + + * **delimitador** + + * **Descrição:** String separando cada par de valor principal. + + * **Valor padrão:** `,` (vírgula) + + * **Substituir:** Defina o campo `delimiter` para alterar esse comportamento. + + * **Separador de Valor-chave** + + * **Descrição:** String usada para atribuir valores às chaves. + * **Valor padrão:** `=` + * **Substituir:** Defina o campo `keyValueSeparator` para uso de separador personalizado. + + * **citaçãoChar** + + * **Descrição:** Caractere usado para delimitar valores com espaços ou caracteres especiais. + * **Valor padrão:** `"` (aspas duplas) + * **Substituir:** Defina um caractere personalizado usando `quoteChar`. + + * **soltarOriginal** + + * **Descrição:** Descarta a mensagem original do log após a análise. Útil para reduzir o armazenamento de logs. + * **Valor padrão:** `true` + * **Substituir:** defina `dropOriginal` como `false` para manter a mensagem original do log. + + * **sem prefixo** + + * **Descrição:** Quando `true`, exclui o nome do campo Grok como um prefixo no objeto resultante. + * **Valor padrão:** `false` + * **Substituição:** Habilite definindo `noPrefix` como `true`. + + * **escapeChar** + + * **Descrição:** Defina um caractere de escape personalizado para manipular caracteres de log especiais. + * **Valor padrão:** &quot;&quot; (barra invertida) + * **Substituir:** personalizar com `escapeChar`. + + * **valores de trim** + + * **Descrição:** Permite o corte de valores que contêm espaços em branco. + * **Valor padrão:** `false` + * **Substituir:** defina `trimValues` como `true` para ativar o corte. + + * **Teclas de ajuste** + + * **Descrição:** Permite o corte de teclas que contêm espaços em branco. + * **Valor padrão:** `true` + * **Substituir:** defina `trimKeys` como `true` para ativar o corte. + ## Organizando por tipo de log [#type] diff --git a/src/i18n/content/pt/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/test-crash-reporting.mdx b/src/i18n/content/pt/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/test-crash-reporting.mdx index 3bef74e559c..4222aa1cb92 100644 --- a/src/i18n/content/pt/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/test-crash-reporting.mdx +++ b/src/i18n/content/pt/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/test-crash-reporting.mdx @@ -37,6 +37,10 @@ translationType: machine React Native + + Flutter + + Unidade @@ -250,6 +254,62 @@ translationType: machine ``` + + ## Sintaxe [#syntax] + + ```dart + crashNow({String name}) : void ; + ``` + + ## Descrição [#description] + + Lança uma exceção de tempo de execução de demonstração no Android/iOS para testar o relatório de falhas do New Relic. + + ## Parâmetro [#parameters] + + + + + + + + + + + + + + + + + + + + + +
+ Parâmetro + + Tipo + + Descrição +
+ `name` + + `string` + + Opcional. Uma mensagem anexada à exceção. +
+ + ## Exemplo [#example] + + ```dart + NewrelicMobile.instance.crashNow(name: "This is a crash"); + NewrelicMobile.instance.crashNow(); + + ``` + + ## Sintaxe [#syntax] diff --git a/src/i18n/content/pt/docs/new-relic-solutions/observability-maturity/uptime-performance-reliability/diagnostics-beginner-guide.mdx b/src/i18n/content/pt/docs/new-relic-solutions/observability-maturity/uptime-performance-reliability/diagnostics-beginner-guide.mdx index 05ad8cb8713..8efb9fa3382 100644 --- a/src/i18n/content/pt/docs/new-relic-solutions/observability-maturity/uptime-performance-reliability/diagnostics-beginner-guide.mdx +++ b/src/i18n/content/pt/docs/new-relic-solutions/observability-maturity/uptime-performance-reliability/diagnostics-beginner-guide.mdx @@ -251,7 +251,67 @@ As fontes dos problemas são organizadas de acordo com sua frequência, sendo as Esta tabela é uma matriz de problemas classificada por ponto de dados de saúde: -| Ponto de dados | Capacidade New Relic | Fontes comuns de problemas | | ---------- | --------------------- | ----------------------------------------------------------------------------------------------------------------------- | | Saída | APM, infra, log, NPM | aplicativo, fontes de dados, alteração de configuração de hardware, infraestrutura, rede interna, provedor terceirizado (AWS, GCP) | | Entrada | Sintético, log | Roteamento externo (CDN, gateways, etc.), roteamento interno, coisas na internet (ISP, etc.) | | Cliente | navegador, celular | código do navegador ou celular | + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Ponto de dados + + Capacidade New Relic + + Fontes de problemas comuns +
+ Saída + + APM, infra, log, NPM + + Aplicativo, fontes de dados, alteração de configuração de hardware, infraestrutura, rede interna, provedor terceirizado (AWS, GCP) +
+ Entrada + + Sintético, registro + + Roteamento externo (CDN, gateways, etc.), roteamento interno, coisas na internet (ISP, etc.) +
+ Cliente + + Browser, mobile + + Código do Browser ou mobile +
Os problemas tendem a ser agravados, mas o objetivo é “encontrar a fonte” e então determinar “o que mudou” para restaurar rapidamente o nível de serviço. 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 3e37010ccbc..9d139fd51a0 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 @@ -17,8 +17,6 @@ Antes de habilitar o monitoramento Serverless usando nossa camada Lambda, você 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. -/\* Então você precisará concluir o seguinte: 1. Instalar \[AWS CLI v2]\(https://docs.aws.amazon.com/cli/latest/userguide/install-cliv2.html) configurar usando \`AWS configure\`. Você precisará de um AWS Access Key ID e AWS Secret Access Key. 2. Instale \[Python]\(https://www.python.org/downloads/) versão 3.3 ou superior. 3. Instale o \[\`newrelic-lambda\` CLI]\(https://github.com/newrelic/newrelic-lambda-cli#installation). Para instalá-lo, execute este comando: \`\`\`bash pip3 install newrelic-lambda-cli \`\`\` 4. Por padrão, usamos a política gerenciada da AWS \`ReadOnlyAccess\`. Isso permite que a infraestrutura de integração veja todos os recursos em sua conta, em vez de apenas sua função do Lambda e métricas do CloudWatch. A New Relic recomenda esse padrão, mas entendemos que algumas organizações preferem uma postura de segurança rigorosa para integração de terceiros. Se você quiser limitar o acesso do New Relic, a função do IAM pode ser concedida com um mínimo destas permissões: \`\`\`yaml Resource: "\*" Action: - "cloudwatch:GetMetricStatistics" - "cloudwatch:ListMetrics" - "cloudwatch:GetMetricData" - "lambda:GetAccountSettings" - "lambda:ListFunctions" - "lambda:ListAliases" - "lambda:ListTags" - "lambda:ListEventSourceMappings" \`\`\` 5. Antes de executar a CLI, você precisará conceder ao New Relic um mínimo destas permissões na AWS: \`\`\`json \{ "Version": "2012-10-17", "Statement": \[ \{ "Sid": "CLIAccessPolicy", "Action": \[ "cloudformation:CreateChangeSet", "cloudformation:CreateStack", "cloudformation:DescribeStacks", "cloudformation:ExecuteChangeSet", "iam:AttachRolePolicy", "iam:CreateRole", "iam:GetRole", "iam:PassRole", "lambda:AddPermission", "lambda:CreateFunction", "lambda:GetFunction", "logs:DeleteSubscriptionFilter", "logs:DescribeSubscriptionFilters", "logs:PutSubscriptionFilter", "s3:GetObject", "serverlessrepo:CreateCloudFormationChangeSet", "secretsmanager:CreateSecret" ], "Efeito": "Permitir", "Recurso": "\*" }, \{ "Sid": "NRLogAccessPolicy", "Efeito": "Permitir", "Ação": \[ "serverlessrepo:CreateCloudFormationTemplate", "serverlessrepo:GetCloudFormationTemplate" ], "Recurso": "arn:AWS:serverlessrepo:us-east-1:463657938898:aplicativo/NewRelic-log-ingestion" } ] } \`\`\` Se quiser saber mais sobre nossa CLI, consulte \[nosso repositório de CLI]\(https://github.com/newrelic/newrelic-lambda-cli#installation). \*/ - ## Tempos de execução suportados Com base no tipo de instrumentação, os seguintes tempos de execução são suportados. 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 6b0771c42fe..d0cba0faccd 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 @@ -193,12 +193,12 @@ Aqui está um guia para adicionar nossa camada pré-construída ao seu código. ### Configure sua função do Lambda - 2. Configure a função do Lambda com as mesmas configurações da função original, mas certifique-se de adicionar quaisquer variáveis de ambiente necessárias para o monitoramento do New Relic Lambda. Consulte nossas [variáveis de ambiente](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/configure-serverless-monitoring-aws-lambda/#environment) para obter mais informações. + 2. Configure a função do Lambda com as mesmas configurações da sua função original, mas certifique-se de adicionar quaisquer variáveis de ambiente necessárias para o monitoramento do New Relic Lambda . Veja nossas [Variáveis de ambiente](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/env-variables-lambda) para mais informações. 3. Atualize o manipulador da sua função para apontar para a camada recém-anexada na substituição `cmd` da sua função. Você pode fazer isso usando as instruções nestes dois documentos: - * [Configuração da interface do console Lambda](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/instrument-your-own/#console) - * [Instrumentação sem camadas para monitoramento Lambda](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/enable-serverless-monitoring-aws-lambda-layerless) + * [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) 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 f11670f4d8f..787cd07eebd 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 @@ -149,9 +149,7 @@ Com base no seu tempo de execução, você pode definir as seguintes variáveis - Desabilite distributed tracing configurando isso para - - `false` + Gerar rastreamento habilitando o rastreamento distribuído @@ -349,9 +347,7 @@ Com base no seu tempo de execução, você pode definir as seguintes variáveis - Desabilite distributed tracing configurando isso para - - `false` + Gerar rastreamento habilitando o rastreamento distribuído @@ -543,9 +539,7 @@ Com base no seu tempo de execução, você pode definir as seguintes variáveis - Desabilite distributed tracing configurando isso para - - `false` + Gerar rastreamento habilitando o rastreamento distribuído @@ -631,9 +625,7 @@ Com base no seu tempo de execução, você pode definir as seguintes variáveis - Desabilite distributed tracing configurando isso para - - `false` + Gerar rastreamento habilitando o rastreamento distribuído @@ -681,9 +673,7 @@ Com base no seu tempo de execução, você pode definir as seguintes variáveis - Desabilite distributed tracing configurando isso para - - `false` + Gerar rastreamento habilitando o rastreamento distribuído @@ -823,9 +813,7 @@ Com base no seu tempo de execução, você pode definir as seguintes variáveis - Desabilite distributed tracing configurando isso para - - `false` + Gerar rastreamento habilitando o rastreamento distribuído diff --git a/src/i18n/content/pt/docs/serverless-function-monitoring/azure-function-monitoring/compatibility-requirement-azure-monitoring.mdx b/src/i18n/content/pt/docs/serverless-function-monitoring/azure-function-monitoring/compatibility-requirement-azure-monitoring.mdx new file mode 100644 index 00000000000..df2ca107f5c --- /dev/null +++ b/src/i18n/content/pt/docs/serverless-function-monitoring/azure-function-monitoring/compatibility-requirement-azure-monitoring.mdx @@ -0,0 +1,54 @@ +--- +title: Compatibilidade e requisitos para instrumentado Azure Functions +metaDescription: Azure function monitoring agent compatibility and requirements. +freshnessValidatedDate: never +translationType: machine +--- + +Antes de [instrumentar Azure Functions](/docs/serverless-function-monitoring/aws-lambda-monitoring/instrument-lambda-function/configure-serverless-aws-monitoring), certifique-se de que seu sistema atende aos seguintes requisitos. + +## Requisitos básicos [#requirements] + +* Azure Functions hospedado em [plano de consumo](https://learn.microsoft.com/en-us/azure/azure-functions/consumption-plan) ou [plano dedicado](https://learn.microsoft.com/en-us/azure/azure-functions/dedicated-plan). + +* Você deve ter a [permissão necessária para acessar o serviço kudu](https://learn.microsoft.com/en-us/azure/app-service/resources-kudu#access-kudu-for-your-app). + +* Uma conta do New Relic com [função de administrador](/docs/accounts/original-accounts-billing/original-users-roles/users-roles-original-user-model/#roles) ou de [gerente de infraestrutura](/docs/accounts/original-accounts-billing/original-users-roles/users-roles-original-user-model#add-on). + +* Um . + +* Agente .NET versão 10.30 ou superior. + + + distributed tracing de ponta a ponta é suportado apenas para solicitações HTTP. Além disso, o rastreamento de chamadas para serviços externos, como banco de dados e Service Bus, ainda está disponível. + + +## Tempos de execução suportados + +Com base no seu ambiente de hospedagem, os seguintes tempos de execução são suportados. + + + + Funções em contêiner Linux Windows + + + + + * .NET: `dotnet6.0`, `dotnet8.0` + + + + * .NET: `dotnet6.0`, `dotnet8.0` + + + + * .NET: `dotnet6.0`, `dotnet8.0` + + + + +## Qual é o próximo + + + Comece com instrumentação e configuração para seu Azure Functions + \ No newline at end of file diff --git a/src/i18n/content/pt/docs/serverless-function-monitoring/azure-function-monitoring/env-variables-azure.mdx b/src/i18n/content/pt/docs/serverless-function-monitoring/azure-function-monitoring/env-variables-azure.mdx new file mode 100644 index 00000000000..deed8d11fb3 --- /dev/null +++ b/src/i18n/content/pt/docs/serverless-function-monitoring/azure-function-monitoring/env-variables-azure.mdx @@ -0,0 +1,221 @@ +--- +title: Variáveis de ambiente para monitoramento Azure Functions +metaDescription: Configure environment variables to monitor your Azure functions with New Relic +freshnessValidatedDate: never +tags: + - AWS Lambda + - Environment Variables + - Configuration + - Secrets Management +translationType: machine +--- + +Variáveis de ambiente são uma maneira de armazenar configurações e segredos fora do seu código. As tabelas a seguir exibem as variáveis obrigatórias e as variáveis específicas do tempo de execução que você pode definir para monitorar suas Funções Azure com o New Relic. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Variável de ambiente + + Valor padrão + + Opções + + Descrição +
+ `CORECLR_ENABLE_PROFILING` + + `0` + + `0` + + , + + `1` + + **Obrigatório** + + . Habilite a criação de perfil definindo isso como + + `1` + + . +
+ `CORECLR_PROFILER` + + + + + + **Obrigatório** + + . Defina isso para habilitar o agente .NET. +
+ `CORECLR_NEWRELIC_HOME` + + + + + + **Obrigatório** + + . Defina isso para habilitar o agente .NET. +
+ `CORECLR_PROFILER_PATH` + + + + + + **Obrigatório** + + . Defina isso para habilitar o agente .NET. +
+ `NEW_RELIC_DISTRIBUTED_TRACING_ENABLED` + + `true` + + `true` + + , + + `false` + + Gere rastreamento habilitando distributed tracing. +
+ `NEW_RELIC_APP_NAME` + + + + + + Defina o nome do aplicativo, embora ele não seja usado na interface do usuário do New Relic. +
+ `NEW_RELIC_AZURE_FUNCTION_MODE_ENABLED` + + `1` + + `1` + + , + + `0` + + Desabilite o modo Azure Functions definindo o valor como + + `0` + + . +
+ `NEW_RELIC_LOG_DIRECTORY` + + + + + + Modifique o local onde você deseja armazenar os logs do agente e do profiler. +
+ `NEW_RELIC_LOG_LEVEL` + + `info` + + `info` + + , + + `debug` + + , + + `finest` + + Defina o nível de log do agente. +
+ +## Qual é o próximo + + + Comece com instrumentação e configuração para seu Azure Functions + \ No newline at end of file diff --git a/src/i18n/content/pt/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx b/src/i18n/content/pt/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx new file mode 100644 index 00000000000..54f8adc5a0f --- /dev/null +++ b/src/i18n/content/pt/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx @@ -0,0 +1,242 @@ +--- +title: Instalar e configurar o monitoramento do Azure Functions no New Relic +metaDescription: Configure your Azure Functions with New Relic +freshnessValidatedDate: never +translationType: machine +--- + +## Antes de você começar [#begin] + +Certifique-se de que suas Azure Functions atendem à nossa [compatibilidade e aos nossos requisitos](/docs/serverless-function-monitoring/azure-function-monitoring/compatibility-requirement-azure-monitoring). + + + + ## Vincule sua conta do Azure ao New Relic + + Você pode vincular sua conta Azure ao New Relic configurando a sondagem do Azure Monitor Métrica. Isso permite que você veja a métrica na interface do New Relic. Para obter mais informações, consulte [integraçãoAzure ](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-functions-monitoring-integration/#polling). + + + + ## Instrumente seu Azure Functions com o agente New Relic .NET + + Com base em suas necessidades, selecione uma das seguintes opções para instrumentar seu Azure Functions com o agente .NET do New Relic. + + + + Funções em contêiner Linux Windows + + + + + 1. Adicione o pacote NuGet `NewRelic.Agent` ao seu projeto de aplicativo. + + * No editor de código do Visual Studio, use o gerenciador de pacotes NuGet para procurar e adicionar a versão mais recente do `NewRelic.Agent` ao seu aplicativo. + * Se estiver usando outros ambientes de desenvolvimento, você pode adicionar o pacote com `dotnet add packages NewRelic.Agent`. + + 2. Use seu mecanismo de publicação preferido para implantar seu aplicativo atualizado no Azure. Isso inclui o agente New Relic, que é instalado na pasta `/home/site/www/newrelic` . + + + + Navegue até a página do serviço Kudu e faça o seguinte: + + 1. No portal do Azure, navegue até seu aplicativo de funções. + 2. Clique na seção **Development tools** e selecione **Advanced Tools > Go**. + 3. Para visualizar as extensões de site disponíveis, clique na aba **Site extensions** . + 4. Para instalar a extensão, procure por `New Relic .NET Agent` e clique em **+**. + + + + Para instalar o agente New Relic .NET, no estágio final do seu Dockerfile, adicione as seguintes linhas: + + ```dockerfile + # install the latest New Relic .NET agent using the apt-get package manager + RUN apt-get update && apt-get install -y wget ca-certificates gnupg \ + && echo 'deb http://apt.newrelic.com/debian/ newrelic non-free' | tee /etc/apt/sources.list.d/newrelic.list \ + && wget https://download.newrelic.com/548C16BF.gpg \ + && apt-key add 548C16BF.gpg \ + && apt-get update \ + && apt-get install -y newrelic-dotnet-agent \ + && rm -rf /var/lib/apt/lists/* + + ``` + + + + + + + ## Configurar as variáveis de ambiente + + Depois de instrumentar seu Azure Functions com o agente .NET do New Relic, faça o seguinte para configurar as [variáveis de ambiente](/docs/serverless-function-monitoring/azure-function-monitoring/env-variables-azure) para enviar os dados ao New Relic. + + 1. Navegue até suas Azure Functions no portal Azure , em **Settings**, clique em **Environment variables** e, em seguida, clique em **Advanced edit**. + + 2. Com base nos requisitos do seu aplicativo, cole os seguintes valores. + + + Certifique-se de adicionar uma vírgula no final da última linha existente e atualizar sua chave de licença e o nome do aplicativo na seguinte configuração. + + + + + Funções em contêiner Linux Windows + + + + + ```json + { + "name": "CORECLR_ENABLE_PROFILING", + "value": "1", + "slotSetting": false + }, + { + "name": "CORECLR_NEWRELIC_HOME", + "value": "/home/site/wwwroot/newrelic", + "slotSetting": false + }, + { + "name": "CORECLR_PROFILER", + "value": "{36032161-FFC0-4B61-B559-F6C5D41BAE5A}", + "slotSetting": false + }, + { + "name": "CORECLR_PROFILER_PATH", + "value": "/home/site/wwwroot/newrelic/libNewRelicProfiler.so", + "slotSetting": false + }, + { + "name": "NEW_RELIC_AZURE_FUNCTION_MODE_ENABLED", + "value": "1", + "slotSetting": false + }, + { + "name": "NEW_RELIC_LICENSE_KEY", + "value": "", + "slotSetting": false + }, + { + "name": "NEWRELIC_LOG_DIRECTORY", + "value": "/home/LogFiles/NewRelic", + "slotSetting": false + }, + { + "name": "NEWRELIC_LOG_LEVEL", + "value": "info", + "slotSetting": false + }, + + + ``` + + + + ```json + { + "name": "CORECLR_PROFILER_PATH", + "value": "C:\\home\\NewRelicAgent\\Core\\NewRelic.Profiler.dll", + "slotSetting": false + }, + { + "name": "CORECLR_NEWRELIC_HOME", + "value": "C:\\home\\NewRelicAgent\\Core", + "slotSetting": false + }, + { + "name": "NEWRELIC_LOG_DIRECTORY", + "value": "C:\\home\\LogFiles\\NewRelic", + "slotSetting": false + }, + { + "name": "NEW_RELIC_AZURE_FUNCTION_MODE_ENABLED", + "value": "1", + "slotSetting": false + }, + { + "name": "CORECLR_ENABLE_PROFILING", + "value": "1", + "slotSetting": false + }, + { + "name": "CORECLR_PROFILER", + "value": "{36032161-FFC0-4B61-B559-F6C5D41BAE5A}", + "slotSetting": false + }, + { + "name": "NEW_RELIC_LICENSE_KEY", + "value": "", + "slotSetting": false + }, + { + "name": "NEWRELIC_LOG_LEVEL", + "value": "info", + "slotSetting": false + }, + { + "name": "NEW_RELIC_APP_NAME", + "value": "", + "slotSetting": false + }, + + ``` + + + + ```json + { + "name": "CORECLR_ENABLE_PROFILING", + "value": "1", + "slotSetting": false + }, + { + "name": "CORECLR_NEWRELIC_HOME", + "value": "/usr/local/newrelic-dotnet-agent", + "slotSetting": false + }, + { + "name": "CORECLR_PROFILER", + "value": "{36032161-FFC0-4B61-B559-F6C5D41BAE5A}", + "slotSetting": false + }, + { + "name": "CORECLR_PROFILER_PATH", + "value": "/usr/local/newrelic-dotnet-agent/libNewRelicProfiler.so", + "slotSetting": false + }, + { + "name": "NEW_RELIC_AZURE_FUNCTION_MODE_ENABLED", + "value": "1", + "slotSetting": false + }, + { + "name": "NEW_RELIC_LICENSE_KEY", + "value": "", + "slotSetting": false + }, + { + "name": "NEWRELIC_LOG_DIRECTORY", + "value": "/home/LogFiles/NewRelic", + "slotSetting": false + }, + { + "name": "NEWRELIC_LOG_LEVEL", + "value": "info", + "slotSetting": false + }, + + ``` + + + + + + + ## Reinicie suas Azure Functions + + Depois de adicionar as variáveis de ambiente, reinicie o Azure Functions para aplicar as alterações. + + + +## Qual é o próximo + +Após concluir as etapas de instalação e configuração, envie tráfego para o Azure Functions para ver a métrica no dashboard da interface do New Relic. \ No newline at end of file diff --git a/src/i18n/content/pt/docs/serverless-function-monitoring/azure-function-monitoring/introduction-azure-monitoring.mdx b/src/i18n/content/pt/docs/serverless-function-monitoring/azure-function-monitoring/introduction-azure-monitoring.mdx new file mode 100644 index 00000000000..43468bd998a --- /dev/null +++ b/src/i18n/content/pt/docs/serverless-function-monitoring/azure-function-monitoring/introduction-azure-monitoring.mdx @@ -0,0 +1,20 @@ +--- +title: Introdução ao monitoramento do Azure Functions +metaDescription: This provides an overview of New Relic's AWS Lambda monitoring and details how to link your accounts. +freshnessValidatedDate: never +translationType: machine +--- + +A instrumentação do New Relic para o Azure Functions oferece visibilidade profunda do funcionamento interno das 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ção, monitore erros, veja distributed tracing e registre detalhes sobre o evento de origem e as respostas da sua função. + + + Para Azure Functions, o agente relata dados como rastreamento e logs distribuídos, que estão disponíveis em 'Serviços - APM ' como uma entidade APM . No entanto, ainda existe uma entidade separada (fornecida pelo monitoramento de infraestrutura) para o Azure Functions. + + +new-relic-azure-function-monitoring.gif + +## Qual é o próximo + + + Saiba mais sobre os tempos de execução suportados e pré-requisitos Comece com instrumentação e configuração para suas Azure Functions + \ No newline at end of file diff --git a/src/i18n/content/pt/docs/serverless-function-monitoring/overview.mdx b/src/i18n/content/pt/docs/serverless-function-monitoring/overview.mdx index 6b4282f7a73..587a9986517 100644 --- a/src/i18n/content/pt/docs/serverless-function-monitoring/overview.mdx +++ b/src/i18n/content/pt/docs/serverless-function-monitoring/overview.mdx @@ -1,12 +1,12 @@ --- -title: Função de monitoramento serverless +title: Monitoramento Serverless freshnessValidatedDate: never translationType: machine --- -Funções serverless são uma maneira de executar código na nuvem sem se preocupar em gerenciar servidores. Em vez de configurar e manter servidores, o provedor de nuvem cuida de tudo para você. Isso significa que os desenvolvedores podem se concentrar em escrever código que responda a eventos específicos, como um usuário clicando em um botão, sem lidar com os detalhes técnicos do gerenciamento do servidor. Ao aproveitar os recursos de monitoramento sem servidor da New Relic, a organização pode aumentar sua eficiência operacional, melhorar o desempenho do aplicativo e garantir uma experiência de usuário perfeita. +Funções serverless são uma maneira de executar código na nuvem sem se preocupar em gerenciar servidores. Em vez de configurar e manter servidores, o provedor de nuvem cuida de tudo para você. Isso significa que os desenvolvedores podem se concentrar em escrever código que responda a eventos específicos, como um usuário clicando em um botão, sem lidar com os detalhes técnicos do gerenciamento do servidor. Ao aproveitar os recursos de monitoramento sem servidor da New Relic, a organização pode aumentar sua eficiência operacional, melhorar o desempenho do aplicativo e garantir uma experiência perfeita para o usuário. -A seguir estão alguns dos principais benefícios de usar o New Relic para monitoramento sem servidor: +A seguir estão alguns dos principais benefícios de usar o New Relic para monitoramento Serverless: * **Monitoramento unificado:** visualize todas as suas funções serverless em um único dashboard, independente do provedor de nuvem, simplificando o gerenciamento e o monitoramento das funções em diferentes ambientes @@ -21,7 +21,7 @@ Selecione o provedor de nuvem que você está usando para saber mais sobre como - + \ No newline at end of file diff --git a/src/i18n/content/pt/docs/service-level-management/create-slm.mdx b/src/i18n/content/pt/docs/service-level-management/create-slm.mdx index 1a4755f02fb..9846247b6c6 100644 --- a/src/i18n/content/pt/docs/service-level-management/create-slm.mdx +++ b/src/i18n/content/pt/docs/service-level-management/create-slm.mdx @@ -129,7 +129,8 @@ Com base no evento `Transaction` , estes SLIs são os mais comuns para serviços Para selecionar um valor apropriado para a condição de duração, uma prática típica é selecionar a duração do percentil 95 das respostas dos últimos 7 ou 15 dias. Encontre esse limite de duração usando o [criador de consulta](/docs/query-your-data/explore-query-data/query-builder/introduction-query-builder/) e use-o para determinar o que você considera um bom evento para o seu SLI: ```sql - SELECT percentile(duration, 95) FROM Transaction WHERE entityGuid = '{entityGuid}' SINCE 7 days ago LIMIT MAX + SELECT percentile(duration, 95) FROM Transaction + WHERE entityGuid = '{entityGuid}' SINCE 7 days ago LIMIT MAX ``` @@ -171,7 +172,8 @@ Com base em extensões OpenTelemetry, estes SLIs são os mais comuns para servi ```sql FROM Span - WHERE entity.guid = '{entityGuid}' AND (span.kind IN ('server', 'consumer') OR kind IN ('server', 'consumer')) + WHERE entity.guid = '{entityGuid}' AND (span.kind IN ('server', 'consumer') + OR kind IN ('server', 'consumer')) ``` Onde `{entityGuid}` é o GUID do serviço. @@ -182,7 +184,8 @@ Com base em extensões OpenTelemetry, estes SLIs são os mais comuns para servi ```sql FROM Span - WHERE entity.guid = '{entityGuid}' AND (span.kind IN ('server', 'consumer') OR kind IN ('server', 'consumer')) AND otel.status_code = 'ERROR' + WHERE entity.guid = '{entityGuid}' AND (span.kind IN ('server', 'consumer') + OR kind IN ('server', 'consumer')) AND otel.status_code = 'ERROR' ``` Onde `{entityGuid}` é o GUID do serviço. @@ -196,7 +199,9 @@ Com base em extensões OpenTelemetry, estes SLIs são os mais comuns para servi Para selecionar um valor apropriado para a condição de duração, uma prática típica é selecionar a duração do percentil 95 das respostas dos últimos 7 ou 15 dias. Encontre esse limite de duração usando o [criador de consulta](/docs/query-your-data/explore-query-data/query-builder/introduction-query-builder/) e use-o para determinar o que você considera um bom evento para o seu SLI: ```sql - SELECT percentile(duration.ms, 95) FROM Span WHERE entityGuid = '{entityGuid}' AND (span.kind IN ('server', 'consumer') OR kind IN ('server', 'consumer')) SINCE 7 days ago LIMIT MAX + SELECT percentile(duration.ms, 95) FROM Span + WHERE entityGuid = '{entityGuid}' AND (span.kind IN ('server', 'consumer') + OR kind IN ('server', 'consumer')) SINCE 7 days ago LIMIT MAX ``` @@ -205,7 +210,8 @@ Com base em extensões OpenTelemetry, estes SLIs são os mais comuns para servi ```sql FROM Span - WHERE entity.guid = '{entityGuid}' AND (span.kind IN ('server', 'consumer') OR kind IN ('server', 'consumer')) + WHERE entity.guid = '{entityGuid}' AND (span.kind IN ('server', 'consumer') + OR kind IN ('server', 'consumer')) ``` Onde `{entityGuid}` é o GUID do serviço. @@ -216,7 +222,8 @@ Com base em extensões OpenTelemetry, estes SLIs são os mais comuns para servi ```sql FROM Span - WHERE entity.guid = '{entityGuid}' AND (span.kind IN ('server', 'consumer') OR kind IN ('server', 'consumer')) AND duration.ms < {duration} + WHERE entity.guid = '{entityGuid}' AND (span.kind IN ('server', 'consumer') + OR kind IN ('server', 'consumer')) AND duration.ms < {duration} ``` * Onde `{entityGuid}` é o GUID do serviço. @@ -407,8 +414,8 @@ Os SLIs a seguir são baseados nos core web vitals do browser do Google. Se desejar criar SLIs separados para rastrear CLS em desktops e dispositivos móveis separadamente, adicione uma destas cláusulas no final do campo: - * `and deviceType = 'Mobile'` - * `and deviceType = 'Desktop'` + * `AND deviceType = 'Mobile'` + * `AND deviceType = 'Desktop'` **Good events fields** @@ -425,14 +432,14 @@ Os SLIs a seguir são baseados nos core web vitals do browser do Google. Se você decidiu criar SLIs separados para rastrear CLS em desktops e dispositivos móveis separadamente quando definiu a consulta de evento válida, adicione esta cláusula no final do campo: - * `and deviceType = 'Mobile'` - * `and deviceType = 'Desktop'` + * `AND deviceType = 'Mobile'` + * `AND deviceType = 'Desktop'` Para determinar um número realista a ser selecionado para `{cumulativeLayoutShift}` em seu ambiente, uma prática típica é selecionar o 75º percentil de carregamentos de página nos últimos 7 ou 15 dias, segmentados em dispositivos móveis e desktop. Encontre-o usando o criador de consulta: ```sql SELECT percentile(cumulativeLayoutShift, 95) FROM PageViewTiming - WHERE entityGuid = '{entityGuid}' since 7 days ago limit max facet deviceType + WHERE entityGuid = '{entityGuid}' SINCE 7 days ago LIMIT MAX FACET deviceType ``` @@ -562,10 +569,10 @@ Para criar nível de serviço, siga estes passos: ```sql FROM Metric - SELECT getField(`newrelic.goldenmetrics.synth.monitor.medianDurationS`, count) as 'Valid' + SELECT getField(`newrelic.goldenmetrics.synth.monitor.medianDurationS`, count) AS 'Valid' FROM Metric - SELECT getCdfCount(`newrelic.goldenmetrics.synth.monitor.medianDurationS`, 0.5) as 'Good' + SELECT getCdfCount(`newrelic.goldenmetrics.synth.monitor.medianDurationS`, 0.5) AS 'Good' ``` Você também pode usar curingas em sua consulta SLI, veja um exemplo: From 162b002a68c9f494eadc3f480d94e772daf77ff3 Mon Sep 17 00:00:00 2001 From: Gaurab Manandhar Date: Tue, 14 Jan 2025 12:25:01 +0530 Subject: [PATCH 2/2] fix: verify-mdx fix --- .../install-serverless-azure-monitoring.mdx | 2 -- .../install-serverless-azure-monitoring.mdx | 2 -- .../install-serverless-azure-monitoring.mdx | 2 -- .../install-serverless-azure-monitoring.mdx | 2 -- 4 files changed, 8 deletions(-) diff --git a/src/i18n/content/es/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx b/src/i18n/content/es/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx index de2f5935e33..4bf021714a1 100644 --- a/src/i18n/content/es/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx +++ b/src/i18n/content/es/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx @@ -125,8 +125,6 @@ Cerciorar de que sus Azure Functions cumplan con nuestros [requisitos y compatib "value": "info", "slotSetting": false }, - - ``` diff --git a/src/i18n/content/jp/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx b/src/i18n/content/jp/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx index ca5f255b16e..d9c3824dbb5 100644 --- a/src/i18n/content/jp/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx +++ b/src/i18n/content/jp/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx @@ -125,8 +125,6 @@ Azure Functions が[互換性と要件を](/docs/serverless-function-monitoring/ "value": "info", "slotSetting": false }, - - ``` diff --git a/src/i18n/content/kr/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx b/src/i18n/content/kr/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx index 19f13f56c37..a2784fdb09f 100644 --- a/src/i18n/content/kr/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx +++ b/src/i18n/content/kr/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx @@ -125,8 +125,6 @@ Azure Functions가 [호환성 및 요구 사항을](/docs/serverless-function-mo "value": "info", "slotSetting": false }, - - ``` diff --git a/src/i18n/content/pt/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx b/src/i18n/content/pt/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx index 54f8adc5a0f..17ea7ba4e98 100644 --- a/src/i18n/content/pt/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx +++ b/src/i18n/content/pt/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx @@ -125,8 +125,6 @@ Certifique-se de que suas Azure Functions atendem à nossa [compatibilidade e ao "value": "info", "slotSetting": false }, - - ```