diff --git a/package.json b/package.json index de314d3892d..47b91504eed 100644 --- a/package.json +++ b/package.json @@ -238,5 +238,6 @@ }, "bugs": { "url": "https://github.com/newrelic/docs-website/issues" - } + }, + "packageManager": "yarn@1.22.22+sha512.a6b2f7906b721bba3d67d4aff083df04dad64c399707841b7acf00f6b133b7ac24255f2652fa22ae3534329dc6180534e98d17432037ff6fd140556e2bb3137e" } diff --git a/src/i18n/content/es/docs/accounts/accounts-billing/new-relic-one-pricing-billing/add-on-billing.mdx b/src/i18n/content/es/docs/accounts/accounts-billing/new-relic-one-pricing-billing/add-on-billing.mdx new file mode 100644 index 00000000000..8f3bfc6661b --- /dev/null +++ b/src/i18n/content/es/docs/accounts/accounts-billing/new-relic-one-pricing-billing/add-on-billing.mdx @@ -0,0 +1,28 @@ +--- +title: Facturación adicional (opcional) +tags: + - Accounts + - Accounts and billing + - New Relic pricing and billing +metaDescription: Add-ons are an optional billing factor +freshnessValidatedDate: '2024-10-23T00:00:00.000Z' +translationType: machine +--- + +Además de los factores de facturación principales de GB Ingested y usuario facturable, también puedes usar complementos facturables opcionales para ampliar tu experiencia con New Relic. + +* **Advanced Compute (anteriormente Add-on Compute)**: este complemento se aplica a la facturación basada en el uso de las acciones que ejecuta relacionadas con CodeStream, Live Archives y otras funciones disponibles. Se le mide y factura en función de su uso de [CCU avanzadas](/docs/licenses/license-information/product-definitions/new-relic-one-pricing-definitions/#compute-capacity-unit). + + + Su uso de CodeStream bajo Calcular avanzado generará cargos de CCU, independientemente del tipo de usuario. Esto significa que el usuario básico gratis puede acceder a Calcular característica avanzada y generar cargos por CCU avanzadas. + + +* **EU Data Center for Original Data or Data Plus**: Este complemento se aplica a su opción de datos (Datos Originales o Datos Plus) cuando selecciona la Unión Europea como su región de datos, según disponibilidad. + +* **Extended Retention for Original Data or Data Plus**: este complemento se aplica si excede el tiempo predeterminado durante el cual se conservan sus datos. Esto se aplica a todos sus datos, no solo a los logs, y es una buena opción si necesita realizar muchas consultas pequeñas o consultas sobre grandes volúmenes de datos. + +* **Live Archives**: amplíe la duración del almacenamiento de logs hasta siete años. Live Archives también requiere Calcular avanzado. + +* **New Relic Synthetic Checks**: este complemento se aplica si tus controles exceden la cantidad predeterminada de controles de monitoreo sintético. + +* **Security RX**: Esta característica está incluida con Data Plus, pero el complemento aplica si usas la característica Security RX sin Data Plus. \ No newline at end of file diff --git a/src/i18n/content/es/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing.mdx b/src/i18n/content/es/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing.mdx new file mode 100644 index 00000000000..0871a750e10 --- /dev/null +++ b/src/i18n/content/es/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing.mdx @@ -0,0 +1,354 @@ +--- +title: 'Datos: Facturación y reglas' +tags: + - Accounts + - Accounts and billing + - New Relic pricing and billing +metaDescription: 'For New Relic pricing, an explanation of how data ingest is calculated for billing purposes.' +freshnessValidatedDate: '2024-10-23T00:00:00.000Z' +translationType: machine +--- + +Para los precios de New Relic, los datos ingeridos por su organización de New Relic son un factor de facturación. + +## Más información sobre los costos [#costs] + +Si aún no es cliente de New Relic y tiene curiosidad sobre los costos, primero consulte [nuestra página principal de precios](https://newrelic.com/pricing). Si ya es cliente, siga leyendo para conocer detalles sobre la facturación de la ingesta de datos. + +## Ver la ingesta de datos en la UI [#ui] + +Para saber cómo encontrar información de uso y facturación en la UI, consulte [UI de facturación](/docs/accounts/accounts-billing/general-account-settings/introduction-account-settings). + +Para saber cómo ver y administrar su ingesta de datos, consulte [Administrar la ingesta](/docs/data-apis/manage-data/manage-data-coming-new-relic). + +## Opciones de datos: Data Plus y original [#data-prices] + +El precio de su organización por GB de datos ingeridos varía según la opción de datos que tenga su organización: **Data Plus** o nuestra opción **Original Data** . La opción Data Plus ofrece capacidades de datos avanzadas para optimizar el rendimiento, la escala, la seguridad y la gobernanza. Una organización New Relic solo puede tener una opción a la vez. + +Aquí hay una tabla con comparaciones de las dos opciones. Los precios y límites son mensuales y los precios están en USD. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Característica/habilidad + + **Original Data** opción + + **Data Plus** opción + + Más detalles característicos +
+ [Ediciones](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing/#editions) + + Todas las ediciones + + Requiere Standard, Pro o Enterprise + + (Anotamos a continuación si una característica es específica de una edición) + +
+ Límite de datos libres + + 100 GB ingeridos + + 100 GB ingeridos + +
+ Precio de los datos
(más allá del límite libre) +
+ $0,40/GB ingerido + + $0,60/GB ingerido + +
+ Límite gratuito de retención de datos
([varía según el tipo de datos](/docs/data-apis/manage-data/manage-data-retention)) +
+ Incumplimiento de al menos 8 días + + 90 días adicionales sobre el incumplimiento + +
+ Precio por cada 30 días adicionales de retención
(más allá del límite gratuito) +
+ +$0.05/GB + + +$0.05/GB + +
+ Precio adicional para almacenar datos en [el centro de datos de la UE](/docs/accounts/accounts-billing/account-setup/choose-your-data-center)
+
+ +$0.05/GB + + +$0.05/GB + + Los datos se almacenan en el centro de datos de EE. UU. de forma predeterminada. +
+ [Límite máximo de consultas](/docs/query-your-data/nrql-new-relic-query-language/get-started/rate-limits-nrql-queries/#query-limits) + + Hasta 20 mil millones de puntos de datos por minuto + + Hasta 60 mil millones de puntos de datos por minuto + +
+ [Duración máxima de la consulta](/docs/query-your-data/nrql-new-relic-query-language/get-started/rate-limits-nrql-queries/#query-duration) + + 1 minuto + + Hasta 10 minutos + +
+ Elección del proveedor de la nube + + Proveedor único de nube + + Azure o múltiples proveedores de nube + + Elija su proveedor de nube preferido para su carga de trabajo de observabilidad para alinear su almacenamiento de telemetría con su modelo de despliegue de ingeniería y preferencia de nube. +
+ [Ofuscación de logs](/docs/logs/ui-data/obfuscation-ui/) + + Enmascarar [automáticamente](/docs/logs/get-started/new-relics-log-management-security-privacy/#log-obfuscation) patrones conocidos de tarjetas de crédito y números de Seguro Social en los logs. + + Cree y realice un seguimiento de reglas directamente en laUI y [enmascarar o aplicar hash](/docs/logs/ui-data/obfuscation-ui/) a datos log sensibles. + +
+ [New Relic Gestión de vulnerabilidades](/docs/vulnerability-management/overview)
(solo usuario de plataforma completa) +
+ +$0.10/GB
(más allá del límite gratuito) +
+ Standard, Pro, y Enterprise + + Identifique vulnerabilidades y aborde los riesgos en cada etapa del ciclo de vida del software. +
+ Elegibilidad [FedRAMP Moderate](/docs/security/security-privacy/compliance/fedramp-compliant-endpoints) y [HIPAA](/docs/security/security-privacy/compliance/hipaa-readiness-new-relic) + + + + Empresa + + Logre el cumplimiento de la seguridad a través de configuraciones que lo ayuden a cumplir con los requisitos de FedRAMP e HIPAA. +
+ [Exportación de streaming de datos](/docs/apis/nerdgraph/examples/nerdgraph-streaming-export) + + + + Standard, Pro, y Enterprise + + Configure reglas para exportar simultáneamente telemetry data al almacenamiento de AWS o Azure de su elección. Se aplicarán tarifas de exportación adicionales al proveedor de la nube. +
+ [Exportación de datos históricos](/docs/apis/nerdgraph/examples/nerdgraph-historical-data-export) + + + + Standard, Pro, y Enterprise + + Ejecute consultas más amplias sin tiempo de espera para análisis y modelado históricos, almacenamiento a largo plazo e integración con otras plataformas de análisis de datos. +
+ Servicio New Relic nativa de Azure + + + + Standard, Pro, y Enterprise
([con algunas limitaciones](#azure-native-data-plus)) +
+
+ +Para ver una comparación lado a lado de Data Plus y nuestra opción de datos original, consulte [nuestra hoja de datos de Data Plus](https://newrelic.com/resources/datasheets/data-plus). + +¿Interesado en Datos Plus? Consulte [Actualizar a Data Plus](#upgrade-data-plus). + +### Detalles del servicio Azure Native New Relic [#azure-native-data-plus] + +Con el [servicio Azure Native New Relic](/docs/infrastructure/microsoft-azure-integrations/get-started/azure-native), puede recopilar y almacenar sus telemetry data para aplicaciones e infraestructura directamente en Azure. Esta característica está incluida con Data Plus, pero con estas limitaciones: + +* Disponible solo en la región del centro de datos de EE. UU. +* Elegibilidad para FedRAMP Moderado/HIPAA no disponible +* Exportación de datos históricos no disponible + +## Actualice a Datos Plus [#upgrade-data-plus] + +Para actualizar a Data Plus, vaya a la [UI**Data retention** ](/docs/data-apis/manage-data/manage-data-retention/#adjust-retention)en el centro de administración de datos y haga clic en **Upgrade retention**. + +* Nota: Es posible que veas un botón **Edit data retention**, pero es diferente del botón **Upgrade retention**. +* Para ver el botón **Upgrade retention** , debes tener [permisos de facturación](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts/#admin-settings). Si cumple con los requisitos y aún no ve la opción **Upgrade retention** , hable con su representante de cuenta de New Relic. + +## ¿Qué se considera GB ingeridos facturables? [#usage-calculation] + +En el contexto del [plan de precios de New Relic](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing), "datos ingeridos" se refiere a los datos guardados en New Relic por su organización después de que aplicamos varias reglas de recorte y transformación de datos. En otras palabras, no es la cantidad de datos sin procesar enviados a New Relic, sino el tamaño de los datos que realmente terminan almacenándose. + +En general, los datos que generamos para proporcionar nuestra función no cuentan para sus GB ingeridos. Algunos ejemplos de datos de características y relacionados con ellas que no cuentan para GB ingeridos incluyen: + +* [Funcionalidad de alerta básica](/docs/alerts-applied-intelligence/new-relic-alerts/learn-alerts/alerts-concepts-workflow). Por ejemplo, `NrAiIncident`, un evento empleado para generar estas características, no cuenta para los GB ingeridos. +* Datos creados a partir de datos brutos agregados (por ejemplo, [datos de infraestructura agregados](/docs/data-apis/manage-data/manage-data-retention/#infrastructure-data) o [datos métricos dimensionales](/data-apis/manage-data/manage-data-retention/#dimensional-metrics)). +* [Métricas doradas](/docs/apis/nerdgraph/examples/golden-metrics-entities-nerdgraph-api-tutorial) (para más información sobre métricas doradas, consulte nuestras [definiciones de entidad](https://github.com/newrelic/entity-definitions)). +* Check de monitoreo sintético. Para obtener detalles sobre la facturación de Sintético, consulte [Límites y precios de Sintético](/docs/synthetics/synthetic-monitoring/using-monitors/monitor-limits). +* Datos de seguimiento de uso y facturación (por ejemplo, `NrConsumption`). +* Datos relacionados con la administración de la cuenta (por ejemplo, `NrIntegrationError`, `NrAuditEvent`). + +Para comprender su uso, consulte la [UI de uso](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing#usage-ui). + +## Otros detalles de cálculo [#calculation-details] + +* En el contexto de nuestro modelo de precios, un GB se define como mil millones de bytes. +* Los GB ingeridos mensualmente se redondean al número entero más cercano. Por ejemplo, si su organización emplea 100,9 GB durante un mes, eso se cuenta como 100 GB. + +## Edición gratuita [#free-tier-limits] + +Para obtener detalles sobre GB Ingested para nuestra edición gratis, consulte [Edición gratis](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing/#free). + +## Aprende más [#related-docs] + +* Para obtener más información sobre cómo gestionar GB ingeridos, consulte [Gestionar la ingesta de datos](/docs/data-apis/manage-data/manage-data-coming-new-relic). +* Para saber cómo consultar el uso, consulte [consulta y alerta de uso](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts). \ No newline at end of file diff --git a/src/i18n/content/es/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts.mdx b/src/i18n/content/es/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts.mdx index 9d5a3fe5c7b..81d289079e9 100644 --- a/src/i18n/content/es/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts.mdx +++ b/src/i18n/content/es/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts.mdx @@ -21,10 +21,11 @@ Tenga en cuenta lo siguiente al utilizar la UI de uso o realizar consultas de co ## Consulta sobre el uso de la ingesta de datos [#data-queries] -La [UI de uso](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing#usage-ui) muestra la ingesta de datos a lo largo del tiempo. Si necesita más detalles de los que proporciona la UI , puede utilizar una variedad de consultas NRQL. Los ejemplos siguientes incluyen dos tipos de datos: +The [usage UI](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing#usage-ui) displays your data ingest over time. If you need more detail than the UI provides, you can use a variety of NRQL queries. The examples below include the following data types: * `NrConsumption`: utilice esto para profundizar en los detalles de su uso hora por hora. Es menos útil como sustituto de su factura. -* `NrMTDConsumption`: utilice esto para ver una buena aproximación de su uso agregado mensual. +* `NrMTDConsumption`: Use this to see an approximation of your monthly aggregated usage. +* `NrCustomerMTDConsumption`: Use this to see an approximation of a customer's monthly aggregated usage. @@ -60,7 +61,7 @@ La [UI de uso](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new - Esta consulta muestra todos los datos ingeridos en la plataforma actual. En otras palabras, muestra cuánto se le facturaría por sus datos para ese mes si se le facturara ahora. La información de la tarifa de uso se calcula cada hora y demora aproximadamente 3 horas en generar. Si no se muestran valores, consulte los datos de hace 4 horas empleando "DESDE hace 4 horas". + This query shows the current full platform ingested data. In other words, it shows how much you'd be billed for your data for that month if you were billed right now. Usage fee information is calculated hourly and takes approximately 3 hours to generate. If no values are displayed, please query data from 4 hours ago using "SINCE 4 hours ago." ```sql FROM NrMTDConsumption SELECT latest(GigabytesIngested) @@ -73,6 +74,72 @@ La [UI de uso](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new +## Compute usage queries [#compute-queries] + +The [usage UI](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing#usage-ui) displays your compute usage over time. If you need more detail than the UI provides, you can use a variety of NRQL queries. The examples below include the following data types: + +* `NrConsumption`: utilice esto para profundizar en los detalles de su uso hora por hora. Es menos útil como sustituto de su factura. +* `NrMTDConsumption`: Use this to see an approximation of your monthly aggregated compute usage. +* `NrCustomerMTDConsumption`: Use this to see an approximation of a customer's monthly aggregated usage. + + + + This query totals your billable core compute usage, and displays a daily value for the past three months: + + ```sql + FROM NrConsumption SELECT sum(consumption) + WHERE metric = 'CoreCCU' + SINCE 3 months ago TIMESERIES 1 day + ``` + + + + This query totals your billable advanced compute usage, and displays a daily value for the past three months: + + ```sql + FROM NrConsumption SELECT sum(consumption) + WHERE metric = 'AdvancedCCU' + SINCE 3 months ago TIMESERIES 1 day + ``` + + + + This query totals your billable core compute usage, and displays a daily value for the past three months faceted by the capability: + + ```sql + FROM NrConsumption SELECT sum(consumption) + WHERE metric = 'CoreCCU' SINCE 3 months ago + FACET dimension_productCapability TIMESERIES 1 day + ``` + + + + This query totals your billable advanced compute usage, and displays a daily value for the past three months faceted by the capability: + + ```sql + FROM NrConsumption SELECT sum(consumption) + WHERE metric = 'AdvancedCCU' SINCE 3 months ago + FACET dimension_productCapability TIMESERIES 1 day + ``` + + + + This query shows the current full platform core compute usage. In other words, it shows how much you'd be billed for your data for that month if you were billed right now. Usage fee information is calculated hourly and takes approximately 3 hours to generate. If no values are displayed, please query data from 4 hours ago using "SINCE 4 hours ago." + + ```sql + FROM NrMTDConsumption select latest(consumption) where metric = 'CoreCCU' since 1 day ago + ``` + + + + This query shows the current full platform advanced compute usage. In other words, it shows how much you'd be billed for your data for that month if you were billed right now. Usage fee information is calculated hourly and takes approximately 3 hours to generate. If no values are displayed, please query data from 4 hours ago using "SINCE 4 hours ago." + + ```sql + FROM NrMTDConsumption select latest(consumption) where metric = 'AdvancedCCU' since 1 day ago + ``` + + + ## Límites de consulta y ingesta de datos [#data-limits] Para obtener información sobre los límites de ingesta de datos y los límites de consulta, consulte [Límites de datos de New Relic](/docs/data-apis/manage-data/view-system-limits). @@ -81,7 +148,7 @@ Para obtener información sobre los límites de ingesta de datos y los límites Para ver una visualización del recuento de usuarios, consulte la [UIde uso](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing#usage-ui). Si necesita más detalles, puede emplear el ejemplo de consulta NRQL a continuación. Para obtener detalles sobre cómo se calculan los usuarios, consulte [Cálculos de usuarios facturables](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/user-count-billing). -La mayoría de las organizaciones de New Relic tienen la capacidad de agregar usuarios principales. Esta sección incluye consultas que funcionarán para esas organizaciones. Si pertenece a una organización anterior que no ha [optado por desbloquear el usuario principal](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing#core-acceptance), consulte [la consulta para organizaciones sin usuario principal](#queries-non-core). +Most New Relic organizations have the ability to add core users. This section includes queries that will work for those organizations. If you're in an older organization that hasn't [opted in to unlock core users](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing#core-acceptance), see [Queries for organizations without core users](#queries-non-core). Aquí hay algunas reglas para consultar a su usuario: @@ -336,7 +403,7 @@ A continuación se muestran algunos ejemplos de condición de alerta NRQL. - Esta consulta creará una alerta cuando su uso supere el umbral mensual fijo de GB: + This query will create an alert when your usage exceeds a fixed monthly threshold for GBs: ```sql FROM NrMTDConsumption @@ -447,5 +514,5 @@ Para obtener más información sobre la estimación del uso, consulte [nuestra p A continuación se muestran algunos detalles técnicos sobre cómo funciona `bytecountestimate()` : * Hay varios tipos de datos que [no cuentan para la ingesta](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing/#usage-calculation) , pero que la función `bytecountestimate()` devuelve. Esto significa que esta función a veces muestra **more** datos de los que realmente se cuentan para su uso. Es posible que rara vez muestre una cantidad menor pero, si lo hace, será sólo ligeramente menor. -* Algunos telemetry data reportados por una entidad comparten un atributo común (por ejemplo, atributo sobre su cuenta New Relic). No contamos el atributo duplicado para su ingesta, pero `bytecountestimate()` sí cuenta esos atributos. En ocasiones, esto puede generar una gran discrepancia entre una consulta `bytecountestimate()` y su uso real. +* Some telemetry data reported from an entity shares common attributes (for example, attributes about your New Relic account). We don't count the duplicated attributes towards your ingest, but `bytecountestimate()` does count those attributes. This can sometimes result in a large discrepancy between a `bytecountestimate()` query and your actual usage. * Nuestros , y informan un tipo de datos conocidos como [datos de intervalo de tiempo de métrica](/docs/data-apis/understand-data/new-relic-data-types/#timeslice-data). Estos datos no se almacenan en NRDB como lo están nuestros otros tipos de datos, por lo que intentar utilizar `bytecountestimate()` en estos datos puede generar resultados confusos. Al consultar estos datos, recomendamos facetar por nombre de la aplicación y no por nombre de la métrica. \ No newline at end of file diff --git a/src/i18n/content/es/docs/alerts/admin/rules-limits-alerts.mdx b/src/i18n/content/es/docs/alerts/admin/rules-limits-alerts.mdx index a0d7d8e2655..aa98e5e581e 100644 --- a/src/i18n/content/es/docs/alerts/admin/rules-limits-alerts.mdx +++ b/src/i18n/content/es/docs/alerts/admin/rules-limits-alerts.mdx @@ -345,6 +345,39 @@ N/A * Aparte de eso: 5k + + + + + + Email addresses per destination + + + + 1 email address + + + + * Free accounts: 5 email addresses per destination + * Paid accounts: 150 email addresses per destination + + + + + + + + Email addresses per organization per 24 hours + + + + N/A + + + + 1000 unique email addresses (applies to all users) + + diff --git a/src/i18n/content/es/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx b/src/i18n/content/es/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx index eafe3e4220c..cb0ede66f03 100644 --- a/src/i18n/content/es/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx +++ b/src/i18n/content/es/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx @@ -269,24 +269,24 @@ Luego de la instalación, el agente se instrumenta automáticamente con nuestro | --------------------------------- | ----------------------- | ------------------------ | -------------------------------------- | | `@apollo/gateway` | 2.3.0 | 2.11.2 | `@newrelic/apollo-server-plugin@1.0.0` | | `@apollo/server` | 4.0.0 | 5.0.0 | `@newrelic/apollo-server-plugin@2.1.0` | -| `@aws-sdk/client-bedrock-runtime` | 3.474.0 | 3.886.0 | 11.13.0 | -| `@aws-sdk/client-dynamodb` | 3.0.0 | 3.886.0 | 8.7.1 | -| `@aws-sdk/client-sns` | 3.0.0 | 3.886.0 | 8.7.1 | -| `@aws-sdk/client-sqs` | 3.0.0 | 3.886.0 | 8.7.1 | -| `@aws-sdk/lib-dynamodb` | 3.377.0 | 3.886.0 | 8.7.1 | +| `@aws-sdk/client-bedrock-runtime` | 3.474.0 | 3.894.0 | 11.13.0 | +| `@aws-sdk/client-dynamodb` | 3.0.0 | 3.894.0 | 8.7.1 | +| `@aws-sdk/client-sns` | 3.0.0 | 3.894.0 | 8.7.1 | +| `@aws-sdk/client-sqs` | 3.0.0 | 3.894.0 | 8.7.1 | +| `@aws-sdk/lib-dynamodb` | 3.377.0 | 3.894.0 | 8.7.1 | | `@aws-sdk/smithy-client` | 3.47.0 | 3.374.0 | 8.7.1 | | `@azure/functions` | 4.7.0 | 4.8.0 | 12.18.0 | | `@elastic/elasticsearch` | 7.16.0 | 9.1.1 | 11.9.0 | -| `@google/genai` | 1.1.0 | 1.19.0 | 12.21.0 | -| `@grpc/grpc-js` | 1.4.0 | 1.13.4 | 8.17.0 | +| `@google/genai` | 1.1.0 | 1.20.0 | 12.21.0 | +| `@grpc/grpc-js` | 1.4.0 | 1.14.0 | 8.17.0 | | `@hapi/hapi` | 20.1.2 | 21.4.3 | 9.0.0 | | `@koa/router` | 12.0.1 | 14.0.0 | 3.2.0 | -| `@langchain/core` | 0.1.17 | 0.3.75 | 11.13.0 | -| `@modelcontextprotocol/sdk` | 1.13.0 | 1.17.5 | 13.2.0 | +| `@langchain/core` | 0.1.17 | 0.3.77 | 11.13.0 | +| `@modelcontextprotocol/sdk` | 1.13.0 | 1.18.1 | 13.2.0 | | `@nestjs/cli` | 9.0.0 | 11.0.10 | 10.1.0 | | `@opensearch-project/opensearch` | 2.1.0 | 3.5.1 | 12.10.0 | -| `@prisma/client` | 5.0.0 | 6.16.0 | 11.0.0 | -| `@smithy/smithy-client` | 2.0.0 | 4.6.1 | 11.0.0 | +| `@prisma/client` | 5.0.0 | 6.16.2 | 11.0.0 | +| `@smithy/smithy-client` | 2.0.0 | 4.6.3 | 11.0.0 | | `amqplib` | 0.5.0 | 0.10.9 | 2.0.0 | | `aws-sdk` | 2.2.48 | 2.1692.0 | 6.2.0 | | `bluebird` | 2.0.0 | 3.7.2 | 1.27.0 | @@ -294,7 +294,7 @@ Luego de la instalación, el agente se instrumenta automáticamente con nuestro | `cassandra-driver` | 3.4.0 | 4.8.0 | 1.7.1 | | `connect` | 3.0.0 | 3.7.0 | 2.6.0 | | `express` | 4.15.0 | 5.1.0 | 2.6.0 | -| `fastify` | 3.0.0 | 5.6.0 | 8.5.0 | +| `fastify` | 3.0.0 | 5.6.1 | 8.5.0 | | `generic-pool` | 3.0.0 | 3.9.0 | 0.9.0 | | `ioredis` | 4.0.0 | 5.7.0 | 1.26.2 | | `kafkajs` | 2.0.0 | 2.2.4 | 11.19.0 | @@ -302,14 +302,14 @@ Luego de la instalación, el agente se instrumenta automáticamente con nuestro | `koa-route` | 3.0.0 | 4.0.1 | 3.2.0 | | `koa-router` | 12.0.1 | 14.0.0 | 3.2.0 | | `memcached` | 2.2.0 | 2.2.2 | 1.26.2 | -| `mongodb` | 4.1.4 | 6.19.0 | 1.32.0 | +| `mongodb` | 4.1.4 | 6.20.0 | 1.32.0 | | `mysql` | 2.16.0 | 2.18.1 | 1.32.0 | -| `mysql2` | 2.0.0 | 3.14.5 | 1.32.0 | -| `next` | 13.4.19 | 15.5.2 | 12.0.0 | -| `openai` | 4.0.0 | 5.20.1 | 11.13.0 | +| `mysql2` | 2.0.0 | 3.15.0 | 1.32.0 | +| `next` | 13.4.19 | 15.5.3 | 12.0.0 | +| `openai` | 4.0.0 | 5.22.0 | 11.13.0 | | `pg` | 8.2.0 | 8.16.3 | 9.0.0 | | `pg-native` | 3.0.0 | 3.5.2 | 9.0.0 | -| `pino` | 8.0.0 | 9.9.5 | 8.11.0 | +| `pino` | 8.0.0 | 9.11.0 | 8.11.0 | | `q` | 1.3.0 | 1.5.1 | 1.26.2 | | `redis` | 3.1.0 | 5.8.2 | 1.31.0 | | `restify` | 11.0.0 | 11.1.0 | 2.6.0 | diff --git a/src/i18n/content/es/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation.mdx b/src/i18n/content/es/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation.mdx new file mode 100644 index 00000000000..e9317c49c4c --- /dev/null +++ b/src/i18n/content/es/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation.mdx @@ -0,0 +1,70 @@ +--- +title: Integración a través de CloudFormation y CloudWatch Metric Streams +tags: + - Integration via CloudFormation + - AWS metric integration + - Amazon integrations + - AWS integrations + - Integration with CloudWatch Metric Streams via CloudFormation +metaDescription: Integrate New Relic with AWS services using CloudFormation templates to automate the setup of CloudWatch Metric Streams for metrics ingestion. +freshnessValidatedDate: never +translationType: machine +--- + +Para una integración perfecta de su cuenta de AWS con New Relic, este es el proceso de integración más recomendado. Puede emplear API Polling para servicios no compatibles con CloudWatch Metric Streams. + +## Requisitos previos [#prerequisites] + +Antes de comenzar a integrar su cuenta de AWS con New Relic, cerciorar de cumplir con los siguientes requisitos previos: + +* **Una [clave de licencia](https://one.newrelic.com/api-keys)de New Relic**: necesitará una clave de licencia para conectar sus servicios de AWS a su cuenta de New Relic. +* **[Licencias](https://docs.aws.amazon.com/ARG/latest/userguide/gettingstarted-prereqs-permissions.html)** para implementar nuevos recursos AWS y **[roles de IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html)**: necesitará esta licencia para su cuenta AWS. +* **[Licencias](/docs/accounts/accounts-billing/new-relic-one-user-management/user-permissions/#infrastructure)** para la integración en la nube: Necesitarás estas licencias para tu cuenta New Relic. + +## Pasos de integración [#integration-steps] + +Para integrar su cuenta de AWS con New Relic mediante CloudFormation y CloudWatch Metric Streams, siga estos pasos: + +1. Navegar a [**Infrastructure > AWS**](https://one.newrelic.com/infra/infrastructure/cloud-aws). + +2. Seleccione la cuenta correcta. + +3. Haga clic en **Set up integration**. + +4. Siga las instrucciones en cada pantalla y complete los campos que correspondan. Para esta integración, elija las siguientes opciones en las pantallas dadas: + + 1. **Choose Data type(s)**: Metrics + 2. **Choose a setup method**: Automate AWS with CloudFormation (Recommended) + 3. **Choose a metrics integration type**: CloudWatch Metric Stream (Recommended) + +5. Si está empleando alguno de los servicios que no son compatibles con CloudWatch Metric Streams, en la página **Choose a metrics integration type**, seleccione **Yes** en el tercer paso para el sondeo API y continúe. + + AWS Integration with CWMS and API Polling + +
+ Integración CWMS de servicios de AWS con sondeo API seleccionado para servicios no soportados. +
+ + Realice la configuración necesaria según las instrucciones de la página **Enable API Polling (optional)** y continúe. + +6. Auto-discovery Detecta y visualiza automáticamente las relaciones entre sus entidades AWS en los mapas y aprovecha algunas otras flexibilidades. Para obtener más detalles, consulte [Descubrimiento automático de entidades AWS ](/docs/infrastructure/amazon-integrations/connect/set-up-auto-discovery-of-aws-entities/). Si desea esta función, habilítela en la página **Enable Auto Discovery (optional)** y continúe. + +7. Haga clic en **Launch your CloudFormation in AWS**. La plantilla de CloudFormation se abre en su consola AWS con el parámetro configurado según sus selecciones en New Relic, por lo que no es necesaria ninguna edición adicional a menos que desee realizar cambios. + +8. Pegue su clave de licencia en su consola de AWS. + +9. Para implementar la stack Cloudformation, en la consola AWS, seleccione **Create stack**. La creación de los recursos stack puede tardar varios minutos y puede generar múltiples pilas, dependiendo de cómo configure el reenvío de métrica. Si falla la creación stack, consulte el [procedimiento de resolución de problemas](https://docs.newrelic.com/docs/logs/troubleshooting/aws-log-integration-issues/stack-creation-fails/). + +10. Luego de crear una stack exitosa, cambie a la plataforma New Relic y continúe con la integración guiada hasta que vea sus datos AWS en New Relic. + +## Temas relacionados [#related-topics] + + + + Aprenda a recopilar datos de varias cuentas de AWS. + + + + Explore y emplee métrica de CloudWatch Metric Streams. + + \ No newline at end of file diff --git a/src/i18n/content/es/docs/infrastructure/other-infrastructure-integrations/stripe-integration.mdx b/src/i18n/content/es/docs/infrastructure/other-infrastructure-integrations/stripe-integration.mdx index 2f15833c927..22c746cee62 100644 --- a/src/i18n/content/es/docs/infrastructure/other-infrastructure-integrations/stripe-integration.mdx +++ b/src/i18n/content/es/docs/infrastructure/other-infrastructure-integrations/stripe-integration.mdx @@ -102,9 +102,9 @@ WHERE metricName = 'stripe_metrics' ### Instale nuestro dashboard de monitoreo de Stripe [#add-dashboard] -Para configurar nuestro dashboard de Stripe prediseñado para monitor su aplicación métrica, vaya a la [instalación dashboard de Stripe](https://onenr.io/0ZQWYYE1rRW) y siga las instrucciones. Una vez instalado, el dashboard debe mostrar métrica. +Para configurar nuestro dashboard Stripe prediseñado para monitorear su aplicación métrica, vaya a la [instalación del dashboard Stripe ](https://onenr.io/0BQrXaNgnRZ)y siga las instrucciones. Una vez instalado, el dashboard debería mostrar métrica. -Si necesita ayuda con el panel de control, consulte: +Si necesita ayuda con el dashboard, consulte: -* [Introducción al panel](/docs/query-your-data/explore-query-data/dashboards/introduction-dashboards) para personalizar tu dashboard y realizar diferentes acciones. +* [Introducción al dashboard](/docs/query-your-data/explore-query-data/dashboards/introduction-dashboards) para personalizar tu dashboard y realizar diferentes acciones. * [Administre su dashboard](/docs/query-your-data/explore-query-data/dashboards/manage-your-dashboard) para ajustar su modo de visualización o para agregar más contenido a su dashboard. \ No newline at end of file diff --git a/src/i18n/content/es/docs/new-relic-solutions/solve-common-issues/find-help-get-support.mdx b/src/i18n/content/es/docs/new-relic-solutions/solve-common-issues/find-help-get-support.mdx index 5772513daa8..7f49d877ef3 100644 --- a/src/i18n/content/es/docs/new-relic-solutions/solve-common-issues/find-help-get-support.mdx +++ b/src/i18n/content/es/docs/new-relic-solutions/solve-common-issues/find-help-get-support.mdx @@ -29,9 +29,9 @@ La vista de soporte en el producto brinda visibilidad de las novedades de New Re In-product support -## Pregunte en Explorers Hub, nuestro foro de soporte gratuito [#nr-forum] +## Pregunte en nuestro foro de soporte gratis [#nr-forum] -[New Relic's Explorers Hub](https://discuss.newrelic.com/) es nuestro foro gratuito para todos los usuarios. El usuario y el empleado de New Relic participan todos los días en conversaciones para solucionar problemas, encontrar soluciones y discutir nuevas características. +[El foro de soporte deNew Relic](https://discuss.newrelic.com/) es nuestro foro gratis para todos los usuarios. Los usuarios y empleados New Relic participan todos los días en conversaciones para solucionar problemas, encontrar soluciones alternativas y analizar nuevas características. ## Ejecute la herramienta de diagnóstico New Relic [#diagnostics] diff --git a/src/i18n/content/es/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx b/src/i18n/content/es/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx index 8ecaf1f4fe2..1adcd19a2f8 100644 --- a/src/i18n/content/es/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx +++ b/src/i18n/content/es/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx @@ -346,15 +346,24 @@ A continuación se muestran algunos tipos diferentes de implementaciones de vari - Puede habilitar la opción de valores múltiples desde la sección de opciones de visualización al crear una variable de tipo `NRQL/ENUM`. + You can enable the multi-value option to allow users to select multiple values from a dropdown instead of just one. This is useful when you want to filter data across multiple criteria simultaneously. - A continuación se muestra un ejemplo de una consulta que crea una variable denominada `{{MultiValue}}` y devuelve una lista de todos los ID de evento únicos: + Multi-value is available for Query and List variable types. Text field variables don't support the multi-value option. + + To enable multi-value: + + 1. When creating a Query or List template variable, select the **Multi-value** option. + 2. In your widget queries, use the `IN` operator instead of `=` to handle multiple selected values. + + /* You can enable the multi-value option from the display options section when creating a variable of type `NRQL/ENUM`. */ + + Here's an example where you'd name your variable `{{MultiValue}}` and use this query to populate its values: ```sql SELECT uniques(eventId) FROM AjaxRequest ``` - Multi-value template variable example + /* <img width="30%;" title="Multi-value template variable example" alt="Multi-value template variable example" src="/images/dashboards_screenshot-crop_add-multivalue.webp" /> */ Luego crearías un widget con la siguiente consulta: @@ -362,22 +371,36 @@ A continuación se muestran algunos tipos diferentes de implementaciones de vari SELECT count(*) FROM AjaxRequest WHERE eventId IN ({{MultiValue}}) ``` - Creating a widget + /* <img width="80%;" title="Creating a widget" alt="Creating a widget" src="/images/dashboards_screenshot-full_multivalue-add-widget.webp" /> */ - Sólo puede definir una variable de plantilla a la vez, pero puede utilizar más de una variable de plantilla en un único widget. + While you can only define one template variable at a time, you can reference multiple variables within the same widget. + + For this example, you need to have the two variables set up: + + 1. `countryCode` variable: Use the query shown earlier in this document: + + ```sql + SELECT uniques(countryCode) FROM PageAction SINCE 2 days ago + ``` + + 2. `city` variable with a similar query: + + ```sql + SELECT uniques(city) FROM PageView SINCE 1 week ago + ``` - A continuación se muestra un ejemplo de una consulta que utiliza dos variables de plantilla. Tenga en cuenta que esto supone que las variables de plantilla `countryCode` y `city` ya se habrán creado y que tienen un valor único. + Here's an example using the above template variables with single values to create the widget: ```sql SELECT countryCode, city FROM PageAction WHERE countryCode = {{countryCode}} AND city = {{city}} ``` - Creating a widget using multiple variables + /* <img title="Creating a widget using multiple variables" alt="Creating a widget using multiple variables" src="/images/dashboards_screenshot-crop_add-widget-multiple-variable.webp" /> */ - Si tiene varios valores para sus variables, como `Chicago`, `New York`, `Paris` para su variable `city` , debe usar `IN`: + If your variables support multiple values (such as `Chicago`, `New York`, `Paris` for your `city` variable), you need to use `IN`: ```sql SELECT countryCode, city FROM PageAction @@ -398,7 +421,7 @@ A continuación se muestran algunos tipos diferentes de implementaciones de vari SELECT uniques(aparse(platformVersion, 'release-*')) FROM PageView ``` - Creating the release version variable + /* <img width="40%;" title="Creating the release version variable" alt="Creating the release version variable" src="/images/dashboards_screenshot-crop_add-var-release-version.webp" /> */ Luego cree un widget con la siguiente consulta: @@ -407,7 +430,7 @@ A continuación se muestran algunos tipos diferentes de implementaciones de vari WHERE aparse(platformVersion, 'release-*') IN ({{releaseversion}}) FACET platformVersion ``` - Creating the widget + /* <img title="Creating the widget" alt="Creating the widget" src="/images/dashboards_screenshot-crop_add-widget-aparse.webp" /> */ O si lo prefieres, puedes usar el comando [`capture`](/docs/query-your-data/nrql-new-relic-query-language/get-started/nrql-syntax-clauses-functions/#func-capture) : @@ -416,15 +439,20 @@ A continuación se muestran algunos tipos diferentes de implementaciones de vari WHERE capture(platformVersion, r'release-(?P\d+)') IN ({{releaseversion}}) FACET platformVersion ``` - Creating the widget + /* <img title="Creating the widget" alt="Creating the widget" src="/images/dashboards_screenshot-crop_add-widget-capture.webp" /> */ Puede utilizar `LIKE` y `RLIKE` como variables de plantilla para filtrar datos en un dashboard. Para usar esta característica, el valor que agregue al crear la variable de plantilla debe usar los símbolos comodín `%` al inicio y al final del valor. - He aquí un ejemplo. Usted define una variable de cadena, como se muestra aquí: + Here's an example. You define a string template variable with the following values: + + * **Name to use in queries:** line\_filter + * **Tipo:** `Text field` + * **Default value:** %@%.com + * **Output format:** `String` - Add `LIKE` as template variable + /* <img width="40%;" title="Add `LIKE` as template variable" alt="Add `LIKE` as template variable" src="/images/dashboards_screenshot-crop_add-var-like-filter.webp" /> */ Luego puedes crear un gráfico widget y usar tu variable de esta manera: @@ -432,7 +460,7 @@ A continuación se muestran algunos tipos diferentes de implementaciones de vari FROM NrdbQuery SELECT user WHERE user LIKE {{like_filter}} ``` - Add `LIKE` as template variable + /* <img title="Add `LIKE` as template variable" alt="Add `LIKE` as template variable" src="/images/dashboards_screenshot-crop_add-widget-like-filter.webp" /> */ o así: @@ -450,13 +478,13 @@ A continuación se muestran algunos tipos diferentes de implementaciones de vari > Puede crear una variable de tipo NRQL con un formato de salida de cadena y usarla después de una cláusula `FACET` para agrupar por diferentes valores. - Por ejemplo, podrías crear una variable denominada `{{userAgentName}}` que tendría este aspecto: + For example, you might create a template variable named `{{userAgentName}}` that would look like: ```sql SELECT uniques(userAgentName) FROM PageAction ``` - Creating the variable + /* <img width="30%;" title="Creating the variable" alt="Creating the variable" src="/images/dashboards_screenshot-crop_add-var-facet.webp" /> */ Luego crearías un widget con la siguiente consulta: @@ -465,15 +493,20 @@ A continuación se muestran algunos tipos diferentes de implementaciones de vari WHERE userAgentName={{userAgentName}} FACET userAgentName ``` - Creating widget using facet + /* <img title="Creating widget using facet" alt="Creating widget using facet" src="/images/dashboards_screenshot-crop_add-widget-facet.webp" /> */ Puede crear una variable con un formato de salida `identifier` y usarla después de una cláusula `FACET` para agruparla por diferentes valores. - Por ejemplo, puede crear una variable `{{location}}` de tipo lista con dos valores posibles: `countryCode` y `city`. Establecerías el formato de salida en `identifier`. + For example, you might create a `{{location}}` variable: - Adding the variable for dynamic grouping + * **Name to use in queries:** location + * **Tipo:** `List` + * **Values separated by commas:** `countryCode` and `city` + * **Output format:** `Identifier` + + /* <img width="40%;" title="Adding the variable for dynamic grouping" alt="Adding the variable for dynamic grouping" src="/images/dashboards_screenshot-crop_add-var-dynamic-grouping.webp" /> */ Luego crearías un widget con la siguiente consulta: @@ -481,15 +514,20 @@ A continuación se muestran algunos tipos diferentes de implementaciones de vari SELECT count(*) FROM PageAction FACET {{location}} ``` - Adding the widget for dynamic grouping + /* <img title="Adding the widget for dynamic grouping" alt="Adding the widget for dynamic grouping" src="/images/dashboards_screenshot-crop_add-widget-dynamic-grouping.webp" /> */ Puede crear una variable con formato de salida `number` y usarla dentro de una función de percentil. - Por ejemplo, podría crear una variable `{{percentile}}` de tipo `list` con dos valores posibles: `55` y `90`. Querrá establecer el formato de salida como `number`. + For example, you could create a `{{percentile}}` variable: + + * **Name to use in queries:** percentile + * **Tipo:** `List` + * **Values separated by commas:** `55` and `90` + * **Output format:** `Number` - Adding the variable for dynamically change the percentile + /* <img width="40%;" title="Adding the variable for dynamically change the percentile" alt="Adding the variable for dynamically change the percentile" src="/images/dashboards_screenshot-crop_add-var-dynamic-percentile.webp" /> */ Luego crearías un widget con la siguiente consulta: @@ -497,7 +535,7 @@ A continuación se muestran algunos tipos diferentes de implementaciones de vari SELECT percentile(duration, {{percentile}}) FROM PageAction ``` - Adding the widget for dynamically change the percentile + /* <img title="Adding the widget for dynamically change the percentile" alt="Adding the widget for dynamically change the percentile" src="/images/dashboards_screenshot-crop_add-widget-dynamic-percentile.webp" /> */ @@ -508,7 +546,7 @@ A continuación se muestran algunos tipos diferentes de implementaciones de vari WHERE countryCode IN ({{countryCode}}) ``` - Use variables to filter + /* <img title="Use variables to filter" alt="Use variables to filter" src="/images/dashboards_screenshot-crop_variables-to-filter.webp" /> */ @@ -528,7 +566,7 @@ A continuación se muestran algunos tipos diferentes de implementaciones de vari Esto da como resultado los valores de los últimos 30 minutos. Cuando establece el valor del selector de tiempo en **Default** y su consulta tiene una cláusula `SINCE` , se utilizará el último valor para ejecutar la consulta. - A screenshot showing the variable form + /* <img title="Example form" alt="A screenshot showing the variable form" src="/images/dashboards_screenshot-crop_example-form.webp" /> */ + Recomendamos actualizar a la última versión del agente tan pronto como esté disponible. Si su organización estableció prácticas que le impiden actualizar a la última versión, cerciorar de que sus agentes se actualicen periódicamente a una versión que tenga como máximo 90 días de antigüedad. Obtenga más información sobre [cómo mantener a su agente actualizado](https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/). + + +## 3.41.0 + +### Agregado + +* Se agregaron `DistributedTracer.Sampler` opciones de configuración para controlar el comportamiento de ejemplificación de las solicitudes entrantes para el rastreo distribuido + + * Para configurar el muestreador, se agregaron `ConfigRemoteParentSampled(flag RemoteParentSamplingConfig)` y `ConfigRemoteParentNotSampled(flag RemoteParentSamplingConfig)` que manejan el comportamiento de la ejemplificación en función de lo que el padre remoto marcó + * Las banderas agregadas son `"always_on", "always_off", and "default"` que se pueden llamar usando `RemoteParentSamplingConfig` + * `Example: newrelic.ConfigRemoteParentSampled(newrelic.AlwaysOff)` + +* Se agregaron pruebas de monitoreo OOM + +* Mayor cobertura de pruebas de agentes seguros + +### Fijado + +* Versiones de bibliotecas de terceros actualizadas debido a problemas de seguridad u otros problemas de compatibilidad informados: + + * `github.com/gofiber/fiber/v2` de 2.52.7 a 2.52.9 en la integración `nrfiber` + * `golang.org/x/net` de 0,25,0 a 0,38,0 en la integración `nrconnect` + +### Declaración de apoyo + +Empleamos la última versión del lenguaje Go. Como mínimo, no deberías emplear ninguna versión de Go anterior a la compatible con el propio equipo de Go. Consulte la [Política de fin de vida del agente Go](https://docs.newrelic.com/docs/apm/agents/go-agent/get-started/go-agent-eol-policy/) para obtener detalles sobre las versiones compatibles del agente Go y los componentes de terceros. \ No newline at end of file diff --git a/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-8-01-2025.mdx b/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-8-01-2025.mdx new file mode 100644 index 00000000000..168add677e4 --- /dev/null +++ b/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-8-01-2025.mdx @@ -0,0 +1,99 @@ +--- +subject: Docs +releaseDate: '2025-08-01' +version: 'July 25 - August 01, 2025' +translationType: machine +--- + +### Nuevos documentos + +* Se agregó [documentación de Cotizaciones de Calcular](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/compute-budgets/overview) para brindarle un mecanismo para monitorear y alertar sobre el uso de su Unidad de Consumo de Calcular (CCU). + +### Cambios importantes + +* [Compatibilidad y requisitos](/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent) actualizados para el agente Node.js. + +* [Compatibilidad y requisitos actualizados para Alpine Linux](/docs/apm/agents/php-agent/getting-started/php-agent-compatibility-requirements) para el agente PHP. + +* Se actualizaron los requisitos específicos del agente para [el control de tuberías](/docs/new-relic-control/pipeline-control/modify-agent-configuration). + +* Se actualizó el JFR relacionado con los requisitos de configuración para [el agente de Java](/docs/apm/agents/java-agent/configuration/java-agent-configuration-config-file#jfr-harvest-interval). + +* Se actualizó la información de precios y facturación de New Relic en: + + * [Datos: Facturación y reglas](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing) + * [Consultas y alertas relacionadas con el uso](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts) + * [Plan de uso de New Relic](/docs/licenses/license-information/usage-plans/new-relic-usage-plan) + +### Cambios menores + +* Se aclaró el lenguaje en el agente .NET para capturar el parámetro SQL en el documento [de compatibilidad del agente y requisitos de .NET](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements). +* Se perfeccionó el lenguaje en [Oracle base de datos monitoreo integración](/docs/infrastructure/host-integrations/host-integrations-list/oracle-database-monitoring-integration). + +### Notas de la versión + +* Consulta nuestras publicaciones de Novedades: + + * [Calcular Cotizaciones ahora disponibles de forma general](/whats-new/2025/07/whats-new-7-30-compute-budgets). + * [Mejorar la experiencia del usuario: aprovechar Session Replay para optimizar los elementos esenciales de la web](/whats-new/2025/07/whats-new-7-31-augmenting-user-experiences-browser). + +* Mantener actualizado con nuestros últimos lanzamientos: + + * [AgenteAndroid v7.6.8](/docs/release-notes/mobile-release-notes/android-release-notes/android-768): + + * Se solucionó un problema en el que el rastreo de stack para errores de Unity no se mostraba correctamente. + * Se solucionó un problema que impedía que se registrara el resumen métrico cuando la aplicación volvía al primer plano luego de su lanzamiento inicial. + * Se solucionó un problema por el cual un JSON no válido en las entradas de registro podía provocar errores. + + * [CLI de diagnóstico (nrdiag) v3.4.0](/docs/release-notes/diagnostics-release-notes/diagnostics-cli-release-notes/diagnostics-cli-341): + * Se agregó `K8s/AgentControl/agent-control-install-job-logs` para recopilar los logs generados por la instalación del control del agente. + + * [Administrador de trabajos v451](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-451): + + * Se corrigieron vulnerabilidades relacionadas con `common-lang3` Java y Ubuntu para abordar problemas de seguridad en SJM. + * Se implementaron cambios en la migración de la cola del procesador relacionados con la migración de nuestra arquitectura de servicio interna. + * Se solucionó un problema para incluir detalles completos de la excepción para proporcionar un mejor contexto para la resolución de problemas en los logs de SJM. + + * [Aplicación móvil para Android v5.30.1](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5301): + * Se mejoró la experiencia de inicio de sesión. + + * [Aplicación móvil para iOS v7.5.8](/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-758): + + * Construí el agente usando Xcode 16.4. + * Se solucionó un problema que podía provocar que rastreo distribuido no tuviera toda la información de cuenta requerida al inicio de una sesión. + * Se solucionó un problema que podía provocar un bloqueo al iniciar el agente. + + * [Tiempo de ejecución de la API de nodo](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.122): + * Se corrigieron las vulnerabilidades de datos de formulario y las vulnerabilidades subyacentes de Ubuntu para abordar vulnerabilidades de seguridad en los tiempos de ejecución de Node API. + + * [Node browser runtime](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.39): + * Se corrigieron las vulnerabilidades de datos de formulario y las vulnerabilidades subyacentes de Ubuntu para abordar vulnerabilidades de seguridad en los tiempos de ejecución de Node Browser. + + * [Tiempo de ejecución de ping](/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.53.0): + * Se corrigieron vulnerabilidades relacionadas con `common-lang3` Java y Ubuntu para abordar problemas de seguridad en el tiempo de ejecución de Ping. + + * [Agente de Python v10.15.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-101500): + + * Se agregó soporte para [`oracledb`](https://pypi.org/project/oracledb/) + * Se corrigió un error en la instrumentación `MessageBroker` donde los métodos serializar buscaban el atributo `destination_name` en `MessageTransaction` y no existía. + * Se solucionó el problema de metadatos de utilización de AWS al ejecutar AWS y K8s juntos. + + * [AgenteRuby v9.20.0](/docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-20-0): + + * Se agregó soporte para registrar el ID de Docker cuando se ejecuta en el entorno AWS ECS Fargate. + * Se agregó un nuevo método auxiliar para simplificar la comparación de versiones. + * Se agregó el atributo `code.stacktrace` a los intervalos de almacenamiento de datos cuando la duración excede el umbral configurado. + * Se corrigieron los `Brewfile` enlaces de origen. + * Se corrigió un error que ocurre cuando se usa `HTTPX 1.5.0` para almacenar la respuesta. + * Se mejoró la información registrada en el nivel de depuración por el agente cuando el agente lee una fuente de configuración. + + * [Agente de Unity v1.4.8](/docs/release-notes/mobile-release-notes/unity-release-notes/unity-agent-148): + + * Se actualizó el agente nativo de Android a v7.6.7. + * Se actualizó el agente nativo de iOS a v7.5.6. + + * [Agente de Unity v1.4.9](/docs/release-notes/mobile-release-notes/unity-release-notes/unity-agent-149): + + * Se actualizó el agente nativo de Android a v7.6.8. + * Se actualizó el agente nativo de iOS a v7.5.8. + * Se solucionó el problema de rastreo de stack de excepciones de Unity cuando se emplean espacios de nombres. \ No newline at end of file diff --git a/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx b/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx new file mode 100644 index 00000000000..01456861c55 --- /dev/null +++ b/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx @@ -0,0 +1,60 @@ +--- +subject: Docs +releaseDate: '2025-08-08' +version: 'August 01 - August 07, 2025' +translationType: machine +--- + +### Nuevos documentos + +* Se agregó [el tutorial de NerdGraph: Crear un rol personalizado para Teams](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/compute-budgets/overview) para guiarlo en el uso de la API de NerdGraph de New Relic para crear y gestionar roles personalizados para Teams. + +### Cambios menores + +* Se modificó el [umbral de alerta de evento por condición](/docs/alerts/admin/rules-limits-alerts) a 1k por minuto. +* Se actualizaron las últimas [versiones y requisitos compatibles del agente .Net](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements) verificados. +* Se actualizó la información de versión y soporte de versión acerca del agente de servicio para [VMware Tanzu](/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-service-broker-integration). +* Se actualizó la información de soporte de la versión sobre el paquete de compilación de integración NGINX de New Relic para [VMware Tanzu](/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-nginx-buildpack-integration). +* Se actualizó la información de versión y soporte de versiones de New Relic Nozzle para [VMware Tanzu](/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-firehose-nozzle-integration/#product-snapshot). + +### Notas de la versión + +* Consulta nuestras publicaciones de Novedades: + + * [Errors Inbox ahora está integrada dentro de carga de trabajo](/whats-new/2025/08/whats-new-08-06-workloads-errors-inbox). + +* Mantener actualizado con nuestros últimos lanzamientos: + + * [Administrador de trabajos v452](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-452): + * Se agregaron mejoras internas para el manejo de excepciones al procesar mensajes de la cola. + + * [IntegraciónKubernetes v3.43.3](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-43-3): + * Se agregó un gráfico Helm para implementar la solución de monitoreo Kubernetes New Relic. + + * [Control de tuberías Gateway v1.1.0](/docs/release-notes/pipeline-control-gateway-release-notes/pipeline-control-gateway-25-08-05): + + * Se implementó una nueva funcionalidad para descartar selectivamente datos y atributos de `SqlTrace` y `TransactionTrace` incluso usando reglas de descartado. + + * Se abordaron vulnerabilidades en el paquete `golang.org/x/net`, incluido un problema de script entre sitios y una omisión de proxy HTTP relacionada con los ID de zona IPv6. + + * Se actualizó a Go `1.24` y las siguientes dependencias se actualizan para mejorar la seguridad e incorporar correcciones recientes: + + * `golang.org/x/net to v0.38.0` + * `golang.org/x/sys to v0.31.0` + * `golang.org/x/text to v0.23.0` + + * [Aplicación móvil para iOS v6.9.11](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6101): + * Se redujo el flujo de inicio de sesión en dos pasos al almacenar el dominio de autenticación de un usuario y redirigirlo directamente a su página de inicio de sesión. + + * [Agente deFlutter v1.1.13](/docs/release-notes/mobile-release-notes/flutter-release-notes/flutter-agent-1113): + + * Agente nativo Android mejorado actualizado a la versión 7.6.8 + * Agente nativo de iOS mejorado actualizado a la versión 7.5.8 + + * [Agente .NET MAUI v1.1.11](/docs/release-notes/mobile-release-notes/net-maui-release-notes/net-maui-agent-1111) + + * Agente nativo Android mejorado actualizado a la versión 7.6.8 + * Agente nativo de iOS mejorado actualizado a la versión 7.5.8 + + * [agente de infraestructura v1.65.5](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1655): + * Se modificó el soporte de montaje de AWS EFS en muestras de almacenamiento. \ No newline at end of file diff --git a/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-8-14-2025.mdx b/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-8-14-2025.mdx new file mode 100644 index 00000000000..aa561dae04a --- /dev/null +++ b/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-8-14-2025.mdx @@ -0,0 +1,112 @@ +--- +subject: Docs +releaseDate: '2025-08-15' +version: 'August 08 - August 14, 2025' +translationType: machine +--- + +### Nuevos documentos + +* Se agregó [soporte para funciones NRQL en reglas de puerta de enlace](/docs/new-relic-control/pipeline-control/nrql-functions) para delinear las funciones NRQL admitidas en las reglas de puerta de enlace de Control de pipelines. +* Se agregaron pasos de resolución de problemas para resolver [Frequent Fluent Bit Restart Events](/docs/infrastructure/infrastructure-troubleshooting/troubleshoot-infrastructure/frequent-fluent-bit-restart-events) ajustando la configuración de resolución del nombre del host en la configuración del agente de New Relic Infrastructure. + +### Cambios importantes + +* [Plan de uso](/docs/licenses/license-information/usage-plans/new-relic-usage-plan/#list-price) actualizado con la última información de precios. +* Se agregó **Errors Inbox** a [la UIde carga de trabajo](/docs/new-relic-solutions/new-relic-one/workloads/use-workloads/#errors). +* Se agregó la desactivación selectiva del agente en función de la clase principal de inicio o el jar ejecutable a través de variables de entorno, junto con configuraciones de seguridad mejoradas para [la configuración del agente de Java ](/docs/apm/agents/java-agent/configuration/java-agent-configuration-config-file/#skip-applications). +* Se agregó soporte para [la configuración de repositorio privado](/docs/new-relic-control/agent-control/configuration/#private-repository-configuration) en el control de agente, lo que permite la implementación de agente gestionado con autenticación a través de métodos de certificado básico o TLS. +* Se agregó soporte para [la gestión de secretos](/docs/new-relic-control/agent-control/configuration/#secrets-management) en el control de agente, para gestionar datos confidenciales, como contraseñas y claves de API, recuperándolos del proveedor de secretos dedicado. + +### Cambios menores + +* Se agregaron restricciones de etiqueta de entidad para la cláusula `WHERE` en [Descartar datos mediante reglas cloud de Control de canalizaciones](/docs/new-relic-control/pipeline-control/cloud-rules-api/#restrictions). +* Se agregaron [las mejores prácticas para optimizar el contenido de su fuente de conocimiento](/docs/agentic-ai/knowledge-integration/overview/#configure) para el conector de conocimiento de New Relic AI. + +### Notas de la versión + +* Consulta nuestras publicaciones de Novedades: + + * [El modo de alta precisión de UniqueCount y el mayor soporte de argumentos ahora están disponibles de manera general](/whats-new/2025/08/whats-new-8-13-high-precision-uniquecount). + +* Mantener actualizado con nuestros últimos lanzamientos: + + * [AgenteCordova v7.0.8](/docs/release-notes/mobile-release-notes/cordova-release-notes/cordova-agent-708/): + + * Actualizar el agente nativo de Android a la versión 7.6.8 + * Actualizar el agente nativo de iOS a la versión 7.5.8 + + * [Agente Cordova v7.0.9](/docs/release-notes/mobile-release-notes/cordova-release-notes/cordova-agent-709/): + + * Actualizar el agente nativo de Android a la versión 7.6.6 + * Actualizar el agente nativo de iOS a la versión 7.5.5 + + * [Agente de Capacitor v1.5.8](/docs/release-notes/mobile-release-notes/capacitor-release-notes/capacitor-agent-158/): + + * Actualizar el agente nativo de Android a la versión 7.6.6 + * Actualizar el agente nativo de iOS a la versión 7.5.5 + + * [Agente de Capacitor v1.5.9](/docs/release-notes/mobile-release-notes/capacitor-release-notes/capacitor-agent-159/): + * Fallo de señal de aborto fijo + + * [Agente de Capacitor v1.5.10](/docs/release-notes/mobile-release-notes/capacitor-release-notes/capacitor-agent-1510/): + + * Actualizar el agente nativo de Android a la versión 7.6.8 + * Actualizar el agente nativo de iOS a la versión 7.5.8 + + * [CLI de diagnóstico (nrdiag) v3.5.0](/docs/release-notes/diagnostics-release-notes/diagnostics-cli-release-notes/diagnostics-cli-350/): + * se actualizó la comprobación de compatibilidad de la versión `Java/Appserver/JbossEapCheck` + + * [Agente .NET v10.44.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-44-0/): + + * Samplers de rendimiento métrica habilitados en modo Serverless + * Se excluyó el proceso de host sitio web de Azure Functions (Linux) de la instrumentación. + + * [NRDOT v1.3.0](/docs/release-notes/nrdot-release-notes/nrdot-2025-08-13/): + + * Se actualizaron las versiones de los componentes del hotel de v0.128.0 a v0.131.0 + * Se introdujo la distribución principal de nrdot + + * [Agente de Node.js v13.1.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-1-0/): + + * Se agregó soporte para la API de logs de OTEL + * Se agregó compatibilidad con métricas cuando se deshabilitó la instrumentación para un paquete + * Instrumentación de temporizadores deshabilitados por defecto en la configuración de muestra. + * Ofuscación fija `transaction.url` + + * [Administrador de trabajos v454](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-454/): + * Se corrigieron las vulnerabilidades subyacentes de Ubuntu para abordar las vulnerabilidades de seguridad en SJM. + + * [Tiempo de ejecución de la API de nodo v1.2.124](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.124/): + * Se corrigieron las vulnerabilidades subyacentes de Ubuntu para abordar vulnerabilidades de seguridad en los tiempos de ejecución de Node API. + + * [Runtime del navegador de nodos v3.0.41](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.41/): + * Se corrigieron las vulnerabilidades temporales `CVE-2025-54798` y las vulnerabilidades subyacentes de Ubuntu para abordar vulnerabilidades de seguridad en los tiempos de ejecución de Node Browser . + + * [Tiempo de ejecución de ping v1.54.0](/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.54.0/): + * Se corrigieron vulnerabilidades relacionadas con Ubuntu para abordar problemas de seguridad en el tiempo de ejecución de Ping. + + * [Agente de Java v8.23.0](/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8230/): + + * Actualizado para soportar v24 de graphql. + * Se agregó instrumentación de lechuga 6.5. + * Se actualizó la versión de Commons Lang a 3.18.0 + + * [Reenviador de logs AWS Lambda v1.1.1](/docs/release-notes/aws-lambda-log-forwarder-release-notes/lambda-25-07-25/): + * Se mejoró la postura de seguridad al actualizar la versión Go a 1.24.4 en los sistemas. + + * [Agente PHP v12.0.0.25](/docs/release-notes/agent-release-notes/php-release-notes/php-agent-12-0-0-25/): + + * Logging de errores del mapa de gancho de Drupal mejorado. + * Se corrigieron problemas de detección de paquetes legacy para Security RX. + + * [agente de infraestructura v1.66.1](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1661/): + * Se revirtió el soporte para montajes de AWS EFS en muestras de almacenamiento. + + * [Aplicación móvil para Android v5.30.6](docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5306/): + * Compatibilidad mejorada con claves de acceso para inicios de sesión SAML y sociales. + + * [Agente del navegador v1.295.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.0/): + + * Se agregó detección de causa de error. + * Se agregaron advertencias sobre parches para monos. \ No newline at end of file diff --git a/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-8-21-2025.mdx b/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-8-21-2025.mdx new file mode 100644 index 00000000000..e554b9e74bb --- /dev/null +++ b/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-8-21-2025.mdx @@ -0,0 +1,56 @@ +--- +subject: Docs +releaseDate: '2025-08-22' +version: 'August 15 - August 21, 2025' +translationType: machine +--- + +### Cambios importantes + +* Reporte actualizado de compatibilidad [del agente Node.js.](/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent/) +* [Agente .NET](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements/) actualizado con las últimas versiones de biblioteca compatibles verificadas. + +### Cambios menores + +* Se actualizó el sistema operativo [Debian](/docs/infrastructure/infrastructure-agent/linux-installation/package-manager-install/) a la versión 12 ("bookworm") para soportar el [agente de infraestructura](/docs/infrastructure/infrastructure-agent/requirements-infrastructure-agent/#os) para Linux. +* Se actualizó la función [`accountId()`](/docs/data-apis/manage-data/query-limits/) para consultar los límites de datos. +* [Instalador MSIWindows ](/docs/infrastructure/infrastructure-agent/windows-installation/windows-msi-installer/#install-windows)actualizado para soportar Windows de 64 bits (Intel/AMD). + +### Notas de la versión + +* Se anunció el 7 de enero de 2026 como la fecha de fin de vida útil de las reglas de lanzamiento a través de la [UI de monitoreo de IA](/docs/ai-monitoring/drop-sensitive-data/). + +* [Agente iOS v7.5.9](/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-759/) + + * Se solucionó un problema que podía provocar que rastreo distribuido no tuviera toda la información de cuenta requerida al inicio de una sesión. + * Se solucionó un problema que podía provocar un bloqueo al iniciar el agente. + +* [Agente de Python v10.16.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-101600/) + + * Se agregó soporte para nuevas funciones [de Redis](https://pypi.org/project/redis/). + * Se convirtieron todas las rutas internas de `os.path` a `pathlib.Path`. + * Problema corregido con la codificación JSON PosixPath. + +* [Integración Kubernetes v3.44.1](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-44-1/) + + * Esta integración está incluida en las siguientes versiones de gráficos: + + * [infraestructura newrelic-3.49.1](https://github.com/newrelic/nri-kubernetes/releases/tag/newrelic-infrastructure-3.49.1) + * [paquete nri-6.0.10](https://github.com/newrelic/helm-charts/releases/tag/nri-bundle-6.0.10) + +* [Agente .NET v10.44.1](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-44-1/) + + * Se corrigió el manejo de excepciones en el contenedor de instrumentación de Service Bus. + * Se excluyó el proceso de host sitio web de Azure Functions (Linux) de la instrumentación. + +* [Agente de Node.js v13.2.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-2-0/) + + * Se agregó la capacidad de registrar `Supportability/Features/Instrumentation/OnRequire/` métrica para instrumentación basada en suscriptores. + * Se agregó el gancho de carga esm y el parche commonjs para trabajar con orchestrion-js. + * Se agregó instrumentación para las llamadas de cliente `@modelcontextprotocol/sdk` `client.callTool`, `client.readResource` y `client.getPrompt`. + * Se corrigió la lógica en torno a la detección de paquetes OTEL. + * Se actualizó `shimmer.setupSubscribers` para configurar y omitir correctamente los suscriptores que están deshabilitados. + +* [Agente de Node.js v13.2.1](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-2-1/) + + * Agente actualizado para emplear `@apm-js-collab/tracing-hooks` para el registro CJS/ESM para rastrear instrumentación basada en canales. \ No newline at end of file diff --git a/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-9-12-2025.mdx b/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-9-12-2025.mdx new file mode 100644 index 00000000000..cc764eedf32 --- /dev/null +++ b/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-9-12-2025.mdx @@ -0,0 +1,94 @@ +--- +subject: Docs +releaseDate: '2025-09-14' +version: 'September 08 - September 12, 2025' +translationType: machine +--- + +### Nuevos documentos + +* Se agregó documentación integral [del Modelo de madurez de observabilidad](/docs/new-relic-solutions/observability-maturity/) para brindar orientación para medir y mejorar las prácticas de observabilidad en cuatro áreas clave: tiempo de actividad empresarial, experiencia digital, excelencia en ingeniería y observabilidad inteligente. + +### Cambios importantes + +* [Configuración de agente PHP](/docs/apm/agents/php-agent/configuration/php-agent-configuration/) actualizada con amplias opciones de configuración nuevas para controles de ejemplificación e instrumentación del controlador de excepciones framework. + +### Cambios menores + +* [Introducción a los dashboards](/docs/query-your-data/explore-query-data/dashboards/introduction-dashboards/) actualizada con orientación mejorada para dashboard uso. +* Documentación [de gestión de dashboard](/docs/query-your-data/explore-query-data/dashboards/manage-your-dashboard/) mejorada con contenido simplificado para la gestión de JSON. +* Se corrigieron los enlaces rotos en la documentación [del plan de uso de New Relic](/docs/licenses/license-information/usage-plans/new-relic-usage-plan/). +* Se corrigió la configuración de depuración en la documentación [del agente resolución de problemas de .NET](/docs/apm/agents/net-agent/troubleshooting/debugging-net-windows/). + +### Notas de la versión + +* Mantener actualizado con nuestros últimos lanzamientos: + + * [Agente de Browser v1.297.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.297.0/): + + * Se evitaron cosechas tempranas durante el periodo de reintento para un mejor manejo de la limitación de velocidad. + * Se eliminó el meta atributo newrelic de la carga de repetición saliente para reducir los bytes facturables. + * Se corrigieron excepciones para cuerpos nulos que surgen de cosechas vacías. + + * [Agente PHP v12.1.0.26](/docs/release-notes/agent-release-notes/php-release-notes/php-agent-12-1-0-26/): + + * Se agregaron controles de ejemplificación basados en la decisión de ejemplificación de trazas de w3c ascendente. + * Se agregó una opción de configuración para omitir la instrumentación de los controladores de excepciones framework. + * Se solucionó una posible pérdida de memoria al llamar `newrelic_end_transaction(true)`. + * Se actualizó la versión de Golang a 1.25.1 para realizar mejoras de seguridad. + + * [Agente de Python v10.17.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-101700/): + + * Se agregó soporte para tareas personalizadas en Celery. + * Se agregó soporte para monitoreo Graphene-Django. + * Se agregó soporte para filtrado de middleware en Django. + * Se agregó soporte para la API de AWS Bedrock Converse. + * Se agregó soporte para el indicador de ejemplificación del encabezado W3CTraceParent. + + * [Agente de Java v8.24.0](/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8240/): + + * Se agregó soporte para MongoDB Reactive Streams 5.2.0 y posteriores. + * Se agregó soporte para Jedis 6. + * Se solucionó el problema de instrumentación doble de CouchBase. + * Se solucionó el problema de ajuste del encabezado de Spring WebClient 5.x. + + * [Agente de Node.js v13.3.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-3-0/): + + * Se agregó soporte para MCP `StreamableHTTPClientTransport`. + + * [Agente de Node.js v13.3.1](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-3-1/): + + * Se solucionó el fallo al establecer de forma predeterminada `requestParameters` en un objeto en `transaction.addRequestParameters`. + + * [Agente de Node.js v13.3.2](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-3-2/): + + * Se agregó código defensivo para obtener `protocol` en llamadas http salientes. + + * [Integración Kubernetes v3.45.1](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-45-1/): + + * Actualizado con las últimas mejoras y correcciones de errores. + + * [Administrador de trabajos v464](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-464/): + + * Se solucionó el problema en el que los clientes no podían extraer imágenes de un registro personalizado usando podman. + + * [Tiempo de ejecución del navegador de nodos v3.0.43](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.43/): + + * Se corrigieron las vulnerabilidades subyacentes de Ubuntu para abordar vulnerabilidades de seguridad. + + * [Aplicación móvil para iOS v6.9.12](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6102/): + + * Se corrigieron problemas de enlaces profundos para el panel y las alertas. + * Se solucionó el problema de identificación del tablero de CCU. + + * [Aplicación móvil para Android v5.30.7](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5307/): + + * Se agregaron correcciones de errores y mejoras. + + * [Agente de Flutter v1.1.14](/docs/release-notes/mobile-release-notes/flutter-release-notes/flutter-agent-1114/): + + * Se agregaron mejoras de estabilidad adicionales y correcciones de errores. + + * [Control de Pipeline Gateway v25.09.01](/docs/release-notes/pipeline-control-gateway-release-notes/pipeline-control-gateway-25-09-01/): + + * Se agregó una nueva versión con capacidades mejoradas de control de tuberías. \ No newline at end of file diff --git a/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-9-15-2025.mdx b/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-9-15-2025.mdx new file mode 100644 index 00000000000..779023f6642 --- /dev/null +++ b/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-9-15-2025.mdx @@ -0,0 +1,84 @@ +--- +subject: Docs +releaseDate: '2025-09-19' +version: 'September 15 - September 19, 2025' +translationType: machine +--- + +### Nuevos documentos + +* Integración AWS reestructurada para métrica: + + * Se agregó [integración manual con AWS](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/manual/) + * Se agregó [la integración de Terraform con AWS](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/terraform/) + * Se agregó [CloudFormation con integración de sondeo de API](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-and-api-polling/) + * Se agregó [una guía de migración del sondeo de API a CloudWatch Metric Streams](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/migrate-from-api-polling-to-cwms/) + +### Cambios importantes + +* [Documentación mejorada de transmisión de video y anuncios](/docs/streaming-video-&-ads/get-started-with-streaming-video-&-ads/) con actualizaciones de la estructura del agente independiente. + +### Cambios menores + +* [API de problemas de NerdGraph actualizada a través de GitHub](/docs/apis/nerdgraph/examples/nerdgraph-issues-api-via-github/) con documentación mejorada. +* [Integración actualizada de Microsoft Teams](/docs/alerts-applied-intelligence/notifications/notification-integrations/) con guía de configuración mejorada. +* Tipo de gráfico [de mapa de calor](docs/query-your-data/explore-query-data/use-charts/chart-types/#widget-heatmap) actualizado. +* [IntegraciónMySQL ](/docs/infrastructure/host-integrations/host-integrations-list/mysql-monitoring-integration/)actualizada con mejoras de tiempos para monitoreo QPM. +* Documentación [de gestión de cardinalidad](/docs/data-apis/ingest-apis/metric-api/cardinality-management/) mejorada con actualizaciones menores. +* Se actualizaron [los requisitos de compatibilidad del agente .NET](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements/) con las últimas versiones de biblioteca compatibles verificadas. +* Se corrigió la documentación de errores [en el código de control de tubería](docs/new-relic-control/pipeline-control/cloud-rules-api/). + +### Notas de la versión + +* [Monitoreo sintético actualizado con nuevas fechas de fin de vida útil para direcciones IP](/eol/2025/02/eol-01-31-25-synthetics-ip/). + +* Mantener actualizado con nuestros últimos lanzamientos: + + * [Agente de Java v8.24.0](/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8240/): + + * Se agregó soporte para MongoDB Reactive Streams 5.2.0 y posteriores. + * Se agregó soporte para Jedis 6. + * Se solucionó el problema de instrumentación doble de CouchBase. + * Se solucionó el problema de ajuste del encabezado de Spring WebClient 5.x. + + * [Agente de Python v10.17.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-101700/): + + * Se agregó soporte para tareas personalizadas en Celery. + * Se agregó soporte para monitoreo Graphene-Django. + * Se agregó soporte para filtrado de middleware en Django. + * Se agregó soporte para la API de AWS Bedrock Converse. + * Se agregó soporte para el indicador de ejemplificación del encabezado W3CTraceParent. + + * [agente de infraestructura v1.68.0](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/1680/): + + * Versión de Go actualizada a 1.25.0. + * Se actualizó la dependencia newrelic/nri-winservices a v1.3.0. + + * [Agente Browser v1.298.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.298.0/): + + * Interacción de navegación suave extendida para incluir tareas largas más allá del tiempo de modificación DOM. + * Se corrigió el LCP para informar la URL de la página original en lugar de la URL de la página actual durante las navegaciones suaves. + + * [Agente Browser v1.297.1](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.297.1/): + + * Se solucionó un problema por el cual la clase agregada Session Replay podía importar dos veces al usar newrelic.recordReplay Método API mientras se habilitaba la precarga. + + * [Agente de React Native v1.5.10](/docs/release-notes/mobile-release-notes/react-native-release-notes/react-native-agent-1510/): + + * Se actualizó el agente nativo de Android a la versión 7.6.9. + * Se actualizó el agente nativo de iOS a la versión 7.5.10. + + * [Agente iOS v7.5.10](/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-7510/): + + * Se solucionó un bloqueo que podía ocurrir al iniciar el agente. + + * [NRDOT v1.4.0](/docs/release-notes/nrdot-release-notes/nrdot-2025-09-18/): + + * Se agregó spanprocessor a nrdot-collector. + * Se actualizaron las versiones del componente OpenTelemetry de v0.131.0 a v0.132.0. + * Se agregó newrelic.service.type a la configuración de telemetría interna. + * Se habilitó la detección de host.name para EC2. + + * [Integración Kubernetes v3.45.2](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-45-2/): + + * Actualizado con las últimas mejoras y correcciones de errores. \ No newline at end of file diff --git a/src/i18n/content/es/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-759.mdx b/src/i18n/content/es/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-759.mdx index 2b2f216713d..9a4fe50de39 100644 --- a/src/i18n/content/es/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-759.mdx +++ b/src/i18n/content/es/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-759.mdx @@ -6,14 +6,6 @@ downloadLink: 'https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agen translationType: machine --- - - A partir de la versión 7.5.4 del SDK de iOS, Se implementó un cambio que hace que se informe el evento de excepción manejada que anteriormente se suprimió. - - Actualice al agente iOS de New Relic 7.5.9. Identificamos un error en la versión 7.5.8 del SDK de iOS que podría provocar una carga de datos incorrecta y se incluye una solución en el agente de iOS 7.5.9 de New Relic. liberar. - - Actualice al agente iOS de New Relic 7.5.9. Identificamos un error en la versión 7.5.7 del SDK de iOS que podría provocar un bloqueo al iniciar el agente, y se incluye una solución en el agente de New Relic para iOS 7.5.9. liberar. - - ## Corregido en esta versión * El agente se construyó empleando Xcode 16.4. diff --git a/src/i18n/content/es/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx b/src/i18n/content/es/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx new file mode 100644 index 00000000000..0f31403d612 --- /dev/null +++ b/src/i18n/content/es/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx @@ -0,0 +1,39 @@ +--- +subject: Browser agent +releaseDate: '2025-08-04' +version: 1.295.0 +downloadLink: 'https://www.npmjs.com/package/@newrelic/browser-agent' +features: + - Add error cause detection +bugs: + - Add monkey-patching warnings + - Calculate first and last timestamps from raw data +security: [] +translationType: machine +--- + +## v1.295.0 + +### Característica + +#### Agregar detección de causa de error + +Detectar y reportar la causa del atributo en el evento JavaScriptError capturado. Si la causa es una instancia de un Error, se capturará el rastreo de la stack, de lo contrario se informará el contenido en cadena de la causa. Esto se podrá consultar en JavaScriptError incluso bajo el atributo `cause`. + +### Corrección de errores + +#### Agregar advertencias sobre parches de mono + +Se agregó detección y advertencias para cuando los valores globales esperados fueron parcheados antes de que el agente se ejecutó en la página. Esto puede provocar comportamientos inesperados y la intención es informar a los clientes sobre este comportamiento. + +#### Calcular la primera y la última marca de tiempo a partir de datos sin procesar + +Cerciorar de que el agente calcule manualmente la primera y la última marca de tiempo de una carga de SessionReplay antes de la recolección para ayudar a mejorar la consistencia en el reproductor UI. + +## Declaración de apoyo + +New Relic recomienda que actualices el agente periódicamente para garantizar que obtengas las últimas características y beneficios de rendimiento. Las versiones anteriores ya no recibirán soporte cuando lleguen [al final de su vida útil](https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/browser-agent-eol-policy/). Las fechas de lanzamiento reflejan la fecha de publicación original de la versión del agente. + +Las nuevas versiones del agente del browser se lanzan a los clientes en pequeñas etapas a lo largo de un periodo de tiempo. Debido a esto, la fecha en que el lanzamiento esté disponible en su cuenta puede no coincidir con la fecha de publicación original. Consulte este [dashboard de estado](https://newrelic.github.io/newrelic-browser-agent-release/) para obtener más información. + +De acuerdo con nuestra [política de compatibilidad de navegadores](https://docs.newrelic.com/docs/browser/new-relic-browser/getting-started/compatibility-requirements-browser-monitoring/#browser-types), la versión 1.295.0 del agente del navegador se creó y probó con estos navegadores y rangos de versiones: Chrome 128-138, Edge 128-138, Safari 17-19 y Firefox 130-140. Para dispositivos móviles, la versión v1.295.0 fue creada y probada para Android OS 16 e iOS Safari 17-26. \ No newline at end of file diff --git a/src/i18n/content/es/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.296.mdx b/src/i18n/content/es/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.296.mdx new file mode 100644 index 00000000000..d281b28d57c --- /dev/null +++ b/src/i18n/content/es/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.296.mdx @@ -0,0 +1,34 @@ +--- +subject: Browser agent +releaseDate: '2025-08-19' +version: 1.296.0 +downloadLink: 'https://www.npmjs.com/package/@newrelic/browser-agent' +features: + - Harvest traces early +bugs: + - Remove event buffer inspection event +security: [] +translationType: machine +--- + +## versión 1.296.0 + +### Característica + +#### Cosecha temprana de traza + +Actualice el agente para manejar el rastreo de sesión de la misma manera que otras características manejan los datos a partir de [1.294.0](https://docs.newrelic.com/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.294.0/). permitiendo cosechas de 16kb de tamaño. + +### Corrección de errores + +#### Eliminar la inspección del búfer de eventos + +Elimina la inspección del búfer de eventos para evitar una pérdida de memoria al usar console.log con el detector de eventos de la ventana `newrelic`. + +## Declaración de apoyo + +New Relic recomienda que actualices el agente periódicamente para garantizar que obtengas las últimas características y beneficios de rendimiento. Las versiones anteriores ya no recibirán soporte cuando lleguen [al final de su vida útil](https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/browser-agent-eol-policy/). Las fechas de lanzamiento reflejan la fecha de publicación original de la versión del agente. + +Las nuevas versiones del agente del browser se lanzan a los clientes en pequeñas etapas a lo largo de un periodo de tiempo. Debido a esto, la fecha en que el lanzamiento esté disponible en su cuenta puede no coincidir con la fecha de publicación original. Consulte este [dashboard de estado](https://newrelic.github.io/newrelic-browser-agent-release/) para obtener más información. + +De acuerdo con nuestra [política de compatibilidad de navegadores](https://docs.newrelic.com/docs/browser/new-relic-browser/getting-started/compatibility-requirements-browser-monitoring/#browser-types), la versión 1.296.0 del agente del navegador se creó y probó con estos navegadores y rangos de versiones: Chrome 129-139, Edge 129-139, Safari 17-19 y Firefox 131-141. Para dispositivos móviles, la versión v1.296.0 fue creada y probada para Android OS 16 e iOS Safari 17-18.1. \ No newline at end of file diff --git a/src/i18n/content/es/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.297.mdx b/src/i18n/content/es/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.297.mdx new file mode 100644 index 00000000000..dceea8b093e --- /dev/null +++ b/src/i18n/content/es/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.297.mdx @@ -0,0 +1,27 @@ +--- +subject: Browser agent +releaseDate: '2025-09-17' +version: 1.297.1 +downloadLink: 'https://www.npmjs.com/package/@newrelic/browser-agent' +features: [] +bugs: + - Prevent double import of Session Replay aggregate class +security: [] +translationType: machine +--- + +## v1.297.1 + +### Corrección de errores + +#### Evitar la doble importación de la clase agregada Session Replay + +Corrige un problema que se encontró donde la clase agregada Session Replay podía importar dos veces al usar el método API newrelic.recordReplay mientras se habilitaba la precarga. + +## Declaración de apoyo + +New Relic recomienda que actualices el agente periódicamente para garantizar que obtengas las últimas características y beneficios de rendimiento. Las versiones anteriores ya no recibirán soporte cuando lleguen [al final de su vida útil](https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/browser-agent-eol-policy/). Las fechas de lanzamiento reflejan la fecha de publicación original de la versión del agente. + +Las nuevas versiones del agente del browser se lanzan a los clientes en pequeñas etapas a lo largo de un periodo de tiempo. Debido a esto, la fecha en que el lanzamiento esté disponible en su cuenta puede no coincidir con la fecha de publicación original. Consulte este [dashboard de estado](https://newrelic.github.io/newrelic-browser-agent-release/) para obtener más información. + +De acuerdo con nuestra [política de compatibilidad de navegadores](https://docs.newrelic.com/docs/browser/new-relic-browser/getting-started/compatibility-requirements-browser-monitoring/#browser-types), la versión 1.297.1 del agente del navegador se creó y probó con estos navegadores y rangos de versiones: Chrome 130-140, Edge 130-140, Safari 17-19 y Firefox 132-142. Para dispositivos móviles, la versión v1.297.1 fue creada y probada para Android OS 16 e iOS Safari 17-18.5. \ No newline at end of file diff --git a/src/i18n/content/es/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.mdx b/src/i18n/content/es/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.mdx new file mode 100644 index 00000000000..06eefb60757 --- /dev/null +++ b/src/i18n/content/es/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.mdx @@ -0,0 +1,10 @@ +--- +subject: Node API runtime +releaseDate: '2025-07-29' +version: 1.2.122 +translationType: machine +--- + +### Correcciones + +* Se corrigieron las vulnerabilidades de datos de formulario y las vulnerabilidades subyacentes de Ubuntu para abordar vulnerabilidades de seguridad en los tiempos de ejecución de Node API. \ No newline at end of file diff --git a/src/i18n/content/es/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.mdx b/src/i18n/content/es/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.mdx new file mode 100644 index 00000000000..fdfdc17442f --- /dev/null +++ b/src/i18n/content/es/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.mdx @@ -0,0 +1,10 @@ +--- +subject: Node browser runtime +releaseDate: '2025-07-29' +version: 3.0.39 +translationType: machine +--- + +### Mejoras + +* Se corrigieron las vulnerabilidades de datos de formulario y las vulnerabilidades subyacentes de Ubuntu para abordar vulnerabilidades de seguridad en los tiempos de ejecución de Node Browser. \ No newline at end of file diff --git a/src/i18n/content/es/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.53.mdx b/src/i18n/content/es/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.53.mdx new file mode 100644 index 00000000000..ec1e32db231 --- /dev/null +++ b/src/i18n/content/es/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.53.mdx @@ -0,0 +1,10 @@ +--- +subject: Ping Runtime +releaseDate: '2025-07-29' +version: 1.53.0 +translationType: machine +--- + +### Mejoras + +* Se corrigieron vulnerabilidades relacionadas con `common-lang3` Java y Ubuntu para abordar problemas de seguridad en el tiempo de ejecución de Ping. \ No newline at end of file diff --git a/src/i18n/content/es/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.54.mdx b/src/i18n/content/es/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.54.mdx new file mode 100644 index 00000000000..65d952ef7ac --- /dev/null +++ b/src/i18n/content/es/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.54.mdx @@ -0,0 +1,10 @@ +--- +subject: Ping Runtime +releaseDate: '2025-08-13' +version: 1.54.0 +translationType: machine +--- + +### Mejoras + +* Se corrigieron vulnerabilidades relacionadas con Ubuntu para abordar problemas de seguridad en el tiempo de ejecución de Ping. \ No newline at end of file diff --git a/src/i18n/content/fr/docs/accounts/accounts-billing/new-relic-one-pricing-billing/add-on-billing.mdx b/src/i18n/content/fr/docs/accounts/accounts-billing/new-relic-one-pricing-billing/add-on-billing.mdx new file mode 100644 index 00000000000..6f47050af84 --- /dev/null +++ b/src/i18n/content/fr/docs/accounts/accounts-billing/new-relic-one-pricing-billing/add-on-billing.mdx @@ -0,0 +1,28 @@ +--- +title: Facturation complémentaire (en option) +tags: + - Accounts + - Accounts and billing + - New Relic pricing and billing +metaDescription: Add-ons are an optional billing factor +freshnessValidatedDate: '2024-10-23T00:00:00.000Z' +translationType: machine +--- + +En plus des principaux facteurs de facturation de GB Ingested et d'utilisateurs facturables, vous pouvez également utiliser des modules complémentaires facturables optionels pour étendre votre expérience avec New Relic. + +* **Calculateur avancé (anciennement calculateur complémentaire)**: ce module complémentaire s'applique à la facturation basée sur l'utilisation pour les actions que vous exécutez en relation avec CodeStream, Live Archives et d'autres fonctionnalités mises à disposition. Vous êtes mesuré et facturé en fonction de votre utilisation des [CCU avancés](/docs/licenses/license-information/product-definitions/new-relic-one-pricing-definitions/#compute-capacity-unit). + + + Votre utilisation de CodeStream sous calculateur avancé (Advanced Compute) entraînera des frais CCU, quel que soit le type d'utilisateur. Cela signifie que l'utilisateur de base gratuit peut accéder à la fonctionnalité de calcul avancée et encourir des frais pour les CCU avancés. + + +* **Centre de données de l'UE pour les données d'origine (Original Data) ou les données Plus (Data Plus)**: ce module complémentaire s'applique à votre option de données (données d'origine ou données Plus) lorsque vous sélectionnez l'Union européenne comme région de données, selon les disponibilités. + +* **Conservation prolongée des données d'origine ou des données plus** : ce module complémentaire s'applique si vous dépassez la durée par défaut pendant laquelle vos données sont conservées. Cela s'applique à toutes vos données, pas seulement aux logs, et constitue une bonne option si vous devez effectuer de nombreuses petites requêtes ou effectuer des requêtes sur de gros volumes de données. + +* **Live Archives** : Prolongez la durée de stockage de vos logs jusqu'à sept ans. Live Archives nécessite également Advanced Compute. + +* **New Relic Synthetics Checks** : Ce module complémentaire s'applique si vos contrôles dépassent le nombre par défaut de contrôles de monitoring synthétiques. + +* **Security RX**: cette fonctionnalité est incluse avec Data Plus, mais le module complémentaire s'applique si vous utilisez la fonctionnalité Security RX sans Data Plus. \ No newline at end of file diff --git a/src/i18n/content/fr/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing.mdx b/src/i18n/content/fr/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing.mdx new file mode 100644 index 00000000000..d92819d86c2 --- /dev/null +++ b/src/i18n/content/fr/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing.mdx @@ -0,0 +1,354 @@ +--- +title: 'Données : Facturation et règles' +tags: + - Accounts + - Accounts and billing + - New Relic pricing and billing +metaDescription: 'For New Relic pricing, an explanation of how data ingest is calculated for billing purposes.' +freshnessValidatedDate: '2024-10-23T00:00:00.000Z' +translationType: machine +--- + +Pour la tarification New Relic, les données ingérées par votre organisation New Relic constituent un facteur de facturation. + +## Informez-vous sur les coûts [#costs] + +Si vous n'êtes pas encore client New Relic et que vous êtes curieux de connaître les coûts, consultez d'abord [notre page de tarification principale](https://newrelic.com/pricing). Si vous êtes déjà client, continuez à lire pour en savoir plus sur la facturation de l'ingestion de données. + +## Afficher l'ingestion de données dans l'UI [#ui] + +Pour savoir comment trouver les informations d'utilisation et de facturation dans l'UI, consultez [UI de facturation](/docs/accounts/accounts-billing/general-account-settings/introduction-account-settings). + +Pour savoir comment afficher et gérer votre ingestion de données, consultez [Gérer l'ingestion](/docs/data-apis/manage-data/manage-data-coming-new-relic). + +## Options de données : Données Plus et originales [#data-prices] + +Le prix de votre organisation par Go de données ingérées varie en fonction de l'option de données dont dispose votre organisation : **Data Plus** ou notre option **Original Data**. L'option Data Plus offre des fonctionnalités de données avancées pour des performances, une évolutivité, une sécurité et une gouvernance optimisées. Une organisation New Relic ne peut avoir qu'une seule option à la fois. + +Voici un tableau comparatif des deux options. Les prix et les limites sont mensuels et les prix sont en USD. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Fonctionnalité/aptitude + + **Original Data** option + + **Data Plus** option + + Plus de détails sur la fonctionnalité +
+ [Éditions](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing/#editions) + + Toutes les éditions + + Nécessite Standard, Pro ou Enterprise + + (Nous notons ci-dessous si une fonctionnalité est spécifique à une édition) + +
+ Limite de données gratuites + + 100 Go ingérés + + 100 Go ingérés + +
+ Prix des données
(au-delà de la limite gratuite) +
+ 0,40 USD/Go ingéré + + 0,60 USD/Go ingéré + +
+ Limite gratuite de rétention des données
([varie selon le type de données](/docs/data-apis/manage-data/manage-data-retention)) +
+ Défaut d'au moins 8 jours + + 90 jours supplémentaires en cas de défaut + +
+ Prix pour chaque tranche de 30 jours de rétention supplémentaire
(au-delà de la limite gratuite) +
+ +0,05$/Go + + +0,05$/Go + +
+ Prix supplémentaire pour stocker des données dans [data centerde l'UE](/docs/accounts/accounts-billing/account-setup/choose-your-data-center)
+
+ +0,05$/Go + + +0,05$/Go + + Les données sont stockées par défaut dans le data center américain. +
+ [Limite de requêtes](/docs/query-your-data/nrql-new-relic-query-language/get-started/rate-limits-nrql-queries/#query-limits)maximale + + Jusqu'à 20 milliards de points de données par minute + + Jusqu'à 60 B de points de données par minute + +
+ [Durée maximale de la requête](/docs/query-your-data/nrql-new-relic-query-language/get-started/rate-limits-nrql-queries/#query-duration) + + 1 minute + + Jusqu'à 10 minutes + +
+ Choix du fournisseur de cloud + + Fournisseur de cloud unique + + Azure ou plusieurs fournisseurs de cloud + + Choisissez votre fournisseur cloud préféré pour votre charge de travail d'observabilité afin d'aligner votre stockage de télémétrie avec votre modèle de déploiement d'ingénierie et votre préférence cloud . +
+ [Obfuscation des logs](/docs/logs/ui-data/obfuscation-ui/) + + Masquer [automatiquement](/docs/logs/get-started/new-relics-log-management-security-privacy/#log-obfuscation) les modèles de carte de crédit et de numéro de sécurité sociale connus dans les logs. + + Créez et suivez des règles directement dans l'UI et [masquez ou hachez](/docs/logs/ui-data/obfuscation-ui/) les données log sensibles. + +
+ [New Relic gestion des vulnérabilités](/docs/vulnerability-management/overview)
(plateforme utilisateur complète uniquement) +
+ +0,10 $/Go
(au-delà de la limite gratuite) +
+ Standard, Pro et Entreprise + + Identifiez les vulnérabilités et traitez les risques à chaque étape du cycle de vie du logiciel. +
+ Admissibilité [au programme FedRAMP Modéré](/docs/security/security-privacy/compliance/fedramp-compliant-endpoints) et [à la loi HIPAA](/docs/security/security-privacy/compliance/hipaa-readiness-new-relic) + + + + Enterprise + + Atteignez la conformité en matière de sécurité grâce à une configuration qui vous aide à répondre à vos exigences FedRAMP et HIPAA. +
+ [données de streaming export](/docs/apis/nerdgraph/examples/nerdgraph-streaming-export) + + + + Standard, Pro et Entreprise + + Configurez des règles pour exporter simultanément des données télémétriques vers le stockage AWS ou Azure de votre choix. Des frais d’exportation supplémentaires vers le fournisseur de cloud s’appliqueront. +
+ [Exportation de données historiques](/docs/apis/nerdgraph/examples/nerdgraph-historical-data-export) + + + + Standard, Pro et Entreprise + + Exécutez des requêtes plus volumineuses sans délai d'expiration pour l'analyse historique et la modélisation, le stockage à long terme et l'intégration avec d'autres plateformes d'analyse de données. +
+ Service natif New Relic d'Azure + + + + Standard, Pro et Entreprise
([avec quelques limitations](#azure-native-data-plus)) +
+
+ +Pour voir une comparaison côte à côte de Data Plus et de notre option de données originales, consultez [notre fiche technique Data Plus](https://newrelic.com/resources/datasheets/data-plus). + +Intéressé par Data Plus ? Voir [Mise à niveau vers Data Plus](#upgrade-data-plus). + +### Détails du service Azure Native New Relic [#azure-native-data-plus] + +Avec le [serviceAzure Native New Relic ](/docs/infrastructure/microsoft-azure-integrations/get-started/azure-native), vous pouvez collecter et stocker vos données télémétriques pour les applications et infrastructure directement dans Azure. Cette fonctionnalité est incluse avec Data Plus, mais avec les limitations suivantes : + +* Disponible uniquement dans la région data center des États-Unis +* L'éligibilité FedRAMP Modéré/HIPAA n'est pas disponible +* L'exportation des données historiques n'est pas disponible + +## Mise à niveau vers Data Plus [#upgrade-data-plus] + +Pour passer à Data Plus, accédez à l'[UI**Data retention** ](/docs/data-apis/manage-data/manage-data-retention/#adjust-retention)dans le hub de gestion des données et cliquez sur **Upgrade retention**. + +* Remarque : vous pouvez voir un bouton **Edit data retention** , mais il est différent du bouton **Upgrade retention**. +* Pour voir le bouton **Upgrade retention** , vous devez disposer [des autorisations de facturation](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts/#admin-settings). Si vous remplissez les conditions et que vous ne voyez toujours pas l'option **Upgrade retention** , contactez votre représentant de compte New Relic. + +## Qu'est-ce qui est considéré comme des Go ingérés facturables ? [#usage-calculation] + +Dans le contexte du [plan tarifaire New Relic](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing), les « données ingérées » font référence aux données enregistrées dans New Relic par votre organisation après l'application de diverses règles de découpage et de transformation des données. En d’autres termes, ce n’est pas la quantité de données brutes envoyées à New Relic qui compte, mais la taille des données qui finissent par être stockées. + +En général, les données que nous générons pour fournir notre fonctionnalité ne comptent pas dans vos Go ingérés. Voici quelques exemples de fonctionnalités et de données liées aux fonctionnalités qui ne sont pas comptabilisées dans les Go ingérés : + +* [Fonctionnalité d'alerte de base](/docs/alerts-applied-intelligence/new-relic-alerts/learn-alerts/alerts-concepts-workflow). Par exemple, `NrAiIncident`, un événement utilisé pour générer ces fonctionnalités, ne compte pas dans les Go ingérés. +* Données créées à partir de données brutes agrégées (par exemple, [données infrastructure agrégées](/docs/data-apis/manage-data/manage-data-retention/#infrastructure-data) ou [données métriques dimensionnelles](/data-apis/manage-data/manage-data-retention/#dimensional-metrics)). +* [métriques dorées](/docs/apis/nerdgraph/examples/golden-metrics-entities-nerdgraph-api-tutorial) (pour en savoir plus sur les métriques dorées, voir nos [définitions d'entités](https://github.com/newrelic/entity-definitions)). +* Contrôles de monitoring synthétiques. Pour plus de détails sur la facturation des produits synthétiques, consultez [Limites et tarifsSynthetics ](/docs/synthetics/synthetic-monitoring/using-monitors/monitor-limits). +* Données de suivi d’utilisation et de facturation (par exemple, `NrConsumption`). +* Données relatives à l’administration du compte (par exemple, `NrIntegrationError`, `NrAuditEvent`). + +Pour comprendre votre utilisation, consultez l'[ UI d'utilisation](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing#usage-ui). + +## Autres détails de calcul [#calculation-details] + +* Dans le contexte de notre modèle de tarification, un Go est défini comme 1 milliard d’octets. +* Le nombre mensuel de Go ingérés est arrondi à l'entier inférieur le plus proche. Par exemple, si votre organisation utilise 100,9 Go au cours d'un mois, cela est comptabilisé comme 100 Go. + +## Édition gratuite [#free-tier-limits] + +Pour plus de détails sur GB Ingested pour notre édition gratuite, voir [Édition gratuite](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing/#free). + +## En savoir plus [#related-docs] + +* Pour en savoir plus sur la gestion des Go ingérés, consultez [Gérer l'ingestion de données](/docs/data-apis/manage-data/manage-data-coming-new-relic). +* Pour savoir comment requêter l'utilisation, voir [requête et alerte sur l'utilisation](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts). \ No newline at end of file diff --git a/src/i18n/content/fr/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts.mdx b/src/i18n/content/fr/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts.mdx index 85677ed8a83..6932f978e7f 100644 --- a/src/i18n/content/fr/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts.mdx +++ b/src/i18n/content/fr/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts.mdx @@ -21,10 +21,11 @@ Gardez les points suivants à l’esprit lorsque vous utilisez l’ UI d’utili ## Requête d'utilisation d'ingestion de données [#data-queries] -L'[UI d'utilisation](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing#usage-ui) affiche vos données ingérées au fil du temps. Si vous avez besoin de plus de détails que ceux fournis par l'UI , vous pouvez utiliser une variété de requêtes NRQL . Les exemples ci-dessous incluent deux types de données : +The [usage UI](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing#usage-ui) displays your data ingest over time. If you need more detail than the UI provides, you can use a variety of NRQL queries. The examples below include the following data types: * `NrConsumption`:Utilisez ceci pour approfondir les détails de votre utilisation heure par heure. C'est moins utile comme substitut à votre facture. -* `NrMTDConsumption`:Utilisez ceci pour voir une bonne approximation de votre utilisation mensuelle agrégée. +* `NrMTDConsumption`: Use this to see an approximation of your monthly aggregated usage. +* `NrCustomerMTDConsumption`: Use this to see an approximation of a customer's monthly aggregated usage. @@ -60,7 +61,7 @@ L'[UI d'utilisation](/docs/accounts/accounts-billing/new-relic-one-pri - Cette requête affiche les données ingérées complètes de la plateforme actuelle. En d'autres termes, il indique le montant qui vous serait facturé pour vos données pour ce mois si vous étiez facturé maintenant. Les informations sur les frais d'utilisation sont calculées toutes les heures et leur génération prend environ 3 heures. Si aucune valeur n'est affichée, veuillez interroger les données d'il y a 4 heures en utilisant « DEPUIS 4 heures ». + This query shows the current full platform ingested data. In other words, it shows how much you'd be billed for your data for that month if you were billed right now. Usage fee information is calculated hourly and takes approximately 3 hours to generate. If no values are displayed, please query data from 4 hours ago using "SINCE 4 hours ago." ```sql FROM NrMTDConsumption SELECT latest(GigabytesIngested) @@ -73,6 +74,72 @@ L'[UI d'utilisation](/docs/accounts/accounts-billing/new-relic-one-pri +## Compute usage queries [#compute-queries] + +The [usage UI](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing#usage-ui) displays your compute usage over time. If you need more detail than the UI provides, you can use a variety of NRQL queries. The examples below include the following data types: + +* `NrConsumption`:Utilisez ceci pour approfondir les détails de votre utilisation heure par heure. C'est moins utile comme substitut à votre facture. +* `NrMTDConsumption`: Use this to see an approximation of your monthly aggregated compute usage. +* `NrCustomerMTDConsumption`: Use this to see an approximation of a customer's monthly aggregated usage. + + + + This query totals your billable core compute usage, and displays a daily value for the past three months: + + ```sql + FROM NrConsumption SELECT sum(consumption) + WHERE metric = 'CoreCCU' + SINCE 3 months ago TIMESERIES 1 day + ``` + + + + This query totals your billable advanced compute usage, and displays a daily value for the past three months: + + ```sql + FROM NrConsumption SELECT sum(consumption) + WHERE metric = 'AdvancedCCU' + SINCE 3 months ago TIMESERIES 1 day + ``` + + + + This query totals your billable core compute usage, and displays a daily value for the past three months faceted by the capability: + + ```sql + FROM NrConsumption SELECT sum(consumption) + WHERE metric = 'CoreCCU' SINCE 3 months ago + FACET dimension_productCapability TIMESERIES 1 day + ``` + + + + This query totals your billable advanced compute usage, and displays a daily value for the past three months faceted by the capability: + + ```sql + FROM NrConsumption SELECT sum(consumption) + WHERE metric = 'AdvancedCCU' SINCE 3 months ago + FACET dimension_productCapability TIMESERIES 1 day + ``` + + + + This query shows the current full platform core compute usage. In other words, it shows how much you'd be billed for your data for that month if you were billed right now. Usage fee information is calculated hourly and takes approximately 3 hours to generate. If no values are displayed, please query data from 4 hours ago using "SINCE 4 hours ago." + + ```sql + FROM NrMTDConsumption select latest(consumption) where metric = 'CoreCCU' since 1 day ago + ``` + + + + This query shows the current full platform advanced compute usage. In other words, it shows how much you'd be billed for your data for that month if you were billed right now. Usage fee information is calculated hourly and takes approximately 3 hours to generate. If no values are displayed, please query data from 4 hours ago using "SINCE 4 hours ago." + + ```sql + FROM NrMTDConsumption select latest(consumption) where metric = 'AdvancedCCU' since 1 day ago + ``` + + + ## Limites d'ingestion et de requête de données [#data-limits] Pour plus d'informations sur les limites d'ingestion de données et les limites de requête, consultez [Limites de données New Relic](/docs/data-apis/manage-data/view-system-limits). @@ -81,7 +148,7 @@ Pour plus d'informations sur les limites d'ingestion de données et le Pour un affichage de votre nombre d'utilisateurs, consultez l'[ UI d'utilisation](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing#usage-ui). Si vous avez besoin de plus de détails, vous pouvez utiliser l'exemple de requête NRQL ci-dessous. Pour plus de détails sur la manière dont les utilisateurs sont calculés, voir [Calculs des utilisateurs facturables](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/user-count-billing). -La plupart des organisations New Relic ont la possibilité d'ajouter un utilisateur principal. Cette section comprend des requêtes qui fonctionneront pour ces organisations. Si vous faites partie d'une organisation plus ancienne qui n'a pas [choisi de déverrouiller l'utilisateur principal](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing#core-acceptance), consultez [la requête pour une organisation sans utilisateur principal](#queries-non-core). +Most New Relic organizations have the ability to add core users. This section includes queries that will work for those organizations. If you're in an older organization that hasn't [opted in to unlock core users](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing#core-acceptance), see [Queries for organizations without core users](#queries-non-core). Voici quelques règles pour interroger votre utilisateur : @@ -336,7 +403,7 @@ Voici quelques exemples de conditions d'alerte NRQL .
- Cette requête créera une alerte lorsque votre utilisation dépasse le seuil mensuel fixe de Go : + This query will create an alert when your usage exceeds a fixed monthly threshold for GBs: ```sql FROM NrMTDConsumption @@ -447,5 +514,5 @@ Pour en savoir plus sur l’estimation de l’utilisation, consultez [notre arti Voici quelques détails techniques sur le fonctionnement de `bytecountestimate()` : * Il existe plusieurs types de données qui [ne sont pas comptabilisées dans l'ingestion](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing/#usage-calculation) mais qui sont renvoyées par la fonction `bytecountestimate()`. Cela signifie que cette fonction affiche parfois **more** données qui ne sont réellement comptabilisées dans votre utilisation. Il se peut que le montant affiché soit inférieur dans de rares cas, mais si c'est le cas, il ne sera que légèrement inférieur. -* Certaines données télémétriques rapportées par une entité partagent un attribut commun (par exemple, un attribut concernant votre compte New Relic ). Nous ne comptons pas l'attribut dupliqué dans votre ingestion, mais `bytecountestimate()` compte ces attributs. Cela peut parfois entraîner une grande différence entre une requête `bytecountestimate()` et votre utilisation réelle. +* Some telemetry data reported from an entity shares common attributes (for example, attributes about your New Relic account). We don't count the duplicated attributes towards your ingest, but `bytecountestimate()` does count those attributes. This can sometimes result in a large discrepancy between a `bytecountestimate()` query and your actual usage. * Nos , et rapportent un type de données appelé [données d'intervalle de temps métrique](/docs/data-apis/understand-data/new-relic-data-types/#timeslice-data). Ces données ne sont pas stockées dans NRDB comme nos autres types de données, et donc essayer d'utiliser `bytecountestimate()` sur ces données peut entraîner des résultats déroutants. Lors de l'interrogation de ces données, nous vous recommandons de les facetter par nom d'application et non par nom de métrique. \ No newline at end of file diff --git a/src/i18n/content/fr/docs/alerts/admin/rules-limits-alerts.mdx b/src/i18n/content/fr/docs/alerts/admin/rules-limits-alerts.mdx index 447d5395497..b53359eb6dc 100644 --- a/src/i18n/content/fr/docs/alerts/admin/rules-limits-alerts.mdx +++ b/src/i18n/content/fr/docs/alerts/admin/rules-limits-alerts.mdx @@ -345,6 +345,39 @@ N/A * À part ça : 5 000 + + + + + + Email addresses per destination + + + + 1 email address + + + + * Free accounts: 5 email addresses per destination + * Paid accounts: 150 email addresses per destination + + + + + + + + Email addresses per organization per 24 hours + + + + N/A + + + + 1000 unique email addresses (applies to all users) + + diff --git a/src/i18n/content/fr/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx b/src/i18n/content/fr/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx index 66c42ad9449..19514d3f8c1 100644 --- a/src/i18n/content/fr/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx +++ b/src/i18n/content/fr/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx @@ -269,24 +269,24 @@ Après installation, l' agent s'instrumente automatiquement avec notre | --------------------------------- | -------------------------------- | ------------------------ | -------------------------------------- | | `@apollo/gateway` | 2.3.0 | 2.11.2 | `@newrelic/apollo-server-plugin@1.0.0` | | `@apollo/server` | 4.0.0 | 5.0.0 | `@newrelic/apollo-server-plugin@2.1.0` | -| `@aws-sdk/client-bedrock-runtime` | 3.474.0 | 3.886.0 | 11.13.0 | -| `@aws-sdk/client-dynamodb` | 3.0.0 | 3.886.0 | 8.7.1 | -| `@aws-sdk/client-sns` | 3.0.0 | 3.886.0 | 8.7.1 | -| `@aws-sdk/client-sqs` | 3.0.0 | 3.886.0 | 8.7.1 | -| `@aws-sdk/lib-dynamodb` | 3.377.0 | 3.886.0 | 8.7.1 | +| `@aws-sdk/client-bedrock-runtime` | 3.474.0 | 3.894.0 | 11.13.0 | +| `@aws-sdk/client-dynamodb` | 3.0.0 | 3.894.0 | 8.7.1 | +| `@aws-sdk/client-sns` | 3.0.0 | 3.894.0 | 8.7.1 | +| `@aws-sdk/client-sqs` | 3.0.0 | 3.894.0 | 8.7.1 | +| `@aws-sdk/lib-dynamodb` | 3.377.0 | 3.894.0 | 8.7.1 | | `@aws-sdk/smithy-client` | 3.47.0 | 3.374.0 | 8.7.1 | | `@azure/functions` | 4.7.0 | 4.8.0 | 12.18.0 | | `@elastic/elasticsearch` | 7.16.0 | 9.1.1 | 11.9.0 | -| `@google/genai` | 1.1.0 | 1.19.0 | 12.21.0 | -| `@grpc/grpc-js` | 1.4.0 | 1.13.4 | 8.17.0 | +| `@google/genai` | 1.1.0 | 1.20.0 | 12.21.0 | +| `@grpc/grpc-js` | 1.4.0 | 1.14.0 | 8.17.0 | | `@hapi/hapi` | 20.1.2 | 21.4.3 | 9.0.0 | | `@koa/router` | 12.0.1 | 14.0.0 | 3.2.0 | -| `@langchain/core` | 0.1.17 | 0,3,75 | 11.13.0 | -| `@modelcontextprotocol/sdk` | 1.13.0 | 1.17.5 | 13.2.0 | +| `@langchain/core` | 0.1.17 | 0.3.77 | 11.13.0 | +| `@modelcontextprotocol/sdk` | 1.13.0 | 1.18.1 | 13.2.0 | | `@nestjs/cli` | 9.0.0 | 11.0.10 | 10.1.0 | | `@opensearch-project/opensearch` | 2.1.0 | 3.5.1 | 12.10.0 | -| `@prisma/client` | 5.0.0 | 6.16.0 | 11.0.0 | -| `@smithy/smithy-client` | 2.0.0 | 4.6.1 | 11.0.0 | +| `@prisma/client` | 5.0.0 | 6.16.2 | 11.0.0 | +| `@smithy/smithy-client` | 2.0.0 | 4.6.3 | 11.0.0 | | `amqplib` | 0.5.0 | 0.10.9 | 2.0.0 | | `aws-sdk` | 2.2.48 | 2.1692.0 | 6.2.0 | | `bluebird` | 2.0.0 | 3.7.2 | 1.27.0 | @@ -294,7 +294,7 @@ Après installation, l' agent s'instrumente automatiquement avec notre | `cassandra-driver` | 3.4.0 | 4.8.0 | 1.7.1 | | `connect` | 3.0.0 | 3.7.0 | 2.6.0 | | `express` | 4.15.0 | 5.1.0 | 2.6.0 | -| `fastify` | 3.0.0 | 5.6.0 | 8.5.0 | +| `fastify` | 3.0.0 | 5.6.1 | 8.5.0 | | `generic-pool` | 3.0.0 | 3.9.0 | 0.9.0 | | `ioredis` | 4.0.0 | 5.7.0 | 1.26.2 | | `kafkajs` | 2.0.0 | 2.2.4 | 11.19.0 | @@ -302,14 +302,14 @@ Après installation, l' agent s'instrumente automatiquement avec notre | `koa-route` | 3.0.0 | 4.0.1 | 3.2.0 | | `koa-router` | 12.0.1 | 14.0.0 | 3.2.0 | | `memcached` | 2.2.0 | 2.2.2 | 1.26.2 | -| `mongodb` | 4.1.4 | 6.19.0 | 1.32.0 | +| `mongodb` | 4.1.4 | 6.20.0 | 1.32.0 | | `mysql` | 2.16.0 | 2.18.1 | 1.32.0 | -| `mysql2` | 2.0.0 | 3.14.5 | 1.32.0 | -| `next` | 13.4.19 | 15.5.2 | 12.0.0 | -| `openai` | 4.0.0 | 5.20.1 | 11.13.0 | +| `mysql2` | 2.0.0 | 3.15.0 | 1.32.0 | +| `next` | 13.4.19 | 15.5.3 | 12.0.0 | +| `openai` | 4.0.0 | 5.22.0 | 11.13.0 | | `pg` | 8.2.0 | 8.16.3 | 9.0.0 | | `pg-native` | 3.0.0 | 3.5.2 | 9.0.0 | -| `pino` | 8.0.0 | 9.9.5 | 8.11.0 | +| `pino` | 8.0.0 | 9.11.0 | 8.11.0 | | `q` | 1.3.0 | 1.5.1 | 1.26.2 | | `redis` | 3.1.0 | 5.8.2 | 1.31.0 | | `restify` | 11.0.0 | 11.1.0 | 2.6.0 | diff --git a/src/i18n/content/fr/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation.mdx b/src/i18n/content/fr/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation.mdx new file mode 100644 index 00000000000..b4b4bbb9208 --- /dev/null +++ b/src/i18n/content/fr/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation.mdx @@ -0,0 +1,70 @@ +--- +title: Intégration via CloudFormation et flux de métriques CloudWatch +tags: + - Integration via CloudFormation + - AWS metric integration + - Amazon integrations + - AWS integrations + - Integration with CloudWatch Metric Streams via CloudFormation +metaDescription: Integrate New Relic with AWS services using CloudFormation templates to automate the setup of CloudWatch Metric Streams for metrics ingestion. +freshnessValidatedDate: never +translationType: machine +--- + +Pour une intégration transparente de votre compte AWS avec New Relic, il s'agit du processus d'intégration le plus recommandé. Vous pouvez utiliser l'interrogation API pour les services non pris en charge par flux de métriques CloudWatch. + +## Prérequis [#prerequisites] + +Avant de commencer à intégrer votre compte AWS à New Relic, assurez-vous de remplir les conditions préalables suivantes : + +* **Une [clé de licence](https://one.newrelic.com/api-keys)New Relic**: vous aurez besoin d’une clé de licence pour connecter vos services AWS à votre compte New Relic. +* **[Autorisations](https://docs.aws.amazon.com/ARG/latest/userguide/gettingstarted-prereqs-permissions.html)** pour déployer de nouvelles ressources AWS et **[rôles IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html)**: vous aurez besoin de cette autorisation pour votre compte AWS. +* **[Autorisations](/docs/accounts/accounts-billing/new-relic-one-user-management/user-permissions/#infrastructure)** pour l'intégration cloud: vous aurez besoin de ces autorisations pour votre compte New Relic. + +## Étapes d'intégration [#integration-steps] + +Pour intégrer votre compte AWS à New Relic à l'aide de CloudFormation et de flux de métriques CloudWatch, suivez ces étapes : + +1. Accédez à [**Infrastructure > AWS**](https://one.newrelic.com/infra/infrastructure/cloud-aws). + +2. Sélectionnez le bon compte. + +3. Cliquez sur **Set up integration**. + +4. Suivez les instructions sur chaque écran et remplissez les champs qui vous concernent. Pour cette intégration, choisissez les options suivantes dans les écrans donnés : + + 1. **Choose Data type(s)**: Metrics + 2. **Choose a setup method**: Automate AWS with CloudFormation (Recommended) + 3. **Choose a metrics integration type**: CloudWatch Metric Stream (Recommended) + +5. Si vous utilisez l'un des services qui ne sont pas pris en charge dans flux de métriques CloudWatch, sur la page **Choose a metrics integration type**, sélectionnez **Yes** à la troisième étape pour l'interrogation de l'API et continuez. + + AWS Integration with CWMS and API Polling + +
+ Intégration CWMS des services AWS avec interrogation API sélectionnée pour les services non pris en charge. +
+ + Effectuez la configuration nécessaire comme indiqué sur la page **Enable API Polling (optional)** et continuez. + +6. Auto-discovery détecte et visualise automatiquement les relations entre vos entités AWS sur des cartes et exploite quelques autres flexibilités. Pour plus de détails, reportez-vous [à Découverte automatique de l'entité AWS](/docs/infrastructure/amazon-integrations/connect/set-up-auto-discovery-of-aws-entities/). Si vous souhaitez cette fonctionnalité, activez-la sur la page **Enable Auto Discovery (optional)** et continuez. + +7. Cliquez sur **Launch your CloudFormation in AWS**. Le modèle CloudFormation s'ouvre dans votre console AWS avec les paramètres configurés en fonction de vos sélections dans New Relic. Aucune modification supplémentaire n'est donc nécessaire, sauf si vous souhaitez apporter des modifications. + +8. Collez votre clé de licence dans votre console AWS. + +9. Pour déployer la stack Cloudformation, dans la console AWS, sélectionnez **Create stack**. La création des ressources stack peut prendre plusieurs minutes et peut générer plusieurs piles, selon la façon dont vous configurez le transfert des métriques. Si la création de la pile échoue, reportez-vous à la [procédure de dépannage](https://docs.newrelic.com/docs/logs/troubleshooting/aws-log-integration-issues/stack-creation-fails/). + +10. Après une création stack réussie, passez à la plateforme New Relic et continuez l'intégration guidée jusqu'à ce que vous voyiez vos données AWS dans New Relic. + +## Sujets connexes [#related-topics] + + + + Découvrez comment collecter des données à partir de plusieurs comptes AWS. + + + + Explorez et utilisez les métriques du flux de métriques CloudWatch. + + \ No newline at end of file diff --git a/src/i18n/content/fr/docs/infrastructure/other-infrastructure-integrations/stripe-integration.mdx b/src/i18n/content/fr/docs/infrastructure/other-infrastructure-integrations/stripe-integration.mdx index c1a70d15cad..0e856aebc52 100644 --- a/src/i18n/content/fr/docs/infrastructure/other-infrastructure-integrations/stripe-integration.mdx +++ b/src/i18n/content/fr/docs/infrastructure/other-infrastructure-integrations/stripe-integration.mdx @@ -102,7 +102,7 @@ WHERE metricName = 'stripe_metrics' ### Installez notre Stripe monitoring dashboard [#add-dashboard] -Pour configurer notre prédéfini Stripe dashboard afin de monitorer les métriques de votre application, accédez à [Stripe dashboard l' installation](https://onenr.io/0ZQWYYE1rRW) et suivez les instructions. Une fois installé, le dashboard devrait afficher des métriques. +Pour configurer notre dashboard Stripe pré-construit afin de monitorer les métriques de votre application, accédez à l' [installation du dashboard pour Stripe](https://onenr.io/0BQrXaNgnRZ) et suivez les instructions. Une fois installé, le dashboard devrait afficher des métriques. Si vous avez besoin d'aide avec le dashboard, consultez : diff --git a/src/i18n/content/fr/docs/new-relic-solutions/solve-common-issues/find-help-get-support.mdx b/src/i18n/content/fr/docs/new-relic-solutions/solve-common-issues/find-help-get-support.mdx index ef1dbfda44c..45468f31e99 100644 --- a/src/i18n/content/fr/docs/new-relic-solutions/solve-common-issues/find-help-get-support.mdx +++ b/src/i18n/content/fr/docs/new-relic-solutions/solve-common-issues/find-help-get-support.mdx @@ -29,9 +29,9 @@ La vue d'assistance intégrée au produit offre une visibilité sur les nou In-product support -## Posez votre question dans Explorers Hub, notre forum d'assistance gratuit [#nr-forum] +## Posez vos questions sur notre forum d'assistance gratuit [#nr-forum] -[Le New Relic's Explorers Hub](https://discuss.newrelic.com/) est notre forum gratuit pour tous les utilisateurs. Les utilisateurs et collaborateurs de New Relic s'engagent chaque jour dans des conversations pour dépanner et résoudre les problèmes, trouver des solutions de contournement et discuter de nouvelles fonctionnalités. +[Le forum de support de New Relic](https://discuss.newrelic.com/) est notre forum gratuit pour tous les utilisateurs. Les utilisateurs et collaborateurs de New Relic s'engagent chaque jour dans des conversations pour dépanner et résoudre les problèmes, trouver des solutions de contournement et discuter de nouvelles fonctionnalités. ## Exécutez l'outil de diagnostic New Relic [#diagnostics] diff --git a/src/i18n/content/fr/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx b/src/i18n/content/fr/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx index 31b8d3e10b6..988a03b6790 100644 --- a/src/i18n/content/fr/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx +++ b/src/i18n/content/fr/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx @@ -346,15 +346,24 @@ Voici quelques types différents d’implémentations de variables de modèle. - Vous pouvez activer l'option multi-valeurs à partir de la section des options d'affichage lors de la création d'une variable de type `NRQL/ENUM`. + You can enable the multi-value option to allow users to select multiple values from a dropdown instead of just one. This is useful when you want to filter data across multiple criteria simultaneously. - Voici un exemple de requête qui crée une variable nommée `{{MultiValue}}` et renvoie une liste de tous les eventId uniques : + Multi-value is available for Query and List variable types. Text field variables don't support the multi-value option. + + To enable multi-value: + + 1. When creating a Query or List template variable, select the **Multi-value** option. + 2. In your widget queries, use the `IN` operator instead of `=` to handle multiple selected values. + + /* You can enable the multi-value option from the display options section when creating a variable of type `NRQL/ENUM`. */ + + Here's an example where you'd name your variable `{{MultiValue}}` and use this query to populate its values: ```sql SELECT uniques(eventId) FROM AjaxRequest ``` - Multi-value template variable example + /* <img width="30%;" title="Multi-value template variable example" alt="Multi-value template variable example" src="/images/dashboards_screenshot-crop_add-multivalue.webp" /> */ Ensuite, vous créeriez un widget avec la requête suivante : @@ -362,22 +371,36 @@ Voici quelques types différents d’implémentations de variables de modèle. SELECT count(*) FROM AjaxRequest WHERE eventId IN ({{MultiValue}}) ``` - Creating a widget + /* <img width="80%;" title="Creating a widget" alt="Creating a widget" src="/images/dashboards_screenshot-full_multivalue-add-widget.webp" /> */ - Vous ne pouvez définir qu'une seule variable de modèle à la fois, mais vous pouvez utiliser plusieurs variables de modèle dans un seul widget. + While you can only define one template variable at a time, you can reference multiple variables within the same widget. + + For this example, you need to have the two variables set up: + + 1. `countryCode` variable: Use the query shown earlier in this document: + + ```sql + SELECT uniques(countryCode) FROM PageAction SINCE 2 days ago + ``` + + 2. `city` variable with a similar query: + + ```sql + SELECT uniques(city) FROM PageView SINCE 1 week ago + ``` - Voici un exemple de requête qui utilise deux variables de modèle. Notez que cela suppose que les variables de modèle `countryCode` et `city` ont déjà été créées et qu'elles ont une valeur unique. + Here's an example using the above template variables with single values to create the widget: ```sql SELECT countryCode, city FROM PageAction WHERE countryCode = {{countryCode}} AND city = {{city}} ``` - Creating a widget using multiple variables + /* <img title="Creating a widget using multiple variables" alt="Creating a widget using multiple variables" src="/images/dashboards_screenshot-crop_add-widget-multiple-variable.webp" /> */ - Si vous avez plusieurs valeurs pour vos variables, telles que `Chicago`, `New York`, `Paris` pour votre variable `city` , vous devez utiliser `IN`: + If your variables support multiple values (such as `Chicago`, `New York`, `Paris` for your `city` variable), you need to use `IN`: ```sql SELECT countryCode, city FROM PageAction @@ -398,7 +421,7 @@ Voici quelques types différents d’implémentations de variables de modèle. SELECT uniques(aparse(platformVersion, 'release-*')) FROM PageView ``` - Creating the release version variable + /* <img width="40%;" title="Creating the release version variable" alt="Creating the release version variable" src="/images/dashboards_screenshot-crop_add-var-release-version.webp" /> */ Créez ensuite un widget avec la requête suivante : @@ -407,7 +430,7 @@ Voici quelques types différents d’implémentations de variables de modèle. WHERE aparse(platformVersion, 'release-*') IN ({{releaseversion}}) FACET platformVersion ``` - Creating the widget + /* <img title="Creating the widget" alt="Creating the widget" src="/images/dashboards_screenshot-crop_add-widget-aparse.webp" /> */ Ou si vous préférez, vous pouvez utiliser la commande [`capture`](/docs/query-your-data/nrql-new-relic-query-language/get-started/nrql-syntax-clauses-functions/#func-capture) : @@ -416,15 +439,20 @@ Voici quelques types différents d’implémentations de variables de modèle. WHERE capture(platformVersion, r'release-(?P\d+)') IN ({{releaseversion}}) FACET platformVersion ``` - Creating the widget + /* <img title="Creating the widget" alt="Creating the widget" src="/images/dashboards_screenshot-crop_add-widget-capture.webp" /> */ Vous pouvez utiliser `LIKE` et `RLIKE` comme variables de modèle pour filtrer les données dans un dashboard. Pour utiliser cette fonctionnalité, la valeur que vous ajoutez lors de la création de la variable de modèle doit utiliser les symboles génériques `%` au début et à la fin de la valeur. - Voici un exemple. Vous définissez une variable de chaîne, comme indiqué ici : + Here's an example. You define a string template variable with the following values: + + * **Name to use in queries:** line\_filter + * **Type :** `Text field` + * **Default value:** %@%.com + * **Output format:** `String` - Add `LIKE` as template variable + /* <img width="40%;" title="Add `LIKE` as template variable" alt="Add `LIKE` as template variable" src="/images/dashboards_screenshot-crop_add-var-like-filter.webp" /> */ Vous pouvez ensuite créer un graphique widget et utiliser votre variable comme ceci : @@ -432,7 +460,7 @@ Voici quelques types différents d’implémentations de variables de modèle. FROM NrdbQuery SELECT user WHERE user LIKE {{like_filter}} ``` - Add `LIKE` as template variable + /* <img title="Add `LIKE` as template variable" alt="Add `LIKE` as template variable" src="/images/dashboards_screenshot-crop_add-widget-like-filter.webp" /> */ ou comme ça : @@ -450,13 +478,13 @@ Voici quelques types différents d’implémentations de variables de modèle. > Vous pouvez créer une variable de type NRQL avec un format de sortie de chaîne et l'utiliser après une clause `FACET` pour regrouper par différentes valeurs. - Par exemple, vous pouvez créer une variable nommée `{{userAgentName}}` qui ressemblerait à : + For example, you might create a template variable named `{{userAgentName}}` that would look like: ```sql SELECT uniques(userAgentName) FROM PageAction ``` - Creating the variable + /* <img width="30%;" title="Creating the variable" alt="Creating the variable" src="/images/dashboards_screenshot-crop_add-var-facet.webp" /> */ Ensuite, vous créerez un widget avec la requête suivante : @@ -465,15 +493,20 @@ Voici quelques types différents d’implémentations de variables de modèle. WHERE userAgentName={{userAgentName}} FACET userAgentName ``` - Creating widget using facet + /* <img title="Creating widget using facet" alt="Creating widget using facet" src="/images/dashboards_screenshot-crop_add-widget-facet.webp" /> */ Vous pouvez créer une variable avec un format de sortie `identifier` et l'utiliser après une clause `FACET` pour regrouper par différentes valeurs. - Par exemple, vous pouvez créer une variable `{{location}}` de type liste avec deux valeurs possibles : `countryCode` et `city`. Vous devez définir le format de sortie sur `identifier`. + For example, you might create a `{{location}}` variable: - Adding the variable for dynamic grouping + * **Name to use in queries:** location + * **Type :** `List` + * **Values separated by commas:** `countryCode` and `city` + * **Output format:** `Identifier` + + /* <img width="40%;" title="Adding the variable for dynamic grouping" alt="Adding the variable for dynamic grouping" src="/images/dashboards_screenshot-crop_add-var-dynamic-grouping.webp" /> */ Ensuite, vous créerez un widget avec la requête suivante : @@ -481,15 +514,20 @@ Voici quelques types différents d’implémentations de variables de modèle. SELECT count(*) FROM PageAction FACET {{location}} ``` - Adding the widget for dynamic grouping + /* <img title="Adding the widget for dynamic grouping" alt="Adding the widget for dynamic grouping" src="/images/dashboards_screenshot-crop_add-widget-dynamic-grouping.webp" /> */ Vous pouvez créer une variable avec le format de sortie `number` et l'utiliser dans une fonction percentile . - Par exemple, vous pouvez créer une variable `{{percentile}}` de type `list` avec deux valeurs possibles : `55` et `90`. Vous souhaiterez définir le format de sortie sur `number`. + For example, you could create a `{{percentile}}` variable: + + * **Name to use in queries:** percentile + * **Type :** `List` + * **Values separated by commas:** `55` and `90` + * **Output format:** `Number` - Adding the variable for dynamically change the percentile + /* <img width="40%;" title="Adding the variable for dynamically change the percentile" alt="Adding the variable for dynamically change the percentile" src="/images/dashboards_screenshot-crop_add-var-dynamic-percentile.webp" /> */ Ensuite, vous créerez un widget avec la requête suivante : @@ -497,7 +535,7 @@ Voici quelques types différents d’implémentations de variables de modèle. SELECT percentile(duration, {{percentile}}) FROM PageAction ``` - Adding the widget for dynamically change the percentile + /* <img title="Adding the widget for dynamically change the percentile" alt="Adding the widget for dynamically change the percentile" src="/images/dashboards_screenshot-crop_add-widget-dynamic-percentile.webp" /> */ @@ -508,7 +546,7 @@ Voici quelques types différents d’implémentations de variables de modèle. WHERE countryCode IN ({{countryCode}}) ``` - Use variables to filter + /* <img title="Use variables to filter" alt="Use variables to filter" src="/images/dashboards_screenshot-crop_variables-to-filter.webp" /> */ @@ -528,7 +566,7 @@ Voici quelques types différents d’implémentations de variables de modèle. Cela donne les valeurs des 30 dernières minutes. Lorsque vous définissez la valeur du sélecteur d'intervalle de temps sur **Default** et que votre requête comporte une clause `SINCE` , la dernière valeur sera utilisée pour exécuter la requête. - A screenshot showing the variable form + /* <img title="Example form" alt="A screenshot showing the variable form" src="/images/dashboards_screenshot-crop_example-form.webp" /> */ + Nous vous recommandons de mettre à jour vers la dernière version de l'agent dès qu'elle est disponible. Si votre organisation a établi des pratiques qui vous empêchent de mettre à jour vers la dernière version, assurez-vous que vos agents sont régulièrement mis à jour vers une version datant d'au plus 90 jours. En savoir plus sur [la façon de tenir votre agent informé](https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/). + + +## 3.41.0 + +### Ajouté + +* Ajout de `DistributedTracer.Sampler` options de configuration pour contrôler le comportement d'échantillonnage des requêtes entrantes pour les traces distribuées + + * Pour configurer l'échantillonneur, ajoutez `ConfigRemoteParentSampled(flag RemoteParentSamplingConfig)` et `ConfigRemoteParentNotSampled(flag RemoteParentSamplingConfig)` qui gèrent le comportement d'échantillonnage en fonction de ce que le parent distant a signalé + * Les indicateurs ajoutés sont `"always_on", "always_off", and "default"` qui peuvent être appelés en utilisant `RemoteParentSamplingConfig` + * `Example: newrelic.ConfigRemoteParentSampled(newrelic.AlwaysOff)` + +* Ajout des tests de monitoring OOM + +* Couverture accrue des tests d'agent sécurisé + +### Fixé + +* Versions de bibliothèques tierces mises à jour en raison de problèmes de sécurité ou d'autres problèmes de support signalés : + + * `github.com/gofiber/fiber/v2` de 2.52.7 à 2.52.9 en intégration `nrfiber` + * `golang.org/x/net` de 0,25,0 à 0,38,0 en intégration `nrconnect` + +### Déclaration de soutien + +Nous utilisons la dernière version du langage Go. Au minimum, vous ne devriez pas utiliser de version de Go plus ancienne que celle prise en charge par l'équipe Go elle-même. Consultez la [politique EOL de l'agent Go](https://docs.newrelic.com/docs/apm/agents/go-agent/get-started/go-agent-eol-policy/) pour plus de détails sur les versions prises en charge de l'agent Go et des composants tiers. \ No newline at end of file diff --git a/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-8-01-2025.mdx b/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-8-01-2025.mdx new file mode 100644 index 00000000000..1fcdfbdf228 --- /dev/null +++ b/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-8-01-2025.mdx @@ -0,0 +1,99 @@ +--- +subject: Docs +releaseDate: '2025-08-01' +version: 'July 25 - August 01, 2025' +translationType: machine +--- + +### Nouveaux documents + +* Ajout [de la documentation Calculer Budgets](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/compute-budgets/overview) pour vous fournir un mécanisme de surveillance et d'alerte sur l'utilisation de votre unité de consommation Calculer (CCU). + +### Changements majeurs + +* [Compatibilité et exigences](/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent) mises à jour pour l'agent Node.js. + +* [Compatibilité et exigences mises à jour pour l'agent Alpine Linux](/docs/apm/agents/php-agent/getting-started/php-agent-compatibility-requirements) pour PHP. + +* Mise à jour des exigences spécifiques à l'agent pour [le Contrôle de pipeline](/docs/new-relic-control/pipeline-control/modify-agent-configuration). + +* Mise à jour du JFR relatif aux exigences de configuration pour [l'agent Java](/docs/apm/agents/java-agent/configuration/java-agent-configuration-config-file#jfr-harvest-interval). + +* Mise à jour des informations de tarification et de facturation pour New Relic dans : + + * [Données : Facturation et règles](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing) + * [Requêtes et alertes liées à l'utilisation](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts) + * [Plan d'utilisation de New Relic](/docs/licenses/license-information/usage-plans/new-relic-usage-plan) + +### Modifications mineures + +* Clarification du langage dans l'agent .NET pour capturer les paramètres SQL dans le document [de compatibilité de l'agent et des exigences .NET](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements). +* Affinement du langage dans [l'intégration de la surveillance de la base de donnéesOracle ](/docs/infrastructure/host-integrations/host-integrations-list/oracle-database-monitoring-integration). + +### Notes de version + +* Consultez nos articles Quoi de neuf : + + * [Les budgets sont désormais généralement disponibles](/whats-new/2025/07/whats-new-7-30-compute-budgets). + * [Amélioration des expériences utilisateur : tirer parti Session Replay pour l'optimisation des éléments essentiels du Web](/whats-new/2025/07/whats-new-7-31-augmenting-user-experiences-browser). + +* Restez au courant de nos dernières sorties : + + * [Agent Android v7.6.8](/docs/release-notes/mobile-release-notes/android-release-notes/android-768): + + * Correction d'un problème où les traces d'appels pour les erreurs Unity ne s'affichaient pas correctement. + * Correction d'un problème qui empêchait l'enregistrement de la métrique récapitulative lorsque l'application revenait au premier plan après son lancement initial. + * Correction d'un problème où un JSON non valide dans les entrées log pouvait provoquer des erreurs. + + * [CLI de diagnostic (nrdiag) v3.4.0](/docs/release-notes/diagnostics-release-notes/diagnostics-cli-release-notes/diagnostics-cli-341): + * Ajout de `K8s/AgentControl/agent-control-install-job-logs` pour collecter les logs générés par l'installation de l'agent-control. + + * [Gestionnaire de tâches v451](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-451): + + * Vulnérabilités corrigées liées à `common-lang3` Java et Ubuntu pour résoudre les problèmes de sécurité dans le SJM. + * Mise en œuvre des modifications de migration de la file d'attente du processeur liées à la migration de notre architecture de service interne. + * Correction d'un problème pour inclure les détails complets de l'exception afin de fournir un meilleur contexte pour le dépannage dans les logs SJM. + + * [Application mobile pour Android v5.30.1](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5301): + * Amélioration de l'expérience de connexion. + + * [Application mobile pour iOS v7.5.8](/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-758): + + * A créé l'agent à l'aide de Xcode 16.4. + * Correction d'un problème qui pouvait entraîner le fait que le traçage distribué ne contienne pas toutes les informations de compte requises au démarrage d'une session. + * Correction d'un problème pouvant provoquer un plantage au démarrage de l'agent. + + * [Exécution de l'API Node](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.122): + * Correction des vulnérabilités des données de formulaire et des vulnérabilités Ubuntu sous-jacentes pour résoudre les vulnérabilités de sécurité dans les environnements d'exécution de l'API Node. + + * [Node browser runtime](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.39): + * Correction des vulnérabilités des données de formulaire et des vulnérabilités Ubuntu sous-jacentes pour résoudre les vulnérabilités de sécurité dans les environnements d'exécution Browser Node. + + * [Durée d'exécution du ping](/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.53.0): + * Vulnérabilités corrigées liées à `common-lang3` Java et Ubuntu pour résoudre les problèmes de sécurité dans l'environnement d'exécution Ping. + + * [Agent Python v10.15.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-101500): + + * Ajout de la prise en charge de [`oracledb`](https://pypi.org/project/oracledb/) + * Correction d'un bug dans les instrumentations `MessageBroker` où les méthodes de sérialisation recherchaient l'attribut `destination_name` sur `MessageTransaction` et il n'existait pas. + * Correction du problème de métadonnées d'utilisation AWS lors de l'exécution d'AWS et de K8 ensemble. + + * [Agent Ruby v9.20.0](/docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-20-0): + + * Ajout de la prise en charge de l'enregistrement de l'ID Docker lors de l'exécution dans l'environnement AWS ECS Fargate. + * Ajout d'une nouvelle méthode d'assistance pour simplifier la comparaison des versions. + * L'attribut `code.stacktrace` a été ajouté aux étendues datastore lorsque la durée dépasse le seuil configuré. + * Liens sources `Brewfile` corrigés. + * Correction d'une erreur qui se produit lors de l'utilisation de `HTTPX 1.5.0` pour stocker la réponse. + * Amélioration de l'informations enregistrées au niveau du débogage par l'agent lorsque l'agent lit une source configuration. + + * [Agent Unity v1.4.8](/docs/release-notes/mobile-release-notes/unity-release-notes/unity-agent-148): + + * Mise à jour de l'agent Android natif vers la version 7.6.7. + * Mise à jour de l'agent iOS natif vers la version 7.5.6. + + * [Agent Unity v1.4.9](/docs/release-notes/mobile-release-notes/unity-release-notes/unity-agent-149): + + * Mise à jour de l'agent Android natif vers la version 7.6.8. + * Mise à jour de l'agent iOS natif vers la version 7.5.8. + * Correction du problème de trace d'appels d'exception Unity lorsque l'espace de nommage est utilisé. \ No newline at end of file diff --git a/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx b/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx new file mode 100644 index 00000000000..d1b3ded6ad8 --- /dev/null +++ b/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx @@ -0,0 +1,60 @@ +--- +subject: Docs +releaseDate: '2025-08-08' +version: 'August 01 - August 07, 2025' +translationType: machine +--- + +### Nouveaux documents + +* [Tutoriel NerdGraph ajouté : Créer un rôle personnalisé pour les équipes](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/compute-budgets/overview) pour vous guider dans l’utilisation de l’API New Relic NerdGraph pour créer et gérer des rôles personnalisés pour les équipes. + +### Modifications mineures + +* Modification du [seuil d'alerte événement par condition](/docs/alerts/admin/rules-limits-alerts) à 1k par minutes. +* Mise à jour des dernières [versions et exigences compatibles avec l'agent .Net](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements) vérifiées. +* Mise à jour des informations de version et de prise en charge des versions concernant le courtier de services pour [VMware Tanzu](/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-service-broker-integration). +* Mise à jour des informations de prise en charge de la version concernant le buildpack d'intégration New Relic NGINX pour [VMware Tanzu](/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-nginx-buildpack-integration). +* Mise à jour des informations de version et de support de version concernant New Relic Nozzle pour [VMware Tanzu](/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-firehose-nozzle-integration/#product-snapshot). + +### Notes de version + +* Consultez nos articles Quoi de neuf : + + * [Errors Inbox est désormais intégrée à la charge de travail](/whats-new/2025/08/whats-new-08-06-workloads-errors-inbox). + +* Restez au courant de nos dernières sorties : + + * [Gestionnaire de tâches v452](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-452): + * Améliorations internes ajoutées pour la gestion des exceptions dans le traitement des messages de file d'attente. + + * [IntégrationKubernetes v3.43.3](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-43-3): + * Ajout d'un graphique Helm pour déployer la solution monitoring New Relic Kubernetes. + + * [Contrôle de pipeline Gateway v1.1.0](/docs/release-notes/pipeline-control-gateway-release-notes/pipeline-control-gateway-25-08-05): + + * Implémentation d'une nouvelle fonctionnalité permettant de supprimer de manière sélective les données et les attributs des événements `SqlTrace` et `TransactionTrace` à l'aide de règles de suppression. + + * Des vulnérabilités ont été corrigées dans le package `golang.org/x/net`, notamment un problème de script intersite et un contournement du proxy HTTP lié aux ID de zone IPv6. + + * Mise à niveau vers Go `1.24` et les dépendances suivantes sont mises à jour pour améliorer la sécurité et intégrer les correctifs récents : + + * `golang.org/x/net to v0.38.0` + * `golang.org/x/sys to v0.31.0` + * `golang.org/x/text to v0.23.0` + + * [Application mobile pour iOS v6.9.11](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6101): + * Le flux de connexion a été réduit de deux étapes en stockant le domaine d'authentification d'un utilisateur et en le redirigeant directement vers sa page de connexion. + + * [Agent Flutter v1.1.13](/docs/release-notes/mobile-release-notes/flutter-release-notes/flutter-agent-1113): + + * Agent Android natif amélioré mis à jour vers la version 7.6.8 + * Agent iOS natif amélioré mis à jour vers la version 7.5.8 + + * [Agent .NET MAUI v1.1.11](/docs/release-notes/mobile-release-notes/net-maui-release-notes/net-maui-agent-1111) + + * Agent Android natif amélioré mis à jour vers la version 7.6.8 + * Agent iOS natif amélioré mis à jour vers la version 7.5.8 + + * [Agent d'infrastructure v1.65.5](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1655): + * Modification de la prise en charge des montages AWS EFS dans les exemples de stockage \ No newline at end of file diff --git a/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-8-14-2025.mdx b/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-8-14-2025.mdx new file mode 100644 index 00000000000..e751e90fd9c --- /dev/null +++ b/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-8-14-2025.mdx @@ -0,0 +1,112 @@ +--- +subject: Docs +releaseDate: '2025-08-15' +version: 'August 08 - August 14, 2025' +translationType: machine +--- + +### Nouveaux documents + +* Ajout [de la prise en charge des fonctions NRQL dans les règles de gateway](/docs/new-relic-control/pipeline-control/nrql-functions) pour décrire les fonctions NRQL prises en charge dans les règles de gateway de Contrôle de pipeline. +* Étapes de dépannage ajoutées pour résoudre [l'événement de redémarrage fréquent Fluent Bit ](/docs/infrastructure/infrastructure-troubleshooting/troubleshoot-infrastructure/frequent-fluent-bit-restart-events)en ajustant les paramètres de résolution du nom d'hôte dans la configuration de l'agent New Relic Infrastructure. + +### Changements majeurs + +* [Plan d'utilisation](/docs/licenses/license-information/usage-plans/new-relic-usage-plan/#list-price) mis à jour avec les dernières informations tarifaires. +* Ajout de **Error inbox** à [l'interface utilisateur de la charge de travail (workloads)](/docs/new-relic-solutions/new-relic-one/workloads/use-workloads/#errors). +* Ajout de la désactivation sélective de l'agent en fonction de la classe principale de démarrage ou du fichier jar exécutable via des variables d'environnement, ainsi que des paramètres de sécurité améliorés pour [la configuration de l'agent Java](/docs/apm/agents/java-agent/configuration/java-agent-configuration-config-file/#skip-applications). +* Ajout de la prise en charge de [la configuration du référentiel privé](/docs/new-relic-control/agent-control/configuration/#private-repository-configuration) dans Agent Control, permettant le déploiement d'agents gérés avec authentification via des méthodes de certificat de base ou TLS. +* Ajout de la prise en charge de [la gestion des secrets](/docs/new-relic-control/agent-control/configuration/#secrets-management) dans Agent Control, pour la gestion des données sensibles, telles que les mots de passe et l'API de clé, en les récupérant auprès d'un fournisseur de secrets dédié. + +### Modifications mineures + +* Ajout de restrictions de balise d'entité pour la clause `WHERE` dans [Drop data using Contrôle de pipeline cloud rules](/docs/new-relic-control/pipeline-control/cloud-rules-api/#restrictions). +* Ajout [de bonnes pratiques pour optimiser le contenu de votre source de connaissances](/docs/agentic-ai/knowledge-integration/overview/#configure) pour le connecteur New Relic AI Knowledge. + +### Notes de version + +* Consultez nos articles Quoi de neuf : + + * [Le mode haute précision UniqueCount et la prise en charge accrue des arguments sont désormais généralement disponibles](/whats-new/2025/08/whats-new-8-13-high-precision-uniquecount). + +* Restez au courant de nos dernières sorties : + + * [Agent Cordova v7.0.8](/docs/release-notes/mobile-release-notes/cordova-release-notes/cordova-agent-708/): + + * Mettre à jour l'agent Android natif vers la version 7.6.8 + * Mettre à jour l'agent iOS natif vers la version 7.5.8 + + * [Agent Cordova v7.0.9](/docs/release-notes/mobile-release-notes/cordova-release-notes/cordova-agent-709/): + + * Mettre à jour l'agent Android natif vers la version 7.6.6 + * Mettre à jour l'agent iOS natif vers la version 7.5.5 + + * [Agent Capacitor v1.5.8](/docs/release-notes/mobile-release-notes/capacitor-release-notes/capacitor-agent-158/): + + * Mettre à jour l'agent Android natif vers la version 7.6.6 + * Mettre à jour l'agent iOS natif vers la version 7.5.5 + + * [Agent Capacitor v1.5.9](/docs/release-notes/mobile-release-notes/capacitor-release-notes/capacitor-agent-159/): + * Correction du crash du signal d'abandon + + * [Agent Capacitor v1.5.10](/docs/release-notes/mobile-release-notes/capacitor-release-notes/capacitor-agent-1510/): + + * Mettre à jour l'agent Android natif vers la version 7.6.8 + * Mettre à jour l'agent iOS natif vers la version 7.5.8 + + * [CLI de diagnostic (nrdiag) v3.5.0](/docs/release-notes/diagnostics-release-notes/diagnostics-cli-release-notes/diagnostics-cli-350/): + * mise à jour de la vérification de compatibilité de la version `Java/Appserver/JbossEapCheck` + + * [Agent .NET v10.44.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-44-0/): + + * Activation des échantillonneurs de performances métriques en mode Serverless + * Processus d'hôte Web Azure Function (Linux) exclu de l'instrumentation. + + * [NRDOT v1.3.0](/docs/release-notes/nrdot-release-notes/nrdot-2025-08-13/): + + * Mise à jour des versions des composants de l'hôtel de la v0.128.0 à la v0.131.0 + * Introduction de la distribution principale nrdot + + * [Agent Node.js v13.1.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-1-0/): + + * Ajout de la prise en charge de l'API de logs OTEL + * Ajout de mesures de prise en charge lorsque l'instrumentation a été désactivée pour un package + * Instrumentation des minuteries désactivée par défaut dans la configuration de l'échantillon + * Correction de l'obfuscation `transaction.url` + + * [Gestionnaire de tâches v454](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-454/): + * Correction des vulnérabilités sous-jacentes d'Ubuntu pour résoudre les vulnérabilités de sécurité dans SJM. + + * [Exécution de l'API Node v1.2.124](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.124/): + * Correction des vulnérabilités sous-jacentes d'Ubuntu pour résoudre les vulnérabilités de sécurité dans les environnements d'exécution de l'API Node. + + * [Exécution du navigateur de nœuds v3.0.41](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.41/): + * Correction des vulnérabilités tmp `CVE-2025-54798` et des vulnérabilités Ubuntu sous-jacentes pour résoudre les vulnérabilités de sécurité dans les environnements d'exécution Browser Node. + + * [Ping Runtime v1.54.0](/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.54.0/): + * Correction de vulnérabilités liées à Ubuntu pour résoudre les problèmes de sécurité dans l'environnement d'exécution Ping. + + * [Agent Java v8.23.0](/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8230/): + + * Mis à jour pour prendre en charge la version 24 de graphql. + * Ajout de l'instrumentation de la laitue 6.5. + * Version commons-lang mise à jour vers 3.18.0 + + * [AWS Lambda redirecteur de logs v1.1.1](/docs/release-notes/aws-lambda-log-forwarder-release-notes/lambda-25-07-25/): + * Posture de sécurité améliorée en mettant à niveau la version Go vers 1.24.4 dans système. + + * [Agent PHP v12.0.0.25](/docs/release-notes/agent-release-notes/php-release-notes/php-agent-12-0-0-25/): + + * Logging des erreurs de la carte des hooks Drupal améliorée. + * Problèmes de détection package legacy corrigés pour Security RX. + + * [Agent d'infrastructure v1.66.1](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1661/): + * Prise en charge rétablie des montages AWS EFS dans les exemples de stockage. + + * [Application mobile pour Android v5.30.6](docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5306/): + * Prise en charge améliorée des clés de passe pour les connexions SAML et sociales. + + * [Agent Browser v1.295.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.0/): + + * Ajout de la détection des causes d'erreur. + * Ajout d'avertissements concernant les correctifs de singe. \ No newline at end of file diff --git a/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-8-21-2025.mdx b/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-8-21-2025.mdx new file mode 100644 index 00000000000..7cc6267277e --- /dev/null +++ b/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-8-21-2025.mdx @@ -0,0 +1,56 @@ +--- +subject: Docs +releaseDate: '2025-08-22' +version: 'August 15 - August 21, 2025' +translationType: machine +--- + +### Changements majeurs + +* Rapport de compatibilité [de l'agent Node.js](/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent/) mis à jour. +* [Agent .NET](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements/) mis à jour avec les dernières versions de bibliothèque compatibles vérifiées. + +### Modifications mineures + +* Mise à jour du système d'exploitation [Debian](/docs/infrastructure/infrastructure-agent/linux-installation/package-manager-install/) vers la version 12 (« bookworm ») pour prendre en charge l' [agentinfrastructure ](/docs/infrastructure/infrastructure-agent/requirements-infrastructure-agent/#os)pour Linux. +* Fonction [`accountId()`](/docs/data-apis/manage-data/query-limits/) mise à jour pour interroger les limites de données. +* [Programme d'installationWindows MSI](/docs/infrastructure/infrastructure-agent/windows-installation/windows-msi-installer/#install-windows) mis à jour pour prendre en charge Windows 64 bits (Intel/AMD). + +### Notes de version + +* Annoncé le 7 janvier 2026 comme date de fin de vie des règles de suppression via l'[UI de monitoring de l'IA](/docs/ai-monitoring/drop-sensitive-data/). + +* [Agent iOS v7.5.9](/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-759/) + + * Correction d'un problème qui pouvait entraîner le fait que le traçage distribué ne contienne pas toutes les informations de compte requises au début d'une session. + * Correction d'un problème pouvant provoquer un plantage au démarrage de l'agent. + +* [Agent Python v10.16.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-101600/) + + * Ajout de la prise en charge des nouvelles fonctions [Redis](https://pypi.org/project/redis/). + * Tous les chemins internes de `os.path` à `pathlib.Path` ont été convertis. + * Problème résolu avec l'encodage JSON PosixPath. + +* [Intégration Kubernetes v3.44.1](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-44-1/) + + * Cette intégration est incluse dans les versions de graphiques suivantes : + + * [newrelic-infrastructure-3.49.1](https://github.com/newrelic/nri-kubernetes/releases/tag/newrelic-infrastructure-3.49.1) + * [nri-bundle-6.0.10](https://github.com/newrelic/helm-charts/releases/tag/nri-bundle-6.0.10) + +* [Agent .NET v10.44.1](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-44-1/) + + * Gestion des exceptions corrigée dans le wrapper d'instrumentation Service Bus. + * Processus d'hôte Web Azure Function (Linux) exclu de l'instrumentation. + +* [Agent Node.js v13.2.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-2-0/) + + * Ajout de la possibilité d'enregistrer `Supportability/Features/Instrumentation/OnRequire/` métriques pour l'instrumentation basée sur l'abonné. + * Ajout du hook de chargement esm et du patch commonjs pour fonctionner avec orchestrion-js. + * Instrumentation ajoutée pour `@modelcontextprotocol/sdk` appels clients `client.callTool`, `client.readResource` et `client.getPrompt`. + * Logique fixe autour de la détection du package OTEL. + * Mise à jour de `shimmer.setupSubscribers` pour configurer correctement et ignorer les abonnés désactivés. + +* [Agent Node.js v13.2.1](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-2-1/) + + * Agent mis à jour pour utiliser `@apm-js-collab/tracing-hooks` pour l'enregistrement CJS/ESM pour le traçage de l'instrumentation basée sur le canal. \ No newline at end of file diff --git a/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-9-12-2025.mdx b/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-9-12-2025.mdx new file mode 100644 index 00000000000..bb5a9bec1bb --- /dev/null +++ b/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-9-12-2025.mdx @@ -0,0 +1,94 @@ +--- +subject: Docs +releaseDate: '2025-09-14' +version: 'September 08 - September 12, 2025' +translationType: machine +--- + +### Nouveaux documents + +* Ajout d'une documentation complète [sur le modèle de maturité d'observabilité](/docs/new-relic-solutions/observability-maturity/) pour fournir des conseils pour mesurer et améliorer les pratiques d'observabilité dans quatre domaines clés : temps de disponibilité des entreprises, expérience numérique, excellence en ingénierie et observabilité intelligente. + +### Changements majeurs + +* [Configuration de l'agent PHP](/docs/apm/agents/php-agent/configuration/php-agent-configuration/) mise à jour avec de nouvelles options de configuration étendues pour les contrôles d'échantillonnage et l'instrumentation du gestionnaire d'exceptions du framework. + +### Modifications mineures + +* [Introduction aux dashboards](/docs/query-your-data/explore-query-data/dashboards/introduction-dashboards/) mise à jour avec des conseils améliorés pour l'utilisation dashboard. +* Documentation [de gestion de dashboard](/docs/query-your-data/explore-query-data/dashboards/manage-your-dashboard/) améliorée avec un contenu simplifié pour la gestion JSON. +* Liens brisés corrigés dans la documentation [du plan d'utilisation de New Relic](/docs/licenses/license-information/usage-plans/new-relic-usage-plan/). +* Configuration de débogage fixe dans la documentation [de dépannage de l'agent .NET](/docs/apm/agents/net-agent/troubleshooting/debugging-net-windows/). + +### Notes de version + +* Restez au courant de nos dernières sorties : + + * [Agent Browser v1.297.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.297.0/): + + * Prévention des récoltes précoces lors de la période de réessai pour une meilleure gestion limitant le taux. + * L'attribut méta newrelic a été supprimé des frais de relecture sortants pour réduire les octets facturables. + * Exceptions corrigées pour les corps nuls résultant de récoltes vides. + + * [Agent PHP v12.1.0.26](/docs/release-notes/agent-release-notes/php-release-notes/php-agent-12-1-0-26/): + + * Ajout de contrôles d'échantillonnage basés sur la décision d'échantillonnage de tracew3c en amont. + * Option de configuration ajoutée pour ignorer l'instrumentation des gestionnaires d'exceptions du framework. + * Fuite de mémoire potentielle corrigée lors de l'appel de `newrelic_end_transaction(true)`. + * La version de Golang a été mise à jour vers la version 1.25.1 pour des améliorations de sécurité. + + * [Agent Python v10.17.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-101700/): + + * Ajout de la prise en charge des tâches personnalisées dans Celery. + * Ajout de la prise en charge de monitoring Graphene-Django. + * Ajout de la prise en charge du filtrage middleware dans Django. + * Prise en charge ajoutée pour l'API AWS Bedrock Converse. + * Prise en charge ajoutée pour l'indicateur d'échantillonnage de l'en-tête W3CTraceParent. + + * [Agent Java v8.24.0](/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8240/): + + * Prise en charge ajoutée pour MongoDB Reactive Streams 5.2.0 et versions ultérieures. + * Ajout du support Jedis 6. + * Correction du problème de double instrumentation de CouchBase. + * Correction du problème d'encapsulation de l'en-tête Spring WebClient 5.x. + + * [Agent Node.js v13.3.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-3-0/): + + * Prise en charge MCP `StreamableHTTPClientTransport` ajoutée. + + * [Agent Node.js v13.3.1](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-3-1/): + + * Correction du crash en définissant par défaut `requestParameters` sur un objet dans `transaction.addRequestParameters`. + + * [Agent Node.js v13.3.2](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-3-2/): + + * Code défensif ajouté pour obtenir `protocol` dans les appels http sortants. + + * [Intégration Kubernetes v3.45.1](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-45-1/): + + * Mis à jour avec les dernières améliorations et débogage. + + * [Gestionnaire de tâches v464](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-464/): + + * Problème résolu où les clients ne pouvaient pas extraire des images d'un registre personnalisé à l'aide de podman. + + * [Exécution du navigateur de nœuds v3.0.43](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.43/): + + * Correction des vulnérabilités sous-jacentes d'Ubuntu pour résoudre les vulnérabilités de sécurité. + + * [Application mobile pour iOS v6.9.12](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6102/): + + * Problèmes de liens profonds corrigés pour le tableau de bord et les alertes. + * Problème d'ID du tableau de bord CCU corrigé. + + * [Application mobile pour Android v5.30.7](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5307/): + + * Ajout du débogage et des améliorations. + + * [Agent Flutter v1.1.14](/docs/release-notes/mobile-release-notes/flutter-release-notes/flutter-agent-1114/): + + * Ajout d'améliorations de stabilité supplémentaires et de débogage. + + * [Contrôle de pipeline Gateway v25.09.01](/docs/release-notes/pipeline-control-gateway-release-notes/pipeline-control-gateway-25-09-01/): + + * Ajout d'une nouvelle sortie avec des capacités de contrôle pipeline améliorées. \ No newline at end of file diff --git a/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-9-15-2025.mdx b/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-9-15-2025.mdx new file mode 100644 index 00000000000..199a09019fa --- /dev/null +++ b/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-9-15-2025.mdx @@ -0,0 +1,84 @@ +--- +subject: Docs +releaseDate: '2025-09-19' +version: 'September 15 - September 19, 2025' +translationType: machine +--- + +### Nouveaux documents + +* Intégration AWS restructurée pour les métriques : + + * Ajout de [l'intégration manuelle AWS](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/manual/) + * Ajout de [l'intégration Terraform AWS](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/terraform/) + * Ajout [de CloudFormation avec intégration d'interrogation API](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-and-api-polling/) + * Ajout [du guide de migration de l'interrogation API vers les flux de métriques CloudWatch](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/migrate-from-api-polling-to-cwms/) + +### Changements majeurs + +* Amélioration [de la documentation Streaming vidéo et publicitaire](/docs/streaming-video-&-ads/get-started-with-streaming-video-&-ads/) avec des mises à jour de la structure des agents autonomes. + +### Modifications mineures + +* [API des problèmes NerdGraph mise à jour via GitHub](/docs/apis/nerdgraph/examples/nerdgraph-issues-api-via-github/) avec une documentation améliorée. +* [Intégration Microsoft Teams](/docs/alerts-applied-intelligence/notifications/notification-integrations/) mise à jour avec des conseils configuration améliorés. +* Type de [carte thermique](docs/query-your-data/explore-query-data/use-charts/chart-types/#widget-heatmap) mis à jour. +* [IntégrationMySQL ](/docs/infrastructure/host-integrations/host-integrations-list/mysql-monitoring-integration/)mise à jour avec des améliorations de synchronisation pour monitoring QPM. +* Documentation [de gestion de cardinalité](/docs/data-apis/ingest-apis/metric-api/cardinality-management/) améliorée avec des mises à jour mineures. +* Mise à jour [des exigences de compatibilité de l'agent .NET](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements/) avec les dernières versions de bibliothèque compatibles vérifiées. +* Correction de la documentation des bogues [du code de contrôle du pipeline](docs/new-relic-control/pipeline-control/cloud-rules-api/). + +### Notes de version + +* [monitoring synthétique mise à jour avec de nouvelles dates de fin de vie pour les adresses IP](/eol/2025/02/eol-01-31-25-synthetics-ip/). + +* Restez au courant de nos dernières sorties : + + * [Agent Java v8.24.0](/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8240/): + + * Prise en charge ajoutée pour MongoDB Reactive Streams 5.2.0 et versions ultérieures. + * Ajout du support Jedis 6. + * Correction du problème de double instrumentation de CouchBase. + * Correction du problème d'encapsulation de l'en-tête Spring WebClient 5.x. + + * [Agent Python v10.17.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-101700/): + + * Ajout de la prise en charge des tâches personnalisées dans Celery. + * Ajout de la prise en charge de monitoring Graphene-Django. + * Ajout de la prise en charge du filtrage middleware dans Django. + * Prise en charge ajoutée pour l'API AWS Bedrock Converse. + * Prise en charge ajoutée pour l'indicateur d'échantillonnage de l'en-tête W3CTraceParent. + + * [Agent d'infrastructure v1.68.0](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/1680/): + + * Version Go mise à niveau vers la version 1.25.0. + * Mise à jour de la dépendance newrelic/nri-winservices vers la version 1.3.0. + + * [Agent Browser v1.298.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.298.0/): + + * Interaction de navigation souple étendue pour inclure des tâches longues au-delà du temps de modification DOM. + * Correction du LCP pour signaler l'URL de la page d'origine au lieu de l'URL de la page actuelle lors des navigations souples. + + * [Agent Browser v1.297.1](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.297.1/): + + * Correction d'un problème où la classe d'agrégation Session Replay pouvait être importée deux fois lors de l'utilisation de newrelic.recordReplay La méthode API lors du préchargement a été activée. + + * [Agent React Native v1.5.10](/docs/release-notes/mobile-release-notes/react-native-release-notes/react-native-agent-1510/): + + * Mise à jour de l'agent Android natif vers la version 7.6.9. + * Mise à jour de l'agent iOS natif vers la version 7.5.10. + + * [Agent iOS v7.5.10](/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-7510/): + + * Correction d'un crash qui pouvait survenir au démarrage de l'agent. + + * [NRDOT v1.4.0](/docs/release-notes/nrdot-release-notes/nrdot-2025-09-18/): + + * Ajout de spanprocessor à nrdot-collector. + * Les versions des composants OpenTelemetry sont passées de la version v0.131.0 à la version v0.132.0. + * Ajout de newrelic.service.type à la configuration de télémétrie interne. + * Détection du nom d'hôte activée pour EC2. + + * [Intégration Kubernetes v3.45.2](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-45-2/) : + + * Mis à jour avec les dernières améliorations et débogage. \ No newline at end of file diff --git a/src/i18n/content/fr/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-759.mdx b/src/i18n/content/fr/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-759.mdx index 37fffbe2473..8dbd2606835 100644 --- a/src/i18n/content/fr/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-759.mdx +++ b/src/i18n/content/fr/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-759.mdx @@ -6,14 +6,6 @@ downloadLink: 'https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agen translationType: machine --- - - À partir de la version 7.5.4 du SDK iOS, un changement a été implémenté qui provoque le signalement d'un événement d'exception gérée précédemment supprimé. - - Veuillez mettre à jour vers l'agent New Relic iOS 7.5.9. Nous avons identifié un bug dans la version 7.5.8 du SDK iOS qui pourrait entraîner un téléchargement de données incorrect, et un correctif est inclus dans l'agent iOS New Relic 7.5.9 sortie. - - Veuillez mettre à jour vers l'agent New Relic iOS 7.5.9. Nous avons identifié un bug dans la version 7.5.7 du SDK iOS qui pourrait provoquer un plantage au lancement de l'agent, et un correctif est inclus dans l'agent iOS New Relic 7.5.9 sortie. - - ## Corrigé dans cette sortie * L'agent est construit à l'aide de Xcode 16.4. diff --git a/src/i18n/content/fr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx b/src/i18n/content/fr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx new file mode 100644 index 00000000000..e635be395dd --- /dev/null +++ b/src/i18n/content/fr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx @@ -0,0 +1,39 @@ +--- +subject: Browser agent +releaseDate: '2025-08-04' +version: 1.295.0 +downloadLink: 'https://www.npmjs.com/package/@newrelic/browser-agent' +features: + - Add error cause detection +bugs: + - Add monkey-patching warnings + - Calculate first and last timestamps from raw data +security: [] +translationType: machine +--- + +## v1.295.0 + +### Caractéristiques + +#### Ajouter une détection de cause d'erreur + +Détecter et signaler l'attribut de cause sur l'événement JavaScriptError capturé. Si la cause est une instance d'une erreur, la trace des appels sera capturée, sinon le contenu stringifié de la cause sera signalé. Cela sera interrogeable dans l'événement JavaScriptError sous l'attribut `cause`. + +### Débogage + +#### Ajouter des avertissements de mise à jour de singe + +Ajout d'une détection et d'avertissements lorsque les variables globales attendues ont été corrigées avant que l'agent ne soit exécuté sur la page. Cela peut entraîner des comportements inattendus et l’objectif est d’informer les clients de ce comportement. + +#### Calculer le premier et le dernier horodatage à partir des données brutes + +Assurez-vous que l'agent calcule manuellement le premier et le dernier horodatage d'une charge SessionReplay avant la récolte pour aider à améliorer la cohérence sur le lecteur d'interface utilisateur. + +## Déclaration de soutien + +New Relic vous recommande de mettre à niveau l'agent régulièrement pour vous assurer de bénéficier des dernières fonctionnalités et avantages en termes de performances. Les sorties plus anciennes ne seront plus prises en charge lorsqu'elles atteindront [la fin de leur vie](https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/browser-agent-eol-policy/). Les dates de sortie reflètent la date de publication originale de la version de l'agent. + +Les nouveaux agents de navigation sont déployés auprès des clients par petites étapes sur une période donnée. De ce fait, la date à laquelle la sortie devient accessible sur votre compte peut ne pas correspondre à la date de publication d'origine. Veuillez consulter ce [dashboard d'état](https://newrelic.github.io/newrelic-browser-agent-release/) pour plus d'informations. + +Conformément à notre [politique de prise en charge des navigateurs](https://docs.newrelic.com/docs/browser/new-relic-browser/getting-started/compatibility-requirements-browser-monitoring/#browser-types), la version 1.295.0 de l'agent de Browser a été conçue et testée sur ces navigateurs et plages de versions : Chrome 128-138, Edge 128-138, Safari 17-19 et Firefox 130-140. Pour les appareils mobiles, la version 1.295.0 a été créée et testée pour Android OS 16 et iOS Safari 17-26. \ No newline at end of file diff --git a/src/i18n/content/fr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.296.mdx b/src/i18n/content/fr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.296.mdx new file mode 100644 index 00000000000..1c13b3f0f23 --- /dev/null +++ b/src/i18n/content/fr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.296.mdx @@ -0,0 +1,34 @@ +--- +subject: Browser agent +releaseDate: '2025-08-19' +version: 1.296.0 +downloadLink: 'https://www.npmjs.com/package/@newrelic/browser-agent' +features: + - Harvest traces early +bugs: + - Remove event buffer inspection event +security: [] +translationType: machine +--- + +## v1.296.0 + +### Caractéristiques + +#### Traces de récolte précoces + +Mettre à jour l'agent pour gérer la trace de session de la même manière que les autres fonctionnalités gèrent les données à partir de [la version 1.294.0](https://docs.newrelic.com/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.294.0/), en permettant des récoltes à une taille de 16 ko. + +### Débogage + +#### Supprimer le tampon d'événement inspection événement + +Supprime l'événement d'inspection du tampon d'événements pour éviter une fuite de mémoire lors de l'utilisation de la console.log avec l'écouteur d'événements de fenêtre `newrelic`. + +## Déclaration de soutien + +New Relic vous recommande de mettre à niveau l'agent régulièrement pour vous assurer de bénéficier des dernières fonctionnalités et avantages en termes de performances. Les sorties plus anciennes ne seront plus prises en charge lorsqu'elles atteindront [la fin de leur vie](https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/browser-agent-eol-policy/). Les dates de sortie reflètent la date de publication originale de la version de l'agent. + +Les nouveaux agents de navigation sont déployés auprès des clients par petites étapes sur une période donnée. De ce fait, la date à laquelle la sortie devient accessible sur votre compte peut ne pas correspondre à la date de publication d'origine. Veuillez consulter ce [dashboard d'état](https://newrelic.github.io/newrelic-browser-agent-release/) pour plus d'informations. + +Conformément à notre [politique de prise en charge des navigateurs](https://docs.newrelic.com/docs/browser/new-relic-browser/getting-started/compatibility-requirements-browser-monitoring/#browser-types), la version 1.296.0 de l'agent Browser a été conçue et testée sur ces navigateurs et plages de versions : Chrome 129-139, Edge 129-139, Safari 17-19 et Firefox 131-141. Pour les appareils mobiles, la version 1.296.0 a été créée et testée pour Android OS 16 et iOS Safari 17-18.1. \ No newline at end of file diff --git a/src/i18n/content/fr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.297.mdx b/src/i18n/content/fr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.297.mdx new file mode 100644 index 00000000000..d923f60c65c --- /dev/null +++ b/src/i18n/content/fr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.297.mdx @@ -0,0 +1,27 @@ +--- +subject: Browser agent +releaseDate: '2025-09-17' +version: 1.297.1 +downloadLink: 'https://www.npmjs.com/package/@newrelic/browser-agent' +features: [] +bugs: + - Prevent double import of Session Replay aggregate class +security: [] +translationType: machine +--- + +## v1.297.1 + +### Débogage + +#### Empêcher la double importation de la classe d'agrégation Session Replay + +Corrige un problème qui a été détecté où la classe d'agrégation Session Replay pouvait être importée deux fois lors de l'utilisation de la méthode API newrelic.recordReplay lors du préchargement a été activée. + +## Déclaration de soutien + +New Relic vous recommande de mettre à niveau l'agent régulièrement pour vous assurer de bénéficier des dernières fonctionnalités et avantages en termes de performances. Les sorties plus anciennes ne seront plus prises en charge lorsqu'elles atteindront [la fin de leur vie](https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/browser-agent-eol-policy/). Les dates de sortie reflètent la date de publication originale de la version de l'agent. + +Les nouveaux agents de navigation sont déployés auprès des clients par petites étapes sur une période donnée. De ce fait, la date à laquelle la sortie devient accessible sur votre compte peut ne pas correspondre à la date de publication d'origine. Veuillez consulter ce [dashboard d'état](https://newrelic.github.io/newrelic-browser-agent-release/) pour plus d'informations. + +Conformément à notre [politique de prise en charge des navigateurs](https://docs.newrelic.com/docs/browser/new-relic-browser/getting-started/compatibility-requirements-browser-monitoring/#browser-types), la version 1.297.1 de l'agent du Browser a été conçue et testée sur ces navigateurs et plages de versions : Chrome 130-140, Edge 130-140, Safari 17-19 et Firefox 132-142. Pour les appareils mobiles, la version 1.297.1 a été créée et testée pour Android OS 16 et iOS Safari 17-18.5. \ No newline at end of file diff --git a/src/i18n/content/fr/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.mdx b/src/i18n/content/fr/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.mdx new file mode 100644 index 00000000000..2170b7cf12c --- /dev/null +++ b/src/i18n/content/fr/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.mdx @@ -0,0 +1,10 @@ +--- +subject: Node API runtime +releaseDate: '2025-07-29' +version: 1.2.122 +translationType: machine +--- + +### Corrections + +* Correction des vulnérabilités des données de formulaire et des vulnérabilités Ubuntu sous-jacentes pour résoudre les vulnérabilités de sécurité dans les environnements d'exécution de l'API Node. \ No newline at end of file diff --git a/src/i18n/content/fr/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.mdx b/src/i18n/content/fr/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.mdx new file mode 100644 index 00000000000..5c9271f27d8 --- /dev/null +++ b/src/i18n/content/fr/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.mdx @@ -0,0 +1,10 @@ +--- +subject: Node browser runtime +releaseDate: '2025-07-29' +version: 3.0.39 +translationType: machine +--- + +### Améliorations + +* Correction des vulnérabilités des données de formulaire et des vulnérabilités Ubuntu sous-jacentes pour résoudre les vulnérabilités de sécurité dans les environnements d'exécution Browser Node. \ No newline at end of file diff --git a/src/i18n/content/fr/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.53.mdx b/src/i18n/content/fr/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.53.mdx new file mode 100644 index 00000000000..40b68beae40 --- /dev/null +++ b/src/i18n/content/fr/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.53.mdx @@ -0,0 +1,10 @@ +--- +subject: Ping Runtime +releaseDate: '2025-07-29' +version: 1.53.0 +translationType: machine +--- + +### Améliorations + +* Vulnérabilités corrigées liées à `common-lang3` Java et Ubuntu pour résoudre les problèmes de sécurité dans l'environnement d'exécution Ping. \ No newline at end of file diff --git a/src/i18n/content/fr/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.54.mdx b/src/i18n/content/fr/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.54.mdx new file mode 100644 index 00000000000..9cf6842663a --- /dev/null +++ b/src/i18n/content/fr/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.54.mdx @@ -0,0 +1,10 @@ +--- +subject: Ping Runtime +releaseDate: '2025-08-13' +version: 1.54.0 +translationType: machine +--- + +### Améliorations + +* Correction de vulnérabilités liées à Ubuntu pour résoudre les problèmes de sécurité dans l'environnement d'exécution Ping. \ No newline at end of file diff --git a/src/i18n/content/jp/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation.mdx b/src/i18n/content/jp/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation.mdx new file mode 100644 index 00000000000..3d58ebbbfa1 --- /dev/null +++ b/src/i18n/content/jp/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation.mdx @@ -0,0 +1,70 @@ +--- +title: CloudFormationとCloudWatchメトリックストリームを介して統合 +tags: + - Integration via CloudFormation + - AWS metric integration + - Amazon integrations + - AWS integrations + - Integration with CloudWatch Metric Streams via CloudFormation +metaDescription: Integrate New Relic with AWS services using CloudFormation templates to automate the setup of CloudWatch Metric Streams for metrics ingestion. +freshnessValidatedDate: never +translationType: machine +--- + +AWSアカウントとNew Relicをシームレスに統合するには、これが最も推奨される統合プロセスです。 CloudWatch メトリック ストリームでサポートされていないサービスに対してAPIポーリングを利用できます。 + +## 前提条件 [#prerequisites] + +AWS アカウントと New Relic の統合を開始する前に、次の前提条件を満たしていることを確認してください。 + +* **New Relic[ライセンスキー](https://one.newrelic.com/api-keys)**: AWSサービスをNew Relicアカウントに接続するには、ライセンスキーが必要です。 +* **[](https://docs.aws.amazon.com/ARG/latest/userguide/gettingstarted-prereqs-permissions.html)**新しい AWS リソースと**[ IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html)** ロール をデプロイするための 権限: AWS アカウントにはこの権限が必要です。 +* クラウド統合の**[権限](/docs/accounts/accounts-billing/new-relic-one-user-management/user-permissions/#infrastructure)**: New Relicアカウントにはこれらの権限が必要です。 + +## 統合手順 [#integration-steps] + +CloudFormation と CloudWatch Metric Streams を使用して AWS アカウントを New Relic と統合するには、次の手順に従います。 + +1. [**Infrastructure > AWS**](https://one.newrelic.com/infra/infrastructure/cloud-aws)に移動します。 + +2. 正しいアカウントを選択してください。 + +3. **Set up integration**をクリックします。 + +4. 各画面の指示に従って、該当するフィールドに入力します。この統合では、所定の画面で次のオプションを選択します。 + + 1. **Choose Data type(s)**Metrics + 2. **Choose a setup method**Automate AWS with CloudFormation (Recommended) + 3. **Choose a metrics integration type**CloudWatch Metric Stream (Recommended) + +5. CloudWatch メトリックストリームでサポートされていないサービスを使用している場合は、 **Choose a metrics integration type**ページで、 APIポーリングの 3 番目のステップで**Yes**を選択して続行します。 + + AWS Integration with CWMS and API Polling + +
+ サポートされていないサービスに対して選択された ポーリングによる サービスの CWMS 統合。AWSAPI +
+ + **Enable API Polling (optional)**ページの指示に従って必要な設定を行い、続行します。 + +6. Auto-discovery マップ上の AWS エンティティ間の関係を自動的に検出して視覚化し、その他の柔軟性も活用します。詳細については、 [「AWS エンティティの自動検出」](/docs/infrastructure/amazon-integrations/connect/set-up-auto-discovery-of-aws-entities/)を参照してください。この機能が必要な場合は、 **Enable Auto Discovery (optional)**ページで有効にして続行してください。 + +7. **Launch your CloudFormation in AWS**をクリックします。CloudFormationAWS New Relicテンプレートは、 での選択に基づいて構成された とともに コンソールで開くため、変更を加えない限り追加の編集は必要ありません。 + +8. ライセンスキーを AWS コンソールに貼り付けます。 + +9. Cloudformation スタックをデプロイするには、AWS コンソールで**Create stack**選択します。スタック リソースの作成には数分かかる場合があり、メトリクス転送の構成によっては複数のスタックが生成される場合があります。 スタックの作成に失敗した場合は、 [トラブルシューティング手順](https://docs.newrelic.com/docs/logs/troubleshooting/aws-log-integration-issues/stack-creation-fails/)を参照してください。 + +10. スタックの作成が成功したら、New Relic プラットフォームに切り替えて、AWS にNew Relic データが表示されるまでガイド付き統合を続行します。 + +## 関連トピック [#related-topics] + + + + 複数の AWS アカウントからデータを収集する方法を学びます。 + + + + CloudWatch メトリック ストリームからメトリクスを探索して使用します。 + + \ No newline at end of file diff --git a/src/i18n/content/jp/docs/infrastructure/other-infrastructure-integrations/stripe-integration.mdx b/src/i18n/content/jp/docs/infrastructure/other-infrastructure-integrations/stripe-integration.mdx index 785026a621d..3f23b8a1055 100644 --- a/src/i18n/content/jp/docs/infrastructure/other-infrastructure-integrations/stripe-integration.mdx +++ b/src/i18n/content/jp/docs/infrastructure/other-infrastructure-integrations/stripe-integration.mdx @@ -102,7 +102,7 @@ WHERE metricName = 'stripe_metrics' ### Stripe 監視ダッシュボードをインストールする [#add-dashboard] -アプリケーションのメトリクスを監視するために事前に構築された Stripe ダッシュボードを設定するには、 [Stripe ダッシュボードのインストール](https://onenr.io/0ZQWYYE1rRW) に移動し、指示に従います。インストールすると、ダッシュボードにメトリクスが表示されるはずです。 +アプリケーション メトリクスを監視するために事前に構築されたStripeダッシュボードをセットアップするには、 [Stripeダッシュボード インストレーション](https://onenr.io/0BQrXaNgnRZ)にアクセスし、指示に従ってください。 インストールすると、ダッシュボードにメトリクスが表示されるはずです。 ダッシュボードに関するヘルプが必要な場合は、以下を参照してください。 diff --git a/src/i18n/content/jp/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx b/src/i18n/content/jp/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx index 16aa2110aa2..d7b6a39b281 100644 --- a/src/i18n/content/jp/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx +++ b/src/i18n/content/jp/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx @@ -346,15 +346,24 @@ FROM PageAction SELECT keyset() SINCE 1 day ago - タイプ `NRQL/ENUM`の変数を作成するときに、表示オプション セクションから複数値オプションを有効にすることができます。 + You can enable the multi-value option to allow users to select multiple values from a dropdown instead of just one. This is useful when you want to filter data across multiple criteria simultaneously. - `{{MultiValue}}` という名前の変数を作成し、一意のすべての eventId のリストを返すクエリの例を次に示します。 + Multi-value is available for Query and List variable types. Text field variables don't support the multi-value option. + + To enable multi-value: + + 1. When creating a Query or List template variable, select the **Multi-value** option. + 2. In your widget queries, use the `IN` operator instead of `=` to handle multiple selected values. + + /* You can enable the multi-value option from the display options section when creating a variable of type `NRQL/ENUM`. */ + + Here's an example where you'd name your variable `{{MultiValue}}` and use this query to populate its values: ```sql SELECT uniques(eventId) FROM AjaxRequest ``` - Multi-value template variable example + /* <img width="30%;" title="Multi-value template variable example" alt="Multi-value template variable example" src="/images/dashboards_screenshot-crop_add-multivalue.webp" /> */ 次に、次のクエリでウィジェットを作成します。 @@ -362,22 +371,36 @@ FROM PageAction SELECT keyset() SINCE 1 day ago SELECT count(*) FROM AjaxRequest WHERE eventId IN ({{MultiValue}}) ``` - Creating a widget + /* <img width="80%;" title="Creating a widget" alt="Creating a widget" src="/images/dashboards_screenshot-full_multivalue-add-widget.webp" /> */ - 一度に定義できるテンプレート変数は 1 つだけですが、1 つのウィジェットで複数のテンプレート変数を使用できます。 + While you can only define one template variable at a time, you can reference multiple variables within the same widget. + + For this example, you need to have the two variables set up: + + 1. `countryCode` variable: Use the query shown earlier in this document: + + ```sql + SELECT uniques(countryCode) FROM PageAction SINCE 2 days ago + ``` + + 2. `city` variable with a similar query: + + ```sql + SELECT uniques(city) FROM PageView SINCE 1 week ago + ``` - 次に、2 つのテンプレート変数を使用するクエリの例を示します。これは、 `countryCode` および `city` テンプレート変数がすでに作成されており、それらの値が 1 つであることを前提としていることに注意してください。 + Here's an example using the above template variables with single values to create the widget: ```sql SELECT countryCode, city FROM PageAction WHERE countryCode = {{countryCode}} AND city = {{city}} ``` - Creating a widget using multiple variables + /* <img title="Creating a widget using multiple variables" alt="Creating a widget using multiple variables" src="/images/dashboards_screenshot-crop_add-widget-multiple-variable.webp" /> */ - `city` 変数の `Chicago` 、 `New York` 、 `Paris` など、変数に複数の値がある場合は、 `IN`を使用する必要があります。 + If your variables support multiple values (such as `Chicago`, `New York`, `Paris` for your `city` variable), you need to use `IN`: ```sql SELECT countryCode, city FROM PageAction @@ -398,7 +421,7 @@ FROM PageAction SELECT keyset() SINCE 1 day ago SELECT uniques(aparse(platformVersion, 'release-*')) FROM PageView ``` - Creating the release version variable + /* <img width="40%;" title="Creating the release version variable" alt="Creating the release version variable" src="/images/dashboards_screenshot-crop_add-var-release-version.webp" /> */ 次に、次のクエリでウィジェットを作成します。 @@ -407,7 +430,7 @@ FROM PageAction SELECT keyset() SINCE 1 day ago WHERE aparse(platformVersion, 'release-*') IN ({{releaseversion}}) FACET platformVersion ``` - Creating the widget + /* <img title="Creating the widget" alt="Creating the widget" src="/images/dashboards_screenshot-crop_add-widget-aparse.webp" /> */ または、 [`capture`](/docs/query-your-data/nrql-new-relic-query-language/get-started/nrql-syntax-clauses-functions/#func-capture) コマンドを使用することもできます。 @@ -416,15 +439,20 @@ FROM PageAction SELECT keyset() SINCE 1 day ago WHERE capture(platformVersion, r'release-(?P\d+)') IN ({{releaseversion}}) FACET platformVersion ``` - Creating the widget + /* <img title="Creating the widget" alt="Creating the widget" src="/images/dashboards_screenshot-crop_add-widget-capture.webp" /> */ `LIKE` と `RLIKE` テンプレート変数として使用して、ダッシュボード内のデータをフィルタリングできます。この機能を使用するには、テンプレート変数の作成時に追加する値で、値の先頭と末尾に `%` ワイルドカード記号を使用する必要があります。 - ここに例を示します。次に示すように、文字列変数を定義します。 + Here's an example. You define a string template variable with the following values: + + * **Name to use in queries:** line\_filter + * **タイプ:** `Text field` + * **Default value:** %@%.com + * **Output format:** `String` - Add `LIKE` as template variable + /* <img width="40%;" title="Add `LIKE` as template variable" alt="Add `LIKE` as template variable" src="/images/dashboards_screenshot-crop_add-var-like-filter.webp" /> */ 次に、ウィジェット グラフを作成し、次のように変数を使用できます。 @@ -432,7 +460,7 @@ FROM PageAction SELECT keyset() SINCE 1 day ago FROM NrdbQuery SELECT user WHERE user LIKE {{like_filter}} ``` - Add `LIKE` as template variable + /* <img title="Add `LIKE` as template variable" alt="Add `LIKE` as template variable" src="/images/dashboards_screenshot-crop_add-widget-like-filter.webp" /> */ またはこのように: @@ -450,13 +478,13 @@ FROM PageAction SELECT keyset() SINCE 1 day ago > 文字列出力形式で NRQL 型の変数を作成し、それを `FACET` 句の後に使用して、異なる値でグループ化できます。 - たとえば、次のような `{{userAgentName}}` という名前の変数を作成できます。 + For example, you might create a template variable named `{{userAgentName}}` that would look like: ```sql SELECT uniques(userAgentName) FROM PageAction ``` - Creating the variable + /* <img width="30%;" title="Creating the variable" alt="Creating the variable" src="/images/dashboards_screenshot-crop_add-var-facet.webp" /> */ 次に、次のクエリを使用してウィジェットを作成します。 @@ -465,15 +493,20 @@ FROM PageAction SELECT keyset() SINCE 1 day ago WHERE userAgentName={{userAgentName}} FACET userAgentName ``` - Creating widget using facet + /* <img title="Creating widget using facet" alt="Creating widget using facet" src="/images/dashboards_screenshot-crop_add-widget-facet.webp" /> */ `identifier`出力形式で変数を作成し、それを`FACET`句の後に使用して、さまざまな値でグループ化できます。 - たとえば、 `countryCode`と`city`の 2 つの可能な値を持つリスト型の`{{location}}`変数を作成するとします。出力形式を`identifier`に設定します。 + For example, you might create a `{{location}}` variable: - Adding the variable for dynamic grouping + * **Name to use in queries:** location + * **タイプ:** `List` + * **Values separated by commas:** `countryCode` and `city` + * **Output format:** `Identifier` + + /* <img width="40%;" title="Adding the variable for dynamic grouping" alt="Adding the variable for dynamic grouping" src="/images/dashboards_screenshot-crop_add-var-dynamic-grouping.webp" /> */ 次に、次のクエリを使用してウィジェットを作成します。 @@ -481,15 +514,20 @@ FROM PageAction SELECT keyset() SINCE 1 day ago SELECT count(*) FROM PageAction FACET {{location}} ``` - Adding the widget for dynamic grouping + /* <img title="Adding the widget for dynamic grouping" alt="Adding the widget for dynamic grouping" src="/images/dashboards_screenshot-crop_add-widget-dynamic-grouping.webp" /> */ 出力形式`number`で変数を作成し、それをパーセンタイル関数内で使用できます。 - たとえば、 `55`と`90`の 2 つの可能な値を持つタイプ`list`の`{{percentile}}`変数を作成できます。出力形式を`number`として設定したいと思います。 + For example, you could create a `{{percentile}}` variable: + + * **Name to use in queries:** percentile + * **タイプ:** `List` + * **Values separated by commas:** `55` and `90` + * **Output format:** `Number` - Adding the variable for dynamically change the percentile + /* <img width="40%;" title="Adding the variable for dynamically change the percentile" alt="Adding the variable for dynamically change the percentile" src="/images/dashboards_screenshot-crop_add-var-dynamic-percentile.webp" /> */ 次に、次のクエリを使用してウィジェットを作成します。 @@ -497,7 +535,7 @@ FROM PageAction SELECT keyset() SINCE 1 day ago SELECT percentile(duration, {{percentile}}) FROM PageAction ``` - Adding the widget for dynamically change the percentile + /* <img title="Adding the widget for dynamically change the percentile" alt="Adding the widget for dynamically change the percentile" src="/images/dashboards_screenshot-crop_add-widget-dynamic-percentile.webp" /> */ @@ -508,7 +546,7 @@ FROM PageAction SELECT keyset() SINCE 1 day ago WHERE countryCode IN ({{countryCode}}) ``` - Use variables to filter + /* <img title="Use variables to filter" alt="Use variables to filter" src="/images/dashboards_screenshot-crop_variables-to-filter.webp" /> */ @@ -528,7 +566,7 @@ FROM PageAction SELECT keyset() SINCE 1 day ago これにより、過去 30 分間の値が得られます。 タイムピッカーの値を**Default**に設定し、クエリに`SINCE`句が含まれている場合、最新の値を使用してクエリが実行されます。 - A screenshot showing the variable form + /* <img title="Example form" alt="A screenshot showing the variable form" src="/images/dashboards_screenshot-crop_example-form.webp" /> */ + 最新のエージェント バージョンが利用可能になったらすぐに更新することをお勧めします。組織で最新バージョンへの更新を妨げる慣行が確立されている場合は、エージェントが最大 90 日前のバージョンに定期的に更新されるようにしてください。[エージェントを最新の状態に保つ方法](https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/)の詳細については、こちらをご覧ください。 + + +## 3.41.0 + +### 追加した + +* ディストリビューティッド(分散)トレーシングの受信リクエストのサンプリング動作を制御するための`DistributedTracer.Sampler`構成オプションを追加しました + + * サンプラーを設定するために、リモート親がフラグ付けした内容に基づいてサンプリング動作を処理する`ConfigRemoteParentSampled(flag RemoteParentSamplingConfig)`と`ConfigRemoteParentNotSampled(flag RemoteParentSamplingConfig)`を追加しました + * 追加されたフラグは`"always_on", "always_off", and "default"`で、 `RemoteParentSamplingConfig` + * `Example: newrelic.ConfigRemoteParentSampled(newrelic.AlwaysOff)` + +* OOM監視テストを追加しました + +* セキュアエージェントのテスト範囲の拡大 + +### 修理済み + +* 報告されたセキュリティまたはその他のサポートの問題により、サードパーティ ライブラリのバージョンが更新されました。 + + * `github.com/gofiber/fiber/v2` `nrfiber`統合の 2.52.7 から 2.52.9 へ + * `golang.org/x/net` `nrconnect`統合の 0.25.0 から 0.38.0 + +### サポートステートメント + +私たちは Go 言語の最新バージョンを使用します。少なくとも、Go チーム自身がサポートしているバージョンよりも古いバージョンの Go は使用しないでください。[Go エージェントおよびサードパーティ コンポーネントのサポートされているバージョンの詳細については、Go エージェントの EOL ポリシー](https://docs.newrelic.com/docs/apm/agents/go-agent/get-started/go-agent-eol-policy/)を参照してください。 \ No newline at end of file diff --git a/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx b/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx new file mode 100644 index 00000000000..9e024f7adf7 --- /dev/null +++ b/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx @@ -0,0 +1,60 @@ +--- +subject: Docs +releaseDate: '2025-08-08' +version: 'August 01 - August 07, 2025' +translationType: machine +--- + +### 新しいドキュメント + +* [NerdGraph チュートリアル「チームのカスタム ロールの作成」が追加され、](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/compute-budgets/overview) New Relic NerdGraph API を使用してチームのカスタム ロールを作成および管理する方法が説明されました。 + +### マイナーチェンジ + +* [条件ごとの集中イベントの値を](/docs/alerts/admin/rules-limits-alerts)1 分あたり 1,000 に変更しました。 +* 最新の検証済み[.Net エージェント互換バージョンと要件](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements)を更新しました。 +* [VMware Tanzu](/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-service-broker-integration)のサービス ブローカーのバージョンおよびバージョン サポート情報を更新しました。 +* [VMware Tanzu](/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-nginx-buildpack-integration)用のNew Relic NGINX 統合ビルドパックに関するバージョン サポート情報を更新しました。 +* New Relic Nozzle for [VMware Tanzu](/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-firehose-nozzle-integration/#product-snapshot)のバージョンおよびバージョン サポート情報を更新しました。 + +### リリースノート + +* 新着情報投稿をご覧ください: + + * [Errors Inboxはワークロード内に統合されました](/whats-new/2025/08/whats-new-08-06-workloads-errors-inbox)。 + +* 弊社の最新リリース情報を常に把握してください: + + * [ジョブマネージャー v452](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-452) : + * キュー メッセージの処理における例外処理の内部的な改善を追加しました。 + + * [Kubernetesインテグレーション v3.43.3](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-43-3) : + * New Relic Kubernetes 監視ソリューションをデプロイするための Helm チャートを追加しました。 + + * [Pipeline Controlゲートウェイ v1.1.0](/docs/release-notes/pipeline-control-gateway-release-notes/pipeline-control-gateway-25-08-05) : + + * ドロップ ルールを使用して`SqlTrace`および`TransactionTrace`イベントからデータと属性を選択的にドロップする新しい機能を実装しました。 + + * クロスサイト スクリプトの問題や、IPv6 ゾーン ID に関連する HTTP プロキシ バイパスなど、 `golang.org/x/net`パッケージの脆弱性に対処しました。 + + * Go `1.24`にアップグレードされ、セキュリティを強化し、最近の修正を組み込むために次の依存関係が更新されました。 + + * `golang.org/x/net to v0.38.0` + * `golang.org/x/sys to v0.31.0` + * `golang.org/x/text to v0.23.0` + + * [iOS向けモバイルアプリv6.9.11](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6101) : + * ユーザーの認証ドメインを保存し、ユーザーをサインイン ページに直接リダイレクトすることで、ログイン フローを 2 ステップ削減しました。 + + * [Flutterエージェント v1.1.13](/docs/release-notes/mobile-release-notes/flutter-release-notes/flutter-agent-1113) : + + * ネイティブ Android エージェントがバージョン 7.6.8 にアップデートされました + * ネイティブ iOS エージェントがバージョン 7.5.8 にアップデートされました + + * [.NET MAUI エージェント v1.1.11](/docs/release-notes/mobile-release-notes/net-maui-release-notes/net-maui-agent-1111) + + * ネイティブ Android エージェントがバージョン 7.6.8 にアップデートされました + * ネイティブ iOS エージェントがバージョン 7.5.8 にアップデートされました + + * [インフラストラクチャエージェント v1.65.5](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1655) : + * ストレージサンプルのAWS efsマウントのサポートを変更しました \ No newline at end of file diff --git a/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-8-14-2025.mdx b/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-8-14-2025.mdx new file mode 100644 index 00000000000..a7591ff8b81 --- /dev/null +++ b/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-8-14-2025.mdx @@ -0,0 +1,112 @@ +--- +subject: Docs +releaseDate: '2025-08-15' +version: 'August 08 - August 14, 2025' +translationType: machine +--- + +### 新しいドキュメント + +* [ゲートウェイ ルールでのNRQL関数のサポート](/docs/new-relic-control/pipeline-control/nrql-functions)を追加しPipeline Controlゲートウェイ ルールでサポートされるNRQL関数の概要を示しました。 +* New Relic Infrastructure エージェント設定でホスト名の解決設定を調整することで[、頻繁なFluent Bit Restart イベント](/docs/infrastructure/infrastructure-troubleshooting/troubleshoot-infrastructure/frequent-fluent-bit-restart-events)を解決するためのトラブルシューティング手順を追加しました。 + +### 主な変更点 + +* 最新の価格情報に合わせて[使用プラン](/docs/licenses/license-information/usage-plans/new-relic-usage-plan/#list-price)を更新しました。 +* [ワークロード UI](/docs/new-relic-solutions/new-relic-one/workloads/use-workloads/#errors) に **Error inbox** \[エラー受信トレイ] を追加しました。 +* [Javaエージェント設定](/docs/apm/agents/java-agent/configuration/java-agent-configuration-config-file/#skip-applications)のセキュリティ設定を強化するとともに、環境変数を介して起動メイン クラスまたは実行可能 jar に基づいて選択的エージェントを無効にする機能を追加しました。 +* Agent Controlに[プライベート リポジトリ設定](/docs/new-relic-control/agent-control/configuration/#private-repository-configuration)のサポートが追加され、基本または TLS 証明書方式による認証による管理対象エージェントのプロイメントが可能になります。 +* Agent Controlに[Secret Management](/docs/new-relic-control/agent-control/configuration/#secrets-management)のサポートが追加されました。これにより、専用のシークレット プロバイダーからパスワードやAPIキーなどの機密データを取得して管理できるようになります。 + +### マイナーチェンジ + +* [Pipeline Control クラウド ルールを使用して、Drop data](/docs/new-relic-control/pipeline-control/cloud-rules-api/#restrictions)の`WHERE`句にエンティティ タグ制限を追加しました。 +* New Relic AI Knowledge コネクタの[ナレッジ ソース コンテンツを最適化するためのベストプラクティス](/docs/agentic-ai/knowledge-integration/overview/#configure)を追加しました。 + +### リリースノート + +* 新着情報投稿をご覧ください: + + * [UniqueCount 高精度モードと引数サポートの増加が一般提供されました](/whats-new/2025/08/whats-new-8-13-high-precision-uniquecount)。 + +* 弊社の最新リリース情報を常に把握してください: + + * [Cordovaエージェント v7.0.8](/docs/release-notes/mobile-release-notes/cordova-release-notes/cordova-agent-708/) : + + * ネイティブ Android エージェントをバージョン 7.6.8 に更新します + * ネイティブ iOS エージェントをバージョン 7.5.8 に更新します + + * [Cordovaエージェント v7.0.9](/docs/release-notes/mobile-release-notes/cordova-release-notes/cordova-agent-709/) : + + * ネイティブ Android エージェントをバージョン 7.6.6 に更新します + * ネイティブ iOS エージェントをバージョン 7.5.5 に更新します + + * [Capacitor v1.5.8](/docs/release-notes/mobile-release-notes/capacitor-release-notes/capacitor-agent-158/) : + + * ネイティブ Android エージェントをバージョン 7.6.6 に更新します + * ネイティブ iOS エージェントをバージョン 7.5.5 に更新します + + * [Capacitor v1.5.9](/docs/release-notes/mobile-release-notes/capacitor-release-notes/capacitor-agent-159/) : + * 中止信号のクラッシュを修正 + + * [Capacitor v1.5.10](/docs/release-notes/mobile-release-notes/capacitor-release-notes/capacitor-agent-1510/) : + + * ネイティブ Android エージェントをバージョン 7.6.8 に更新します + * ネイティブ iOS エージェントをバージョン 7.5.8 に更新します + + * [診断 CLI (nrdiag) v3.5.0](/docs/release-notes/diagnostics-release-notes/diagnostics-cli-release-notes/diagnostics-cli-350/) : + * `Java/Appserver/JbossEapCheck`バージョンの互換性チェックを更新しました + + * [.NET エージェント v10.44.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-44-0/) : + + * Serverlessモードでパフォーマンス メトリクス サンプラーを有効にしました + * Azure Function webhost (Linux) プロセスを計装から除外しました。 + + * [NRDOT v1.3.0](/docs/release-notes/nrdot-release-notes/nrdot-2025-08-13/) : + + * オテルコンポーネントのバージョンを v0.128.0 から v0.131.0 に上げました + * nrdotコアディストリビューションを導入 + + * [Node.jsエージェント v13.1.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-1-0/) : + + * OTEL ログAPIのサポートを追加しました + * パッケージで計装が無効になっている場合のメトリクスのサポートを追加しました + * サンプル設定ではデフォルトで無効になっているタイマーを計装しています + * `transaction.url`難読化を修正しました + + * [ジョブマネージャーv454](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-454/) : + * SJM のセキュリティ脆弱性に対処するために、Ubuntu の根本的な脆弱性を修正しました。 + + * [Node API ランタイム v1.2.124](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.124/) : + * Node API ランタイムのセキュリティ脆弱性に対処するために、根本的な Ubuntu の脆弱性を修正しました。 + + * [Node ブラウザ ランタイム v3.0.41](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.41/) : + * ノードBrowserランタイムのセキュリティ脆弱性に対処するために、tmp `CVE-2025-54798`脆弱性と基礎となる Ubuntu 脆弱性を修正しました。 + + * [Pingランタイムv1.54.0](/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.54.0/) : + * Ping ランタイムのセキュリティ問題に対処するために、Ubuntu に関連する脆弱性を修正しました。 + + * [Javaエージェント v8.23.0](/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8230/) : + + * graphql の v24 をサポートするように更新されました。 + * レタス6.5計装を追加しました。 + * commons-lang バージョンを 3.18.0 にアップグレードしました + + * [AWS Lambda ログフォワーダー v1.1.1](/docs/release-notes/aws-lambda-log-forwarder-release-notes/lambda-25-07-25/) : + * システムの Go バージョンを 1.24.4 にアップグレードすることで、セキュリティ体制を強化しました。 + + * [PHPエージェント v12.0.0.25](/docs/release-notes/agent-release-notes/php-release-notes/php-agent-12-0-0-25/) : + + * Drupal フック マップのエラー ログが改善されました。 + * Security RX のレガシー パッケージ検出の問題を修正しました。 + + * [インフラストラクチャエージェント v1.66.1](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1661/) : + * ストレージ サンプルの AWS EFS マウントのサポートを元に戻しました。 + + * [Android用モバイルアプリv5.30.6](docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5306/) : + * SAML およびソーシャル ログインのパスキー サポートが強化されました。 + + * [Browser v1.295.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.0/) : + + * エラー原因の検出を追加しました。 + * モンキーパッチの警告を追加しました。 \ No newline at end of file diff --git a/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-9-12-2025.mdx b/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-9-12-2025.mdx new file mode 100644 index 00000000000..5e0abc2d13d --- /dev/null +++ b/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-9-12-2025.mdx @@ -0,0 +1,94 @@ +--- +subject: Docs +releaseDate: '2025-09-14' +version: 'September 08 - September 12, 2025' +translationType: machine +--- + +### 新しいドキュメント + +* ビジネス実行時間、デジタル エクスペリエンス、エンジニアリング エクセレンス、インテリジェント オブザーバビリティの 4 つの主要領域にわたるオブザーバビリティの実践を測定および改善するためのガイダンスを提供する、包括的な[オブザーバビリティ成熟度モデルの](/docs/new-relic-solutions/observability-maturity/)ドキュメントを追加しました。 + +### 主な変更点 + +* サンプリング コントロールとフレームワーク例外ハンドラー計装のための広範な新しい設定オプションを備えた[PHP エージェント設定](/docs/apm/agents/php-agent/configuration/php-agent-configuration/)を更新しました。 + +### マイナーチェンジ + +* ダッシュボードの使用に関するガイダンスを強化して[ダッシュボードの紹介](/docs/query-your-data/explore-query-data/dashboards/introduction-dashboards/)を更新しました。 +* JSON 管理のコンテンツが簡素化された、[ダッシュボード管理](/docs/query-your-data/explore-query-data/dashboards/manage-your-dashboard/)ドキュメントが強化されました。 +* [New Relic 使用プランの](/docs/licenses/license-information/usage-plans/new-relic-usage-plan/)ドキュメント内の壊れたリンクを修正しました。 +* [.NET エージェント トラブルシューティング](/docs/apm/agents/net-agent/troubleshooting/debugging-net-windows/)ドキュメントのデバッグ設定を修正しました。 + +### リリースノート + +* 弊社の最新リリース情報を常に把握してください: + + * [Browser v1.297.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.297.0/) : + + * レート制限処理を改善するために、再試行期間中の早期収穫を防止しました。 + * 課金対象バイトを削減するために、送信されるリプレイ ペイロードから NewRelic メタ属性を削除しました。 + * 空の収穫から発生するヌル ボディの例外を修正しました。 + + * [PHPエージェント v12.1.0.26](/docs/release-notes/agent-release-notes/php-release-notes/php-agent-12-1-0-26/) : + + * アップストリームの w3c トレースサンプリングの決定に基づいたサンプリング制御を追加しました。 + * フレームワーク例外ハンドラーの計装をスキップする設定オプションを追加しました。 + * `newrelic_end_transaction(true)`呼び出すときに発生する可能性のあるメモリ リークを修正しました。 + * セキュリティ強化のため、golang バージョンを 1.25.1 にアップグレードしました。 + + * [Pythonエージェント v10.17.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-101700/) : + + * Celery のカスタム タスクのサポートが追加されました。 + * Graphene-Django 監視のサポートが追加されました。 + * Django でのミドルウェア フィルタリングのサポートが追加されました。 + * AWS Bedrock Converse API のサポートが追加されました。 + * W3CTraceParent ヘッダー サンプリング フラグのサポートが追加されました。 + + * [Javaエージェント v8.24.0](/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8240/) : + + * MongoDB Reactive Streams 5.2.0 以降のサポートが追加されました。 + * Jedis 6のサポートを追加しました。 + * CouchBaseの二重計装の問題を修正しました。 + * Spring WebClient 5.x のヘッダー ラッピングの問題を修正しました。 + + * [Node.jsエージェント v13.3.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-3-0/) : + + * MCP `StreamableHTTPClientTransport`サポートが追加されました。 + + * [Node.jsエージェント v13.3.1](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-3-1/) : + + * `requestParameters` `transaction.addRequestParameters`内のオブジェクトにデフォルト設定することでクラッシュする問題を修正しました。 + + * [Node.jsエージェント v13.3.2](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-3-2/) : + + * アウトバウンド HTTP 呼び出しで`protocol`取得するための防御コードを追加しました。 + + * [Kubernetesインテグレーション v3.45.1](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-45-1/) : + + * 最新の改善とバグ修正を加えて更新されました。 + + * [ジョブマネージャーv464](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-464/) : + + * 顧客が podman を使用してカスタム レジストリからイメージをプルできない問題を修正しました。 + + * [Node ブラウザ ランタイム v3.0.43](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.43/) : + + * セキュリティの脆弱性に対処するために、Ubuntu の根本的な脆弱性を修正しました。 + + * [iOS向けモバイルアプリv6.9.12](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6102/) : + + * ダッシュボードとアラートのディープリンクの問題を修正しました。 + * CCU ダッシュボード ID の問題を修正しました。 + + * [Android用モバイルアプリv5.30.7](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5307/) : + + * バグ修正と改善を追加しました。 + + * [Flutterエージェント v1.1.14](/docs/release-notes/mobile-release-notes/flutter-release-notes/flutter-agent-1114/) : + + * 追加の安定性の改善とバグ修正を追加しました。 + + * [Pipeline Controlゲートウェイ v25.09.01](/docs/release-notes/pipeline-control-gateway-release-notes/pipeline-control-gateway-25-09-01/) : + + * パイプライン制御機能が強化された新しいリリースが追加されました。 \ No newline at end of file diff --git a/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-9-15-2025.mdx b/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-9-15-2025.mdx new file mode 100644 index 00000000000..1f58da3da3d --- /dev/null +++ b/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-9-15-2025.mdx @@ -0,0 +1,84 @@ +--- +subject: Docs +releaseDate: '2025-09-19' +version: 'September 15 - September 19, 2025' +translationType: machine +--- + +### 新しいドキュメント + +* メトリクス向けに再構築されたAWSインテグレーション: + + * [AWSインテグレーションマニュアル](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/manual/)を追加 + * [Terraform AWSインテグレーション](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/terraform/)を追加しました + * [APIポーリング統合による CloudFormation を](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-and-api-polling/)追加しました + * [APIポーリングからCloudWatch Metric Streamsへの移行ガイド](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/migrate-from-api-polling-to-cwms/)を追加しました + +### 主な変更点 + +* スタンドアロン エージェント構造の更新により、[ストリーミング ビデオと広告のドキュメント](/docs/streaming-video-&-ads/get-started-with-streaming-video-&-ads/)が強化されました。 + +### マイナーチェンジ + +* [GitHub 経由で NerdGraph Issues API](/docs/apis/nerdgraph/examples/nerdgraph-issues-api-via-github/)を更新し、ドキュメントを強化しました。 +* [Microsoft Teams 統合](/docs/alerts-applied-intelligence/notifications/notification-integrations/)が更新され、設定ガイダンスが改善されました。 +* [ヒートマップ](docs/query-your-data/explore-query-data/use-charts/chart-types/#widget-heatmap)チャートの種類を更新しました。 +* [MySQL統合](/docs/infrastructure/host-integrations/host-integrations-list/mysql-monitoring-integration/)を更新し、QPM 監視のタイミングを改善しました。 +* マイナーアップデートにより[カーディナリティ管理](/docs/data-apis/ingest-apis/metric-api/cardinality-management/)ドキュメントが強化されました。 +* 最新の検証済み互換性ライブラリ バージョンで[.NET エージェントの互換性要件](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements/)を更新しました。 +* [パイプライン制御コードの](docs/new-relic-control/pipeline-control/cloud-rules-api/)バグドキュメントを修正しました。 + +### リリースノート + +* [IP アドレスの新しいサポート終了日を含む外形監視](/eol/2025/02/eol-01-31-25-synthetics-ip/)が更新されました。 + +* 弊社の最新リリース情報を常に把握してください: + + * [Javaエージェント v8.24.0](/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8240/) : + + * MongoDB Reactive Streams 5.2.0 以降のサポートが追加されました。 + * Jedis 6のサポートを追加しました。 + * CouchBaseの二重計装の問題を修正しました。 + * Spring WebClient 5.x のヘッダー ラッピングの問題を修正しました。 + + * [Pythonエージェント v10.17.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-101700/) : + + * Celery のカスタム タスクのサポートが追加されました。 + * Graphene-Django 監視のサポートが追加されました。 + * Django でのミドルウェア フィルタリングのサポートが追加されました。 + * AWS Bedrock Converse API のサポートが追加されました。 + * W3CTraceParent ヘッダー サンプリング フラグのサポートが追加されました。 + + * [インフラストラクチャエージェント v1.68.0](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/1680/) : + + * goバージョンを1.25.0にアップグレードしました。 + * 依存関係 newrelic/nri-winservices を v1.3.0 に更新しました。 + + * [Browser v1.298.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.298.0/) : + + * DOM 変更時間を超える長いタスクを含めるようにソフト ナビゲーション インタラクションを拡張しました。 + * ソフト ナビゲーション中に現在のページ URL ではなく元のページ URL を報告するように LCP を修正しました。 + + * [Browser v1.297.1](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.297.1/) : + + * newrelic.recordReplay を使用する際にセッションリプレイ集約クラスが二重にインポートされる可能性がある問題を修正しました。プリロード中の API メソッドが有効になりました。 + + * [React Nativeエージェント v1.5.10](/docs/release-notes/mobile-release-notes/react-native-release-notes/react-native-agent-1510/) : + + * ネイティブ Android エージェントをバージョン 7.6.9 に更新しました。 + * ネイティブ iOS エージェントをバージョン 7.5.10 に更新しました。 + + * [iOS エージェント v7.5.10](/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-7510/) : + + * エージェントの起動時に発生する可能性があったクラッシュを修正しました。 + + * [NRDOT v1.4.0](/docs/release-notes/nrdot-release-notes/nrdot-2025-09-18/) : + + * nrdot-collectors にspanprocessorを追加しました。 + * OpenTelemetry コンポーネントのバージョンを v0.131.0 から v0.132.0 に上げました。 + * newrelic.service.type を内部テレメトリー設定に追加しました。 + * EC2 の host.name 検出を有効にしました。 + + * [Kubernetesインテグレーション v3.45.2](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-45-2/) : + + * 最新の改善とバグ修正を加えて更新されました。 \ No newline at end of file diff --git a/src/i18n/content/jp/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-759.mdx b/src/i18n/content/jp/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-759.mdx index 4c010efbb4c..24dae8d0dbb 100644 --- a/src/i18n/content/jp/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-759.mdx +++ b/src/i18n/content/jp/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-759.mdx @@ -6,14 +6,6 @@ downloadLink: 'https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agen translationType: machine --- - - iOS SDKバージョン7.5.4以降では、以前は抑制されていた処理済み例外イベントが報告される変更が実装されました。 - - New Relic iOS エージェント 7.5.9 に更新してください。iOS SDKバージョン7.5.8に、データのアップロードに誤りが生じる可能性のあるバグが確認されました。New New Relic iOS エージェント7.5.9に修正が含まれています。 リリース。 - - New Relic iOS エージェント 7.5.9 に更新してください。エージェント リリースでクラッシュを引き起こす可能性のある iOS SDK バージョン 7.5.7 のバグを特定しました。修正はNew Relic iOS エージェント 7.5.9 に含まれています。 リリース。 - - ## このリリースで修正された点 * エージェントは Xcode 16.4 を使用して構築されます。 diff --git a/src/i18n/content/jp/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx b/src/i18n/content/jp/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx new file mode 100644 index 00000000000..6e5b982a15b --- /dev/null +++ b/src/i18n/content/jp/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx @@ -0,0 +1,39 @@ +--- +subject: Browser agent +releaseDate: '2025-08-04' +version: 1.295.0 +downloadLink: 'https://www.npmjs.com/package/@newrelic/browser-agent' +features: + - Add error cause detection +bugs: + - Add monkey-patching warnings + - Calculate first and last timestamps from raw data +security: [] +translationType: machine +--- + +## v1.295.0 + +### 特徴 + +#### エラー原因検出を追加 + +キャプチャされた JavaScriptError イベントの原因属性を検出して報告します。原因がエラーのインスタンスである場合はスタックトレースがキャプチャされ、それ以外の場合は原因の文字列化された内容が報告されます。 これは、属性`cause`の下の JavaScriptError イベントでクエリ可能になります。 + +### バグ修正 + +#### モンキーパッチの警告を追加する + +エージェントがページで実行される前に、予期されるグローバルにモンキーパッチが適用された場合の検出と警告を追加しました。これにより予期しない動作が発生する可能性があり、この動作について顧客に通知することが目的です。 + +#### 生データから最初と最後のタイムスタンプを計算する + +UI リプレーヤーの一貫性を向上させるために、収集前にエージェントが SessionReplay ペイロードの最初と最後のタイムスタンプを手動で計算することを確認します。 + +## サポートステートメント + +New Relic では、最新の機能とパフォーマンス上のメリットを確実に得られるよう、エージェントを定期的にアップグレードすることをお勧めします。古いリリースは[サポート終了](https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/browser-agent-eol-policy/)になるとサポートされなくなります。リリース日は、エージェント バージョンの元の公開日を反映します。 + +新しいブラウザエージェントのリリースは、一定期間にわたって小さな段階で顧客に展開されます。 このため、リリースがアカウントでアクセス可能になる日付は、元の公開日と一致しない可能性があります。詳細については、この[ステータス ダッシュボード](https://newrelic.github.io/newrelic-browser-agent-release/)をご覧ください。 + +弊社の[ブラウザ サポート ポリシー](https://docs.newrelic.com/docs/browser/new-relic-browser/getting-started/compatibility-requirements-browser-monitoring/#browser-types)に従い、 Browserの v1.295.0 は、 Chrome 128 ~ 138、Edge 128 ~ 138、Safari 17 ~ 19、Firefox 130 ~ 140 のブラウザとバージョン範囲向けに構築され、テストされました。 モバイル デバイスの場合、v1.295.0 は Android OS 16 および iOS Safari 17-26 用に構築およびテストされました。 \ No newline at end of file diff --git a/src/i18n/content/jp/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.297.mdx b/src/i18n/content/jp/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.297.mdx new file mode 100644 index 00000000000..9d3fed96462 --- /dev/null +++ b/src/i18n/content/jp/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.297.mdx @@ -0,0 +1,27 @@ +--- +subject: Browser agent +releaseDate: '2025-09-17' +version: 1.297.1 +downloadLink: 'https://www.npmjs.com/package/@newrelic/browser-agent' +features: [] +bugs: + - Prevent double import of Session Replay aggregate class +security: [] +translationType: machine +--- + +## バージョン1.297.1 + +### バグ修正 + +#### セッションリプレイ集約クラスの二重インポートを防止する + +newrelic.recordReplay の使用時にセッションリプレイ集約クラスが二重にインポートされる可能性がある問題を修正しました。プリロード中の API メソッドが有効になりました。 + +## サポートステートメント + +New Relic では、最新の機能とパフォーマンス上のメリットを確実に得られるよう、エージェントを定期的にアップグレードすることをお勧めします。古いリリースは[サポート終了](https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/browser-agent-eol-policy/)になるとサポートされなくなります。リリース日は、エージェント バージョンの元の公開日を反映します。 + +新しいブラウザエージェントのリリースは、一定期間にわたって小さな段階で顧客に展開されます。 このため、リリースがアカウントでアクセス可能になる日付は、元の公開日と一致しない可能性があります。詳細については、この[ステータス ダッシュボード](https://newrelic.github.io/newrelic-browser-agent-release/)をご覧ください。 + +弊社の[ブラウザ サポート ポリシー](https://docs.newrelic.com/docs/browser/new-relic-browser/getting-started/compatibility-requirements-browser-monitoring/#browser-types)に従い、 Browserの v1.297.1 は、 Chrome 130 ~ 140、Edge 130 ~ 140、Safari 17 ~ 19、Firefox 132 ~ 142 のブラウザとバージョン範囲向けに構築され、テストされました。 モバイル デバイスの場合、v1.297.1 は Android OS 16 および iOS Safari 17-18.5 用に構築およびテストされました。 \ No newline at end of file diff --git a/src/i18n/content/jp/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.54.mdx b/src/i18n/content/jp/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.54.mdx new file mode 100644 index 00000000000..d3726ad0d76 --- /dev/null +++ b/src/i18n/content/jp/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.54.mdx @@ -0,0 +1,10 @@ +--- +subject: Ping Runtime +releaseDate: '2025-08-13' +version: 1.54.0 +translationType: machine +--- + +### 改良点 + +* Ping ランタイムのセキュリティ問題に対処するために、Ubuntu に関連する脆弱性を修正しました。 \ No newline at end of file diff --git a/src/i18n/content/kr/docs/accounts/accounts-billing/new-relic-one-pricing-billing/add-on-billing.mdx b/src/i18n/content/kr/docs/accounts/accounts-billing/new-relic-one-pricing-billing/add-on-billing.mdx new file mode 100644 index 00000000000..65be8f0b577 --- /dev/null +++ b/src/i18n/content/kr/docs/accounts/accounts-billing/new-relic-one-pricing-billing/add-on-billing.mdx @@ -0,0 +1,28 @@ +--- +title: 추가 결제(선택사항) +tags: + - Accounts + - Accounts and billing + - New Relic pricing and billing +metaDescription: Add-ons are an optional billing factor +freshnessValidatedDate: '2024-10-23T00:00:00.000Z' +translationType: machine +--- + +GB Ingested 및 청구 가능 사용자의 기본 청구 요소 외에도 선택적 청구 가능 추가 기능을 사용하여 뉴렐릭의 경험을 확장할 수 있습니다. + +* **Advanced Compute \[高度なコンピューティング] (旧称 Add-on Compute \[アドオン コンピューティング])**: 이 애드온은 CodeStream, Live Archives 및 기타 사용 가능한 기능과 관련하여 실행하는 작업에 대한 사용량 기반 청구에 적용됩니다. [고급 CCU](/docs/licenses/license-information/product-definitions/new-relic-one-pricing-definitions/#compute-capacity-unit) 사용량에 따라 측정 및 요금이 청구됩니다. + + + 고급 컴퓨팅 모드에서 CodeStream 사용하면 사용자 유형에 관계없이 CCU 요금이 부과됩니다. 즉, 무료 기본 사용자는 고급 컴퓨팅 기능에 액세스할 수 있지만 고급 CCU에 대해서는 요금이 부과됩니다. + + +* **Original Data 또는 Data Plus용 EU 데이터센터**: 이 추가 기능은 사용 가능한 경우 데이터 지역으로 유럽 연합을 선택하면 데이터 옵션(Original Data 또는 Data Plus)에 적용됩니다. + +* **Extended Retention for Original Data or Data Plus \[원본 데이터 또는 데이터 플러스의 연장 보존]**: 이 추가 기능은 데이터가 보존되는 기본 기간을 초과한 경우 적용됩니다. 이는 로그뿐만 아니라 모든 데이터에 적용되며, 많은 양의 작은 쿼리를 실행해야 하거나 대량의 데이터에 대한 쿼리를 실행해야 하는 경우 좋은 옵션입니다. + +* **Live Archives \[라이브 아카이브]**: 로그 보관 기간을 최대 7년까지 연장합니다. 라이브 아카이브에는 고급 컴퓨팅도 필요합니다. + +* **New Relic Synthetics Checks**: 이 추가 기능은 귀하의 수표가 신세틱 모니터링 검사의 기본 수를 초과하는 경우 적용됩니다. + +* **Security RX**: 이 기능은 데이터 플러스에 포함되어 있지만, 데이터 플러스 없이 시큐리티 RX 기능을 사용하는 경우 추가 기능이 적용됩니다. \ No newline at end of file diff --git a/src/i18n/content/kr/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing.mdx b/src/i18n/content/kr/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing.mdx new file mode 100644 index 00000000000..4e466ace0f4 --- /dev/null +++ b/src/i18n/content/kr/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing.mdx @@ -0,0 +1,354 @@ +--- +title: '데이터: 청구 및 규칙' +tags: + - Accounts + - Accounts and billing + - New Relic pricing and billing +metaDescription: 'For New Relic pricing, an explanation of how data ingest is calculated for billing purposes.' +freshnessValidatedDate: '2024-10-23T00:00:00.000Z' +translationType: machine +--- + +New Relic 가격 책정의 경우 New Relic 조직에서 수집한 데이터가 청구 요소 중 하나입니다. + +## 비용에 대해 알아보기 [#costs] + +아직 New Relic 고객이 아니고 비용에 대해 궁금한 경우 먼저 [기본 가격 페이지를](https://newrelic.com/pricing)참조하십시오. 기존 고객인 경우 데이터 수집 청구에 대한 세부 정보를 계속 읽으십시오. + +## UI에서 데이터 수집 보기 [#ui] + +UI에서 사용량 및 청구 정보를 찾는 방법은 [청구 UI를](/docs/accounts/accounts-billing/general-account-settings/introduction-account-settings)참조하십시오. + +데이터 수집을 보고 관리하는 방법은 [수집 관리를](/docs/data-apis/manage-data/manage-data-coming-new-relic)참조하십시오. + +## 데이터 옵션: 데이터 플러스 및 원본 [#data-prices] + +조직의 수집된 데이터 GB당 가격은 조직의 데이터 옵션( **Data Plus** 또는 **Original Data** 옵션)에 따라 다릅니다. Data Plus 옵션은 최적화된 성능, 규모, 보안 및 거버넌스를 위한 고급 데이터 기능을 제공합니다. 뉴렐릭 조직은 한 번에 하나의 옵션만 가질 수 있습니다. + +다음은 두 옵션을 비교한 표입니다. 가격 및 한도는 월 단위이며 가격은 USD로 표시됩니다. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ 특징/능력 + + **Original Data** 옵션 + + **Data Plus** 옵션 + + 더 많은 기능 세부 정보 +
+ [에디션](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing/#editions) + + 모든 에디션 + + 스탠다드(Standard), 프로(Pro) 또는 엔터프라이즈(Enterprise) 필요 + + (기능이 에디션에만 해당되는 경우 아래에 설명되어 있습니다.) + +
+ 데이터 무료 한도 + + 100GB 수집됨 + + 100GB 수집됨 + +
+ 데이터 가격
(무료 한도를 초과) +
+ $0.40/GB 수집됨 + + $0.60/GB 수집됨 + +
+ 데이터 보존 무료 한도
([데이터 유형에 따라 다름](/docs/data-apis/manage-data/manage-data-retention)) +
+ 최소 8일의 기본값 + + 기본 기간보다 90일 추가 + +
+ 추가 30일 보존 기간당 가격
(무료 한도 초과) +
+ +$0.05/GB + + +$0.05/GB + +
+ [EU 데이터 센터](/docs/accounts/accounts-billing/account-setup/choose-your-data-center)에 데이터를 저장하기 위한 추가 가격
+
+ +$0.05/GB + + +$0.05/GB + + 데이터는 기본적으로 미국 데이터 센터에 저장됩니다. +
+ 최대 [쿼리 한도](/docs/query-your-data/nrql-new-relic-query-language/get-started/rate-limits-nrql-queries/#query-limits) + + 분당 최대 200억 개의 데이터 포인트 + + 분당 최대 60B 데이터 포인트 + +
+ 최대 [쿼리 기간](/docs/query-your-data/nrql-new-relic-query-language/get-started/rate-limits-nrql-queries/#query-duration) + + 1 분 + + 최대 10분 + +
+ 클라우드 공급자 선택 + + 단일 클라우드 공급자 + + Azure 또는 여러 클라우드 공급자 + + 원격 측정 스토리지를 엔지니어링 배포 모델 및 클라우드 기본 설정에 맞추려면 관측 가능성 워크로드에 대해 선호하는 클라우드 공급자를 선택하세요. +
+ [로그 난독화](/docs/logs/ui-data/obfuscation-ui/) + + 로그에서 알려진 신용 카드 및 주민등록번호 패턴을[자동으로](/docs/logs/get-started/new-relics-log-management-security-privacy/#log-obfuscation) 마스킹합니다. + + UI에서 직접 규칙을 만들고 추적하며 [마스크 또는 민감한 로그 데이터를 해시](/docs/logs/ui-data/obfuscation-ui/) 합니다. + +
+ [New Relic 취약점 관리](/docs/vulnerability-management/overview)
(전체 플랫폼 사용자만 해당) +
+ +$0.10/GB
(무료 한도 초과) +
+ 스탠다드(Standard), 프로(Pro), 엔터프라이즈(Enterprise) + + 소프트웨어 수명 주기의 모든 단계에서 취약점을 식별하고 위험을 해결합니다. +
+ [FedRAMP 보통](/docs/security/security-privacy/compliance/fedramp-compliant-endpoints) 및 [HIPAA](/docs/security/security-privacy/compliance/hipaa-readiness-new-relic) 자격 + + + + 기업 + + FedRAMP 및 HIPAA 요구 사항을 충족하는 데 도움이 되는 구성을 통해 보안 규정 준수를 달성하십시오. +
+ [스트리밍 데이터 내보내기](/docs/apis/nerdgraph/examples/nerdgraph-streaming-export) + + + + 스탠다드(Standard), 프로(Pro), 엔터프라이즈(Enterprise) + + 원격 분석 데이터를 선택한 AWS 또는 Azure 스토리지로 동시에 내보내는 규칙을 구성합니다. 클라우드 공급자에 대한 추가 수출 수수료가 적용됩니다. +
+ [과거 데이터 내보내기](/docs/apis/nerdgraph/examples/nerdgraph-historical-data-export) + + + + 스탠다드(Standard), 프로(Pro), 엔터프라이즈(Enterprise) + + 기록 분석 및 모델링, 장기 저장 및 다른 데이터 분석 플랫폼과의 통합을 위한 제한 시간 없이 더 큰 쿼리를 실행합니다. +
+ Azure Native New Relic Service + + + + 스탠다드, 프로, 엔터프라이즈
([몇 가지 제한 사항이 있음](#azure-native-data-plus)) +
+
+ +Data Plus와 기존 데이터 옵션을 나란히 비교하려면 [Data Plus 데이터 시트를](https://newrelic.com/resources/datasheets/data-plus) 확인하세요. + +데이터 플러스에 관심이 있으십니까? [데이터 플러스로 업그레이드를](#upgrade-data-plus)참조하십시오. + +### Azure Native New Relic Service 세부 정보 [#azure-native-data-plus] + +[Azure Native New Relic Service를](/docs/infrastructure/microsoft-azure-integrations/get-started/azure-native) 사용하면 Azure에서 직접 앱 및 인프라에 대한 원격 분석 데이터를 수집하고 저장할 수 있습니다. 이 기능은 Data Plus에 포함되어 있지만 다음과 같은 제한 사항이 있습니다. + +* 미국 데이터 센터 지역에서만 사용 가능 +* FedRAMP 보통/HIPAA 자격 없음 +* 이전 데이터 내보내기를 사용할 수 없음 + +## 데이터 플러스로 업그레이드 [#upgrade-data-plus] + +데이터 플러스(Data Plus)로 업그레이드하려면 데이터 관리 허브의 [**Data retention** UI](/docs/data-apis/manage-data/manage-data-retention/#adjust-retention) 로 이동하여 **Upgrade retention** 클릭하세요. + +* 참고: **Edit data retention** 버튼이 보일 수 있지만 이것은 **Upgrade retention** 버튼과 다릅니다. +* **Upgrade retention** 버튼을 보려면 [결제 권한이](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts/#admin-settings) 있어야 합니다. 요구 사항을 충족했지만 여전히 **Upgrade retention** 옵션이 표시되지 않으면 뉴렐릭 계정 담당자에게 문의하세요. + +## 청구 가능한 GB 수집량으로 간주되는 것은 무엇입니까? [#usage-calculation] + +[New Relic 요금제](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing)의 맥락에서 "수집된 데이터"는 다양한 데이터 트리밍 및 데이터 변환 규칙을 적용한 후 조직에서 New Relic에 저장한 데이터를 의미합니다. 즉, New Relic으로 보내는 raw data의 양이 아니라 실제로 저장되는 데이터의 크기입니다. + +일반적으로, 당사의 기능을 제공하기 위해 생성되는 데이터는 수집된 GB에 포함되지 않습니다. GB Ingested에 포함되지 않는 기능 및 기능 관련 데이터의 예는 다음과 같습니다. + +* [기본 알림 기능](/docs/alerts-applied-intelligence/new-relic-alerts/learn-alerts/alerts-concepts-workflow). 예를 들어, 이러한 기능을 생성하는 데 사용되는 이벤트인 `NrAiIncident` 은 수집된 GB에 포함되지 않습니다. +* 집계된 원시 데이터(예: [집계된 인프라 데이터](/docs/data-apis/manage-data/manage-data-retention/#infrastructure-data) 또는 [차원 메트릭 데이터](/data-apis/manage-data/manage-data-retention/#dimensional-metrics))로 생성된 데이터입니다. +* [골든 메트릭](/docs/apis/nerdgraph/examples/golden-metrics-entities-nerdgraph-api-tutorial) (골든 메트릭에 대한 자세한 내용은 [엔터티 정의](https://github.com/newrelic/entity-definitions)참조). +* 합성 모니터 확인. 합성 청구에 대한 자세한 내용은 [합성 한도 및 가격 책정을](/docs/synthetics/synthetic-monitoring/using-monitors/monitor-limits)참조하십시오. +* 사용량 및 청구 추적 데이터(예: `NrConsumption`). +* 계정 관리와 관련된 데이터(예: `NrIntegrationError`, `NrAuditEvent`). + +사용량을 이해하려면 [사용량 UI를](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing#usage-ui)참조하세요. + +## 기타 계산 세부 정보 [#calculation-details] + +* 가격 책정 모델의 맥락에서 GB는 10억 바이트로 정의됩니다. +* 월별 수집된 GB 수는 가장 가까운 정수로 반올림됩니다. 예를 들어, 조직에서 한 달에 100.9GB를 사용했다면 100GB로 계산됩니다. + +## 무료 버전 [#free-tier-limits] + +무료 버전의 GB Ingested에 대한 자세한 내용은 [무료 버전을](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing/#free) 참조하세요. + +## 더 알아보기 [#related-docs] + +* 수집된 GB를 관리하는 방법에 대한 자세한 내용은 [데이터 수집 관리를](/docs/data-apis/manage-data/manage-data-coming-new-relic) 참조하세요. +* 사용량을 쿼리하는 방법은 [쿼리 및 사용량 알림을](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts) 참조하세요. \ No newline at end of file diff --git a/src/i18n/content/kr/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts.mdx b/src/i18n/content/kr/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts.mdx index 3d97685636d..c84bba42391 100644 --- a/src/i18n/content/kr/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts.mdx +++ b/src/i18n/content/kr/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts.mdx @@ -21,10 +21,11 @@ translationType: machine ## 데이터 수집 사용 쿼리 [#data-queries] -[사용량 UI에는](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing#usage-ui) 시간 경과에 따른 데이터 수집이 표시됩니다. UI가 제공하는 것보다 더 자세한 내용이 필요한 경우 다양한 NRQL 쿼리를 사용할 수 있습니다. 아래 예에는 두 가지 데이터 유형이 포함되어 있습니다. +The [usage UI](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing#usage-ui) displays your data ingest over time. If you need more detail than the UI provides, you can use a variety of NRQL queries. The examples below include the following data types: * `NrConsumption`: 시간별 사용량 세부정보를 자세히 알아보려면 이 기능을 사용하세요. 청구서를 대신하는 데에는 도움이 되지 않습니다. -* `NrMTDConsumption`: 이를 사용하면 월간 집계 사용량에 대한 대략적인 수치를 확인할 수 있습니다. +* `NrMTDConsumption`: Use this to see an approximation of your monthly aggregated usage. +* `NrCustomerMTDConsumption`: Use this to see an approximation of a customer's monthly aggregated usage. @@ -60,7 +61,7 @@ translationType: machine - 이 쿼리는 현재 전체 플랫폼에서 수집된 데이터를 보여줍니다. 즉, 지금 요금을 청구받는다면 그 달에 얼마의 데이터 요금이 청구될 것인지를 보여줍니다. 사용료 정보는 매 시간 계산되며 생성하는 데 약 3시간이 소요됩니다. 값이 표시되지 않는 경우 "SINCE 4 hour ago"를 사용하여 4시간 전의 데이터를 쿼리하세요. + This query shows the current full platform ingested data. In other words, it shows how much you'd be billed for your data for that month if you were billed right now. Usage fee information is calculated hourly and takes approximately 3 hours to generate. If no values are displayed, please query data from 4 hours ago using "SINCE 4 hours ago." ```sql FROM NrMTDConsumption SELECT latest(GigabytesIngested) @@ -73,6 +74,72 @@ translationType: machine +## Compute usage queries [#compute-queries] + +The [usage UI](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing#usage-ui) displays your compute usage over time. If you need more detail than the UI provides, you can use a variety of NRQL queries. The examples below include the following data types: + +* `NrConsumption`: 시간별 사용량 세부정보를 자세히 알아보려면 이 기능을 사용하세요. 청구서를 대신하는 데에는 도움이 되지 않습니다. +* `NrMTDConsumption`: Use this to see an approximation of your monthly aggregated compute usage. +* `NrCustomerMTDConsumption`: Use this to see an approximation of a customer's monthly aggregated usage. + + + + This query totals your billable core compute usage, and displays a daily value for the past three months: + + ```sql + FROM NrConsumption SELECT sum(consumption) + WHERE metric = 'CoreCCU' + SINCE 3 months ago TIMESERIES 1 day + ``` + + + + This query totals your billable advanced compute usage, and displays a daily value for the past three months: + + ```sql + FROM NrConsumption SELECT sum(consumption) + WHERE metric = 'AdvancedCCU' + SINCE 3 months ago TIMESERIES 1 day + ``` + + + + This query totals your billable core compute usage, and displays a daily value for the past three months faceted by the capability: + + ```sql + FROM NrConsumption SELECT sum(consumption) + WHERE metric = 'CoreCCU' SINCE 3 months ago + FACET dimension_productCapability TIMESERIES 1 day + ``` + + + + This query totals your billable advanced compute usage, and displays a daily value for the past three months faceted by the capability: + + ```sql + FROM NrConsumption SELECT sum(consumption) + WHERE metric = 'AdvancedCCU' SINCE 3 months ago + FACET dimension_productCapability TIMESERIES 1 day + ``` + + + + This query shows the current full platform core compute usage. In other words, it shows how much you'd be billed for your data for that month if you were billed right now. Usage fee information is calculated hourly and takes approximately 3 hours to generate. If no values are displayed, please query data from 4 hours ago using "SINCE 4 hours ago." + + ```sql + FROM NrMTDConsumption select latest(consumption) where metric = 'CoreCCU' since 1 day ago + ``` + + + + This query shows the current full platform advanced compute usage. In other words, it shows how much you'd be billed for your data for that month if you were billed right now. Usage fee information is calculated hourly and takes approximately 3 hours to generate. If no values are displayed, please query data from 4 hours ago using "SINCE 4 hours ago." + + ```sql + FROM NrMTDConsumption select latest(consumption) where metric = 'AdvancedCCU' since 1 day ago + ``` + + + ## 데이터 수집 및 쿼리 제한 [#data-limits] 데이터 수집 제한 및 쿼리 제한에 대한 자세한 내용은 [New Relic 데이터 제한을](/docs/data-apis/manage-data/view-system-limits) 참조하세요. @@ -81,7 +148,7 @@ translationType: machine 사용자 수를 표시하려면 [사용 UI를](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing#usage-ui)참조하십시오. 그보다 더 자세한 정보가 필요한 경우 아래의 NRQL 쿼리 예제를 사용할 수 있습니다. 사용자 계산 방법에 대한 자세한 내용은 [청구 가능한 사용자 계산을](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/user-count-billing)참조하십시오. -대부분의 New Relic 조직에는 핵심 사용자를 추가할 수 있는 기능이 있습니다. 이 섹션에는 해당 조직에 적합한 쿼리가 포함되어 있습니다. [핵심 사용자 잠금 해제를 선택하지 않은 이전 조직에 있는 경우 핵심 사용자](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing#core-acceptance) 가 [없는 조직에 대한 쿼리를](#queries-non-core) 참조하십시오. +Most New Relic organizations have the ability to add core users. This section includes queries that will work for those organizations. If you're in an older organization that hasn't [opted in to unlock core users](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing#core-acceptance), see [Queries for organizations without core users](#queries-non-core). 다음은 사용자 쿼리에 대한 몇 가지 규칙입니다. @@ -336,7 +403,7 @@ SINCE 3 hours ago
- 이 쿼리는 사용량이 GB에 대한 고정된 월별 임계값을 초과할 때 경고를 생성합니다. + This query will create an alert when your usage exceeds a fixed monthly threshold for GBs: ```sql FROM NrMTDConsumption @@ -447,5 +514,5 @@ SINCE 3 hours ago 다음은 `bytecountestimate()` 작동 방식에 대한 몇 가지 기술적 세부정보입니다. * [수집에 포함되지 않지만](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing/#usage-calculation) `bytecountestimate()` 함수에 의해 반환되는 여러 유형의 데이터가 있습니다. 이는 이 함수가 실제로 사용량에 계산되는 것보다 **more** 데이터를 표시하는 경우가 있음을 의미합니다. 더 낮은 금액이 표시되는 경우는 거의 없지만, 표시되는 경우에는 약간만 낮아집니다. -* 엔터티에서 보고된 일부 원격 측정 데이터는 공통 속성(예: New Relic 계정에 대한 속성)을 공유합니다. 중복된 속성은 수집에 포함되지 않지만 `bytecountestimate()` 는) 이러한 속성을 포함합니다. 이로 인해 때때로 `bytecountestimate()` 쿼리와 실제 사용량 간에 큰 불일치가 발생할 수 있습니다. +* Some telemetry data reported from an entity shares common attributes (for example, attributes about your New Relic account). We don't count the duplicated attributes towards your ingest, but `bytecountestimate()` does count those attributes. This can sometimes result in a large discrepancy between a `bytecountestimate()` query and your actual usage. * , 는 [지표 타임슬라이스 데이터](/docs/data-apis/understand-data/new-relic-data-types/#timeslice-data) 로 알려진 데이터 유형을 보고합니다. 이 데이터는 다른 데이터 유형처럼 NRDB에 저장되지 않으므로 이 데이터에 `bytecountestimate()` 사용하려고 하면 혼란스러운 결과가 발생할 수 있습니다. 이 데이터를 조회할 때는 지표 이름이 아닌 특수 이름으로 패싯을 조회하는 것이 좋습니다. \ No newline at end of file diff --git a/src/i18n/content/kr/docs/alerts/admin/rules-limits-alerts.mdx b/src/i18n/content/kr/docs/alerts/admin/rules-limits-alerts.mdx index 0cd7d9162d6..6f115dd9400 100644 --- a/src/i18n/content/kr/docs/alerts/admin/rules-limits-alerts.mdx +++ b/src/i18n/content/kr/docs/alerts/admin/rules-limits-alerts.mdx @@ -345,6 +345,39 @@ translationType: machine * 그 외 : 5k + + + + + + Email addresses per destination + + + + 1 email address + + + + * Free accounts: 5 email addresses per destination + * Paid accounts: 150 email addresses per destination + + + + + + + + Email addresses per organization per 24 hours + + + + 해당 없음 + + + + 1000 unique email addresses (applies to all users) + + 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 02f578b4097..b5905a70a50 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 @@ -269,24 +269,24 @@ Node.js 에이전트는 [npm(Node Package Manager) 저장소](https://npmjs.org/ | --------------------------------- | ---------- | -------- | -------------------------------------- | | `@apollo/gateway` | 2.3.0 | 2.11.2 | `@newrelic/apollo-server-plugin@1.0.0` | | `@apollo/server` | 4.0.0 | 5.0.0 | `@newrelic/apollo-server-plugin@2.1.0` | -| `@aws-sdk/client-bedrock-runtime` | 3.474.0 | 3.886.0 | 11.13.0 | -| `@aws-sdk/client-dynamodb` | 3.0.0 | 3.886.0 | 8.7.1 | -| `@aws-sdk/client-sns` | 3.0.0 | 3.886.0 | 8.7.1 | -| `@aws-sdk/client-sqs` | 3.0.0 | 3.886.0 | 8.7.1 | -| `@aws-sdk/lib-dynamodb` | 3.377.0 | 3.886.0 | 8.7.1 | +| `@aws-sdk/client-bedrock-runtime` | 3.474.0 | 3.894.0 | 11.13.0 | +| `@aws-sdk/client-dynamodb` | 3.0.0 | 3.894.0 | 8.7.1 | +| `@aws-sdk/client-sns` | 3.0.0 | 3.894.0 | 8.7.1 | +| `@aws-sdk/client-sqs` | 3.0.0 | 3.894.0 | 8.7.1 | +| `@aws-sdk/lib-dynamodb` | 3.377.0 | 3.894.0 | 8.7.1 | | `@aws-sdk/smithy-client` | 3.47.0 | 3.374.0 | 8.7.1 | | `@azure/functions` | 4.7.0 | 4.8.0 | 12.18.0 | | `@elastic/elasticsearch` | 7.16.0 | 9.1.1 | 11.9.0 | -| `@google/genai` | 1.1.0 | 1.19.0 | 12.21.0 | -| `@grpc/grpc-js` | 1.4.0 | 1.13.4 | 8.17.0 | +| `@google/genai` | 1.1.0 | 1.20.0 | 12.21.0 | +| `@grpc/grpc-js` | 1.4.0 | 1.14.0 | 8.17.0 | | `@hapi/hapi` | 20.1.2 | 21.4.3 | 9.0.0 | | `@koa/router` | 12.0.1 | 14.0.0 | 3.2.0 | -| `@langchain/core` | 0.1.17 | 0.3.75 | 11.13.0 | -| `@modelcontextprotocol/sdk` | 1.13.0 | 1.17.5 | 13.2.0 | +| `@langchain/core` | 0.1.17 | 0.3.77 | 11.13.0 | +| `@modelcontextprotocol/sdk` | 1.13.0 | 1.18.1 | 13.2.0 | | `@nestjs/cli` | 9.0.0 | 11.0.10 | 10.1.0 | | `@opensearch-project/opensearch` | 2.1.0 | 3.5.1 | 12.10.0 | -| `@prisma/client` | 5.0.0 | 6.16.0 | 11.0.0 | -| `@smithy/smithy-client` | 2.0.0 | 4.6.1 | 11.0.0 | +| `@prisma/client` | 5.0.0 | 6.16.2 | 11.0.0 | +| `@smithy/smithy-client` | 2.0.0 | 4.6.3 | 11.0.0 | | `amqplib` | 0.5.0 | 0.10.9 | 2.0.0 | | `aws-sdk` | 2.2.48 | 2.1692.0 | 6.2.0 | | `bluebird` | 2.0.0 | 3.7.2 | 1.27.0 | @@ -294,7 +294,7 @@ Node.js 에이전트는 [npm(Node Package Manager) 저장소](https://npmjs.org/ | `cassandra-driver` | 3.4.0 | 4.8.0 | 1.7.1 | | `connect` | 3.0.0 | 3.7.0 | 2.6.0 | | `express` | 4.15.0 | 5.1.0 | 2.6.0 | -| `fastify` | 3.0.0 | 5.6.0 | 8.5.0 | +| `fastify` | 3.0.0 | 5.6.1 | 8.5.0 | | `generic-pool` | 3.0.0 | 3.9.0 | 0.9.0 | | `ioredis` | 4.0.0 | 5.7.0 | 1.26.2 | | `kafkajs` | 2.0.0 | 2.2.4 | 11.19.0 | @@ -302,14 +302,14 @@ Node.js 에이전트는 [npm(Node Package Manager) 저장소](https://npmjs.org/ | `koa-route` | 3.0.0 | 4.0.1 | 3.2.0 | | `koa-router` | 12.0.1 | 14.0.0 | 3.2.0 | | `memcached` | 2.2.0 | 2.2.2 | 1.26.2 | -| `mongodb` | 4.1.4 | 6.19.0 | 1.32.0 | +| `mongodb` | 4.1.4 | 6.20.0 | 1.32.0 | | `mysql` | 2.16.0 | 2.18.1 | 1.32.0 | -| `mysql2` | 2.0.0 | 3.14.5 | 1.32.0 | -| `next` | 13.4.19 | 15.5.2 | 12.0.0 | -| `openai` | 4.0.0 | 5.20.1 | 11.13.0 | +| `mysql2` | 2.0.0 | 3.15.0 | 1.32.0 | +| `next` | 13.4.19 | 15.5.3 | 12.0.0 | +| `openai` | 4.0.0 | 5.22.0 | 11.13.0 | | `pg` | 8.2.0 | 8.16.3 | 9.0.0 | | `pg-native` | 3.0.0 | 3.5.2 | 9.0.0 | -| `pino` | 8.0.0 | 9.9.5 | 8.11.0 | +| `pino` | 8.0.0 | 9.11.0 | 8.11.0 | | `q` | 1.3.0 | 1.5.1 | 1.26.2 | | `redis` | 3.1.0 | 5.8.2 | 1.31.0 | | `restify` | 11.0.0 | 11.1.0 | 2.6.0 | diff --git a/src/i18n/content/kr/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation.mdx b/src/i18n/content/kr/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation.mdx new file mode 100644 index 00000000000..301e808de43 --- /dev/null +++ b/src/i18n/content/kr/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation.mdx @@ -0,0 +1,70 @@ +--- +title: CloudFormation 및 CloudWatch Metric Streams를 통해 통합 +tags: + - Integration via CloudFormation + - AWS metric integration + - Amazon integrations + - AWS integrations + - Integration with CloudWatch Metric Streams via CloudFormation +metaDescription: Integrate New Relic with AWS services using CloudFormation templates to automate the setup of CloudWatch Metric Streams for metrics ingestion. +freshnessValidatedDate: never +translationType: machine +--- + +AWS 계정을 뉴렐릭과 원활하게 통합하려면 이 통합 프로세스가 가장 권장됩니다. CloudWatch Metric Streams에서 지원하지 않는 서비스에도 API 폴링을 활용할 수 있습니다. + +## 전제 조건 [#prerequisites] + +AWS 계정을 뉴렐릭과 통합하기 전에 다음 필수 조건을 충족하는지 확인하세요. + +* **뉴렐릭 [클러스터 키](https://one.newrelic.com/api-keys)**: AWS 서비스를 뉴베리 계정에 연결하려면 클러스터 키가 필요합니다. +* **[새로운 리소스](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html)** 및 IAM 역할을 구현하고 배포하기 위한 **[권한](https://docs.aws.amazon.com/ARG/latest/userguide/gettingstarted-prereqs-permissions.html)** AWS :AWS 계정에 이 권한이 필요합니다. +* 클라우드 통합 **[권한](/docs/accounts/accounts-billing/new-relic-one-user-management/user-permissions/#infrastructure)** : 뉴렐릭 계정에 대해 다음 권한이 필요합니다. + +## 통합 단계 [#integration-steps] + +CloudFormation 및 사용하여 계정을 뉴렐릭과 통합하려면 AWS CloudWatch Metric Streams 다음 단계를 따르세요. + +1. [**Infrastructure > AWS**](https://one.newrelic.com/infra/infrastructure/cloud-aws) 로 이동합니다. + +2. 올바른 계정을 선택하세요. + +3. **Set up integration** 을(를) 클릭합니다. + +4. 각 화면의 지시를 따르고, 귀하에게 해당하는 필드를 작성하세요. 이 통합을 위해 주어진 화면에서 다음 옵션을 선택하세요. + + 1. **Choose Data type(s)**: Metrics + 2. **Choose a setup method**: Automate AWS with CloudFormation (Recommended) + 3. **Choose a metrics integration type**: CloudWatch Metric Stream (Recommended) + +5. CloudWatch Metric Streams에서 지원되지 않는 서비스를 사용하는 경우 **Choose a metrics integration type** 페이지에서 API 폴링을 위한 세 번째 단계에서 **Yes** 선택하고 계속 진행합니다. + + AWS Integration with CWMS and API Polling + +
+ 지원되지 않는 서비스에 대해 선택된 API 폴링을 통해 AWS 서비스와 CWMS가 통합되었습니다. +
+ + **Enable API Polling (optional)** 페이지에 안내된 대로 필요한 설정을 수행하고 계속 진행하세요. + +6. Auto-discovery AWS 와 관련된 관계를 지도에서 자동으로 감지하고 시각화하며, 다른 몇 가지 유연성을 활용합니다. 자세한 내용은 [AWS 자동 검색을](/docs/infrastructure/amazon-integrations/connect/set-up-auto-discovery-of-aws-entities/) 참조하세요. 이 기능을 원하시면 **Enable Auto Discovery (optional)** 페이지에서 해당 기능을 활성화하고 계속 진행하세요. + +7. **Launch your CloudFormation in AWS** 클릭하세요. CloudFormation 템플릿은 AWS 콘솔에서 구성된 파라미터와 함께 열립니다. 파라미터는 뉴렐릭에서 선택한 내용에 따라 달라지므로, 변경하려는 경우가 아니면 추가 편집이 필요하지 않습니다. + +8. AWS 콘솔에 라이선스 키를 붙여넣습니다. + +9. Cloudformation 그리드를 구현하거나 배포하려면 AWS 콘솔에서 **Create stack** 선택합니다. 택시 리소스를 만드는 데는 몇 분이 걸릴 수 있으며, 택시 전달을 구성하는 방법에 따라 여러 택시가 생성될 수 있습니다. 그리드 생성에 실패할 경우 [문제 해결, 해결 절차를](https://docs.newrelic.com/docs/logs/troubleshooting/aws-log-integration-issues/stack-creation-fails/) 참조하세요. + +10. 그리드 생성이 성공적으로 완료되면 뉴렐릭 플랫폼으로 전환하고 뉴렐릭에서 AWS 데이터가 표시될 때까지 통합 안내를 계속 진행하세요. + +## 관련 주제 [#related-topics] + + + + 여러 AWS 계정에서 데이터를 수집하는 방법을 알아보세요. + + + + CloudWatch Metric Streams의 지표를 탐색하고 사용하세요. + + \ No newline at end of file diff --git a/src/i18n/content/kr/docs/infrastructure/other-infrastructure-integrations/stripe-integration.mdx b/src/i18n/content/kr/docs/infrastructure/other-infrastructure-integrations/stripe-integration.mdx index d7c7d36c560..e2ba3f7a1ef 100644 --- a/src/i18n/content/kr/docs/infrastructure/other-infrastructure-integrations/stripe-integration.mdx +++ b/src/i18n/content/kr/docs/infrastructure/other-infrastructure-integrations/stripe-integration.mdx @@ -102,7 +102,7 @@ WHERE metricName = 'stripe_metrics' ### Stripe 모니터링 대시보드 설치 [#add-dashboard] -애플리케이션 지표를 모니터링하기 위해 사전 구축된 Stripe 대시보드를 설정하려면 [Stripe 대시보드 설치](https://onenr.io/0ZQWYYE1rRW) 로 이동하여 지침을 따르십시오. 설치되면 대시보드에 측정항목이 표시됩니다. +사전 제작된 Stripe 대시보드를 설정하여 귀하의 전형적인 피규어를 모니터링하려면 [Stripe 대시보드 설치](https://onenr.io/0BQrXaNgnRZ) 로 이동하여 지침을 따르십시오. 대시보드를 설치하면 대시보드에 지표가 표시됩니다. 대시보드에 대한 도움이 필요하면 다음을 참조하세요. diff --git a/src/i18n/content/kr/docs/new-relic-solutions/solve-common-issues/find-help-get-support.mdx b/src/i18n/content/kr/docs/new-relic-solutions/solve-common-issues/find-help-get-support.mdx index 8bf049ee2c4..f244fa55e16 100644 --- a/src/i18n/content/kr/docs/new-relic-solutions/solve-common-issues/find-help-get-support.mdx +++ b/src/i18n/content/kr/docs/new-relic-solutions/solve-common-issues/find-help-get-support.mdx @@ -29,9 +29,9 @@ New Relic은 온라인 도움말, 문제 해결 도구, 자세한 절차 및 문 In-product support -## 무료 지원 포럼인 Explorers Hub에 문의하세요. [#nr-forum] +## 무료 지원 포럼에서 질문하세요 [#nr-forum] -[New Relic의 Explorers Hub는](https://discuss.newrelic.com/) 모든 사용자에게 무료로 제공되는 포럼입니다. New Relic 사용자와 직원은 매일 대화에 참여하여 문제를 해결하고 해결 방법을 찾고 새로운 기능에 대해 논의합니다. +[뉴렐릭의 지원 포럼은](https://discuss.newrelic.com/) 모든 사용자에게 무료로 제공되는 포럼입니다. 뉴렐릭 사용자와 직원은 매일 대화에 참여하여 문제를 해결하고, 해결 방법을 찾고, 새로운 기능에 대해 논의합니다. ## 새 유물 진단 도구 실행 [#diagnostics] diff --git a/src/i18n/content/kr/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx b/src/i18n/content/kr/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx index c3d14bbbed2..18c890cfbf2 100644 --- a/src/i18n/content/kr/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx +++ b/src/i18n/content/kr/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx @@ -346,15 +346,24 @@ FROM PageAction SELECT keyset() SINCE 1 day ago - `NRQL/ENUM`유형의 변수를 생성할 때 표시 옵션 섹션에서 다중 값 옵션을 활성화할 수 있습니다. + You can enable the multi-value option to allow users to select multiple values from a dropdown instead of just one. This is useful when you want to filter data across multiple criteria simultaneously. - 다음은 `{{MultiValue}}` 라는 변수를 생성하고 고유한 모든 eventId의 목록을 반환하는 쿼리의 예입니다. + Multi-value is available for Query and List variable types. Text field variables don't support the multi-value option. + + To enable multi-value: + + 1. When creating a Query or List template variable, select the **Multi-value** option. + 2. In your widget queries, use the `IN` operator instead of `=` to handle multiple selected values. + + /* You can enable the multi-value option from the display options section when creating a variable of type `NRQL/ENUM`. */ + + Here's an example where you'd name your variable `{{MultiValue}}` and use this query to populate its values: ```sql SELECT uniques(eventId) FROM AjaxRequest ``` - Multi-value template variable example + /* <img width="30%;" title="Multi-value template variable example" alt="Multi-value template variable example" src="/images/dashboards_screenshot-crop_add-multivalue.webp" /> */ 그런 다음 다음 쿼리를 사용하여 위젯을 만듭니다. @@ -362,22 +371,36 @@ FROM PageAction SELECT keyset() SINCE 1 day ago SELECT count(*) FROM AjaxRequest WHERE eventId IN ({{MultiValue}}) ``` - Creating a widget + /* <img width="80%;" title="Creating a widget" alt="Creating a widget" src="/images/dashboards_screenshot-full_multivalue-add-widget.webp" /> */ - 한 번에 하나의 템플릿 변수만 정의할 수 있지만 단일 위젯에서 둘 이상의 템플릿 변수를 사용할 수 있습니다. + While you can only define one template variable at a time, you can reference multiple variables within the same widget. + + For this example, you need to have the two variables set up: + + 1. `countryCode` variable: Use the query shown earlier in this document: + + ```sql + SELECT uniques(countryCode) FROM PageAction SINCE 2 days ago + ``` + + 2. `city` variable with a similar query: + + ```sql + SELECT uniques(city) FROM PageView SINCE 1 week ago + ``` - 다음은 두 개의 템플릿 변수를 사용하는 쿼리의 예입니다. 이는 `countryCode` 및 `city` 템플릿 변수가 이미 생성되었으며 단일 값을 가지고 있다고 가정합니다. + Here's an example using the above template variables with single values to create the widget: ```sql SELECT countryCode, city FROM PageAction WHERE countryCode = {{countryCode}} AND city = {{city}} ``` - Creating a widget using multiple variables + /* <img title="Creating a widget using multiple variables" alt="Creating a widget using multiple variables" src="/images/dashboards_screenshot-crop_add-widget-multiple-variable.webp" /> */ - 변수에 여러 값이 있는 경우(예: `city` 변수에 대한 `Chicago`, `New York`, `Paris` , `IN` 사용해야 합니다. + If your variables support multiple values (such as `Chicago`, `New York`, `Paris` for your `city` variable), you need to use `IN`: ```sql SELECT countryCode, city FROM PageAction @@ -398,7 +421,7 @@ FROM PageAction SELECT keyset() SINCE 1 day ago SELECT uniques(aparse(platformVersion, 'release-*')) FROM PageView ``` - Creating the release version variable + /* <img width="40%;" title="Creating the release version variable" alt="Creating the release version variable" src="/images/dashboards_screenshot-crop_add-var-release-version.webp" /> */ 그런 다음 다음 쿼리를 사용하여 위젯을 만듭니다. @@ -407,7 +430,7 @@ FROM PageAction SELECT keyset() SINCE 1 day ago WHERE aparse(platformVersion, 'release-*') IN ({{releaseversion}}) FACET platformVersion ``` - Creating the widget + /* <img title="Creating the widget" alt="Creating the widget" src="/images/dashboards_screenshot-crop_add-widget-aparse.webp" /> */ 또는 원하는 경우 [`capture`](/docs/query-your-data/nrql-new-relic-query-language/get-started/nrql-syntax-clauses-functions/#func-capture) 명령을 사용할 수 있습니다. @@ -416,15 +439,20 @@ FROM PageAction SELECT keyset() SINCE 1 day ago WHERE capture(platformVersion, r'release-(?P\d+)') IN ({{releaseversion}}) FACET platformVersion ``` - Creating the widget + /* <img title="Creating the widget" alt="Creating the widget" src="/images/dashboards_screenshot-crop_add-widget-capture.webp" /> */ `LIKE` 및 `RLIKE` 템플릿 변수로 사용하여 대시보드에서 데이터를 필터링할 수 있습니다. 이 기능을 사용하려면 템플릿 변수를 생성할 때 추가하는 값은 값의 시작과 끝에 `%` 와일드카드 기호를 사용해야 합니다. - 여기에 예가 있습니다. 다음과 같이 문자열 변수를 정의합니다. + Here's an example. You define a string template variable with the following values: + + * **Name to use in queries:** line\_filter + * **유형:** `Text field` + * **Default value:** %@%.com + * **Output format:** `String` - Add `LIKE` as template variable + /* <img width="40%;" title="Add `LIKE` as template variable" alt="Add `LIKE` as template variable" src="/images/dashboards_screenshot-crop_add-var-like-filter.webp" /> */ 그런 다음 위젯 차트를 만들고 다음과 같이 변수를 사용할 수 있습니다. @@ -432,7 +460,7 @@ FROM PageAction SELECT keyset() SINCE 1 day ago FROM NrdbQuery SELECT user WHERE user LIKE {{like_filter}} ``` - Add `LIKE` as template variable + /* <img title="Add `LIKE` as template variable" alt="Add `LIKE` as template variable" src="/images/dashboards_screenshot-crop_add-widget-like-filter.webp" /> */ 또는 다음과 같이: @@ -450,13 +478,13 @@ FROM PageAction SELECT keyset() SINCE 1 day ago > 문자열 출력 형식으로 NRQL 유형의 변수를 생성하고 `FACET` 절 뒤에 사용하여 다른 값으로 그룹화할 수 있습니다. - 예를 들어 다음과 같은 `{{userAgentName}}` 라는 변수를 만들 수 있습니다. + For example, you might create a template variable named `{{userAgentName}}` that would look like: ```sql SELECT uniques(userAgentName) FROM PageAction ``` - Creating the variable + /* <img width="30%;" title="Creating the variable" alt="Creating the variable" src="/images/dashboards_screenshot-crop_add-var-facet.webp" /> */ 그런 다음 다음 쿼리를 사용하여 위젯을 만듭니다. @@ -465,15 +493,20 @@ FROM PageAction SELECT keyset() SINCE 1 day ago WHERE userAgentName={{userAgentName}} FACET userAgentName ``` - Creating widget using facet + /* <img title="Creating widget using facet" alt="Creating widget using facet" src="/images/dashboards_screenshot-crop_add-widget-facet.webp" /> */ `identifier` 출력 형식으로 변수를 만들고 `FACET` 절 뒤에 사용하여 다른 값으로 그룹화할 수 있습니다. - 예를 들어 `countryCode` 및 `city` 의 두 가지 가능한 값을 사용하여 목록 유형의 `{{location}}` 변수를 생성할 수 있습니다. 출력 형식을 `identifier` 로 설정합니다. + For example, you might create a `{{location}}` variable: - Adding the variable for dynamic grouping + * **Name to use in queries:** location + * **유형:** `List` + * **Values separated by commas:** `countryCode` and `city` + * **Output format:** `Identifier` + + /* <img width="40%;" title="Adding the variable for dynamic grouping" alt="Adding the variable for dynamic grouping" src="/images/dashboards_screenshot-crop_add-var-dynamic-grouping.webp" /> */ 그런 다음 다음 쿼리를 사용하여 위젯을 만듭니다. @@ -481,15 +514,20 @@ FROM PageAction SELECT keyset() SINCE 1 day ago SELECT count(*) FROM PageAction FACET {{location}} ``` - Adding the widget for dynamic grouping + /* <img title="Adding the widget for dynamic grouping" alt="Adding the widget for dynamic grouping" src="/images/dashboards_screenshot-crop_add-widget-dynamic-grouping.webp" /> */ 출력 형식이 `number` 인 변수를 만들고 백분위수 함수 내에서 사용할 수 있습니다. - 예를 들어 `55` 및 `90` 의 두 가지 가능한 값을 사용하여 `list` 유형의 `{{percentile}}` 변수를 생성할 수 있습니다. 출력 형식을 `number` 로 설정하려고 합니다. + For example, you could create a `{{percentile}}` variable: + + * **Name to use in queries:** percentile + * **유형:** `List` + * **Values separated by commas:** `55` and `90` + * **Output format:** `Number` - Adding the variable for dynamically change the percentile + /* <img width="40%;" title="Adding the variable for dynamically change the percentile" alt="Adding the variable for dynamically change the percentile" src="/images/dashboards_screenshot-crop_add-var-dynamic-percentile.webp" /> */ 그런 다음 다음 쿼리를 사용하여 위젯을 만듭니다. @@ -497,7 +535,7 @@ FROM PageAction SELECT keyset() SINCE 1 day ago SELECT percentile(duration, {{percentile}}) FROM PageAction ``` - Adding the widget for dynamically change the percentile + /* <img title="Adding the widget for dynamically change the percentile" alt="Adding the widget for dynamically change the percentile" src="/images/dashboards_screenshot-crop_add-widget-dynamic-percentile.webp" /> */ @@ -508,7 +546,7 @@ FROM PageAction SELECT keyset() SINCE 1 day ago WHERE countryCode IN ({{countryCode}}) ``` - Use variables to filter + /* <img title="Use variables to filter" alt="Use variables to filter" src="/images/dashboards_screenshot-crop_variables-to-filter.webp" /> */ @@ -528,7 +566,7 @@ FROM PageAction SELECT keyset() SINCE 1 day ago 그러면 지난 30분 동안의 값이 나옵니다. 타임 피커 값을 **Default** 으로 설정하고 쿼리에 `SINCE` 절이 있는 경우 최신 값이 쿼리를 실행하는 데 사용됩니다. - A screenshot showing the variable form + /* <img title="Example form" alt="A screenshot showing the variable form" src="/images/dashboards_screenshot-crop_example-form.webp" /> */ + 최신 에이전트 버전이 출시되면 즉시 업데이트하는 것이 좋습니다. 조직에서 최신 버전으로 업데이트하지 못하도록 하는 관행을 확립한 경우, 에이전트가 최대 90일 된 버전으로 정기적으로 업데이트되도록 하세요. [에이전트에게 최신 정보를 제공하는 방법](https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) 에 대해 자세히 알아보세요. + + +## 3.41.0 + +### 추가됨 + +* 분산 트레이스에 대한 인바운드 요청의 샘플링 동작을 제어하기 위한 `DistributedTracer.Sampler` 구성 옵션이 추가되었습니다. + + * 샘플러를 구성하려면 원격 부모가 플래그를 지정한 내용에 따라 샘플링 동작을 처리하는 `ConfigRemoteParentSampled(flag RemoteParentSamplingConfig)` 및 `ConfigRemoteParentNotSampled(flag RemoteParentSamplingConfig)` 추가했습니다. + * 추가된 플래그는 `"always_on", "always_off", and "default"` 이며 다음을 사용하여 호출할 수 있습니다. `RemoteParentSamplingConfig` + * `Example: newrelic.ConfigRemoteParentSampled(newrelic.AlwaysOff)` + +* OOM 모니터링 테스트 추가 + +* 보안 에이전트 테스트 범위 확대 + +### 결정된 + +* 보고된 보안 또는 기타 지원 문제로 인해 타사 라이브러리 버전이 업데이트되었습니다. + + * `github.com/gofiber/fiber/v2` `nrfiber` 통합에서 2.52.7에서 2.52.9로 + * `golang.org/x/net` `nrconnect` 통합에서 0.25.0에서 0.38.0으로 + +### 지지 성명 + +우리는 최신 버전의 Go 언어를 사용합니다. 최소한 Go 팀에서 지원하는 것보다 오래된 Go 버전은 사용해서는 안 됩니다. 지원되는 Go 에이전트 버전과 타사 구성 요소에 대한 자세한 내용은 [Go 에이전트 EOL 정책을](https://docs.newrelic.com/docs/apm/agents/go-agent/get-started/go-agent-eol-policy/) 참조하세요. \ No newline at end of file diff --git a/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-8-01-2025.mdx b/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-8-01-2025.mdx new file mode 100644 index 00000000000..e6aff2f120f --- /dev/null +++ b/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-8-01-2025.mdx @@ -0,0 +1,99 @@ +--- +subject: Docs +releaseDate: '2025-08-01' +version: 'July 25 - August 01, 2025' +translationType: machine +--- + +### 새로운 문서 + +* 컴퓨트 소비 단위(CCU) 사용량에 대한 모니터링 및 공지 메커니즘을 제공하기 위해 [컴퓨트 예산 문서를](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/compute-budgets/overview) 추가했습니다. + +### 주요 변경 사항 + +* Node.js 에이전트에 대한 [호환성 및 요구 사항이](/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent) 업데이트되었습니다. + +* PHP 에이전트용 [Arcin Linux의 호환성 및 요구 사항이](/docs/apm/agents/php-agent/getting-started/php-agent-compatibility-requirements) 업데이트되었습니다. + +* [파이프라인](/docs/new-relic-control/pipeline-control/modify-agent-configuration) 위험에 대한 에이전트별 요구 사항을 업데이트했습니다. + +* [지속 저항](/docs/apm/agents/java-agent/configuration/java-agent-configuration-config-file#jfr-harvest-interval) 에 대한 설정 요구 사항과 관련된 JFR을 업데이트했습니다. + +* 뉴렐릭 가격 및 청구에 대한 가격 및 청구 정보가 업데이트되었습니다. + + * [데이터: 청구 및 규칙](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing) + * [사용량 관련 쿼리 및 알림](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts) + * [뉴렐릭 이용 계획](/docs/licenses/license-information/usage-plans/new-relic-usage-plan) + +### 사소한 변경 사항 + +* .NET 에이전트 [호환성 및 요구 사항 문서에서 SQL 에이전트를 캡처하기 위해 .NET 에이전트](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements) 의 언어를 명확하게 했습니다. +* [작업 데이터베이스 모니터링 통합](/docs/infrastructure/host-integrations/host-integrations-list/oracle-database-monitoring-integration) 의 언어가 개선되었습니다. + +### 릴리즈 정보 + +* 새로운 소식 게시물을 확인하세요. + + * [컴퓨터 예산이 이제 일반적으로 이용 가능합니다](/whats-new/2025/07/whats-new-7-30-compute-budgets). + * [사용자 경험 강화: 핵심 웹 바이탈 최적화를 위해 세션 리플레이 활용](/whats-new/2025/07/whats-new-7-31-augmenting-user-experiences-browser). + +* 최신 릴리스에 대한 최신 정보를 받아보세요. + + * [안드로이드 에이전트 v7.6.8](/docs/release-notes/mobile-release-notes/android-release-notes/android-768): + + * Unity 오류에 대한 스택 추적이 올바르게 표시되지 않는 문제를 해결했습니다. + * 앱이 처음 실행된 후 포그라운드로 돌아왔을 때 요약 지표가 기록되지 않는 문제를 해결했습니다. + * 로그 항목에 잘못된 JSON이 포함되어 오류가 발생할 수 있는 문제를 해결했습니다. + + * [진단 CLI(nrdiag) v3.4.0](/docs/release-notes/diagnostics-release-notes/diagnostics-cli-release-notes/diagnostics-cli-341): + * 에이전트 제어 설치에서 생성된 로그를 수집하기 위해 `K8s/AgentControl/agent-control-install-job-logs` 을 추가했습니다. + + * [작업 관리자 v451](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-451): + + * SJM의 보안 문제를 해결하기 위해 `common-lang3` ยู่ 및 Ubuntu와 관련된 버그를 수정했습니다. + * 내부 서비스 아키텍처의 마이그레이션과 관련된 프로세서 대기열 마이그레이션 변경 사항을 구현했습니다. + * SJM 로그에서 문제 해결, 해결에 대한 더 나은 컨텍스트를 제공하기 위해 전체 예외 세부 정보를 포함하도록 문제를 수정했습니다. + + * [Android v5.30.1용 모바일 앱](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5301): + * 로그인 경험이 향상되었습니다. + + * [iOS v7.5.8용 모바일 앱](/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-758): + + * Xcode 16.4를 사용하여 에이전트를 빌드했습니다. + * 세션 시작 시 분산 추적에 필요한 모든 계정 정보가 포함되지 않는 문제를 해결했습니다. + * 에이전트 시작 시 충돌이 발생할 수 있는 문제를 해결했습니다. + + * [노드 API 런타임](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.122): + * Node API 런타임에서 보안 교육을 처리하기 위해 양식 데이터 잘라내 및 기본 Ubuntu 잘라내를 수정했습니다. + + * [노드 브라우저 런타임](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.39): + * Node 브라우저 런타임의 보안 쿠키를 해결하기 위해 form-data 쿠키 및 기본 Ubuntu 괄호를 수정했습니다. + + * [Ping 런타임](/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.53.0): + * Ping 런타임의 보안 문제를 해결하기 위해 `common-lang3` ย 및 Ubuntu와 관련된 고정된 버그를 수정했습니다. + + * [접착제 에이전트 v10.15.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-101500): + + * [`oracledb`](https://pypi.org/project/oracledb/)에 대한 지원이 추가되었습니다. + * `MessageBroker` 측정, 과학적에서 serialize 메서드가 `MessageTransaction` 에서 `destination_name` 속성을 찾고 있었지만 해당 속성이 존재하지 않았던 버그를 수정했습니다. + * AWS와 K8s를 함께 실행할 때 발생하는 AWS 활용 메타데이터 문제를 해결했습니다. + + * [루비 에이전트 v9.20.0](/docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-20-0): + + * AWS ECS Fargate 환경에서 실행할 때 도커 ID를 기록하는 지원이 추가되었습니다. + * 버전 비교를 단순화하기 위해 새로운 도우미 메서드를 추가했습니다. + * 기간이 구성된 청년 값을 초과하는 경우 데이터 스토어 범위에 `code.stacktrace` 속성을 추가했습니다. + * `Brewfile` 소스 링크가 수정되었습니다. + * `HTTPX 1.5.0` 사용하여 응답을 저장할 때 발생하는 오류를 수정했습니다. + * 에이전트가 설정 소스를 읽을 때 디버그 수준에서 에이전트에 의한 정보 로그를 개선했습니다. + + * [유니티 에이전트 v1.4.8](/docs/release-notes/mobile-release-notes/unity-release-notes/unity-agent-148): + + * 네이티브 안드로이드 에이전트를 v7.6.7로 업데이트했습니다. + * 네이티브 iOS 에이전트를 v7.5.6으로 업데이트했습니다. + + * [유니티 에이전트 v1.4.9](/docs/release-notes/mobile-release-notes/unity-release-notes/unity-agent-149): + + * 네이티브 안드로이드 에이전트를 v7.6.8로 업데이트했습니다. + * 네이티브 iOS 에이전트를 v7.5.8로 업데이트했습니다. + * 네임스페이스가 사용될 때 발생하는 Unity 예외 스택 추적 문제가 해결되었습니다. \ No newline at end of file diff --git a/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx b/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx new file mode 100644 index 00000000000..8223f140d0d --- /dev/null +++ b/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx @@ -0,0 +1,60 @@ +--- +subject: Docs +releaseDate: '2025-08-08' +version: 'August 01 - August 07, 2025' +translationType: machine +--- + +### 새로운 문서 + +* [NerdGraph 튜토리얼을 추가했습니다: Teams에 대한 사용자 지정 역할 만들기는](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/compute-budgets/overview) NerdGraph API 사용하여 Teams에 대한 사용자 지정 역할을 만들고 관리하는 방법을 안내합니다. + +### 사소한 변경 사항 + +* [조건별 알림 이벤트를 분당 1,000개로](/docs/alerts/admin/rules-limits-alerts) 변경했습니다. +* 최신 검증된 [.Net 에이전트 호환 버전과 요구 사항을](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements) 업데이트했습니다. +* [VMware Tanzu](/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-service-broker-integration) 의 서비스 브로커에 대한 버전 및 버전 지원 정보가 업데이트되었습니다. +* [VMware Tanzu](/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-nginx-buildpack-integration) 용 뉴렐릭 NGINX 통합 빌드팩에 대한 버전 지원 정보를 업데이트했습니다. +* [VMware Tanzu](/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-firehose-nozzle-integration/#product-snapshot) 용 뉴렐릭 Nozzle에 대한 버전 및 버전 지원 정보를 업데이트했습니다. + +### 릴리즈 정보 + +* 새로운 소식 게시물을 확인하세요. + + * [의 인박스(errors inbox)가 이제 워크로드 내에 통합되었습니다](/whats-new/2025/08/whats-new-08-06-workloads-errors-inbox). + +* 최신 릴리스에 대한 최신 정보를 받아보세요. + + * [작업 관리자 v452](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-452): + * 대기열 메시지 처리 시 예외 처리를 위한 내부 개선 사항이 추가되었습니다. + + * [Kubernetes 통합 v3.43.3](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-43-3): + * 뉴렐릭 Kubernetes 모니터링 솔루션을 구현하고 배포하기 위해 Helm 차트를 추가했습니다. + + * [파이프라인 컨트롤 게이트웨이 v1.1.0](/docs/release-notes/pipeline-control-gateway-release-notes/pipeline-control-gateway-25-08-05): + + * 삭제 규칙을 사용하여 `SqlTrace` 및 `TransactionTrace` 이벤트에서 데이터와 속성을 선택적으로 삭제하는 새로운 기능을 구현했습니다. + + * IPv6 영역 ID와 관련된 HTTP 프록시 우회 및 사이트 간 스프레드시트 문제를 포함하여 `golang.org/x/net` 패키지의 취약점을 해결했습니다. + + * Go `1.24` 로 업그레이드되었으며 다음 의존성/종속성이 보안을 강화하고 최근 수정 사항을 통합하도록 업데이트되었습니다. + + * `golang.org/x/net to v0.38.0` + * `golang.org/x/sys to v0.31.0` + * `golang.org/x/text to v0.23.0` + + * [iOS v6.9.11용 모바일 앱](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6101): + * 사용자의 인증 도메인을 저장하고 사용자를 로그인 페이지로 직접 리디렉션하여 로그인 흐름을 두 단계로 줄였습니다. + + * [플러터 에이전트 v1.1.13](/docs/release-notes/mobile-release-notes/flutter-release-notes/flutter-agent-1113): + + * 개선된 네이티브 Android 에이전트가 버전 7.6.8로 업데이트되었습니다. + * 향상된 네이티브 iOS 에이전트가 버전 7.5.8로 업데이트되었습니다. + + * [.NET MAUI 에이전트 v1.1.11](/docs/release-notes/mobile-release-notes/net-maui-release-notes/net-maui-agent-1111) + + * 개선된 네이티브 Android 에이전트가 버전 7.6.8로 업데이트되었습니다. + * 향상된 네이티브 iOS 에이전트가 버전 7.5.8로 업데이트되었습니다. + + * [인프라 에이전트 v1.65.5](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1655): + * 저장소 샘플에서 지원 AWS EFS 마운트를 변경했습니다. \ No newline at end of file diff --git a/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-8-14-2025.mdx b/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-8-14-2025.mdx new file mode 100644 index 00000000000..aa88f66f598 --- /dev/null +++ b/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-8-14-2025.mdx @@ -0,0 +1,112 @@ +--- +subject: Docs +releaseDate: '2025-08-15' +version: 'August 08 - August 14, 2025' +translationType: machine +--- + +### 새로운 문서 + +* [NRQL 함수에 대한 지원을 게이트웨이 규칙에](/docs/new-relic-control/pipeline-control/nrql-functions) 추가하여 NRQL 게이트웨이 규칙에서 지원되는 NRQL 함수를 간략하게 설명했습니다. +* 뉴렐릭 인프라 에이전트 설정에서 호스트명 해상도 설정을 조정하여 [빈번한 Fluent Bit Restart 이벤트를](/docs/infrastructure/infrastructure-troubleshooting/troubleshoot-infrastructure/frequent-fluent-bit-restart-events) 해결하기 위한 문제 해결, 해결 단계를 추가했습니다. + +### 주요 변경 사항 + +* 최신 가격 정보가 포함된 업데이트된 [사용 계획](/docs/licenses/license-information/usage-plans/new-relic-usage-plan/#list-price) 입니다. +* [워크로드 UI](/docs/new-relic-solutions/new-relic-one/workloads/use-workloads/#errors)에 **Error inbox** \[오류 받은 편지함]을 추가했습니다. +* [저항](/docs/apm/agents/java-agent/configuration/java-agent-configuration-config-file/#skip-applications) 세력 설정에 대한 강화된 보안 설정과 함께 환경 변수를 통해 시작 메인 클래스 또는 실행 가능한 jar를 기반으로 선택적 에이전트 비활성화를 추가했습니다. +* 에이전트 제어에 [개인용 스테이션 설정](/docs/new-relic-control/agent-control/configuration/#private-repository-configuration) 에 대한 지원이 추가되어 기본 또는 TLS 인증서 방법을 통한 인증으로 관리형 에이전트의 구현, 배포가 가능해졌습니다. +* 에이전트 제어에서 [비밀 관리](/docs/new-relic-control/agent-control/configuration/#secrets-management) 에 대한 지원이 추가되어 전용 비밀 공급자로부터 비밀번호 및 API 키와 같은 민감한 데이터를 검색하여 관리할 수 있습니다. + +### 사소한 변경 사항 + +* [파이프라인 제어 cloud 규칙을 사용하여 데이터 삭제](/docs/new-relic-control/pipeline-control/cloud-rules-api/#restrictions) 에 `WHERE` 절에 대한 카테고리 태그 제한을 추가했습니다. +* 뉴렐릭 AI 지식 커넥터에 대한 [지식 소스 콘텐츠를 최적화하기 위한 모범 사례를](/docs/agentic-ai/knowledge-integration/overview/#configure) 추가했습니다. + +### 릴리즈 정보 + +* 새로운 소식 게시물을 확인하세요. + + * [UniqueCount 고정밀 모드와 향상된 인수 지원이 이제 일반적으로 사용 가능합니다](/whats-new/2025/08/whats-new-8-13-high-precision-uniquecount). + +* 최신 릴리스에 대한 최신 정보를 받아보세요. + + * [코도바 에이전트 v7.0.8](/docs/release-notes/mobile-release-notes/cordova-release-notes/cordova-agent-708/): + + * 네이티브 안드로이드 에이전트를 7.6.8 버전으로 업데이트하세요 + * 네이티브 iOS 에이전트를 7.5.8 버전으로 업데이트하세요. + + * [코도바 에이전트 v7.0.9](/docs/release-notes/mobile-release-notes/cordova-release-notes/cordova-agent-709/): + + * 네이티브 안드로이드 에이전트를 7.6.6 버전으로 업데이트하세요 + * 네이티브 iOS 에이전트를 7.5.5 버전으로 업데이트하세요. + + * [Capacitor 에이전트 v1.5.8](/docs/release-notes/mobile-release-notes/capacitor-release-notes/capacitor-agent-158/): + + * 네이티브 안드로이드 에이전트를 7.6.6 버전으로 업데이트하세요 + * 네이티브 iOS 에이전트를 7.5.5 버전으로 업데이트하세요. + + * [Capacitor 에이전트 v1.5.9](/docs/release-notes/mobile-release-notes/capacitor-release-notes/capacitor-agent-159/): + * 고정된 중단 신호 충돌 + + * [Capacitor 에이전트 v1.5.10](/docs/release-notes/mobile-release-notes/capacitor-release-notes/capacitor-agent-1510/): + + * 네이티브 안드로이드 에이전트를 7.6.8 버전으로 업데이트하세요 + * 네이티브 iOS 에이전트를 7.5.8 버전으로 업데이트하세요. + + * [진단 CLI(nrdiag) v3.5.0](/docs/release-notes/diagnostics-release-notes/diagnostics-cli-release-notes/diagnostics-cli-350/): + * `Java/Appserver/JbossEapCheck` 버전 호환성 검사를 업데이트했습니다. + + * [.NET 에이전트 v10.44.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-44-0/): + + * Serverless 모드에서 성능 메트릭 샘플러 활성화 + * 측정, 리소스에서 Azure Function 웹호스트(Linux) 프로세스를 제외했습니다. + + * [NRDOT v1.3.0](/docs/release-notes/nrdot-release-notes/nrdot-2025-08-13/): + + * 호텔 구성 요소 버전이 v0.128.0에서 v0.131.0으로 상향 조정되었습니다. + * nrdot 코어 배포판 출시 + + * [Node.js 에이전트 v13.1.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-1-0/): + + * OTEL 로그 API에 대한 지원이 추가되었습니다. + * 패키지에 대해 측정, 로그가 비활성화된 경우 지원 가능성 지표를 추가했습니다. + * 비활성화된 타이머 측정, 기본적으로 샘플 설정의 로그 + * `transaction.url` 난독화 수정 + + * [작업 관리자 v454](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-454/): + * SJM의 보안 취약점을 해결하기 위해 Ubuntu의 기본 취약점을 수정했습니다. + + * [노드 API 런타임 v1.2.124](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.124/): + * Node API 런타임의 보안 취약점을 해결하기 위해 기본 Ubuntu 취약점을 수정했습니다. + + * [노드 브라우저 런타임 v3.0.41](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.41/): + * 노드 브라우저 런타임의 보안 쿠키를 해결하기 위해 tmp `CVE-2025-54798` 붂개 및 기본 Ubuntu 접속을 수정했습니다. + + * [Ping 런타임 v1.54.0](/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.54.0/): + * Ping 런타임의 보안 문제를 해결하기 위해 Ubuntu와 관련된 취약점을 수정했습니다. + + * [대응 에이전트 v8.23.0](/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8230/): + + * graphql v24를 지원하도록 업데이트되었습니다. + * 양상추 6.5 측정, 로그가 추가되었습니다. + * commons-lang 버전을 3.18.0으로 올렸습니다. + + * [AWS Lambda 로그인 전달자 v1.1.1](/docs/release-notes/aws-lambda-log-forwarder-release-notes/lambda-25-07-25/): + * 시스템의 Go 버전을 1.24.4로 업그레이드하여 보안 태세를 강화했습니다. + + * [PHP 에이전트 v12.0.0.25](/docs/release-notes/agent-release-notes/php-release-notes/php-agent-12-0-0-25/): + + * Drupal Hook Map 오류 로깅이 개선되었습니다. + * 시큐리티 RX의 구형 패키지 감지 문제를 수정했습니다. + + * [인프라 에이전트 v1.66.1](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1661/): + * 스토리지 샘플에서 AWS EFS 마운트에 대한 지원을 되돌렸습니다. + + * [Android v5.30.6용 모바일 앱](docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5306/): + * SAML 및 소셜 로그인에 대한 향상된 Passkey 지원. + + * [브라우저 에이전트 v1.295.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.0/): + + * 오류 원인 감지 기능이 추가되었습니다. + * 몽키 패칭 경고를 추가했습니다. \ No newline at end of file diff --git a/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-8-21-2025.mdx b/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-8-21-2025.mdx new file mode 100644 index 00000000000..690e192131c --- /dev/null +++ b/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-8-21-2025.mdx @@ -0,0 +1,56 @@ +--- +subject: Docs +releaseDate: '2025-08-22' +version: 'August 15 - August 21, 2025' +translationType: machine +--- + +### 주요 변경 사항 + +* [Node.js 에이전트](/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent/) 호환성 보고서가 업데이트되었습니다. +* 최신 검증된 호환 라이브러리 버전으로 [.NET 에이전트를](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements/) 업데이트했습니다. + +### 사소한 변경 사항 + +* Linux용 [에이전트](/docs/infrastructure/infrastructure-agent/requirements-infrastructure-agent/#os) 에이전트를 지원하도록 [Debian 운영 시스템을 버전 12("bookworm")로 업데이트했습니다.](/docs/infrastructure/infrastructure-agent/linux-installation/package-manager-install/) +* 데이터 제한을 쿼리하기 위한 [`accountId()`](/docs/data-apis/manage-data/query-limits/) 함수가 업데이트되었습니다. +* 64비트Windows (Intel/AMD)를 지원하도록 [Windows MSI 설치기를](/docs/infrastructure/infrastructure-agent/windows-installation/windows-msi-installer/#install-windows) 업데이트했습니다. + +### 릴리즈 정보 + +* [AI 모니터링 UI](/docs/ai-monitoring/drop-sensitive-data/) 를 통해 2026년 1월 7일이 폐기 규칙의 수명 종료일로 발표되었습니다. + +* [iOS 에이전트 v7.5.9](/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-759/) + + * 세션 시작 시 분산 추적에 필요한 모든 계정 정보가 포함되지 않는 문제를 해결했습니다. + * 에이전트 시작 시 충돌이 발생할 수 있는 문제를 해결했습니다. + +* [파이썬 에이전트 v10.16.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-101600/) + + * 새로운 [REDIS](https://pypi.org/project/redis/) 기능에 대한 지원이 추가되었습니다. + * 모든 내부 경로를 `os.path` 에서 `pathlib.Path` 로 변환했습니다. + * PosixPath의 JSON 인코딩 문제가 해결되었습니다. + +* [Kubernetes 통합 v3.44.1](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-44-1/) + + * 이 통합은 다음 차트 버전에 포함되어 있습니다. + + * [뉴렐릭-인프라-3.49.1](https://github.com/newrelic/nri-kubernetes/releases/tag/newrelic-infrastructure-3.49.1) + * [nri-bundle-6.0.10](https://github.com/newrelic/helm-charts/releases/tag/nri-bundle-6.0.10) + +* [.NET 에이전트 v10.44.1](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-44-1/) + + * Service Bus 측정, 로그 래퍼에서 예외 처리가 수정되었습니다. + * 측정, 리소스에서 Azure Function 웹호스트(Linux) 프로세스를 제외했습니다. + +* [Node.js 에이전트 v13.2.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-2-0/) + + * 구독자 기반 측정, 리소스에 대한 `Supportability/Features/Instrumentation/OnRequire/` 지표를 등록하는 기능이 추가되었습니다. + * orchestrion-js와 함께 작동하도록 esm 로더 후크와 commonjs 패치를 추가했습니다. + * `@modelcontextprotocol/sdk` 클라이언트 호출 `client.callTool`, `client.readResource` 및 `client.getPrompt` 에 대한 측정, 로그가 추가되었습니다. + * OTEL 패키지 감지에 대한 고정 논리가 적용되었습니다. + * 비활성화된 구독자를 올바르게 설정하고 건너뛸 수 있도록 `shimmer.setupSubscribers` 업데이트했습니다. + +* [Node.js 에이전트 v13.2.1](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-2-1/) + + * 추적 채널 기반 측정을 위한 CJS/ESM 등록에 `@apm-js-collab/tracing-hooks` 사용하도록 에이전트가 업데이트되었습니다. \ No newline at end of file diff --git a/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-9-12-2025.mdx b/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-9-12-2025.mdx new file mode 100644 index 00000000000..b882f2ec86d --- /dev/null +++ b/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-9-12-2025.mdx @@ -0,0 +1,94 @@ +--- +subject: Docs +releaseDate: '2025-09-14' +version: 'September 08 - September 12, 2025' +translationType: machine +--- + +### 새로운 문서 + +* 4가지 핵심 영역(비즈니스 업타임, 디지털 경험, 엔지니어링 우수성, 인텔리전스)에 걸쳐 옵저버빌리티 관행을 측정하고 개선하기 위한 지침을 제공하기 위해 포괄적인 [옵저버빌리티 성숙도 모델](/docs/new-relic-solutions/observability-maturity/) 문서를 추가했습니다. + +### 주요 변경 사항 + +* 샘플링 컨트롤 및 프레임워크 예외 처리기 측정을 위한 광범위한 새 설정 옵션으로 [PHP 에이전트 설정이](/docs/apm/agents/php-agent/configuration/php-agent-configuration/) 업데이트되었습니다. + +### 사소한 변경 사항 + +* 대시보드 사용에 대한 향상된 가이드를 포함하여 [대시보드 소개가](/docs/query-your-data/explore-query-data/dashboards/introduction-dashboards/) 업데이트되었습니다. +* JSON 관리를 위한 간소화된 콘텐츠로 [대시보드 관리](/docs/query-your-data/explore-query-data/dashboards/manage-your-dashboard/) 문서가 개선되었습니다. +* [뉴렐릭 사용 계획](/docs/licenses/license-information/usage-plans/new-relic-usage-plan/) 문서의 깨진 링크를 수정했습니다. +* [.NET 에이전트 문제 해결, 해결](/docs/apm/agents/net-agent/troubleshooting/debugging-net-windows/) 문서의 디버깅 설정이 수정되었습니다. + +### 릴리즈 정보 + +* 최신 릴리스에 대한 최신 정보를 받아보세요. + + * [브라우저 에이전트 v1.297.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.297.0/): + + * 재시도 기간 동안 조기 수확을 방지하여 더 나은 속도 제한 처리를 제공합니다. + * 청구 가능한 바이트를 줄이기 위해 나가는 리플레이 페이로드에서 Newrelic 메타 속성을 제거했습니다. + * 빈 수확으로 인해 발생하는 null 본문에 대한 고정 예외가 수정되었습니다. + + * [PHP 에이전트 v12.1.0.26](/docs/release-notes/agent-release-notes/php-release-notes/php-agent-12-1-0-26/): + + * 업스트림 w3c 트레이스 바로 결정을 기반으로 샘플링 제어가 추가되었습니다. + * 프레임워크 예외 처리기의 측정, 서명을 건너뛰는 설정 옵션이 추가되었습니다. + * `newrelic_end_transaction(true)` 호출할 때 잠재적인 메모리 누수가 해결되었습니다. + * 보안 개선을 위해 Golang 버전을 1.25.1로 올렸습니다. + + * [접착제 에이전트 v10.17.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-101700/): + + * Celery에서 사용자 정의 작업에 대한 지원이 추가되었습니다. + * Graphene-Django 모니터링에 대한 지원이 추가되었습니다. + * Django에서 미들웨어 필터링에 대한 지원이 추가되었습니다. + * AWS Bedrock Converse API에 대한 지원이 추가되었습니다. + * W3CTraceParent 헤더 샘플링 플래그에 대한 지원이 추가되었습니다. + + * [대응 에이전트 v8.24.0](/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8240/): + + * MongoDB Reactive Streams 5.2.0 이상에 대한 지원이 추가되었습니다. + * Jedis 6 지원이 추가되었습니다. + * CouchBase 이중 측정, 로그 문제가 해결되었습니다. + * Spring WebClient 5.x 헤더 래핑 문제가 해결되었습니다. + + * [Node.js 에이전트 v13.3.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-3-0/): + + * MCP `StreamableHTTPClientTransport` 지원이 추가되었습니다. + + * [Node.js 에이전트 v13.3.1](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-3-1/): + + * `transaction.addRequestParameters` 의 객체에 `requestParameters` 기본값으로 지정하여 충돌을 해결했습니다. + + * [Node.js 에이전트 v13.3.2](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-3-2/): + + * 아웃바운드 http 호출에서 `protocol` 얻기 위한 방어 코드가 추가되었습니다. + + * [Kubernetes 통합 v3.45.1](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-45-1/): + + * 최신 개선 사항과 버그 수정이 적용되었습니다. + + * [작업 관리자 v464](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-464/): + + * 고객이 podman을 사용하여 사용자 지정 레지스트리에서 이미지를 가져올 수 없는 문제가 해결되었습니다. + + * [노드 브라우저 런타임 v3.0.43](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.43/): + + * 보안 취약점을 해결하기 위해 Ubuntu의 기본 취약점을 수정했습니다. + + * [iOS v6.9.12용 모바일 앱](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6102/): + + * 대시보드 및 알림에 대한 딥 링크 문제가 해결되었습니다. + * CCU 대시보드 ID 문제가 해결되었습니다. + + * [Android v5.30.7용 모바일 앱](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5307/): + + * 버그 수정 및 개선 사항이 추가되었습니다. + + * [플러터 에이전트 v1.1.14](/docs/release-notes/mobile-release-notes/flutter-release-notes/flutter-agent-1114/): + + * 추가적인 안정성 개선 및 버그 수정이 이루어졌습니다. + + * [파이프라인 컨트롤 게이트웨이 v25.09.01](/docs/release-notes/pipeline-control-gateway-release-notes/pipeline-control-gateway-25-09-01/): + + * 파이프라인 제어 기능이 향상된 새로운 릴리스가 추가되었습니다. \ No newline at end of file diff --git a/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-9-15-2025.mdx b/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-9-15-2025.mdx new file mode 100644 index 00000000000..4d22ef57c31 --- /dev/null +++ b/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-9-15-2025.mdx @@ -0,0 +1,84 @@ +--- +subject: Docs +releaseDate: '2025-09-19' +version: 'September 15 - September 19, 2025' +translationType: machine +--- + +### 새로운 문서 + +* 메트릭에 대한 AWS 통합 재구성: + + * [수동 AWS 통합](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/manual/)추가 + * [Terraform AWS 통합이](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/terraform/)추가되었습니다. + * [API 폴링 통합을 통해 CloudFormation](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-and-api-polling/)추가 + * [API 폴링에서 CloudWatch Metric Streams으로의 마이그레이션 가이드가](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/migrate-from-api-polling-to-cwms/)추가되었습니다. + +### 주요 변경 사항 + +* 독립형 에이전트 구조 업데이트로 향상된 [스트리밍 비디오 및 광고 문서가](/docs/streaming-video-&-ads/get-started-with-streaming-video-&-ads/) 추가되었습니다. + +### 사소한 변경 사항 + +* 향상된 문서화를 통해 [GitHub을 통해 NerdGraph 문제 API를](/docs/apis/nerdgraph/examples/nerdgraph-issues-api-via-github/) 업데이트했습니다. +* 향상된 설정 지침으로 [Microsoft Teams 통합이](/docs/alerts-applied-intelligence/notifications/notification-integrations/) 업데이트되었습니다. +* [히트맵](docs/query-your-data/explore-query-data/use-charts/chart-types/#widget-heatmap) 차트 유형이 업데이트되었습니다. +* QPM 모니터링을 위한 타이밍 개선을 통해 [MySQL 통합이](/docs/infrastructure/host-integrations/host-integrations-list/mysql-monitoring-integration/) 업데이트되었습니다. +* 사소한 업데이트로 향상된 [기수 관리](/docs/data-apis/ingest-apis/metric-api/cardinality-management/) 문서가 추가되었습니다. +* 최신 검증된 호환 라이브러리 버전으로 [.NET 에이전트 호환성 요구 사항을](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements/) 업데이트했습니다. +* [파이프라인 제어 코드](docs/new-relic-control/pipeline-control/cloud-rules-api/) 버그 문서를 수정했습니다. + +### 릴리즈 정보 + +* [IP 주소에 대한 새로운 수명 종료 날짜로 신세틱 모니터링이](/eol/2025/02/eol-01-31-25-synthetics-ip/) 업데이트되었습니다. + +* 최신 릴리스에 대한 최신 정보를 받아보세요. + + * [대응 에이전트 v8.24.0](/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8240/): + + * MongoDB Reactive Streams 5.2.0 이상에 대한 지원이 추가되었습니다. + * Jedis 6 지원이 추가되었습니다. + * CouchBase 이중 측정, 로그 문제가 해결되었습니다. + * Spring WebClient 5.x 헤더 래핑 문제가 해결되었습니다. + + * [접착제 에이전트 v10.17.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-101700/): + + * Celery에서 사용자 정의 작업에 대한 지원이 추가되었습니다. + * Graphene-Django 모니터링에 대한 지원이 추가되었습니다. + * Django에서 미들웨어 필터링에 대한 지원이 추가되었습니다. + * AWS Bedrock Converse API에 대한 지원이 추가되었습니다. + * W3CTraceParent 헤더 샘플링 플래그에 대한 지원이 추가되었습니다. + + * [인프라 에이전트 v1.68.0](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/1680/): + + * Go 버전을 1.25.0으로 업그레이드했습니다. + * 의존성/종속성 newrelic/nri-winservices를 v1.3.0으로 업데이트했습니다. + + * [브라우저 에이전트 v1.298.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.298.0/): + + * DOM 수정 시간을 넘어서는 긴 작업을 포함하도록 확장된 소프트 탐색 기능을 제공합니다. + * 소프트 탐색 중에 현재 페이지 URL 대신 원래 페이지 URL을 보고하도록 LCP를 수정했습니다. + + * [브라우저 에이전트 v1.297.1](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.297.1/): + + * newrelic.recordReplay를 사용할 때 세션 리플레이 집계 클래스를 두 번 가져올 수 있는 문제를 해결했습니다. 사전 로딩이 활성화된 동안 API 메서드가 활성화되었습니다. + + * [리액트 작용 에이전트 v1.5.10](/docs/release-notes/mobile-release-notes/react-native-release-notes/react-native-agent-1510/): + + * 네이티브 안드로이드 에이전트를 7.6.9 버전으로 업데이트했습니다. + * 네이티브 iOS 에이전트를 7.5.10 버전으로 업데이트했습니다. + + * [iOS 에이전트 v7.5.10](/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-7510/): + + * 에이전트 시작 시 발생할 수 있는 충돌을 해결했습니다. + + * [NRDOT v1.4.0](/docs/release-notes/nrdot-release-notes/nrdot-2025-09-18/): + + * nrdot-수집기에 스팬프로세서를 추가했습니다. + * OpenTelemetry 구성 요소 버전이 v0.131.0에서 v0.132.0으로 상향 조정되었습니다. + * 내부 텔레메트리 구성에 newrelic.service.type을 추가했습니다. + * EC2에 대한 호스트 이름 감지가 활성화되었습니다. + + * [Kubernetes 통합 v3.45.2](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-45-2/): + + * 최신 개선 사항과 버그 수정이 적용되었습니다. \ No newline at end of file diff --git a/src/i18n/content/kr/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-759.mdx b/src/i18n/content/kr/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-759.mdx index 8f729551e26..1150bb71926 100644 --- a/src/i18n/content/kr/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-759.mdx +++ b/src/i18n/content/kr/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-759.mdx @@ -6,14 +6,6 @@ downloadLink: 'https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agen translationType: machine --- - - iOS SDK 버전 7.5.4부터 이전에 억제되었던 Handled Exception 이벤트가 보고되도록 변경되었습니다. - - 뉴렐릭 iOS 에이전트 7.5.9로 업데이트해주세요. iOS SDK 버전 7.5.8에서 잘못된 데이터 업로드를 유발할 수 있는 버그가 발견되었으며, 해당 수정 사항은 뉴렐릭 iOS 에이전트 7.5.9에 포함되어 있습니다. 풀어 주다. - - 뉴렐릭 iOS 에이전트 7.5.9로 업데이트해주세요. iOS SDK 버전 7.5.7에서 에이전트에 충돌을 일으킬 수 있는 버그가 발견되었으며, 이를 뉴렐릭 iOS 7.5.9에 수정했습니다. 풀어 주다. - - ## 이 릴리스에서 수정됨 * 에이전트는 Xcode 16.4를 사용하여 빌드되었습니다. diff --git a/src/i18n/content/kr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx b/src/i18n/content/kr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx new file mode 100644 index 00000000000..d2e754e3a25 --- /dev/null +++ b/src/i18n/content/kr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx @@ -0,0 +1,39 @@ +--- +subject: Browser agent +releaseDate: '2025-08-04' +version: 1.295.0 +downloadLink: 'https://www.npmjs.com/package/@newrelic/browser-agent' +features: + - Add error cause detection +bugs: + - Add monkey-patching warnings + - Calculate first and last timestamps from raw data +security: [] +translationType: machine +--- + +## v1.295.0 + +### 특징 + +#### 오류 원인 감지 추가 + +캡처된 JavaScriptError 이벤트에서 원인 속성을 감지하고 보고합니다. 원인이 오류의 인스턴스인 경우 스택 추적이 캡처되고, 그렇지 않은 경우 원인의 문자열화된 내용이 보고됩니다. 이는 `cause` 속성 아래의 JavaScriptError 이벤트에서 쿼리될 수 있습니다. + +### 버그 수정 + +#### 몽키 패칭 경고 추가 + +에이전트가 페이지에서 실행되기 전에 예상되는 글로벌 변수에 몽키 패치가 적용된 경우 감지 및 경고가 추가되었습니다. 이로 인해 예상치 못한 동작이 발생할 수 있으며, 고객에게 이러한 동작에 대해 알리는 것이 목적입니다. + +#### 원시 데이터에서 첫 번째 및 마지막 타임스탬프 계산 + +UI 리플레이어의 일관성을 개선하기 위해 수집하기 전에 에이전트가 SessionReplay 페이로드의 첫 번째 및 마지막 타임스탬프를 수동으로 계산하도록 합니다. + +## 지지 성명 + +뉴렐릭은 에이전트를 정기적으로 업그레이드하여 최신 기능과 성능 이점을 얻을 것을 권장합니다. 이전 릴리스는 지원 [종료](https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/browser-agent-eol-policy/) 시점부터 더 이상 지원되지 않습니다. 출시일은 에이전트 버전의 원래 출판일을 반영합니다. + +새로운 브라우저 에이전트 릴리스는 일정 기간 동안 작은 단계로 고객에게 출시됩니다. 이로 인해, 귀하의 계정에서 해당 릴리스에 접근할 수 있는 날짜가 원래 게시 날짜와 일치하지 않을 수 있습니다. 자세한 내용은 이 [상태 대시보드를](https://newrelic.github.io/newrelic-browser-agent-release/) 참조하세요. + +[브라우저 지원 정책](https://docs.newrelic.com/docs/browser/new-relic-browser/getting-started/compatibility-requirements-browser-monitoring/#browser-types) 에 따라, 브라우저 에이전트 v1.295.0은 다음 브라우저 및 버전 범위에 맞춰 빌드되고 테스트되었습니다: Chrome 128-138, Edge 128-138, Safari 17-19, Firefox 130-140. 모바일 장치의 경우 v1.295.0은 Android OS 16 및 iOS Safari 17-26용으로 구축 및 테스트되었습니다. \ No newline at end of file diff --git a/src/i18n/content/kr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.296.mdx b/src/i18n/content/kr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.296.mdx new file mode 100644 index 00000000000..6325fc4941e --- /dev/null +++ b/src/i18n/content/kr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.296.mdx @@ -0,0 +1,34 @@ +--- +subject: Browser agent +releaseDate: '2025-08-19' +version: 1.296.0 +downloadLink: 'https://www.npmjs.com/package/@newrelic/browser-agent' +features: + - Harvest traces early +bugs: + - Remove event buffer inspection event +security: [] +translationType: machine +--- + +## v1.296.0 + +### 특징 + +#### 수확 트레이스 조기 + +에이전트가 [1.294.0](https://docs.newrelic.com/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.294.0/) 부터 다른 기능이 데이터를 처리하는 것과 동일한 방식으로 세션 트레이스를 처리하도록 업데이트합니다. 16kb 크기에서 수확을 허용함으로써. + +### 버그 수정 + +#### 이벤트 버퍼 검사 이벤트 제거 + +`newrelic` 창 이벤트 리스너와 함께 console.log를 사용할 때 메모리 누수를 방지하기 위해 이벤트 버퍼 검사 이벤트를 제거합니다. + +## 지지 성명 + +뉴렐릭은 에이전트를 정기적으로 업그레이드하여 최신 기능과 성능 이점을 얻을 것을 권장합니다. 이전 릴리스는 지원 [종료](https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/browser-agent-eol-policy/) 시점부터 더 이상 지원되지 않습니다. 출시일은 에이전트 버전의 원래 출판일을 반영합니다. + +새로운 브라우저 에이전트 릴리스는 일정 기간 동안 작은 단계로 고객에게 출시됩니다. 이로 인해, 귀하의 계정에서 해당 릴리스에 접근할 수 있는 날짜가 원래 게시 날짜와 일치하지 않을 수 있습니다. 자세한 내용은 이 [상태 대시보드를](https://newrelic.github.io/newrelic-browser-agent-release/) 참조하세요. + +[브라우저 지원 정책](https://docs.newrelic.com/docs/browser/new-relic-browser/getting-started/compatibility-requirements-browser-monitoring/#browser-types) 에 따라, 브라우저 에이전트 v1.296.0은 다음 브라우저 및 버전 범위에 맞춰 빌드되고 테스트되었습니다: Chrome 129-139, Edge 129-139, Safari 17-19, Firefox 131-141. 모바일 장치의 경우 v1.296.0은 Android OS 16 및 iOS Safari 17-18.1에 대해 구축 및 테스트되었습니다. \ No newline at end of file diff --git a/src/i18n/content/kr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.297.mdx b/src/i18n/content/kr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.297.mdx new file mode 100644 index 00000000000..67041e6d551 --- /dev/null +++ b/src/i18n/content/kr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.297.mdx @@ -0,0 +1,27 @@ +--- +subject: Browser agent +releaseDate: '2025-09-17' +version: 1.297.1 +downloadLink: 'https://www.npmjs.com/package/@newrelic/browser-agent' +features: [] +bugs: + - Prevent double import of Session Replay aggregate class +security: [] +translationType: machine +--- + +## v1.297.1 + +### 버그 수정 + +#### 세션 리플레이 집계 클래스 이중 가져오기 방지 + +newrelic.recordReplay를 사용할 때 세션 재생 집계 클래스를 두 번 가져올 수 있는 문제가 발견되었습니다. 사전 로딩이 활성화된 동안 API 메서드가 활성화되었습니다. + +## 지지 성명 + +뉴렐릭은 에이전트를 정기적으로 업그레이드하여 최신 기능과 성능 이점을 얻을 것을 권장합니다. 이전 릴리스는 지원 [종료](https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/browser-agent-eol-policy/) 시점부터 더 이상 지원되지 않습니다. 출시일은 에이전트 버전의 원래 출판일을 반영합니다. + +새로운 브라우저 에이전트 릴리스는 일정 기간 동안 작은 단계로 고객에게 출시됩니다. 이로 인해, 귀하의 계정에서 해당 릴리스에 접근할 수 있는 날짜가 원래 게시 날짜와 일치하지 않을 수 있습니다. 자세한 내용은 이 [상태 대시보드를](https://newrelic.github.io/newrelic-browser-agent-release/) 참조하세요. + +[브라우저 지원 정책](https://docs.newrelic.com/docs/browser/new-relic-browser/getting-started/compatibility-requirements-browser-monitoring/#browser-types) 에 따라, 브라우저 에이전트 v1.297.1은 다음 브라우저 및 버전 범위에 맞춰 빌드되고 테스트되었습니다: Chrome 130-140, Edge 130-140, Safari 17-19, Firefox 132-142. 모바일 장치의 경우 v1.297.1은 Android OS 16 및 iOS Safari 17-18.5에 대해 구축 및 테스트되었습니다. \ No newline at end of file diff --git a/src/i18n/content/kr/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.mdx b/src/i18n/content/kr/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.mdx new file mode 100644 index 00000000000..3406c1d2490 --- /dev/null +++ b/src/i18n/content/kr/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.mdx @@ -0,0 +1,10 @@ +--- +subject: Node API runtime +releaseDate: '2025-07-29' +version: 1.2.122 +translationType: machine +--- + +### 수정 사항 + +* Node API 런타임에서 보안 교육을 처리하기 위해 양식 데이터 잘라내 및 기본 Ubuntu 잘라내를 수정했습니다. \ No newline at end of file diff --git a/src/i18n/content/kr/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.mdx b/src/i18n/content/kr/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.mdx new file mode 100644 index 00000000000..063ff1fe630 --- /dev/null +++ b/src/i18n/content/kr/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.mdx @@ -0,0 +1,10 @@ +--- +subject: Node browser runtime +releaseDate: '2025-07-29' +version: 3.0.39 +translationType: machine +--- + +### 개량 + +* Node 브라우저 런타임의 보안 쿠키를 해결하기 위해 form-data 쿠키 및 기본 Ubuntu 괄호를 수정했습니다. \ No newline at end of file diff --git a/src/i18n/content/kr/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.53.mdx b/src/i18n/content/kr/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.53.mdx new file mode 100644 index 00000000000..d0c4af0c3c3 --- /dev/null +++ b/src/i18n/content/kr/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.53.mdx @@ -0,0 +1,10 @@ +--- +subject: Ping Runtime +releaseDate: '2025-07-29' +version: 1.53.0 +translationType: machine +--- + +### 개량 + +* Ping 런타임의 보안 문제를 해결하기 위해 `common-lang3` ย 및 Ubuntu와 관련된 고정된 버그를 수정했습니다. \ No newline at end of file diff --git a/src/i18n/content/kr/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.54.mdx b/src/i18n/content/kr/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.54.mdx new file mode 100644 index 00000000000..1e9b8e6103d --- /dev/null +++ b/src/i18n/content/kr/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.54.mdx @@ -0,0 +1,10 @@ +--- +subject: Ping Runtime +releaseDate: '2025-08-13' +version: 1.54.0 +translationType: machine +--- + +### 개량 + +* Ping 런타임의 보안 문제를 해결하기 위해 Ubuntu와 관련된 취약점을 수정했습니다. \ No newline at end of file diff --git a/src/i18n/content/pt/docs/accounts/accounts-billing/new-relic-one-pricing-billing/add-on-billing.mdx b/src/i18n/content/pt/docs/accounts/accounts-billing/new-relic-one-pricing-billing/add-on-billing.mdx new file mode 100644 index 00000000000..518f9563586 --- /dev/null +++ b/src/i18n/content/pt/docs/accounts/accounts-billing/new-relic-one-pricing-billing/add-on-billing.mdx @@ -0,0 +1,28 @@ +--- +title: Faturamento adicional (opcional) +tags: + - Accounts + - Accounts and billing + - New Relic pricing and billing +metaDescription: Add-ons are an optional billing factor +freshnessValidatedDate: '2024-10-23T00:00:00.000Z' +translationType: machine +--- + +Além dos fatores de cobrança principais do GB Ingested e do usuário faturável, você também pode usar complementos faturáveis opcionais para estender sua experiência com New Relic. + +* **Advanced Compute (anteriormente Add-on Compute)**: este complemento se aplica à cobrança baseada no uso para ações que você executa relacionadas ao CodeStream, Live Archives e outros recursos disponibilizados. Você é medido e cobrado com base no uso de [CCUs avançadas](/docs/licenses/license-information/product-definitions/new-relic-one-pricing-definitions/#compute-capacity-unit). + + + O uso do CodeStream no Advanced Computer incorrerá em cobranças de CCU, independentemente do tipo de usuário. Isso significa que o usuário básico gratuito pode acessar recursos de computador avançados e incorrer em cobranças por CCUs avançados. + + +* **EU Data Center for Original Data or Data Plus**: Este complemento se aplica à sua opção de dados (Dados Originais ou Dados Plus) quando você seleciona a União Europeia como sua região de dados, conforme disponível. + +* **Extended Retention for Original Data or Data Plus**: este complemento será aplicado se você exceder o período padrão de retenção dos seus dados. Isso se aplica a todos os seus dados — não apenas aos logs — e é uma boa opção se você precisar fazer muitas consultas pequenas ou consultar grandes volumes de dados. + +* **Live Archives**: estenda a duração do armazenamento de logs em até sete anos. Live Archives também requer um computador avançado. + +* **New Relic Synthetic Checks**: este complemento é aplicado caso suas verificações excedam o número padrão de verificações do monitoramento sintético. + +* **Security RX**: Este recurso está incluído no Data Plus, mas o complemento se aplica se você usar o recurso Security RX sem o Data Plus. \ No newline at end of file diff --git a/src/i18n/content/pt/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing.mdx b/src/i18n/content/pt/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing.mdx new file mode 100644 index 00000000000..6d724b3c3f9 --- /dev/null +++ b/src/i18n/content/pt/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing.mdx @@ -0,0 +1,354 @@ +--- +title: 'Dados: Faturamento e regras' +tags: + - Accounts + - Accounts and billing + - New Relic pricing and billing +metaDescription: 'For New Relic pricing, an explanation of how data ingest is calculated for billing purposes.' +freshnessValidatedDate: '2024-10-23T00:00:00.000Z' +translationType: machine +--- + +Para os preços da New Relic, os dados ingeridos pela sua organização New Relic são um fator de cobrança. + +## Saiba mais sobre custos [#costs] + +Se você ainda não é cliente New Relic e está curioso sobre custos, consulte primeiro [nossa página principal de preços](https://newrelic.com/pricing). Se você já é cliente, continue lendo para saber detalhes sobre o faturamento de ingestão de dados. + +## Ver a ingestão de dados na interface [#ui] + +Para saber como encontrar informações de uso e cobrança na interface, consulte [Interface de cobrança](/docs/accounts/accounts-billing/general-account-settings/introduction-account-settings). + +Para saber como visualizar e gerenciar a ingestão de dados, consulte [Gerenciar ingestão](/docs/data-apis/manage-data/manage-data-coming-new-relic). + +## Opções de dados: Data Plus e original [#data-prices] + +O preço da sua organização por GB de dados ingeridos varia dependendo da opção de dados que sua organização tem: **Data Plus** ou nossa opção **Original Data** . A opção Data Plus oferece recursos avançados de dados para desempenho, escala, segurança e governança otimizados. Uma organização New Relic pode ter apenas uma opção por vez. + +Aqui está uma tabela com comparações das duas opções. Os preços e limites são mensais e os preços estão em dólares americanos. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Recurso/habilidade + + **Original Data** opção + + **Data Plus** opção + + Mais detalhes do recurso +
+ [Edições](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing/#editions) + + Todas as edições + + Requer Standard, Pro ou Enterprise + + (Observamos abaixo se um recurso é específico de uma edição) + +
+ Limite de dados grátis + + 100 GB ingeridos + + 100 GB ingeridos + +
+ Preço dos dados
(além do limite livre) +
+ US$ 0,40/GB ingerido + + US$ 0,60/GB ingerido + +
+ Limite livre de retenção de dados
([varia de acordo com o tipo de dados](/docs/data-apis/manage-data/manage-data-retention)) +
+ Padrão de pelo menos 8 dias + + 90 dias extras por inadimplência + +
+ Preço para cada 30 dias adicionais de retenção
(além do limite gratuito) +
+ +US$ 0,05/GB + + +US$ 0,05/GB + +
+ Preço adicional para armazenar dados no [data center da UE](/docs/accounts/accounts-billing/account-setup/choose-your-data-center)
+
+ +US$ 0,05/GB + + +US$ 0,05/GB + + Os dados são armazenados no data center dos EUA por padrão. +
+ [Limite máximo de consulta](/docs/query-your-data/nrql-new-relic-query-language/get-started/rate-limits-nrql-queries/#query-limits) + + Até 20 bilhões de pontos de dados por minuto + + Até 60 bilhões de pontos de dados por minuto + +
+ [Duração máxima da consulta](/docs/query-your-data/nrql-new-relic-query-language/get-started/rate-limits-nrql-queries/#query-duration) + + 1 minuto + + Até 10 minutos + +
+ Escolha do provedor de nuvem + + Provedor de nuvem único + + Azure ou vários provedores de nuvem + + Escolha seu provedor de nuvem preferido para sua carga de trabalho de observabilidade para alinhar seu armazenamento de telemetria com seu modelo de implantação de engenharia e preferência de nuvem. +
+ [Ofuscação de logs](/docs/logs/ui-data/obfuscation-ui/) + + Mascarar [automaticamente](/docs/logs/get-started/new-relics-log-management-security-privacy/#log-obfuscation) padrões conhecidos de cartões de crédito e números de previdência social nos registros. + + Crie e rastreie regras diretamente na interface e [mascarar ou aplicar](/docs/logs/ui-data/obfuscation-ui/) dados log sensíveis a hash. + +
+ [Gerenciamento de vulnerabilidades New Relic ](/docs/vulnerability-management/overview)
(apenas usuário da plataforma completa) +
+ +US$ 0,10/GB
(além do limite gratuito) +
+ Standard, Pro e Enterprise + + Identifique vulnerabilidades e resolva riscos em todas as fases do ciclo de vida do software. +
+ Elegibilidade [FedRAMP Moderate](/docs/security/security-privacy/compliance/fedramp-compliant-endpoints) e [HIPAA](/docs/security/security-privacy/compliance/hipaa-readiness-new-relic) + + + + Empreendimento + + Obtenha conformidade de segurança por meio de configurações que ajudam você a atender aos requisitos FedRAMP e HIPAA. +
+ [Exportação de dados de streaming](/docs/apis/nerdgraph/examples/nerdgraph-streaming-export) + + + + Standard, Pro e Enterprise + + Configure regras para exportar simultaneamente dados de telemetria para o armazenamento AWS ou Azure de sua preferência. Serão aplicadas taxas de exportação adicionais para o provedor de nuvem. +
+ [Exportação de dados históricos](/docs/apis/nerdgraph/examples/nerdgraph-historical-data-export) + + + + Standard, Pro e Enterprise + + Execute consultas maiores sem tempo limite para análise e modelagem histórica, armazenamento de longo prazo e integração com outras plataformas de análise de dados. +
+ Serviço New Relic Nativo do Azure + + + + Standard, Pro e Enterprise
([com algumas limitações](#azure-native-data-plus)) +
+
+ +Para ver uma comparação lado a lado do Data Plus e nossa opção de dados original, consulte [nossa planilha de dados do Data Plus](https://newrelic.com/resources/datasheets/data-plus). + +Interessado no Data Plus? Consulte [Atualizar para Data Plus](#upgrade-data-plus). + +### Detalhes do serviço New Relic nativo do Azure [#azure-native-data-plus] + +Com o [Azure Native New Relic Service](/docs/infrastructure/microsoft-azure-integrations/get-started/azure-native), você pode coletar e armazenar dados de telemetria para aplicativos e infraestrutura diretamente no Azure. Este recurso está incluído no Data Plus, mas com estas limitações: + +* Disponível apenas na região do data center dos EUA +* Elegibilidade FedRAMP moderada/HIPAA não disponível +* Exportação de dados históricos não disponível + +## Atualize para o Data Plus [#upgrade-data-plus] + +Para atualizar para o Data Plus, acesse a [interface do usuário**Data retention** ](/docs/data-apis/manage-data/manage-data-retention/#adjust-retention)no hub de gerenciamento de dados e clique em **Upgrade retention**. + +* Observação: você pode ver um botão **Edit data retention** , mas ele é diferente do botão **Upgrade retention** . +* Para ver o botão **Upgrade retention** , você precisa ter [permissões de faturamento](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts/#admin-settings). Se você atende aos requisitos e ainda não vê a opção **Upgrade retention**, fale com seu representante de conta New Relic . + +## O que conta como GB ingeridos faturáveis? [#usage-calculation] + +No contexto do [plano de preços da New Relic](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing), "dados ingeridos" referem-se aos dados salvos na New Relic pela sua organização depois de aplicarmos várias regras de corte e transformação de dados. Em outras palavras, não é a quantidade de dados brutos enviados para a New Relic, mas o tamanho dos dados que realmente acabam sendo armazenados. + +Em geral, os dados que geramos para fornecer nosso recurso não contam para seus GB ingeridos. Exemplos de recursos e dados relacionados a recursos que não contam para o GB Ingerido incluem: + +* [Funcionalidade básica de alerta](/docs/alerts-applied-intelligence/new-relic-alerts/learn-alerts/alerts-concepts-workflow). Por exemplo, `NrAiIncident`, um evento usado para gerar esses recursos, não conta para GB ingeridos. +* Dados criados por dados brutos agregados (por exemplo, [dados agregados de infraestrutura](/docs/data-apis/manage-data/manage-data-retention/#infrastructure-data) ou [dados métricos dimensionais](/data-apis/manage-data/manage-data-retention/#dimensional-metrics)). +* [métricas clássicas](/docs/apis/nerdgraph/examples/golden-metrics-entities-nerdgraph-api-tutorial) (para mais informações clássicas, consulte nossas [definições de entidade](https://github.com/newrelic/entity-definitions)). +* Verificação do monitoramento sintético. Para obter detalhes sobre o faturamento do Sintético, consulte [Limites e preços do Sintético](/docs/synthetics/synthetic-monitoring/using-monitors/monitor-limits). +* Dados de rastreamento de uso e faturamento (por exemplo, `NrConsumption`). +* Dados relacionados à administração da conta (por exemplo, `NrIntegrationError`, `NrAuditEvent`). + +Para entender seu uso, consulte a [interface de uso](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing#usage-ui). + +## Outros detalhes de cálculo [#calculation-details] + +* No contexto do nosso modelo de preços, um GB é definido como 1 bilhão de bytes. +* O GB ingerido mensalmente é arredondado para o número inteiro mais próximo. Por exemplo, se sua organização usa 100,9 GB durante um mês, isso é contado como 100 GB. + +## Edição grátis [#free-tier-limits] + +Para obter detalhes sobre o GB Ingested para nossa edição gratuita, consulte [Edição gratuita](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing/#free). + +## Saber mais [#related-docs] + +* Para obter mais informações sobre como gerenciar GB ingeridos, consulte [Gerenciar ingestão de dados](/docs/data-apis/manage-data/manage-data-coming-new-relic). +* Para saber como consultar o uso, veja [consulta e alerta de uso](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts). \ No newline at end of file diff --git a/src/i18n/content/pt/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts.mdx b/src/i18n/content/pt/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts.mdx index e8072165ce0..21b8607f407 100644 --- a/src/i18n/content/pt/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts.mdx +++ b/src/i18n/content/pt/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts.mdx @@ -21,10 +21,11 @@ Tenha em mente o seguinte ao utilizar a interface de utilização ou realizar co ## Consulta de uso de ingestão de dados [#data-queries] -A [interface de uso](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing#usage-ui) exibe a ingestão de dados ao longo do tempo. Se precisar de mais detalhes do que a interface fornece, você pode usar uma variedade de consultas NRQL. Os exemplos abaixo incluem dois tipos de dados: +The [usage UI](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing#usage-ui) displays your data ingest over time. If you need more detail than the UI provides, you can use a variety of NRQL queries. The examples below include the following data types: * `NrConsumption`: use isso para se aprofundar nos detalhes de seu uso hora a hora. É menos útil como proxy para sua fatura. -* `NrMTDConsumption`: use isto para ver uma boa aproximação do seu uso agregado mensal. +* `NrMTDConsumption`: Use this to see an approximation of your monthly aggregated usage. +* `NrCustomerMTDConsumption`: Use this to see an approximation of a customer's monthly aggregated usage. @@ -60,7 +61,7 @@ A [interface de uso](/docs/accounts/accounts-billing/new-relic-one-pricing-billi - Esta consulta mostra os dados atuais ingeridos pela plataforma completa. Em outras palavras, ele mostra quanto você seria cobrado pelos seus dados naquele mês se fosse cobrado agora. As informações sobre taxas de uso são calculadas por hora e levam aproximadamente 3 horas para serem geradas. Se nenhum valor for exibido, consulte os dados de 4 horas atrás usando "SINCE 4 hour ago". + This query shows the current full platform ingested data. In other words, it shows how much you'd be billed for your data for that month if you were billed right now. Usage fee information is calculated hourly and takes approximately 3 hours to generate. If no values are displayed, please query data from 4 hours ago using "SINCE 4 hours ago." ```sql FROM NrMTDConsumption SELECT latest(GigabytesIngested) @@ -73,6 +74,72 @@ A [interface de uso](/docs/accounts/accounts-billing/new-relic-one-pricing-billi +## Compute usage queries [#compute-queries] + +The [usage UI](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing#usage-ui) displays your compute usage over time. If you need more detail than the UI provides, you can use a variety of NRQL queries. The examples below include the following data types: + +* `NrConsumption`: use isso para se aprofundar nos detalhes de seu uso hora a hora. É menos útil como proxy para sua fatura. +* `NrMTDConsumption`: Use this to see an approximation of your monthly aggregated compute usage. +* `NrCustomerMTDConsumption`: Use this to see an approximation of a customer's monthly aggregated usage. + + + + This query totals your billable core compute usage, and displays a daily value for the past three months: + + ```sql + FROM NrConsumption SELECT sum(consumption) + WHERE metric = 'CoreCCU' + SINCE 3 months ago TIMESERIES 1 day + ``` + + + + This query totals your billable advanced compute usage, and displays a daily value for the past three months: + + ```sql + FROM NrConsumption SELECT sum(consumption) + WHERE metric = 'AdvancedCCU' + SINCE 3 months ago TIMESERIES 1 day + ``` + + + + This query totals your billable core compute usage, and displays a daily value for the past three months faceted by the capability: + + ```sql + FROM NrConsumption SELECT sum(consumption) + WHERE metric = 'CoreCCU' SINCE 3 months ago + FACET dimension_productCapability TIMESERIES 1 day + ``` + + + + This query totals your billable advanced compute usage, and displays a daily value for the past three months faceted by the capability: + + ```sql + FROM NrConsumption SELECT sum(consumption) + WHERE metric = 'AdvancedCCU' SINCE 3 months ago + FACET dimension_productCapability TIMESERIES 1 day + ``` + + + + This query shows the current full platform core compute usage. In other words, it shows how much you'd be billed for your data for that month if you were billed right now. Usage fee information is calculated hourly and takes approximately 3 hours to generate. If no values are displayed, please query data from 4 hours ago using "SINCE 4 hours ago." + + ```sql + FROM NrMTDConsumption select latest(consumption) where metric = 'CoreCCU' since 1 day ago + ``` + + + + This query shows the current full platform advanced compute usage. In other words, it shows how much you'd be billed for your data for that month if you were billed right now. Usage fee information is calculated hourly and takes approximately 3 hours to generate. If no values are displayed, please query data from 4 hours ago using "SINCE 4 hours ago." + + ```sql + FROM NrMTDConsumption select latest(consumption) where metric = 'AdvancedCCU' since 1 day ago + ``` + + + ## Ingestão de dados e limites de consulta [#data-limits] Para obter informações sobre limites de ingestão de dados e limites de consulta, consulte [Limites de dados do New Relic](/docs/data-apis/manage-data/view-system-limits). @@ -81,7 +148,7 @@ Para obter informações sobre limites de ingestão de dados e limites de consul Para ver sua contagem de usuários, consulte a [interface de uso](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing#usage-ui). Se precisar de mais detalhes do que isso, você pode usar o exemplo de consulta NRQL abaixo. Para obter detalhes sobre como usuário são calculados, consulte [Cálculos de usuários faturáveis](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/user-count-billing). -A maioria das organizações da New Relic tem a capacidade de adicionar usuários principais. Esta seção inclui consultas que funcionarão para essas organizações. Se você pertence a uma organização mais antiga que não [optou por desbloquear o usuário core](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing#core-acceptance), consulte [a consulta para organizações sem usuário core](#queries-non-core). +Most New Relic organizations have the ability to add core users. This section includes queries that will work for those organizations. If you're in an older organization that hasn't [opted in to unlock core users](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing#core-acceptance), see [Queries for organizations without core users](#queries-non-core). Aqui estão algumas regras para consultar seu usuário: @@ -336,7 +403,7 @@ Aqui estão alguns exemplos de NRQL condição do alerta.
- Esta consulta criará um alerta quando seu uso exceder o limite mensal fixo de GBs: + This query will create an alert when your usage exceeds a fixed monthly threshold for GBs: ```sql FROM NrMTDConsumption @@ -447,5 +514,5 @@ Para obter mais informações sobre como estimar o uso, consulte [nossa postagem Aqui estão alguns detalhes técnicos sobre como `bytecountestimate()` funciona: * Existem vários tipos de dados que [não contam para a ingestão](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing/#usage-calculation) , mas são retornados pela função `bytecountestimate()` . Isso significa que esta função às vezes mostra **more** dados que realmente são contabilizados para seu uso. Raramente poderá apresentar um valor inferior, mas, se o fizer, será apenas ligeiramente inferior. -* Alguns dados de telemetria relatados por uma entidade compartilham um atributo comum (por exemplo, um atributo sobre sua conta New Relic). Não contamos o atributo duplicado em sua ingestão, mas `bytecountestimate()` conta esses atributos. Às vezes, isso pode resultar em uma grande discrepância entre uma consulta `bytecountestimate()` e seu uso real. +* Some telemetry data reported from an entity shares common attributes (for example, attributes about your New Relic account). We don't count the duplicated attributes towards your ingest, but `bytecountestimate()` does count those attributes. This can sometimes result in a large discrepancy between a `bytecountestimate()` query and your actual usage. * Nossos , e relatam um tipo de dados conhecido como [métrica de fração de tempo data](/docs/data-apis/understand-data/new-relic-data-types/#timeslice-data). Esses dados não são armazenados no NRDB como nossos outros tipos de dados e, portanto, tentar usar `bytecountestimate()` nesses dados pode resultar em resultados confusos. Ao consultar esses dados, recomendamos facetar pelo nome do aplicativo e não pelo nome da métrica. \ No newline at end of file diff --git a/src/i18n/content/pt/docs/alerts/admin/rules-limits-alerts.mdx b/src/i18n/content/pt/docs/alerts/admin/rules-limits-alerts.mdx index 03b96fe4104..a36d743ecb1 100644 --- a/src/i18n/content/pt/docs/alerts/admin/rules-limits-alerts.mdx +++ b/src/i18n/content/pt/docs/alerts/admin/rules-limits-alerts.mdx @@ -345,6 +345,39 @@ N/A * Fora isso: 5k + + + + + + Email addresses per destination + + + + 1 email address + + + + * Free accounts: 5 email addresses per destination + * Paid accounts: 150 email addresses per destination + + + + + + + + Email addresses per organization per 24 hours + + + + N/A + + + + 1000 unique email addresses (applies to all users) + + 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 3e3f9308e53..76c589b425a 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 @@ -269,24 +269,24 @@ Após a instalação, o agente automaticamente instrumento com nosso catálogo d | --------------------------------- | ----------------------- | ----------------------- | -------------------------------------- | | `@apollo/gateway` | 2.3.0 | 2.11.2 | `@newrelic/apollo-server-plugin@1.0.0` | | `@apollo/server` | 4.0.0 | 5.0.0 | `@newrelic/apollo-server-plugin@2.1.0` | -| `@aws-sdk/client-bedrock-runtime` | 3.474.0 | 3.886.0 | 11.13.0 | -| `@aws-sdk/client-dynamodb` | 3.0.0 | 3.886.0 | 8.7.1 | -| `@aws-sdk/client-sns` | 3.0.0 | 3.886.0 | 8.7.1 | -| `@aws-sdk/client-sqs` | 3.0.0 | 3.886.0 | 8.7.1 | -| `@aws-sdk/lib-dynamodb` | 3.377.0 | 3.886.0 | 8.7.1 | +| `@aws-sdk/client-bedrock-runtime` | 3.474.0 | 3.894.0 | 11.13.0 | +| `@aws-sdk/client-dynamodb` | 3.0.0 | 3.894.0 | 8.7.1 | +| `@aws-sdk/client-sns` | 3.0.0 | 3.894.0 | 8.7.1 | +| `@aws-sdk/client-sqs` | 3.0.0 | 3.894.0 | 8.7.1 | +| `@aws-sdk/lib-dynamodb` | 3.377.0 | 3.894.0 | 8.7.1 | | `@aws-sdk/smithy-client` | 3.47.0 | 3.374.0 | 8.7.1 | | `@azure/functions` | 4.7.0 | 4.8.0 | 12.18.0 | | `@elastic/elasticsearch` | 7.16.0 | 9.1.1 | 11.9.0 | -| `@google/genai` | 1.1.0 | 1.19.0 | 12.21.0 | -| `@grpc/grpc-js` | 1.4.0 | 1.13.4 | 8.17.0 | +| `@google/genai` | 1.1.0 | 1.20.0 | 12.21.0 | +| `@grpc/grpc-js` | 1.4.0 | 1.14.0 | 8.17.0 | | `@hapi/hapi` | 20.1.2 | 21.4.3 | 9.0.0 | | `@koa/router` | 12.0.1 | 14.0.0 | 3.2.0 | -| `@langchain/core` | 0.1.17 | 0,3,75 | 11.13.0 | -| `@modelcontextprotocol/sdk` | 1.13.0 | 1.17.5 | 13.2.0 | +| `@langchain/core` | 0.1.17 | 0,3,77 | 11.13.0 | +| `@modelcontextprotocol/sdk` | 1.13.0 | 1.18.1 | 13.2.0 | | `@nestjs/cli` | 9.0.0 | 11.0.10 | 10.1.0 | | `@opensearch-project/opensearch` | 2.1.0 | 3.5.1 | 12.10.0 | -| `@prisma/client` | 5.0.0 | 6.16.0 | 11.0.0 | -| `@smithy/smithy-client` | 2.0.0 | 4.6.1 | 11.0.0 | +| `@prisma/client` | 5.0.0 | 6.16.2 | 11.0.0 | +| `@smithy/smithy-client` | 2.0.0 | 4.6.3 | 11.0.0 | | `amqplib` | 0.5.0 | 0,10,9 | 2.0.0 | | `aws-sdk` | 2.2.48 | 2.1692.0 | 6.2.0 | | `bluebird` | 2.0.0 | 3.7.2 | 1.27.0 | @@ -294,7 +294,7 @@ Após a instalação, o agente automaticamente instrumento com nosso catálogo d | `cassandra-driver` | 3.4.0 | 4.8.0 | 1.7.1 | | `connect` | 3.0.0 | 3.7.0 | 2.6.0 | | `express` | 4.15.0 | 5.1.0 | 2.6.0 | -| `fastify` | 3.0.0 | 5.6.0 | 8.5.0 | +| `fastify` | 3.0.0 | 5.6.1 | 8.5.0 | | `generic-pool` | 3.0.0 | 3.9.0 | 0.9.0 | | `ioredis` | 4.0.0 | 5.7.0 | 1.26.2 | | `kafkajs` | 2.0.0 | 2.2.4 | 11.19.0 | @@ -302,14 +302,14 @@ Após a instalação, o agente automaticamente instrumento com nosso catálogo d | `koa-route` | 3.0.0 | 4.0.1 | 3.2.0 | | `koa-router` | 12.0.1 | 14.0.0 | 3.2.0 | | `memcached` | 2.2.0 | 2.2.2 | 1.26.2 | -| `mongodb` | 4.1.4 | 6.19.0 | 1.32.0 | +| `mongodb` | 4.1.4 | 6.20.0 | 1.32.0 | | `mysql` | 2.16.0 | 2.18.1 | 1.32.0 | -| `mysql2` | 2.0.0 | 3.14.5 | 1.32.0 | -| `next` | 13.4.19 | 15.5.2 | 12.0.0 | -| `openai` | 4.0.0 | 5.20.1 | 11.13.0 | +| `mysql2` | 2.0.0 | 3.15.0 | 1.32.0 | +| `next` | 13.4.19 | 15.5.3 | 12.0.0 | +| `openai` | 4.0.0 | 5.22.0 | 11.13.0 | | `pg` | 8.2.0 | 8.16.3 | 9.0.0 | | `pg-native` | 3.0.0 | 3.5.2 | 9.0.0 | -| `pino` | 8.0.0 | 9.9.5 | 8.11.0 | +| `pino` | 8.0.0 | 9.11.0 | 8.11.0 | | `q` | 1.3.0 | 1.5.1 | 1.26.2 | | `redis` | 3.1.0 | 5.8.2 | 1.31.0 | | `restify` | 11.0.0 | 11.1.0 | 2.6.0 | diff --git a/src/i18n/content/pt/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation.mdx b/src/i18n/content/pt/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation.mdx new file mode 100644 index 00000000000..f6b4ed7fdbd --- /dev/null +++ b/src/i18n/content/pt/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation.mdx @@ -0,0 +1,70 @@ +--- +title: Integrar via CloudFormation e CloudWatch Metric Streams +tags: + - Integration via CloudFormation + - AWS metric integration + - Amazon integrations + - AWS integrations + - Integration with CloudWatch Metric Streams via CloudFormation +metaDescription: Integrate New Relic with AWS services using CloudFormation templates to automate the setup of CloudWatch Metric Streams for metrics ingestion. +freshnessValidatedDate: never +translationType: machine +--- + +Para uma integração perfeita da sua conta da AWS com o New Relic, este é o processo de integração mais recomendado. Você pode utilizar API Polling para serviços não suportados pelo CloudWatch Metric Streams. + +## Pré-requisitos [#prerequisites] + +Antes de começar a integrar sua conta da AWS com o New Relic, certifique-se de atender aos seguintes pré-requisitos: + +* **Uma [chave de licença](https://one.newrelic.com/api-keys)do New Relic**: você precisará de uma chave de licença para conectar seus serviços da AWS à sua conta do New Relic. +* **[Permissões](https://docs.aws.amazon.com/ARG/latest/userguide/gettingstarted-prereqs-permissions.html)** para implantar novos recursos da AWS e **[funções do IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html)**: você precisará dessa permissão para sua conta da AWS. +* **[Permissões](/docs/accounts/accounts-billing/new-relic-one-user-management/user-permissions/#infrastructure)** para integração na nuvem: Você precisará dessas permissões para sua conta New Relic. + +## Etapas de integração [#integration-steps] + +Para integrar sua conta da AWS com o New Relic usando o CloudFormation e o CloudWatch Metric Streams, siga estas etapas: + +1. Navegue até [**Infrastructure > AWS**](https://one.newrelic.com/infra/infrastructure/cloud-aws). + +2. Selecione a conta correta. + +3. Clique em **Set up integration**. + +4. Siga as instruções em cada tela e preencha os campos que se aplicam a você. Para esta integração, escolha as seguintes opções nas telas fornecidas: + + 1. **Choose Data type(s)**: Metrics + 2. **Choose a setup method**: Automate AWS with CloudFormation (Recommended) + 3. **Choose a metrics integration type**: CloudWatch Metric Stream (Recommended) + +5. Se você estiver usando algum dos serviços que não são suportados no CloudWatch Metric Streams, na página **Choose a metrics integration type**, selecione **Yes** na terceira etapa para pesquisa API e continue. + + AWS Integration with CWMS and API Polling + +
+ CWMS integração de serviços da AWS com sondagem API selecionada para serviços não suportados. +
+ + Faça a configuração necessária conforme orientado na página **Enable API Polling (optional)** e continue. + +6. Auto-discovery detecta e visualiza automaticamente os relacionamentos entre suas entidades AWS em mapas e aproveita algumas outras flexibilidades. Para mais detalhes, consulte [Descoberta automática de entidade AWS ](/docs/infrastructure/amazon-integrations/connect/set-up-auto-discovery-of-aws-entities/). Se você quiser esse recurso, ative-o na página **Enable Auto Discovery (optional)** e continue. + +7. Clique em **Launch your CloudFormation in AWS**. O modelo do CloudFormation é aberto no seu console AWS com o parâmetro configurado com base nas suas seleções no New Relic, portanto, nenhuma edição adicional é necessária, a menos que você queira fazer alterações. + +8. Cole sua chave de licença no console da AWS. + +9. Para implantar a stack Cloudformation, no console AWS, selecione **Create stack**. A criação dos recursos stack pode levar vários minutos e pode gerar múltiplas pilhas, dependendo de como você configura o encaminhamento métrico. Se a criação stack falhar, consulte o [procedimento de resolução de problemas](https://docs.newrelic.com/docs/logs/troubleshooting/aws-log-integration-issues/stack-creation-fails/). + +10. Após a criação bem-sucedida stack, mude para a plataforma New Relic e continue com a integração guiada até ver seus dados AWS no New Relic. + +## Tópicos relacionados [#related-topics] + + + + Aprenda a coletar dados de várias contas da AWS. + + + + Explore e use o métrica do CloudWatch Metric Streams. + + \ No newline at end of file diff --git a/src/i18n/content/pt/docs/infrastructure/other-infrastructure-integrations/stripe-integration.mdx b/src/i18n/content/pt/docs/infrastructure/other-infrastructure-integrations/stripe-integration.mdx index 62a336c438b..d50cb78af1e 100644 --- a/src/i18n/content/pt/docs/infrastructure/other-infrastructure-integrations/stripe-integration.mdx +++ b/src/i18n/content/pt/docs/infrastructure/other-infrastructure-integrations/stripe-integration.mdx @@ -102,7 +102,7 @@ WHERE metricName = 'stripe_metrics' ### Instale nosso dashboard de monitoramento Stripe [#add-dashboard] -Para configurar nosso dashboard Stripe pré-construído para monitor seu aplicativo métrica, acesse a [instalação dashboard Stripe](https://onenr.io/0ZQWYYE1rRW) e siga as instruções. Depois de instalado, o dashboard deverá exibir métricas. +Para configurar nosso dashboard Stripe pré-criado para monitorar seu aplicativo métrico, acesse a [instalação do dashboard Stripe ](https://onenr.io/0BQrXaNgnRZ)e siga as instruções. Uma vez instalado, o dashboard deve exibir métrica. Se precisar de ajuda com o painel, consulte: diff --git a/src/i18n/content/pt/docs/new-relic-solutions/solve-common-issues/find-help-get-support.mdx b/src/i18n/content/pt/docs/new-relic-solutions/solve-common-issues/find-help-get-support.mdx index 472c7cff9bd..8aadf7ce65d 100644 --- a/src/i18n/content/pt/docs/new-relic-solutions/solve-common-issues/find-help-get-support.mdx +++ b/src/i18n/content/pt/docs/new-relic-solutions/solve-common-issues/find-help-get-support.mdx @@ -29,9 +29,9 @@ A visualização do suporte no produto fornece visibilidade sobre o que há de n In-product support -## Pergunte no Explorers Hub, nosso fórum de suporte gratuito [#nr-forum] +## Pergunte em nosso fórum de suporte gratuito [#nr-forum] -[O Explorers Hub da New Relic](https://discuss.newrelic.com/) é nosso fórum gratuito para todos os usuários. Usuário e funcionário da New Relic conversam diariamente para solucionar problemas, encontrar soluções alternativas e discutir novos recursos. +[O fórum de suporte doNew Relic](https://discuss.newrelic.com/) é nosso fórum gratuito para todos os usuários. Usuários e funcionários New Relic conversam diariamente para solucionar problemas, encontrar soluções alternativas e discutir novos recursos. ## Execute a ferramenta New Relic Diagnostics [#diagnostics] diff --git a/src/i18n/content/pt/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx b/src/i18n/content/pt/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx index 56c9921775b..b3cb7a2a380 100644 --- a/src/i18n/content/pt/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx +++ b/src/i18n/content/pt/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx @@ -346,15 +346,24 @@ Aqui estão alguns tipos diferentes de implementações de variáveis de modelo. - Você pode ativar a opção de vários valores na seção de opções de exibição ao criar uma variável do tipo `NRQL/ENUM`. + You can enable the multi-value option to allow users to select multiple values from a dropdown instead of just one. This is useful when you want to filter data across multiple criteria simultaneously. - Aqui está um exemplo de consulta que cria uma variável chamada `{{MultiValue}}` e retorna uma lista de todos os eventIds exclusivos: + Multi-value is available for Query and List variable types. Text field variables don't support the multi-value option. + + To enable multi-value: + + 1. When creating a Query or List template variable, select the **Multi-value** option. + 2. In your widget queries, use the `IN` operator instead of `=` to handle multiple selected values. + + /* You can enable the multi-value option from the display options section when creating a variable of type `NRQL/ENUM`. */ + + Here's an example where you'd name your variable `{{MultiValue}}` and use this query to populate its values: ```sql SELECT uniques(eventId) FROM AjaxRequest ``` - Multi-value template variable example + /* <img width="30%;" title="Multi-value template variable example" alt="Multi-value template variable example" src="/images/dashboards_screenshot-crop_add-multivalue.webp" /> */ Então você criaria um widget com a seguinte consulta: @@ -362,22 +371,36 @@ Aqui estão alguns tipos diferentes de implementações de variáveis de modelo. SELECT count(*) FROM AjaxRequest WHERE eventId IN ({{MultiValue}}) ``` - Creating a widget + /* <img width="80%;" title="Creating a widget" alt="Creating a widget" src="/images/dashboards_screenshot-full_multivalue-add-widget.webp" /> */ - Você pode definir apenas uma variável de modelo por vez, mas pode usar mais de uma variável de modelo em um único widget. + While you can only define one template variable at a time, you can reference multiple variables within the same widget. + + For this example, you need to have the two variables set up: + + 1. `countryCode` variable: Use the query shown earlier in this document: + + ```sql + SELECT uniques(countryCode) FROM PageAction SINCE 2 days ago + ``` + + 2. `city` variable with a similar query: + + ```sql + SELECT uniques(city) FROM PageView SINCE 1 week ago + ``` - Aqui está um exemplo de consulta que usa duas variáveis de modelo. Observe que isso pressupõe que as variáveis de modelo `countryCode` e `city` já tenham sido criadas e que tenham um único valor. + Here's an example using the above template variables with single values to create the widget: ```sql SELECT countryCode, city FROM PageAction WHERE countryCode = {{countryCode}} AND city = {{city}} ``` - Creating a widget using multiple variables + /* <img title="Creating a widget using multiple variables" alt="Creating a widget using multiple variables" src="/images/dashboards_screenshot-crop_add-widget-multiple-variable.webp" /> */ - Se você tiver vários valores para suas variáveis, como `Chicago`, `New York`, `Paris` para sua variável `city` , será necessário usar `IN`: + If your variables support multiple values (such as `Chicago`, `New York`, `Paris` for your `city` variable), you need to use `IN`: ```sql SELECT countryCode, city FROM PageAction @@ -398,7 +421,7 @@ Aqui estão alguns tipos diferentes de implementações de variáveis de modelo. SELECT uniques(aparse(platformVersion, 'release-*')) FROM PageView ``` - Creating the release version variable + /* <img width="40%;" title="Creating the release version variable" alt="Creating the release version variable" src="/images/dashboards_screenshot-crop_add-var-release-version.webp" /> */ Em seguida, crie um widget com a seguinte consulta: @@ -407,7 +430,7 @@ Aqui estão alguns tipos diferentes de implementações de variáveis de modelo. WHERE aparse(platformVersion, 'release-*') IN ({{releaseversion}}) FACET platformVersion ``` - Creating the widget + /* <img title="Creating the widget" alt="Creating the widget" src="/images/dashboards_screenshot-crop_add-widget-aparse.webp" /> */ Ou se preferir, você pode usar o comando [`capture`](/docs/query-your-data/nrql-new-relic-query-language/get-started/nrql-syntax-clauses-functions/#func-capture) : @@ -416,15 +439,20 @@ Aqui estão alguns tipos diferentes de implementações de variáveis de modelo. WHERE capture(platformVersion, r'release-(?P\d+)') IN ({{releaseversion}}) FACET platformVersion ``` - Creating the widget + /* <img title="Creating the widget" alt="Creating the widget" src="/images/dashboards_screenshot-crop_add-widget-capture.webp" /> */ Você pode usar `LIKE` e `RLIKE` como variáveis de modelo para filtrar dados em um dashboard. Para usar esse recurso, o valor adicionado ao criar a variável de modelo deve usar os símbolos curinga `%` no início e no final do valor. - Aqui está um exemplo. Você define uma variável de string, conforme mostrado aqui: + Here's an example. You define a string template variable with the following values: + + * **Name to use in queries:** line\_filter + * **Tipo:** `Text field` + * **Default value:** %@%.com + * **Output format:** `String` - Add `LIKE` as template variable + /* <img width="40%;" title="Add `LIKE` as template variable" alt="Add `LIKE` as template variable" src="/images/dashboards_screenshot-crop_add-var-like-filter.webp" /> */ Você pode então criar um gráfico de widget e usar sua variável assim: @@ -432,7 +460,7 @@ Aqui estão alguns tipos diferentes de implementações de variáveis de modelo. FROM NrdbQuery SELECT user WHERE user LIKE {{like_filter}} ``` - Add `LIKE` as template variable + /* <img title="Add `LIKE` as template variable" alt="Add `LIKE` as template variable" src="/images/dashboards_screenshot-crop_add-widget-like-filter.webp" /> */ ou assim: @@ -450,13 +478,13 @@ Aqui estão alguns tipos diferentes de implementações de variáveis de modelo. > Você pode criar uma variável do tipo NRQL com um formato de saída de string e usá-la após uma cláusula `FACET` para agrupar por valores diferentes. - Por exemplo, você pode criar uma variável chamada `{{userAgentName}}` com a seguinte aparência: + For example, you might create a template variable named `{{userAgentName}}` that would look like: ```sql SELECT uniques(userAgentName) FROM PageAction ``` - Creating the variable + /* <img width="30%;" title="Creating the variable" alt="Creating the variable" src="/images/dashboards_screenshot-crop_add-var-facet.webp" /> */ Então você criaria um widget com a seguinte consulta: @@ -465,15 +493,20 @@ Aqui estão alguns tipos diferentes de implementações de variáveis de modelo. WHERE userAgentName={{userAgentName}} FACET userAgentName ``` - Creating widget using facet + /* <img title="Creating widget using facet" alt="Creating widget using facet" src="/images/dashboards_screenshot-crop_add-widget-facet.webp" /> */ Você pode criar uma variável com formato de saída `identifier` e usá-la após uma cláusula `FACET` para agrupar por valores diferentes. - Por exemplo, você pode criar uma variável `{{location}}` do tipo lista com dois valores possíveis: `countryCode` e `city`. Você definiria o formato de saída como `identifier`. + For example, you might create a `{{location}}` variable: - Adding the variable for dynamic grouping + * **Name to use in queries:** location + * **Tipo:** `List` + * **Values separated by commas:** `countryCode` and `city` + * **Output format:** `Identifier` + + /* <img width="40%;" title="Adding the variable for dynamic grouping" alt="Adding the variable for dynamic grouping" src="/images/dashboards_screenshot-crop_add-var-dynamic-grouping.webp" /> */ Então você criaria um widget com a seguinte consulta: @@ -481,15 +514,20 @@ Aqui estão alguns tipos diferentes de implementações de variáveis de modelo. SELECT count(*) FROM PageAction FACET {{location}} ``` - Adding the widget for dynamic grouping + /* <img title="Adding the widget for dynamic grouping" alt="Adding the widget for dynamic grouping" src="/images/dashboards_screenshot-crop_add-widget-dynamic-grouping.webp" /> */ Você pode criar uma variável com formato de saída `number` e usá-la dentro de uma função percentil. - Por exemplo, você poderia criar uma variável `{{percentile}}` do tipo `list` com dois valores possíveis: `55` e `90`. Você deseja definir o formato de saída como `number`. + For example, you could create a `{{percentile}}` variable: + + * **Name to use in queries:** percentile + * **Tipo:** `List` + * **Values separated by commas:** `55` and `90` + * **Output format:** `Number` - Adding the variable for dynamically change the percentile + /* <img width="40%;" title="Adding the variable for dynamically change the percentile" alt="Adding the variable for dynamically change the percentile" src="/images/dashboards_screenshot-crop_add-var-dynamic-percentile.webp" /> */ Então você criaria um widget com a seguinte consulta: @@ -497,7 +535,7 @@ Aqui estão alguns tipos diferentes de implementações de variáveis de modelo. SELECT percentile(duration, {{percentile}}) FROM PageAction ``` - Adding the widget for dynamically change the percentile + /* <img title="Adding the widget for dynamically change the percentile" alt="Adding the widget for dynamically change the percentile" src="/images/dashboards_screenshot-crop_add-widget-dynamic-percentile.webp" /> */ @@ -508,7 +546,7 @@ Aqui estão alguns tipos diferentes de implementações de variáveis de modelo. WHERE countryCode IN ({{countryCode}}) ``` - Use variables to filter + /* <img title="Use variables to filter" alt="Use variables to filter" src="/images/dashboards_screenshot-crop_variables-to-filter.webp" /> */ @@ -528,7 +566,7 @@ Aqui estão alguns tipos diferentes de implementações de variáveis de modelo. Isso resulta nos valores dos últimos 30 minutos. Quando você define o valor do seletor de hora como **Default** e sua consulta tem uma cláusula `SINCE` , o valor mais recente será usado para executar a consulta. - A screenshot showing the variable form + /* <img title="Example form" alt="A screenshot showing the variable form" src="/images/dashboards_screenshot-crop_example-form.webp" /> */ + Recomendamos atualizar para a versão mais recente do agente assim que estiver disponível. Se sua organização tiver estabelecido práticas que impedem a atualização para a versão mais recente, certifique-se de que seu agente seja atualizado regularmente para uma versão que tenha no máximo 90 dias. Saiba mais sobre [como manter seu agente atualizado](https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/). + + +## 3.41.0 + +### Adicionado + +* Adicionadas `DistributedTracer.Sampler` opções de configuração para controlar o comportamento de amostragem para solicitações de entrada para rastreamento distribuído + + * Para configurar o amostrador, foram adicionados `ConfigRemoteParentSampled(flag RemoteParentSamplingConfig)` e `ConfigRemoteParentNotSampled(flag RemoteParentSamplingConfig)`, que manipulam o comportamento de amostragem com base no que o pai remoto sinalizou. + * Os sinalizadores adicionados são `"always_on", "always_off", and "default"` que podem ser chamados usando `RemoteParentSamplingConfig` + * `Example: newrelic.ConfigRemoteParentSampled(newrelic.AlwaysOff)` + +* Testes de monitoramento OOM adicionados + +* Maior cobertura de teste de agente seguro + +### Fixo + +* Versões atualizadas de bibliotecas de terceiros devido a problemas de segurança ou outros problemas de suporte: + + * `github.com/gofiber/fiber/v2` de 2.52.7 a 2.52.9 na integração `nrfiber` + * `golang.org/x/net` de 0,25,0 a 0,38,0 na integração `nrconnect` + +### Declaração de apoio + +Usamos a versão mais recente da linguagem Go. No mínimo, você não deve usar nenhuma versão do Go mais antiga do que aquela suportada pela própria equipe do Go. Consulte a [Política de EOL do agente Go](https://docs.newrelic.com/docs/apm/agents/go-agent/get-started/go-agent-eol-policy/) para obter detalhes sobre versões com suporte do agente Go e componentes de terceiros. \ No newline at end of file diff --git a/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-8-01-2025.mdx b/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-8-01-2025.mdx new file mode 100644 index 00000000000..465d315090e --- /dev/null +++ b/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-8-01-2025.mdx @@ -0,0 +1,99 @@ +--- +subject: Docs +releaseDate: '2025-08-01' +version: 'July 25 - August 01, 2025' +translationType: machine +--- + +### Novos documentos + +* Adicionadas [documentações de orçamentos de computador](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/compute-budgets/overview) para fornecer um mecanismo para monitorar e alertar sobre o uso da unidade de consumo (CCU) do seu computador. + +### Grandes mudanças + +* [Compatibilidade e requisitos](/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent) atualizados para o agente Node.js. + +* [Compatibilidade e requisitos atualizados para o Alpine Linux](/docs/apm/agents/php-agent/getting-started/php-agent-compatibility-requirements) para o agente PHP. + +* Atualizados os requisitos específicos do agente para [Controle de Pipeline](/docs/new-relic-control/pipeline-control/modify-agent-configuration). + +* Atualizou o JFR relacionado aos requisitos de configuração para [o agente Java](/docs/apm/agents/java-agent/configuration/java-agent-configuration-config-file#jfr-harvest-interval). + +* Atualizadas as informações de preços e cobrança do New Relic em: + + * [Dados: Faturamento e regras](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing) + * [Consultas e alertas relacionados a uso](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts) + * [Plano de uso do New Relic](/docs/licenses/license-information/usage-plans/new-relic-usage-plan) + +### Pequenas mudanças + +* Esclareceu a linguagem no .NET agente para capturar o parâmetro SQL no [.NET compatível com o agente e o documento de requisitos](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements). +* Aprimorou a linguagem no [Oracle banco de dados monitoramento integração](/docs/infrastructure/host-integrations/host-integrations-list/oracle-database-monitoring-integration). + +### Notas de versão + +* Confira nossas postagens de Novidades: + + * [Orçamentos de computadores agora disponíveis para o público em geral](/whats-new/2025/07/whats-new-7-30-compute-budgets). + * [Aumentando a experiência do usuário: aproveitando Session Replay para otimização vital da Web](/whats-new/2025/07/whats-new-7-31-augmenting-user-experiences-browser). + +* Fique por dentro dos nossos últimos lançamentos: + + * [AgenteAndroid v7.6.8](/docs/release-notes/mobile-release-notes/android-release-notes/android-768): + + * Corrigido um problema em que o rastreamento stack para erros do Unity não era exibido corretamente. + * Corrigido um problema que impedia que o resumo métrico fosse gravado quando o aplicativo retornava ao primeiro plano após seu lançamento inicial. + * Corrigido um problema em que JSON inválido em entradas de log poderia causar erros. + + * [CLI de diagnóstico (nrdiag) v3.4.0](/docs/release-notes/diagnostics-release-notes/diagnostics-cli-release-notes/diagnostics-cli-341): + * Adicionado `K8s/AgentControl/agent-control-install-job-logs` para coletar logs gerados pela instalação do controle do agente. + + * [Gerenciador de tarefas v451](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-451): + + * Vulnerabilidades corrigidas relacionadas ao `common-lang3` Java e Ubuntu para resolver problemas de segurança no SJM. + * Implementou alterações na migração da fila do processador relacionadas à migração da nossa arquitetura de serviço interna. + * Corrigido um problema para incluir detalhes completos da exceção para fornecer melhor contexto para resolução de problemas em logs do SJM. + + * [Aplicativo móvel para Android v5.30.1](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5301): + * Melhorou a experiência de login. + + * [Aplicativo móvel para iOS v7.5.8](/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-758): + + * Criei o agente usando o Xcode 16.4. + * Corrigido um problema que poderia fazer com que distributed tracing não tivesse todas as informações de conta necessárias no início de uma sessão. + * Corrigido um problema que poderia causar uma falha na inicialização do agente. + + * [Tempo de execução da API do Node](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.122): + * Corrigidas as vulnerabilidades de dados de formulário e as vulnerabilidades subjacentes do Ubuntu para lidar com vulnerabilidades de segurança em tempos de execução API do Node. + + * [Node browser runtime](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.39): + * Corrigidas as vulnerabilidades de dados de formulário e as vulnerabilidades subjacentes do Ubuntu para lidar com vulnerabilidades de segurança em tempos de execução do Node Browser. + + * [Tempo de execução do ping](/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.53.0): + * Vulnerabilidades corrigidas relacionadas ao `common-lang3` Java e Ubuntu para resolver problemas de segurança no tempo de execução do Ping. + + * [Agente Python v10.15.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-101500): + + * Adicionado suporte para [`oracledb`](https://pypi.org/project/oracledb/) + * Corrigido um bug na instrumentação `MessageBroker` onde os métodos de serialização estavam procurando o atributo `destination_name` no `MessageTransaction` e ele não existia. + * Corrigiu o problema de metadados de utilização da AWS ao executar AWS e K8s juntos. + + * [AgenteRuby v9.20.0](/docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-20-0): + + * Adicionado suporte para registrar o ID do Docker ao executar no ambiente AWS ECS Fargate. + * Adicionado um novo método auxiliar para simplificar a comparação de versões. + * Adicionado o atributo `code.stacktrace` aos intervalos de armazenamento de dados quando a duração excede o limite configurado. + * Links de origem corrigidos `Brewfile`. + * Corrigido um erro que ocorre ao usar `HTTPX 1.5.0` para armazenar resposta. + * Melhorou as informações registradas no nível de depuração pelo agente quando o agente lê uma fonte de configuração. + + * [Agente Unity v1.4.8](/docs/release-notes/mobile-release-notes/unity-release-notes/unity-agent-148): + + * O agente Android nativo foi atualizado para a versão 7.6.7. + * O agente nativo do iOS foi atualizado para a versão 7.5.6. + + * [Agente Unity v1.4.9](/docs/release-notes/mobile-release-notes/unity-release-notes/unity-agent-149): + + * O agente Android nativo foi atualizado para a versão 7.6.8. + * O agente nativo do iOS foi atualizado para a versão 7.5.8. + * Problema de rastreamento stack de exceção do Unity corrigido quando namespace é usado. \ No newline at end of file diff --git a/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx b/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx new file mode 100644 index 00000000000..56fc49bcdf6 --- /dev/null +++ b/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx @@ -0,0 +1,60 @@ +--- +subject: Docs +releaseDate: '2025-08-08' +version: 'August 01 - August 07, 2025' +translationType: machine +--- + +### Novos documentos + +* Adicionado [tutorial do NerdGraph: Criar função personalizada para equipes](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/compute-budgets/overview) para orientar você no uso da API NerdGraph do New Relic para criar e gerenciar funções personalizadas para equipes. + +### Pequenas mudanças + +* Alterado o [limite de eventos de alerta por condição](/docs/alerts/admin/rules-limits-alerts) para 1k por minuto. +* Atualizadas as últimas [versões e requisitos compatíveis do agente .Net](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements) verificados. +* Atualizadas as informações de versão e suporte de versão sobre o service broker para [VMware Tanzu](/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-service-broker-integration). +* Atualizadas as informações de suporte de versão sobre o pacote de integração New Relic NGINX para [VMware Tanzu](/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-nginx-buildpack-integration). +* Atualizadas as informações de versão e suporte de versão sobre o New Relic Nozzle para [VMware Tanzu](/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-firehose-nozzle-integration/#product-snapshot). + +### Notas de versão + +* Confira nossas postagens de Novidades: + + * [Errors Inbox agora está integrada à carga de trabalho](/whats-new/2025/08/whats-new-08-06-workloads-errors-inbox). + +* Fique por dentro dos nossos últimos lançamentos: + + * [Gerenciador de tarefas v452](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-452): + * Melhorias internas adicionadas para tratamento de exceções no processamento de mensagens da fila. + + * [IntegraçãoKubernetes v3.43.3](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-43-3): + * Adicionou um gráfico Helm para implantar a solução de monitoramento Kubernetes da New Relic. + + * [Controle de Pipeline Gateway v1.1.0](/docs/release-notes/pipeline-control-gateway-release-notes/pipeline-control-gateway-25-08-05): + + * Implementou uma nova funcionalidade para descartar seletivamente dados e atributos dos eventos `SqlTrace` e `TransactionTrace` usando regras de descarte. + + * Foram corrigidas vulnerabilidades no pacote `golang.org/x/net`, incluindo um problema de script entre sites e um desvio de proxy HTTP relacionado a IDs de zona IPv6. + + * Atualizado para Go `1.24` e as seguintes dependências foram atualizadas para aumentar a segurança e incorporar correções recentes: + + * `golang.org/x/net to v0.38.0` + * `golang.org/x/sys to v0.31.0` + * `golang.org/x/text to v0.23.0` + + * [Aplicativo móvel para iOS v6.9.11](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6101): + * Reduziu o fluxo de login em duas etapas, armazenando o domínio de autenticação do usuário e redirecionando-o diretamente para sua página de login. + + * [AgenteFlutter v1.1.13](/docs/release-notes/mobile-release-notes/flutter-release-notes/flutter-agent-1113): + + * Agente Android nativo aprimorado e atualizado para a versão 7.6.8 + * Agente iOS nativo aprimorado atualizado para a versão 7.5.8 + + * [Agente .NET MAUI v1.1.11](/docs/release-notes/mobile-release-notes/net-maui-release-notes/net-maui-agent-1111) + + * Agente Android nativo aprimorado e atualizado para a versão 7.6.8 + * Agente iOS nativo aprimorado atualizado para a versão 7.5.8 + + * [agente de infraestrutura v1.65.5](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1655): + * Alterado o suporte para montagens AWS efs em amostras de armazenamento \ No newline at end of file diff --git a/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-8-14-2025.mdx b/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-8-14-2025.mdx new file mode 100644 index 00000000000..1ca88ca0ec1 --- /dev/null +++ b/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-8-14-2025.mdx @@ -0,0 +1,112 @@ +--- +subject: Docs +releaseDate: '2025-08-15' +version: 'August 08 - August 14, 2025' +translationType: machine +--- + +### Novos documentos + +* Adicionado [suporte para funções NRQL em regras de gateway](/docs/new-relic-control/pipeline-control/nrql-functions) para delinear as funções NRQL suportadas nas regras de gateway do Controle de Pipeline . +* Adicionadas etapas de resolução de problemas para resolver [eventos de reinicialização frequente de Fluent Bit](/docs/infrastructure/infrastructure-troubleshooting/troubleshoot-infrastructure/frequent-fluent-bit-restart-events) ajustando as configurações de resolução de nome do host na configuração do agente do New Relic Infrastructure. + +### Grandes mudanças + +* [Plano de uso](/docs/licenses/license-information/usage-plans/new-relic-usage-plan/#list-price) atualizado com as informações de preços mais recentes. +* **Errors Inbox** adicionada à [interface de carga de trabalho](/docs/new-relic-solutions/new-relic-one/workloads/use-workloads/#errors). +* Adicionada desativação seletiva do agente com base na classe principal de inicialização ou no jar executável por meio de variáveis de ambiente, juntamente com configurações de segurança aprimoradas para [configuração do agente Java](/docs/apm/agents/java-agent/configuration/java-agent-configuration-config-file/#skip-applications). +* Adicionado suporte para [configuração de repositório privado](/docs/new-relic-control/agent-control/configuration/#private-repository-configuration) no Controle de Agente, possibilitando a implantação de agente gerenciado com autenticação via métodos de certificado básico ou TLS. +* Adicionado suporte para [Gerenciamento de Segredos](/docs/new-relic-control/agent-control/configuration/#secrets-management) no Agente de Controle, para gerenciar dados confidenciais, como senhas e chaves de API, recuperando-os de um provedor de segredos dedicado. + +### Pequenas mudanças + +* Adicionadas restrições de tag de entidade para a cláusula `WHERE` em [Drop data usando regras cloud do Controle de Pipeline ](/docs/new-relic-control/pipeline-control/cloud-rules-api/#restrictions). +* Adicionadas [práticas recomendadas para otimizar o conteúdo da sua fonte de conhecimento](/docs/agentic-ai/knowledge-integration/overview/#configure) para o conector New Relic AI Knowledge. + +### Notas de versão + +* Confira nossas postagens de Novidades: + + * [O modo de alta precisão UniqueCount e o suporte de argumentos aumentado agora estão disponíveis para o público em geral](/whats-new/2025/08/whats-new-8-13-high-precision-uniquecount). + +* Fique por dentro dos nossos últimos lançamentos: + + * [Cordova agente v7.0.8](/docs/release-notes/mobile-release-notes/cordova-release-notes/cordova-agent-708/): + + * Atualizar o agente Android nativo para a versão 7.6.8 + * Atualizar o agente iOS nativo para a versão 7.5.8 + + * [Cordova agente v7.0.9](/docs/release-notes/mobile-release-notes/cordova-release-notes/cordova-agent-709/): + + * Atualizar o agente Android nativo para a versão 7.6.6 + * Atualizar o agente iOS nativo para a versão 7.5.5 + + * [Capacitor agente v1.5.8](/docs/release-notes/mobile-release-notes/capacitor-release-notes/capacitor-agent-158/): + + * Atualizar o agente Android nativo para a versão 7.6.6 + * Atualizar o agente iOS nativo para a versão 7.5.5 + + * [Capacitor agente v1.5.9](/docs/release-notes/mobile-release-notes/capacitor-release-notes/capacitor-agent-159/): + * Corrigida a falha do sinal de aborto + + * [Capacitor agente v1.5.10](/docs/release-notes/mobile-release-notes/capacitor-release-notes/capacitor-agent-1510/): + + * Atualizar o agente Android nativo para a versão 7.6.8 + * Atualizar o agente iOS nativo para a versão 7.5.8 + + * [CLI de diagnóstico (nrdiag) v3.5.0](/docs/release-notes/diagnostics-release-notes/diagnostics-cli-release-notes/diagnostics-cli-350/): + * atualizou a verificação de compatibilidade da versão `Java/Appserver/JbossEapCheck` + + * [.NET agente v10.44.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-44-0/): + + * Amostradores de métricas de desempenho habilitados no modo Serverless + * Processo de host da Web do Azure Function (Linux) excluído da instrumentação. + + * [NRDOT v1.3.0](/docs/release-notes/nrdot-release-notes/nrdot-2025-08-13/): + + * Versões do componente hotel aumentadas de v0.128.0 para v0.131.0 + * Introdução da distribuição do núcleo nrdot + + * [Agente Node.js v13.1.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-1-0/): + + * Adicionado suporte para API de logs OTEL + * Adicionada a capacidade de suporte métrico quando a instrumentação foi desabilitada para um pacote + * Instrumentação de temporizadores desabilitados por padrão no exemplo de configuração + * Ofuscação `transaction.url` fixa + + * [Gerenciador de tarefas v454](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-454/): + * Corrigidas as vulnerabilidades subjacentes do Ubuntu para abordar vulnerabilidades de segurança no SJM. + + * [Tempo de execução da API do Node v1.2.124](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.124/): + * Corrigidas as vulnerabilidades subjacentes do Ubuntu para lidar com vulnerabilidades de segurança nos tempos de execução da API do Node. + + * [Runtime do navegador Node v3.0.41](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.41/): + * Corrigidas as vulnerabilidades do tmp `CVE-2025-54798` e as vulnerabilidades subjacentes do Ubuntu para abordar vulnerabilidades de segurança nos tempos de execução do Node Browser . + + * [Tempo de execução do Ping v1.54.0](/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.54.0/): + * Vulnerabilidades corrigidas relacionadas ao Ubuntu para resolver problemas de segurança no tempo de execução do Ping. + + * [Agente Java v8.23.0](/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8230/): + + * Atualizado para oferecer suporte à v24 do graphql. + * Adicionada instrumentação lettuce 6.5. + * Versão commons-lang elevada para 3.18.0 + + * [AWS Lambda direcionador de logs v1.1.1](/docs/release-notes/aws-lambda-log-forwarder-release-notes/lambda-25-07-25/): + * Postura de segurança aprimorada com a atualização da versão Go para 1.24.4 nos sistemas. + + * [Agente PHP v12.0.0.25](/docs/release-notes/agent-release-notes/php-release-notes/php-agent-12-0-0-25/): + + * Melhoria no logging de erros do mapa de hooks do Drupal. + * Problemas corrigidos de detecção de pacotes legados para Security RX. + + * [agente de infraestrutura v1.66.1](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1661/): + * Suporte revertido para montagens do AWS EFS em amostras de armazenamento. + + * [Aplicativo móvel para Android v5.30.6](docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5306/): + * Suporte aprimorado de senha para logins SAML e sociais. + + * [Agente Browser v1.295.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.0/): + + * Adicionada detecção de causa de erro. + * Adicionados avisos de monkey-patching. \ No newline at end of file diff --git a/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-8-21-2025.mdx b/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-8-21-2025.mdx new file mode 100644 index 00000000000..bb5951d3f88 --- /dev/null +++ b/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-8-21-2025.mdx @@ -0,0 +1,56 @@ +--- +subject: Docs +releaseDate: '2025-08-22' +version: 'August 15 - August 21, 2025' +translationType: machine +--- + +### Grandes mudanças + +* Relatório de compatibilidade [do agente Node.js](/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent/) atualizado. +* [Agente .NET](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements/) atualizado com as últimas versões de bibliotecas compatíveis verificadas. + +### Pequenas mudanças + +* Atualizou o sistema operacional [Debian](/docs/infrastructure/infrastructure-agent/linux-installation/package-manager-install/) para a versão 12 ("bookworm") para oferecer suporte ao [agente de infraestrutura](/docs/infrastructure/infrastructure-agent/requirements-infrastructure-agent/#os) para Linux. +* Função [`accountId()`](/docs/data-apis/manage-data/query-limits/) atualizada para consultar os limites de dados. +* [Instalador MSIWindows ](/docs/infrastructure/infrastructure-agent/windows-installation/windows-msi-installer/#install-windows)atualizado para oferecer suporte Windows de 64 bits (Intel/AMD). + +### Notas de versão + +* Anunciado 7 de janeiro de 2026 como a data de fim da vida útil das regras de descarte por meio da [interface de AI Monitoring](/docs/ai-monitoring/drop-sensitive-data/). + +* [Agente iOS v7.5.9](/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-759/) + + * Corrigido um problema que poderia fazer com que distributed tracing não tivesse todas as informações de conta necessárias no início de uma sessão. + * Corrigido um problema que poderia causar uma falha na inicialização do agente. + +* [Agente Python v10.16.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-101600/) + + * Adicionado suporte para novas funções [do Redis](https://pypi.org/project/redis/). + * Converteu todos os caminhos internos de `os.path` para `pathlib.Path`. + * Problema corrigido com codificação JSON PosixPath. + +* [Integração Kubernetes v3.44.1](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-44-1/) + + * Essa integração está incluída nas seguintes versões de gráfico: + + * [newrelic-infraestrutura-3.49.1](https://github.com/newrelic/nri-kubernetes/releases/tag/newrelic-infrastructure-3.49.1) + * [nri-bundle-6.0.10](https://github.com/newrelic/helm-charts/releases/tag/nri-bundle-6.0.10) + +* [.NET agente v10.44.1](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-44-1/) + + * Tratamento de exceções corrigido no wrapper de instrumentação do Service Bus. + * Processo de host da Web do Azure Function (Linux) excluído da instrumentação. + +* [Agente Node.js v13.2.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-2-0/) + + * Adicionada capacidade de registrar `Supportability/Features/Instrumentation/OnRequire/` métricas para instrumentação baseada em assinantes. + * Adicionado gancho do carregador esm e patch commonjs para funcionar com orchestran-js. + * Adicionada instrumentação para `@modelcontextprotocol/sdk` chamadas de cliente `client.callTool`, `client.readResource` e `client.getPrompt`. + * Lógica corrigida em torno da detecção de pacotes OTEL. + * Atualizado `shimmer.setupSubscribers` para configurar corretamente e ignorar assinantes desabilitados. + +* [Agente Node.js v13.2.1](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-2-1/) + + * Agente atualizado para usar `@apm-js-collab/tracing-hooks` para o registro CJS/ESM para rastreamento de instrumentação baseada em canal. \ No newline at end of file diff --git a/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-9-12-2025.mdx b/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-9-12-2025.mdx new file mode 100644 index 00000000000..9d88cfd440c --- /dev/null +++ b/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-9-12-2025.mdx @@ -0,0 +1,94 @@ +--- +subject: Docs +releaseDate: '2025-09-14' +version: 'September 08 - September 12, 2025' +translationType: machine +--- + +### Novos documentos + +* Adicionada documentação abrangente [do Modelo de Maturidade de Observabilidade](/docs/new-relic-solutions/observability-maturity/) para fornecer orientação para medir e melhorar práticas de observabilidade em quatro áreas principais: Tempo de operação de negócios, Experiência Digital, Excelência em Engenharia e Observabilidade Inteligente. + +### Grandes mudanças + +* [Configuração de agente PHP](/docs/apm/agents/php-agent/configuration/php-agent-configuration/) atualizada com novas opções de configuração extensivas para controles de amostragem e instrumentação de manipulador de exceções framework. + +### Pequenas mudanças + +* [Introdução o dashboard](/docs/query-your-data/explore-query-data/dashboards/introduction-dashboards/) atualizada com orientação aprimorada para uso dashboard. +* Documentação aprimorada [de dashboard](/docs/query-your-data/explore-query-data/dashboards/manage-your-dashboard/) com conteúdo simplificado para gerenciamento de JSON. +* Links quebrados corrigidos na documentação [do plano de uso do New Relic](/docs/licenses/license-information/usage-plans/new-relic-usage-plan/). +* Corrigida configuração de depuração na documentação [do agente de resolução de problemas do .NET](/docs/apm/agents/net-agent/troubleshooting/debugging-net-windows/). + +### Notas de versão + +* Fique por dentro dos nossos últimos lançamentos: + + * [Agente Browser v1.297.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.297.0/): + + * Evitar colheitas precoces durante o período de repetição para melhor manejo de limitação de taxa. + * O meta atributo newrelic foi removido da carga de replay de saída para reduzir bytes faturáveis. + * Exceções corrigidas para corpos nulos decorrentes de colheitas vazias. + + * [Agente PHP v12.1.0.26](/docs/release-notes/agent-release-notes/php-release-notes/php-agent-12-1-0-26/): + + * Controles de amostragem adicionados com base na decisão de amostragem de trace w3c upstream. + * Adicionada opção de configuração para pular a instrumentação de manipuladores de exceção do framework. + * Corrigido possível vazamento de memória ao chamar `newrelic_end_transaction(true)`. + * A versão do golang foi aumentada para 1.25.1 para melhorias de segurança. + + * [Agente Python v10.17.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-101700/): + + * Adicionado suporte para tarefas personalizadas no Celery. + * Adicionado suporte para monitoramento Graphene-Django. + * Adicionado suporte para filtragem de middleware no Django. + * Adicionado suporte para a API AWS Bedrock Converse. + * Adicionado suporte para o sinalizador amostrado do cabeçalho W3CTraceParent. + + * [Agente Java v8.24.0](/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8240/): + + * Adicionado suporte para MongoDB Reactive Streams 5.2.0 e superiores. + * Adicionado suporte para Jedis 6. + * Corrigido o problema de instrumentação dupla do CouchBase. + * Corrigido o problema de encapsulamento de cabeçalho do Spring WebClient 5.x. + + * [Agente Node.js v13.3.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-3-0/): + + * Adicionado suporte a MCP `StreamableHTTPClientTransport`. + + * [Agente Node.js v13.3.1](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-3-1/): + + * Corrigida a falha ao definir `requestParameters` como padrão para um objeto em `transaction.addRequestParameters`. + + * [Agente Node.js v13.3.2](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-3-2/): + + * Adicionado código defensivo para obter `protocol` em chamadas http de saída. + + * [Integração Kubernetes v3.45.1](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-45-1/): + + * Atualizado com as últimas melhorias e correções de bugs. + + * [Gerenciador de tarefas v464](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-464/): + + * Problema corrigido em que os clientes não conseguiam extrair imagens de um registro personalizado usando o podman. + + * [Tempo de execução do navegador Node v3.0.43](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.43/): + + * Vulnerabilidades subjacentes do Ubuntu corrigidas para lidar com vulnerabilidades de segurança. + + * [Aplicativo móvel para iOS v6.9.12](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6102/): + + * Problemas de link profundo corrigidos para painel e alertas. + * Problema corrigido no ID do painel do CCU. + + * [Aplicativo móvel para Android v5.30.7](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5307/): + + * Adicionadas correções de bugs e melhorias. + + * [Agente Flutter v1.1.14](/docs/release-notes/mobile-release-notes/flutter-release-notes/flutter-agent-1114/): + + * Adicionou melhorias adicionais de estabilidade e correções de bugs. + + * [Controle de Pipeline Gateway v25.09.01](/docs/release-notes/pipeline-control-gateway-release-notes/pipeline-control-gateway-25-09-01/): + + * Adicionada nova versão com recursos aprimorados de controle de pipeline. \ No newline at end of file diff --git a/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-9-15-2025.mdx b/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-9-15-2025.mdx new file mode 100644 index 00000000000..351e3339825 --- /dev/null +++ b/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-9-15-2025.mdx @@ -0,0 +1,84 @@ +--- +subject: Docs +releaseDate: '2025-09-19' +version: 'September 15 - September 19, 2025' +translationType: machine +--- + +### Novos documentos + +* Integração AWS reestruturada para métrica: + + * Adicionada [integração manual com AWS](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/manual/) + * Adicionada [integração do Terraform com a AWS](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/terraform/) + * Adicionado [CloudFormation com integração de pesquisa de API](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-and-api-polling/) + * [Guia de migração adicionado da pesquisa de API para o CloudWatch Metric Streams](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/migrate-from-api-polling-to-cwms/) + +### Grandes mudanças + +* [Documentação aprimorada de streaming de vídeo e anúncios](/docs/streaming-video-&-ads/get-started-with-streaming-video-&-ads/) com atualizações de estrutura de agente autônomo. + +### Pequenas mudanças + +* [API de problemas do NerdGraph atualizada via GitHub](/docs/apis/nerdgraph/examples/nerdgraph-issues-api-via-github/) com documentação aprimorada. +* [Integração atualizada do Microsoft Teams](/docs/alerts-applied-intelligence/notifications/notification-integrations/) com orientação de configuração aprimorada. +* Tipo de gráfico [de mapa de calor](docs/query-your-data/explore-query-data/use-charts/chart-types/#widget-heatmap) atualizado. +* [IntegraçãoMySQL ](/docs/infrastructure/host-integrations/host-integrations-list/mysql-monitoring-integration/)atualizada com melhorias de timing para monitoramento QPM. +* Documentação [de gerenciamento de cardinalidade](/docs/data-apis/ingest-apis/metric-api/cardinality-management/) aprimorada com pequenas atualizações. +* [Requisitos de compatibilidade do agente .NET](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements/) atualizados com as versões mais recentes da biblioteca compatível verificada. +* Corrigido bug na documentação [do código de controle do pipeline](docs/new-relic-control/pipeline-control/cloud-rules-api/). + +### Notas de versão + +* [Monitoramento sintético atualizado com novas datas de fim de vida para endereços IP](/eol/2025/02/eol-01-31-25-synthetics-ip/). + +* Fique por dentro dos nossos últimos lançamentos: + + * [Agente Java v8.24.0](/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8240/): + + * Adicionado suporte para MongoDB Reactive Streams 5.2.0 e superiores. + * Adicionado suporte para Jedis 6. + * Corrigido o problema de instrumentação dupla do CouchBase. + * Corrigido o problema de encapsulamento de cabeçalho do Spring WebClient 5.x. + + * [Agente Python v10.17.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-101700/): + + * Adicionado suporte para tarefas personalizadas no Celery. + * Adicionado suporte para monitoramento Graphene-Django. + * Adicionado suporte para filtragem de middleware no Django. + * Adicionado suporte para a API AWS Bedrock Converse. + * Adicionado suporte para o sinalizador amostrado do cabeçalho W3CTraceParent. + + * [agente de infraestrutura v1.68.0](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/1680/): + + * Versão Go atualizada para 1.25.0. + * Dependência newrelic/nri-winservices atualizada para v1.3.0. + + * [Agente Browser v1.298.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.298.0/): + + * Interação de navegação suave estendida para incluir tarefas longas além do tempo de modificação DOM. + * LCP corrigido para relatar a URL da página original em vez da URL da página atual durante navegações suaves. + + * [Agente Browser v1.297.1](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.297.1/): + + * Corrigido um problema em que a classe agregada Session Replay poderia ser importada duas vezes ao usar o newrelic.recordReplay O método API durante o pré-carregamento foi habilitado. + + * [Agente React Native v1.5.10](/docs/release-notes/mobile-release-notes/react-native-release-notes/react-native-agent-1510/): + + * Atualizou o agente Android nativo para a versão 7.6.9. + * O agente nativo do iOS foi atualizado para a versão 7.5.10. + + * [Agente iOS v7.5.10](/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-7510/): + + * Corrigida uma falha que poderia ocorrer na inicialização do agente. + + * [NRDOT v1.4.0](/docs/release-notes/nrdot-release-notes/nrdot-2025-09-18/): + + * Adicionado spanprocessor ao nrdot-collector. + * Versões do componente OpenTelemetry aumentadas de v0.131.0 para v0.132.0. + * Adicionado newrelic.service.type à configuração de telemetria interna. + * Detecção de nome de host habilitada para EC2. + + * [Integração Kubernetes v3.45.2](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-45-2/): + + * Atualizado com as últimas melhorias e correções de bugs. \ No newline at end of file diff --git a/src/i18n/content/pt/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-759.mdx b/src/i18n/content/pt/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-759.mdx index 50a0ddef640..99860de0d7e 100644 --- a/src/i18n/content/pt/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-759.mdx +++ b/src/i18n/content/pt/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-759.mdx @@ -6,14 +6,6 @@ downloadLink: 'https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agen translationType: machine --- - - A partir da versão 7.5.4 do iOS SDK, uma alteração foi implementada que faz com que o evento Handled Exception suprimido anteriormente seja relatado. - - Atualize para o agente iOS 7.5.9 do New Relic. Identificamos um bug no iOS SDK versão 7.5.8 que pode causar upload incorreto de dados, e uma correção está incluída no agente iOS 7.5.9 do New Relic liberar. - - Atualize para o agente iOS 7.5.9 do New Relic. Identificamos um bug no iOS SDK versão 7.5.7 que poderia causar uma falha no lançamento do agente, e uma correção está incluída no New Relic iOS agente 7.5.9 liberar. - - ## Corrigido nesta versão * O agente foi criado usando o Xcode 16.4. diff --git a/src/i18n/content/pt/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx b/src/i18n/content/pt/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx new file mode 100644 index 00000000000..3cf842161b5 --- /dev/null +++ b/src/i18n/content/pt/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx @@ -0,0 +1,39 @@ +--- +subject: Browser agent +releaseDate: '2025-08-04' +version: 1.295.0 +downloadLink: 'https://www.npmjs.com/package/@newrelic/browser-agent' +features: + - Add error cause detection +bugs: + - Add monkey-patching warnings + - Calculate first and last timestamps from raw data +security: [] +translationType: machine +--- + +## v1.295.0 + +### Recurso + +#### Adicionar detecção de causa de erro + +Detecte e relate o atributo de causa no evento JavaScriptError capturado. Se a causa for uma instância de um erro, o stack trace será capturado; caso contrário, o conteúdo em string da causa será relatado. Isso poderá ser consultado no evento JavaScriptError sob o atributo `cause`. + +### Correções de bugs + +#### Adicionar avisos de monkey-patching + +Detecção e avisos adicionados para quando os globais esperados foram corrigidos antes do agente ser executado na página. Isso pode causar comportamentos inesperados e a intenção é informar os clientes sobre esse comportamento. + +#### Calcular o primeiro e o último registro de data e hora a partir de dados brutos + +Certifique-se de que o agente calcule manualmente o primeiro e o último registro de data e hora de uma carga do SessionReplay antes da coleta para ajudar a melhorar a consistência no replayer da interface. + +## Declaração de apoio + +New Relic recomenda que você atualize o agente regularmente para garantir que esteja obtendo os benefícios mais recentes de recursos e desempenho. Versões mais antigas não terão mais suporte quando chegarem [ao fim de sua vida útil](https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/browser-agent-eol-policy/). As datas de lançamento refletem a data de publicação original da versão do agente. + +Novos lançamentos de agente do browser são disponibilizados aos clientes em pequenas etapas ao longo de um período de tempo. Por esse motivo, a data em que o lançamento fica acessível à sua conta pode não corresponder à data de publicação original. Consulte este [dashboard de status](https://newrelic.github.io/newrelic-browser-agent-release/) para obter mais informações. + +De acordo com nossa [política de suporte a navegadores](https://docs.newrelic.com/docs/browser/new-relic-browser/getting-started/compatibility-requirements-browser-monitoring/#browser-types), a versão v1.295.0 do Agente do browser foi criada e testada nesses navegadores e intervalos de versão: Chrome 128-138, Edge 128-138, Safari 17-19 e Firefox 130-140. Para dispositivos móveis, a versão v1.295.0 foi criada e testada para Android OS 16 e iOS Safari 17-26. \ No newline at end of file diff --git a/src/i18n/content/pt/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.296.mdx b/src/i18n/content/pt/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.296.mdx new file mode 100644 index 00000000000..2f08aaa8206 --- /dev/null +++ b/src/i18n/content/pt/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.296.mdx @@ -0,0 +1,34 @@ +--- +subject: Browser agent +releaseDate: '2025-08-19' +version: 1.296.0 +downloadLink: 'https://www.npmjs.com/package/@newrelic/browser-agent' +features: + - Harvest traces early +bugs: + - Remove event buffer inspection event +security: [] +translationType: machine +--- + +## v1.296.0 + +### Recurso + +#### Colheita de rastros precoce + +Atualize o agente para tratar o trace da sessão da mesma forma que outros recursos tratam os dados a partir de [1.294.0](https://docs.newrelic.com/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.294.0/), permitindo colheitas com tamanho de 16kb. + +### Correções de bugs + +#### Remover evento de inspeção de buffer de evento + +Remove a inspeção do buffer de eventos para evitar um vazamento de memória ao usar console.log com o ouvinte de eventos da janela `newrelic`. + +## Declaração de apoio + +New Relic recomenda que você atualize o agente regularmente para garantir que esteja obtendo os benefícios mais recentes de recursos e desempenho. Versões mais antigas não terão mais suporte quando chegarem [ao fim de sua vida útil](https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/browser-agent-eol-policy/). As datas de lançamento refletem a data de publicação original da versão do agente. + +Novos lançamentos de agente do browser são disponibilizados aos clientes em pequenas etapas ao longo de um período de tempo. Por esse motivo, a data em que o lançamento fica acessível à sua conta pode não corresponder à data de publicação original. Consulte este [dashboard de status](https://newrelic.github.io/newrelic-browser-agent-release/) para obter mais informações. + +De acordo com nossa [política de suporte a navegadores](https://docs.newrelic.com/docs/browser/new-relic-browser/getting-started/compatibility-requirements-browser-monitoring/#browser-types), a versão v1.296.0 do agente Browser foi criada e testada nesses navegadores e intervalos de versão: Chrome 129-139, Edge 129-139, Safari 17-19 e Firefox 131-141. Para dispositivos móveis, a versão v1.296.0 foi criada e testada para Android OS 16 e iOS Safari 17-18.1. \ No newline at end of file diff --git a/src/i18n/content/pt/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.297.mdx b/src/i18n/content/pt/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.297.mdx index 002dfdb8f1e..6bbf1648510 100644 --- a/src/i18n/content/pt/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.297.mdx +++ b/src/i18n/content/pt/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.297.mdx @@ -1,34 +1,22 @@ --- subject: Browser agent -releaseDate: '2025-09-10' -version: 1.297.0 +releaseDate: '2025-09-17' +version: 1.297.1 downloadLink: 'https://www.npmjs.com/package/@newrelic/browser-agent' -features: - - Prevent early harvests when in retry period - - remove newrelic meta attribute +features: [] bugs: - - Fix exceptions for null bodies arising from empty harvests + - Prevent double import of Session Replay aggregate class security: [] translationType: machine --- -## v1.297.0 - -### Recurso - -#### Evite colheitas precoces no período de repetição - -Evite que o agente faça a colheita mais cedo quando a taxa estiver limitada. Se o serviço de ingestão retornar 429, o agente substituirá seus dados e tentará a coleta novamente mais tarde. Enquanto isso acontece, ele não poderá mais coletar dados antecipadamente, conforme novos dados chegam, até que a coleta seja bem-sucedida. - -#### remover meta atributo newrelic - -Remover o relatório do meta atributo \_\_newrelic da carga de replay de saída. Isso está sendo realizado como uma medida para ajudar a economizar bytes faturáveis para os clientes e reduzir o custo de uso das funcionalidades do Session Replay. +## v1.297.1 ### Correções de bugs -#### Corrigir exceções para corpos nulos decorrentes de colheitas vazias +#### Impedir importação dupla da classe agregada Session Replay -Foi feita uma alteração para garantir que toda carga limpa garanta uma saída válida. Antes, uma string vazia passando pelo processo de limpeza do corpo poderia gerar um erro, pois o mecanismo retornaria o corpo como nulo. Agora, strings vazias passarão intactas, permitindo que o processamento posterior seja aplicado com sucesso. +Corrige um problema encontrado em que a classe agregada Session Replay poderia ser importada duas vezes ao usar o método API newrelic.recordReplay durante o pré-carregamento foi habilitado. ## Declaração de apoio @@ -36,4 +24,4 @@ New Relic recomenda que você atualize o agente regularmente para garantir que e Novos lançamentos de agente do browser são disponibilizados aos clientes em pequenas etapas ao longo de um período de tempo. Por esse motivo, a data em que o lançamento fica acessível à sua conta pode não corresponder à data de publicação original. Consulte este [dashboard de status](https://newrelic.github.io/newrelic-browser-agent-release/) para obter mais informações. -De acordo com nossa [política de suporte a navegadores](https://docs.newrelic.com/docs/browser/new-relic-browser/getting-started/compatibility-requirements-browser-monitoring/#browser-types), a versão v1.297.0 do agente do Browser foi criada e testada nesses navegadores e intervalos de versão: Chrome 129-139, Edge 129-139, Safari 17-19 e Firefox 131-141. Para dispositivos móveis, a versão v1.297.0 foi criada e testada para Android OS 16 e iOS Safari 17-18.1. \ No newline at end of file +De acordo com nossa [política de suporte a navegadores](https://docs.newrelic.com/docs/browser/new-relic-browser/getting-started/compatibility-requirements-browser-monitoring/#browser-types), a versão v1.297.1 do agente do Browser foi criada e testada nesses navegadores e intervalos de versão: Chrome 130-140, Edge 130-140, Safari 17-19 e Firefox 132-142. Para dispositivos móveis, a versão v1.297.1 foi criada e testada para Android OS 16 e iOS Safari 17-18.5. diff --git a/src/i18n/content/pt/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.mdx b/src/i18n/content/pt/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.mdx new file mode 100644 index 00000000000..a893b8d607c --- /dev/null +++ b/src/i18n/content/pt/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.mdx @@ -0,0 +1,10 @@ +--- +subject: Node API runtime +releaseDate: '2025-07-29' +version: 1.2.122 +translationType: machine +--- + +### Correções + +* Corrigidas as vulnerabilidades de dados de formulário e as vulnerabilidades subjacentes do Ubuntu para lidar com vulnerabilidades de segurança em tempos de execução API do Node. \ No newline at end of file diff --git a/src/i18n/content/pt/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.53.mdx b/src/i18n/content/pt/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.53.mdx new file mode 100644 index 00000000000..4bb67078ec7 --- /dev/null +++ b/src/i18n/content/pt/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.53.mdx @@ -0,0 +1,10 @@ +--- +subject: Ping Runtime +releaseDate: '2025-07-29' +version: 1.53.0 +translationType: machine +--- + +### Melhorias + +* Vulnerabilidades corrigidas relacionadas ao `common-lang3` Java e Ubuntu para resolver problemas de segurança no tempo de execução do Ping. \ No newline at end of file diff --git a/src/i18n/content/pt/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.54.mdx b/src/i18n/content/pt/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.54.mdx new file mode 100644 index 00000000000..b7b8a18c47c --- /dev/null +++ b/src/i18n/content/pt/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.54.mdx @@ -0,0 +1,10 @@ +--- +subject: Ping Runtime +releaseDate: '2025-08-13' +version: 1.54.0 +translationType: machine +--- + +### Melhorias + +* Vulnerabilidades corrigidas relacionadas ao Ubuntu para resolver problemas de segurança no tempo de execução do Ping. \ No newline at end of file