|
- [BrowserPerformance](/attribute-dictionary/?event=BrowserPerformance) events
+ Événements [BrowserPerformance](/attribute-dictionary/?event=BrowserPerformance)
|
diff --git a/src/i18n/content/fr/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/manual.mdx b/src/i18n/content/fr/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/manual.mdx
new file mode 100644
index 00000000000..7afacbeb65a
--- /dev/null
+++ b/src/i18n/content/fr/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/manual.mdx
@@ -0,0 +1,72 @@
+---
+title: Intégrer manuellement depuis la console AWS
+tags:
+ - Integrate manually
+ - Manual integration
+ - AWS metric integration
+ - Amazon integrations
+ - AWS integrations
+metaDescription: Integrate New Relic with AWS services manually from the AWS console.
+freshnessValidatedDate: never
+translationType: machine
+---
+
+Pour une intégration transparente de votre compte AWS avec New Relic, [l'intégration via CloudFormation et flux de métriques CloudWatch](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation) est l'approche la plus recommandée. Si vous ne pouvez pas utiliser les modèles CloudFormation et ne préférez pas utiliser Terraform, reportez-vous à la procédure suivante pour effectuer une intégration manuelle à partir de la console AWS.
+
+## 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 New Relic Ingest et une clé utilisateur](https://one.newrelic.com/api-keys)**: vous aurez besoin de ces clés 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, 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**: Manually integrate your AWS account
+
+5. Sur l'écran **Select services**, si nécessaire, utilisez le bouton bascule **Show resources not supported by CloudWatch Metric Streams**, sélectionnez les services que vous souhaitez monitorer, puis continuez.
+
+6. Sur l’écran **Choose data integration type**, choisissez parmi les options d’intégration suivantes :
+
+ * **Monitoring AWS en temps réel (Recommandé)**: Cette option est destinée aux services qui prennent en charge le flux de métriques CloudWatch.
+ * **Sondage API**: Cette option convient aux services non pris en charge par flux de métriques CloudWatch.
+
+7. De la page **Create role** à la page **Configure budgets policy**, suivez les instructions à l’écran et effectuez les étapes dans la console AWS.
+
+8. Après avoir créé la politique dans la console AWS, 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.
+
+
+
+ Intégrez les services AWS avec New Relic en utilisant CloudFormation et les flux de métriques CloudWatch.
+
+
+
+ Intégrez les services AWS à New Relic à l’aide de CloudFormation et d’API Polling.
+
+
+
+ Intégrez les services AWS avec New Relic à l’aide de Terraform.
+
+
\ No newline at end of file
diff --git a/src/i18n/content/fr/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/migrate-from-api-polling-to-cwms.mdx b/src/i18n/content/fr/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/migrate-from-api-polling-to-cwms.mdx
new file mode 100644
index 00000000000..17bfeef7417
--- /dev/null
+++ b/src/i18n/content/fr/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/migrate-from-api-polling-to-cwms.mdx
@@ -0,0 +1,111 @@
+---
+title: Migrer des interrogations API vers les flux de métriques CloudWatch
+tags:
+ - API polling to CWMS migration
+metaDescription: Migrate your New Relic and AWS services integration type from API Polling to CloudWatch Metric Streams.
+freshnessValidatedDate: never
+translationType: machine
+---
+
+Pour une intégration transparente de votre compte AWS avec New Relic, [l'intégration via CloudFormation et flux de métriques CloudWatch](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation) est l'approche la plus recommandée. Cependant, si vous avez déjà intégré votre compte AWS à New Relic à l'aide d'API Polling, reportez-vous à la procédure suivante pour migrer d'API Polling vers 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 New Relic Ingest et une clé utilisateur](https://one.newrelic.com/api-keys)**: vous aurez besoin de ces clés 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.
+* Pour les utilisateurs qui gèrent plusieurs comptes AWS, [connectez chaque compte à un seul compte New Relic](/docs/infrastructure/amazon-integrations/manage-aws-data/aws-multi-account).
+* Pour les utilisateurs qui gèrent plusieurs régions au sein de ces comptes, vous devez créer un Kinesis Data Firehose distinct qui pointe vers New Relic pour chaque région.
+
+
+
+ ## Migrer vers l'intégration flux de métriques CloudWatch [#migrate]
+
+ Vous pouvez migrer à partir de l'interrogation API en créant un modèle CloudFormation ou en rajoutant votre compte AWS et en suivant nos procédures guidées d'installation dans l'application. Nous vous recommandons d'utiliser la méthode de modèle CloudFormation, car c'est le moyen le plus efficace de migrer. Ces intégrations ne sont pas supportées par flux de métriques CloudWatch et ne peuvent pas être migrées vers notre intégration :
+
+ * AWS CloudTrail
+ * AWS Health
+ * AWS Trusted Advisor
+ * AWS X-Ray
+
+ Si vous utilisez ces intégrations, vous devez toujours utiliser la méthode d’interrogation API.
+
+
+
+ Le modèle CloudFormation vous permet de mettre à jour un modèle avec un espace de nommage préconfiguré en fonction de votre configuration d'interrogation.
+
+ 1. Accédez à **[one.newrelic.com > Infrastructure > AWS](https://one.newrelic.com/infra/infrastructure/cloud-aws)**, puis cliquez sur **Migrate to CloudWatch Metric stream**.
+ 2. Suivez les procédures. Vous téléchargerez le modèle, puis répliquerez l'espace de nommage à partir du sondage API. Assurez-vous d'ajouter les détails de votre compte au modèle téléchargé.
+ 3. Depuis AWS Console, accédez à **Cloud Formation > Create Stack > Upload a template file**. Téléchargez votre modèle CloudFormation mis à jour.
+
+
+
+ Si vous ne souhaitez pas utiliser la méthode CloudFormation, vous devez rajouter votre compte AWS même si vous avez déjà lié votre compte AWS à l'intégration d'interrogation. Ces procédures peuvent vous amener à quitter ce document, mais n'oubliez pas de revenir pour désactiver votre intégration d'interrogation.
+
+ 1. Allez à **[one.newrelic.com > All capabilities >Infrastructure > AWS](https://one.newrelic.com/infra/infrastructure/cloud-aws)**, puis cliquez sur **Add AWS account**. Choisissez votre méthode.
+ 2. Suivez les étapes AWS Console à partir du [fluxAWS Console ](/install/aws-cloudwatch/?task=console)dans ce document.
+ 3. [Désactivez toutes les intégrations d’interrogation inutiles](/docs/infrastructure/amazon-integrations/connect/uninstall-aws/) dans le compte de fournisseur AWS précédent.
+
+ Lors de la désactivation, gardez à l'esprit que [certaines intégrations ne sont pas prises en charge par flux de métriques CloudWatch](/docs/infrastructure/amazon-integrations/connect/connect-aws-new-relic-infrastructure-monitoring/).
+
+
+
+ Notre intégration de flux de métriques CloudWatch utilise l'API métrique pour pousser les métriques au format [métrique dimensionnel](/docs/data-apis/understand-data/new-relic-data-types/#dimensional-metrics). Notre méthode d'interrogation API, quant à elle, envoie des métriques basées sur [l'événement](/docs/data-apis/understand-data/new-relic-data-types/#events-new-relic).
+
+ * Pour faciliter la transition, nous fournissons un mécanisme de calage qui vous permet d'écrire de manière transparente des requêtes dans n'importe quel format. Ces requêtes sont traitées comme prévu en fonction de la source disponible, soit d'événement à métriques, soit de métriques à événement.
+ * Nous vous recommandons de revoir [certaines limitations](/docs/query-your-data/nrql-new-relic-query-language/nrql-query-tutorials/query-infrastructure-dimensional-metrics-nrql/#known-limitations) concernant le mécanisme de shimming qui vous permet d'utiliser une requête basée sur des événements avec l'intégration de flux de métriques CloudWatch.
+
+ Après la migration, certaines fonctionnalités de New Relic qui dépendent de vos données d'interrogation API peuvent se comporter différemment :
+
+ * **Dashboards**: le tableau de bord personnalisé qui utilise un événement d'intégration AWS basé sur des sondages fonctionnera toujours comme prévu.
+ * **Alerts**: condition d'alerte selon laquelle l'utilisation d'un événement AWS basé sur un sondage fonctionnera toujours. Nous vous recommandons de les adapter au format de métrique dimensionnelle qui utilise NRQL comme source.
+ * **Entities**: votre liste d'entités monitorées peut afficher des entités dupliquées pendant 24 heures maximum.
+ * **Attributes**: l'intégration AWS basée sur les sondages préfixe la balise de ressource collectée avec `label.`, tandis que l'intégration AWS CloudWatch Metric Streams préfixe la balise de ressource collectée avec `tags.`. Si les deux intégrations sont activées pour le même compte AWS, la balise de ressource apparaîtra sous les deux préfixes lors de l'utilisation du format événement.
+
+
+
+ ## Validez vos données [#validate-data]
+
+ Pour confirmer que vous recevez des données des flux métriques, suivez ces étapes :
+
+ 1. Aller à **[one.newrelic.com > All capabilities > Infrastructure > AWS](https://one.newrelic.com/infra/infrastructure/cloud-aws)**. Recherchez le compte AWS que vous avez connecté à New Relic. **Stream** comptes.
+ 2. Vérifiez le dashboard l’état du compte et confirmez que New Relic reçoit les données métriques. Cela peut inclure des erreurs et le nombre d'espaces de nommage et de métriques ingérés.
+ 3. Explorez vos données en écrivant des requêtes pour des ensembles spécifiques de métriques.
+
+ Il faudra peut-être quelques minutes à New Relic pour détecter de nouvelles ressources et les synthétiser en tant qu'entité.
+
+
+ Les métriques AWS CloudWatch pour les services mondiaux, tels qu'AWS AWS Billing, ne sont disponibles que dans la région **us-east-1**. Assurez-vous qu’un flux de métriques CloudWatch actif est configuré dans cette région.
+
+
+
+
+## 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.
+
+
+
+ Intégrez les services AWS avec New Relic en utilisant CloudFormation et les flux de métriques CloudWatch.
+
+
+
+ Intégrez les services AWS à New Relic à l’aide de CloudFormation et d’API Polling.
+
+
+
+ Intégrez les services AWS avec New Relic à l’aide de Terraform.
+
+
+
+ Intégrez manuellement les services AWS avec New Relic depuis la console AWS.
+
+
\ No newline at end of file
diff --git a/src/i18n/content/fr/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/terraform.mdx b/src/i18n/content/fr/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/terraform.mdx
new file mode 100644
index 00000000000..92c565d70bf
--- /dev/null
+++ b/src/i18n/content/fr/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/terraform.mdx
@@ -0,0 +1,65 @@
+---
+title: Intégration avec Terraform
+tags:
+ - Integrate with Terraform
+ - AWS metric integration
+ - Amazon integrations
+ - AWS integrations
+metaDescription: Integrate New Relic with AWS services using Terraform.
+freshnessValidatedDate: never
+translationType: machine
+---
+
+Pour une intégration transparente de votre compte AWS avec New Relic, [l'intégration via CloudFormation et flux de métriques CloudWatch](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation) est l'approche la plus recommandée. Si vous gérez déjà vos comptes et services AWS à l’aide de Terraform, vous préférerez peut-être la méthode d’intégration suivante, car New Relic propose un module cloud d’intégration AWS qui simplifie la configuration de l’intégration.
+
+## Prérequis [#prerequisites]
+
+Avant de commencer à intégrer votre compte AWS à New Relic, assurez-vous de remplir les conditions préalables suivantes :
+
+* **[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.
+* L'ID de compte New Relic et la région que vous souhaitez lier à AWS.
+
+## Étapes d'intégration [#integration-steps]
+
+Pour intégrer votre compte AWS à New Relic, 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 with Terraform
+
+5. Sur l'écran **Select services**, si nécessaire, utilisez le bouton bascule **Show resources not supported by CloudWatch Metric Streams**, sélectionnez les services que vous souhaitez monitorer, puis continuez.
+
+6. Depuis l’écran **Terraform**, ouvrez la documentation qui explique comment connecter votre compte New Relic au compte du fournisseur Terraform.
+
+7. Après une intégration réussie, vous pouvez voir 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.
+
+
+
+ Intégrez les services AWS avec New Relic en utilisant CloudFormation et les flux de métriques CloudWatch.
+
+
+
+ Intégrez les services AWS à New Relic à l’aide de CloudFormation et d’API Polling.
+
+
+
+ Intégrez manuellement les services AWS avec New Relic depuis la console AWS.
+
+
\ No newline at end of file
diff --git a/src/i18n/content/fr/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-and-api-polling.mdx b/src/i18n/content/fr/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-and-api-polling.mdx
new file mode 100644
index 00000000000..e56dc90829c
--- /dev/null
+++ b/src/i18n/content/fr/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-and-api-polling.mdx
@@ -0,0 +1,77 @@
+---
+title: Intégration via CloudFormation et sondage API
+tags:
+ - Integration via CloudFormation
+ - AWS metric integration
+ - Amazon integrations
+ - AWS integrations
+ - Integration with API polling via CloudFormation
+metaDescription: Integrate New Relic with AWS services using CloudFormation templates to automate the setup of API polling for metrics ingestion.
+freshnessValidatedDate: never
+translationType: machine
+---
+
+Pour une intégration transparente de votre compte AWS avec New Relic, [l'intégration via CloudFormation et flux de métriques CloudWatch](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation) est l'approche la plus recommandée. Vous pouvez également utiliser API Polling pour l'intégration avec certaines limitations de récupération de données. Pour plus de détails, reportez-vous au tableau de comparaison dans [Ingestion des métriques AWS](/docs/infrastructure/amazon-integrations/get-started/introduction-aws-integrations/#aws-metrics-ingestion). Il est recommandé d'utiliser API Polling uniquement 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 New Relic Ingest et une clé utilisateur](https://one.newrelic.com/api-keys)**: vous aurez besoin de ces clés 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 d'API Polling, procédez comme suit :
+
+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**: API Polling
+
+5. Sur l'écran **Select services**, si nécessaire, utilisez le bouton bascule **Show resources not supported by CloudWatch Metric Streams**, sélectionnez les services que vous souhaitez monitorer, puis 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 la clé de licence Ingest et la clé utilisateur dans votre console AWS.
+
+
+ Pour obtenir des métadonnées supplémentaires à partir de vos services AWS, activez **AWS Config** depuis la console AWS.
+
+
+10. 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/).
+11. 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.
+
+
+
+ Intégrez les services AWS avec New Relic en utilisant CloudFormation et les flux de métriques CloudWatch.
+
+
+
+ Intégrez les services AWS avec New Relic à l’aide de Terraform.
+
+
+
+ Intégrez manuellement les services AWS avec New Relic depuis la console AWS.
+
+
\ No newline at end of file
diff --git a/src/i18n/content/fr/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms.mdx b/src/i18n/content/fr/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms.mdx
new file mode 100644
index 00000000000..2edd17cb421
--- /dev/null
+++ b/src/i18n/content/fr/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms.mdx
@@ -0,0 +1,86 @@
+---
+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 New Relic Ingest et une clé utilisateur](https://one.newrelic.com/api-keys)**: vous aurez besoin de ces clés 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.
+
+ 
+
+
+ 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 la clé de licence Ingest et la clé utilisateur dans votre console AWS.
+
+
+ Pour obtenir des métadonnées supplémentaires à partir de vos services AWS, activez **AWS Config** depuis la console AWS.
+
+
+10. 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/).
+
+11. 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.
+
+
+
+ Intégrez les services AWS à New Relic à l’aide de CloudFormation et d’API Polling.
+
+
+
+ Intégrez les services AWS avec New Relic à l’aide de Terraform.
+
+
+
+ Intégrez manuellement les services AWS avec New Relic depuis la console AWS.
+
+
\ No newline at end of file
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.
+
+
+
+
+ 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/amazon-integrations/get-started/introduction-aws-integrations.mdx b/src/i18n/content/fr/docs/infrastructure/amazon-integrations/get-started/introduction-aws-integrations.mdx
index 29733798af2..6a47e18f7e5 100644
--- a/src/i18n/content/fr/docs/infrastructure/amazon-integrations/get-started/introduction-aws-integrations.mdx
+++ b/src/i18n/content/fr/docs/infrastructure/amazon-integrations/get-started/introduction-aws-integrations.mdx
@@ -181,14 +181,14 @@ Les services AWS suivants ne sont pas pris en charge par flux de métriques Clou
Si vous utilisez d'autres services AWS en plus de ceux-ci, vous pouvez toujours choisir l'intégration d'Amazon flux de métriques CloudWatch. Lors de la configuration, New Relic offre la possibilité de configurer l’interrogation API spécifiquement pour ces services non pris en charge.
-Following are the ways to integrate your AWS services with New Relic:
+Voici les moyens d’intégrer vos services AWS à New Relic :
-* [Via CloudFormation and CloudWatch metric stream](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms).
-* [Via CloudFormation and API Polling](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-and-api-polling).
-* [Via Terraform](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/terraform).
-* [Manually from AWS console](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/manual).
+* [Via CloudFormation et flux de métriques CloudWatch](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms).
+* [Via CloudFormation et API Polling](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-and-api-polling).
+* [Par Terraform](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/terraform).
+* [Manuellement depuis la console AWS](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/manual).
-If you have already integrated your AWS account with New Relic using API Polling, refer to the [migration procedure](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/migrate-from-api-polling-to-cwms) to migrate to CloudWatch Metric Streams.
+Si vous avez déjà intégré votre compte AWS à New Relic à l'aide d'API Polling, reportez-vous à la [procédure de migration](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/migrate-from-api-polling-to-cwms) pour migrer vers flux de métriques CloudWatch.
### Coûts d'intégration AWS [#aws-costs]
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
-## 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
```
- 
+ /* <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}})
```
- 
+ /* <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}}
```
- 
+ /* <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
```
- 
+ /* <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
```
- 
+ /* <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
```
- 
+ /* <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`
- 
+ /* <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}}
```
- 
+ /* <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
```
- 
+ /* <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
```
- 
+ /* <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:
- 
+ * **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}}
```
- 
+ /* <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`
- 
+ /* <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
```
- 
+ /* <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}})
```
- 
+ /* <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.
- 
+ /* <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/agent-release-notes/java-release-notes/java-agent-8240.mdx b/src/i18n/content/fr/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8240.mdx
index 4f8b007a681..79bd6c0a770 100644
--- a/src/i18n/content/fr/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8240.mdx
+++ b/src/i18n/content/fr/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8240.mdx
@@ -7,8 +7,8 @@ features:
- “Support MongoDB Reactive Streams 5.2.0 and up”
- “Jedis 6 support”
bugs:
- - “CouchBase: Add skip class to prevent double instrumentation”
- - “Spring WebClient 5.x: Only wrap headers instead of the entire response”
+ - 'CouchBase: Add skip class to prevent double instrumentation'
+ - 'Spring WebClient 5.x: Only wrap headers instead of the entire response'
security: []
translationType: machine
---
diff --git a/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx b/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx
new file mode 100644
index 00000000000..ad96fe73bd5
--- /dev/null
+++ b/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx
@@ -0,0 +1,267 @@
+---
+subject: Docs
+releaseDate: '2025-07-25'
+version: 'June 13 - July 24, 2025'
+translationType: machine
+---
+
+### Nouveaux documents
+
+* Ajout d'une nouvelle fonctionnalité sur [la façon de déboguer les problèmes de l'agent New Relic Browser ](/docs/browser/new-relic-browser/troubleshooting/how-to-debug-browser-agent/), y compris le logging détaillé, monitoring des demandes réseau et l'événement d'inspection pour un dépannage amélioré dans les versions d'agent 1.285.0 et supérieures.
+* Ajout de la prise en charge [d’Azure Functions](/docs/serverless-function-monitoring/azure-function-monitoring/introduction-azure-monitoring/) pour le monitoring des fonctions `python` et `.node.js`.
+* Ajout [d'un optimiseur de coûts](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/compute-optimizer/) pour des informations détaillées exploitables pour améliorer l'efficacité du calcul, avec une fonctionnalité permettant d'identifier les inefficacités, de fournir des recommandations d'optimisation et d'estimer les économies de CCU dans la plateforme New Relic.
+* Ajout [d'Intelligence Coûts du cloud](/docs/cci/getting-started/overview), offrant des outils de visibilité et de gestion des coûts cloud, y compris des fonctionnalités telles que la répartition complète des coûts, l'allocation des coûts Kubernetes, l'estimation des coûts en temps réel et la collecte de données inter-comptes, prenant actuellement en charge uniquement les coûts AWS cloud.
+* Ajout [de l'observabilité OpenTelemetry pour Kubernetes avec l'intégration indépendante du fournisseur de fonctionnalités New Relic](/docs/kubernetes-pixie/k8s-otel/intro/) pour monitoring transparente du cluster via le graphique Helm, améliorant les signaux de télémétrie pour les métriques, les événements et les logs transmis aux outils et au tableau de bord de New Relic.
+* Ajout [de limitations et de dépannage pour l'intégration Windows](/docs/kubernetes-pixie/kubernetes-integration/troubleshooting/troubleshooting-windows/)
+* Ajout de l'intégration AWS via [CloudFormation et flux de métriques CloudWatch](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms/), prenant en charge l'API Polling pour les services non pris en charge.
+* Ajout [d'une balise améliorée pour la base de données entité New Relic](/docs/infrastructure/host-integrations/db-entity-tags/) pour le moniteur de base de données entité via l'intégration sur hôte pour MySQL et MS SQL Server, enrichissant les métadonnées informations détaillées et l'organisation dans New Relic sans affecter la facturation ou la télémétrie existante.
+
+### Changements majeurs
+
+* Ajout de fonctions non-agrégateur aux [référencesNRQL ](/docs/nrql/nrql-syntax-clauses-functions/#non-aggregator-functions/).
+* Mise à jour des [exigences de l'agentRuby et du framework pris en charge](/docs/apm/agents/ruby-agent/getting-started/ruby-agent-requirements-supported-frameworks/).
+* Ajout des logs en tant qu'événements New Relic personnalisé (New Relic Custom Events) aux [logs OpenTelemetry dans le document New Relic](/docs/opentelemetry/best-practices/opentelemetry-best-practices-logs/#custom-events).
+* Mise à jour des runtimes pris en charge pour les fonctions Linux, Windows et conteneurisées dans le document [Compatibilité et exigences pour les fonctions Azure instrumentées](/docs/serverless-function-monitoring/azure-function-monitoring/compatibility-requirement-azure-monitoring/#supported-runtimes).
+* Mise à jour des données métriques pour [l'intégration cloudConfluent](/docs/message-queues-streaming/installation/confluent-cloud-integration/#metrics).
+* Suppression de GCP Cloud Run de [la configuration de l'agent Node.js.](/docs/apm/agents/nodejs-agent/installation-configuration/nodejs-agent-configuration/)
+* [Compatibilité et exigences mises à jour pour monitoring de l'IA](/docs/ai-monitoring/compatibility-requirements-ai-monitoring/) pour inclure une bibliothèque supplémentaire prise en charge par l'agent .NET.
+* Ajout du point de terminaison New Relic télémétrie dualstack au [trafic réseau New Relic](/docs/new-relic-solutions/get-started/networks/#new-relic-endpoints).
+* Ajout `GcpHttpExternalRegionalLoadBalancerSample` à l' [intégration de monitoring de Google Cloud Load Balancing](/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-load-balancing-monitoring-integration/).
+* Ajout de la procédure de démarrage OpenShift sur la façon d' [installer le document du gestionnaire de tâches Synthetics](/docs/synthetics/synthetic-monitoring/private-locations/install-job-manager/#-install).
+* Mise à jour de la [version 12 de l'agent Node.js.](/docs/apm/agents/nodejs-agent/installation-configuration/update-nodejs-agent/)
+* Ajout d'une intégration transparente pour [AWS avec New Relic utilisant CloudFormation et le flux de métriques CloudWatch](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms/), y compris la prise en charge de l'interrogation API.
+
+### Modifications mineures
+
+* Ajout `Transaction` comme période de conservation pour [la trace de transaction](/docs/data-apis/manage-data/manage-data-retention/#retention-periods/).
+* Ajout `Destination` comme nouvelle catégorie aux [règles et limites d'alerte](/docs/alerts/admin/rules-limits-alerts/).
+* Ajout d’une légende dans [le document Introduction au service Azure Native New Relic](/docs/infrastructure/microsoft-azure-integrations/get-started/azure-native/) pour garantir que les paramètres de diagnostic sur les ressources Azure sont correctement configurés ou désactiver le transfert via le service Azure Native New Relic pour empêcher l’envoi de données à la plateforme New Relic.
+* Mise à jour de la dernière bibliothèque compatible pour [l'agent .NET](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements/).
+* Ajout d'un appel dans le document [de notes de sortie de l'agent iOS](/docs/release-notes/mobile-release-notes/ios-release-notes/index/) pour annoncer qu'à partir de la version 7.5.4 du SDK iOS, un changement entraîne désormais le signalement d'un événement d'exception gérée précédemment supprimé.
+* Exigences mises à jour pour les relations service-conteneur pour spécifier l'attribut de ressource pour les environnements Kubernetes et `container.id` pour les environnements non-Kubernetes, garantissant configuration de télémétrie appropriée pour [les ressources-OpenTelemetry dans New Relic](/docs/opentelemetry/best-practices/opentelemetry-best-practices-resources/).
+* Ajout de la prise en charge CLI pour l'installation d'une version [d'agent infrastructure spécifique](/docs/infrastructure/infrastructure-agent/new-relic-guided-install-overview/#install-specific-versions), permettant un déploiement cohérent et une compatibilité système ; spécifiez la version à l'aide de `@X.XX.X` dans le nom de la recette.
+* Ajout d'une légende pour souligner les exigences d'accès aux rôles pour l'utilisation des fonctionnalités **Manage Account Cardinality**, **Manage Metric Cardinality** et **Create Pruning Rules** dans l'interface utilisateur ; assurez-vous que les autorisations sont définies dans la [gestion de la cardinalité](/docs/data-apis/ingest-apis/metric-api/cardinality-management/#attributes-table).
+* Mise à jour de la [compatibilité et des exigences pour l'agent Node.js](/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent/) vers `v12.23.0`.
+* Ajout des autorisations minimales requises pour la configuration d'un [Elasticsearch](/docs/infrastructure/host-integrations/host-integrations-list/elasticsearch/elasticsearch-integration).
+* Mise à jour de l'attribut `FACET` utilisation maximale acceptable des limites de 5 000 à 20 000 valeurs pour [la syntaxe d'alerte NRQL](/docs/alerts/create-alert/create-alert-condition/create-nrql-alert-conditions/).
+
+### Notes de version
+
+* Annoncé le 7 janvier 2026 comme date de fin de vie des [règles d'abandon ciblant l'événement infrastructure dans `SystemSample`, `ProcessSample`, `NetworkSample`, et `StorageSample`](/eol/2025/05/drop-rule-filter/)
+
+* À compter d'aujourd'hui, la fin de vie de [FACET sur messageId et horodatage en condition d'alerte](/eol/2025/07/deprecating-alert-conditions/).
+
+* Annoncé le 28 octobre 2025 comme date de fin de vie pour [Attention requise](/eol/2025/07/upcoming-eols/).
+
+* Consultez nos articles Quoi de neuf :
+
+ * [Envoyer une notification directement à Microsoft Teams](/whats-new/2025/03/whats-new-03-13-microsoft-teams-integration/)
+ * [New Relic Compute Optimizer est généralement disponible !](/whats-new/2025/06/whats-new-06-25-compute-optimizer/)
+ * [Logs Cross Account Query dans le Unified Query Explorer](/whats-new/2025/07/whats-new-07-01-logs-uqe-cross-account-query/)
+ * [Monitoring Kubernetes avec OpenTelemetry est généralement disponible !](/whats-new/2025/07/whats-new-7-01-k8s-otel-monitoring/)
+ * [Monitoring des nœuds Windows pour Kubernetes est désormais en version préliminaire publique](/whats-new/2025/07/whats-new-07-04-k8s-windows-nodes-preview/)
+ * [Identifier les problèmes de performances : filtrage avancé des pages vues et des Core Web Vitals](/whats-new/2025/07/whats-new-07-09-browser-monitoring/)
+ * [Vous pouvez désormais trier par erreurs les plus récentes](/whats-new/2025/07/whats-new-7-08-ei-sort-by-newest/)
+ * [Vos données de navigateur, vos termes : Nouvelles options de contrôle](/whats-new/2025/07/whats-new-07-10-browser-monitoring/)
+ * [Analyse approfondie des requêtes pour la base de données désormais généralement disponible](/whats-new/2025/07/whats-new-07-24-db-query-performance-monitoring/)
+ * [Les prévisions NRQL et les alertes prédictives sont désormais disponibles pour tous](/whats-new/2025/07/whats-new-7-22-predictive-analytics/)
+ * [APM + OpenTelemetry Convergence GA](/whats-new/2025/07/whats-new-07-21-apm-otel/)
+ * [L'intégration agentique pour GitHub Copilot et ServiceNow est désormais disponible](/whats-new/2025/07/whats-new-7-15-agentic-ai-integrations/)
+
+* Restez au courant de nos dernières sorties :
+
+ * [Exécution de l'API Node v1.2.119](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.119/)
+ * Problèmes de vulnérabilité résolus.
+
+ * [Ping Runtime v1.51.0](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.119/)
+
+ * Correction des vulnérabilités de logback-core pour l'exécution du ping.
+ * Correction des vulnérabilités du serveur Jetty pour l'exécution du ping.
+ * Correction des vulnérabilités d'Ubuntu pour l'exécution du ping.
+
+ * [Agent Browser v1.292.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.292.0/)
+
+ * Mettre à jour les définitions `BrowserInteraction` et `previousUrl`.
+ * Ajout d'un événement d'inspection supplémentaire.
+ * Valeur API `finished` fixe `timeSinceLoad`.
+
+ * [Intégration Kubernetes v3.42.1](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-42-1/)
+ * Correction des ajustements internes liés au backend et au CI pour la compatibilité future de la plateforme.
+
+ * [Gestionnaire de tâches v444](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-444/)
+ * Correction d'un problème qui empêchait certains clients de voir les résultats de certains moniteurs avec des temps d'exécution plus longs.
+
+ * [Agent Python v10.14.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-101400/)
+
+ * Prise en charge ajoutée pour `Azure Function Apps`.
+ * Correction `pb2` fichiers pour activer la prise en charge `protobuf v6`.
+
+ * [Agent Android v7.6.7](/docs/release-notes/mobile-release-notes/android-release-notes/android-767/)
+
+ * Amélioration des performances pour résoudre les ANR lors du reporting des logs.
+ * Correction d'un problème permettant de continuer à signaler les logs à la fin de l'application.
+ * Résolution d’un problème avec monitoring de l’état de l’application et la transmission des données.
+ * Amélioration de quelques violations lors de l'activation du mode strict.
+
+ * [Intégration Kubernetes v3.42.2](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-42-2/)
+
+ * Mis à jour `golang.org/x/crypto` à `v0.39.0`.
+ * Mis à jour `go` à `v1.24.4`.
+
+ * [Agent .NET v10.42.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-42-0/)
+
+ * Prise en charge ajoutée pour Azure Service Bus.
+ * Correction des erreurs de construction du profileur avec la dernière version de VS.
+
+ * [Agent PHP v11.10.0.24](/docs/release-notes/agent-release-notes/php-release-notes/php-agent-11-10-0-24/)
+
+ * Ajout de l'API d'exécution Composer à utiliser par défaut pour détecter le package utilisé par les applications PHP.
+ * Comportement indéfini corrigé lors de l'exécution de l'API Composer.
+
+ * [Exécution du navigateur de nœuds v3.0.32](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.32/)
+ * Options de création de Chrome mises à jour pour Chrome 131.
+
+ * [Application mobile pour iOS v6.9.8](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6098/)
+ * Amélioration de la fonctionnalité Ask AI avec une connexion socket plus robuste et plus fiable, garantissant une expérience transparente.
+
+ * [Application mobile pour Android v5.29.7](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5297/)
+ * Amélioration de la fonctionnalité Ask AI avec une connexion socket plus robuste et plus fiable, garantissant une expérience transparente.
+
+ * [Agent Node.js v12.22.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-22-0/)
+
+ * Ajout de la prise en charge du streaming `openai` v5.
+ * Prise en charge ajoutée pour l'API `openai.responses.create`.
+ * Logging des erreurs corrigée pour l'en-tête tracestate non défini.
+
+ * [Agent d'infrastructure v1.65.0](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1650/)
+
+ * Mise à jour de la dépendance `newrelic/nri-winservices` à `v1.2.0`
+ * Mise à jour tag docker alpine pour `v3.22`
+
+ * [Agent d'infrastructure v1.65.1](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1651/)
+ * mettre à jour la dépendance `newrelic/nri-flex` vers `v1.16.6`
+
+ * [Agent Browser v1.292.1](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.292.1/)
+ * Correction de la priorité des conditions de course de l'attribut personnalisé.
+
+ * [NRDOT v1.2.0](/docs/release-notes/nrdot-release-notes/nrdot-2025-06-26/)
+ * Le noyau bêta d'OTEL a été augmenté à `v0.128.0`
+
+ * [Agent multimédia pour HTML5.JS v3.0.0](/docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-25-04-15/)
+
+ * Introduction d'un nouveau type d'événement.
+ * Le type d'événement `PageAction` est obsolète.
+
+ * [Agent multimédia pour HTML5.JS v3.1.1](/docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-25-06-15/)
+
+ * Activation de la publication npm pour le package, garantissant une accessibilité et une distribution faciles.
+ * Ajout des builds `cjs`, `esm` et `umd` au dossier `dist`, garantissant la compatibilité avec les formats de modules CommonJS, ES et UMD.
+
+ * [Agent multimédia pour Roku v4.0.0](/docs/release-notes/streaming-others-release-notes/streaming-others-agent-25-02-25/)
+
+ * Introduction d'un nouveau type d'événement.
+ * Le type d'événement `RokuVideo` est obsolète.
+ * Le type d'événement `RokuSystem` est obsolète.
+
+ * [Agent multimédia pour Roku v4.0.1](/docs/release-notes/streaming-others-release-notes/streaming-others-agent-25-04-22/)
+ * Renommer `errorName` avec `errorMessage` en `errorName` est obsolète.
+
+ * [Gestionnaire de tâches v447](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-447/)
+ * Mise à niveau de l'image de base fixe de `ubuntu 22.04` à `ubuntu 24.4`
+
+ * [Ping Runtime v1.52.0](/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.52.0/)
+ * Mise à niveau de l'image de base améliorée de `ubuntu 22.04` à `ubuntu 24.04`
+
+ * [Intégration Kubernetes v3.43.0](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-43-0/)
+ * Ajout de la prise en charge de monitoring des nœuds Windows dans le cluster Kubernetes.
+
+ * [Application mobile pour Android v5.29.8](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5298/)
+ * Bug corrigé et interface utilisateur améliorée pour une expérience plus fluide.
+
+ * [Agent Node.js v12.23.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-23-0/)
+
+ * Ajout de la possibilité de générer des rapports uniquement sur les portées d'entrée et de sortie.
+ * Prise en charge de Node.js 24 ajoutée.
+ * Rapport de compatibilité mis à jour.
+
+ * [Exécution de l'API Node v1.2.120](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.120/)
+ * Correction des vulnérabilités pour `CVE-2024-39249`
+
+ * [Application mobile pour iOS v6.9.9](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6099/)
+ * Amélioration de la fonctionnalité Ask AI avec une invite dynamique.
+
+ * [Agent Browser v1.293.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.293.0/)
+
+ * Ajout d'un message interne **sur les tâches longues**.
+ * Problème résolu empêchant la désactivation des traces distribuées.
+
+ * [Exécution du navigateur de nœuds v3.0.35](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.35/)
+ * Image de base améliorée
+
+ * [Agent Java v8.22.0](/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8220/)
+
+ * Métadonnées liées pour les services Azure App.
+ * Suppression de l'instrumentation `MonoFlatMapMain`.
+
+ * [Agent Node.js v12.24.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-24-0/)
+
+ * Limite de taille de valeur d'attribut configurable implémentée
+ * Rapport de compatibilité mis à jour.
+
+ * [Intégration Kubernetes v3.43.2](docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-43-2/)
+ * Mettre à jour la version du graphique kube-state-métriques de `5.12.1` vers `5.30.1`
+
+ * [Agent iOS v7.5.7](/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-757/)
+ * 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.
+
+ * [Application mobile pour Android v5.29.9](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5299/)
+ * Amélioration des commentaires avec un rendu d'interface utilisateur dynamique.
+
+ * [Application mobile pour Android v5.30.0](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-53000/)
+ * Correction de bugs et mise à jour des indicateurs Teams GA pour une expérience utilisateur améliorée.
+
+ * [Agent Go v3.40.1](/docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-40-1/)
+
+ * Utilisation annulée. Retour à la version 3.39.0 sortie en raison d'un bug de blocage
+ * Suppression des tests awssupport\_test.go qui ajoutaient une dépendance directe au module go
+
+ * [Agent Flutter v1.1.12](/docs/release-notes/mobile-release-notes/flutter-release-notes/flutter-agent-1112/)
+
+ * Amélioration de l'agent Android natif mis à jour vers la version 7.6.7
+ * Amélioration de l'agent iOS natif mis à jour vers la version 7.5.6
+
+ * [Agent Node.js v13.0.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-0-0/)
+
+ * Suppression du support pour Node.js 18
+ * Version minimale prise en charge mise à jour pour `fastify` vers 3.0.0, `pino` à 8.0.0 et `koa-router` à 12.0.0
+
+ * [Agent Browser v1.294.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.294.0/)
+ * Rapport fixe vide previousUrl comme non défini
+
+ * [Agent d'infrastructure v1.65.4](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1654/)
+ * Mise à jour de la dépendance `newrelic/nri-prometheus` vers la version 2.26.2
+
+ * [Application mobile pour iOS v6.9.10](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6100/)
+ * Amélioration des commentaires avec un rendu d'interface utilisateur dynamique.
+
+ * [Agent Android NDK v1.1.3](/docs/release-notes/mobile-release-notes/android-release-notes/android-ndk-113/)
+ * Ajout de la prise en charge de la taille de page de 16 Ko
+
+ * [Agent d'infrastructure v1.65.3](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1653/)
+
+ * Modification du handle de processus Windows.
+ * Remonté `nri-docker` à `v2.5.1`, `nri-prometheus` à `v2.26.1`
+
+ * [Agent .NET v10.43.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-43-0/)
+ * Ajout de la prise en charge des rubriques dans Azure Service Bus
+
+ * [Agent Node.js v12.25.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-25-0/)
+ * API AWS Bedrock Converse à instrument fixe
+
+ * [Agent Node.js v12.24.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-24-0/)
+
+ * Limite de taille de valeur d'attribut configurable implémentée
+ * Rapport de compatibilité mis à jour
+
+ * [CLI de diagnostic (nrdiag) v3.4.0](/docs/release-notes/diagnostics-release-notes/diagnostics-cli-release-notes/diagnostics-cli-340/)
+ * Les erreurs liées à GLIBC fixes telles que `/lib64/libc.so.6: version 'GLIBC_2.34'` introuvable ont été résolues
\ 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/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.298.mdx b/src/i18n/content/fr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.298.mdx
new file mode 100644
index 00000000000..389ac9b5e39
--- /dev/null
+++ b/src/i18n/content/fr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.298.mdx
@@ -0,0 +1,34 @@
+---
+subject: Browser agent
+releaseDate: '2025-09-19'
+version: 1.298.0
+downloadLink: 'https://www.npmjs.com/package/@newrelic/browser-agent'
+features:
+ - Factor long tasks into soft nav base interaction span
+bugs:
+ - Force LCP to report the original page URL
+security: []
+translationType: machine
+---
+
+## v1.298.0
+
+### Caractéristiques
+
+#### Intégrer les tâches longues dans la durée d'interaction de la base de navigation souple
+
+`BrowserInteraction` sous navigation douce (« SPA 2.0 »), la durée s'étendra au-delà du temps de modification du DOM jusqu'au point où aucune tâche longue n'a été observée pendant 5 secondes. `JavascriptError` et `AjaxRequest` ne sont pas encore associés à une telle interaction pendant cette période prolongée au-delà de la fin de l'heuristique d'origine.
+
+### Débogage
+
+#### Forcer LCP à signaler l'URL de la page d'origine
+
+Autoriser LCP à signaler son URL de page distinctement de l'URL de récolte. Un problème a été observé où les navigations souples se produisant avant la récolte LCP signalaient l'URL de la page actuelle au lieu de l'URL de la page d'origine liée à LCP. Cette modification permet aux nœuds de récolte LCP de signaler l’URL d’origine, quelle que soit l’URL de la page actuelle. Le changement doit s’appliquer à la fois aux attributs `pageUrl` et `targetGroupedUrl`.
+
+## 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.298.0 de l'agent 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.298.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/nrdot-release-notes/nrdot-2025-09-18.mdx b/src/i18n/content/fr/docs/release-notes/nrdot-release-notes/nrdot-2025-09-18.mdx
new file mode 100644
index 00000000000..6e8ba0066e6
--- /dev/null
+++ b/src/i18n/content/fr/docs/release-notes/nrdot-release-notes/nrdot-2025-09-18.mdx
@@ -0,0 +1,16 @@
+---
+subject: NRDOT
+releaseDate: '2025-09-18'
+version: 1.4.0
+metaDescription: Release notes for NRDOT Collector version 1.4.0
+translationType: machine
+---
+
+## Log des modifications
+
+### Caractéristiques
+
+* exploit : ajout de spanprocessor à nrdot-collecteur (#371)
+* exploit : augmentation des versions des composants de l'hôtel de la v0.131.0 à la v0.132.0 (#368)
+* exploit : ajouter newrelic.service.type à la configuration de télémétrie interne (#380)
+* exploit : activer la détection du nom d'hôte pour ec2 (#382)
\ No newline at end of file
diff --git a/src/i18n/content/fr/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-467.mdx b/src/i18n/content/fr/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-467.mdx
new file mode 100644
index 00000000000..7e3ae860676
--- /dev/null
+++ b/src/i18n/content/fr/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-467.mdx
@@ -0,0 +1,10 @@
+---
+subject: Job Manager
+releaseDate: '2025-09-22'
+version: '467'
+translationType: machine
+---
+
+### Corrections
+
+* Correction de CVE-2025-58056, CVE-2025-58057 et des vulnérabilités Ubuntu sous-jacentes pour résoudre les vulnérabilités de sécurité dans sjm.
\ 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/apis/nerdgraph/examples/nerdgraph-issues-api-via-github.mdx b/src/i18n/content/jp/docs/apis/nerdgraph/examples/nerdgraph-issues-api-via-github.mdx
index 5a3fc15c967..d22edfae610 100644
--- a/src/i18n/content/jp/docs/apis/nerdgraph/examples/nerdgraph-issues-api-via-github.mdx
+++ b/src/i18n/content/jp/docs/apis/nerdgraph/examples/nerdgraph-issues-api-via-github.mdx
@@ -663,7 +663,7 @@ New Relic のデータ型の詳細については、こちらをご覧くださ
```graphql
{
- currentUser {
+ actor {
account(id: ACCOUNT_ID) {
aiIssues {
issues {
@@ -685,7 +685,7 @@ New Relic のデータ型の詳細については、こちらをご覧くださ
```json
{
"data": {
- "currentUser": {
+ "actor": {
"account": {
"aiIssues": {
"issues": {
@@ -724,7 +724,7 @@ New Relic のデータ型の詳細については、こちらをご覧くださ
```graphql
{
- currentUser {
+ actor {
account(id: YOUR_ACCOUNT_ID) {
aiIssues {
issues(cursor: "") {
@@ -747,7 +747,7 @@ New Relic のデータ型の詳細については、こちらをご覧くださ
```json
{
"data": {
- "currentUser": {
+ "actor": {
"account": {
"aiIssues": {
"issues": {
@@ -791,7 +791,7 @@ New Relic のデータ型の詳細については、こちらをご覧くださ
```graphql
{
- currentUser {
+ actor {
account(id: YOUR_ACCOUNT_ID) {
aiIssues {
issues(cursor: "=ATN") {
@@ -840,7 +840,7 @@ New Relic のデータ型の詳細については、こちらをご覧くださ
```graphql
{
- currentUser {
+ actor {
account(id: YOUR_ACCOUNT_ID) {
aiIssues {
issues(filter: {priority: "CRITICAL", states: CLOSED}) {
@@ -863,7 +863,7 @@ New Relic のデータ型の詳細については、こちらをご覧くださ
```json
{
"data": {
- "currentUser": {
+ "actor": {
"account": {
"aiIssues": {
"issues": {
@@ -1066,7 +1066,7 @@ New Relic のデータ型の詳細については、こちらをご覧くださ
```graphql
{
- currentUser {
+ actor {
account(id: YOUR_ACCOUNT_ID) {
aiIssues {
issuesEvents {
@@ -1089,7 +1089,7 @@ New Relic のデータ型の詳細については、こちらをご覧くださ
```json
{
"data": {
- "currentUser": {
+ "actor": {
"account": {
"aiIssues": {
"issuesEvents": {
@@ -1160,7 +1160,7 @@ New Relic のデータ型の詳細については、こちらをご覧くださ
```graphql
{
- currentUser {
+ actor {
account(id: YOUR_ACCOUNT_ID) {
aiIssues {
issuesEvents(filter: {ids: "fe0d512f-36c7-4b7a-8a80-4c47c040807a"}) {
@@ -1186,7 +1186,7 @@ New Relic のデータ型の詳細については、こちらをご覧くださ
```json
{
"data": {
- "currentUser": {
+ "actor": {
"account": {
"aiIssues": {
"issuesEvents": {
@@ -1264,7 +1264,7 @@ New Relic のデータ型の詳細については、こちらをご覧くださ
```graphql
{
- currentUser {
+ actor {
account(id: YOUR_ACCOUNT_ID) {
aiIssues {
incidents {
@@ -1293,7 +1293,7 @@ New Relic のデータ型の詳細については、こちらをご覧くださ
```json
{
"data": {
- "currentUser": {
+ "actor": {
"account": {
"aiIssues": {
"incidents": {
@@ -1404,7 +1404,7 @@ New Relic のデータ型の詳細については、こちらをご覧くださ
```graphql
{
- currentUser {
+ actor {
account(id: YOUR_ACCOUNT_ID) {
aiIssues {
incidents(filter: {priority: "CRITICAL", states: CREATED}) {
@@ -1434,7 +1434,7 @@ New Relic のデータ型の詳細については、こちらをご覧くださ
```json
{
"data": {
- "currentUser": {
+ "actor": {
"account": {
"aiIssues": {
"incidents": {
@@ -1502,7 +1502,7 @@ New Relic のデータ型の詳細については、こちらをご覧くださ
```graphql
{
- currentUser {
+ actor {
account(id: YOUR_ACCOUNT_ID) {
aiIssues {
incidents(filter: {ids: "97373770-caad-46cd-a69d-a358de3be090"}) {
@@ -1532,7 +1532,7 @@ New Relic のデータ型の詳細については、こちらをご覧くださ
```json
{
"data": {
- "currentUser": {
+ "actor": {
"account": {
"aiIssues": {
"incidents": {
@@ -1573,7 +1573,7 @@ New Relic のデータ型の詳細については、こちらをご覧くださ
```graphql
{
- currentUser {
+ actor {
account(id: YOUR_ACCOUNT_ID) {
aiIssues {
incidentsEvents {
@@ -1597,7 +1597,7 @@ New Relic のデータ型の詳細については、こちらをご覧くださ
```json
{
"data": {
- "currentUser": {
+ "actor": {
"account": {
"aiIssues": {
"incidentsEvents": {
@@ -1664,7 +1664,7 @@ New Relic のデータ型の詳細については、こちらをご覧くださ
```graphql
{
- currentUser {
+ actor {
account(id: YOUR_ACCOUNT_ID) {
aiIssues {
incidentsEvents(filter: {ids: "cd512082-6ebe-46ac-a6dc-d387dc86dc80"}) {
@@ -1694,7 +1694,7 @@ New Relic のデータ型の詳細については、こちらをご覧くださ
```json
{
"data": {
- "currentUser": {
+ "actor": {
"account": {
"aiIssues": {
"incidentsEvents": {
@@ -1749,7 +1749,7 @@ Issues サービスには、いくつかの構成パラメーターがありま
```graphql
{
- currentUser {
+ actor {
account(id: YOUR_ACCOUNT_ID) {
aiIssues {
configByEnvironment {
@@ -1772,7 +1772,7 @@ Issues サービスには、いくつかの構成パラメーターがありま
```json
{
"data": {
- "currentUser": {
+ "actor": {
"account": {
"aiIssues": {
"configByEnvironment": {
@@ -1963,7 +1963,7 @@ Issues サービスには、いくつかの構成パラメーターがありま
```graphql
{
- currentUser {
+ actor {
account(id: YOUR_ACCOUNT_ID) {
aiIssues {
issues {
diff --git a/src/i18n/content/jp/docs/browser/browser-monitoring/browser-pro-features/session-replay/additional-information.mdx b/src/i18n/content/jp/docs/browser/browser-monitoring/browser-pro-features/session-replay/additional-information.mdx
index ac087385102..7bcac6ae635 100644
--- a/src/i18n/content/jp/docs/browser/browser-monitoring/browser-pro-features/session-replay/additional-information.mdx
+++ b/src/i18n/content/jp/docs/browser/browser-monitoring/browser-pro-features/session-replay/additional-information.mdx
@@ -45,7 +45,7 @@ New Relic GDPRの下ではデータ プロセッサとして、CCPA の下では
* 戦略的なペイロード収集: 大きな (圧縮された) ペイロードは、完全な DOM がキャプチャされた場合にのみ送信されます。これは通常、再生機能が最初にインポートされたときに発生します。 その後、ユーザーのアクションに関連する小さなペイロードのみが送信されます。 ブラウザエージェントは、次の条件の最初の発生に基づいてデータを収集します。
- * ペイロードは圧縮すると 64 KB を超えます。
- * 60秒が経過します。
+ * ペイロードは圧縮すると 16 kB を超えます。
+ * 30秒が経過します。
* ページの可視性が変更されます (例: タブの変更、フォーカス、ナビゲーション)。
* セッションが終了します。
\ No newline at end of file
diff --git a/src/i18n/content/jp/docs/browser/new-relic-browser/lab/debug-slowness.mdx b/src/i18n/content/jp/docs/browser/new-relic-browser/lab/debug-slowness.mdx
index 64eff37a5c0..e2396cf77c3 100644
--- a/src/i18n/content/jp/docs/browser/new-relic-browser/lab/debug-slowness.mdx
+++ b/src/i18n/content/jp/docs/browser/new-relic-browser/lab/debug-slowness.mdx
@@ -5,22 +5,15 @@ freshnessValidatedDate: never
translationType: machine
---
-
- この手順は、New Relic を使用して Web アプリのトラブルシューティングを行う方法を説明するラボの一部です。
+
+ この手順は、New Relic を使用して Web アプリのトラブルシューティングを行う方法を説明するラボの一部です。
- ラボの各手順は最後の手順に基づいているため、この手順を開始する前に、最後の手順 [_であるアプリケーションのエラーをデバッグするを_](/docs/browser/new-relic-browser/lab/debug-errors)完了していることを確認してください。
+ ラボの各手順は最後の手順に基づいているため、この手順を開始する前に、最後の手順 [*であるアプリケーションのエラーをデバッグするを*](/docs/browser/new-relic-browser/lab/debug-errors)完了していることを確認してください。
アプリケーションの JavaScript エラーを修正した後、あなたとあなたのチームは自信を持っています。ダウンタイムの準備ができて、ソーシャル メディアに向かいますが、Twitter をチェックすると、混乱している顧客が何人かいます。
-
+
ええとああ！あなたの顧客は幸せそうに見えません。New Relic ブラウザー監視を使用して、遅延の原因を発見する時が来ました。
@@ -36,29 +29,17 @@ translationType: machine
New Relic ホームページから**Browser**に移動し、 **Relicstaurants**アプリケーションを選択します。
- 
+
ここには、**Page views with JavaScript errors**、**Core web vitals**、**User time on the site**、**Initial page load and route changes** などを含む、 browserアプリケーションに関連するすべてのデータが表示されます。
- 
+
**largest contentful paint (LCP)**に注目してください。
- 
+
最大コンテンツフル ペイント (LCP) は、Web ページのメイン コンテンツが読み込まれる速度を表します。 理想的には、コンテンツの読み込みに 1 ～ 2 秒以上かかることはありません。 ここでは、サイトの読み込みに 5 秒以上かかっていることがわかります。 ユーザーが不満を言うのも不思議ではありません。
@@ -68,29 +49,17 @@ translationType: machine
下にスクロールして、 **Front end vs. back end**グラフに注目してください。
- 
+
**Back end (time to first byte) (50%)**をクリックしてグラフをフィルタリングし、バックエンドの読み込みにかかる時間を確認します。
- 
+
- このグラフは、最悪の場合、バックエンドがリクエストを処理するのに最大 140 ミリ秒かかったことを示しています。これは、フロントエンドが遅延を引き起こしているということですか?
+ グラフは、最悪の場合、バックエンドがリクエストを処理するのに最大 140 ミリ秒かかったことを示しています。これはフロントエンドが遅延を引き起こしていることを意味しますか?
**Front end (Window load + AJAX) (50%)**をクリックします。
- 
+
そこで問題です！グラフは、遅延がフロントエンドで発生していることを示しています。
@@ -98,21 +67,13 @@ translationType: machine
フロントエンドでの遅延の原因を絞り込むには、 **Initial page load and route change**グラフを詳しく見てください。
- 
+
**Initial page load (Window load + AJAX)**をクリックします。
- 
+
グラフは、 **Initial page load (Window load + AJAX)**に 5 ～ 6 秒かかっていることを示しており、これは憂慮すべきことです。
@@ -120,53 +81,29 @@ translationType: machine
詳細を表示するには、 **Initial page load and route change**をクリックしてください。
- 
+
これにより、 **Page views**に移動します。
- 
+
ページを**Most time-consuming**で並べ替えます。
- 
+
最初のページの読み込みに約 90% の時間がかかっていることに注意してください。
- 
+
それをクリックして詳細を表示します。
- 
+
このページには、 **Page view breakdown** 、 **Median initial page load time** 、およびその他の重要な詳細が表示されます。 **Page view breakdown**グラフは、ページに時間がかかる理由と場所を絞り込むのに役立つため、ここでは特に重要です。 このグラフを詳しく見ると、 **Page rendering** 5000 ミリ秒もの時間がかかっていることがわかります。
- 
+
最初のページのレンダリングにかなりの時間がかかり、アプリケーションが遅くなっていることがわかりました。 次に、 **Session traces**を観察して、レンダリング プロセスを遅らせている原因を特定します。
@@ -176,31 +113,19 @@ translationType: machine
左側のナビゲーションから**Session traces**に移動し、 **Page load**の降順に並べ替えます。
- 
+
ここでは、セッショントレースが**Page load**時間の順に並べ替えられていることがわかります。
- 
+
リストから、最初のものをクリックします。
- 
+
@@ -208,51 +133,31 @@ translationType: machine
ここでは、その特定のセッションの完全なトレースが表示されます。 このページには、 **Backend** 、 **Dom Processing** 、 **Page Load** 、およびその他のトレース関連情報も表示されます。
- 
+
**Page load**には予想より時間がかかっていることに注意してください。 負荷の詳細なタイムラインが必要です。 ポインタを左右にスクロールしてタイムラインを調整します。
- 
+
トレースをスクロールしてタイム ウィンドウを移動し、このセッション中の個々のイベントの詳細を確認します。
- 
+
特定のイベントに 5 秒以上かかっていることに注意してください。
- 
+
イベントをクリックすると詳細が表示されます。
- 
+
イメージですのでご了承ください。特に、読み込みに 5 ～ 6 秒かかり、遅延の原因となっているのはアプリケーションの背景画像です。
@@ -272,4 +177,4 @@ translationType: machine
素晴らしい！モニタリングをすぐに開始できるようになったので、ジャーニーの次のステップに進むのに役立つドキュメントをいくつか紹介します。
* [Browserモニタリングの概要](/docs/browser/browser-monitoring/getting-started/introduction-browser-monitoring/)
-* [ブラウザ監視機能](/docs/browser/new-relic-browser/browser-pro-features/intro-to-browser-pro-features)
+* [ブラウザ監視機能](/docs/browser/new-relic-browser/browser-pro-features/intro-to-browser-pro-features)
\ No newline at end of file
diff --git a/src/i18n/content/jp/docs/browser/new-relic-browser/performance-quality/browser-monitoring-performance-impact.mdx b/src/i18n/content/jp/docs/browser/new-relic-browser/performance-quality/browser-monitoring-performance-impact.mdx
index 8cae7bf4bf3..add9555cc65 100644
--- a/src/i18n/content/jp/docs/browser/new-relic-browser/performance-quality/browser-monitoring-performance-impact.mdx
+++ b/src/i18n/content/jp/docs/browser/new-relic-browser/performance-quality/browser-monitoring-performance-impact.mdx
@@ -96,7 +96,7 @@ JavaScriptのオーバーヘッドは、ユーザーへの影響とお客様の
### ブラウザエージェントのハーベスト [#agent-harvests]
-Browser events are first harvested after the PageView event is successfully collected, and then every 30 seconds thereafter. If any event type exceeds 16 kB of data before the next scheduled harvest, an early harvest is triggered for that event. Additionally, a final harvest occurs whenever the document transitions to `hidden` via a `visibilitychange` event (e.g. when a user navigates away, switches tabs, closes the tab, minimizes or closes the browser, or switches from the browser to another app if they're on a mobile device).
+Browserイベントは、PageView イベントが正常に収集された後に最初に収集され、その後は 30 秒ごとに収集されます。 次回のスケジュールされた収集の前に、いずれかのイベント タイプが 16 KB のデータを超えると、そのイベントに対して早期収集がトリガーされます。さらに、ドキュメントが`visibilitychange`イベントを介して`hidden`に遷移するたびに、最終的な収集が行われます (たとえば、ユーザーが別の場所に移動したり、タブを切り替えたり、タブを閉じたり、ブラウザを最小化または閉じたり、モバイル デバイスの場合はブラウザから別のアプリに切り替えたりしたときなど)。
@@ -164,7 +164,7 @@ Browser events are first harvested after the PageView event is successfully coll
|
- `PageViewTiming` events are harvested by all agents and includes timing data like core web vitals measurements. See the [PageViewTiming docs](/docs/browser/new-relic-browser/page-load-timing-resources/pageviewtiming-async-or-dynamic-page-details/#interactivity-metrics) for a list of reported events.
+ `PageViewTiming` イベントはすべてのエージェントによって収集され、コアウェブバイタル測定などのタイミング データが含まれます。 報告されたイベントのリストについては、 [PageViewTiming のドキュメントを](/docs/browser/new-relic-browser/page-load-timing-resources/pageviewtiming-async-or-dynamic-page-details/#interactivity-metrics)参照してください。
|
@@ -186,7 +186,7 @@ Browser events are first harvested after the PageView event is successfully coll
- `JavaScriptError` metrics are sent together with Ajax metrics as timeslice data.
+ `JavaScriptError` メトリクスは、Ajax メトリクスとともに時間区切りデータとして送信されます。
|
@@ -230,7 +230,7 @@ Browser events are first harvested after the PageView event is successfully coll
- `AjaxRequest` events follows the 30 seconds harvest cycle unless the `SPA` agent is in use. If using the `SPA` agent, the first harvest will happen after the `load` page lifecycle event and additional harvests will either happen every 30 seconds or when the `SPA` agent notices a route change.
+ `AjaxRequest` `SPA`エージェントが使用されていない限り、イベントは 30 秒の収集サイクルに従います。`SPA`エージェントを使用する場合、最初の収集は`load`ページ ライフサイクル イベントの後に行われ、追加の収集は 30 秒ごとに、または`SPA`エージェントがルートの変更を認識したときに行われます。
|
@@ -252,7 +252,7 @@ Browser events are first harvested after the PageView event is successfully coll
- Session traces can generate a large amount of data, but that can be controlled by sampling. By default, only about 90 page views per hour will be sampled to send session trace data. There is also an option to set a custom sampling rate.
+ セッションレースは大量のデータを生成する可能性がありますが、それはサンプリングによって制御できます。 デフォルトでは、セッショントレース データを送信するためにサンプリングされるのは 1 時間あたり約 90 ページ ビューだけです。 カスタム サンプリング レートを設定するオプションもあります。
|
@@ -274,7 +274,7 @@ Browser events are first harvested after the PageView event is successfully coll
- In addition to the the general harvest cycles, session replay harvests that include snapshots and metadata payloads will be harvested immediately.
+ 一般的な収集サイクルに加えて、スナップショットやメタデータ ペイロードを含むセッションリプレイの収集もすぐに収集されます。
エンドポイントはロケールによって異なる場合がありますが、米国の例では`https://bam.nr-data.net/browser/blobs`になります。
|
@@ -318,13 +318,13 @@ Browser events are first harvested after the PageView event is successfully coll
- `BrowserInteraction` events are harvested immediately after the interaction finishes. There will always be at least one interaction that represents the initial page load. Additional interactions are collected only if the URL changes (representing route change). `AjaxRequest` events are also harvested at the same time if they occur during an interaction.
+ `BrowserInteraction` イベントは、インタラクションの終了直後に収集されます。最初のページ読み込みを表すインタラクションが常に少なくとも 1 つ存在します。追加のインタラクションは、URL が変更された (ルートの変更を表す) 場合にのみ収集されます。インタラクション中に発生した場合、 `AjaxRequest`イベントも同時に収集されます。
|
|
- Browser logs
+ ブラウザログ
|
@@ -344,7 +344,7 @@ Browser events are first harvested after the PageView event is successfully coll
|
|
- [UserAction](/attribute-dictionary/?event=UserAction) events
+ [UserAction](/attribute-dictionary/?event=UserAction)イベント
|
@@ -364,7 +364,7 @@ Browser events are first harvested after the PageView event is successfully coll
|
|
- [BrowserPerformance](/attribute-dictionary/?event=BrowserPerformance) events
+ [ブラウザパフォーマンス](/attribute-dictionary/?event=BrowserPerformance)イベント
|
diff --git a/src/i18n/content/jp/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/manual.mdx b/src/i18n/content/jp/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/manual.mdx
new file mode 100644
index 00000000000..0af26ab924f
--- /dev/null
+++ b/src/i18n/content/jp/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/manual.mdx
@@ -0,0 +1,72 @@
+---
+title: AWSコンソールから手動で統合する
+tags:
+ - Integrate manually
+ - Manual integration
+ - AWS metric integration
+ - Amazon integrations
+ - AWS integrations
+metaDescription: Integrate New Relic with AWS services manually from the AWS console.
+freshnessValidatedDate: never
+translationType: machine
+---
+
+AWSアカウントとNew Relicをシームレスに統合するには、 [CloudFormation および CloudWatch Metric Streams を介した](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation)統合が最も推奨されるアプローチです。 CloudFormation テンプレートを使用できず、Terraform を使用したくない場合は、次の手順を参照して AWS コンソールから手動で統合してください。
+
+## 前提条件 [#prerequisites]
+
+AWS アカウントと New Relic の統合を開始する前に、次の前提条件を満たしていることを確認してください。
+
+* **New Relic[Ingest \[の取り込み\] - ライセンスキーとユーザー キー](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]
+
+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**： Manually integrate your AWS account
+
+5. **Select services**画面で、必要に応じて**Show resources not supported by CloudWatch Metric Streams**トグルを使用して、モニターするサービスを選択し、続行します。
+
+6. **Choose data integration type**画面で、次の統合オプションから選択します。
+
+ * **突然AWS監視 (推奨)** : このオプションはCloudWatch Metric Streamsをサポートするサービス用です。
+ * **APIポーリング**: このオプションはCloudWatch Metric Streamsでサポートされていないサービスに適しています。
+
+7. **Create role**ページから**Configure budgets policy**ページまで、画面上の指示に従って AWS コンソールで手順を実行します。
+
+8. AWSコンソールでポリシーを作成した後、 New Relicプラットフォームに切り替え、 New RelicにAWSデータが表示されるまでガイド付き統合を続行します。
+
+## 関連トピック [#related-topics]
+
+
+
+ 複数の AWS アカウントからデータを収集する方法を学びます。
+
+
+
+ CloudWatch メトリック ストリームからメトリクスを探索して使用します。
+
+
+
+ CloudFormation とCloudWatch Metric Streamsを使用して、 AWSサービスをNew Relicと統合します。
+
+
+
+ CloudFormation とAPIポーリングを使用して、 AWSサービスをNew Relicと統合します。
+
+
+
+ Terraform を使用してAWSサービスをNew Relicと統合します。
+
+
\ No newline at end of file
diff --git a/src/i18n/content/jp/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/migrate-from-api-polling-to-cwms.mdx b/src/i18n/content/jp/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/migrate-from-api-polling-to-cwms.mdx
new file mode 100644
index 00000000000..3a41167f2f0
--- /dev/null
+++ b/src/i18n/content/jp/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/migrate-from-api-polling-to-cwms.mdx
@@ -0,0 +1,111 @@
+---
+title: APIポーリングからCloudWatch Metric Streamsへの移行
+tags:
+ - API polling to CWMS migration
+metaDescription: Migrate your New Relic and AWS services integration type from API Polling to CloudWatch Metric Streams.
+freshnessValidatedDate: never
+translationType: machine
+---
+
+AWSアカウントとNew Relicをシームレスに統合するには、 [CloudFormation および CloudWatch Metric Streams を介した](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation)統合が最も推奨されるアプローチです。 ただし、 APIポーリングを使用してAWSアカウントをNew Relicとすでに統合している場合は、次の手順を参照してAPIポーリングからCloudWatch Metric Streamsに移行してください。
+
+## 前提条件 [#prerequisites]
+
+AWS アカウントと New Relic の統合を開始する前に、次の前提条件を満たしていることを確認してください。
+
+* **New Relic[Ingest \[の取り込み\] - ライセンスキーとユーザー キー](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アカウントにはこれらの権限が必要です。
+* 複数の AWS アカウントを管理するユーザーの場合は、[各アカウントを 1 つの New Relic アカウントに接続します](/docs/infrastructure/amazon-integrations/manage-aws-data/aws-multi-account)。
+* これらのアカウント内で複数のリージョンを管理するユーザーの場合は、リージョンごとに New Relic を指す個別の Kinesis Data Firehose を作成する必要があります。
+
+
+
+ ## CloudWatch Metric Streams統合への移行 [#migrate]
+
+ APIポーリングから移行するには、CloudFormation テンプレートを作成するか、 AWSアカウントを再追加してアプリ内のガイド付きインストール手順に従う必要があります。 最も効率的な移行方法であるため、CloudFormation テンプレート方式を使用することをお勧めします。これらの統合はCloudWatch Metric Streamsではサポートされていないため、統合に移行できません。
+
+ * AWS CloudTrail
+ * AWS Health
+ * AWS Trusted Advisor
+ * AWS X-Ray
+
+ これらの統合を使用する場合でも、 APIポーリング方式を使用する必要があります。
+
+
+
+ CloudFormation テンプレートを使用すると、ポーリング設定に基づいて事前設定されたネームスペースでテンプレートを更新できます。
+
+ 1. **[one.newrelic.com > Infrastructure > AWS](https://one.newrelic.com/infra/infrastructure/cloud-aws)**に移動し、 **Migrate to CloudWatch Metric stream**クリックします。
+ 2. 手順に従ってください。テンプレートをダウンロードし、 APIポーリングからネームスペースを複製します。 ダウンロードしたテンプレートにアカウントの詳細を必ず追加してください。
+ 3. AWS Consoleから**Cloud Formation > Create Stack > Upload a template file**に移動します。 更新された CloudFormation テンプレートをアップロードします。
+
+
+
+ CloudFormation 方式を使用しない場合は、すでにAWSアカウントをポーリングインテグレーションにリンクしている場合でも、 AWSアカウントを再度追加する必要があります。 これらの手順により、このドキュメントから離れる必要があるかもしれませんが、ポーリング統合を無効にするために戻ってください。
+
+ 1. **[one.newrelic.com > All capabilities >Infrastructure > AWS](https://one.newrelic.com/infra/infrastructure/cloud-aws)**に移動し、 **Add AWS account**をクリックします。方法を選択してください。
+ 2. このドキュメントのAWS Console[フローのAWS Console](/install/aws-cloudwatch/?task=console)手順に従います。
+ 3. 以前のAWSプロバイダー アカウントでの[不要なポーリング統合をすべて無効にします](/docs/infrastructure/amazon-integrations/connect/uninstall-aws/)。
+
+ 無効にする場合は、 [一部の統合がCloudWatch Metric Streamsでサポートされない](/docs/infrastructure/amazon-integrations/connect/connect-aws-new-relic-infrastructure-monitoring/)ことに注意してください。
+
+
+
+ CloudWatch Metric Streams統合は、メトリクスAPIを使用して、メトリクスを[次元メトリクス](/docs/data-apis/understand-data/new-relic-data-types/#dimensional-metrics)形式でプッシュします。 一方、 APIポーリング方式は[イベント](/docs/data-apis/understand-data/new-relic-data-types/#events-new-relic)に基づいてメトリクスをプッシュします。
+
+ * 移行を支援するために、あらゆる形式でクエリを透過的に記述できるシミング メカニズムを提供します。これらの書き込みは、イベントからメトリクス、またはメトリクスからイベントのいずれかで、利用可能なソースに基づいて期待どおりに処理されます。
+ * CloudWatch Metric Streams 統合でイベントベースの書き込みを使用できるようにするシミング メカニズムに関する[いくつかの制限](/docs/query-your-data/nrql-new-relic-query-language/nrql-query-tutorials/query-infrastructure-dimensional-metrics-nrql/#known-limitations)を確認することをお勧めします。
+
+ 移行後、API ポーリング データに依存する一部の New Relic 機能の動作が異なる場合があります。
+
+ * **Dashboards**: 投票ベースのAWSインテグレーション イベントを使用するカスタムダッシュボードは引き続き期待どおりに機能します。
+ * **Alerts**: ポーリングベースの AWS イベントを使用するアラート条件は引き続き機能します。これらを、 NRQLソースとして使用する次元メトリクス形式に適合させることをお勧めします。
+ * **Entities**：モニターエンティティのリストには、重複したエンティティが最大24時間表示される場合があります
+ * **Attributes**：ポーリングベースのAWS統合では、収集されたリソースタグに`label.`プレフィックスが付けられましたが、Amazon CloudWatch Metric Streams統合では、収集されたリソースタグに`tags.`プレフィックスが付けられました。同じAWSアカウントに対して両方の統合が有効になっている場合、イベント形式を使用すると、リソースタグが両方のプレフィックスの下に表示されます
+
+
+
+ ## データの検証 [#validate-data]
+
+ メトリック ストリームからデータを受信していることを確認するには、次の手順に従います。
+
+ 1. **[one.newrelic.com > All capabilities > Infrastructure > AWS](https://one.newrelic.com/infra/infrastructure/cloud-aws)**へ移動します。New Relic に接続した AWS アカウントを検索します。**Stream**アカウント。
+ 2. アカウント ステータス ダッシュボードを確認し、 New Relicメトリクス データを受信していることを確認します。 これには、エラー、取り込まれたネームスペースおよびメトリクスの数が含まれる場合があります。
+ 3. メトリクスの特定のセットに対して書き込みを行って、データを探索します。
+
+ New Relic が新しいリソースを検出し、それをエンティティとして合成するまでに数分かかる場合があります。
+
+
+ AWS Billingなどのグローバル サービス用のAWS CloudWatchメトリクスは、 **us-east-1**リージョンでのみ利用できます。 そのリージョンにアクティブな CloudWatch メトリック ストリームが設定されていることを確認します。
+
+
+
+
+## 関連トピック [#related-topics]
+
+
+
+ 複数の AWS アカウントからデータを収集する方法を学びます。
+
+
+
+ CloudWatch メトリック ストリームからメトリクスを探索して使用します。
+
+
+
+ CloudFormation とCloudWatch Metric Streamsを使用して、 AWSサービスをNew Relicと統合します。
+
+
+
+ CloudFormation とAPIポーリングを使用して、 AWSサービスをNew Relicと統合します。
+
+
+
+ Terraform を使用してAWSサービスをNew Relicと統合します。
+
+
+
+ AWSコンソールからAWSサービスをNew Relicと手動で統合します。
+
+
\ No newline at end of file
diff --git a/src/i18n/content/jp/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/terraform.mdx b/src/i18n/content/jp/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/terraform.mdx
new file mode 100644
index 00000000000..207830f8c4b
--- /dev/null
+++ b/src/i18n/content/jp/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/terraform.mdx
@@ -0,0 +1,65 @@
+---
+title: Terraformとの統合
+tags:
+ - Integrate with Terraform
+ - AWS metric integration
+ - Amazon integrations
+ - AWS integrations
+metaDescription: Integrate New Relic with AWS services using Terraform.
+freshnessValidatedDate: never
+translationType: machine
+---
+
+AWSアカウントとNew Relicをシームレスに統合するには、 [CloudFormation および CloudWatch Metric Streams を介した](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation)統合が最も推奨されるアプローチです。 すでに Terraform を使用してAWSアカウントとサービスを管理している場合は、 New Relic統合のセットアップを簡素化するAWSクラウド統合モジュールを提供しているため、次の統合方法を好む場合があります。
+
+## 前提条件 [#prerequisites]
+
+AWS アカウントと New Relic の統合を開始する前に、次の前提条件を満たしていることを確認してください。
+
+* クラウド統合の**[権限](/docs/accounts/accounts-billing/new-relic-one-user-management/user-permissions/#infrastructure)**: New Relicアカウントにはこれらの権限が必要です。
+* AWS にリンクする New Relic アカウント ID とリージョン。
+
+## 統合手順 [#integration-steps]
+
+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 with Terraform
+
+5. **Select services**画面で、必要に応じて**Show resources not supported by CloudWatch Metric Streams**トグルを使用して、モニターするサービスを選択し、続行します。
+
+6. **Terraform**画面から、New Relic アカウントを Terraform プロバイダー アカウントに接続する方法を説明するドキュメントを開きます。
+
+7. 統合が成功すると、 New RelicでAWSデータを確認できるようになります。
+
+## 関連トピック [#related-topics]
+
+
+
+ 複数の AWS アカウントからデータを収集する方法を学びます。
+
+
+
+ CloudWatch メトリック ストリームからメトリクスを探索して使用します。
+
+
+
+ CloudFormation とCloudWatch Metric Streamsを使用して、 AWSサービスをNew Relicと統合します。
+
+
+
+ CloudFormation とAPIポーリングを使用して、 AWSサービスをNew Relicと統合します。
+
+
+
+ AWSコンソールからAWSサービスをNew Relicと手動で統合します。
+
+
\ No newline at end of file
diff --git a/src/i18n/content/jp/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-and-api-polling.mdx b/src/i18n/content/jp/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-and-api-polling.mdx
new file mode 100644
index 00000000000..46222f2aec2
--- /dev/null
+++ b/src/i18n/content/jp/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-and-api-polling.mdx
@@ -0,0 +1,77 @@
+---
+title: CloudFormationとAPIポーリングによる統合
+tags:
+ - Integration via CloudFormation
+ - AWS metric integration
+ - Amazon integrations
+ - AWS integrations
+ - Integration with API polling via CloudFormation
+metaDescription: Integrate New Relic with AWS services using CloudFormation templates to automate the setup of API polling for metrics ingestion.
+freshnessValidatedDate: never
+translationType: machine
+---
+
+AWSアカウントとNew Relicをシームレスに統合するには、 [CloudFormation および CloudWatch Metric Streams を介した](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation)統合が最も推奨されるアプローチです。 特定のデータ取得制限付きで、統合のためにAPIポーリングを利用することもできます。 詳細については、 [AWS メトリクスの取り込み](/docs/infrastructure/amazon-integrations/get-started/introduction-aws-integrations/#aws-metrics-ingestion)の比較表を参照してください。CloudWatch Metric Streamsでサポートされていないサービスに対してのみAPIポーリングを使用することをお勧めします。
+
+## 前提条件 [#prerequisites]
+
+AWS アカウントと New Relic の統合を開始する前に、次の前提条件を満たしていることを確認してください。
+
+* **New Relic[Ingest \[の取り込み\] - ライセンスキーとユーザー キー](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 と API ポーリングを使用して 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**： API Polling
+
+5. **Select services**画面で、必要に応じて**Show resources not supported by CloudWatch Metric Streams**トグルを使用して、モニターするサービスを選択し、続行します。
+
+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. Ingest - ライセンスキーとユーザーキーを AWS コンソールに貼り付けます。
+
+
+ AWSサービスから追加のメタデータを取得するには、 AWSコンソールから**AWS Config**有効にします。
+
+
+10. CloudFormation スタックをデプロイするには、AWS コンソールで**Create stack**選択します。スタック リソースの作成には数分かかる場合があり、メトリクス転送の構成によっては複数のスタックが生成される場合があります。 スタックの作成に失敗した場合は、 [トラブルシューティング手順](https://docs.newrelic.com/docs/logs/troubleshooting/aws-log-integration-issues/stack-creation-fails/)を参照してください。
+11. スタックの作成が成功したら、New Relic プラットフォームに切り替えて、AWS にNew Relic データが表示されるまでガイド付き統合を続行します。
+
+## 関連トピック [#related-topics]
+
+
+
+ 複数の AWS アカウントからデータを収集する方法を学びます。
+
+
+
+ CloudWatch メトリック ストリームからメトリクスを探索して使用します。
+
+
+
+ CloudFormation とCloudWatch Metric Streamsを使用して、 AWSサービスをNew Relicと統合します。
+
+
+
+ Terraform を使用してAWSサービスをNew Relicと統合します。
+
+
+
+ AWSコンソールからAWSサービスをNew Relicと手動で統合します。
+
+
\ No newline at end of file
diff --git a/src/i18n/content/jp/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms.mdx b/src/i18n/content/jp/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms.mdx
index 3d58ebbbfa1..48f1bc300a1 100644
--- a/src/i18n/content/jp/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms.mdx
+++ b/src/i18n/content/jp/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms.mdx
@@ -17,7 +17,7 @@ AWSアカウントとNew Relicをシームレスに統合するには、これ
AWS アカウントと New Relic の統合を開始する前に、次の前提条件を満たしていることを確認してください。
-* **New Relic[ライセンスキー](https://one.newrelic.com/api-keys)**: AWSサービスをNew Relicアカウントに接続するには、ライセンスキーが必要です。
+* **New Relic[Ingest \[の取り込み\] - ライセンスキーとユーザー キー](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アカウントにはこれらの権限が必要です。
@@ -47,15 +47,19 @@ CloudFormation と CloudWatch Metric Streams を使用して AWS アカウント
**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)**ページで有効にして続行してください。
+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 コンソールに貼り付けます。
+8. Ingest - ライセンスキーとユーザーキーを AWS コンソールに貼り付けます。
-9. Cloudformation スタックをデプロイするには、AWS コンソールで**Create stack**選択します。スタック リソースの作成には数分かかる場合があり、メトリクス転送の構成によっては複数のスタックが生成される場合があります。 スタックの作成に失敗した場合は、 [トラブルシューティング手順](https://docs.newrelic.com/docs/logs/troubleshooting/aws-log-integration-issues/stack-creation-fails/)を参照してください。
+
+ AWSサービスから追加のメタデータを取得するには、 AWSコンソールから**AWS Config**有効にします。
+
-10. スタックの作成が成功したら、New Relic プラットフォームに切り替えて、AWS にNew Relic データが表示されるまでガイド付き統合を続行します。
+10. CloudFormation スタックをデプロイするには、AWS コンソールで**Create stack**選択します。スタック リソースの作成には数分かかる場合があり、メトリクス転送の構成によっては複数のスタックが生成される場合があります。 スタックの作成に失敗した場合は、 [トラブルシューティング手順](https://docs.newrelic.com/docs/logs/troubleshooting/aws-log-integration-issues/stack-creation-fails/)を参照してください。
+
+11. スタックの作成が成功したら、New Relic プラットフォームに切り替えて、AWS にNew Relic データが表示されるまでガイド付き統合を続行します。
## 関連トピック [#related-topics]
@@ -67,4 +71,16 @@ CloudFormation と CloudWatch Metric Streams を使用して AWS アカウント
CloudWatch メトリック ストリームからメトリクスを探索して使用します。
+
+
+ CloudFormation とAPIポーリングを使用して、 AWSサービスをNew Relicと統合します。
+
+
+
+ Terraform を使用してAWSサービスをNew Relicと統合します。
+
+
+
+ AWSコンソールからAWSサービスをNew Relicと手動で統合します。
+
\ 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**を選択して続行します。
+
+
+
+
+ サポートされていないサービスに対して選択された ポーリングによる サービスの 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
```
-
+ /* <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}})
```
-
+ /* <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}}
```
-
+ /* <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
```
-
+ /* <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
```
-
+ /* <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
```
-
+ /* <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`
-
+ /* <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}}
```
-
+ /* <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
```
-
+ /* <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
```
-
+ /* <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:
-
+ * **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}}
```
-
+ /* <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`
-
+ /* <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
```
-
+ /* <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}})
```
-
+ /* <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`句が含まれている場合、最新の値を使用してクエリが実行されます。
-
+ /* <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-7-25-2025.mdx b/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx
new file mode 100644
index 00000000000..0a034bbee70
--- /dev/null
+++ b/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx
@@ -0,0 +1,267 @@
+---
+subject: Docs
+releaseDate: '2025-07-25'
+version: 'June 13 - July 24, 2025'
+translationType: machine
+---
+
+### 新しいドキュメント
+
+* [New Relic Browserエージェントの問題をデバッグする方法](/docs/browser/new-relic-browser/troubleshooting/how-to-debug-browser-agent/)に関する新しい機能が追加されました。これには、バージョン 1.285.0 以降で強化されたトラブルシューティングのための詳細なログ記録、ネットワーク リクエストの監視、検査イベントが含まれます。
+* `python`および`.node.js`関数の監視に[Azure Functions の](/docs/serverless-function-monitoring/azure-function-monitoring/introduction-azure-monitoring/)サポートが追加されました。
+* New Relicプラットフォームで非効率性を特定し、最適化の推奨事項を提供し、CCU 削減量を見積もる機能を備えた、計算効率を高めるための実用的なインサイト用の[コスト オプティマイザー](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/compute-optimizer/)を追加しました。
+* [Cloud Cost Intelligence](/docs/cci/getting-started/overview)を追加しました。 cloudコストの可視化と管理のためのツールを提供します。これには、包括的なコストの内訳、 Kubernetesコストの割り当て、手動コストの見積もり、クロスアカウント データ収集などの機能が含まれます。現在はAWSクラウド コストのみをサポートしています。
+* [KubernetesにOpenTelemetryオブザーバNew Relic](/docs/kubernetes-pixie/k8s-otel/intro/)を追加し、 Helmチャートを介してクラスタをシームレスに監視するための New Relic 機能プロバイダーに依存しない統合を使用して、 New Relicのツールとダッシュボードに送信されるメトリクス、イベント、ログのテレメトリー信号を強化しました。
+* [Windowsインテグレーションの制限とトラブルシューティング](/docs/kubernetes-pixie/kubernetes-integration/troubleshooting/troubleshooting-windows/)を追加
+* [CloudFormation およびCloudWatch Metric Streams](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms/)を介したAWSインテグレーションが追加され、サポートされていないサービスのAPIポーリングがサポートされました。
+* MySQL および MS SQL Server のオンホスト インテグレーションを介して[、 New Relicデータベース](/docs/infrastructure/host-integrations/db-entity-tags/)エンティティ for MySQLや既存のテレメトリーに影響を与えることなく、 New Relicのメタデータ インサイトと組織を強化しました。
+
+### 主な変更点
+
+* [NRQL References](/docs/nrql/nrql-syntax-clauses-functions/#non-aggregator-functions/)に非集計関数を追加しました。
+* [Ruby エージェントの要件とサポートされるフレームワーク](/docs/apm/agents/ruby-agent/getting-started/ruby-agent-requirements-supported-frameworks/)を更新しました。
+* New Relicドキュメント[のOpenTelemetryログにNew Relicカスタム](/docs/opentelemetry/best-practices/opentelemetry-best-practices-logs/#custom-events)イベントとしてログを追加しました。
+* [インストゥルメント化されたAzure関数の互換性と要件に関する](/docs/serverless-function-monitoring/azure-function-monitoring/compatibility-requirement-azure-monitoring/#supported-runtimes)ドキュメントの Linux、 Windows 、およびコンテナー化された関数でサポートされているランタイムを更新しました。
+* [Confluent クラウド インテグレーション](/docs/message-queues-streaming/installation/confluent-cloud-integration/#metrics)のメトリクス データを更新しました。
+* GCP Cloud Run を[Node.jsエージェント設定](/docs/apm/agents/nodejs-agent/installation-configuration/nodejs-agent-configuration/)から削除しました。
+* [AI モニタリングの互換性と要件](/docs/ai-monitoring/compatibility-requirements-ai-monitoring/)を更新し、.NET エージェントでサポートされる追加のライブラリを追加しました。
+* New Relicテレメトリー デュアルスタック エンドポイントを[New Relicネットワーク トラフィック](/docs/new-relic-solutions/get-started/networks/#new-relic-endpoints)に追加しました。
+* [Google Cloud Load Balancing監視統合](/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-load-balancing-monitoring-integration/)に`GcpHttpExternalRegionalLoadBalancerSample`追加しました。
+* [外形監視ジョブマネージャードキュメントのインストール](/docs/synthetics/synthetic-monitoring/private-locations/install-job-manager/#-install)方法にOpenShiftの起動手順を追加しました。
+* [Node.js エージェント バージョン 12](/docs/apm/agents/nodejs-agent/installation-configuration/update-nodejs-agent/)を更新しました。
+* APIポーリングのサポートを含む、 [CloudFormation およびCloudWatch Metric Streamsを利用したNew RelicとのAWS](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms/)のシームレスな統合が追加されました。
+
+### マイナーチェンジ
+
+* [境界トレース](/docs/data-apis/manage-data/manage-data-retention/#retention-periods/)の保存期間として`Transaction`を追加しました。
+* [アラートルールと制限](/docs/alerts/admin/rules-limits-alerts/)に新しいカテゴリとして`Destination`追加しました。
+* [Azure ネイティブ New Relic サービスの概要](/docs/infrastructure/microsoft-azure-integrations/get-started/azure-native/)ドキュメントに、Azure リソースの診断設定が正しく構成されていることを確認するか、Azure ネイティブ New Relic サービス経由の転送を無効にしてデータが New Relic プラットフォームに送信されないようにするためのコールアウトを追加しました。
+* [.NET エージェント](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements/)の最新の互換ライブラリを更新しました。
+* [iOS エージェント リリース ノート](/docs/release-notes/mobile-release-notes/ios-release-notes/index/)ドキュメントにコールアウトを追加して、iOS SDK バージョン 7.5.4 以降、 変更により、以前は抑制されていた処理済み例外イベントが報告されるようになりました。
+* Kubernetes環境のリソース プロパティと非Kubernetes環境の`container.id`指定に対するサービスとコンテナの関係の要件を更新し、 [New RelicのOpenTelemetryリソース](/docs/opentelemetry/best-practices/opentelemetry-best-practices-resources/)の適切なテレメトリー設定を確保します。
+* [特定のインフラストラクチャエージェント](/docs/infrastructure/infrastructure-agent/new-relic-guided-install-overview/#install-specific-versions)バージョンインストレーション用の CLI サポートを追加し、一貫したデプロイメントとシステム互換性を可能にします。レシピ名に`@X.XX.X`を使用してバージョンを指定します。
+* UIで**Manage Account Cardinality** \[アカウント カーディナリティの管理]、**Manage Metric Cardinality** \[メトリック カーディナリティの管理]、および**Create Pruning Rules** \[プルーニング ルールの作成]機能を使用するためのロール アクセス要件を強調するコールアウトを追加しました。[カーディナリティ管理](/docs/data-apis/ingest-apis/metric-api/cardinality-management/#attributes-table)で権限が設定されていることを確認してください。
+* [Node.js エージェントの互換性と要件を](/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent/)`v12.23.0`に更新しました。
+* [Elasticsearch](/docs/infrastructure/host-integrations/host-integrations-list/elasticsearch/elasticsearch-integration)をセットアップするために必要な最小限の権限を追加しました。
+* [NRQL形式構文](/docs/alerts/create-alert/create-alert-condition/create-nrql-alert-conditions/)の`FACET`プロパティの最大許容使用制限値を 5000 から 20000 の値に更新しました。
+
+### リリースノート
+
+* [`SystemSample` 、 `ProcessSample` 、 `NetworkSample` 、 `StorageSample`のインフラストラクチャ イベントを対象とするドロップ ルールの](/eol/2025/05/drop-rule-filter/)サポート終了日として、2026 年 1 月 7 日が発表されました。
+
+* [アラート条件の messageId およびタイムスタンプの FACET](/eol/2025/07/deprecating-alert-conditions/)のサポートが直ちに有効になります。
+
+* 2025 年 10 月 28 日が[Attention Required](/eol/2025/07/upcoming-eols/)のサポート終了日として発表されました。
+
+* 新着情報投稿をご覧ください:
+
+ * [Microsoft Teams に直接通知を送信する](/whats-new/2025/03/whats-new-03-13-microsoft-teams-integration/)
+ * [New Relicの計算オプティマイザーが一般提供されました!](/whats-new/2025/06/whats-new-06-25-compute-optimizer/)
+ * [統合クエリエクスプローラーでアカウント間クエリをログに記録する](/whats-new/2025/07/whats-new-07-01-logs-uqe-cross-account-query/)
+ * [OpenTelemetryを使用したKubernetes監視が一般公開されました。](/whats-new/2025/07/whats-new-7-01-k8s-otel-monitoring/)
+ * [Kubernetes の Windows ノード監視がパブリック プレビューになりました](/whats-new/2025/07/whats-new-07-04-k8s-windows-nodes-preview/)
+ * [パフォーマンスの問題を正確に特定: ページビューと Core Web Vitals の高度なフィルタリング](/whats-new/2025/07/whats-new-07-09-browser-monitoring/)
+ * [最新のエラーで並べ替えられるようになりました](/whats-new/2025/07/whats-new-7-08-ei-sort-by-newest/)
+ * [ブラウザデータ、条件: 新しいコントロール オプション](/whats-new/2025/07/whats-new-07-10-browser-monitoring/)
+ * [データベースの詳細なクエリ分析が一般提供開始](/whats-new/2025/07/whats-new-07-24-db-query-performance-monitoring/)
+ * [NRQL予測と予測アラートが一般提供開始](/whats-new/2025/07/whats-new-7-22-predictive-analytics/)
+ * [APM + OpenTelemetry コンバージェンス GA](/whats-new/2025/07/whats-new-07-21-apm-otel/)
+ * [GitHub Copilot と ServiceNow のエージェント統合が一般提供開始](/whats-new/2025/07/whats-new-7-15-agentic-ai-integrations/)
+
+* 弊社の最新リリース情報を常に把握してください:
+
+ * [Node API ランタイム v1.2.119](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.119/)
+ * 脆弱性の問題を修正しました。
+
+ * [Ping ランタイム v1.51.0](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.119/)
+
+ * ping ランタイムの logback-core の脆弱性を修正しました。
+ * ping ランタイムの jetty サーバーの脆弱性を修正しました。
+ * ping ランタイムの Ubuntu の脆弱性を修正しました。
+
+ * [Browser v1.292.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.292.0/)
+
+ * `BrowserInteraction`と`previousUrl`定義を更新します。
+ * 追加の検査イベントを追加しました。
+ * `finished` API `timeSinceLoad`値を修正しました。
+
+ * [Kubernetesインテグレーション v3.42.1](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-42-1/)
+ * 将来のプラットフォーム互換性のために、内部バックエンドと CI 関連の調整を修正しました。
+
+ * [ジョブマネージャー v444](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-444/)
+ * 実行時間が長い一部のモニターの結果が特定の顧客に表示されない問題を修正しました。
+
+ * [Pythonエージェント v10.14.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-101400/)
+
+ * `Azure Function Apps`のサポートが追加されました。
+ * `protobuf v6`サポートを有効にするために`pb2`ファイルを修正しました。
+
+ * [Android エージェント v7.6.7](/docs/release-notes/mobile-release-notes/android-release-notes/android-767/)
+
+ * ログを報告するときに ANR を解決するためのパフォーマンスが向上しました。
+ * アプリケーションの終了後もログの報告を継続する問題を修正しました。
+ * アプリケーション状態の監視とデータ転送に関する問題を解決しました。
+ * 厳密モードをオンにしたときのいくつかの違反が改善されました。
+
+ * [Kubernetesインテグレーション v3.42.2](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-42-2/)
+
+ * `golang.org/x/crypto` `v0.39.0`に更新しました。
+ * `go` `v1.24.4`に更新しました。
+
+ * [.NET エージェント v10.42.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-42-0/)
+
+ * Azure Service Bus のサポートが追加されました。
+ * 最新の VS でのプロファイラー ビルド エラーを修正しました。
+
+ * [PHPエージェント v11.10.0.24](/docs/release-notes/agent-release-notes/php-release-notes/php-agent-11-10-0-24/)
+
+ * PHP アプリケーションで使用されるパッケージを検出するためにデフォルトで使用される Composer ランタイム API を追加しました。
+ * Composer ランタイム API の未定義の動作を修正しました。
+
+ * [Node ブラウザ ランタイム v3.0.32](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.32/)
+ * Chrome 131 の Chrome ビルダー オプションが更新されました。
+
+ * [iOS向けモバイルアプリv6.9.8](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6098/)
+ * より堅牢で信頼性の高いソケット接続により Ask AI 機能が強化され、シームレスなエクスペリエンスが保証されます。
+
+ * [Android用モバイルアプリv5.29.7](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5297/)
+ * より堅牢で信頼性の高いソケット接続により Ask AI 機能が強化され、シームレスなエクスペリエンスが保証されます。
+
+ * [Node.jsエージェント v12.22.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-22-0/)
+
+ * `openai` v5 ストリーミング サポートが追加されました。
+ * `openai.responses.create` API のサポートが追加されました。
+ * 未定義のトレース状態ヘッダーのエラー ログを修正しました。
+
+ * [インフラストラクチャエージェント v1.65.0](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1650/)
+
+ * 依存関係`newrelic/nri-winservices`を更新しました `v1.2.0`
+ * alpine docker タグを次のように更新しました。 `v3.22`
+
+ * [インフラストラクチャエージェント v1.65.1](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1651/)
+ * 依存関係`newrelic/nri-flex`を更新して `v1.16.6`
+
+ * [Browser v1.292.1](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.292.1/)
+ * カスタムアトリビュートの競合状態の優先順位を修正しました。
+
+ * [NRDOT v1.2.0](/docs/release-notes/nrdot-release-notes/nrdot-2025-06-26/)
+ * OTELベータコアを `v0.128.0`
+
+ * [HTML5.JS v3.0.0 用メディアエージェント](/docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-25-04-15/)
+
+ * 新しいイベントタイプを導入しました。
+ * `PageAction`イベント タイプは非推奨になりました。
+
+ * [HTML5.JS v3.1.1 用メディアエージェント](/docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-25-06-15/)
+
+ * パッケージの npm 公開を有効にして、アクセスと配布を容易にしました。
+ * `cjs` 、 `esm` 、 `umd`ビルドを`dist`フォルダーに追加し、CommonJS、ES モジュール、UMD モジュール形式との互換性を確保しました。
+
+ * [Roku 用メディアエージェント v4.0.0](/docs/release-notes/streaming-others-release-notes/streaming-others-agent-25-02-25/)
+
+ * 新しいイベントタイプを導入しました。
+ * `RokuVideo`イベント タイプは非推奨になりました。
+ * `RokuSystem`イベント タイプは非推奨になりました。
+
+ * [Roku 用メディアエージェント v4.0.1](/docs/release-notes/streaming-others-release-notes/streaming-others-agent-25-04-22/)
+ * `errorName`は非推奨になったため、 `errorName`名前を`errorMessage`に変更しました。
+
+ * [ジョブマネージャー v447](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-447/)
+ * ベースイメージのアップグレードを`ubuntu 22.04`から `ubuntu 24.4`
+
+ * [Ping ランタイム v1.52.0](/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.52.0/)
+ * ベースイメージのアップグレードが`ubuntu 22.04`から `ubuntu 24.04`
+
+ * [Kubernetesインテグレーション v3.43.0](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-43-0/)
+ * KubernetesクラスタにWindowsノード監視のサポートが追加されました。
+
+ * [Android用モバイルアプリv5.29.8](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5298/)
+ * バグが修正され、UI が改善されてよりスムーズなエクスペリエンスが実現しました。
+
+ * [Node.jsエージェント v12.23.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-23-0/)
+
+ * エントリースパンとエグジットスパンのみレポートする機能を追加しました。
+ * Node.js 24 のサポートが追加されました。
+ * 互換性レポートを更新しました。
+
+ * [Node API ランタイム v1.2.120](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.120/)
+ * 脆弱性を修正しました `CVE-2024-39249`
+
+ * [iOS向けモバイルアプリv6.9.9](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6099/)
+ * 動的プロンプトによる Ask AI 機能が強化されました。
+
+ * [Browser v1.293.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.293.0/)
+
+ * **長いタスクの**内部メッセージを追加しました。
+ * ディストリビューティッド（分散）トレーシングが無効にならない問題を修正しました。
+
+ * [Node ブラウザ ランタイム v3.0.35](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.35/)
+ * ベースイメージのアップグレード
+
+ * [Javaエージェント v8.22.0](/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8220/)
+
+ * Azure App Services のリンクされたメタデータ。
+ * `MonoFlatMapMain`計装を削除しました。
+
+ * [Node.jsエージェント v12.24.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-24-0/)
+
+ * 設定可能な属性値のサイズ制限を実装しました
+ * 互換性レポートを更新しました。
+
+ * [Kubernetesインテグレーション v3.43.2](docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-43-2/)
+ * kube-state-メトリクス チャートのバージョンを`5.12.1`から に更新します `5.30.1`
+
+ * [iOS エージェント v7.5.7](/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-757/)
+ * セッション開始時にディストリビューティッド（分散）トレーシングに必要なアカウント情報がすべて揃っていない可能性がある問題を修正しました。
+
+ * [Android用モバイルアプリv5.29.9](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5299/)
+ * 動的 UI レンダリングによるフィードバックを強化しました。
+
+ * [Android 向けモバイルアプリ v5.30.0](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-53000/)
+ * バグを修正し、Teams GA フラグを更新して、ユーザー エクスペリエンスを向上させました。
+
+ * [Go エージェント v3.40.1](/docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-40-1/)
+
+ * デッドロックバグのため、使用率を元に戻しました。v3.39.0 リリースに戻してください。
+ * go モジュールに直接依存関係を追加した awssupport\_test.go テストを削除しました
+
+ * [Flutterエージェント v1.1.12](/docs/release-notes/mobile-release-notes/flutter-release-notes/flutter-agent-1112/)
+
+ * ネイティブ Android エージェントをバージョン 7.6.7 にアップデートしました
+ * ネイティブ iOS エージェントを改善し、バージョン 7.5.6 に更新しました
+
+ * [Node.jsエージェント v13.0.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-0-0/)
+
+ * Node.js 18のサポートを終了しました
+ * `fastify`の最小サポートバージョンを 3.0.0 に更新しました。`pino`を 8.0.0 に、 `koa-router`を 12.0.0 に
+
+ * [Browser v1.294.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.294.0/)
+ * レポートの空の previousUrl を undefined として修正しました
+
+ * [インフラストラクチャエージェント v1.65.4](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1654/)
+ * 依存関係`newrelic/nri-prometheus`を v2.26.2 に更新しました
+
+ * [iOS向けモバイルアプリv6.9.10](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6100/)
+ * 動的 UI レンダリングによるフィードバックを強化しました。
+
+ * [Android NDK エージェント v1.1.3](/docs/release-notes/mobile-release-notes/android-release-notes/android-ndk-113/)
+ * 16KBページサイズのサポートを追加
+
+ * [インフラストラクチャエージェント v1.65.3](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1653/)
+
+ * Windows プロセス ハンドルを変更しました。
+ * `nri-docker`を`v2.5.1`に、 `nri-prometheus`を `v2.26.1`
+
+ * [.NET エージェント v10.43.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-43-0/)
+ * Azure Service Bus にトピックのサポートを追加しました
+
+ * [Node.jsエージェント v12.25.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-25-0/)
+ * 計装AWS Bedrock Converse APIを修正
+
+ * [Node.jsエージェント v12.24.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-24-0/)
+
+ * 設定可能な属性値のサイズ制限を実装しました
+ * 互換性レポートを更新しました
+
+ * [診断 CLI (nrdiag) v3.4.0](/docs/release-notes/diagnostics-release-notes/diagnostics-cli-release-notes/diagnostics-cli-340/)
+ * `/lib64/libc.so.6: version 'GLIBC_2.34'`が見つからないなどのGLIBC関連のエラーを修正しました
\ 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/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.298.mdx b/src/i18n/content/jp/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.298.mdx
new file mode 100644
index 00000000000..f05dbb15f6d
--- /dev/null
+++ b/src/i18n/content/jp/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.298.mdx
@@ -0,0 +1,34 @@
+---
+subject: Browser agent
+releaseDate: '2025-09-19'
+version: 1.298.0
+downloadLink: 'https://www.npmjs.com/package/@newrelic/browser-agent'
+features:
+ - Factor long tasks into soft nav base interaction span
+bugs:
+ - Force LCP to report the original page URL
+security: []
+translationType: machine
+---
+
+## バージョン1.298.0
+
+### 特徴
+
+#### 長いタスクをソフトナビゲーションベースのインタラクションスパンに組み込む
+
+`BrowserInteraction` ソフト ナビゲーション ("SPA 2.0") では、5 秒間長いタスクが観察されない時点まで、DOM の変更時間を超えて期間が延長されます。`JavascriptError`と`AjaxRequest` 、元のヒューリスティックの終了を超えたこの延長期間中、まだそのようなインターラクションに関連付けられていません。
+
+### バグ修正
+
+#### LCP に元のページ URL を報告させる
+
+LCP が、収集 URL とは別に、pageUrl を報告できるようにします。LCP 収集前に発生するソフト ナビゲーションで、LCP に関連付けられた元のページ URL ではなく、現在のページ URL が報告されるという問題が確認されました。この変更により、LCP ハーベスト ノードは、現在のページ URL に関係なく、元の URL を報告できるようになります。変更は`pageUrl`と`targetGroupedUrl`属性の両方に適用される必要があります。
+
+## サポートステートメント
+
+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.298.0 は、 Chrome 130 ～ 140、Edge 130 ～ 140、Safari 17 ～ 19、Firefox 132 ～ 142 のブラウザとバージョン範囲を対象に構築され、テストされています。 モバイル デバイスの場合、v1.298.0 は Android OS 16 および iOS Safari 17-26 用に構築およびテストされました。
\ No newline at end of file
diff --git a/src/i18n/content/jp/docs/release-notes/nrdot-release-notes/nrdot-2025-09-18.mdx b/src/i18n/content/jp/docs/release-notes/nrdot-release-notes/nrdot-2025-09-18.mdx
new file mode 100644
index 00000000000..ca248513de2
--- /dev/null
+++ b/src/i18n/content/jp/docs/release-notes/nrdot-release-notes/nrdot-2025-09-18.mdx
@@ -0,0 +1,16 @@
+---
+subject: NRDOT
+releaseDate: '2025-09-18'
+version: 1.4.0
+metaDescription: Release notes for NRDOT Collector version 1.4.0
+translationType: machine
+---
+
+## 変更ログ
+
+### 特徴
+
+* 特技: nrdot-collectors にspanprocessor を追加 (#371)
+* 機能: ホテルコンポーネントのバージョンを v0.131.0 から v0.132.0 にアップグレード (#368)
+* 特技: newrelic.service.type を内部テレメトリー設定に追加 (#380)
+* 機能: ec2 の host.name 検出を有効にする (#382)
\ No newline at end of file
diff --git a/src/i18n/content/jp/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-467.mdx b/src/i18n/content/jp/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-467.mdx
new file mode 100644
index 00000000000..1939b461327
--- /dev/null
+++ b/src/i18n/content/jp/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-467.mdx
@@ -0,0 +1,10 @@
+---
+subject: Job Manager
+releaseDate: '2025-09-22'
+version: '467'
+translationType: machine
+---
+
+### 修正
+
+* sjm のセキュリティ脆弱性に対処するために、CVE-2025-58056、CVE-2025-58057 および基礎となる Ubuntu の脆弱性を修正しました。
\ No newline at end of file
diff --git a/src/i18n/content/jp/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.mdx b/src/i18n/content/jp/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.mdx
new file mode 100644
index 00000000000..711e5d6cceb
--- /dev/null
+++ b/src/i18n/content/jp/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.mdx
@@ -0,0 +1,11 @@
+---
+subject: Node API runtime
+releaseDate: '2025-09-22'
+version: 1.2.134
+translationType: machine
+---
+
+### 修正
+
+* Node APIランタイムのセキュリティ脆弱性に対処するために、Ubuntuの根本的な脆弱性を修正しました。
+* 日間の SSL チェッカーの状態、残りのバグ修正。
\ No newline at end of file
diff --git a/src/i18n/content/jp/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.mdx b/src/i18n/content/jp/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.mdx
new file mode 100644
index 00000000000..92db3ea7169
--- /dev/null
+++ b/src/i18n/content/jp/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.mdx
@@ -0,0 +1,14 @@
+---
+subject: Node browser runtime
+releaseDate: '2025-09-22'
+version: 3.0.50
+translationType: machine
+---
+
+### 改良点
+
+* Chromeブラウザのバージョンを131から134にアップグレードする
+
+### 修正
+
+* CVE-2025-58754 および基盤となる Ubuntu の脆弱性を修正し、Node ブラウザ ランタイムのセキュリティ脆弱性に対処しました。
\ 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/apis/nerdgraph/examples/nerdgraph-issues-api-via-github.mdx b/src/i18n/content/kr/docs/apis/nerdgraph/examples/nerdgraph-issues-api-via-github.mdx
index ad34e013611..4eaa92f8a2b 100644
--- a/src/i18n/content/kr/docs/apis/nerdgraph/examples/nerdgraph-issues-api-via-github.mdx
+++ b/src/i18n/content/kr/docs/apis/nerdgraph/examples/nerdgraph-issues-api-via-github.mdx
@@ -663,7 +663,7 @@ translationType: machine
```graphql
{
- currentUser {
+ actor {
account(id: ACCOUNT_ID) {
aiIssues {
issues {
@@ -685,7 +685,7 @@ translationType: machine
```json
{
"data": {
- "currentUser": {
+ "actor": {
"account": {
"aiIssues": {
"issues": {
@@ -724,7 +724,7 @@ translationType: machine
```graphql
{
- currentUser {
+ actor {
account(id: YOUR_ACCOUNT_ID) {
aiIssues {
issues(cursor: "") {
@@ -747,7 +747,7 @@ translationType: machine
```json
{
"data": {
- "currentUser": {
+ "actor": {
"account": {
"aiIssues": {
"issues": {
@@ -791,7 +791,7 @@ translationType: machine
```graphql
{
- currentUser {
+ actor {
account(id: YOUR_ACCOUNT_ID) {
aiIssues {
issues(cursor: "=ATN") {
@@ -840,7 +840,7 @@ translationType: machine
```graphql
{
- currentUser {
+ actor {
account(id: YOUR_ACCOUNT_ID) {
aiIssues {
issues(filter: {priority: "CRITICAL", states: CLOSED}) {
@@ -863,7 +863,7 @@ translationType: machine
```json
{
"data": {
- "currentUser": {
+ "actor": {
"account": {
"aiIssues": {
"issues": {
@@ -1066,7 +1066,7 @@ translationType: machine
```graphql
{
- currentUser {
+ actor {
account(id: YOUR_ACCOUNT_ID) {
aiIssues {
issuesEvents {
@@ -1089,7 +1089,7 @@ translationType: machine
```json
{
"data": {
- "currentUser": {
+ "actor": {
"account": {
"aiIssues": {
"issuesEvents": {
@@ -1160,7 +1160,7 @@ translationType: machine
```graphql
{
- currentUser {
+ actor {
account(id: YOUR_ACCOUNT_ID) {
aiIssues {
issuesEvents(filter: {ids: "fe0d512f-36c7-4b7a-8a80-4c47c040807a"}) {
@@ -1186,7 +1186,7 @@ translationType: machine
```json
{
"data": {
- "currentUser": {
+ "actor": {
"account": {
"aiIssues": {
"issuesEvents": {
@@ -1264,7 +1264,7 @@ translationType: machine
```graphql
{
- currentUser {
+ actor {
account(id: YOUR_ACCOUNT_ID) {
aiIssues {
incidents {
@@ -1293,7 +1293,7 @@ translationType: machine
```json
{
"data": {
- "currentUser": {
+ "actor": {
"account": {
"aiIssues": {
"incidents": {
@@ -1404,7 +1404,7 @@ translationType: machine
```graphql
{
- currentUser {
+ actor {
account(id: YOUR_ACCOUNT_ID) {
aiIssues {
incidents(filter: {priority: "CRITICAL", states: CREATED}) {
@@ -1434,7 +1434,7 @@ translationType: machine
```json
{
"data": {
- "currentUser": {
+ "actor": {
"account": {
"aiIssues": {
"incidents": {
@@ -1502,7 +1502,7 @@ translationType: machine
```graphql
{
- currentUser {
+ actor {
account(id: YOUR_ACCOUNT_ID) {
aiIssues {
incidents(filter: {ids: "97373770-caad-46cd-a69d-a358de3be090"}) {
@@ -1532,7 +1532,7 @@ translationType: machine
```json
{
"data": {
- "currentUser": {
+ "actor": {
"account": {
"aiIssues": {
"incidents": {
@@ -1573,7 +1573,7 @@ translationType: machine
```graphql
{
- currentUser {
+ actor {
account(id: YOUR_ACCOUNT_ID) {
aiIssues {
incidentsEvents {
@@ -1597,7 +1597,7 @@ translationType: machine
```json
{
"data": {
- "currentUser": {
+ "actor": {
"account": {
"aiIssues": {
"incidentsEvents": {
@@ -1664,7 +1664,7 @@ translationType: machine
```graphql
{
- currentUser {
+ actor {
account(id: YOUR_ACCOUNT_ID) {
aiIssues {
incidentsEvents(filter: {ids: "cd512082-6ebe-46ac-a6dc-d387dc86dc80"}) {
@@ -1694,7 +1694,7 @@ translationType: machine
```json
{
"data": {
- "currentUser": {
+ "actor": {
"account": {
"aiIssues": {
"incidentsEvents": {
@@ -1749,7 +1749,7 @@ translationType: machine
```graphql
{
- currentUser {
+ actor {
account(id: YOUR_ACCOUNT_ID) {
aiIssues {
configByEnvironment {
@@ -1772,7 +1772,7 @@ translationType: machine
```json
{
"data": {
- "currentUser": {
+ "actor": {
"account": {
"aiIssues": {
"configByEnvironment": {
@@ -1963,7 +1963,7 @@ translationType: machine
```graphql
{
- currentUser {
+ actor {
account(id: YOUR_ACCOUNT_ID) {
aiIssues {
issues {
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/browser/browser-monitoring/browser-pro-features/session-replay/additional-information.mdx b/src/i18n/content/kr/docs/browser/browser-monitoring/browser-pro-features/session-replay/additional-information.mdx
index f580219e84b..6739761cd4f 100644
--- a/src/i18n/content/kr/docs/browser/browser-monitoring/browser-pro-features/session-replay/additional-information.mdx
+++ b/src/i18n/content/kr/docs/browser/browser-monitoring/browser-pro-features/session-replay/additional-information.mdx
@@ -45,7 +45,7 @@ translationType: machine
* 전략적 페이로드 수집: 전체 DOM이 캡처될 때만 대용량(압축) 페이로드가 전송되며, 이는 일반적으로 리플레이 기능을 처음 가져올 때 발생합니다. 그 후에는 사용자의 동작과 관련된 작은 페이로드만 전송됩니다. 브라우저 에이전트는 다음 조건이 처음 발생할 때 데이터를 수집합니다.
- * The payload reaches more than 16 kB compressed.
- * 30 seconds elapses.
+ * 압축 시 페이로드는 16kB가 넘습니다.
+ * 30초가 경과합니다.
* 페이지 표시 여부가 변경됩니다(예: 탭 변경, 포커스, 탐색).
* 세션이 종료됩니다.
\ No newline at end of file
diff --git a/src/i18n/content/kr/docs/browser/new-relic-browser/lab/debug-slowness.mdx b/src/i18n/content/kr/docs/browser/new-relic-browser/lab/debug-slowness.mdx
index 4d17ef00a0c..8ef38e304bd 100644
--- a/src/i18n/content/kr/docs/browser/new-relic-browser/lab/debug-slowness.mdx
+++ b/src/i18n/content/kr/docs/browser/new-relic-browser/lab/debug-slowness.mdx
@@ -5,22 +5,15 @@ freshnessValidatedDate: never
translationType: machine
---
-
- 이 절차는 뉴렐릭 을(를) 사용하여 웹 앱 문제를 해결하는 방법을 알려주는 실습의 일부입니다.
+
+ 이 절차는 뉴렐릭 을(를) 사용하여 웹 앱 문제를 해결하는 방법을 알려주는 실습의 일부입니다.
- 랩의 각 절차는 마지막 절차를 기반으로 하므로 이 절차를 시작하기 전에 마지막 절차 [_인 애플리케이션의 오류 디버그 를_](/docs/browser/new-relic-browser/lab/debug-errors)완료했는지 확인하십시오.
+ 랩의 각 절차는 마지막 절차를 기반으로 하므로 이 절차를 시작하기 전에 마지막 절차 [*인 애플리케이션의 오류 디버그 를*](/docs/browser/new-relic-browser/lab/debug-errors)완료했는지 확인하십시오.
애플리케이션에서 JavaScript 오류를 수정한 후 귀하와 귀하의 팀은 자신감을 느낍니다. 다운 타임을 준비하고 소셜 미디어로 이동하지만 Twitter를 확인하고 혼란스러워하는 고객을 봅니다.
-
+
어 오! 고객이 행복해 보이지 않습니다. 지연의 원인을 찾기 위해 New Relic 브라우저 모니터링을 사용할 때입니다.
@@ -36,29 +29,17 @@ translationType: machine
뉴렐릭 홈페이지에서 **Browser** 으로 이동하여 **Relicstaurants** 를 선택하세요.
-
+
여기에서는 **Page views with JavaScript errors**, **Core web vitals**, **User time on the site**, **Initial page load and route changes** 등을 포함하여 브라우저 애플리케이션과 관련된 모든 데이터를 볼 수 있습니다.
-
+
**largest contentful paint (LCP)** 에 주목하세요.
-
+
콘텐츠가 포함된 최대 페인트(LCP)는 웹 페이지의 기본 콘텐츠가 로드되는 속도를 나타냅니다. 이상적으로는 콘텐츠를 로드하는 데 1-2초 이상 걸리지 않아야 합니다. 여기에서는 사이트가 5초 이상 로드되는 것을 볼 수 있습니다. 사용자가 불평하는 것도 당연합니다!
@@ -68,29 +49,17 @@ translationType: machine
아래로 스크롤하여 **Front end vs. back end** 그래프를 확인하세요.
-
+
그래프를 필터링하고 백앤드를 로드하는 데 걸리는 시간을 확인하려면 **Back end (time to first byte) (50%)** 을 클릭하세요.
-
+
- 그래프는 백엔드가 최악의 경우 요청을 처리하는 데 최대 140밀리초가 걸렸음을 나타냅니다. 이것은 프런트 엔드가 지연을 유발한다는 것을 의미합니까?
+ 그래프는 최악의 경우 백엔드가 요청을 처리하는 데 최대 140밀리초가 걸렸음을 나타냅니다. 이것은 프론트엔드가 지연을 일으킨다는 뜻인가요?
**Front end (Window load + AJAX) (50%)** 을 클릭합니다.
-
+
문제가 있습니다! 그래프는 프런트 엔드에서 지연이 발생하고 있음을 나타냅니다.
@@ -98,21 +67,13 @@ translationType: machine
프론트엔드에서 지연이 발생하는 원인을 좁히려면 **Initial page load and route change** 그래프를 자세히 살펴보세요.
-
+
**Initial page load (Window load + AJAX)** 을 클릭합니다.
-
+
그래프는 **Initial page load (Window load + AJAX)** 5-6초가 걸리는 것을 나타냅니다. 이는 놀라운 일입니다.
@@ -120,53 +81,29 @@ translationType: machine
자세한 내용을 보려면 **Initial page load and route change** 클릭하세요.
-
+
그러면 **Page views** 으로 이동합니다.
-
+
페이지를 **Most time-consuming** 기준으로 정렬합니다.
-
+
초기 페이지를 로드하는 데 거의 90%의 시간이 걸립니다.
-
+
그것을 클릭하면 세부 정보를 볼 수 있습니다.
-
+
이 페이지에는 **Page view breakdown**, **Median initial page load time** 및 기타 중요한 세부정보가 표시됩니다. **Page view breakdown** 그래프는 페이지가 더 오래 걸리는 이유와 위치를 좁히는 데 도움이 되므로 여기서 특히 중요합니다. 이 그래프를 자세히 살펴보면 **Page rendering** 최대 5000밀리초까지 걸리는 것을 알 수 있습니다.
-
+
이제 초기 페이지를 렌더링하는 데 꽤 오랜 시간이 걸려 애플리케이션 속도가 느려진다는 사실을 알게 되었습니다. 다음으로, 렌더링 프로세스 속도를 늦추는 원인이 무엇인지 파악하기 위해 **Session traces** 를 관찰합니다.
@@ -176,31 +113,19 @@ translationType: machine
왼쪽 탐색에서 **Session traces** 으로 이동하여 **Page load** 의 내림차순으로 정렬합니다.
-
+
여기에서는 세션 트레이스가 **Page load** 시간 순서로 정렬된 것을 볼 수 있습니다.
-
+
목록에서 첫 번째 항목을 클릭합니다.
-
+
@@ -208,51 +133,31 @@ translationType: machine
여기서는 특정 세션에 대한 전체 트레이스를 볼 수 있습니다. 이 페이지에는 **Backend**, **Dom Processing**, **Page Load** 및 기타 트레이스 관련 정보도 표시됩니다.
-
+
**Page load** 이(가) 예상보다 오래 걸리고 있습니다. 로드에 대한 자세한 타임라인이 필요합니다. 타임라인을 조정하려면 포인터를 왼쪽과 오른쪽으로 스크롤하세요.
-
+
추적을 스크롤하여 시간 창을 이동하고 이 세션 동안 개별 이벤트의 세부 정보를 확인합니다.
-
+
특정 이벤트는 5초 이상 소요됩니다.
-
+
이벤트를 클릭하면 세부 정보를 볼 수 있습니다.
-
+
이미지라는 점에 유의하십시오. 특히 로드하는 데 5 - 6초가 걸리고 지연을 유발하는 애플리케이션의 배경 이미지입니다.
@@ -272,4 +177,4 @@ translationType: machine
잘하셨어요! 이제 모니터링을 시작했으므로 여정의 다음 단계를 수행하는 데 도움이 되는 몇 가지 문서가 있습니다.
* [브라우저 모니터링 소개](/docs/browser/browser-monitoring/getting-started/introduction-browser-monitoring/)
-* [브라우저 모니터링 기능](/docs/browser/new-relic-browser/browser-pro-features/intro-to-browser-pro-features)
+* [브라우저 모니터링 기능](/docs/browser/new-relic-browser/browser-pro-features/intro-to-browser-pro-features)
\ No newline at end of file
diff --git a/src/i18n/content/kr/docs/browser/new-relic-browser/page-load-timing-resources/instrumentation-browser-monitoring.mdx b/src/i18n/content/kr/docs/browser/new-relic-browser/page-load-timing-resources/instrumentation-browser-monitoring.mdx
index 8be28107080..b4861250a3d 100644
--- a/src/i18n/content/kr/docs/browser/new-relic-browser/page-load-timing-resources/instrumentation-browser-monitoring.mdx
+++ b/src/i18n/content/kr/docs/browser/new-relic-browser/page-load-timing-resources/instrumentation-browser-monitoring.mdx
@@ -156,11 +156,11 @@ https **and** http 웹페이지 모두 https를 통해 데이터를
|
- All other browser event data
+ 기타 모든 브라우저 이벤트 데이터
|
- See [Browser agent harvests](/docs/browser/new-relic-browser/performance-quality/browser-monitoring-performance-impact#agent-harvests)
+ [브라우저 에이전트 수집](/docs/browser/new-relic-browser/performance-quality/browser-monitoring-performance-impact#agent-harvests)보기
|
diff --git a/src/i18n/content/kr/docs/browser/new-relic-browser/performance-quality/browser-monitoring-performance-impact.mdx b/src/i18n/content/kr/docs/browser/new-relic-browser/performance-quality/browser-monitoring-performance-impact.mdx
index dbf0adb4e1e..818fdb5bcee 100644
--- a/src/i18n/content/kr/docs/browser/new-relic-browser/performance-quality/browser-monitoring-performance-impact.mdx
+++ b/src/i18n/content/kr/docs/browser/new-relic-browser/performance-quality/browser-monitoring-performance-impact.mdx
@@ -96,7 +96,7 @@ JavaScript의 오버헤드는 사용자에 대한 영향과 시스템 성능에
### 브라우저 에이전트 수확 [#agent-harvests]
-Browser events are first harvested after the PageView event is successfully collected, and then every 30 seconds thereafter. If any event type exceeds 16 kB of data before the next scheduled harvest, an early harvest is triggered for that event. Additionally, a final harvest occurs whenever the document transitions to `hidden` via a `visibilitychange` event (e.g. when a user navigates away, switches tabs, closes the tab, minimizes or closes the browser, or switches from the browser to another app if they're on a mobile device).
+브라우저 이벤트는 PageView 이벤트가 성공적으로 수집된 후 처음 수집되고 그 후 30초마다 수집됩니다. 다음에 예정된 수확 전에 이벤트 유형이 16kB의 데이터를 초과하면 해당 이벤트에 대해 조기 수확이 트리거됩니다. 또한, 문서가 `visibilitychange` 이벤트를 통해 `hidden` 으로 전환될 때마다 최종 수집이 발생합니다(예: 사용자가 다른 곳으로 이동하거나, 탭을 전환하거나, 탭을 닫거나, 브라우저를 최소화하거나 닫거나, 모바일 기기를 사용하는 경우 브라우저에서 다른 앱으로 전환하는 경우).
@@ -164,7 +164,7 @@ Browser events are first harvested after the PageView event is successfully coll
|
- `PageViewTiming` events are harvested by all agents and includes timing data like core web vitals measurements. See the [PageViewTiming docs](/docs/browser/new-relic-browser/page-load-timing-resources/pageviewtiming-async-or-dynamic-page-details/#interactivity-metrics) for a list of reported events.
+ `PageViewTiming` 이벤트는 모든 에이전트에 의해 수집되며 코어 웹 바이탈 측정과 같은 타이밍 데이터를 포함합니다. 보고된 이벤트 목록은 [PageViewTiming 문서를](/docs/browser/new-relic-browser/page-load-timing-resources/pageviewtiming-async-or-dynamic-page-details/#interactivity-metrics) 참조하세요.
|
@@ -186,7 +186,7 @@ Browser events are first harvested after the PageView event is successfully coll
- `JavaScriptError` metrics are sent together with Ajax metrics as timeslice data.
+ `JavaScriptError` 메트릭은 Ajax 메트릭과 함께 타임슬라이스 데이터로 전송됩니다.
|
@@ -230,7 +230,7 @@ Browser events are first harvested after the PageView event is successfully coll
- `AjaxRequest` events follows the 30 seconds harvest cycle unless the `SPA` agent is in use. If using the `SPA` agent, the first harvest will happen after the `load` page lifecycle event and additional harvests will either happen every 30 seconds or when the `SPA` agent notices a route change.
+ `AjaxRequest` `SPA` 에이전트를 사용하지 않는 한 이벤트는 30초 하베스트 조치를 따릅니다. `SPA` 에이전트를 사용하는 경우 첫 번째 수집은 `load` 페이지 수명 주기 이벤트 이후에 발생하고 추가 수집은 30초마다 발생하거나 `SPA` 에이전트가 경로 변경을 감지할 때 발생합니다.
|
@@ -252,7 +252,7 @@ Browser events are first harvested after the PageView event is successfully coll
- Session traces can generate a large amount of data, but that can be controlled by sampling. By default, only about 90 page views per hour will be sampled to send session trace data. There is also an option to set a custom sampling rate.
+ 세션 트레이스는 많은 양의 데이터를 생성할 수 있지만, 샘플링을 통해 제어할 수 있습니다. 기본적으로 시간당 약 90개의 페이지 뷰만 샘플링되어 세션 트레이스 데이터를 전송합니다. 사용자 정의 샘플링 속도를 설정하는 옵션도 있습니다.
|
@@ -274,7 +274,7 @@ Browser events are first harvested after the PageView event is successfully coll
- In addition to the the general harvest cycles, session replay harvests that include snapshots and metadata payloads will be harvested immediately.
+ 일반 하베스트 서버 외에도 스냅샷이 포함된 세션 리플레이 수집과 메타페이데이터로드가 즉시 수집됩니다.
엔드포인트는 로케일에 따라 다를 수 있지만 미국의 예는 `https://bam.nr-data.net/browser/blobs` 입니다.
|
@@ -318,13 +318,13 @@ Browser events are first harvested after the PageView event is successfully coll
- `BrowserInteraction` events are harvested immediately after the interaction finishes. There will always be at least one interaction that represents the initial page load. Additional interactions are collected only if the URL changes (representing route change). `AjaxRequest` events are also harvested at the same time if they occur during an interaction.
+ `BrowserInteraction` 이벤트는 상호작용이 끝난 직후에 수집됩니다. 초기 페이지 로드를 나타내는 상호작용은 항상 하나 이상 발생합니다. 추가 상호작용은 URL이 변경되는 경우(경로 변경을 나타냄)에만 수집됩니다. `AjaxRequest` 이벤트는 블록결합 중에 발생하는 경우에도 동시에 수집됩니다.
|
|
- Browser logs
+ 브라우저 로그
|
@@ -344,7 +344,7 @@ Browser events are first harvested after the PageView event is successfully coll
|
|
- [UserAction](/attribute-dictionary/?event=UserAction) events
+ [UserAction](/attribute-dictionary/?event=UserAction) 이벤트
|
@@ -364,7 +364,7 @@ Browser events are first harvested after the PageView event is successfully coll
|
|
- [BrowserPerformance](/attribute-dictionary/?event=BrowserPerformance) events
+ [브라우저 성능](/attribute-dictionary/?event=BrowserPerformance) 이벤트
|
diff --git a/src/i18n/content/kr/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/manual.mdx b/src/i18n/content/kr/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/manual.mdx
new file mode 100644
index 00000000000..faa42c73700
--- /dev/null
+++ b/src/i18n/content/kr/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/manual.mdx
@@ -0,0 +1,72 @@
+---
+title: AWS 콘솔에서 수동으로 통합
+tags:
+ - Integrate manually
+ - Manual integration
+ - AWS metric integration
+ - Amazon integrations
+ - AWS integrations
+metaDescription: Integrate New Relic with AWS services manually from the AWS console.
+freshnessValidatedDate: never
+translationType: machine
+---
+
+AWS 계정과 뉴렐릭을 원활하게 통합하려면 [CloudFormation 및 CloudWatch Metric Streams를 통한 통합](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation) 이 가장 권장되는 방법입니다. CloudFormation 템플릿을 사용할 수 없고 Terraform을 사용하고 싶지 않은 경우 다음 절차에 따라 AWS 콘솔에서 수동으로 통합하세요.
+
+## 전제 조건 [#prerequisites]
+
+AWS 계정을 뉴렐릭과 통합하기 전에 다음 필수 조건을 충족하는지 확인하세요.
+
+* **A 뉴렐릭 [Ingest - 볼륨 키 및 사용자 키](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]
+
+AWS 계정을 뉴렐릭과 통합하려면 다음 단계를 따르세요.
+
+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**: Manually integrate your AWS account
+
+5. **Select services** 화면에서 필요한 경우 **Show resources not supported by CloudWatch Metric Streams** 토글을 사용하여 모니터링하려는 서비스를 선택한 다음 계속합니다.
+
+6. **Choose data integration type** 화면에서 다음 통합 옵션 중에서 선택하세요.
+
+ * **실시간 AWS 모니터링(권장)**: 이 옵션은 CloudWatch Metric Streams 지원하는 서비스를 위한 것입니다.
+ * **API 폴링**: 이 옵션은 CloudWatch Metric Streams에서 지원하지 않는 서비스에 적합합니다.
+
+7. **Create role** 페이지에서 **Configure budgets policy** 페이지로 화면의 지침을 따르고 AWS 콘솔에서 단계를 수행합니다.
+
+8. AWS 콘솔에서 정책을 만든 후 뉴렐릭 플랫폼으로 전환하고 뉴렐릭에 AWS 데이터가 표시될 때까지 안내에 따라 통합을 계속 진행합니다.
+
+## 관련 주제 [#related-topics]
+
+
+
+ 여러 AWS 계정에서 데이터를 수집하는 방법을 알아보세요.
+
+
+
+ CloudWatch Metric Streams의 지표를 탐색하고 사용하세요.
+
+
+
+ CloudFormation 및 CloudWatch Metric Streams 사용하여 AWS 서비스를 뉴렐릭과 통합합니다.
+
+
+
+ CloudFormation 및 API 폴링을 사용하여 AWS 서비스를 뉴렐릭과 통합하세요.
+
+
+
+ Terraform을 사용하여 AWS 서비스를 뉴렐릭과 통합합니다.
+
+
\ No newline at end of file
diff --git a/src/i18n/content/kr/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/migrate-from-api-polling-to-cwms.mdx b/src/i18n/content/kr/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/migrate-from-api-polling-to-cwms.mdx
new file mode 100644
index 00000000000..28e8475debd
--- /dev/null
+++ b/src/i18n/content/kr/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/migrate-from-api-polling-to-cwms.mdx
@@ -0,0 +1,111 @@
+---
+title: API 폴링에서 CloudWatch Metric Streams으로 마이그레이션
+tags:
+ - API polling to CWMS migration
+metaDescription: Migrate your New Relic and AWS services integration type from API Polling to CloudWatch Metric Streams.
+freshnessValidatedDate: never
+translationType: machine
+---
+
+AWS 계정과 뉴렐릭을 원활하게 통합하려면 [CloudFormation 및 CloudWatch Metric Streams를 통한 통합](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation) 이 가장 권장되는 방법입니다. 하지만 API 폴링을 사용하여 AWS 계정을 뉴렐릭과 이미 통합한 경우 다음 절차를 참조하여 API 폴링에서 CloudWatch Metric Streams 으로 마이그레이션하세요.
+
+## 전제 조건 [#prerequisites]
+
+AWS 계정을 뉴렐릭과 통합하기 전에 다음 필수 조건을 충족하는지 확인하세요.
+
+* **A 뉴렐릭 [Ingest - 볼륨 키 및 사용자 키](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)** : 뉴렐릭 계정에 대해 다음 권한이 필요합니다.
+* 여러 AWS 계정을 관리하는 사용자의 경우 [각 계정을 단일 뉴렐릭 계정에 연결합니다](/docs/infrastructure/amazon-integrations/manage-aws-data/aws-multi-account).
+* 해당 계정 내에서 여러 지역을 관리하는 사용자의 경우 각 지역의 뉴렐릭을 가리키는 별도의 Kinesis Data Firehose를 만들어야 합니다.
+
+
+
+ ## CloudWatch Metric Streams 통합으로 마이그레이션 [#migrate]
+
+ CloudFormation 템플릿을 생성하거나 AWS 계정을 다시 추가하고 앱 내 안내 설치 절차를 따르면 API 폴링에서 마이그레이션할 수 있습니다. 가장 효율적인 마이그레이션 방법인 CloudFormation 템플릿 방법을 사용하는 것이 좋습니다. 이러한 통합은 CloudWatch Metric Streams 에서 지원되지 않으며 당사의 통합으로 마이그레이션할 수 없습니다.
+
+ * AWS 클라우드 트레일
+ * AWS 상태
+ * AWS 신뢰할 수 있는 고문
+ * AWS 엑스레이
+
+ 이러한 통합을 사용하는 경우에도 API 폴링 방법을 사용해야 합니다.
+
+
+
+ CloudFormation 템플릿을 사용하면 폴링 설정에 따라 미리 구성된 네임스페이스로 템플릿을 업데이트할 수 있습니다.
+
+ 1. **[one.newrelic.com > Infrastructure > AWS](https://one.newrelic.com/infra/infrastructure/cloud-aws)** 로 이동한 다음 **Migrate to CloudWatch Metric stream** 클릭합니다.
+ 2. 절차를 따르세요. 템플릿을 다운로드한 다음 API 폴링에서 네임스페이스를 복제합니다. 다운로드한 템플릿에 계정 세부 정보를 추가하세요.
+ 3. AWS Console 에서 **Cloud Formation > Create Stack > Upload a template file** 로 이동합니다. 업데이트된 CloudFormation 템플릿을 업로드하세요.
+
+
+
+ CloudFormation 방법을 사용하지 않으려면 AWS 계정을 폴링 통합과 이미 연결했더라도 AWS 계정을 다시 추가해야 합니다. 이러한 절차를 수행하려면 이 문서를 종료해야 할 수도 있지만, 폴링 통합을 비활성화하려면 다시 돌아와야 합니다.
+
+ 1. **[one.newrelic.com > All capabilities >Infrastructure > AWS](https://one.newrelic.com/infra/infrastructure/cloud-aws)** 로 이동한 다음 **Add AWS account** 클릭하세요. 원하는 방법을 선택하세요.
+ 2. 이 문서의 [AWS Console 흐름](/install/aws-cloudwatch/?task=console) 에서AWS Console 단계를 따르세요.
+ 3. 이전 AWS 공급자 계정에서 [불필요한 모든 폴링 통합을 비활성화합니다](/docs/infrastructure/amazon-integrations/connect/uninstall-aws/) .
+
+ 비활성화할 경우 [일부 통합은 CloudWatch Metric Streams에서 지원되지 않는다는](/docs/infrastructure/amazon-integrations/connect/connect-aws-new-relic-infrastructure-monitoring/) 점을 명심하세요.
+
+
+
+ CloudWatch Metric Streams 통합은 지표 API 사용하여 [차원 지표](/docs/data-apis/understand-data/new-relic-data-types/#dimensional-metrics) 형식으로 지표를 푸시합니다. 반면에 우리의 API 폴링 방법은 [이벤트를](/docs/data-apis/understand-data/new-relic-data-types/#events-new-relic) 기반으로 메트릭을 푸시합니다.
+
+ * 전환을 돕기 위해 우리는 여러분이 어떤 형식으로든 쿼리를 작성할 수 있게 해주는 쉬밍 메커니즘을 제공합니다. 이러한 쿼리는 이벤트에서 메트릭으로, 메트릭에서 이벤트로 사용 가능한 소스를 기반으로 예상대로 처리됩니다.
+ * CloudWatch Metric Streams 통합을 사용하여 이벤트 기반 쿼리를 사용할 수 있게 해주는 시밍 메커니즘에 대한 [몇 가지 제한 사항을](/docs/query-your-data/nrql-new-relic-query-language/nrql-query-tutorials/query-infrastructure-dimensional-metrics-nrql/#known-limitations) 검토하는 것이 좋습니다.
+
+ 마이그레이션 후 API 폴링 데이터에 의존하는 일부 뉴렐릭 기능이 다르게 동작할 수 있습니다.
+
+ * **Dashboards**: 폴링 기반 AWS 통합 이벤트를 사용하는 사용자 정의 대시보드는 예상대로 계속 작동합니다.
+ * **Alerts**: 폴링 기반 AWS 이벤트를 사용하는 공지 조건은 계속 작동합니다. NRQL 소스로 사용하는 차원 지표 형식에 맞게 조정하는 것이 좋습니다.
+ * **Entities**: 모니터링되는 부분 목록에는 최대 24시간 동안 중복된 부분이 표시될 수 있습니다.
+ * **Attributes**: 폴 기반 AWS 통합은 수집된 리소스 태그에 `label.` 접두사를 붙이는 반면, AWS CloudWatch Metric Streams 통합은 수집된 리소스 태그에 `tags.` 접두사를 붙입니다. 동일한 AWS 계정에 대해 두 통합이 모두 활성화된 경우 이벤트 형식을 사용할 때 리소스 태그가 두 접두사 아래에 표시됩니다.
+
+
+
+ ## 귀하의 데이터를 검증하세요 [#validate-data]
+
+ Metric Streams에서 데이터를 수신하고 있는지 확인하려면 다음 단계를 따르세요.
+
+ 1. **[one.newrelic.com > All capabilities > Infrastructure > AWS](https://one.newrelic.com/infra/infrastructure/cloud-aws)** 로 이동합니다. 연결한 AWS 계정을 검색하세요. **Stream** 개 계정.
+ 2. 대시보드에서 계정 상태를 확인하고 뉴렐릭이 지표 데이터를 수신하는지 확인하세요. 여기에는 오류와 수집된 네임스페이스 및 메트릭 수가 포함될 수 있습니다.
+ 3. 특정 메트릭 세트에 대한 쿼리를 작성하여 데이터를 탐색합니다.
+
+ 뉴렐릭이 새로운 리소스를 감지하고 이를 합성하는 데 몇 분이 걸릴 수 있습니다.
+
+
+ AWS Billing 과 같은 글로벌 서비스에 대한 AWS CloudWatch 지표는 **us-east-1** 지역에서만 사용할 수 있습니다. 해당 지역에 활성 CloudWatch Metric Streams가 구성되어 있는지 확인하세요.
+
+
+
+
+## 관련 주제 [#related-topics]
+
+
+
+ 여러 AWS 계정에서 데이터를 수집하는 방법을 알아보세요.
+
+
+
+ CloudWatch Metric Streams의 지표를 탐색하고 사용하세요.
+
+
+
+ CloudFormation 및 CloudWatch Metric Streams 사용하여 AWS 서비스를 뉴렐릭과 통합합니다.
+
+
+
+ CloudFormation 및 API 폴링을 사용하여 AWS 서비스를 뉴렐릭과 통합하세요.
+
+
+
+ Terraform을 사용하여 AWS 서비스를 뉴렐릭과 통합합니다.
+
+
+
+ AWS 콘솔에서 AWS 서비스를 뉴렐릭과 수동으로 통합하세요.
+
+
\ No newline at end of file
diff --git a/src/i18n/content/kr/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/terraform.mdx b/src/i18n/content/kr/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/terraform.mdx
new file mode 100644
index 00000000000..36ec8752370
--- /dev/null
+++ b/src/i18n/content/kr/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/terraform.mdx
@@ -0,0 +1,65 @@
+---
+title: Terraform과 통합
+tags:
+ - Integrate with Terraform
+ - AWS metric integration
+ - Amazon integrations
+ - AWS integrations
+metaDescription: Integrate New Relic with AWS services using Terraform.
+freshnessValidatedDate: never
+translationType: machine
+---
+
+AWS 계정과 뉴렐릭을 원활하게 통합하려면 [CloudFormation 및 CloudWatch Metric Streams를 통한 통합](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation) 이 가장 권장되는 방법입니다. 이미 Terraform을 사용하여 AWS 계정과 서비스를 관리하고 있다면 다음 통합 방법을 선호할 수 있습니다. 뉴렐릭은 통합 설정을 간소화하는 AWS 클라우드 통합 모듈을 제공하기 때문입니다.
+
+## 전제 조건 [#prerequisites]
+
+AWS 계정을 뉴렐릭과 통합하기 전에 다음 필수 조건을 충족하는지 확인하세요.
+
+* 클라우드 통합 **[권한](/docs/accounts/accounts-billing/new-relic-one-user-management/user-permissions/#infrastructure)** : 뉴렐릭 계정에 대해 다음 권한이 필요합니다.
+* AWS 에 연결하려는 뉴렐릭 계정 ID 및 지역입니다.
+
+## 통합 단계 [#integration-steps]
+
+AWS 계정을 뉴렐릭과 통합하려면 다음 단계를 따르세요.
+
+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 with Terraform
+
+5. **Select services** 화면에서 필요한 경우 **Show resources not supported by CloudWatch Metric Streams** 토글을 사용하여 모니터링하려는 서비스를 선택한 다음 계속합니다.
+
+6. **Terraform** 화면에서 Terraform 공급자 계정과 뉴렐릭 계정을 연결하는 방법을 안내하는 설명서를 엽니다.
+
+7. 성공적으로 통합한 후에는 AWS 데이터를 Newrellic에서 볼 수 있습니다.
+
+## 관련 주제 [#related-topics]
+
+
+
+ 여러 AWS 계정에서 데이터를 수집하는 방법을 알아보세요.
+
+
+
+ CloudWatch Metric Streams의 지표를 탐색하고 사용하세요.
+
+
+
+ CloudFormation 및 CloudWatch Metric Streams 사용하여 AWS 서비스를 뉴렐릭과 통합합니다.
+
+
+
+ CloudFormation 및 API 폴링을 사용하여 AWS 서비스를 뉴렐릭과 통합하세요.
+
+
+
+ AWS 콘솔에서 AWS 서비스를 뉴렐릭과 수동으로 통합하세요.
+
+
\ No newline at end of file
diff --git a/src/i18n/content/kr/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-and-api-polling.mdx b/src/i18n/content/kr/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-and-api-polling.mdx
new file mode 100644
index 00000000000..d7efd399ecb
--- /dev/null
+++ b/src/i18n/content/kr/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-and-api-polling.mdx
@@ -0,0 +1,77 @@
+---
+title: CloudFormation 및 API 폴링을 통한 통합
+tags:
+ - Integration via CloudFormation
+ - AWS metric integration
+ - Amazon integrations
+ - AWS integrations
+ - Integration with API polling via CloudFormation
+metaDescription: Integrate New Relic with AWS services using CloudFormation templates to automate the setup of API polling for metrics ingestion.
+freshnessValidatedDate: never
+translationType: machine
+---
+
+AWS 계정과 뉴렐릭을 원활하게 통합하려면 [CloudFormation 및 CloudWatch Metric Streams를 통한 통합](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation) 이 가장 권장되는 방법입니다. 특정 데이터 검색 제한 사항을 통합하기 위해 API 폴링을 활용할 수도 있습니다. 자세한 내용은 [AWS 메트릭 수집](/docs/infrastructure/amazon-integrations/get-started/introduction-aws-integrations/#aws-metrics-ingestion) 의 비교 표를 참조하세요. CloudWatch Metric Streams에서 지원하지 않는 서비스에만 API 폴링을 사용하는 것이 좋습니다.
+
+## 전제 조건 [#prerequisites]
+
+AWS 계정을 뉴렐릭과 통합하기 전에 다음 필수 조건을 충족하는지 확인하세요.
+
+* **A 뉴렐릭 [Ingest - 볼륨 키 및 사용자 키](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 및 API 폴링을 사용하여 AWS 계정을 뉴렐릭과 통합하려면 다음 단계를 따르세요.
+
+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**: API Polling
+
+5. **Select services** 화면에서 필요한 경우 **Show resources not supported by CloudWatch Metric Streams** 토글을 사용하여 모니터링하려는 서비스를 선택한 다음 계속합니다.
+
+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. Ingest - 인스턴스 키와 사용자 키를 AWS 콘솔에 붙여넣습니다.
+
+
+ AWS 서비스에서 추가 메타데이터를 얻으려면 AWS 콘솔에서 **AWS Config** 활성화하세요.
+
+
+10. CloudFormation 그리드를 구현하고 배포하려면 AWS 콘솔에서 **Create stack** 선택합니다. 택시 리소스 생성에는 몇 분이 걸릴 수 있으며, 메트릭 전달을 구성하는 방법에 따라 여러 택시가 생성될 수 있습니다. 그리드 생성에 실패할 경우 [문제 해결, 해결 절차를](https://docs.newrelic.com/docs/logs/troubleshooting/aws-log-integration-issues/stack-creation-fails/) 참조하세요.
+11. 그리드 생성이 성공적으로 완료되면 뉴렐릭 플랫폼으로 전환하고 뉴렐릭에서 AWS 데이터가 표시될 때까지 통합 안내를 계속 진행하세요.
+
+## 관련 주제 [#related-topics]
+
+
+
+ 여러 AWS 계정에서 데이터를 수집하는 방법을 알아보세요.
+
+
+
+ CloudWatch Metric Streams의 지표를 탐색하고 사용하세요.
+
+
+
+ CloudFormation 및 CloudWatch Metric Streams 사용하여 AWS 서비스를 뉴렐릭과 통합합니다.
+
+
+
+ Terraform을 사용하여 AWS 서비스를 뉴렐릭과 통합합니다.
+
+
+
+ AWS 콘솔에서 AWS 서비스를 뉴렐릭과 수동으로 통합하세요.
+
+
\ No newline at end of file
diff --git a/src/i18n/content/kr/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms.mdx b/src/i18n/content/kr/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms.mdx
new file mode 100644
index 00000000000..0a4473c14c2
--- /dev/null
+++ b/src/i18n/content/kr/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms.mdx
@@ -0,0 +1,86 @@
+---
+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 계정을 뉴렐릭과 통합하기 전에 다음 필수 조건을 충족하는지 확인하세요.
+
+* **A 뉴렐릭 [Ingest - 볼륨 키 및 사용자 키](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** 선택하고 계속 진행합니다.
+
+
+
+
+ 지원되지 않는 서비스에 대해 선택된 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. Ingest - 인스턴스 키와 사용자 키를 AWS 콘솔에 붙여넣습니다.
+
+
+ AWS 서비스에서 추가 메타데이터를 얻으려면 AWS 콘솔에서 **AWS Config** 활성화하세요.
+
+
+10. CloudFormation 그리드를 구현하고 배포하려면 AWS 콘솔에서 **Create stack** 선택합니다. 택시 리소스 생성에는 몇 분이 걸릴 수 있으며, 메트릭 전달을 구성하는 방법에 따라 여러 택시가 생성될 수 있습니다. 그리드 생성에 실패할 경우 [문제 해결, 해결 절차를](https://docs.newrelic.com/docs/logs/troubleshooting/aws-log-integration-issues/stack-creation-fails/) 참조하세요.
+
+11. 그리드 생성이 성공적으로 완료되면 뉴렐릭 플랫폼으로 전환하고 뉴렐릭에서 AWS 데이터가 표시될 때까지 통합 안내를 계속 진행하세요.
+
+## 관련 주제 [#related-topics]
+
+
+
+ 여러 AWS 계정에서 데이터를 수집하는 방법을 알아보세요.
+
+
+
+ CloudWatch Metric Streams의 지표를 탐색하고 사용하세요.
+
+
+
+ CloudFormation 및 API 폴링을 사용하여 AWS 서비스를 뉴렐릭과 통합하세요.
+
+
+
+ Terraform을 사용하여 AWS 서비스를 뉴렐릭과 통합합니다.
+
+
+
+ AWS 콘솔에서 AWS 서비스를 뉴렐릭과 수동으로 통합하세요.
+
+
\ No newline at end of file
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** 선택하고 계속 진행합니다.
+
+
+
+
+ 지원되지 않는 서비스에 대해 선택된 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/amazon-integrations/get-started/introduction-aws-integrations.mdx b/src/i18n/content/kr/docs/infrastructure/amazon-integrations/get-started/introduction-aws-integrations.mdx
index f0450c64e35..6d0e4604f21 100644
--- a/src/i18n/content/kr/docs/infrastructure/amazon-integrations/get-started/introduction-aws-integrations.mdx
+++ b/src/i18n/content/kr/docs/infrastructure/amazon-integrations/get-started/introduction-aws-integrations.mdx
@@ -181,14 +181,14 @@ AWS 계정을 뉴렐릭과 연결하여 메트릭 수집을 수행하려면 다
이러한 서비스와 함께 다른 AWS 서비스를 활용하는 경우에도 Amazon CloudWatch Metric Streams 통합을 선택할 수 있습니다. 설정 중에 뉴렐릭은 이러한 지원되지 않는 서비스에 대해 특별히 API 폴링을 구성하는 옵션을 제공합니다.
-Following are the ways to integrate your AWS services with New Relic:
+다음은 AWS 서비스를 뉴렐릭과 통합하는 방법입니다.
-* [Via CloudFormation and CloudWatch metric stream](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms).
-* [Via CloudFormation and API Polling](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-and-api-polling).
-* [Via Terraform](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/terraform).
-* [Manually from AWS console](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/manual).
+* [CloudFormation 및 CloudWatch Metric Streams를 통해](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms).
+* [CloudFormation 및 API 폴링을 통해](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-and-api-polling).
+* [Terraform을 통해](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/terraform).
+* [AWS 콘솔에서 수동으로](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/manual).
-If you have already integrated your AWS account with New Relic using API Polling, refer to the [migration procedure](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/migrate-from-api-polling-to-cwms) to migrate to CloudWatch Metric Streams.
+API 폴링을 사용하여 AWS 계정을 뉴렐릭과 이미 통합한 경우 CloudWatch Metric Streams 로 마이그레이션하기 위한 [마이그레이션 절차를](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/migrate-from-api-polling-to-cwms) 참조하세요.
### AWS 통합 비용 [#aws-costs]
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은 온라인 도움말, 문제 해결 도구, 자세한 절차 및 문
-## 무료 지원 포럼인 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
```
-
+ /* <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}})
```
-
+ /* <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}}
```
-
+ /* <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
```
-
+ /* <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
```
-
+ /* <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
```
-
+ /* <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`
-
+ /* <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}}
```
-
+ /* <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
```
-
+ /* <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
```
-
+ /* <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:
-
+ * **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}}
```
-
+ /* <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`
-
+ /* <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
```
-
+ /* <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}})
```
-
+ /* <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` 절이 있는 경우 최신 값이 쿼리를 실행하는 데 사용됩니다.
-
+ /* <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/agent-release-notes/java-release-notes/java-agent-8240.mdx b/src/i18n/content/kr/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8240.mdx
index f28004846c9..22489e3f20e 100644
--- a/src/i18n/content/kr/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8240.mdx
+++ b/src/i18n/content/kr/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8240.mdx
@@ -7,8 +7,8 @@ features:
- “Support MongoDB Reactive Streams 5.2.0 and up”
- “Jedis 6 support”
bugs:
- - “CouchBase: Add skip class to prevent double instrumentation”
- - “Spring WebClient 5.x: Only wrap headers instead of the entire response”
+ - 'CouchBase: Add skip class to prevent double instrumentation'
+ - 'Spring WebClient 5.x: Only wrap headers instead of the entire response'
security: []
translationType: machine
---
diff --git a/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx b/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx
new file mode 100644
index 00000000000..44ee3a23503
--- /dev/null
+++ b/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx
@@ -0,0 +1,267 @@
+---
+subject: Docs
+releaseDate: '2025-07-25'
+version: 'June 13 - July 24, 2025'
+translationType: machine
+---
+
+### 새로운 문서
+
+* 에이전트 버전 1.285.0 이상에서 향상된 문제 해결을 위한 세부 로깅, 네트워크 요청 모니터링, 검사 이벤트를 포함하여 [뉴렐릭 브라우저 에이전트 문제를 디버깅하는 방법](/docs/browser/new-relic-browser/troubleshooting/how-to-debug-browser-agent/) 에 대한 새로운 기능이 추가되었습니다.
+* `python` 및 `.node.js` 함수 모니터링에 대한 [Azure Functions](/docs/serverless-function-monitoring/azure-function-monitoring/introduction-azure-monitoring/) 지원이 추가되었습니다.
+* 뉴렐릭 플랫폼에서 비효율성을 식별하고, 최적화 권장 사항을 제공하고, CCU 절감액을 추정하는 기능을 통해 컴퓨트 효율성을 향상시키기 위해 실행 가능한 인사이트를 위한 [비용 최적화 기능](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/compute-optimizer/) 을 추가했습니다.
+* [클라우드 비용 인텔리전스](/docs/cci/getting-started/overview) 가 추가되어 포괄적인 비용 분석, Kubernetes 비용 할당, 미래 비용 추정, 계정 간 데이터 수집 등의 기능을 포함하여 cloud 비용의 가시성과 관리를 위한 도구를 제공하며 현재는 AWS 클라우드 비용만 지원합니다.
+* Helm 차트를 통한 클러스터의 원활한 모니터링을 위해 [뉴렐릭 기능 제공자 독립적 통합이 포함된 Kubernetes 용OpenTelemetry 옵저버빌리티가](/docs/kubernetes-pixie/k8s-otel/intro/) 추가되었으며, 메트릭, 이벤트에 대한 텔메트리 신호가 향상되고 뉴렐릭 도구와 대시보드로 전송됩니다.
+* [Windows 통합에 대한 제한 사항 및 문제 해결, 해결](/docs/kubernetes-pixie/kubernetes-integration/troubleshooting/troubleshooting-windows/)추가
+* [CloudFormation 및 CloudWatch Metric Streams를](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms/) 통해 AWS 통합을 추가하여 지원되지 않는 서비스에 대한 API 폴링을 지원합니다.
+* MySQL 및 MS SQL Server용 온호스트 통합을 통해 데이터베이스 부분 모니터용 [뉴렐릭 데이터베이스 처리에 대한 향상된 태그를](/docs/infrastructure/host-integrations/db-entity-tags/) 추가하여 청구 또는 기존 텔레메트리에 영향을 주지 않고 메타데이터 인사이트 및 뉴렐릭 조직을 강화했습니다.
+
+### 주요 변경 사항
+
+* [NRQL 참조](/docs/nrql/nrql-syntax-clauses-functions/#non-aggregator-functions/) 에 집계자 이외의 함수를 추가했습니다.
+* [루비 에이전트 요구 사항을 업데이트하고 프레임워크를 지원했습니다](/docs/apm/agents/ruby-agent/getting-started/ruby-agent-requirements-supported-frameworks/).
+* [뉴렐릭 문서의OpenTelemetry 로그인에](/docs/opentelemetry/best-practices/opentelemetry-best-practices-logs/#custom-events) 뉴렐릭 커스텀 대시보드로 로그를 추가했습니다.
+* [범용 Azure Functions에 대한 호환성 및 요구 사항](/docs/serverless-function-monitoring/azure-function-monitoring/compatibility-requirement-azure-monitoring/#supported-runtimes) 문서에서 Linux, Windows 및 컨테이너화된 함수에 대해 지원되는 런타임이 업데이트되었습니다.
+* [Confluent 클라우드 통합에](/docs/message-queues-streaming/installation/confluent-cloud-integration/#metrics) 대한 메트릭 데이터를 업데이트했습니다.
+* [Node.js 에이전트 설정](/docs/apm/agents/nodejs-agent/installation-configuration/nodejs-agent-configuration/) 에서 GCP Cloud Run을 삭제했습니다.
+* .NET 에이전트에서 지원하는 추가 라이브러리를 포함하도록 [AI 모니터링에 대한 호환성 및 요구 사항이](/docs/ai-monitoring/compatibility-requirements-ai-monitoring/) 업데이트되었습니다.
+* [뉴렐릭 네트워크 트래픽](/docs/new-relic-solutions/get-started/networks/#new-relic-endpoints) 에 뉴렐릭 플래메트리 듀얼 스택 엔드포인트를 추가했습니다.
+* [Google Cloud Load Balancing 모니터링 통합](/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-load-balancing-monitoring-integration/) 에 `GcpHttpExternalRegionalLoadBalancerSample` 추가했습니다.
+* [신세틱스 작업 관리자 문서를 설치하는](/docs/synthetics/synthetic-monitoring/private-locations/install-job-manager/#-install) 방법에 대한 OpenShift 시작 절차를 추가했습니다.
+* [Node.js 에이전트 버전 12를](/docs/apm/agents/nodejs-agent/installation-configuration/update-nodejs-agent/) 업데이트했습니다.
+* [CloudFormation 및 CloudWatch Metric Streams활용한AWS ](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms/)용 원활한 통합을 추가했으며, API 폴링도 지원합니다.
+
+### 사소한 변경 사항
+
+* [프로세서 트레이스](/docs/data-apis/manage-data/manage-data-retention/#retention-periods/) 의 보존 기간으로 `Transaction` 추가했습니다.
+* [알림 규칙 및 제한](/docs/alerts/admin/rules-limits-alerts/) 에 `Destination` 새 카테고리로 추가했습니다.
+* [Azure Native 서비스 소개](/docs/infrastructure/microsoft-azure-integrations/get-started/azure-native/) 문서에 Azure 리소스의 진단 설정이 올바르게 구성되었는지 확인하거나 Azure Native 서비스를 통한 전달을 비활성화하여 데이터가 Azure Native 플랫폼으로 전송되지 않도록 하는 콜아웃을 추가했습니다.
+* [.NET 에이전트](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements/) 에 대한 최신 호환 라이브러리를 업데이트했습니다.
+* iOS SDK 버전 7.5.4부터 시작되는 내용을 알리기 위해 [iOS 에이전트 릴리스 노트](/docs/release-notes/mobile-release-notes/ios-release-notes/index/) 문서에 콜아웃을 추가했습니다. 이제 변경 사항으로 인해 이전에 억제되었던 처리된 예외 이벤트가 보고됩니다.
+* Kubernetes 환경에 대한 리소스 속성 및Kubernetes 가 아닌 환경에 대한 `container.id` 지정에 대한 서비스-컨테이너 관계에 대한 요구 사항을 업데이트하여 [뉴렐릭에서OpenTelemetry 리소스](/docs/opentelemetry/best-practices/opentelemetry-best-practices-resources/) 에 대한 적절한 텔레메트리 설정을 보장합니다.
+* [특정 구현 에이전트](/docs/infrastructure/infrastructure-agent/new-relic-guided-install-overview/#install-specific-versions) 버전 설치에 대한 CLI 지원이 추가되어 일관된 구현, 배포 및 시스템 호환성이 가능해졌습니다. 레시피 이름에 `@X.XX.X` 사용하여 버전을 지정합니다.
+* UI 에서 **Manage Account Cardinality**, **Manage Indicator Cardinality**, **Create Pruning Rules** 기능을 사용하기 위한 역할 액세스 요구 사항을 강조하는 콜아웃을 추가했습니다. [Cardinality Management](/docs/data-apis/ingest-apis/metric-api/cardinality-management/#attributes-table) 에서 권한이 설정되어 있는지 확인하세요.
+* [Node.js 에이전트의 호환성 및 요구 사항을](/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent/) `v12.23.0` 으로 업데이트했습니다.
+* [Elasticsearch를](/docs/infrastructure/host-integrations/host-integrations-list/elasticsearch/elasticsearch-integration) 설정하는 데 필요한 최소 권한을 추가했습니다.
+* [NRQL 공지 구문](/docs/alerts/create-alert/create-alert-condition/create-nrql-alert-conditions/) 에 대한 `FACET` 속성 최대 허용 제한 사용 값을 5000에서 20000으로 업데이트했습니다.
+
+### 릴리즈 정보
+
+* [`SystemSample`, `ProcessSample`, `NetworkSample` 및 `StorageSample`의 인프라 이벤트를 타겟으로 하는 삭제 규칙](/eol/2025/05/drop-rule-filter/)의 수명 종료 날짜로 2026년 1월 7일을 발표함
+
+* [공지 조건의 messageId 및 타임스탬프에 대한 FACET](/eol/2025/07/deprecating-alert-conditions/) 의 수명 종료가 즉시 발효됩니다.
+
+* 2025년 10월 28일을 [Attention Required](/eol/2025/07/upcoming-eols/) 의 수명 종료일로 발표했습니다.
+
+* 새로운 소식 게시물을 확인하세요.
+
+ * [Microsoft Teams에 직접 공지 보내기](/whats-new/2025/03/whats-new-03-13-microsoft-teams-integration/)
+ * [뉴렐릭 컴퓨팅 Optimizer가 정식 출시되었습니다!](/whats-new/2025/06/whats-new-06-25-compute-optimizer/)
+ * [통합 쿼리 탐색기에서 계정 간 쿼리 로그](/whats-new/2025/07/whats-new-07-01-logs-uqe-cross-account-query/)
+ * [OpenTelemetry를 활용한 Kubernetes 모니터링이 정식 출시되었습니다!](/whats-new/2025/07/whats-new-7-01-k8s-otel-monitoring/)
+ * [Kubernetes용 Windows 노드 모니터링이 이제 공개 미리 보기로 제공됩니다.](/whats-new/2025/07/whats-new-07-04-k8s-windows-nodes-preview/)
+ * [성능 문제 정확히 파악: 페이지 뷰 및 Core Web Vitals에 대한 고급 필터링](/whats-new/2025/07/whats-new-07-09-browser-monitoring/)
+ * [이제 최신 오류별로 정렬할 수 있습니다.](/whats-new/2025/07/whats-new-7-08-ei-sort-by-newest/)
+ * [귀하의 브라우저 데이터, 귀하의 이용 약관: 새로운 제어 옵션](/whats-new/2025/07/whats-new-07-10-browser-monitoring/)
+ * [데이터베이스에 대한 심층 쿼리 분석이 이제 일반적으로 사용 가능합니다.](/whats-new/2025/07/whats-new-07-24-db-query-performance-monitoring/)
+ * [NRQL 프리딕션 및 예측 경보가 이제 일반적으로 사용 가능합니다.](/whats-new/2025/07/whats-new-7-22-predictive-analytics/)
+ * [APM + OpenTelemetry Convergence GA](/whats-new/2025/07/whats-new-07-21-apm-otel/)
+ * [GitHub Copilot 및 ServiceNow용 Agentic 통합이 이제 일반적으로 사용 가능합니다.](/whats-new/2025/07/whats-new-7-15-agentic-ai-integrations/)
+
+* 최신 릴리스에 대한 최신 정보를 받아보세요.
+
+ * [노드 API 런타임 v1.2.119](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.119/)
+ * 취약점 문제가 해결되었습니다.
+
+ * [Ping 런타임 v1.51.0](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.119/)
+
+ * ping 런타임에 대한 logback-core 취약점이 수정되었습니다.
+ * ping 런타임에 대한 jetty-server 취약점이 수정되었습니다.
+ * ping 런타임에 대한 Ubuntu 취약점이 수정되었습니다.
+
+ * [브라우저 에이전트 v1.292.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.292.0/)
+
+ * `BrowserInteraction` 및 `previousUrl` 정의를 업데이트합니다.
+ * 추가 검사 이벤트를 추가했습니다.
+ * `finished` API `timeSinceLoad` 값이 고정되었습니다.
+
+ * [Kubernetes 통합 v3.42.1](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-42-1/)
+ * 향후 플랫폼 호환성을 위해 백앤드 및 CI 관련 내부 조정을 수정했습니다.
+
+ * [작업 관리자 v444](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-444/)
+ * 일부 모니터에서 실행 시간이 길어서 일부 고객이 결과를 볼 수 없었던 문제를 해결했습니다.
+
+ * [파이썬 에이전트 v10.14.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-101400/)
+
+ * `Azure Function Apps` 에 대한 지원이 추가되었습니다.
+ * `protobuf v6` 지원을 활성화하기 위해 `pb2` 파일을 수정했습니다.
+
+ * [안드로이드 에이전트 v7.6.7](/docs/release-notes/mobile-release-notes/android-release-notes/android-767/)
+
+ * 로그를 보고할 때 ANR을 해결하는 성능이 향상되었습니다.
+ * 애플리케이션을 종료한 후에도 로그 보고를 계속하도록 문제를 해결했습니다.
+ * 애플리케이션 상태 모니터링 및 데이터 전송과 관련된 문제가 해결되었습니다.
+ * strictmode를 켜면 몇 가지 위반 사항이 개선되었습니다.
+
+ * [Kubernetes 통합 v3.42.2](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-42-2/)
+
+ * `golang.org/x/crypto` `v0.39.0` 로 업데이트했습니다.
+ * `go` `v1.24.4` 로 업데이트했습니다.
+
+ * [.NET 에이전트 v10.42.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-42-0/)
+
+ * Azure Service Bus에 대한 지원이 추가되었습니다.
+ * 최신 VS에서 발생한 프로필러 빌드 오류를 수정했습니다.
+
+ * [PHP 에이전트 v11.10.0.24](/docs/release-notes/agent-release-notes/php-release-notes/php-agent-11-10-0-24/)
+
+ * PHP 애플리케이션에서 사용하는 패키지를 감지하기 위해 기본적으로 사용되는 Composer 런타임 API를 추가했습니다.
+ * Composer 런타임 API에서 정의되지 않은 동작이 수정되었습니다.
+
+ * [노드 브라우저 런타임 v3.0.32](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.32/)
+ * 크롬 131에 대한 크롬 빌더 옵션이 업데이트되었습니다.
+
+ * [iOS v6.9.8용 모바일 앱](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6098/)
+ * 더욱 견고하고 안정적인 소켓 연결로 Ask AI 기능을 향상시켜 원활한 경험을 보장합니다.
+
+ * [Android v5.29.7용 모바일 앱](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5297/)
+ * 더욱 견고하고 안정적인 소켓 연결로 Ask AI 기능을 향상시켜 원활한 경험을 보장합니다.
+
+ * [Node.js 에이전트 v12.22.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-22-0/)
+
+ * `openai` v5 스트리밍 지원이 추가되었습니다.
+ * `openai.responses.create` API에 대한 지원이 추가되었습니다.
+ * 정의되지 않은 tracestate 헤더에 대한 오류 로깅이 수정되었습니다.
+
+ * [인프라 에이전트 v1.65.0](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1650/)
+
+ * 의존성/종속성 `newrelic/nri-winservices` 을(를) 다음으로 업데이트했습니다. `v1.2.0`
+ * 알파인 도커 태그가 업데이트되었습니다. `v3.22`
+
+ * [인프라 에이전트 v1.65.1](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1651/)
+ * 의존성/종속성 `newrelic/nri-flex` 을(를) 다음으로 업데이트하세요. `v1.16.6`
+
+ * [브라우저 에이전트 v1.292.1](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.292.1/)
+ * 사용자 정의 속성 경쟁 조건 우선 순위를 수정했습니다.
+
+ * [NRDOT v1.2.0](/docs/release-notes/nrdot-release-notes/nrdot-2025-06-26/)
+ * OTEL 베타 코어를 범프했습니다. `v0.128.0`
+
+ * [HTML5.JS v3.0.0용 미디어 에이전트](/docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-25-04-15/)
+
+ * 새로운 이벤트 유형을 도입했습니다.
+ * `PageAction` 이벤트 유형이 더 이상 사용되지 않습니다.
+
+ * [HTML5.JS v3.1.1용 미디어 에이전트](/docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-25-06-15/)
+
+ * 패키지에 대한 npm 게시를 활성화하여 쉬운 접근성과 배포를 보장했습니다.
+ * CommonJS, ES 모듈 및 UMD 모듈 형식과의 호환성을 보장하기 위해 `dist` 폴더에 `cjs`, `esm` 및 `umd` 빌드를 추가했습니다.
+
+ * [Roku v4.0.0용 미디어 에이전트](/docs/release-notes/streaming-others-release-notes/streaming-others-agent-25-02-25/)
+
+ * 새로운 이벤트 유형을 도입했습니다.
+ * `RokuVideo` 이벤트 유형이 더 이상 사용되지 않습니다.
+ * `RokuSystem` 이벤트 유형이 더 이상 사용되지 않습니다.
+
+ * [Roku v4.0.1용 미디어 에이전트](/docs/release-notes/streaming-others-release-notes/streaming-others-agent-25-04-22/)
+ * `errorName` 더 이상 사용되지 않으므로 `errorName` 의 이름이 `errorMessage` 로 변경되었습니다.
+
+ * [작업 관리자 v447](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-447/)
+ * `ubuntu 22.04` 에서 고정 기본 이미지 업그레이드 `ubuntu 24.4`
+
+ * [핑 런타임 v1.52.0](/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.52.0/)
+ * `ubuntu 22.04` 에서 기본 이미지 업그레이드가 개선되었습니다. `ubuntu 24.04`
+
+ * [Kubernetes 통합 v3.43.0](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-43-0/)
+ * 쿠버네티스 클러스터에 Windows 노드 모니터링 지원이 추가되었습니다.
+
+ * [Android v5.29.8용 모바일 앱](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5298/)
+ * 버그를 수정하고 UI를 개선하여 더욱 원활한 경험을 제공했습니다.
+
+ * [Node.js 에이전트 v12.23.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-23-0/)
+
+ * 진입 및 종료 기간에 대해서만 보고하는 기능이 추가되었습니다.
+ * Node.js 24 지원이 추가되었습니다.
+ * 호환성 보고서가 업데이트되었습니다.
+
+ * [노드 API 런타임 v1.2.120](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.120/)
+ * 취약점을 수정했습니다. `CVE-2024-39249`
+
+ * [iOS v6.9.9용 모바일 앱](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6099/)
+ * 동적 프롬프트를 통해 AI 질문 기능을 향상시켰습니다.
+
+ * [브라우저 에이전트 v1.293.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.293.0/)
+
+ * **긴 작업** 내부 메시지를 추가했습니다.
+ * 내보내기 트레이스가 비활성화되지 않도록 하는 문제를 해결했습니다.
+
+ * [노드 브라우저 런타임 v3.0.35](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.35/)
+ * 업그레이드된 기본 이미지
+
+ * [자바 에이전트 v8.22.0](/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8220/)
+
+ * Azure App Services에 대한 연결된 메타데이터입니다.
+ * `MonoFlatMapMain` 측정, 로그를 삭제했습니다.
+
+ * [Node.js 에이전트 v12.24.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-24-0/)
+
+ * 구성 가능한 속성 값 크기 제한을 구현했습니다.
+ * 호환성 보고서가 업데이트되었습니다.
+
+ * [Kubernetes 통합 v3.43.2](docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-43-2/)
+ * kube-state-Metric 차트 버전을 `5.12.1` 에서 업데이트합니다. `5.30.1`
+
+ * [iOS 에이전트 v7.5.7](/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-757/)
+ * 세션 시작 시 분산 추적에 필요한 모든 계정 정보가 포함되지 않는 문제를 해결했습니다.
+
+ * [Android v5.29.9용 모바일 앱](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5299/)
+ * 동적 UI 렌더링으로 피드백을 향상시켰습니다.
+
+ * [Android v5.30.0용 모바일 앱](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-53000/)
+ * 버그를 수정하고 Teams GA 플래그를 업데이트하여 사용자 경험을 개선했습니다.
+
+ * [Go 에이전트 v3.40.1](/docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-40-1/)
+
+ * 교착 상태 버그로 인해 활용도가 되돌려졌습니다. v3.39.0 릴리스로 돌아갑니다.
+ * go 모듈에 직접 의존성/종속성을 추가한 awssupport\_test.go 테스트를 제거했습니다.
+
+ * [플러터 에이전트 v1.1.12](/docs/release-notes/mobile-release-notes/flutter-release-notes/flutter-agent-1112/)
+
+ * 네이티브 안드로이드 에이전트가 7.6.7 버전으로 업데이트되었습니다.
+ * 네이티브 iOS 에이전트가 7.5.6 버전으로 업데이트되어 개선되었습니다.
+
+ * [Node.js 에이전트 v13.0.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-0-0/)
+
+ * Node.js 18에 대한 지원이 중단되었습니다.
+ * `fastify` 에 대한 최소 지원 버전을 3.0.0으로 업데이트했습니다. `pino` 에서 8.0.0으로, `koa-router` 에서 12.0.0으로
+
+ * [브라우저 에이전트 v1.294.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.294.0/)
+ * 고정 보고서가 비어 있는 previousUrl을 정의되지 않은 것으로 표시했습니다.
+
+ * [인프라 에이전트 v1.65.4](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1654/)
+ * 의존성/종속성 `newrelic/nri-prometheus` 을 v2.26.2로 업데이트했습니다.
+
+ * [iOS v6.9.10용 모바일 앱](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6100/)
+ * 동적 UI 렌더링으로 피드백을 향상시켰습니다.
+
+ * [안드로이드 NDK 에이전트 v1.1.3](/docs/release-notes/mobile-release-notes/android-release-notes/android-ndk-113/)
+ * 16KB 페이지 크기에 대한 지원이 추가되었습니다.
+
+ * [인프라 에이전트 v1.65.3](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1653/)
+
+ * Windows 프로세스 핸들이 변경되었습니다.
+ * `nri-docker` `v2.5.1` 로, `nri-prometheus` 로 올렸습니다. `v2.26.1`
+
+ * [.NET 에이전트 v10.43.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-43-0/)
+ * Azure Service Bus에 대한 항목 지원이 추가되었습니다.
+
+ * [Node.js 에이전트 v12.25.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-25-0/)
+ * 수정된 리소스입니다. AWS Bedrock Converse API
+
+ * [Node.js 에이전트 v12.24.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-24-0/)
+
+ * 구성 가능한 속성 값 크기 제한을 구현했습니다.
+ * 업데이트된 호환성 보고서
+
+ * [진단 CLI(nrdiag) v3.4.0](/docs/release-notes/diagnostics-release-notes/diagnostics-cli-release-notes/diagnostics-cli-340/)
+ * `/lib64/libc.so.6: version 'GLIBC_2.34'` 찾을 수 없음과 같은 GLIBC 관련 오류가 해결되었습니다.
\ 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/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.298.mdx b/src/i18n/content/kr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.298.mdx
new file mode 100644
index 00000000000..9461f6b5431
--- /dev/null
+++ b/src/i18n/content/kr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.298.mdx
@@ -0,0 +1,34 @@
+---
+subject: Browser agent
+releaseDate: '2025-09-19'
+version: 1.298.0
+downloadLink: 'https://www.npmjs.com/package/@newrelic/browser-agent'
+features:
+ - Factor long tasks into soft nav base interaction span
+bugs:
+ - Force LCP to report the original page URL
+security: []
+translationType: machine
+---
+
+## v1.298.0
+
+### 특징
+
+#### 긴 작업을 소프트 네비게이션 기반의 블록 복합 스팬으로 통합
+
+`BrowserInteraction` 소프트 네비게이션("SPA 2.0")에서는 DOM 수정 시간을 넘어 5초 동안 긴 작업이 관찰되지 않는 지점까지 지속 시간이 확장됩니다. `JavascriptError` 및 `AjaxRequest` 원래 휴리스틱이 끝난 이후 이 확장된 기간 동안 아직 그러한 전략과 연관되지 않았습니다.
+
+### 버그 수정
+
+#### LCP가 원래 페이지 URL을 보고하도록 강제합니다.
+
+LCP가 수확 URL과 별도로 pageUrl을 보고하도록 허용합니다. LCP 수집 전에 발생하는 소프트 탐색에서 LCP에 연결된 원래 페이지 URL 대신 현재 페이지 URL이 보고되는 문제가 관찰되었습니다. 이 변경을 통해 LCP 수확 노드는 현재 페이지 URL에 관계없이 원래 URL을 보고할 수 있습니다. 변경 사항은 `pageUrl` 및 `targetGroupedUrl` 속성 모두에 적용되어야 합니다.
+
+## 지지 성명
+
+뉴렐릭은 에이전트를 정기적으로 업그레이드하여 최신 기능과 성능 이점을 얻을 것을 권장합니다. 이전 릴리스는 지원 [종료](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.298.0은 다음 브라우저 및 버전 범위에 맞춰 빌드되고 테스트되었습니다: Chrome 130-140, Edge 130-140, Safari 17-19, Firefox 132-142. 모바일 장치의 경우 v1.298.0이 Android OS 16 및 iOS Safari 17-26용으로 구축 및 테스트되었습니다.
\ No newline at end of file
diff --git a/src/i18n/content/kr/docs/release-notes/nrdot-release-notes/nrdot-2025-09-18.mdx b/src/i18n/content/kr/docs/release-notes/nrdot-release-notes/nrdot-2025-09-18.mdx
new file mode 100644
index 00000000000..99a90681c73
--- /dev/null
+++ b/src/i18n/content/kr/docs/release-notes/nrdot-release-notes/nrdot-2025-09-18.mdx
@@ -0,0 +1,16 @@
+---
+subject: NRDOT
+releaseDate: '2025-09-18'
+version: 1.4.0
+metaDescription: Release notes for NRDOT Collector version 1.4.0
+translationType: machine
+---
+
+## 변경 로그
+
+### 특징
+
+* feat: nrdot-수집기에 spanprocessor 추가 (#371)
+* 기능: 호텔 구성 요소 버전을 v0.131.0에서 v0.132.0으로 상향 조정(#368)
+* feat: 내부 텔레메트리 구성에 newrelic.service.type 추가 (#380)
+* 기능: ec2에 대한 호스트 이름 감지 활성화(#382)
\ No newline at end of file
diff --git a/src/i18n/content/kr/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-467.mdx b/src/i18n/content/kr/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-467.mdx
new file mode 100644
index 00000000000..4deafbedd7b
--- /dev/null
+++ b/src/i18n/content/kr/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-467.mdx
@@ -0,0 +1,10 @@
+---
+subject: Job Manager
+releaseDate: '2025-09-22'
+version: '467'
+translationType: machine
+---
+
+### 수정 사항
+
+* sjm의 보안 취약점을 해결하기 위해 CVE-2025-58056, CVE-2025-58057 및 기본 Ubuntu 취약점을 수정했습니다.
\ 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/apis/nerdgraph/examples/nerdgraph-issues-api-via-github.mdx b/src/i18n/content/pt/docs/apis/nerdgraph/examples/nerdgraph-issues-api-via-github.mdx
index c31aeeec378..14d3e4442ea 100644
--- a/src/i18n/content/pt/docs/apis/nerdgraph/examples/nerdgraph-issues-api-via-github.mdx
+++ b/src/i18n/content/pt/docs/apis/nerdgraph/examples/nerdgraph-issues-api-via-github.mdx
@@ -663,7 +663,7 @@ A consulta `issues` permite paginar todos os seus problemas por conta. Também p
```graphql
{
- currentUser {
+ actor {
account(id: ACCOUNT_ID) {
aiIssues {
issues {
@@ -685,7 +685,7 @@ A consulta `issues` permite paginar todos os seus problemas por conta. Também p
```json
{
"data": {
- "currentUser": {
+ "actor": {
"account": {
"aiIssues": {
"issues": {
@@ -724,7 +724,7 @@ A consulta `issues` permite paginar todos os seus problemas por conta. Também p
```graphql
{
- currentUser {
+ actor {
account(id: YOUR_ACCOUNT_ID) {
aiIssues {
issues(cursor: "") {
@@ -747,7 +747,7 @@ A consulta `issues` permite paginar todos os seus problemas por conta. Também p
```json
{
"data": {
- "currentUser": {
+ "actor": {
"account": {
"aiIssues": {
"issues": {
@@ -791,7 +791,7 @@ A consulta `issues` permite paginar todos os seus problemas por conta. Também p
```graphql
{
- currentUser {
+ actor {
account(id: YOUR_ACCOUNT_ID) {
aiIssues {
issues(cursor: "=ATN") {
@@ -840,7 +840,7 @@ A consulta `issues` permite paginar todos os seus problemas por conta. Também p
```graphql
{
- currentUser {
+ actor {
account(id: YOUR_ACCOUNT_ID) {
aiIssues {
issues(filter: {priority: "CRITICAL", states: CLOSED}) {
@@ -863,7 +863,7 @@ A consulta `issues` permite paginar todos os seus problemas por conta. Também p
```json
{
"data": {
- "currentUser": {
+ "actor": {
"account": {
"aiIssues": {
"issues": {
@@ -1066,7 +1066,7 @@ A consulta `issuesEvents` permite paginar todos os seus problemas por conta. Tam
```graphql
{
- currentUser {
+ actor {
account(id: YOUR_ACCOUNT_ID) {
aiIssues {
issuesEvents {
@@ -1089,7 +1089,7 @@ A consulta `issuesEvents` permite paginar todos os seus problemas por conta. Tam
```json
{
"data": {
- "currentUser": {
+ "actor": {
"account": {
"aiIssues": {
"issuesEvents": {
@@ -1160,7 +1160,7 @@ A consulta `issuesEvents` permite paginar todos os seus problemas por conta. Tam
```graphql
{
- currentUser {
+ actor {
account(id: YOUR_ACCOUNT_ID) {
aiIssues {
issuesEvents(filter: {ids: "fe0d512f-36c7-4b7a-8a80-4c47c040807a"}) {
@@ -1186,7 +1186,7 @@ A consulta `issuesEvents` permite paginar todos os seus problemas por conta. Tam
```json
{
"data": {
- "currentUser": {
+ "actor": {
"account": {
"aiIssues": {
"issuesEvents": {
@@ -1264,7 +1264,7 @@ Os seguintes tipos de incidente são suportados:
```graphql
{
- currentUser {
+ actor {
account(id: YOUR_ACCOUNT_ID) {
aiIssues {
incidents {
@@ -1293,7 +1293,7 @@ Os seguintes tipos de incidente são suportados:
```json
{
"data": {
- "currentUser": {
+ "actor": {
"account": {
"aiIssues": {
"incidents": {
@@ -1404,7 +1404,7 @@ Os seguintes tipos de incidente são suportados:
```graphql
{
- currentUser {
+ actor {
account(id: YOUR_ACCOUNT_ID) {
aiIssues {
incidents(filter: {priority: "CRITICAL", states: CREATED}) {
@@ -1434,7 +1434,7 @@ Os seguintes tipos de incidente são suportados:
```json
{
"data": {
- "currentUser": {
+ "actor": {
"account": {
"aiIssues": {
"incidents": {
@@ -1502,7 +1502,7 @@ Os seguintes tipos de incidente são suportados:
```graphql
{
- currentUser {
+ actor {
account(id: YOUR_ACCOUNT_ID) {
aiIssues {
incidents(filter: {ids: "97373770-caad-46cd-a69d-a358de3be090"}) {
@@ -1532,7 +1532,7 @@ Os seguintes tipos de incidente são suportados:
```json
{
"data": {
- "currentUser": {
+ "actor": {
"account": {
"aiIssues": {
"incidents": {
@@ -1573,7 +1573,7 @@ A consulta `incidentsEvents` permite paginar todos os seus eventos de incidente
```graphql
{
- currentUser {
+ actor {
account(id: YOUR_ACCOUNT_ID) {
aiIssues {
incidentsEvents {
@@ -1597,7 +1597,7 @@ A consulta `incidentsEvents` permite paginar todos os seus eventos de incidente
```json
{
"data": {
- "currentUser": {
+ "actor": {
"account": {
"aiIssues": {
"incidentsEvents": {
@@ -1664,7 +1664,7 @@ A consulta `incidentsEvents` permite paginar todos os seus eventos de incidente
```graphql
{
- currentUser {
+ actor {
account(id: YOUR_ACCOUNT_ID) {
aiIssues {
incidentsEvents(filter: {ids: "cd512082-6ebe-46ac-a6dc-d387dc86dc80"}) {
@@ -1694,7 +1694,7 @@ A consulta `incidentsEvents` permite paginar todos os seus eventos de incidente
```json
{
"data": {
- "currentUser": {
+ "actor": {
"account": {
"aiIssues": {
"incidentsEvents": {
@@ -1749,7 +1749,7 @@ Para obter o parâmetro de configuração atual para seu ambiente, você pode ex
```graphql
{
- currentUser {
+ actor {
account(id: YOUR_ACCOUNT_ID) {
aiIssues {
configByEnvironment {
@@ -1772,7 +1772,7 @@ Para obter o parâmetro de configuração atual para seu ambiente, você pode ex
```json
{
"data": {
- "currentUser": {
+ "actor": {
"account": {
"aiIssues": {
"configByEnvironment": {
@@ -1963,7 +1963,7 @@ Para executar a consulta na linha de comando:
```graphql
{
- currentUser {
+ actor {
account(id: YOUR_ACCOUNT_ID) {
aiIssues {
issues {
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/browser/browser-monitoring/browser-pro-features/session-replay/additional-information.mdx b/src/i18n/content/pt/docs/browser/browser-monitoring/browser-pro-features/session-replay/additional-information.mdx
index 08650d9f317..ed550fd09da 100644
--- a/src/i18n/content/pt/docs/browser/browser-monitoring/browser-pro-features/session-replay/additional-information.mdx
+++ b/src/i18n/content/pt/docs/browser/browser-monitoring/browser-pro-features/session-replay/additional-information.mdx
@@ -45,7 +45,7 @@ O Session Replay minimiza o impacto no desempenho do aplicativo com:
* Coleta estratégica de carga útil: uma carga útil grande (compactada) é enviada somente quando o DOM completo é capturado, o que normalmente ocorre quando o recurso de reprodução é importado pela primeira vez. Posteriormente, apenas pequenas cargas relacionadas às ações do usuário são enviadas. O agente do browser coletará dados com base na primeira ocorrência das seguintes condições:
- * The payload reaches more than 16 kB compressed.
- * 30 seconds elapses.
+ * A carga útil atinge mais de 16 kB compactados.
+ * 30 segundos se passaram.
* A visibilidade da página muda (por exemplo, mudança de aba, foco, navegação).
* A sessão termina.
\ No newline at end of file
diff --git a/src/i18n/content/pt/docs/browser/new-relic-browser/lab/debug-slowness.mdx b/src/i18n/content/pt/docs/browser/new-relic-browser/lab/debug-slowness.mdx
index 803d12b05a7..e363f50cad2 100644
--- a/src/i18n/content/pt/docs/browser/new-relic-browser/lab/debug-slowness.mdx
+++ b/src/i18n/content/pt/docs/browser/new-relic-browser/lab/debug-slowness.mdx
@@ -5,22 +5,15 @@ freshnessValidatedDate: never
translationType: machine
---
-
- Este procedimento faz parte de um laboratório que ensina como solucionar problemas do seu aplicativo da web com o New Relic .
+
+ Este procedimento faz parte de um laboratório que ensina como solucionar problemas do seu aplicativo da web com o New Relic .
- Cada procedimento no laboratório baseia-se no anterior, portanto, certifique-se de ter concluído o último procedimento, [_Depurar erros no seu aplicativo_](/docs/browser/new-relic-browser/lab/debug-errors), antes de iniciar este.
+ Cada procedimento no laboratório baseia-se no anterior, portanto, certifique-se de ter concluído o último procedimento, [*Depurar erros no seu aplicativo*](/docs/browser/new-relic-browser/lab/debug-errors), antes de iniciar este.
Depois de corrigir erros de JavaScript em seu aplicativo, você e sua equipe se sentem confiantes. Pronto para o seu tempo de inatividade, você acessa as redes sociais, mas verifica o Twitter e vê alguns clientes confusos:
-
+
Ah, ah! Vocês, clientes, não parecem felizes. É hora de usar o monitoramento de browser New Relic para descobrir a origem do atraso.
@@ -36,29 +29,17 @@ Ah, ah! Vocês, clientes, não parecem felizes. É hora de usar o monitoramento
Na página inicial do New Relic, navegue até **Browser** e escolha seu aplicativo **Relicstaurants** .
-
+
Aqui você vê todos os dados relacionados ao seu aplicativo de browser, incluindo **Page views with JavaScript errors**, **Core web vitals**, **User time on the site**, **Initial page load and route changes** e outros.
-
+
Observe o **largest contentful paint (LCP)**.
-
+
A pintura de maior conteúdo (LCP) representa a rapidez com que o conteúdo principal de uma página da web é carregado. Idealmente, o conteúdo não deve demorar mais do que um ou dois segundos para carregar. Aqui você vê que seu site carrega em mais de 5 segundos. Não é à toa que seu usuário está reclamando!
@@ -68,29 +49,17 @@ Ah, ah! Vocês, clientes, não parecem felizes. É hora de usar o monitoramento
Role para baixo e observe o gráfico **Front end vs. back end** .
-
+
Clique em **Back end (time to first byte) (50%)** para filtrar o gráfico e ver quanto tempo backend leva para carregar.
-
+
- O gráfico indica que o back-end levou no máximo 140 mili segundos para processar a solicitação na pior das hipóteses. Isso significa que seu frontend está causando atraso?
+ O gráfico indica que o back-end levou no máximo 140 milissegundos para processar a solicitação no pior caso. Isso significa que seu frontend está causando atraso?
Clique em **Front end (Window load + AJAX) (50%)**.
-
+
Aí está o problema! O gráfico indica que o atraso está acontecendo no frontend.
@@ -98,21 +67,13 @@ Ah, ah! Vocês, clientes, não parecem felizes. É hora de usar o monitoramento
Para restringir o que pode estar causando o atraso no front-end, observe mais de perto o gráfico **Initial page load and route change** .
-
+
Clique em **Initial page load (Window load + AJAX)**.
-
+
O gráfico indica que **Initial page load (Window load + AJAX)** está demorando de 5 a 6 segundos, o que é alarmante.
@@ -120,53 +81,29 @@ Ah, ah! Vocês, clientes, não parecem felizes. É hora de usar o monitoramento
Clique em **Initial page load and route change** para ver mais detalhes.
-
+
Isso leva você para **Page views**.
-
+
Classifique as páginas por **Most time-consuming**.
-
+
Observe que a página inicial está demorando quase 90% para carregar.
-
+
Clique nele para ver seus detalhes.
-
+
Esta página mostra **Page view breakdown**, **Median initial page load time** e outros detalhes importantes. O gráfico **Page view breakdown** é especialmente importante aqui, pois ajuda a definir por que e onde sua página está demorando mais. Ao examinar este gráfico mais de perto, você verá que **Page rendering** está demorando até 5.000 milissegundos.
-
+
Agora você sabe que a página inicial está demorando muito para ser renderizada, tornando seu aplicativo lento. A seguir, observamos **Session traces** para descobrir o que está retardando o processo de renderização.
@@ -176,31 +113,19 @@ Ah, ah! Vocês, clientes, não parecem felizes. É hora de usar o monitoramento
Na navegação à esquerda, navegue até **Session traces** e classifique-os na ordem decrescente de **Page load**.
-
+
Aqui você vê o trace da sessão classificado na ordem do tempo **Page load** .
-
+
Na lista, clique no primeiro.
-
+
@@ -208,51 +133,31 @@ Ah, ah! Vocês, clientes, não parecem felizes. É hora de usar o monitoramento
Aqui você vê o trace completo daquela sessão específica. Esta página também mostra **Backend**, **Dom Processing**, **Page Load** e outras informações relacionadas trace .
-
+
Observe que **Page load** está demorando mais que o esperado. Você precisa de um cronograma detalhado da carga. Role o ponteiro para a esquerda e para a direita para ajustar a linha do tempo.
-
+
Percorra o trace para percorrer a janela de tempo e ver os detalhes do evento individual durante esta sessão.
-
+
Observe que um evento específico está demorando mais de 5 segundos.
-
+
Clique no evento para ver seus detalhes.
-
+
Observe que é uma imagem. Particularmente, é a imagem de fundo do seu aplicativo que leva de 5 a 6 segundos para carregar e causa atraso.
@@ -272,4 +177,4 @@ Recapitulando, você observou lentidão em sua aplicação e utilizou o monitora
Bom trabalho! Agora que você já começou com nosso monitoramento, aqui estão alguns documentos que ajudarão você a dar os próximos passos em sua jornada.
* [Introdução ao monitoramento de browser](/docs/browser/browser-monitoring/getting-started/introduction-browser-monitoring/)
-* [Monitoramento de recurso do browser](/docs/browser/new-relic-browser/browser-pro-features/intro-to-browser-pro-features)
+* [Monitoramento de recurso do browser](/docs/browser/new-relic-browser/browser-pro-features/intro-to-browser-pro-features)
\ No newline at end of file
diff --git a/src/i18n/content/pt/docs/browser/new-relic-browser/page-load-timing-resources/instrumentation-browser-monitoring.mdx b/src/i18n/content/pt/docs/browser/new-relic-browser/page-load-timing-resources/instrumentation-browser-monitoring.mdx
index e21b3067495..a5223f8d6b1 100644
--- a/src/i18n/content/pt/docs/browser/new-relic-browser/page-load-timing-resources/instrumentation-browser-monitoring.mdx
+++ b/src/i18n/content/pt/docs/browser/new-relic-browser/page-load-timing-resources/instrumentation-browser-monitoring.mdx
@@ -156,11 +156,11 @@ Para ambas as páginas https **and** http, transmitimos dados via htt
|
- All other browser event data
+ Todos os outros dados de eventos do browser
|
- See [Browser agent harvests](/docs/browser/new-relic-browser/performance-quality/browser-monitoring-performance-impact#agent-harvests)
+ Veja [as colheitas do agente do Browser](/docs/browser/new-relic-browser/performance-quality/browser-monitoring-performance-impact#agent-harvests)
|
diff --git a/src/i18n/content/pt/docs/browser/new-relic-browser/performance-quality/browser-monitoring-performance-impact.mdx b/src/i18n/content/pt/docs/browser/new-relic-browser/performance-quality/browser-monitoring-performance-impact.mdx
index f70e7e19b40..da0d1683888 100644
--- a/src/i18n/content/pt/docs/browser/new-relic-browser/performance-quality/browser-monitoring-performance-impact.mdx
+++ b/src/i18n/content/pt/docs/browser/new-relic-browser/performance-quality/browser-monitoring-performance-impact.mdx
@@ -96,7 +96,7 @@ O agente consiste em múltiplos scripts para reduzir o tamanho inicial do "
### Colheitas do agente browser [#agent-harvests]
-Browser events are first harvested after the PageView event is successfully collected, and then every 30 seconds thereafter. If any event type exceeds 16 kB of data before the next scheduled harvest, an early harvest is triggered for that event. Additionally, a final harvest occurs whenever the document transitions to `hidden` via a `visibilitychange` event (e.g. when a user navigates away, switches tabs, closes the tab, minimizes or closes the browser, or switches from the browser to another app if they're on a mobile device).
+Os eventos Browser são coletados primeiro após o evento PageView ser coletado com sucesso e, depois, a cada 30 segundos. Se qualquer tipo de evento exceder 16 kB de dados antes da próxima coleta programada, uma coleta antecipada será acionada para esse evento. Além disso, uma colheita final ocorre sempre que o documento faz a transição para `hidden` por meio de um evento `visibilitychange` (por exemplo, quando um usuário sai, alterna entre guias, fecha a guia, minimiza ou fecha o navegador ou alterna do navegador para outro aplicativo se estiver em um dispositivo móvel).
@@ -164,7 +164,7 @@ Browser events are first harvested after the PageView event is successfully coll
|
- `PageViewTiming` events are harvested by all agents and includes timing data like core web vitals measurements. See the [PageViewTiming docs](/docs/browser/new-relic-browser/page-load-timing-resources/pageviewtiming-async-or-dynamic-page-details/#interactivity-metrics) for a list of reported events.
+ `PageViewTiming` Os eventos são coletados por todos os agentes e incluem dados de tempo, como medições core web vitals. Consulte a [documentação do PageViewTiming](/docs/browser/new-relic-browser/page-load-timing-resources/pageviewtiming-async-or-dynamic-page-details/#interactivity-metrics) para obter uma lista de eventos relatados.
|
@@ -186,7 +186,7 @@ Browser events are first harvested after the PageView event is successfully coll
- `JavaScriptError` metrics are sent together with Ajax metrics as timeslice data.
+ `JavaScriptError` métrica são enviadas junto com a métrica Ajax como dados da fração de tempo.
|
@@ -230,7 +230,7 @@ Browser events are first harvested after the PageView event is successfully coll
- `AjaxRequest` events follows the 30 seconds harvest cycle unless the `SPA` agent is in use. If using the `SPA` agent, the first harvest will happen after the `load` page lifecycle event and additional harvests will either happen every 30 seconds or when the `SPA` agent notices a route change.
+ `AjaxRequest` o evento segue o ciclo de coleta de 30 segundos, a menos que o agente `SPA` esteja em uso. Se estiver usando o agente `SPA`, a primeira coleta ocorrerá após o evento do ciclo de vida da página `load` e coletas adicionais ocorrerão a cada 30 segundos ou quando o agente `SPA` perceber uma alteração de rota.,
|
@@ -252,7 +252,7 @@ Browser events are first harvested after the PageView event is successfully coll
- Session traces can generate a large amount of data, but that can be controlled by sampling. By default, only about 90 page views per hour will be sampled to send session trace data. There is also an option to set a custom sampling rate.
+ O rastreamento da sessão pode gerar uma grande quantidade de dados, mas isso pode ser controlado por amostragem. Por padrão, apenas cerca de 90 visualizações de página por hora serão amostradas para enviar dados trace da sessão. Também há uma opção para definir uma taxa de amostragem personalizada.
|
@@ -274,7 +274,7 @@ Browser events are first harvested after the PageView event is successfully coll
- In addition to the the general harvest cycles, session replay harvests that include snapshots and metadata payloads will be harvested immediately.
+ Além do ciclo geral de coleta, as coletas do Session Replay que incluem snapshots e carga de metadados serão coletadas imediatamente.
O endpoint pode diferir dependendo da localidade, mas um exemplo para os EUA seria `https://bam.nr-data.net/browser/blobs`.
|
@@ -318,13 +318,13 @@ Browser events are first harvested after the PageView event is successfully coll
- `BrowserInteraction` events are harvested immediately after the interaction finishes. There will always be at least one interaction that represents the initial page load. Additional interactions are collected only if the URL changes (representing route change). `AjaxRequest` events are also harvested at the same time if they occur during an interaction.
+ `BrowserInteraction` evento são colhidos imediatamente após o término da interação. Sempre haverá pelo menos uma interação que representa o carregamento inicial da página. Interações adicionais são coletadas somente se a URL mudar (representando mudança de rota). `AjaxRequest` evento também são coletados ao mesmo tempo se ocorrerem durante uma interação.
|
|
- Browser logs
+ Logs do navegador
|
@@ -344,7 +344,7 @@ Browser events are first harvested after the PageView event is successfully coll
|
|
- [UserAction](/attribute-dictionary/?event=UserAction) events
+ Evento [UserAction](/attribute-dictionary/?event=UserAction)
|
@@ -364,7 +364,7 @@ Browser events are first harvested after the PageView event is successfully coll
|
|
- [BrowserPerformance](/attribute-dictionary/?event=BrowserPerformance) events
+ Eventos [BrowserPerformance](/attribute-dictionary/?event=BrowserPerformance)
|
diff --git a/src/i18n/content/pt/docs/cci/configure-cci/general-setting.mdx b/src/i18n/content/pt/docs/cci/configure-cci/general-setting.mdx
index 51b145e5e15..b532be6ba3f 100644
--- a/src/i18n/content/pt/docs/cci/configure-cci/general-setting.mdx
+++ b/src/i18n/content/pt/docs/cci/configure-cci/general-setting.mdx
@@ -43,10 +43,10 @@ A Inteligência de Custos na Nuvem suporta tag personalizada junto com tag padr
1. Para solicitar informações sobre as contas das quais você deseja extrair dados de telemetria para análise de custos, selecione a aba **Telemetry Data** .
2. Para visualizar e gerenciar dados de telemetria para sua análise de custos, na lista **Select accounts for telemetry data** , escolha uma ou mais contas.
-
- * A estimativa de custos em tempo real é suportada por dados de telemetria.
- * A alocação de K8s é suportada por dados de telemetria.
- * Reutilizamos o pipeline de telemetria existente para obter a métrica de utilização, e nenhum dado novo é ingerido, exceto a ingestão do arquivo CUR.
-
+
+ * A estimativa de custos em tempo real é suportada por dados de telemetria.
+ * A alocação de K8s é suportada por dados de telemetria.
+ * Reutilizamos o pipeline de telemetria existente para obter a métrica de utilização, e nenhum dado novo é ingerido, exceto a ingestão do arquivo CUR.
+
\ No newline at end of file
diff --git a/src/i18n/content/pt/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/manual.mdx b/src/i18n/content/pt/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/manual.mdx
new file mode 100644
index 00000000000..15e0cfefd5b
--- /dev/null
+++ b/src/i18n/content/pt/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/manual.mdx
@@ -0,0 +1,72 @@
+---
+title: Integrar manualmente a partir do console da AWS
+tags:
+ - Integrate manually
+ - Manual integration
+ - AWS metric integration
+ - Amazon integrations
+ - AWS integrations
+metaDescription: Integrate New Relic with AWS services manually from the AWS console.
+freshnessValidatedDate: never
+translationType: machine
+---
+
+Para uma integração perfeita da sua conta AWS com New Relic, [a integração via CloudFormation e CloudWatch Metric Streams](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation) é a abordagem mais recomendada. Se você não puder usar modelos do CloudFormation e não preferir usar o Terraform, consulte o procedimento a seguir para integrar manualmente a partir do console da AWS.
+
+## 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 do New Relic Ingest e uma chave de usuário](https://one.newrelic.com/api-keys)**: você precisará dessas chaves 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 ao New Relic, 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**: Manually integrate your AWS account
+
+5. Na tela **Select services**, se necessário, use o botão de alternância **Show resources not supported by CloudWatch Metric Streams**, selecione os serviços que deseja monitorar e continue.
+
+6. Na tela **Choose data integration type**, escolha entre as seguintes opções de integração:
+
+ * **Monitoramento AWS en tempo real (Recomendado)**: Esta opção é para os serviços que suportam CloudWatch Metric Streams.
+ * **Sondagem de API**: esta opção é adequada para serviços não suportados pelo CloudWatch Metric Streams.
+
+7. Da página **Create role** para a página **Configure budgets policy**, siga as instruções na tela e execute as etapas no console da AWS.
+
+8. Depois de criar a política no console da AWS, mude para a plataforma New Relic e continue com a integração guiada até ver seus dados da 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.
+
+
+
+ Integre os serviços da AWS com o New Relic usando o CloudFormation e o CloudWatch Metric Streams.
+
+
+
+ Integre serviços da AWS com o New Relic usando CloudFormation e API Polling.
+
+
+
+ Integre serviços da AWS com o New Relic usando o Terraform.
+
+
\ No newline at end of file
diff --git a/src/i18n/content/pt/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/migrate-from-api-polling-to-cwms.mdx b/src/i18n/content/pt/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/migrate-from-api-polling-to-cwms.mdx
new file mode 100644
index 00000000000..fc2453f514d
--- /dev/null
+++ b/src/i18n/content/pt/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/migrate-from-api-polling-to-cwms.mdx
@@ -0,0 +1,111 @@
+---
+title: Migrar do API Polling para o CloudWatch Metric Streams
+tags:
+ - API polling to CWMS migration
+metaDescription: Migrate your New Relic and AWS services integration type from API Polling to CloudWatch Metric Streams.
+freshnessValidatedDate: never
+translationType: machine
+---
+
+Para uma integração perfeita da sua conta AWS com New Relic, [a integração via CloudFormation e CloudWatch Metric Streams](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation) é a abordagem mais recomendada. No entanto, se você já integrou sua conta da AWS com o New Relic usando o API Polling, consulte o procedimento a seguir para migrar do API Polling para o 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 do New Relic Ingest e uma chave de usuário](https://one.newrelic.com/api-keys)**: você precisará dessas chaves 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.
+* Para usuários que gerenciam várias contas AWS, [conecte cada conta a uma única conta New Relic ](/docs/infrastructure/amazon-integrations/manage-aws-data/aws-multi-account).
+* Para usuários que gerenciam várias regiões dentro dessas contas, é necessário criar um Kinesis Data Firehose separado que aponte para o New Relic para cada região.
+
+
+
+ ## Migrar para a integração do CloudWatch Metric Streams [#migrate]
+
+ Você pode migrar da pesquisa de API criando um modelo do CloudFormation ou adicionando novamente sua conta da AWS e seguindo nossos procedimentos de instalação guiada no aplicativo. Recomendamos que você use o método de modelo do CloudFormation, pois é a maneira mais eficiente de migrar. Essas integrações não são suportadas pelo CloudWatch Metric Streams e não podem ser migradas para nossa integração:
+
+ * AWS CloudTrail
+ * AWS Health
+ * AWS Trusted Advisor
+ * AWS X-Ray
+
+ Se você usar essa integração, ainda precisará usar o método de pesquisa API.
+
+
+
+ O modelo CloudFormation permite que você atualize um modelo com namespace pré-configurado com base na sua configuração de pesquisa.
+
+ 1. Acesse **[one.newrelic.com > Infrastructure > AWS](https://one.newrelic.com/infra/infrastructure/cloud-aws)** e clique em **Migrate to CloudWatch Metric stream**.
+ 2. Siga os procedimentos. Você baixará o modelo e replicará o namespace da pesquisa API. Não se esqueça de adicionar os detalhes da sua conta ao modelo baixado.
+ 3. No AWS Console, acesse **Cloud Formation > Create Stack > Upload a template file**. Carregue seu modelo CloudFormation atualizado.
+
+
+
+ Se não quiser usar o método CloudFormation, você precisará adicionar novamente sua conta AWS, mesmo que já tenha vinculado sua conta AWS à integração de pesquisa. Esses procedimentos podem fazer com que você saia deste documento, mas lembre-se de retornar para desabilitar sua integração de polling.
+
+ 1. Vá para **[one.newrelic.com > All capabilities >Infrastructure > AWS](https://one.newrelic.com/infra/infrastructure/cloud-aws)** e clique em **Add AWS account**. Escolha seu método.
+ 2. Siga as etapas AWS Console do [fluxo doAWS Console ](/install/aws-cloudwatch/?task=console)neste documento.
+ 3. [Desabilite todas as integrações de pesquisa desnecessárias](/docs/infrastructure/amazon-integrations/connect/uninstall-aws/) na conta anterior do provedor AWS.
+
+ Ao desabilitar, tenha em mente que [algumas integrações não são suportadas pelo CloudWatch Metric Streams](/docs/infrastructure/amazon-integrations/connect/connect-aws-new-relic-infrastructure-monitoring/).
+
+
+
+ Nossa integração CloudWatch Metric Streams usa a API métrica para enviar métricas no formato [métrica dimensional](/docs/data-apis/understand-data/new-relic-data-types/#dimensional-metrics). Nosso método de pesquisa de API, por outro lado, envia métrica com base em [evento](/docs/data-apis/understand-data/new-relic-data-types/#events-new-relic).
+
+ * Para auxiliar na transição, fornecemos um mecanismo de shimming que permite que você escreva consultas de forma transparente em qualquer formato. Essas consultas são processadas conforme o esperado com base na fonte disponível, seja de evento para métrica ou de métrica para evento.
+ * Recomendamos revisar [algumas limitações](/docs/query-your-data/nrql-new-relic-query-language/nrql-query-tutorials/query-infrastructure-dimensional-metrics-nrql/#known-limitations) sobre o mecanismo de shimming que permite usar consultas baseadas em eventos com a integração do CloudWatch Metric Streams.
+
+ Após a migração, alguns recursos do New Relic que dependem dos dados de pesquisa da sua API podem se comportar de maneira diferente:
+
+ * **Dashboards**: o painel personalizado que usa o evento de integração AWS baseado em enquete ainda funcionará conforme o esperado.
+ * **Alerts**: condição do alerta de que usar evento AWS baseado em enquete ainda funcionará. Recomendamos adaptá-los ao formato métrico dimensional que usa NRQL como fonte.
+ * **Entities**: Sua lista de entidade monitora pode apresentar entidade duplicada por até 24 horas.
+ * **Attributes**: As integrações da AWS baseadas em pesquisa prefixam a tag de recurso coletada com `label.`, enquanto a integração do AWS CloudWatch Metric Streams prefixa a tag de recurso coletada com `tags.`. Se ambas as integrações estiverem habilitadas para a mesma conta AWS, a tag do recurso aparecerá em ambos os prefixos ao usar o formato de evento.
+
+
+
+ ## Valide se seus dados [#validate-data]
+
+ Para confirmar que você está recebendo dados dos Streams métrica, siga estes passos:
+
+ 1. Vá para **[one.newrelic.com > All capabilities > Infrastructure > AWS](https://one.newrelic.com/infra/infrastructure/cloud-aws)**. Procure a conta da AWS que você conectou ao New Relic. **Stream** contas.
+ 2. Verifique o dashboard de status da conta e confirme se New Relic recebe os dados métricos. Isso pode incluir erros e número de namespace e métrica ingeridos.
+ 3. Explore seus dados escrevendo consultas para conjuntos específicos de métricas.
+
+ Pode levar alguns minutos para que New Relic detecte novos recursos e os sintetize como entidade.
+
+
+ As métricas AWS do CloudWatch para serviços globais, como AWS Billing, estão disponíveis somente na região **us-east-1**. Certifique-se de que haja um CloudWatch Metric Streams ativo configurado nessa região.
+
+
+
+
+## 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.
+
+
+
+ Integre os serviços da AWS com o New Relic usando o CloudFormation e o CloudWatch Metric Streams.
+
+
+
+ Integre serviços da AWS com o New Relic usando CloudFormation e API Polling.
+
+
+
+ Integre serviços da AWS com o New Relic usando o Terraform.
+
+
+
+ Integre manualmente os serviços da AWS com o New Relic a partir do console da AWS.
+
+
\ No newline at end of file
diff --git a/src/i18n/content/pt/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/terraform.mdx b/src/i18n/content/pt/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/terraform.mdx
new file mode 100644
index 00000000000..0d84065598c
--- /dev/null
+++ b/src/i18n/content/pt/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/terraform.mdx
@@ -0,0 +1,65 @@
+---
+title: Integrar com o Terraform
+tags:
+ - Integrate with Terraform
+ - AWS metric integration
+ - Amazon integrations
+ - AWS integrations
+metaDescription: Integrate New Relic with AWS services using Terraform.
+freshnessValidatedDate: never
+translationType: machine
+---
+
+Para uma integração perfeita da sua conta AWS com New Relic, [a integração via CloudFormation e CloudWatch Metric Streams](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation) é a abordagem mais recomendada. Se você já gerencia suas contas e serviços AWS usando o Terraform, talvez prefira o seguinte método de integração, porque New Relic oferece um módulo de integração na nuvem AWS que simplifica a configuração da integração.
+
+## 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:
+
+* **[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.
+* O ID da conta e a região do New Relic que você deseja vincular à AWS.
+
+## Etapas de integração [#integration-steps]
+
+Para integrar sua conta da AWS ao New Relic, 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 with Terraform
+
+5. Na tela **Select services**, se necessário, use o botão de alternância **Show resources not supported by CloudWatch Metric Streams**, selecione os serviços que deseja monitorar e continue.
+
+6. Na tela **Terraform**, abra a documentação que orienta como conectar sua conta do New Relic à conta do provedor do Terraform.
+
+7. Após uma integração bem-sucedida, você poderá ver seus dados da 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.
+
+
+
+ Integre os serviços da AWS com o New Relic usando o CloudFormation e o CloudWatch Metric Streams.
+
+
+
+ Integre serviços da AWS com o New Relic usando CloudFormation e API Polling.
+
+
+
+ Integre manualmente os serviços da AWS com o New Relic a partir do console da AWS.
+
+
\ No newline at end of file
diff --git a/src/i18n/content/pt/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-and-api-polling.mdx b/src/i18n/content/pt/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-and-api-polling.mdx
new file mode 100644
index 00000000000..8f679c00d73
--- /dev/null
+++ b/src/i18n/content/pt/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-and-api-polling.mdx
@@ -0,0 +1,77 @@
+---
+title: Integrar via CloudFormation e sondagem de API
+tags:
+ - Integration via CloudFormation
+ - AWS metric integration
+ - Amazon integrations
+ - AWS integrations
+ - Integration with API polling via CloudFormation
+metaDescription: Integrate New Relic with AWS services using CloudFormation templates to automate the setup of API polling for metrics ingestion.
+freshnessValidatedDate: never
+translationType: machine
+---
+
+Para uma integração perfeita da sua conta AWS com New Relic, [a integração via CloudFormation e CloudWatch Metric Streams](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation) é a abordagem mais recomendada. Você também pode utilizar a API Polling para integração com certas limitações de recuperação de dados. Para mais detalhes, consulte a tabela de comparação em [Ingestão métricaAWS ](/docs/infrastructure/amazon-integrations/get-started/introduction-aws-integrations/#aws-metrics-ingestion). É recomendável usar a API Polling somente 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 do New Relic Ingest e uma chave de usuário](https://one.newrelic.com/api-keys)**: você precisará dessas chaves 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 API Polling, 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**: API Polling
+
+5. Na tela **Select services**, se necessário, use o botão de alternância **Show resources not supported by CloudWatch Metric Streams**, selecione os serviços que deseja monitorar e continue.
+
+6. Auto-discovery detecta e visualiza automaticamente os relacionamentos entre sua entidade 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 a chave de licença de ingestão e a chave de usuário no seu console da AWS.
+
+
+ Para obter metadados adicionais dos seus serviços da AWS, habilite **AWS Config** no console da AWS.
+
+
+10. 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 várias 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/).
+11. 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.
+
+
+
+ Integre os serviços da AWS com o New Relic usando o CloudFormation e o CloudWatch Metric Streams.
+
+
+
+ Integre serviços da AWS com o New Relic usando o Terraform.
+
+
+
+ Integre manualmente os serviços da AWS com o New Relic a partir do console da AWS.
+
+
\ No newline at end of file
diff --git a/src/i18n/content/pt/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms.mdx b/src/i18n/content/pt/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms.mdx
new file mode 100644
index 00000000000..1c468d4689b
--- /dev/null
+++ b/src/i18n/content/pt/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms.mdx
@@ -0,0 +1,86 @@
+---
+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 do New Relic Ingest e uma chave de usuário](https://one.newrelic.com/api-keys)**: você precisará dessas chaves 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.
+
+
+
+
+ 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 sua entidade 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 a chave de licença de ingestão e a chave de usuário no seu console da AWS.
+
+
+ Para obter metadados adicionais dos seus serviços da AWS, habilite **AWS Config** no console da AWS.
+
+
+10. 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 várias 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/).
+
+11. 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.
+
+
+
+ Integre serviços da AWS com o New Relic usando CloudFormation e API Polling.
+
+
+
+ Integre serviços da AWS com o New Relic usando o Terraform.
+
+
+
+ Integre manualmente os serviços da AWS com o New Relic a partir do console da AWS.
+
+
\ No newline at end of file
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.
+
+
+
+
+ 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/amazon-integrations/get-started/introduction-aws-integrations.mdx b/src/i18n/content/pt/docs/infrastructure/amazon-integrations/get-started/introduction-aws-integrations.mdx
index ea0529cdf2d..f9ee9acc521 100644
--- a/src/i18n/content/pt/docs/infrastructure/amazon-integrations/get-started/introduction-aws-integrations.mdx
+++ b/src/i18n/content/pt/docs/infrastructure/amazon-integrations/get-started/introduction-aws-integrations.mdx
@@ -181,14 +181,14 @@ Os seguintes serviços da AWS não são suportados pelo CloudWatch Metric Stream
Se você utilizar outros serviços da AWS junto com qualquer um desses, ainda poderá escolher a integração do Amazon CloudWatch Metric Streams. Durante a configuração, o New Relic oferece a opção de configurar a pesquisa de API especificamente para esses serviços não suportados.
-Following are the ways to integrate your AWS services with New Relic:
+A seguir estão as maneiras de integrar seus serviços da AWS com o New Relic:
-* [Via CloudFormation and CloudWatch metric stream](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms).
-* [Via CloudFormation and API Polling](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-and-api-polling).
+* [Por meio dos fluxos de métricas CloudFormation e CloudWatch](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms).
+* [Via CloudFormation e API Polling](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-and-api-polling).
* [Via Terraform](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/terraform).
-* [Manually from AWS console](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/manual).
+* [Manualmente a partir do console da AWS](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/manual).
-If you have already integrated your AWS account with New Relic using API Polling, refer to the [migration procedure](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/migrate-from-api-polling-to-cwms) to migrate to CloudWatch Metric Streams.
+Se você já integrou sua conta da AWS com o New Relic usando o API Polling, consulte o [procedimento de migração](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/migrate-from-api-polling-to-cwms) para migrar para o CloudWatch Metric Streams.
### Custos da AWS para integração [#aws-costs]
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
-## 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
```
-
+ /* <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}})
```
-
+ /* <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}}
```
-
+ /* <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
```
-
+ /* <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
```
-
+ /* <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
```
-
+ /* <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`
-
+ /* <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}}
```
-
+ /* <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
```
-
+ /* <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
```
-
+ /* <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:
-
+ * **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}}
```
-
+ /* <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`
-
+ /* <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
```
-
+ /* <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}})
```
-
+ /* <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.
-
+ /* <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/agent-release-notes/java-release-notes/java-agent-8240.mdx b/src/i18n/content/pt/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8240.mdx
index 13b4fd95229..2d1920426dd 100644
--- a/src/i18n/content/pt/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8240.mdx
+++ b/src/i18n/content/pt/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8240.mdx
@@ -7,8 +7,8 @@ features:
- “Support MongoDB Reactive Streams 5.2.0 and up”
- “Jedis 6 support”
bugs:
- - “CouchBase: Add skip class to prevent double instrumentation”
- - “Spring WebClient 5.x: Only wrap headers instead of the entire response”
+ - 'CouchBase: Add skip class to prevent double instrumentation'
+ - 'Spring WebClient 5.x: Only wrap headers instead of the entire response'
security: []
translationType: machine
---
diff --git a/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx b/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx
new file mode 100644
index 00000000000..85a43dedea4
--- /dev/null
+++ b/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx
@@ -0,0 +1,267 @@
+---
+subject: Docs
+releaseDate: '2025-07-25'
+version: 'June 13 - July 24, 2025'
+translationType: machine
+---
+
+### Novos documentos
+
+* Adicionado novo recurso sobre [como depurar problemas de agente New Relic Browser ](/docs/browser/new-relic-browser/troubleshooting/how-to-debug-browser-agent/), incluindo logging detalhado, monitoramento de solicitação de rede e evento de inspeção para melhor resolução de problemas em agentes versões 1.285.0 e superiores.
+* Adicionado suporte [ao Azure Functions](/docs/serverless-function-monitoring/azure-function-monitoring/introduction-azure-monitoring/) para monitoramento de funções `python` e `.node.js`.
+* [Otimizador de custos](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/compute-optimizer/) adicionado para insights acionáveis para melhorar a eficiência do computador, com recurso para identificar ineficiências, fornecer recomendações de otimização e estimar economias de CCU na plataforma New Relic.
+* Adicionada [Inteligência de Custos na Nuvem](/docs/cci/getting-started/overview), oferecendo ferramentas para visibilidade e gerenciamento de custos cloud, incluindo recursos como detalhamentos abrangentes de custos, alocação de custos Kubernetes, estimativa de custos em tempo real e coleta de dados entre contas, atualmente suportando apenas custos da Nuvem da AWS.
+* Adicionada [observabilidade OpenTelemetry para Kubernetes com integração independente de provedor de recursos New Relic](/docs/kubernetes-pixie/k8s-otel/intro/) para monitoramento contínuo do cluster por meio do gráfico Helm, aprimorando os sinais de telemetria para métricas, eventos e logs transmitidos para as ferramentas e o painel do New Relic.
+* Adicionada [limitação e resolução de problemas para integração Windows](/docs/kubernetes-pixie/kubernetes-integration/troubleshooting/troubleshooting-windows/)
+* Adicionada integração com AWS via [CloudFormation e CloudWatch Metric Streams](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms/), com suporte à API Polling para serviços não suportados.
+* Adicionada [tag aprimorada para banco de dados entidade New Relic ](/docs/infrastructure/host-integrations/db-entity-tags/)para banco de dados entidade monitorada via integração no host para MySQL e MS SQL Server, enriquecendo insights e organização de metadados no New Relic sem afetar o faturamento ou a telemetria existente.
+
+### Grandes mudanças
+
+* Adicionadas funções não agregadoras às [referênciasNRQL ](/docs/nrql/nrql-syntax-clauses-functions/#non-aggregator-functions/).
+* Atualizados os [requisitos do agenteRuby e a estrutura suportada](/docs/apm/agents/ruby-agent/getting-started/ruby-agent-requirements-supported-frameworks/).
+* Adicionados logs como evento personalizado New Relic aos [logs do OpenTelemetry no documento New Relic](/docs/opentelemetry/best-practices/opentelemetry-best-practices-logs/#custom-events).
+* Atualizados os tempos de execução com suporte para funções Linux, Windows e em contêineres no documento [Compatibilidade e requisitos para funções Azure instrumentadas](/docs/serverless-function-monitoring/azure-function-monitoring/compatibility-requirement-azure-monitoring/#supported-runtimes).
+* Atualizados os dados métricos do [Confluent integração na nuvem](/docs/message-queues-streaming/installation/confluent-cloud-integration/#metrics).
+* O GCP Cloud Run foi removido da [configuração do agente Node.js.](/docs/apm/agents/nodejs-agent/installation-configuration/nodejs-agent-configuration/)
+* [Compatibilidade e requisitos atualizados para monitoramento de IA](/docs/ai-monitoring/compatibility-requirements-ai-monitoring/) para incluir bibliotecas adicionais suportadas pelo agente .NET.
+* Adicionado ponto de extremidade dualstack de telemetria New Relic ao [tráfego de redeNew Relic ](/docs/new-relic-solutions/get-started/networks/#new-relic-endpoints).
+* Adicionado `GcpHttpExternalRegionalLoadBalancerSample` à [integração de monitoramento do Google Cloud Load Balancing](/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-load-balancing-monitoring-integration/).
+* Adicionado o procedimento de inicialização do OpenShift sobre como [instalar o documento do gerenciador de tarefas do Sintéticos](/docs/synthetics/synthetic-monitoring/private-locations/install-job-manager/#-install).
+* Atualizada a [versão 12 do agente Node.js.](/docs/apm/agents/nodejs-agent/installation-configuration/update-nodejs-agent/)
+* Adicionada integração perfeita para [AWS com New Relic utilizando CloudFormation e CloudWatch Metric Streams](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms/), incluindo suporte para pesquisa de API.
+
+### Pequenas mudanças
+
+* Adicionado `Transaction` como período de retenção para [rastreamento da transação](/docs/data-apis/manage-data/manage-data-retention/#retention-periods/).
+* Adicionado `Destination` como uma nova categoria para [Regras e limites de alerta](/docs/alerts/admin/rules-limits-alerts/).
+* Foi adicionado um destaque na [Introdução ao documento do Azure Native New Relic Service](/docs/infrastructure/microsoft-azure-integrations/get-started/azure-native/) para garantir que as configurações de diagnóstico nos recursos do Azure estejam configuradas corretamente ou desabilitar o encaminhamento por meio do Azure Native New Relic Service para impedir que dados sejam enviados para a plataforma New Relic.
+* Atualizou a última biblioteca compatível para [o agente .NET](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements/).
+* Adicionou um aviso no documento [de notas de versão do agente iOS](/docs/release-notes/mobile-release-notes/ios-release-notes/index/) para anunciar que, a partir da versão 7.5.4 do iOS SDK, uma alteração agora resulta no relato de evento Handled Exception suprimido anteriormente.
+* Requisitos atualizados para relacionamentos de contêiner de serviço para especificar atributos de recursos para ambientes Kubernetes e `container.id` para ambientes não-Kubernetes, garantindo a configuração de telemetria adequada para [recursosOpenTelemetry no New Relic](/docs/opentelemetry/best-practices/opentelemetry-best-practices-resources/).
+* Adicionado suporte CLI para instalação de versão de [agente de infraestrutura específica](/docs/infrastructure/infrastructure-agent/new-relic-guided-install-overview/#install-specific-versions), permitindo implantação consistente e compatibilidade de sistema; especifique a versão usando `@X.XX.X` no nome da receita.
+* Foi adicionado um destaque para enfatizar os requisitos de acesso de função para usar os recursos **Manage Account Cardinality**, **Manage Metric Cardinality** e **Create Pruning Rules** na interface; certifique-se de que as permissões estejam definidas no [Gerenciamento de Cardinalidade](/docs/data-apis/ingest-apis/metric-api/cardinality-management/#attributes-table).
+* Atualizada a [compatibilidade e os requisitos para o agente Node.js](/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent/) para `v12.23.0`.
+* Adicionadas permissões mínimas necessárias para configurar um [Elasticsearch](/docs/infrastructure/host-integrations/host-integrations-list/elasticsearch/elasticsearch-integration).
+* Atualizou o atributo `FACET` limite máximo de uso aceitável de 5.000 para 20.000 valores para [sintaxe de alerta NRQL](/docs/alerts/create-alert/create-alert-condition/create-nrql-alert-conditions/).
+
+### Notas de versão
+
+* Anunciado 7 de janeiro de 2026 como a data de fim de vida para as [regras de descarte direcionadas a infraestrutura evento em `SystemSample`, `ProcessSample`, `NetworkSample` e `StorageSample`](/eol/2025/05/drop-rule-filter/)
+
+* Com efeito imediato, o Fim da Vida Útil do [FACET em messageId e timestamp na condição do alerta](/eol/2025/07/deprecating-alert-conditions/).
+
+* Anunciado 28 de outubro de 2025 como a data de fim da vida útil do [Attention Required](/eol/2025/07/upcoming-eols/).
+
+* Confira nossas postagens de Novidades:
+
+ * [Envie notificação diretamente para o Microsoft Teams](/whats-new/2025/03/whats-new-03-13-microsoft-teams-integration/)
+ * [O New Relic Compute Optimizer já está disponível para todos!](/whats-new/2025/06/whats-new-06-25-compute-optimizer/)
+ * [Consulta de Logs Cross Account no Unified consulta Explorer](/whats-new/2025/07/whats-new-07-01-logs-uqe-cross-account-query/)
+ * [O monitoramento do Kubernetes com OpenTelemetry já está disponível!](/whats-new/2025/07/whats-new-7-01-k8s-otel-monitoring/)
+ * [O monitoramento de nós do Windows para Kubernetes agora está em versão de visualização pública](/whats-new/2025/07/whats-new-07-04-k8s-windows-nodes-preview/)
+ * [Identificar problemas de desempenho: filtragem avançada para visualizações de página e Core Web Vitals](/whats-new/2025/07/whats-new-07-09-browser-monitoring/)
+ * [Agora você pode classificar pelos erros mais recentes](/whats-new/2025/07/whats-new-7-08-ei-sort-by-newest/)
+ * [Seus dados do navegador, seus termos: Novas opções de controle](/whats-new/2025/07/whats-new-07-10-browser-monitoring/)
+ * [Análise de consulta profunda para banco de dados agora disponível para todos](/whats-new/2025/07/whats-new-07-24-db-query-performance-monitoring/)
+ * [NRQL Previsões e Alertas Preditivos agora estão disponíveis para o público em geral](/whats-new/2025/07/whats-new-7-22-predictive-analytics/)
+ * [Convergência APM + OpenTelemetry GA](/whats-new/2025/07/whats-new-07-21-apm-otel/)
+ * [Integração Agentic para GitHub Copilot e ServiceNow agora disponível para todos](/whats-new/2025/07/whats-new-7-15-agentic-ai-integrations/)
+
+* Fique por dentro dos nossos últimos lançamentos:
+
+ * [Tempo de execução da API do Node v1.2.119](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.119/)
+ * Corrigidos problemas de vulnerabilidades.
+
+ * [Tempo de execução do Ping v1.51.0](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.119/)
+
+ * Vulnerabilidades de logback-core corrigidas para tempo de execução de ping.
+ * Vulnerabilidades do servidor jetty corrigidas para tempo de execução de ping.
+ * Vulnerabilidades corrigidas do Ubuntu para tempo de execução de ping.
+
+ * [Agente Browser v1.292.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.292.0/)
+
+ * Atualizar definição de `BrowserInteraction` e `previousUrl`.
+ * Adicionado evento de inspeção adicional.
+ * Valor fixo da API `finished` `timeSinceLoad`.
+
+ * [Integração Kubernetes v3.42.1](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-42-1/)
+ * Ajustes internos corrigidos no backend e relacionados ao CI para compatibilidade futura da plataforma.
+
+ * [Gerenciador de tarefas v444](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-444/)
+ * Corrigido um problema que impedia que certos clientes vissem resultados para alguns monitores com tempos de execução mais longos.
+
+ * [Agente Python v10.14.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-101400/)
+
+ * Adicionado suporte para `Azure Function Apps`.
+ * Arquivos `pb2` corrigidos para habilitar o suporte `protobuf v6`.
+
+ * [Agente Android v7.6.7](/docs/release-notes/mobile-release-notes/android-release-notes/android-767/)
+
+ * Desempenho aprimorado para resolver ANRs ao relatar logs.
+ * Corrigido um problema para continuar relatando logs após o encerramento do aplicativo.
+ * Foi resolvido um problema com o monitoramento do estado do aplicativo e a transmissão de dados.
+ * Poucas violações foram melhoradas ao ativar o modo estrito.
+
+ * [Integração Kubernetes v3.42.2](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-42-2/)
+
+ * Atualizado `golang.org/x/crypto` para `v0.39.0`.
+ * Atualizado `go` para `v1.24.4`.
+
+ * [.NET agente v10.42.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-42-0/)
+
+ * Adicionado suporte para o Azure Service Bus.
+ * Erros de compilação do profiler corrigidos com o VS mais recente.
+
+ * [agente PHP v11.10.0.24](/docs/release-notes/agent-release-notes/php-release-notes/php-agent-11-10-0-24/)
+
+ * Adicionada API de tempo de execução do Composer para ser usada por padrão para detectar pacotes usados pelo aplicativo PHP.
+ * Corrigido comportamento indefinido na API de tempo de execução do Composer.
+
+ * [Tempo de execução do navegador Node v3.0.32](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.32/)
+ * Opções do construtor de cromo atualizadas para o Chrome 131.
+
+ * [Aplicativo móvel para iOS v6.9.8](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6098/)
+ * O recurso Ask AI foi aprimorado com uma conexão de soquete mais robusta e confiável, garantindo uma experiência perfeita.
+
+ * [Aplicativo móvel para Android v5.29.7](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5297/)
+ * O recurso Ask AI foi aprimorado com uma conexão de soquete mais robusta e confiável, garantindo uma experiência perfeita.
+
+ * [Agente Node.js v12.22.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-22-0/)
+
+ * Adicionado suporte para streaming `openai` v5.
+ * Adicionado suporte para api `openai.responses.create`.
+ * Corrigido o log de erro para cabeçalho tracestate indefinido.
+
+ * [agente de infraestrutura v1.65.0](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1650/)
+
+ * Dependência atualizada `newrelic/nri-winservices` para `v1.2.0`
+ * tag do docker alpina atualizada para `v3.22`
+
+ * [agente de infraestrutura v1.65.1](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1651/)
+ * atualizar dependência `newrelic/nri-flex` para `v1.16.6`
+
+ * [Agente Browser v1.292.1](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.292.1/)
+ * Corrigida a precedência da condição de corrida do atributo personalizado.
+
+ * [NRDOT v1.2.0](/docs/release-notes/nrdot-release-notes/nrdot-2025-06-26/)
+ * Aumentou o núcleo beta do OTEL para `v0.128.0`
+
+ * [Agente de mídia para HTML5.JS v3.0.0](/docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-25-04-15/)
+
+ * Foi introduzido um novo tipo de evento.
+ * O tipo de evento `PageAction` foi descontinuado.
+
+ * [Agente de mídia para HTML5.JS v3.1.1](/docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-25-06-15/)
+
+ * Publicação npm habilitada para o pacote, garantindo fácil acessibilidade e distribuição.
+ * As compilações `cjs`, `esm` e `umd` foram adicionadas à pasta `dist`, garantindo compatibilidade com os formatos de módulo CommonJS, ES Modules e UMD.
+
+ * [Agente de mídia para Roku v4.0.0](/docs/release-notes/streaming-others-release-notes/streaming-others-agent-25-02-25/)
+
+ * Foi introduzido um novo tipo de evento.
+ * O tipo de evento `RokuVideo` foi descontinuado.
+ * O tipo de evento `RokuSystem` foi descontinuado.
+
+ * [Agente de mídia para Roku v4.0.1](/docs/release-notes/streaming-others-release-notes/streaming-others-agent-25-04-22/)
+ * Renomeado `errorName` com `errorMessage`, pois `errorName` foi descontinuado.
+
+ * [Gerenciador de tarefas v447](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-447/)
+ * Atualização de imagem base fixa de `ubuntu 22.04` para `ubuntu 24.4`
+
+ * [Tempo de execução do Ping v1.52.0](/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.52.0/)
+ * Atualização da imagem base aprimorada de `ubuntu 22.04` para `ubuntu 24.04`
+
+ * [Kubernetes integração v3.43.0](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-43-0/)
+ * Adicionado suporte para monitoramento de nós Windows no cluster do Kubernetes.
+
+ * [Aplicativo móvel para Android v5.29.8](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5298/)
+ * Bug corrigido e interface de usuário melhorada para uma experiência mais suave.
+
+ * [Agente Node.js v12.23.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-23-0/)
+
+ * Adicionada a capacidade de gerar relatórios apenas sobre os intervalos de entrada e saída.
+ * Adicionado suporte ao Node.js 24.
+ * Relatório de compatibilidade atualizado.
+
+ * [Tempo de execução da API do Node v1.2.120](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.120/)
+ * Corrigidas as vulnerabilidades para `CVE-2024-39249`
+
+ * [Aplicativo móvel para iOS v6.9.9](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6099/)
+ * O recurso Ask AI foi aprimorado com prompt dinâmico.
+
+ * [Agente Browser v1.293.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.293.0/)
+
+ * Adicionada mensagem interna **para tarefas longas**.
+ * Resolvido o problema que impedia que o rastreamento distribuído fosse desabilitado.
+
+ * [Tempo de execução do navegador Node v3.0.35](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.35/)
+ * Imagem base atualizada
+
+ * [Agente Java v8.22.0](/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8220/)
+
+ * Metadados vinculados para serviços de aplicativos Azure.
+ * Removido `MonoFlatMapMain` instrumentação.
+
+ * [Agente Node.js v12.24.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-24-0/)
+
+ * Implementado limite de tamanho de valor de atributo configurável
+ * Relatório de compatibilidade atualizado.
+
+ * [Integração Kubernetes v3.43.2](docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-43-2/)
+ * Atualizar a versão do gráfico kube-state-métrica de `5.12.1` para `5.30.1`
+
+ * [Agente iOS v7.5.7](/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-757/)
+ * 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.
+
+ * [Aplicativo móvel para Android v5.29.9](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5299/)
+ * Feedback aprimorado com renderização dinâmica da interface do usuário.
+
+ * [Aplicativo móvel para Android v5.30.0](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-53000/)
+ * Corrigimos bugs e atualizamos os sinalizadores do Teams GA para uma melhor experiência do usuário.
+
+ * [Go agente v3.40.1](/docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-40-1/)
+
+ * Utilização revertida. Voltar para a versão v3.39.0 devido a bug de deadlock
+ * Removidos os testes awssupport\_test.go que adicionavam dependência direta ao módulo go
+
+ * [Agente Flutter v1.1.12](/docs/release-notes/mobile-release-notes/flutter-release-notes/flutter-agent-1112/)
+
+ * Melhorou o agente nativo do Android atualizado para a versão 7.6.7
+ * Melhorou o agente nativo do iOS atualizado para a versão 7.5.6
+
+ * [Agente Node.js v13.0.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-0-0/)
+
+ * Suporte abandonado para Node.js 18
+ * Versão mínima suportada atualizada para `fastify` para 3.0.0, `pino` para 8.0.0 e `koa-router` para 12.0.0
+
+ * [Agente Browser v1.294.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.294.0/)
+ * Corrigido o relatório previousUrl vazio como indefinido
+
+ * [agente de infraestrutura v1.65.4](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1654/)
+ * Atualizou a dependência `newrelic/nri-prometheus` para v2.26.2
+
+ * [Aplicativo móvel para iOS v6.9.10](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6100/)
+ * Feedback aprimorado com renderização dinâmica da interface do usuário.
+
+ * [Agente Android NDK v1.1.3](/docs/release-notes/mobile-release-notes/android-release-notes/android-ndk-113/)
+ * Adicionado suporte para tamanho de página de 16 KB
+
+ * [agente de infraestrutura v1.65.3](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1653/)
+
+ * Alça de processo do Windows alterada.
+ * Colidiu `nri-docker` para `v2.5.1`, `nri-prometheus` para `v2.26.1`
+
+ * [.NET agente v10.43.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-43-0/)
+ * Adicionado suporte para tópicos no Azure Service Bus
+
+ * [Agente Node.js v12.25.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-25-0/)
+ * Instrumento fixo AWS Bedrock Converse API
+
+ * [Agente Node.js v12.24.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-24-0/)
+
+ * Implementado limite de tamanho de valor de atributo configurável
+ * Relatório de compatibilidade atualizado
+
+ * [CLI de diagnóstico (nrdiag) v3.4.0](/docs/release-notes/diagnostics-release-notes/diagnostics-cli-release-notes/diagnostics-cli-340/)
+ * Erros corrigidos relacionados ao GLIBC, como `/lib64/libc.so.6: version 'GLIBC_2.34'` não encontrado, foram resolvidos
\ 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
new file mode 100644
index 00000000000..c5167cc6355
--- /dev/null
+++ b/src/i18n/content/pt/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
+
+### Correções de bugs
+
+#### Impedir importação dupla da classe agregada Session Replay
+
+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
+
+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.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.
\ 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.298.mdx b/src/i18n/content/pt/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.298.mdx
new file mode 100644
index 00000000000..a076aefbcc4
--- /dev/null
+++ b/src/i18n/content/pt/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.298.mdx
@@ -0,0 +1,34 @@
+---
+subject: Browser agent
+releaseDate: '2025-09-19'
+version: 1.298.0
+downloadLink: 'https://www.npmjs.com/package/@newrelic/browser-agent'
+features:
+ - Factor long tasks into soft nav base interaction span
+bugs:
+ - Force LCP to report the original page URL
+security: []
+translationType: machine
+---
+
+## v1.298.0
+
+### Recurso
+
+#### Fator de tarefas longas em um intervalo de interação de base de navegação suave
+
+`BrowserInteraction` sob navegação suave ("SPA 2.0") se estenderá em duração além do tempo de modificação do DOM até o ponto em que nenhuma tarefa longa for observada por 5 segundos. `JavascriptError` e `AjaxRequest` ainda não estão associados a essa interação durante esse período estendido além do fim da heurística original.
+
+### Correções de bugs
+
+#### Forçar o LCP a relatar a URL da página original
+
+Permitir que o LCP relate seu pageUrl de forma distinta do URL de coleta. Foi observado um problema em que navegações suaves ocorrendo antes da coleta do LCP relatavam a URL da página atual em vez da URL da página original vinculada ao LCP. Essa alteração permite que os nós de coleta do LCP relatem o URL original, independentemente do URL da página atual. A alteração deve ser aplicada aos atributos `pageUrl` e `targetGroupedUrl`.
+
+## 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.298.0 do agente 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.298.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/nrdot-release-notes/nrdot-2025-09-18.mdx b/src/i18n/content/pt/docs/release-notes/nrdot-release-notes/nrdot-2025-09-18.mdx
new file mode 100644
index 00000000000..c4b1a34139d
--- /dev/null
+++ b/src/i18n/content/pt/docs/release-notes/nrdot-release-notes/nrdot-2025-09-18.mdx
@@ -0,0 +1,16 @@
+---
+subject: NRDOT
+releaseDate: '2025-09-18'
+version: 1.4.0
+metaDescription: Release notes for NRDOT Collector version 1.4.0
+translationType: machine
+---
+
+## Registro de alterações
+
+### Recurso
+
+* façanha: Adicionar spanprocessor ao nrdot-coletor (#371)
+* façanha: Aumente as versões do componente do hotel de v0.131.0 para v0.132.0 (#368)
+* façanha: Adicionar newrelic.service.type à configuração de telemetria interna (#380)
+* façanha: Habilitar detecção de host.name para ec2 (#382)
\ No newline at end of file
diff --git a/src/i18n/content/pt/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-467.mdx b/src/i18n/content/pt/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-467.mdx
new file mode 100644
index 00000000000..ce60925dded
--- /dev/null
+++ b/src/i18n/content/pt/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-467.mdx
@@ -0,0 +1,10 @@
+---
+subject: Job Manager
+releaseDate: '2025-09-22'
+version: '467'
+translationType: machine
+---
+
+### Correções
+
+* Corrigimos CVE-2025-58056, CVE-2025-58057 e as vulnerabilidades subjacentes do Ubuntu para abordar vulnerabilidades de segurança no sjm.
\ No newline at end of file
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/node-browser-runtime-release-notes/node-browser-runtime-3.0.mdx b/src/i18n/content/pt/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.mdx
new file mode 100644
index 00000000000..36ec24357e4
--- /dev/null
+++ b/src/i18n/content/pt/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
+---
+
+### Melhorias
+
+* 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.
\ 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
| |