From 4716e99eaecc310631572a3440f2a1bda26f1de9 Mon Sep 17 00:00:00 2001 From: Abhilash Dutta Date: Sat, 27 Sep 2025 01:31:52 +0530 Subject: [PATCH 01/21] Azure CCI Integration document --- .../microsoft-azure.mdx | 97 +++++++++++++++++++ 1 file changed, 97 insertions(+) create mode 100644 src/content/docs/cci/financial-intelligence/microsoft-azure.mdx diff --git a/src/content/docs/cci/financial-intelligence/microsoft-azure.mdx b/src/content/docs/cci/financial-intelligence/microsoft-azure.mdx new file mode 100644 index 00000000000..b46707a4165 --- /dev/null +++ b/src/content/docs/cci/financial-intelligence/microsoft-azure.mdx @@ -0,0 +1,97 @@ +--- +title: Azure CCI +metaDescription: Connect your Azure billing to New Relic Cloud Cost Intelligence to monitor, analyze, and optimize cloud spending across Azure services. +freshnessValidatedDate: never +--- + + + We're still working on this feature, but we'd love for you to try it out! + + This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). + + +Connect your Azure billing to Cloud Cost Intelligence for complete cost monitoring and optimization of your Azure infrastructure. Get real-time visibility into spending patterns, resource use, and cost allocation across services and resource groups. + +With the Azure integration, you can: + - Monitor spending across all subscriptions and resource groups + - Analyze cost trends and identify anomalies + - Optimize resource allocation and eliminate waste + - Create custom dashboards for financial reporting + - Set up alerts for budget thresholds and cost spikes + +## Prerequisites + +Before you connect Azure to Cloud Cost Intelligence, make sure you have: + - **Azure subscription** with active billing account + - **Contributor or Owner role** on the subscription you want to monitor + - **Access to Azure Cost Management** features + - **Billing reader permissions** for the subscription or management group + +## Benefits + +With the Azure - CCI, you can: + +- **Optimize resource usage** - Find underutilized or costly Azure services and VMs to adjust allocations across subscriptions and resource groups + +- **Control expenses** - See specific cost drivers in your Azure environment, including compute, storage, networking, and database services for better financial decisions + +- **Enhance efficiency** - Focus on resource management strategies that align with business objectives for efficient use of Azure resources and budget + +- **Monitor multi-subscription costs** - Track spending across multiple Azure subscriptions and management groups from one dashboard + +- **Enable cost accountability** - Implement department-level cost allocation and chargeback using Azure tags and resource group organization + +- **Manage budgets proactively** - Set up alerts for Azure spending thresholds and budget limits to prevent overruns and maintain financial control + +## Connect Azure to Cloud Cost Intelligence + + + + ### Select your account + + Start the integration by choosing which New Relic account will receive your Azure cost data. + + 1. Go to [**one.newrelic.com**](https://one.newrelic.com) > **All Capabilities** > **Azure-CCI**. + 2. Select your account from the dropdown and click **Continue**. + + + + ### Configure connection details + + Provide your Azure billing information to establish the connection between Azure and Cloud Cost Intelligence. + + 1. On the connection setup page, enter this information to connect to your Azure billing account: + - **Connection name** - Provide a descriptive name like "Azure Production Environment" + - **Azure Agreement Type** - Select your agreement type: Enterprise Agreement, MCP, or CSP + - **Tenant ID** - Enter your Azure tenant ID from the Azure portal + - **Billing account ID** - Enter your Azure billing account ID from the Azure portal + - **Storage account** - Enter your Azure storage account name from the Azure portal + - **Container name** - Enter your Azure container name from the Azure portal + 2. Click **Continue**. + + + + ### Test and create connection + + Verify the connection works and create the integration with proper permissions. + + 1. Click **Initiate Connection** to start the request (admin approval required). + + Complete these Azure admin tasks: + 1. Grant access to the service principal named **msazurecostdata**. See [View enterprise applications](https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/view-applications-portal) to learn how to use Microsoft Entra admin center to find enterprise applications in your tenant. + 2. Provide [Access Control (IAM)](https://learn.microsoft.com/en-us/azure/role-based-access-control/quickstart-assign-role-user-portal#grant-access) access to the service principal for the necessary Azure resources. + + 2. Click **Create Connection** to create the **msazurecostdata** entry. + 3. Click **See your data**. + + + + ### Verify data collection + + Go to the [**Cost Overview**](/docs/cci/financial-intelligence/cloud-cost-insights) and check that your Azure cost data displays correctly. + + + Processing your data for the first time can take up to 12 hours. + + + \ No newline at end of file From c7db2de5822b70a0a5086cb29560783d98bf4a89 Mon Sep 17 00:00:00 2001 From: Abhilash Dutta Date: Sat, 27 Sep 2025 01:34:15 +0530 Subject: [PATCH 02/21] Azure CCI documentation --- .../{microsoft-azure.mdx => cci-azure.mdx} | 0 src/nav/cci.yml | 2 ++ 2 files changed, 2 insertions(+) rename src/content/docs/cci/financial-intelligence/{microsoft-azure.mdx => cci-azure.mdx} (100%) diff --git a/src/content/docs/cci/financial-intelligence/microsoft-azure.mdx b/src/content/docs/cci/financial-intelligence/cci-azure.mdx similarity index 100% rename from src/content/docs/cci/financial-intelligence/microsoft-azure.mdx rename to src/content/docs/cci/financial-intelligence/cci-azure.mdx diff --git a/src/nav/cci.yml b/src/nav/cci.yml index e7982d29cb9..f58da81cedf 100644 --- a/src/nav/cci.yml +++ b/src/nav/cci.yml @@ -23,6 +23,8 @@ pages: path: /docs/cci/financial-intelligence/k8s-cost-insights - title: Budget summary path: /docs/cci/financial-intelligence/cci-budgets + - title: Azure CCI + path: /docs/cci/financial-intelligence/cci-azure - title: Query your data with NRQL path: /docs/cci/financial-intelligence/nrql-for-cci - title: Troubleshooting CCI From ef4db4f84fecdefbaa029232987878b87e0991ba Mon Sep 17 00:00:00 2001 From: Abhilash Dutta Date: Sat, 27 Sep 2025 01:44:21 +0530 Subject: [PATCH 03/21] Updated the verification details --- src/content/docs/cci/financial-intelligence/cci-azure.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/cci/financial-intelligence/cci-azure.mdx b/src/content/docs/cci/financial-intelligence/cci-azure.mdx index b46707a4165..f361f1b8855 100644 --- a/src/content/docs/cci/financial-intelligence/cci-azure.mdx +++ b/src/content/docs/cci/financial-intelligence/cci-azure.mdx @@ -88,7 +88,7 @@ With the Azure - CCI, you can: ### Verify data collection - Go to the [**Cost Overview**](/docs/cci/financial-intelligence/cloud-cost-insights) and check that your Azure cost data displays correctly. + Go to [**Cost Overview**](/docs/cci/financial-intelligence/cloud-cost-insights) to view your Azure cost data. Processing your data for the first time can take up to 12 hours. From 4aebcbe6433c622352801a576cc2c8958b00878d Mon Sep 17 00:00:00 2001 From: Abhilash Dutta Date: Sat, 27 Sep 2025 01:57:04 +0530 Subject: [PATCH 04/21] Updated the callout --- .../docs/cci/financial-intelligence/cci-azure.mdx | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/src/content/docs/cci/financial-intelligence/cci-azure.mdx b/src/content/docs/cci/financial-intelligence/cci-azure.mdx index f361f1b8855..47f5654d2e5 100644 --- a/src/content/docs/cci/financial-intelligence/cci-azure.mdx +++ b/src/content/docs/cci/financial-intelligence/cci-azure.mdx @@ -49,7 +49,7 @@ With the Azure - CCI, you can: ### Select your account - Start the integration by choosing which New Relic account will receive your Azure cost data. + Start the integration by choosing your New Relic account. 1. Go to [**one.newrelic.com**](https://one.newrelic.com) > **All Capabilities** > **Azure-CCI**. 2. Select your account from the dropdown and click **Continue**. @@ -78,8 +78,8 @@ With the Azure - CCI, you can: 1. Click **Initiate Connection** to start the request (admin approval required). Complete these Azure admin tasks: - 1. Grant access to the service principal named **msazurecostdata**. See [View enterprise applications](https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/view-applications-portal) to learn how to use Microsoft Entra admin center to find enterprise applications in your tenant. - 2. Provide [Access Control (IAM)](https://learn.microsoft.com/en-us/azure/role-based-access-control/quickstart-assign-role-user-portal#grant-access) access to the service principal for the necessary Azure resources. +
  • Provide access to the service principal **msazurecostdata**. See [View enterprise applications](https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/view-applications-portal) to learn how to use Microsoft Entra admin center to find enterprise applications in your tenant.
    • +
  • Provide [Access Control (IAM)](https://learn.microsoft.com/en-us/azure/role-based-access-control/quickstart-assign-role-user-portal#grant-access) access to the service principal for the necessary Azure resources.
    •  2. Click **Create Connection** to create the **msazurecostdata** entry. 3. Click **See your data**. @@ -90,8 +90,8 @@ With the Azure - CCI, you can: Go to [**Cost Overview**](/docs/cci/financial-intelligence/cloud-cost-insights) to view your Azure cost data. - - Processing your data for the first time can take up to 12 hours. - + + Processing your data for the first time can take up to 12 hours. +     \ No newline at end of file From fb8ec15c0b07061ef245c8c57ab7336f526014cf Mon Sep 17 00:00:00 2001 From: Abhilash Dutta Date: Sat, 27 Sep 2025 02:06:49 +0530 Subject: [PATCH 05/21] Added Unordered List to the callout --- src/content/docs/cci/financial-intelligence/cci-azure.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/content/docs/cci/financial-intelligence/cci-azure.mdx b/src/content/docs/cci/financial-intelligence/cci-azure.mdx index 47f5654d2e5..73eb6751d40 100644 --- a/src/content/docs/cci/financial-intelligence/cci-azure.mdx +++ b/src/content/docs/cci/financial-intelligence/cci-azure.mdx @@ -78,8 +78,10 @@ With the Azure - CCI, you can: 1. Click **Initiate Connection** to start the request (admin approval required). Complete these Azure admin tasks: +
    • Provide access to the service principal **msazurecostdata**. See [View enterprise applications](https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/view-applications-portal) to learn how to use Microsoft Entra admin center to find enterprise applications in your tenant.
    • Provide [Access Control (IAM)](https://learn.microsoft.com/en-us/azure/role-based-access-control/quickstart-assign-role-user-portal#grant-access) access to the service principal for the necessary Azure resources.
      • +
    2. Click **Create Connection** to create the **msazurecostdata** entry. 3. Click **See your data**. From 9d5332ac0625b0f4372aaaf8220f9d29945fbc2e Mon Sep 17 00:00:00 2001 From: Abhilash Dutta Date: Thu, 9 Oct 2025 19:38:09 +0530 Subject: [PATCH 06/21] Updated the navigation and added the content to Azure and GCP --- .../cci/financial-intelligence/cci-azure.mdx | 67 +++++++++---------- .../financial-intelligence/cci-budgets.mdx | 2 +- .../cci/{getting-started => }/overview.mdx | 2 + .../{getting-started => }/prerequisites.mdx | 4 +- .../docs/cci/{getting-started => }/setup.mdx | 4 +- src/nav/cci.yml | 20 +++--- 6 files changed, 48 insertions(+), 51 deletions(-) rename src/content/docs/cci/{getting-started => }/overview.mdx (99%) rename src/content/docs/cci/{getting-started => }/prerequisites.mdx (99%) rename src/content/docs/cci/{getting-started => }/setup.mdx (98%) diff --git a/src/content/docs/cci/financial-intelligence/cci-azure.mdx b/src/content/docs/cci/financial-intelligence/cci-azure.mdx index 73eb6751d40..ded001259c4 100644 --- a/src/content/docs/cci/financial-intelligence/cci-azure.mdx +++ b/src/content/docs/cci/financial-intelligence/cci-azure.mdx @@ -2,6 +2,8 @@ title: Azure CCI metaDescription: Connect your Azure billing to New Relic Cloud Cost Intelligence to monitor, analyze, and optimize cloud spending across Azure services. freshnessValidatedDate: never +redirect: + - /docs/cci/financial-intelligence/cci-azure --- @@ -10,14 +12,14 @@ freshnessValidatedDate: never This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). -Connect your Azure billing to Cloud Cost Intelligence for complete cost monitoring and optimization of your Azure infrastructure. Get real-time visibility into spending patterns, resource use, and cost allocation across services and resource groups. +Connect your Azure billing to Cloud Cost Intelligence for complete cost monitoring and optimization of your Azure infrastructure. Get real-time visibility into spending patterns, resource use, and cost allocation across services and resource groups. With the Azure - CCI, you can: -With the Azure integration, you can: - - Monitor spending across all subscriptions and resource groups - - Analyze cost trends and identify anomalies - - Optimize resource allocation and eliminate waste - - Create custom dashboards for financial reporting - - Set up alerts for budget thresholds and cost spikes + - **Optimize resource usage** - Find underutilized or costly Azure services and VMs to adjust allocations across subscriptions and resource groups + - **Control expenses** - See specific cost drivers in your Azure environment, including compute, storage, networking, and database services for better financial decisions + - **Enhance efficiency** - Focus on resource management strategies that align with business objectives for efficient use of Azure resources and budget + - **Monitor multi-subscription costs** - Track spending across multiple Azure subscriptions and management groups from one dashboard + - **Enable cost accountability** - Implement department-level cost allocation and chargeback using Azure tags and resource group organization + - **Manage budgets proactively** - Set up alerts for Azure spending thresholds and budget limits to prevent overruns and maintain financial control ## Prerequisites @@ -27,22 +29,6 @@ Before you connect Azure to Cloud Cost Intelligence, make sure you have: - **Access to Azure Cost Management** features - **Billing reader permissions** for the subscription or management group -## Benefits - -With the Azure - CCI, you can: - -- **Optimize resource usage** - Find underutilized or costly Azure services and VMs to adjust allocations across subscriptions and resource groups - -- **Control expenses** - See specific cost drivers in your Azure environment, including compute, storage, networking, and database services for better financial decisions - -- **Enhance efficiency** - Focus on resource management strategies that align with business objectives for efficient use of Azure resources and budget - -- **Monitor multi-subscription costs** - Track spending across multiple Azure subscriptions and management groups from one dashboard - -- **Enable cost accountability** - Implement department-level cost allocation and chargeback using Azure tags and resource group organization - -- **Manage budgets proactively** - Set up alerts for Azure spending thresholds and budget limits to prevent overruns and maintain financial control - ## Connect Azure to Cloud Cost Intelligence @@ -51,23 +37,30 @@ With the Azure - CCI, you can: Start the integration by choosing your New Relic account. - 1. Go to [**one.newrelic.com**](https://one.newrelic.com) > **All Capabilities** > **Azure-CCI**. + 1. Go to [**one.newrelic.com**](https://one.newrelic.com) > **All Capabilities** > **Azure - CCI**. 2. Select your account from the dropdown and click **Continue**.     - ### Configure connection details - - Provide your Azure billing information to establish the connection between Azure and Cloud Cost Intelligence. - - 1. On the connection setup page, enter this information to connect to your Azure billing account: - - **Connection name** - Provide a descriptive name like "Azure Production Environment" - - **Azure Agreement Type** - Select your agreement type: Enterprise Agreement, MCP, or CSP - - **Tenant ID** - Enter your Azure tenant ID from the Azure portal - - **Billing account ID** - Enter your Azure billing account ID from the Azure portal - - **Storage account** - Enter your Azure storage account name from the Azure portal - - **Container name** - Enter your Azure container name from the Azure portal - 2. Click **Continue**. + ### Connect your Azure billing account + + Enter your Azure billing information to connect Azure with Cloud Cost Intelligence: + - **Connection name** - Enter a descriptive name, such as "Azure Production Environment. + - **Azure Agreement Type** - Select your agreement type. You must have **[Cost and usage details (FOCUS) access](https://learn.microsoft.com/en-us/azure/cost-management-billing/dataset-schema/schema-index#latest-dataset-schema-files)**. For more information, see [Billing accounts and scopes in the Azure portal](https://learn.microsoft.com/en-us/azure/cost-management-billing/manage/view-all-accounts). + + To locate your agreement type, navigate to **[Microsoft Entra Admin center](https://entra.microsoft.com/#home) > Billing > Properties**. + + - **Tenant ID** - Enter the unique identifier for your organization's Microsoft Entra ID instance in Azure. + + To locate your **Tenant ID**, go to **[Microsoft Entra Admin center](https://entra.microsoft.com/#home)**. + + - **Billing account ID** - Enter your Azure billing account ID. For more information, see [Billing administration](https://learn.microsoft.com/en-us/azure/cost-management-billing/manage/direct-ea-administration#to-view-enrollment-properties). + - **Azure Storage account name** - Enter the name of your storage account, which provides a unique global address for all your Azure cloud storage data. + - **Storage Container Name** - Enter the name of the container within your storage account that organizes and groups your block blobs or files. + + To locate the Storage Container Name, go to **[Microsoft Azure](https://portal.azure.com/#home) > Subscription > Storage account > Container**. It is mandatory to add authentication for our service principal in your Azure container. + + - **Base drop path** - Enter the base path where billing data is stored in monthly format (for example, 20251001-20251031 for October 2025). This field is empty by default. @@ -79,7 +72,7 @@ With the Azure - CCI, you can: Complete these Azure admin tasks:
      -
    • Provide access to the service principal **msazurecostdata**. See [View enterprise applications](https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/view-applications-portal) to learn how to use Microsoft Entra admin center to find enterprise applications in your tenant.
      • +
    • Provide access to the service principal **msazurecostdata**. See [View enterprise applications](https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/view-applications-portal) for more information.
    • Provide [Access Control (IAM)](https://learn.microsoft.com/en-us/azure/role-based-access-control/quickstart-assign-role-user-portal#grant-access) access to the service principal for the necessary Azure resources.
     diff --git a/src/content/docs/cci/financial-intelligence/cci-budgets.mdx b/src/content/docs/cci/financial-intelligence/cci-budgets.mdx index 0a1b1f60ed8..d52d463616e 100644 --- a/src/content/docs/cci/financial-intelligence/cci-budgets.mdx +++ b/src/content/docs/cci/financial-intelligence/cci-budgets.mdx @@ -1,5 +1,5 @@ --- -title: Budgets +title: CCI Budgets tag: - cci - budgets diff --git a/src/content/docs/cci/getting-started/overview.mdx b/src/content/docs/cci/overview.mdx similarity index 99% rename from src/content/docs/cci/getting-started/overview.mdx rename to src/content/docs/cci/overview.mdx index c44e1a28f9c..fe0807256ef 100644 --- a/src/content/docs/cci/getting-started/overview.mdx +++ b/src/content/docs/cci/overview.mdx @@ -2,6 +2,8 @@ title: 'Cloud Cost Intelligence: Take control of your cloud spending' metaDescription: Gain comprehensive visibility and control over AWS cloud costs with CCI, enhancing your FinOps strategy for holistic cost management. freshnessValidatedDate: never +redirect: + - /docs/cci/getting-started/overview --- diff --git a/src/content/docs/cci/getting-started/prerequisites.mdx b/src/content/docs/cci/prerequisites.mdx similarity index 99% rename from src/content/docs/cci/getting-started/prerequisites.mdx rename to src/content/docs/cci/prerequisites.mdx index 360f60c2f14..b02f892616c 100644 --- a/src/content/docs/cci/getting-started/prerequisites.mdx +++ b/src/content/docs/cci/prerequisites.mdx @@ -2,6 +2,8 @@ title: Prerequisites for CCI metaDescription: Set up AWS for CCI with consolidated billing, CUR, IAM roles, and region activation to optimize cost analysis in New Relic. freshnessValidatedDate: never +redirect: + - /docs/cci/getting-started/prerequisites --- @@ -12,8 +14,6 @@ freshnessValidatedDate: never Prepare your AWS environment for Cloud Cost Intelligence (CCI) integration by following these prerequisites, including setting up consolidated billing, enabling cost and usage reports, configuring IAM roles and policies for secure access, and activating necessary AWS regions. Ensure your setup supports effective cost analysis and management within the New Relic platform. -## Prerequisites - diff --git a/src/nav/cci.yml b/src/nav/cci.yml index f58da81cedf..fffb93c0af3 100644 --- a/src/nav/cci.yml +++ b/src/nav/cci.yml @@ -1,14 +1,16 @@ title: Cloud Cost Intelligence path: /docs/cci pages: - - title: Getting started - pages: - - title: Overview - path: /docs/cci/getting-started/overview - - title: Prerequisites - path: /docs/cci/getting-started/prerequisites - - title: Set up - path: /docs/cci/getting-started/setup + - title: Overview + path: /docs/cci/overview + - title: Prerequisites + path: /docs/cci/prerequisites + - title: Set up Cloud Cost Intelligence + path: /docs/cci/setup + - title: Azure CCI + path: /docs/cci/financial-intelligence/cci-azure + - title: Google Cloud Platform CCI + path: /docs/cci/financial-intelligence/cci-gcp - title: Configure Cloud Cost Intelligence pages: - title: General settings @@ -23,8 +25,6 @@ pages: path: /docs/cci/financial-intelligence/k8s-cost-insights - title: Budget summary path: /docs/cci/financial-intelligence/cci-budgets - - title: Azure CCI - path: /docs/cci/financial-intelligence/cci-azure - title: Query your data with NRQL path: /docs/cci/financial-intelligence/nrql-for-cci - title: Troubleshooting CCI From 3f4432932b802815b016ce10a58eb5eb1c8e621a Mon Sep 17 00:00:00 2001 From: Abhilash Dutta Date: Thu, 9 Oct 2025 19:40:42 +0530 Subject: [PATCH 07/21] Added two new section --- .../docs/cci/{financial-intelligence => }/cci-azure.mdx | 0 src/content/docs/cci/google-cloud-platform-cci.mdx | 7 +++++++ 2 files changed, 7 insertions(+) rename src/content/docs/cci/{financial-intelligence => }/cci-azure.mdx (100%) create mode 100644 src/content/docs/cci/google-cloud-platform-cci.mdx diff --git a/src/content/docs/cci/financial-intelligence/cci-azure.mdx b/src/content/docs/cci/cci-azure.mdx similarity index 100% rename from src/content/docs/cci/financial-intelligence/cci-azure.mdx rename to src/content/docs/cci/cci-azure.mdx diff --git a/src/content/docs/cci/google-cloud-platform-cci.mdx b/src/content/docs/cci/google-cloud-platform-cci.mdx new file mode 100644 index 00000000000..26ac88f7f3f --- /dev/null +++ b/src/content/docs/cci/google-cloud-platform-cci.mdx @@ -0,0 +1,7 @@ +--- +title: Google Cloud Platform CCI +metaDescription: Connect your Google Cloud Platform billing to New Relic Cloud Cost Intelligence to monitor, analyze, and optimize cloud spending across GCP services. +freshnessValidatedDate: never +--- + +This page needs to be updated \ No newline at end of file From 7377294988ac0730c829f3a1d5e2047f531add47 Mon Sep 17 00:00:00 2001 From: Abhilash Dutta Date: Thu, 9 Oct 2025 19:50:08 +0530 Subject: [PATCH 08/21] Updated the navigation --- src/nav/cci.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/nav/cci.yml b/src/nav/cci.yml index fffb93c0af3..5cbd93c1b54 100644 --- a/src/nav/cci.yml +++ b/src/nav/cci.yml @@ -8,9 +8,9 @@ pages: - title: Set up Cloud Cost Intelligence path: /docs/cci/setup - title: Azure CCI - path: /docs/cci/financial-intelligence/cci-azure + path: /docs/cci/cci-azure - title: Google Cloud Platform CCI - path: /docs/cci/financial-intelligence/cci-gcp + path: /docs/cci/cci-gcp - title: Configure Cloud Cost Intelligence pages: - title: General settings From 13de7533cd960328dee25ed01782a21a3bf3da36 Mon Sep 17 00:00:00 2001 From: Abhilash Dutta Date: Thu, 9 Oct 2025 19:59:46 +0530 Subject: [PATCH 09/21] Deleted the orphan docs --- .../add-on-billing.mdx | 28 -- .../data-ingest-billing.mdx | 354 ------------------ .../es/docs/cci/getting-started/overview.mdx | 61 --- .../es/docs/cci/getting-started/setup.mdx | 83 ---- .../via-cloudformation.mdx | 70 ---- .../docs-release-notes/docs-7-25-2025.mdx | 267 ------------- .../docs-release-notes/docs-8-01-2025.mdx | 99 ----- .../docs-release-notes/docs-8-08-2025.mdx | 60 --- .../docs-release-notes/docs-8-14-2025.mdx | 112 ------ .../docs-release-notes/docs-8-21-2025.mdx | 56 --- .../docs-release-notes/docs-9-12-2025.mdx | 94 ----- .../browser-agent-v1.295.mdx | 39 -- .../browser-agent-v1.296.mdx | 34 -- .../browser-agent-v1.297.mdx | 27 -- .../node-api-runtime-1.2.mdx | 10 - .../node-browser-runtime-3.0.mdx | 10 - .../ping-runtime-1.53.mdx | 10 - .../ping-runtime-1.54.mdx | 10 - .../add-on-billing.mdx | 28 -- .../data-ingest-billing.mdx | 354 ------------------ .../fr/docs/cci/getting-started/overview.mdx | 61 --- .../fr/docs/cci/getting-started/setup.mdx | 83 ---- .../via-cloudformation.mdx | 70 ---- .../docs-release-notes/docs-7-25-2025.mdx | 267 ------------- .../docs-release-notes/docs-8-01-2025.mdx | 99 ----- .../docs-release-notes/docs-8-08-2025.mdx | 60 --- .../docs-release-notes/docs-8-14-2025.mdx | 112 ------ .../docs-release-notes/docs-8-21-2025.mdx | 56 --- .../docs-release-notes/docs-9-12-2025.mdx | 94 ----- .../browser-agent-v1.295.mdx | 39 -- .../browser-agent-v1.296.mdx | 34 -- .../browser-agent-v1.297.mdx | 27 -- .../node-api-runtime-1.2.mdx | 10 - .../node-browser-runtime-3.0.mdx | 10 - .../ping-runtime-1.53.mdx | 10 - .../ping-runtime-1.54.mdx | 10 - .../jp/docs/cci/getting-started/setup.mdx | 83 ---- .../cci/{getting-started => }/overview.mdx | 0 .../via-cloudformation.mdx | 70 ---- .../docs-release-notes/docs-7-25-2025.mdx | 267 ------------- .../docs-release-notes/docs-8-08-2025.mdx | 60 --- .../docs-release-notes/docs-8-14-2025.mdx | 112 ------ .../docs-release-notes/docs-9-12-2025.mdx | 94 ----- .../browser-agent-v1.295.mdx | 39 -- .../browser-agent-v1.297.mdx | 27 -- .../node-api-runtime-1.2.mdx | 10 - .../node-browser-runtime-3.0.mdx | 10 - .../ping-runtime-1.54.mdx | 10 - .../add-on-billing.mdx | 28 -- .../data-ingest-billing.mdx | 354 ------------------ .../kr/docs/cci/getting-started/overview.mdx | 61 --- .../kr/docs/cci/getting-started/setup.mdx | 83 ---- .../via-cloudformation.mdx | 70 ---- .../docs-release-notes/docs-7-25-2025.mdx | 267 ------------- .../docs-release-notes/docs-8-01-2025.mdx | 99 ----- .../docs-release-notes/docs-8-08-2025.mdx | 60 --- .../docs-release-notes/docs-8-14-2025.mdx | 112 ------ .../docs-release-notes/docs-8-21-2025.mdx | 56 --- .../docs-release-notes/docs-9-12-2025.mdx | 94 ----- .../browser-agent-v1.295.mdx | 39 -- .../browser-agent-v1.296.mdx | 34 -- .../browser-agent-v1.297.mdx | 27 -- .../node-api-runtime-1.2.mdx | 10 - .../node-browser-runtime-3.0.mdx | 10 - .../ping-runtime-1.53.mdx | 10 - .../ping-runtime-1.54.mdx | 10 - .../add-on-billing.mdx | 28 -- .../data-ingest-billing.mdx | 354 ------------------ .../pt/docs/cci/getting-started/overview.mdx | 61 --- .../pt/docs/cci/getting-started/setup.mdx | 83 ---- .../via-cloudformation.mdx | 70 ---- .../docs-release-notes/docs-7-25-2025.mdx | 267 ------------- .../docs-release-notes/docs-8-01-2025.mdx | 99 ----- .../docs-release-notes/docs-8-08-2025.mdx | 60 --- .../docs-release-notes/docs-8-14-2025.mdx | 112 ------ .../docs-release-notes/docs-8-21-2025.mdx | 56 --- .../docs-release-notes/docs-9-12-2025.mdx | 94 ----- .../browser-agent-v1.295.mdx | 39 -- .../browser-agent-v1.296.mdx | 34 -- .../browser-agent-v1.297.mdx | 27 -- .../node-api-runtime-1.2.mdx | 10 - .../node-browser-runtime-3.0.mdx | 10 - .../ping-runtime-1.53.mdx | 10 - .../ping-runtime-1.54.mdx | 10 - 84 files changed, 6478 deletions(-) delete mode 100644 src/i18n/content/es/docs/accounts/accounts-billing/new-relic-one-pricing-billing/add-on-billing.mdx delete mode 100644 src/i18n/content/es/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing.mdx delete mode 100644 src/i18n/content/es/docs/cci/getting-started/overview.mdx delete mode 100644 src/i18n/content/es/docs/cci/getting-started/setup.mdx delete mode 100644 src/i18n/content/es/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation.mdx delete mode 100644 src/i18n/content/es/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx delete mode 100644 src/i18n/content/es/docs/release-notes/docs-release-notes/docs-8-01-2025.mdx delete mode 100644 src/i18n/content/es/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx delete mode 100644 src/i18n/content/es/docs/release-notes/docs-release-notes/docs-8-14-2025.mdx delete mode 100644 src/i18n/content/es/docs/release-notes/docs-release-notes/docs-8-21-2025.mdx delete mode 100644 src/i18n/content/es/docs/release-notes/docs-release-notes/docs-9-12-2025.mdx delete mode 100644 src/i18n/content/es/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx delete mode 100644 src/i18n/content/es/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.296.mdx delete mode 100644 src/i18n/content/es/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.297.mdx delete mode 100644 src/i18n/content/es/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.mdx delete mode 100644 src/i18n/content/es/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.mdx delete mode 100644 src/i18n/content/es/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.53.mdx delete mode 100644 src/i18n/content/es/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.54.mdx delete mode 100644 src/i18n/content/fr/docs/accounts/accounts-billing/new-relic-one-pricing-billing/add-on-billing.mdx delete mode 100644 src/i18n/content/fr/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing.mdx delete mode 100644 src/i18n/content/fr/docs/cci/getting-started/overview.mdx delete mode 100644 src/i18n/content/fr/docs/cci/getting-started/setup.mdx delete mode 100644 src/i18n/content/fr/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation.mdx delete mode 100644 src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx delete mode 100644 src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-8-01-2025.mdx delete mode 100644 src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx delete mode 100644 src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-8-14-2025.mdx delete mode 100644 src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-8-21-2025.mdx delete mode 100644 src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-9-12-2025.mdx delete mode 100644 src/i18n/content/fr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx delete mode 100644 src/i18n/content/fr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.296.mdx delete mode 100644 src/i18n/content/fr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.297.mdx delete mode 100644 src/i18n/content/fr/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.mdx delete mode 100644 src/i18n/content/fr/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.mdx delete mode 100644 src/i18n/content/fr/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.53.mdx delete mode 100644 src/i18n/content/fr/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.54.mdx delete mode 100644 src/i18n/content/jp/docs/cci/getting-started/setup.mdx rename src/i18n/content/jp/docs/cci/{getting-started => }/overview.mdx (100%) delete mode 100644 src/i18n/content/jp/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation.mdx delete mode 100644 src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx delete mode 100644 src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx delete mode 100644 src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-8-14-2025.mdx delete mode 100644 src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-9-12-2025.mdx delete mode 100644 src/i18n/content/jp/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx delete mode 100644 src/i18n/content/jp/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.297.mdx delete mode 100644 src/i18n/content/jp/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.mdx delete mode 100644 src/i18n/content/jp/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.mdx delete mode 100644 src/i18n/content/jp/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.54.mdx delete mode 100644 src/i18n/content/kr/docs/accounts/accounts-billing/new-relic-one-pricing-billing/add-on-billing.mdx delete mode 100644 src/i18n/content/kr/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing.mdx delete mode 100644 src/i18n/content/kr/docs/cci/getting-started/overview.mdx delete mode 100644 src/i18n/content/kr/docs/cci/getting-started/setup.mdx delete mode 100644 src/i18n/content/kr/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation.mdx delete mode 100644 src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx delete mode 100644 src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-8-01-2025.mdx delete mode 100644 src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx delete mode 100644 src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-8-14-2025.mdx delete mode 100644 src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-8-21-2025.mdx delete mode 100644 src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-9-12-2025.mdx delete mode 100644 src/i18n/content/kr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx delete mode 100644 src/i18n/content/kr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.296.mdx delete mode 100644 src/i18n/content/kr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.297.mdx delete mode 100644 src/i18n/content/kr/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.mdx delete mode 100644 src/i18n/content/kr/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.mdx delete mode 100644 src/i18n/content/kr/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.53.mdx delete mode 100644 src/i18n/content/kr/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.54.mdx delete mode 100644 src/i18n/content/pt/docs/accounts/accounts-billing/new-relic-one-pricing-billing/add-on-billing.mdx delete mode 100644 src/i18n/content/pt/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing.mdx delete mode 100644 src/i18n/content/pt/docs/cci/getting-started/overview.mdx delete mode 100644 src/i18n/content/pt/docs/cci/getting-started/setup.mdx delete mode 100644 src/i18n/content/pt/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation.mdx delete mode 100644 src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx delete mode 100644 src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-8-01-2025.mdx delete mode 100644 src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx delete mode 100644 src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-8-14-2025.mdx delete mode 100644 src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-8-21-2025.mdx delete mode 100644 src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-9-12-2025.mdx delete mode 100644 src/i18n/content/pt/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx delete mode 100644 src/i18n/content/pt/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.296.mdx delete mode 100644 src/i18n/content/pt/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.297.mdx delete mode 100644 src/i18n/content/pt/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.mdx delete mode 100644 src/i18n/content/pt/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.mdx delete mode 100644 src/i18n/content/pt/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.53.mdx delete mode 100644 src/i18n/content/pt/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.54.mdx diff --git a/src/i18n/content/es/docs/accounts/accounts-billing/new-relic-one-pricing-billing/add-on-billing.mdx b/src/i18n/content/es/docs/accounts/accounts-billing/new-relic-one-pricing-billing/add-on-billing.mdx deleted file mode 100644 index 8f3bfc6661b..00000000000 --- a/src/i18n/content/es/docs/accounts/accounts-billing/new-relic-one-pricing-billing/add-on-billing.mdx +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: Facturación adicional (opcional) -tags: - - Accounts - - Accounts and billing - - New Relic pricing and billing -metaDescription: Add-ons are an optional billing factor -freshnessValidatedDate: '2024-10-23T00:00:00.000Z' -translationType: machine ---- - -Además de los factores de facturación principales de GB Ingested y usuario facturable, también puedes usar complementos facturables opcionales para ampliar tu experiencia con New Relic. - -* **Advanced Compute (anteriormente Add-on Compute)**: este complemento se aplica a la facturación basada en el uso de las acciones que ejecuta relacionadas con CodeStream, Live Archives y otras funciones disponibles. Se le mide y factura en función de su uso de [CCU avanzadas](/docs/licenses/license-information/product-definitions/new-relic-one-pricing-definitions/#compute-capacity-unit). - - - Su uso de CodeStream bajo Calcular avanzado generará cargos de CCU, independientemente del tipo de usuario. Esto significa que el usuario básico gratis puede acceder a Calcular característica avanzada y generar cargos por CCU avanzadas. - - -* **EU Data Center for Original Data or Data Plus**: Este complemento se aplica a su opción de datos (Datos Originales o Datos Plus) cuando selecciona la Unión Europea como su región de datos, según disponibilidad. - -* **Extended Retention for Original Data or Data Plus**: este complemento se aplica si excede el tiempo predeterminado durante el cual se conservan sus datos. Esto se aplica a todos sus datos, no solo a los logs, y es una buena opción si necesita realizar muchas consultas pequeñas o consultas sobre grandes volúmenes de datos. - -* **Live Archives**: amplíe la duración del almacenamiento de logs hasta siete años. Live Archives también requiere Calcular avanzado. - -* **New Relic Synthetic Checks**: este complemento se aplica si tus controles exceden la cantidad predeterminada de controles de monitoreo sintético. - -* **Security RX**: Esta característica está incluida con Data Plus, pero el complemento aplica si usas la característica Security RX sin Data Plus. \ No newline at end of file diff --git a/src/i18n/content/es/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing.mdx b/src/i18n/content/es/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing.mdx deleted file mode 100644 index 0871a750e10..00000000000 --- a/src/i18n/content/es/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing.mdx +++ /dev/null @@ -1,354 +0,0 @@ ---- -title: 'Datos: Facturación y reglas' -tags: - - Accounts - - Accounts and billing - - New Relic pricing and billing -metaDescription: 'For New Relic pricing, an explanation of how data ingest is calculated for billing purposes.' -freshnessValidatedDate: '2024-10-23T00:00:00.000Z' -translationType: machine ---- - -Para los precios de New Relic, los datos ingeridos por su organización de New Relic son un factor de facturación. - -## Más información sobre los costos [#costs] - -Si aún no es cliente de New Relic y tiene curiosidad sobre los costos, primero consulte [nuestra página principal de precios](https://newrelic.com/pricing). Si ya es cliente, siga leyendo para conocer detalles sobre la facturación de la ingesta de datos. - -## Ver la ingesta de datos en la UI [#ui] - -Para saber cómo encontrar información de uso y facturación en la UI, consulte [UI de facturación](/docs/accounts/accounts-billing/general-account-settings/introduction-account-settings). - -Para saber cómo ver y administrar su ingesta de datos, consulte [Administrar la ingesta](/docs/data-apis/manage-data/manage-data-coming-new-relic). - -## Opciones de datos: Data Plus y original [#data-prices] - -El precio de su organización por GB de datos ingeridos varía según la opción de datos que tenga su organización: **Data Plus** o nuestra opción **Original Data** . La opción Data Plus ofrece capacidades de datos avanzadas para optimizar el rendimiento, la escala, la seguridad y la gobernanza. Una organización New Relic solo puede tener una opción a la vez. - -Aquí hay una tabla con comparaciones de las dos opciones. Los precios y límites son mensuales y los precios están en USD. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    - Característica/habilidad - - **Original Data** opción - - **Data Plus** opción - - Más detalles característicos -
    - [Ediciones](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing/#editions) - - Todas las ediciones - - Requiere Standard, Pro o Enterprise - - (Anotamos a continuación si una característica es específica de una edición) - -
    - Límite de datos libres - - 100 GB ingeridos - - 100 GB ingeridos - -
    - Precio de los datos
    (más allá del límite libre) -     		- $0,40/GB ingerido - - $0,60/GB ingerido - -
    - Límite gratuito de retención de datos
    ([varía según el tipo de datos](/docs/data-apis/manage-data/manage-data-retention)) -     		- Incumplimiento de al menos 8 días - - 90 días adicionales sobre el incumplimiento - -
    - Precio por cada 30 días adicionales de retención
    (más allá del límite gratuito) -     		- +$0.05/GB - - +$0.05/GB - -
    - Precio adicional para almacenar datos en [el centro de datos de la UE](/docs/accounts/accounts-billing/account-setup/choose-your-data-center)
    -     		- +$0.05/GB - - +$0.05/GB - - Los datos se almacenan en el centro de datos de EE. UU. de forma predeterminada. -
    - [Límite máximo de consultas](/docs/query-your-data/nrql-new-relic-query-language/get-started/rate-limits-nrql-queries/#query-limits) - - Hasta 20 mil millones de puntos de datos por minuto - - Hasta 60 mil millones de puntos de datos por minuto - -
    - [Duración máxima de la consulta](/docs/query-your-data/nrql-new-relic-query-language/get-started/rate-limits-nrql-queries/#query-duration) - - 1 minuto - - Hasta 10 minutos - -
    - Elección del proveedor de la nube - - Proveedor único de nube - - Azure o múltiples proveedores de nube - - Elija su proveedor de nube preferido para su carga de trabajo de observabilidad para alinear su almacenamiento de telemetría con su modelo de despliegue de ingeniería y preferencia de nube. -
    - [Ofuscación de logs](/docs/logs/ui-data/obfuscation-ui/) - - Enmascarar [automáticamente](/docs/logs/get-started/new-relics-log-management-security-privacy/#log-obfuscation) patrones conocidos de tarjetas de crédito y números de Seguro Social en los logs. - - Cree y realice un seguimiento de reglas directamente en laUI y [enmascarar o aplicar hash](/docs/logs/ui-data/obfuscation-ui/) a datos log sensibles. - -
    - [New Relic Gestión de vulnerabilidades](/docs/vulnerability-management/overview)
    (solo usuario de plataforma completa) -     		- +$0.10/GB
    (más allá del límite gratuito) -     		- Standard, Pro, y Enterprise - - Identifique vulnerabilidades y aborde los riesgos en cada etapa del ciclo de vida del software. -
    - Elegibilidad [FedRAMP Moderate](/docs/security/security-privacy/compliance/fedramp-compliant-endpoints) y [HIPAA](/docs/security/security-privacy/compliance/hipaa-readiness-new-relic) - - - - Empresa - - Logre el cumplimiento de la seguridad a través de configuraciones que lo ayuden a cumplir con los requisitos de FedRAMP e HIPAA. -
    - [Exportación de streaming de datos](/docs/apis/nerdgraph/examples/nerdgraph-streaming-export) - - - - Standard, Pro, y Enterprise - - Configure reglas para exportar simultáneamente telemetry data al almacenamiento de AWS o Azure de su elección. Se aplicarán tarifas de exportación adicionales al proveedor de la nube. -
    - [Exportación de datos históricos](/docs/apis/nerdgraph/examples/nerdgraph-historical-data-export) - - - - Standard, Pro, y Enterprise - - Ejecute consultas más amplias sin tiempo de espera para análisis y modelado históricos, almacenamiento a largo plazo e integración con otras plataformas de análisis de datos. -
    - Servicio New Relic nativa de Azure - - - - Standard, Pro, y Enterprise
    ([con algunas limitaciones](#azure-native-data-plus)) -     		-
    - -Para ver una comparación lado a lado de Data Plus y nuestra opción de datos original, consulte [nuestra hoja de datos de Data Plus](https://newrelic.com/resources/datasheets/data-plus). - -¿Interesado en Datos Plus? Consulte [Actualizar a Data Plus](#upgrade-data-plus). - -### Detalles del servicio Azure Native New Relic [#azure-native-data-plus] - -Con el [servicio Azure Native New Relic](/docs/infrastructure/microsoft-azure-integrations/get-started/azure-native), puede recopilar y almacenar sus telemetry data para aplicaciones e infraestructura directamente en Azure. Esta característica está incluida con Data Plus, pero con estas limitaciones: - -* Disponible solo en la región del centro de datos de EE. UU. -* Elegibilidad para FedRAMP Moderado/HIPAA no disponible -* Exportación de datos históricos no disponible - -## Actualice a Datos Plus [#upgrade-data-plus] - -Para actualizar a Data Plus, vaya a la [UI**Data retention** ](/docs/data-apis/manage-data/manage-data-retention/#adjust-retention)en el centro de administración de datos y haga clic en **Upgrade retention**. - -* Nota: Es posible que veas un botón **Edit data retention**, pero es diferente del botón **Upgrade retention**. -* Para ver el botón **Upgrade retention** , debes tener [permisos de facturación](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts/#admin-settings). Si cumple con los requisitos y aún no ve la opción **Upgrade retention** , hable con su representante de cuenta de New Relic. - -## ¿Qué se considera GB ingeridos facturables? [#usage-calculation] - -En el contexto del [plan de precios de New Relic](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing), "datos ingeridos" se refiere a los datos guardados en New Relic por su organización después de que aplicamos varias reglas de recorte y transformación de datos. En otras palabras, no es la cantidad de datos sin procesar enviados a New Relic, sino el tamaño de los datos que realmente terminan almacenándose. - -En general, los datos que generamos para proporcionar nuestra función no cuentan para sus GB ingeridos. Algunos ejemplos de datos de características y relacionados con ellas que no cuentan para GB ingeridos incluyen: - -* [Funcionalidad de alerta básica](/docs/alerts-applied-intelligence/new-relic-alerts/learn-alerts/alerts-concepts-workflow). Por ejemplo, `NrAiIncident`, un evento empleado para generar estas características, no cuenta para los GB ingeridos. -* Datos creados a partir de datos brutos agregados (por ejemplo, [datos de infraestructura agregados](/docs/data-apis/manage-data/manage-data-retention/#infrastructure-data) o [datos métricos dimensionales](/data-apis/manage-data/manage-data-retention/#dimensional-metrics)). -* [Métricas doradas](/docs/apis/nerdgraph/examples/golden-metrics-entities-nerdgraph-api-tutorial) (para más información sobre métricas doradas, consulte nuestras [definiciones de entidad](https://github.com/newrelic/entity-definitions)). -* Check de monitoreo sintético. Para obtener detalles sobre la facturación de Sintético, consulte [Límites y precios de Sintético](/docs/synthetics/synthetic-monitoring/using-monitors/monitor-limits). -* Datos de seguimiento de uso y facturación (por ejemplo, `NrConsumption`). -* Datos relacionados con la administración de la cuenta (por ejemplo, `NrIntegrationError`, `NrAuditEvent`). - -Para comprender su uso, consulte la [UI de uso](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing#usage-ui). - -## Otros detalles de cálculo [#calculation-details] - -* En el contexto de nuestro modelo de precios, un GB se define como mil millones de bytes. -* Los GB ingeridos mensualmente se redondean al número entero más cercano. Por ejemplo, si su organización emplea 100,9 GB durante un mes, eso se cuenta como 100 GB. - -## Edición gratuita [#free-tier-limits] - -Para obtener detalles sobre GB Ingested para nuestra edición gratis, consulte [Edición gratis](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing/#free). - -## Aprende más [#related-docs] - -* Para obtener más información sobre cómo gestionar GB ingeridos, consulte [Gestionar la ingesta de datos](/docs/data-apis/manage-data/manage-data-coming-new-relic). -* Para saber cómo consultar el uso, consulte [consulta y alerta de uso](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts). \ No newline at end of file diff --git a/src/i18n/content/es/docs/cci/getting-started/overview.mdx b/src/i18n/content/es/docs/cci/getting-started/overview.mdx deleted file mode 100644 index e0c53cb34ba..00000000000 --- a/src/i18n/content/es/docs/cci/getting-started/overview.mdx +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: 'Inteligencia para costos en la nube: Tome el control de su gasto cloud' -metaDescription: 'Gain comprehensive visibility and control over AWS cloud costs with CCI, enhancing your FinOps strategy for holistic cost management.' -freshnessValidatedDate: never -translationType: machine ---- - - - Todavía estamos trabajando en esta característica, ¡pero nos encantaría que la probaras! - - Esta característica se proporciona actualmente como parte de un programa de vista previa de conformidad con nuestras [políticas de prelanzamiento](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). - - -Inteligencia para costos en la nube está diseñado para proporcionar visibilidad y gestión de los costos cloud. Inteligencia para costos en la nube monitoreo de IA para cerrar la brecha entre la visibilidad de costos y la observabilidad de la infraestructura, ofreciéndole una visión holística de sus gastos cloud. - -Por ejemplo, a medida que su gran compañía amplía rápidamente el uso de servicios en la nube, el seguimiento y la gestión de los gastos cloud pueden volver cada vez más complejos. Inteligencia para costos en la nube ayuda brindándole información valiosa sobre dónde se asigna su dinero. Esto puede ayudarlo a identificar áreas para posibles ahorros de costos. Al alinear los gastos cloud con el uso real, puede optimizar sus cotizaciones y continuar apoyando iniciativas de crecimiento estratégico. Este enfoque ayuda a garantizar que cada dólar que invierte contribuya al éxito general de su compañía. - - - Actualmente, solo se admiten los costos cloud de AWS. - - -Cloud Cost Intelligence summary page showing total costs, real-time cost estimates, average cost by day, and top 5 cost variance - -## Característica clave - -### Visibilidad integral de costos - -* **Desglose por categoría:** vea los costos cloud segmentados por aplicación, servicio, equipo propietario y región. -* **Análisis de tendencias:** obtenga información valiosa sobre las tendencias de costos mes a mes, los costos promedio y los principales impulsores de costos. - -### Asignación de costos de Kubernetes - -Obtenga visibilidad de los costos relacionados con Kubernetes. Aprovechamos telemetry data de New Relic para desglosar los costos por nombre de aplicación. - -### Estimación de costos en tiempo real - -Inteligencia para costos en la nube aprovecha telemetry data y patrones de costos históricos para proporcionar actualizaciones de costos cada hora, reflejando los cambios dentro de una hora del aprovisionamiento de recursos. Esta integración con sus datos de facturación permite realizar estimaciones de costos basadas en el precio unitario promedio de la semana pasada y New Relic telemetry data para el periodo reciente de 48 horas. Sin esta integración, las estimaciones predeterminadas son tarifas unitarias estándar potencialmente más altas. - -Para obtener estimaciones más precisas, integre la telemetría y mantenga al menos 7 días de datos históricos. Estos datos ayudan a calcular los costos para la misma instancia. A falta de tales datos, las estimaciones vuelven al modelo de precios según demanda, el modelo estándar de pago por uso empleado por los proveedores cloud. - - - **Recopilación de datos entre cuentas**
    Inteligencia para costos en la nube está dirigida al usuario y recopila telemetry data de todas las cuentas asociadas con sus credenciales de usuario New Relic. Esto significa que incluso si usa una sola cuenta New Relic para Inteligencia para costos en la nube, telemetry data de cualquier cuenta New Relic adicional a la que tenga acceso también se recopilarán y serán visibles dentro de esa única cuenta New Relic. Verifique que las licencias de su cuenta de usuario estén en línea con sus políticas internas y permitan el acceso a los datos de las cuentas de New Relic que desea ver. -     - -## Cómo Inteligencia para costos en la nube recupera los costos cloud a través de soluciones de almacenamiento [#fetch-costs] - -Inteligencia para costos en la nube accede automáticamente a sus reportes de uso y costos de AWS (CUR) en su depósito S3 designado una vez que se completan la configuración y la integración. Este proceso comienza con su autorización y la concesión de licencias de acceso. Es importante tener en cuenta que Inteligencia para costos en la nube solo puede generar reportes después de que los datos se exporten a su bucket S3 designado. Cerciorar de que el prefijo de ruta S3 esté configurado en cost-and-usage-reports como se especifica en los [requisitos previos](/docs/cci/getting-started/prerequisites). - -Normalmente, AWS actualiza el CUR tres veces al día e Inteligencia para costos en la nube recupera el CUR de su bucket S3 una vez cada hora luego de la configuración. Su último CUR será visible dentro de Inteligencia para costos en la nube cuando AWS proporcione su actualización e Inteligencia para costos en la nube la recupere poco después. - - - **Privacidad de sus datos**
    CUR son datos sobre su uso de los servicios en la nube y sus costos, que no deben incluir datos personales. Cerciorar de que los datos que envíe estén libres de información de identificación personal o información confidencial antes de agregar el CUR a su depósito S3 y antes de cargarlo en New Relic. La eliminación de datos CUR no es compatible en este momento. Recomendamos no generar el CUR con información personal identificable o información sensible. - - **Retención de datos:** Nuestra política actual de retención de datos es mantener los datos hasta por 5 años. Luego de 2 años, los datos se trasladan a AWS Glacier, una opción de almacenamiento de menor costo con un mayor tiempo de recuperación. - - **Acceso de visualización:** tenga en cuenta que cualquier persona con acceso a la cuenta de New Relic que seleccione durante la instalación podrá ver todos los datos dentro de Inteligencia para costos en la nube. Elija una cuenta con privilegios de acceso adecuados para satisfacer sus requisitos de RBAC y política de acceso. -     - -### Análisis y elaboración de reportes de datos - -Luego de recuperar los datos CUR, Inteligencia para costos en la nube procesa y analiza esta información para presentar información valiosa y procesable en sus dashboards. Puede visualizar las participaciones financieras de su uso cloud con claridad, identificando los impulsores de costos y las áreas potenciales de optimización. \ No newline at end of file diff --git a/src/i18n/content/es/docs/cci/getting-started/setup.mdx b/src/i18n/content/es/docs/cci/getting-started/setup.mdx deleted file mode 100644 index 5b3aacb856a..00000000000 --- a/src/i18n/content/es/docs/cci/getting-started/setup.mdx +++ /dev/null @@ -1,83 +0,0 @@ ---- -title: Configurar CCI -metaDescription: Set up Cloud Cost Intelligence with AWS. Configure IAM roles and data paths for detailed cost analysis and streamlined access in New Relic. -freshnessValidatedDate: never -translationType: machine ---- - - - Todavía estamos trabajando en esta característica, ¡pero nos encantaría que la probaras! - - Esta característica se proporciona actualmente como parte de un programa de vista previa de conformidad con nuestras [políticas de prelanzamiento](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). - - -Aprenda a configurar Inteligencia Artificial en la nube con AWS configurando ajustes de integración esenciales, incluidos los roles de IAM y las rutas de exportación de datos. Esta guía lo guiará a través de los pasos necesarios para permitir el análisis y la gestión de costos detallados dentro de su plataforma New Relic. - -Siga estos pasos para configurar Inteligencia para costos en la nube: - - - - ## Comience a integrar - - Haga clic en **Cloud Cost Intelligence** en el panel izquierdo, luego haga clic en **Add the integration**. Alternativamente, haga clic en **Integrations & Agents** en el panel izquierdo, busque Inteligencia para costos en la nube entre todas las capacidades y luego haga clic en **Cloud Cost Intelligence**. - - - - ## Seleccionar cuenta - - Seleccione la cuenta New Relic que desea emplear para la configuración y haga clic en **Continue**. - - - - ## Proporcionar detalles de conexión - - Ingrese los siguientes detalles necesarios para obtener datos de costos de AWS: - - * **Nombre de la conexión:** se completa de forma predeterminada. Edite si desea un nombre personalizado. - * **ARN del rol de IAM entre cuentas:** el nombre de recurso de Amazon (ARN) para el rol de IAM que Inteligencia para costos en la nube asumirá para acceder a su bucket de S3. Un ARN es un identificador único para varios recursos de AWS, incluidos los roles de IAM. Sigue un formato estándar que incluye el servicio, la región, el ID de la cuenta y los detalles del recurso, como `arn:aws:iam:::role/`. - * **ID externo:** copie el ID externo de su cuenta de New Relic y agréguelo a su configuración de rol de IAM como parte de los requisitos previos. Debe agregarlo a la política de confianza del rol de IAM en su cuenta de AWS. - * **Nombre de exportación de datos:** el nombre del archivo de exportación de datos. Se emplea para construir la ruta al archivo CUR correspondiente. Para un reporte llamado `cci-ingestion-test`, la ruta construida sería `cost-and-usage-reports/cci-ingestion-test/data`. Aquí es donde se almacenan los datos CUR dentro del depósito S3. - * **Nombre del depósito S3:** el nombre exacto de su depósito S3. Cerciorar de que incluya el prefijo `cost-and-usage-reports`. Emplee un depósito S3 ubicado en la región `us-east-2` para lograr un rendimiento óptimo y una mayor rentabilidad. - - - - ## Establecer una política de confianza - - Agregue el usuario global New Relic a la política de confianza de su rol de IAM y proporcione licencias de rol. Esto permite que el usuario global New Relic para Inteligencia para costos en la nube asuma el rol de IAM. - - Para permitir que Inteligencia artificial para costos en la nube acceda a sus recursos AWS, configure una política de confianza en su Consola de administración AWS que permita que el usuario global New Relic, `arn:aws:iam::207192125115:user/cci_global_user`, asuma un rol de IAM. A continuación se muestra un ejemplo de documento de política de confianza: - - ```json - { - "Version": "2012-10-17", - "Statement": [ - { - "Effect": "Allow", - "Principal": { - "AWS": "arn:aws:iam::207192125115:user/cci_global_user" - }, - "Action": "sts:AssumeRole", - "Condition": { - "StringEquals": { - "sts:ExternalId": "" - } - } - } - ] - } - ``` - - - * El `sts:ExternalId` es un componente crítico para la seguridad. Configúrelo en el ID externo que copió en el paso anterior. Esta identificación garantiza que el rol se asuma solo en el contexto previsto por New Relic, lo que mejora la seguridad de su integración. - * Si sus recursos están en regiones de AWS donde el Servicio de token de seguridad (STS) no está activo de forma predeterminada (por ejemplo, `ap-east-1`, `eu-south-1`), active STS para esas regiones. - - - - - ## Conexión de prueba - - Por último, inicie una prueba para verificar que la conexión a su entorno de AWS sea exitosa. - - - -Luego de una configuración exitosa, pueden pasar algunas horas hasta que los datos comiencen a aparecer en la New Relic UI, especialmente durante la configuración inicial. \ No newline at end of file diff --git a/src/i18n/content/es/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation.mdx b/src/i18n/content/es/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation.mdx deleted file mode 100644 index e9317c49c4c..00000000000 --- a/src/i18n/content/es/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation.mdx +++ /dev/null @@ -1,70 +0,0 @@ ---- -title: Integración a través de CloudFormation y CloudWatch Metric Streams -tags: - - Integration via CloudFormation - - AWS metric integration - - Amazon integrations - - AWS integrations - - Integration with CloudWatch Metric Streams via CloudFormation -metaDescription: Integrate New Relic with AWS services using CloudFormation templates to automate the setup of CloudWatch Metric Streams for metrics ingestion. -freshnessValidatedDate: never -translationType: machine ---- - -Para una integración perfecta de su cuenta de AWS con New Relic, este es el proceso de integración más recomendado. Puede emplear API Polling para servicios no compatibles con CloudWatch Metric Streams. - -## Requisitos previos [#prerequisites] - -Antes de comenzar a integrar su cuenta de AWS con New Relic, cerciorar de cumplir con los siguientes requisitos previos: - -* **Una [clave de licencia](https://one.newrelic.com/api-keys)de New Relic**: necesitará una clave de licencia para conectar sus servicios de AWS a su cuenta de New Relic. -* **[Licencias](https://docs.aws.amazon.com/ARG/latest/userguide/gettingstarted-prereqs-permissions.html)** para implementar nuevos recursos AWS y **[roles de IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html)**: necesitará esta licencia para su cuenta AWS. -* **[Licencias](/docs/accounts/accounts-billing/new-relic-one-user-management/user-permissions/#infrastructure)** para la integración en la nube: Necesitarás estas licencias para tu cuenta New Relic. - -## Pasos de integración [#integration-steps] - -Para integrar su cuenta de AWS con New Relic mediante CloudFormation y CloudWatch Metric Streams, siga estos pasos: - -1. Navegar a [**Infrastructure > AWS**](https://one.newrelic.com/infra/infrastructure/cloud-aws). - -2. Seleccione la cuenta correcta. - -3. Haga clic en **Set up integration**. - -4. Siga las instrucciones en cada pantalla y complete los campos que correspondan. Para esta integración, elija las siguientes opciones en las pantallas dadas: - - 1. **Choose Data type(s)**: Metrics - 2. **Choose a setup method**: Automate AWS with CloudFormation (Recommended) - 3. **Choose a metrics integration type**: CloudWatch Metric Stream (Recommended) - -5. Si está empleando alguno de los servicios que no son compatibles con CloudWatch Metric Streams, en la página **Choose a metrics integration type**, seleccione **Yes** en el tercer paso para el sondeo API y continúe. - - AWS Integration with CWMS and API Polling - -
    - Integración CWMS de servicios de AWS con sondeo API seleccionado para servicios no soportados. -
    - - Realice la configuración necesaria según las instrucciones de la página **Enable API Polling (optional)** y continúe. - -6. Auto-discovery Detecta y visualiza automáticamente las relaciones entre sus entidades AWS en los mapas y aprovecha algunas otras flexibilidades. Para obtener más detalles, consulte [Descubrimiento automático de entidades AWS ](/docs/infrastructure/amazon-integrations/connect/set-up-auto-discovery-of-aws-entities/). Si desea esta función, habilítela en la página **Enable Auto Discovery (optional)** y continúe. - -7. Haga clic en **Launch your CloudFormation in AWS**. La plantilla de CloudFormation se abre en su consola AWS con el parámetro configurado según sus selecciones en New Relic, por lo que no es necesaria ninguna edición adicional a menos que desee realizar cambios. - -8. Pegue su clave de licencia en su consola de AWS. - -9. Para implementar la stack Cloudformation, en la consola AWS, seleccione **Create stack**. La creación de los recursos stack puede tardar varios minutos y puede generar múltiples pilas, dependiendo de cómo configure el reenvío de métrica. Si falla la creación stack, consulte el [procedimiento de resolución de problemas](https://docs.newrelic.com/docs/logs/troubleshooting/aws-log-integration-issues/stack-creation-fails/). - -10. Luego de crear una stack exitosa, cambie a la plataforma New Relic y continúe con la integración guiada hasta que vea sus datos AWS en New Relic. - -## Temas relacionados [#related-topics] - - - - Aprenda a recopilar datos de varias cuentas de AWS. - - - - Explore y emplee métrica de CloudWatch Metric Streams. - - \ No newline at end of file diff --git a/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx b/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx deleted file mode 100644 index 0b18e090f5b..00000000000 --- a/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx +++ /dev/null @@ -1,267 +0,0 @@ ---- -subject: Docs -releaseDate: '2025-07-25' -version: 'June 13 - July 24, 2025' -translationType: machine ---- - -### Nuevos documentos - -* Se agregó una nueva característica sobre [Cómo depurar problemas del agente New Relic Browser ](/docs/browser/new-relic-browser/troubleshooting/how-to-debug-browser-agent/), que incluye logging detallado, monitoreo de solicitudes de red e inspección de eventos para una resolución mejorada de problemas en las versiones del agente 1.285.0 y superiores. -* Se agregó compatibilidad con [Azure Functions](/docs/serverless-function-monitoring/azure-function-monitoring/introduction-azure-monitoring/) para la supervisión de funciones `python` y `.node.js`. -* Se agregó [un optimizador de costos](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/compute-optimizer/) para obtener información procesable valiosa para mejorar la eficiencia del cálculo, con una función para identificar ineficiencias, brindar recomendaciones de optimización y estimar ahorros de CCU en la plataforma New Relic. -* Se agregó [Inteligencia para costos en la nube](/docs/cci/getting-started/overview), que ofrece herramientas para la visibilidad y la gestión de los costos cloud, incluidas características como desgloses completos de costos, asignación de costos Kubernetes, estimación de costos en tiempo real y recopilación de datos entre cuentas, y que actualmente solo admite los costos AWS cloud. -* Se agregó [la observabilidad OpenTelemetry para Kubernetes con la integración independiente del proveedor de la característica New Relic](/docs/kubernetes-pixie/k8s-otel/intro/) para un monitoreo continuo del clúster a través del diagrama Helm, mejorando las señales de telemetría para métricas, eventos y logs transmitidos a las herramientas y el tablero de New Relic. -* Se agregó [limitación y resolución de problemas para la integración Windows](/docs/kubernetes-pixie/kubernetes-integration/troubleshooting/troubleshooting-windows/) -* Added AWS integration via [CloudFormation and CloudWatch Metric Streams](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms/), supporting API Polling for unsupported services. -* Se agregó [una etiqueta mejorada para la base de datos de entidad New Relic ](/docs/infrastructure/host-integrations/db-entity-tags/)para la base de datos de entidad monitoreada mediante integración en el host para MySQL y MS SQL Server, enriqueciendo metadatos, información valiosa y organización en New Relic sin afectar la facturación o la telemetría existente. - -### Cambios importantes - -* Se agregaron funciones no agregadoras a [las referenciasNRQL ](/docs/nrql/nrql-syntax-clauses-functions/#non-aggregator-functions/). -* Se actualizaron los [requisitos del agenteRuby y el marco compatible](/docs/apm/agents/ruby-agent/getting-started/ruby-agent-requirements-supported-frameworks/). -* Se agregaron logs como evento personalizado New Relic a los [logs OpenTelemetry en el documento New Relic](/docs/opentelemetry/best-practices/opentelemetry-best-practices-logs/#custom-events). -* Se actualizaron los tiempos de ejecución compatibles con Linux, Windows y funciones en contenedores en el documento [Compatibilidad y requisitos para funciones instrumentadas Azure Functions](/docs/serverless-function-monitoring/azure-function-monitoring/compatibility-requirement-azure-monitoring/#supported-runtimes). -* Se actualizaron los datos métricos de [Confluent integración en la nube](/docs/message-queues-streaming/installation/confluent-cloud-integration/#metrics). -* Se eliminó GCP Cloud Run de [la configuración del agente Node.js.](/docs/apm/agents/nodejs-agent/installation-configuration/nodejs-agent-configuration/) -* Se actualizó [la compatibilidad y los requisitos para el monitoreo de IA](/docs/ai-monitoring/compatibility-requirements-ai-monitoring/) para incluir bibliotecas adicionales compatibles con el agente .NET. -* Se agregó New Relic telemetría dualstack extremo al [tráfico de redNew Relic ](/docs/new-relic-solutions/get-started/networks/#new-relic-endpoints). -* Se agregó `GcpHttpExternalRegionalLoadBalancerSample` a la [integración de monitoreo de Google Cloud Load Balancing](/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-load-balancing-monitoring-integration/). -* Se agregó el procedimiento de inicio de OpenShift sobre cómo [instalar el documento del administrador de trabajos Sintéticos](/docs/synthetics/synthetic-monitoring/private-locations/install-job-manager/#-install). -* Se actualizó la [versión 12 del agente Node.js.](/docs/apm/agents/nodejs-agent/installation-configuration/update-nodejs-agent/) -* Added seamless integration for [AWS with New Relic utilizing CloudFormation and CloudWatch Metric Streams](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms/), including support for API polling. - -### Cambios menores - -* Se agregó `Transaction` como periodo de retención para [la traza de la transacción](/docs/data-apis/manage-data/manage-data-retention/#retention-periods/). -* Se agregó `Destination` como una nueva categoría a [Reglas y límites de alerta](/docs/alerts/admin/rules-limits-alerts/). -* Se agregó una llamada en [el documento Introducción al servicio New Relic nativo de Azure](/docs/infrastructure/microsoft-azure-integrations/get-started/azure-native/) para garantizar que las configuraciones de diagnóstico en los recursos de Azure estén configuradas correctamente o deshabilitar el reenvío a través del servicio New Relic nativo de Azure para evitar que los datos se envíen a la plataforma New Relic. -* Se actualizó la última biblioteca compatible con [el agente .NET](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements/). -* Se agregó una llamada en el documento [de notas de la versión del agente de iOS](/docs/release-notes/mobile-release-notes/ios-release-notes/index/) para anunciar que, a partir de la versión 7.5.4 del SDK de iOS, Un cambio ahora da como resultado el reporte de eventos de excepción manejados que anteriormente se suprimieron. -* Se actualizaron los requisitos para las relaciones servicio-contenedor para especificar el atributo de recurso para entornos Kubernetes y `container.id` para entornos que no son-Kubernetes, lo que garantiza una configuración de telemetría adecuada para [los recursos de OpenTelemetry en New Relic](/docs/opentelemetry/best-practices/opentelemetry-best-practices-resources/). -* Se agregó compatibilidad CLI para la instalación de versiones [específicas del agente de infraestructura](/docs/infrastructure/infrastructure-agent/new-relic-guided-install-overview/#install-specific-versions), lo que permite una implementación consistente y compatibilidad del sistema; especifique la versión usando `@X.XX.X` en el nombre de la receta. -* Se agregó un llamado para enfatizar los requisitos de acceso de roles para usar las funciones **Manage Account Cardinality**, **Manage Metric Cardinality** y **Create Pruning Rules** en la UI; cerciorar de que las licencias estén configuradas en [Administración de cardinalidad](/docs/data-apis/ingest-apis/metric-api/cardinality-management/#attributes-table). -* Se actualizó la [compatibilidad y los requisitos para el agente Node.js](/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent/) a `v12.23.0`. -* Se agregaron las licencias mínimas requeridas para configurar un [Elasticsearch](/docs/infrastructure/host-integrations/host-integrations-list/elasticsearch/elasticsearch-integration). -* Se actualizó el uso máximo aceptable del atributo `FACET` de los límites de 5000 a 20000 valores para [la sintaxis de alerta NRQL](/docs/alerts/create-alert/create-alert-condition/create-nrql-alert-conditions/). - -### Notas de la versión - -* Se anunció el 7 de enero de 2026 como la fecha de finalización de la vida útil de las [reglas de lanzamiento dirigidas a eventos de infraestructura en `SystemSample`, `ProcessSample`, `NetworkSample` y `StorageSample`](/eol/2025/05/drop-rule-filter/) - -* Con vigencia inmediata, el fin de la vida útil de [FACET en messageId y timestamp en condición de alerta](/eol/2025/07/deprecating-alert-conditions/). - -* Se anunció el 28 de octubre de 2025 como la fecha de finalización de la vida útil de [Atención requerida](/eol/2025/07/upcoming-eols/). - -* Consulta nuestras publicaciones de Novedades: - - * [Enviar notificación directamente a Microsoft Teams](/whats-new/2025/03/whats-new-03-13-microsoft-teams-integration/) - * [¡New Relic Compute Optimizer ya está disponible de forma general!](/whats-new/2025/06/whats-new-06-25-compute-optimizer/) - * [Logs de consultas de cuentas cruzadas en el Explorador de consultas unificado](/whats-new/2025/07/whats-new-07-01-logs-uqe-cross-account-query/) - * [¡El monitoreo de Kubernetes con OpenTelemetry ya está disponible de manera general!](/whats-new/2025/07/whats-new-7-01-k8s-otel-monitoring/) - * [La monitorización de nodos Windows para Kubernetes ahora está en versión preliminar pública](/whats-new/2025/07/whats-new-07-04-k8s-windows-nodes-preview/) - * [Identificar problemas de rendimiento: filtrado avanzado para páginas vistas y Core Web Vitals](/whats-new/2025/07/whats-new-07-09-browser-monitoring/) - * [Ahora puedes ordenar por errores más recientes](/whats-new/2025/07/whats-new-7-08-ei-sort-by-newest/) - * [Tus datos del navegador, tus términos: Nuevas opciones de control](/whats-new/2025/07/whats-new-07-10-browser-monitoring/) - * [Análisis de consulta profunda para base de datos ahora disponible de forma general](/whats-new/2025/07/whats-new-07-24-db-query-performance-monitoring/) - * [Las predicciones NRQL y las alertas predictivas ya están disponibles de forma general](/whats-new/2025/07/whats-new-7-22-predictive-analytics/) - * [Convergencia APM + OpenTelemetry GA](/whats-new/2025/07/whats-new-07-21-apm-otel/) - * [La integración de Agentic para GitHub Copilot y ServiceNow ya está disponible de forma general](/whats-new/2025/07/whats-new-7-15-agentic-ai-integrations/) - -* Mantener actualizado con nuestros últimos lanzamientos: - - * [Tiempo de ejecución de la API de Node v1.2.119](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.119/) - * Se corrigieron problemas de vulnerabilidades. - - * [Tiempo de ejecución de ping v1.51.0](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.119/) - - * Se corrigieron las vulnerabilidades del núcleo logback durante el tiempo de ejecución de ping. - * Se corrigieron las vulnerabilidades del servidor Jetty durante el tiempo de ejecución de ping. - * Se corrigieron las vulnerabilidades de Ubuntu para el tiempo de ejecución de ping. - - * [Agente de Browser v1.292.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.292.0/) - - * Actualizar la definición `BrowserInteraction` y `previousUrl`. - * Se agregó evento de inspección adicional. - * Valor fijo `finished` API `timeSinceLoad`. - - * [Integración Kubernetes v3.42.1](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-42-1/) - * Se corrigieron los ajustes internos backend y relacionados con CI para compatibilidad futura con plataformas. - - * [Administrador de trabajos v444](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-444/) - * Se solucionó un problema que impedía que ciertos clientes vieran resultados para algunos monitores con tiempos de ejecución más prolongados. - - * [Agente de Python v10.14.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-101400/) - - * Se agregó soporte para `Azure Function Apps`. - * Se corrigieron los archivos `pb2` para habilitar el soporte `protobuf v6`. - - * [Agente Android v7.6.7](/docs/release-notes/mobile-release-notes/android-release-notes/android-767/) - - * Rendimiento mejorado para resolver ANR al informar logs. - * Se solucionó un problema para continuar informando logs al finalizar la aplicación. - * Se resolvió un problema con la aplicación de monitoreo de estado y transmisión de datos. - * Se mejoraron algunas complicaciones al activar el modo estricto. - - * [Integración Kubernetes v3.42.2](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-42-2/) - - * Actualizado `golang.org/x/crypto` a `v0.39.0`. - * Actualizado `go` a `v1.24.4`. - - * [Agente .NET v10.42.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-42-0/) - - * Se agregó soporte para Azure Service Bus. - * Se corrigieron errores de compilación del generador de perfiles con la última versión de VS. - - * [agente PHP v11.10.0.24](/docs/release-notes/agent-release-notes/php-release-notes/php-agent-11-10-0-24/) - - * Se agregó API de tiempo de ejecución de Composer para usarla de manera predeterminada para detectar paquetes empleados por la aplicación PHP. - * Se solucionó el comportamiento indefinido cuando se ejecuta la API de tiempo de ejecución de Composer. - - * [Tiempo de ejecución del navegador de nodos v3.0.32](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.32/) - * Opciones de creación de Chrome actualizadas para Chrome 131. - - * [Aplicación móvil para iOS v6.9.8](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6098/) - * Se mejoró la función Ask AI con una conexión de socket más robusta y confiable, cerciorando una experiencia perfecta. - - * [Aplicación móvil para Android v5.29.7](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5297/) - * Se mejoró la función Ask AI con una conexión de socket más robusta y confiable, cerciorando una experiencia perfecta. - - * [Agente de Node.js v12.22.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-22-0/) - - * Se agregó soporte para transmisión `openai` v5. - * Se agregó soporte para la API `openai.responses.create`. - * Se corrigió el log de error para el encabezado de estado de seguimiento no definido. - - * [agente de infraestructura v1.65.0](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1650/) - - * Dependencia actualizada `newrelic/nri-winservices` a `v1.2.0` - * Etiqueta de Docker Alpine actualizada a `v3.22` - - * [agente de infraestructura v1.65.1](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1651/) - * actualizar la dependencia `newrelic/nri-flex` a `v1.16.6` - - * [Agente de Browser v1.292.1](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.292.1/) - * Se corrigió la precedencia de la condición de carrera del atributo personalizado. - - * [NRDOT v1.2.0](/docs/release-notes/nrdot-release-notes/nrdot-2025-06-26/) - * Se elevó el núcleo beta de OTEL a `v0.128.0` - - * [Agente de medios para HTML5.JS v3.0.0](/docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-25-04-15/) - - * Se introdujo un nuevo tipo de evento. - * El tipo de evento `PageAction` quedó obsoleto. - - * [Agente de medios para HTML5.JS v3.1.1](/docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-25-06-15/) - - * Se habilitó la publicación npm para el paquete, lo que garantiza una fácil accesibilidad y distribución. - * Se agregaron las compilaciones `cjs`, `esm` y `umd` a la carpeta `dist`, lo que garantiza la compatibilidad con los formatos de módulos CommonJS, ES y UMD. - - * [Agente multimedia para Roku v4.0.0](/docs/release-notes/streaming-others-release-notes/streaming-others-agent-25-02-25/) - - * Se introdujo un nuevo tipo de evento. - * El tipo de evento `RokuVideo` quedó obsoleto. - * El tipo de evento `RokuSystem` quedó obsoleto. - - * [Agente multimedia para Roku v4.0.1](/docs/release-notes/streaming-others-release-notes/streaming-others-agent-25-04-22/) - * El nombre `errorName` renombrado con `errorMessage` como `errorName` quedó obsoleto. - - * [Administrador de trabajos v447](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-447/) - * Actualización de la imagen base fija de `ubuntu 22.04` a `ubuntu 24.4` - - * [Tiempo de ejecución de ping v1.52.0](/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.52.0/) - * Actualización de imagen base mejorada de `ubuntu 22.04` a `ubuntu 24.04` - - * [Integración Kubernetes v3.43.0](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-43-0/) - * Se agregó soporte para la monitorización de nodos Windows en el clúster de Kubernetes. - - * [Aplicación móvil para Android v5.29.8](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5298/) - * Se corrigió un error y se mejoró UI para una experiencia más fluida. - - * [Agente de Node.js v12.23.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-23-0/) - - * Se agregó la capacidad de informar solo sobre los tramos de entrada y salida. - * Se agregó compatibilidad con Node.js 24. - * Reporte de compatibilidad actualizado. - - * [Tiempo de ejecución de la API de Node v1.2.120](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.120/) - * Se corrigieron las vulnerabilidades de `CVE-2024-39249` - - * [Aplicación móvil para iOS v6.9.9](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6099/) - * Se mejoró la característica Ask AI con símbolo dinámico. - - * [Agente de Browser v1.293.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.293.0/) - - * Se agregó mensaje interno **de tareas largas**. - * Se solucionó el problema que impedía deshabilitar el rastreo distribuido. - - * [Tiempo de ejecución del navegador de nodos v3.0.35](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.35/) - * Imagen base mejorada - - * [Agente de Java v8.22.0](/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8220/) - - * Metadatos vinculados para servicios de aplicaciones Azure. - * Se eliminó la instrumentación `MonoFlatMapMain`. - - * [Agente de Node.js v12.24.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-24-0/) - - * Se implementó un límite de tamaño de valor de atributo configurable - * Reporte de compatibilidad actualizado. - - * [Integración Kubernetes v3.43.2](docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-43-2/) - * Actualizar la versión del gráfico kube-state-métrica de `5.12.1` a `5.30.1` - - * [Agente iOS v7.5.7](/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-757/) - * Se solucionó un problema que podía provocar que rastreo distribuido no tuviera toda la información de cuenta requerida al inicio de una sesión. - - * [Aplicación móvil para Android v5.29.9](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5299/) - * Se mejoró la retroalimentación con representación de UI dinámica. - - * [Aplicación móvil para Android v5.30.0](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-53000/) - * Se corrigieron errores y se actualizaron las banderas de Teams GA para una mejor experiencia de usuario. - - * [Go agente v3.40.1](/docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-40-1/) - - * Utilización revertida. Vuelva a la versión v3.39.0 debido a un error de bloqueo. - * Se eliminaron las pruebas awssupport\_test.go que agregaron dependencia directa al módulo go - - * [Agente de Flutter v1.1.12](/docs/release-notes/mobile-release-notes/flutter-release-notes/flutter-agent-1112/) - - * Se mejoró el agente nativo de Android actualizado a la versión 7.6.7 - * Se mejoró el agente nativo de iOS actualizado a la versión 7.5.6 - - * [Agente de Node.js v13.0.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-0-0/) - - * Se eliminó el soporte para Node.js 18 - * Se actualizó la versión mínima compatible para `fastify` a 3.0.0. `pino` a 8.0.0 y `koa-router` a 12.0.0 - - * [Agente de Browser v1.294.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.294.0/) - * Reporte corregido: URL anterior vacía como indefinida - - * [agente de infraestructura v1.65.4](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1654/) - * Se actualizó la dependencia `newrelic/nri-prometheus` a v2.26.2 - - * [Aplicación móvil para iOS v6.9.10](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6100/) - * Se mejoró la retroalimentación con representación de UI dinámica. - - * [Agente NDK Android v1.1.3](/docs/release-notes/mobile-release-notes/android-release-notes/android-ndk-113/) - * Se agregó soporte para tamaño de página de 16 KB - - * [agente de infraestructura v1.65.3](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1653/) - - * Se modificó el identificador del proceso de Windows. - * Subió `nri-docker` a `v2.5.1`, `nri-prometheus` a `v2.26.1` - - * [Agente .NET v10.43.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-43-0/) - * Se agregó compatibilidad con temas para Azure Service Bus - - * [Agente de Node.js v12.25.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-25-0/) - * Se corrigió el instrumento AWS Bedrock Converse API - - * [Agente de Node.js v12.24.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-24-0/) - - * Se implementó un límite de tamaño de valor de atributo configurable - * Reporte de compatibilidad actualizado - - * [CLI de diagnóstico (nrdiag) v3.4.0](/docs/release-notes/diagnostics-release-notes/diagnostics-cli-release-notes/diagnostics-cli-340/) - * Se resolvieron los errores relacionados con GLIBC, como `/lib64/libc.so.6: version 'GLIBC_2.34'` no encontrado. \ No newline at end of file diff --git a/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-8-01-2025.mdx b/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-8-01-2025.mdx deleted file mode 100644 index 168add677e4..00000000000 --- a/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-8-01-2025.mdx +++ /dev/null @@ -1,99 +0,0 @@ ---- -subject: Docs -releaseDate: '2025-08-01' -version: 'July 25 - August 01, 2025' -translationType: machine ---- - -### Nuevos documentos - -* Se agregó [documentación de Cotizaciones de Calcular](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/compute-budgets/overview) para brindarle un mecanismo para monitorear y alertar sobre el uso de su Unidad de Consumo de Calcular (CCU). - -### Cambios importantes - -* [Compatibilidad y requisitos](/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent) actualizados para el agente Node.js. - -* [Compatibilidad y requisitos actualizados para Alpine Linux](/docs/apm/agents/php-agent/getting-started/php-agent-compatibility-requirements) para el agente PHP. - -* Se actualizaron los requisitos específicos del agente para [el control de tuberías](/docs/new-relic-control/pipeline-control/modify-agent-configuration). - -* Se actualizó el JFR relacionado con los requisitos de configuración para [el agente de Java](/docs/apm/agents/java-agent/configuration/java-agent-configuration-config-file#jfr-harvest-interval). - -* Se actualizó la información de precios y facturación de New Relic en: - - * [Datos: Facturación y reglas](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing) - * [Consultas y alertas relacionadas con el uso](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts) - * [Plan de uso de New Relic](/docs/licenses/license-information/usage-plans/new-relic-usage-plan) - -### Cambios menores - -* Se aclaró el lenguaje en el agente .NET para capturar el parámetro SQL en el documento [de compatibilidad del agente y requisitos de .NET](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements). -* Se perfeccionó el lenguaje en [Oracle base de datos monitoreo integración](/docs/infrastructure/host-integrations/host-integrations-list/oracle-database-monitoring-integration). - -### Notas de la versión - -* Consulta nuestras publicaciones de Novedades: - - * [Calcular Cotizaciones ahora disponibles de forma general](/whats-new/2025/07/whats-new-7-30-compute-budgets). - * [Mejorar la experiencia del usuario: aprovechar Session Replay para optimizar los elementos esenciales de la web](/whats-new/2025/07/whats-new-7-31-augmenting-user-experiences-browser). - -* Mantener actualizado con nuestros últimos lanzamientos: - - * [AgenteAndroid v7.6.8](/docs/release-notes/mobile-release-notes/android-release-notes/android-768): - - * Se solucionó un problema en el que el rastreo de stack para errores de Unity no se mostraba correctamente. - * Se solucionó un problema que impedía que se registrara el resumen métrico cuando la aplicación volvía al primer plano luego de su lanzamiento inicial. - * Se solucionó un problema por el cual un JSON no válido en las entradas de registro podía provocar errores. - - * [CLI de diagnóstico (nrdiag) v3.4.0](/docs/release-notes/diagnostics-release-notes/diagnostics-cli-release-notes/diagnostics-cli-341): - * Se agregó `K8s/AgentControl/agent-control-install-job-logs` para recopilar los logs generados por la instalación del control del agente. - - * [Administrador de trabajos v451](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-451): - - * Se corrigieron vulnerabilidades relacionadas con `common-lang3` Java y Ubuntu para abordar problemas de seguridad en SJM. - * Se implementaron cambios en la migración de la cola del procesador relacionados con la migración de nuestra arquitectura de servicio interna. - * Se solucionó un problema para incluir detalles completos de la excepción para proporcionar un mejor contexto para la resolución de problemas en los logs de SJM. - - * [Aplicación móvil para Android v5.30.1](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5301): - * Se mejoró la experiencia de inicio de sesión. - - * [Aplicación móvil para iOS v7.5.8](/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-758): - - * Construí el agente usando Xcode 16.4. - * Se solucionó un problema que podía provocar que rastreo distribuido no tuviera toda la información de cuenta requerida al inicio de una sesión. - * Se solucionó un problema que podía provocar un bloqueo al iniciar el agente. - - * [Tiempo de ejecución de la API de nodo](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.122): - * Se corrigieron las vulnerabilidades de datos de formulario y las vulnerabilidades subyacentes de Ubuntu para abordar vulnerabilidades de seguridad en los tiempos de ejecución de Node API. - - * [Node browser runtime](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.39): - * Se corrigieron las vulnerabilidades de datos de formulario y las vulnerabilidades subyacentes de Ubuntu para abordar vulnerabilidades de seguridad en los tiempos de ejecución de Node Browser. - - * [Tiempo de ejecución de ping](/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.53.0): - * Se corrigieron vulnerabilidades relacionadas con `common-lang3` Java y Ubuntu para abordar problemas de seguridad en el tiempo de ejecución de Ping. - - * [Agente de Python v10.15.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-101500): - - * Se agregó soporte para [`oracledb`](https://pypi.org/project/oracledb/) - * Se corrigió un error en la instrumentación `MessageBroker` donde los métodos serializar buscaban el atributo `destination_name` en `MessageTransaction` y no existía. - * Se solucionó el problema de metadatos de utilización de AWS al ejecutar AWS y K8s juntos. - - * [AgenteRuby v9.20.0](/docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-20-0): - - * Se agregó soporte para registrar el ID de Docker cuando se ejecuta en el entorno AWS ECS Fargate. - * Se agregó un nuevo método auxiliar para simplificar la comparación de versiones. - * Se agregó el atributo `code.stacktrace` a los intervalos de almacenamiento de datos cuando la duración excede el umbral configurado. - * Se corrigieron los `Brewfile` enlaces de origen. - * Se corrigió un error que ocurre cuando se usa `HTTPX 1.5.0` para almacenar la respuesta. - * Se mejoró la información registrada en el nivel de depuración por el agente cuando el agente lee una fuente de configuración. - - * [Agente de Unity v1.4.8](/docs/release-notes/mobile-release-notes/unity-release-notes/unity-agent-148): - - * Se actualizó el agente nativo de Android a v7.6.7. - * Se actualizó el agente nativo de iOS a v7.5.6. - - * [Agente de Unity v1.4.9](/docs/release-notes/mobile-release-notes/unity-release-notes/unity-agent-149): - - * Se actualizó el agente nativo de Android a v7.6.8. - * Se actualizó el agente nativo de iOS a v7.5.8. - * Se solucionó el problema de rastreo de stack de excepciones de Unity cuando se emplean espacios de nombres. \ No newline at end of file diff --git a/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx b/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx deleted file mode 100644 index 01456861c55..00000000000 --- a/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx +++ /dev/null @@ -1,60 +0,0 @@ ---- -subject: Docs -releaseDate: '2025-08-08' -version: 'August 01 - August 07, 2025' -translationType: machine ---- - -### Nuevos documentos - -* Se agregó [el tutorial de NerdGraph: Crear un rol personalizado para Teams](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/compute-budgets/overview) para guiarlo en el uso de la API de NerdGraph de New Relic para crear y gestionar roles personalizados para Teams. - -### Cambios menores - -* Se modificó el [umbral de alerta de evento por condición](/docs/alerts/admin/rules-limits-alerts) a 1k por minuto. -* Se actualizaron las últimas [versiones y requisitos compatibles del agente .Net](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements) verificados. -* Se actualizó la información de versión y soporte de versión acerca del agente de servicio para [VMware Tanzu](/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-service-broker-integration). -* Se actualizó la información de soporte de la versión sobre el paquete de compilación de integración NGINX de New Relic para [VMware Tanzu](/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-nginx-buildpack-integration). -* Se actualizó la información de versión y soporte de versiones de New Relic Nozzle para [VMware Tanzu](/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-firehose-nozzle-integration/#product-snapshot). - -### Notas de la versión - -* Consulta nuestras publicaciones de Novedades: - - * [Errors Inbox ahora está integrada dentro de carga de trabajo](/whats-new/2025/08/whats-new-08-06-workloads-errors-inbox). - -* Mantener actualizado con nuestros últimos lanzamientos: - - * [Administrador de trabajos v452](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-452): - * Se agregaron mejoras internas para el manejo de excepciones al procesar mensajes de la cola. - - * [IntegraciónKubernetes v3.43.3](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-43-3): - * Se agregó un gráfico Helm para implementar la solución de monitoreo Kubernetes New Relic. - - * [Control de tuberías Gateway v1.1.0](/docs/release-notes/pipeline-control-gateway-release-notes/pipeline-control-gateway-25-08-05): - - * Se implementó una nueva funcionalidad para descartar selectivamente datos y atributos de `SqlTrace` y `TransactionTrace` incluso usando reglas de descartado. - - * Se abordaron vulnerabilidades en el paquete `golang.org/x/net`, incluido un problema de script entre sitios y una omisión de proxy HTTP relacionada con los ID de zona IPv6. - - * Se actualizó a Go `1.24` y las siguientes dependencias se actualizan para mejorar la seguridad e incorporar correcciones recientes: - - * `golang.org/x/net to v0.38.0` - * `golang.org/x/sys to v0.31.0` - * `golang.org/x/text to v0.23.0` - - * [Aplicación móvil para iOS v6.9.11](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6101): - * Se redujo el flujo de inicio de sesión en dos pasos al almacenar el dominio de autenticación de un usuario y redirigirlo directamente a su página de inicio de sesión. - - * [Agente deFlutter v1.1.13](/docs/release-notes/mobile-release-notes/flutter-release-notes/flutter-agent-1113): - - * Agente nativo Android mejorado actualizado a la versión 7.6.8 - * Agente nativo de iOS mejorado actualizado a la versión 7.5.8 - - * [Agente .NET MAUI v1.1.11](/docs/release-notes/mobile-release-notes/net-maui-release-notes/net-maui-agent-1111) - - * Agente nativo Android mejorado actualizado a la versión 7.6.8 - * Agente nativo de iOS mejorado actualizado a la versión 7.5.8 - - * [agente de infraestructura v1.65.5](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1655): - * Se modificó el soporte de montaje de AWS EFS en muestras de almacenamiento. \ No newline at end of file diff --git a/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-8-14-2025.mdx b/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-8-14-2025.mdx deleted file mode 100644 index aa561dae04a..00000000000 --- a/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-8-14-2025.mdx +++ /dev/null @@ -1,112 +0,0 @@ ---- -subject: Docs -releaseDate: '2025-08-15' -version: 'August 08 - August 14, 2025' -translationType: machine ---- - -### Nuevos documentos - -* Se agregó [soporte para funciones NRQL en reglas de puerta de enlace](/docs/new-relic-control/pipeline-control/nrql-functions) para delinear las funciones NRQL admitidas en las reglas de puerta de enlace de Control de pipelines. -* Se agregaron pasos de resolución de problemas para resolver [Frequent Fluent Bit Restart Events](/docs/infrastructure/infrastructure-troubleshooting/troubleshoot-infrastructure/frequent-fluent-bit-restart-events) ajustando la configuración de resolución del nombre del host en la configuración del agente de New Relic Infrastructure. - -### Cambios importantes - -* [Plan de uso](/docs/licenses/license-information/usage-plans/new-relic-usage-plan/#list-price) actualizado con la última información de precios. -* Se agregó **Errors Inbox** a [la UIde carga de trabajo](/docs/new-relic-solutions/new-relic-one/workloads/use-workloads/#errors). -* Se agregó la desactivación selectiva del agente en función de la clase principal de inicio o el jar ejecutable a través de variables de entorno, junto con configuraciones de seguridad mejoradas para [la configuración del agente de Java ](/docs/apm/agents/java-agent/configuration/java-agent-configuration-config-file/#skip-applications). -* Se agregó soporte para [la configuración de repositorio privado](/docs/new-relic-control/agent-control/configuration/#private-repository-configuration) en el control de agente, lo que permite la implementación de agente gestionado con autenticación a través de métodos de certificado básico o TLS. -* Se agregó soporte para [la gestión de secretos](/docs/new-relic-control/agent-control/configuration/#secrets-management) en el control de agente, para gestionar datos confidenciales, como contraseñas y claves de API, recuperándolos del proveedor de secretos dedicado. - -### Cambios menores - -* Se agregaron restricciones de etiqueta de entidad para la cláusula `WHERE` en [Descartar datos mediante reglas cloud de Control de canalizaciones](/docs/new-relic-control/pipeline-control/cloud-rules-api/#restrictions). -* Se agregaron [las mejores prácticas para optimizar el contenido de su fuente de conocimiento](/docs/agentic-ai/knowledge-integration/overview/#configure) para el conector de conocimiento de New Relic AI. - -### Notas de la versión - -* Consulta nuestras publicaciones de Novedades: - - * [El modo de alta precisión de UniqueCount y el mayor soporte de argumentos ahora están disponibles de manera general](/whats-new/2025/08/whats-new-8-13-high-precision-uniquecount). - -* Mantener actualizado con nuestros últimos lanzamientos: - - * [AgenteCordova v7.0.8](/docs/release-notes/mobile-release-notes/cordova-release-notes/cordova-agent-708/): - - * Actualizar el agente nativo de Android a la versión 7.6.8 - * Actualizar el agente nativo de iOS a la versión 7.5.8 - - * [Agente Cordova v7.0.9](/docs/release-notes/mobile-release-notes/cordova-release-notes/cordova-agent-709/): - - * Actualizar el agente nativo de Android a la versión 7.6.6 - * Actualizar el agente nativo de iOS a la versión 7.5.5 - - * [Agente de Capacitor v1.5.8](/docs/release-notes/mobile-release-notes/capacitor-release-notes/capacitor-agent-158/): - - * Actualizar el agente nativo de Android a la versión 7.6.6 - * Actualizar el agente nativo de iOS a la versión 7.5.5 - - * [Agente de Capacitor v1.5.9](/docs/release-notes/mobile-release-notes/capacitor-release-notes/capacitor-agent-159/): - * Fallo de señal de aborto fijo - - * [Agente de Capacitor v1.5.10](/docs/release-notes/mobile-release-notes/capacitor-release-notes/capacitor-agent-1510/): - - * Actualizar el agente nativo de Android a la versión 7.6.8 - * Actualizar el agente nativo de iOS a la versión 7.5.8 - - * [CLI de diagnóstico (nrdiag) v3.5.0](/docs/release-notes/diagnostics-release-notes/diagnostics-cli-release-notes/diagnostics-cli-350/): - * se actualizó la comprobación de compatibilidad de la versión `Java/Appserver/JbossEapCheck` - - * [Agente .NET v10.44.0](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-44-0/): - - * Samplers de rendimiento métrica habilitados en modo Serverless - * Se excluyó el proceso de host sitio web de Azure Functions (Linux) de la instrumentación. - - * [NRDOT v1.3.0](/docs/release-notes/nrdot-release-notes/nrdot-2025-08-13/): - - * Se actualizaron las versiones de los componentes del hotel de v0.128.0 a v0.131.0 - * Se introdujo la distribución principal de nrdot - - * [Agente de Node.js v13.1.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-1-0/): - - * Se agregó soporte para la API de logs de OTEL - * Se agregó compatibilidad con métricas cuando se deshabilitó la instrumentación para un paquete - * Instrumentación de temporizadores deshabilitados por defecto en la configuración de muestra. - * Ofuscación fija `transaction.url` - - * [Administrador de trabajos v454](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-454/): - * Se corrigieron las vulnerabilidades subyacentes de Ubuntu para abordar las vulnerabilidades de seguridad en SJM. - - * [Tiempo de ejecución de la API de nodo v1.2.124](/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.124/): - * Se corrigieron las vulnerabilidades subyacentes de Ubuntu para abordar vulnerabilidades de seguridad en los tiempos de ejecución de Node API. - - * [Runtime del navegador de nodos v3.0.41](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.41/): - * Se corrigieron las vulnerabilidades temporales `CVE-2025-54798` y las vulnerabilidades subyacentes de Ubuntu para abordar vulnerabilidades de seguridad en los tiempos de ejecución de Node Browser . - - * [Tiempo de ejecución de ping v1.54.0](/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.54.0/): - * Se corrigieron vulnerabilidades relacionadas con Ubuntu para abordar problemas de seguridad en el tiempo de ejecución de Ping. - - * [Agente de Java v8.23.0](/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8230/): - - * Actualizado para soportar v24 de graphql. - * Se agregó instrumentación de lechuga 6.5. - * Se actualizó la versión de Commons Lang a 3.18.0 - - * [Reenviador de logs AWS Lambda v1.1.1](/docs/release-notes/aws-lambda-log-forwarder-release-notes/lambda-25-07-25/): - * Se mejoró la postura de seguridad al actualizar la versión Go a 1.24.4 en los sistemas. - - * [Agente PHP v12.0.0.25](/docs/release-notes/agent-release-notes/php-release-notes/php-agent-12-0-0-25/): - - * Logging de errores del mapa de gancho de Drupal mejorado. - * Se corrigieron problemas de detección de paquetes legacy para Security RX. - - * [agente de infraestructura v1.66.1](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1661/): - * Se revirtió el soporte para montajes de AWS EFS en muestras de almacenamiento. - - * [Aplicación móvil para Android v5.30.6](docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5306/): - * Compatibilidad mejorada con claves de acceso para inicios de sesión SAML y sociales. - - * [Agente del navegador v1.295.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.0/): - - * Se agregó detección de causa de error. - * Se agregaron advertencias sobre parches para monos. \ No newline at end of file diff --git a/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-8-21-2025.mdx b/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-8-21-2025.mdx deleted file mode 100644 index e554b9e74bb..00000000000 --- a/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-8-21-2025.mdx +++ /dev/null @@ -1,56 +0,0 @@ ---- -subject: Docs -releaseDate: '2025-08-22' -version: 'August 15 - August 21, 2025' -translationType: machine ---- - -### Cambios importantes - -* Reporte actualizado de compatibilidad [del agente Node.js.](/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent/) -* [Agente .NET](/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements/) actualizado con las últimas versiones de biblioteca compatibles verificadas. - -### Cambios menores - -* Se actualizó el sistema operativo [Debian](/docs/infrastructure/infrastructure-agent/linux-installation/package-manager-install/) a la versión 12 ("bookworm") para soportar el [agente de infraestructura](/docs/infrastructure/infrastructure-agent/requirements-infrastructure-agent/#os) para Linux. -* Se actualizó la función [`accountId()`](/docs/data-apis/manage-data/query-limits/) para consultar los límites de datos. -* [Instalador MSIWindows ](/docs/infrastructure/infrastructure-agent/windows-installation/windows-msi-installer/#install-windows)actualizado para soportar Windows de 64 bits (Intel/AMD). - -### Notas de la versión - -* Se anunció el 7 de enero de 2026 como la fecha de fin de vida útil de las reglas de lanzamiento a través de la [UI de monitoreo de IA](/docs/ai-monitoring/drop-sensitive-data/). - -* [Agente iOS v7.5.9](/docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-759/) - - * Se solucionó un problema que podía provocar que rastreo distribuido no tuviera toda la información de cuenta requerida al inicio de una sesión. - * Se solucionó un problema que podía provocar un bloqueo al iniciar el agente. - -* [Agente de Python v10.16.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-101600/) - - * Se agregó soporte para nuevas funciones [de Redis](https://pypi.org/project/redis/). - * Se convirtieron todas las rutas internas de `os.path` a `pathlib.Path`. - * Problema corregido con la codificación JSON PosixPath. - -* [Integración Kubernetes v3.44.1](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-44-1/) - - * Esta integración está incluida en las siguientes versiones de gráficos: - - * [infraestructura newrelic-3.49.1](https://github.com/newrelic/nri-kubernetes/releases/tag/newrelic-infrastructure-3.49.1) - * [paquete nri-6.0.10](https://github.com/newrelic/helm-charts/releases/tag/nri-bundle-6.0.10) - -* [Agente .NET v10.44.1](/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-44-1/) - - * Se corrigió el manejo de excepciones en el contenedor de instrumentación de Service Bus. - * Se excluyó el proceso de host sitio web de Azure Functions (Linux) de la instrumentación. - -* [Agente de Node.js v13.2.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-2-0/) - - * Se agregó la capacidad de registrar `Supportability/Features/Instrumentation/OnRequire/` métrica para instrumentación basada en suscriptores. - * Se agregó el gancho de carga esm y el parche commonjs para trabajar con orchestrion-js. - * Se agregó instrumentación para las llamadas de cliente `@modelcontextprotocol/sdk` `client.callTool`, `client.readResource` y `client.getPrompt`. - * Se corrigió la lógica en torno a la detección de paquetes OTEL. - * Se actualizó `shimmer.setupSubscribers` para configurar y omitir correctamente los suscriptores que están deshabilitados. - -* [Agente de Node.js v13.2.1](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-2-1/) - - * Agente actualizado para emplear `@apm-js-collab/tracing-hooks` para el registro CJS/ESM para rastrear instrumentación basada en canales. \ No newline at end of file diff --git a/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-9-12-2025.mdx b/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-9-12-2025.mdx deleted file mode 100644 index cc764eedf32..00000000000 --- a/src/i18n/content/es/docs/release-notes/docs-release-notes/docs-9-12-2025.mdx +++ /dev/null @@ -1,94 +0,0 @@ ---- -subject: Docs -releaseDate: '2025-09-14' -version: 'September 08 - September 12, 2025' -translationType: machine ---- - -### Nuevos documentos - -* Se agregó documentación integral [del Modelo de madurez de observabilidad](/docs/new-relic-solutions/observability-maturity/) para brindar orientación para medir y mejorar las prácticas de observabilidad en cuatro áreas clave: tiempo de actividad empresarial, experiencia digital, excelencia en ingeniería y observabilidad inteligente. - -### Cambios importantes - -* [Configuración de agente PHP](/docs/apm/agents/php-agent/configuration/php-agent-configuration/) actualizada con amplias opciones de configuración nuevas para controles de ejemplificación e instrumentación del controlador de excepciones framework. - -### Cambios menores - -* [Introducción a los dashboards](/docs/query-your-data/explore-query-data/dashboards/introduction-dashboards/) actualizada con orientación mejorada para dashboard uso. -* Documentación [de gestión de dashboard](/docs/query-your-data/explore-query-data/dashboards/manage-your-dashboard/) mejorada con contenido simplificado para la gestión de JSON. -* Se corrigieron los enlaces rotos en la documentación [del plan de uso de New Relic](/docs/licenses/license-information/usage-plans/new-relic-usage-plan/). -* Se corrigió la configuración de depuración en la documentación [del agente resolución de problemas de .NET](/docs/apm/agents/net-agent/troubleshooting/debugging-net-windows/). - -### Notas de la versión - -* Mantener actualizado con nuestros últimos lanzamientos: - - * [Agente de Browser v1.297.0](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.297.0/): - - * Se evitaron cosechas tempranas durante el periodo de reintento para un mejor manejo de la limitación de velocidad. - * Se eliminó el meta atributo newrelic de la carga de repetición saliente para reducir los bytes facturables. - * Se corrigieron excepciones para cuerpos nulos que surgen de cosechas vacías. - - * [Agente PHP v12.1.0.26](/docs/release-notes/agent-release-notes/php-release-notes/php-agent-12-1-0-26/): - - * Se agregaron controles de ejemplificación basados en la decisión de ejemplificación de trazas de w3c ascendente. - * Se agregó una opción de configuración para omitir la instrumentación de los controladores de excepciones framework. - * Se solucionó una posible pérdida de memoria al llamar `newrelic_end_transaction(true)`. - * Se actualizó la versión de Golang a 1.25.1 para realizar mejoras de seguridad. - - * [Agente de Python v10.17.0](/docs/release-notes/agent-release-notes/python-release-notes/python-agent-101700/): - - * Se agregó soporte para tareas personalizadas en Celery. - * Se agregó soporte para monitoreo Graphene-Django. - * Se agregó soporte para filtrado de middleware en Django. - * Se agregó soporte para la API de AWS Bedrock Converse. - * Se agregó soporte para el indicador de ejemplificación del encabezado W3CTraceParent. - - * [Agente de Java v8.24.0](/docs/release-notes/agent-release-notes/java-release-notes/java-agent-8240/): - - * Se agregó soporte para MongoDB Reactive Streams 5.2.0 y posteriores. - * Se agregó soporte para Jedis 6. - * Se solucionó el problema de instrumentación doble de CouchBase. - * Se solucionó el problema de ajuste del encabezado de Spring WebClient 5.x. - - * [Agente de Node.js v13.3.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-3-0/): - - * Se agregó soporte para MCP `StreamableHTTPClientTransport`. - - * [Agente de Node.js v13.3.1](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-3-1/): - - * Se solucionó el fallo al establecer de forma predeterminada `requestParameters` en un objeto en `transaction.addRequestParameters`. - - * [Agente de Node.js v13.3.2](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-3-2/): - - * Se agregó código defensivo para obtener `protocol` en llamadas http salientes. - - * [Integración Kubernetes v3.45.1](/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-45-1/): - - * Actualizado con las últimas mejoras y correcciones de errores. - - * [Administrador de trabajos v464](/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-464/): - - * Se solucionó el problema en el que los clientes no podían extraer imágenes de un registro personalizado usando podman. - - * [Tiempo de ejecución del navegador de nodos v3.0.43](/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.43/): - - * Se corrigieron las vulnerabilidades subyacentes de Ubuntu para abordar vulnerabilidades de seguridad. - - * [Aplicación móvil para iOS v6.9.12](/docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6102/): - - * Se corrigieron problemas de enlaces profundos para el panel y las alertas. - * Se solucionó el problema de identificación del tablero de CCU. - - * [Aplicación móvil para Android v5.30.7](/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5307/): - - * Se agregaron correcciones de errores y mejoras. - - * [Agente de Flutter v1.1.14](/docs/release-notes/mobile-release-notes/flutter-release-notes/flutter-agent-1114/): - - * Se agregaron mejoras de estabilidad adicionales y correcciones de errores. - - * [Control de Pipeline Gateway v25.09.01](/docs/release-notes/pipeline-control-gateway-release-notes/pipeline-control-gateway-25-09-01/): - - * Se agregó una nueva versión con capacidades mejoradas de control de tuberías. \ No newline at end of file diff --git a/src/i18n/content/es/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx b/src/i18n/content/es/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx deleted file mode 100644 index 0f31403d612..00000000000 --- a/src/i18n/content/es/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx +++ /dev/null @@ -1,39 +0,0 @@ ---- -subject: Browser agent -releaseDate: '2025-08-04' -version: 1.295.0 -downloadLink: 'https://www.npmjs.com/package/@newrelic/browser-agent' -features: - - Add error cause detection -bugs: - - Add monkey-patching warnings - - Calculate first and last timestamps from raw data -security: [] -translationType: machine ---- - -## v1.295.0 - -### Característica - -#### Agregar detección de causa de error - -Detectar y reportar la causa del atributo en el evento JavaScriptError capturado. Si la causa es una instancia de un Error, se capturará el rastreo de la stack, de lo contrario se informará el contenido en cadena de la causa. Esto se podrá consultar en JavaScriptError incluso bajo el atributo `cause`. - -### Corrección de errores - -#### Agregar advertencias sobre parches de mono - -Se agregó detección y advertencias para cuando los valores globales esperados fueron parcheados antes de que el agente se ejecutó en la página. Esto puede provocar comportamientos inesperados y la intención es informar a los clientes sobre este comportamiento. - -#### Calcular la primera y la última marca de tiempo a partir de datos sin procesar - -Cerciorar de que el agente calcule manualmente la primera y la última marca de tiempo de una carga de SessionReplay antes de la recolección para ayudar a mejorar la consistencia en el reproductor UI. - -## Declaración de apoyo - -New Relic recomienda que actualices el agente periódicamente para garantizar que obtengas las últimas características y beneficios de rendimiento. Las versiones anteriores ya no recibirán soporte cuando lleguen [al final de su vida útil](https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/browser-agent-eol-policy/). Las fechas de lanzamiento reflejan la fecha de publicación original de la versión del agente. - -Las nuevas versiones del agente del browser se lanzan a los clientes en pequeñas etapas a lo largo de un periodo de tiempo. Debido a esto, la fecha en que el lanzamiento esté disponible en su cuenta puede no coincidir con la fecha de publicación original. Consulte este [dashboard de estado](https://newrelic.github.io/newrelic-browser-agent-release/) para obtener más información. - -De acuerdo con nuestra [política de compatibilidad de navegadores](https://docs.newrelic.com/docs/browser/new-relic-browser/getting-started/compatibility-requirements-browser-monitoring/#browser-types), la versión 1.295.0 del agente del navegador se creó y probó con estos navegadores y rangos de versiones: Chrome 128-138, Edge 128-138, Safari 17-19 y Firefox 130-140. Para dispositivos móviles, la versión v1.295.0 fue creada y probada para Android OS 16 e iOS Safari 17-26. \ No newline at end of file diff --git a/src/i18n/content/es/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.296.mdx b/src/i18n/content/es/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.296.mdx deleted file mode 100644 index d281b28d57c..00000000000 --- a/src/i18n/content/es/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.296.mdx +++ /dev/null @@ -1,34 +0,0 @@ ---- -subject: Browser agent -releaseDate: '2025-08-19' -version: 1.296.0 -downloadLink: 'https://www.npmjs.com/package/@newrelic/browser-agent' -features: - - Harvest traces early -bugs: - - Remove event buffer inspection event -security: [] -translationType: machine ---- - -## versión 1.296.0 - -### Característica - -#### Cosecha temprana de traza - -Actualice el agente para manejar el rastreo de sesión de la misma manera que otras características manejan los datos a partir de [1.294.0](https://docs.newrelic.com/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.294.0/). permitiendo cosechas de 16kb de tamaño. - -### Corrección de errores - -#### Eliminar la inspección del búfer de eventos - -Elimina la inspección del búfer de eventos para evitar una pérdida de memoria al usar console.log con el detector de eventos de la ventana `newrelic`. - -## Declaración de apoyo - -New Relic recomienda que actualices el agente periódicamente para garantizar que obtengas las últimas características y beneficios de rendimiento. Las versiones anteriores ya no recibirán soporte cuando lleguen [al final de su vida útil](https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/browser-agent-eol-policy/). Las fechas de lanzamiento reflejan la fecha de publicación original de la versión del agente. - -Las nuevas versiones del agente del browser se lanzan a los clientes en pequeñas etapas a lo largo de un periodo de tiempo. Debido a esto, la fecha en que el lanzamiento esté disponible en su cuenta puede no coincidir con la fecha de publicación original. Consulte este [dashboard de estado](https://newrelic.github.io/newrelic-browser-agent-release/) para obtener más información. - -De acuerdo con nuestra [política de compatibilidad de navegadores](https://docs.newrelic.com/docs/browser/new-relic-browser/getting-started/compatibility-requirements-browser-monitoring/#browser-types), la versión 1.296.0 del agente del navegador se creó y probó con estos navegadores y rangos de versiones: Chrome 129-139, Edge 129-139, Safari 17-19 y Firefox 131-141. Para dispositivos móviles, la versión v1.296.0 fue creada y probada para Android OS 16 e iOS Safari 17-18.1. \ No newline at end of file diff --git a/src/i18n/content/es/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.297.mdx b/src/i18n/content/es/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.297.mdx deleted file mode 100644 index dceea8b093e..00000000000 --- a/src/i18n/content/es/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.297.mdx +++ /dev/null @@ -1,27 +0,0 @@ ---- -subject: Browser agent -releaseDate: '2025-09-17' -version: 1.297.1 -downloadLink: 'https://www.npmjs.com/package/@newrelic/browser-agent' -features: [] -bugs: - - Prevent double import of Session Replay aggregate class -security: [] -translationType: machine ---- - -## v1.297.1 - -### Corrección de errores - -#### Evitar la doble importación de la clase agregada Session Replay - -Corrige un problema que se encontró donde la clase agregada Session Replay podía importar dos veces al usar el método API newrelic.recordReplay mientras se habilitaba la precarga. - -## Declaración de apoyo - -New Relic recomienda que actualices el agente periódicamente para garantizar que obtengas las últimas características y beneficios de rendimiento. Las versiones anteriores ya no recibirán soporte cuando lleguen [al final de su vida útil](https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/browser-agent-eol-policy/). Las fechas de lanzamiento reflejan la fecha de publicación original de la versión del agente. - -Las nuevas versiones del agente del browser se lanzan a los clientes en pequeñas etapas a lo largo de un periodo de tiempo. Debido a esto, la fecha en que el lanzamiento esté disponible en su cuenta puede no coincidir con la fecha de publicación original. Consulte este [dashboard de estado](https://newrelic.github.io/newrelic-browser-agent-release/) para obtener más información. - -De acuerdo con nuestra [política de compatibilidad de navegadores](https://docs.newrelic.com/docs/browser/new-relic-browser/getting-started/compatibility-requirements-browser-monitoring/#browser-types), la versión 1.297.1 del agente del navegador se creó y probó con estos navegadores y rangos de versiones: Chrome 130-140, Edge 130-140, Safari 17-19 y Firefox 132-142. Para dispositivos móviles, la versión v1.297.1 fue creada y probada para Android OS 16 e iOS Safari 17-18.5. \ No newline at end of file diff --git a/src/i18n/content/es/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.mdx b/src/i18n/content/es/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.mdx deleted file mode 100644 index 06eefb60757..00000000000 --- a/src/i18n/content/es/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.mdx +++ /dev/null @@ -1,10 +0,0 @@ ---- -subject: Node API runtime -releaseDate: '2025-07-29' -version: 1.2.122 -translationType: machine ---- - -### Correcciones - -* Se corrigieron las vulnerabilidades de datos de formulario y las vulnerabilidades subyacentes de Ubuntu para abordar vulnerabilidades de seguridad en los tiempos de ejecución de Node API. \ No newline at end of file diff --git a/src/i18n/content/es/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.mdx b/src/i18n/content/es/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.mdx deleted file mode 100644 index fdfdc17442f..00000000000 --- a/src/i18n/content/es/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.mdx +++ /dev/null @@ -1,10 +0,0 @@ ---- -subject: Node browser runtime -releaseDate: '2025-07-29' -version: 3.0.39 -translationType: machine ---- - -### Mejoras - -* Se corrigieron las vulnerabilidades de datos de formulario y las vulnerabilidades subyacentes de Ubuntu para abordar vulnerabilidades de seguridad en los tiempos de ejecución de Node Browser. \ No newline at end of file diff --git a/src/i18n/content/es/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.53.mdx b/src/i18n/content/es/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.53.mdx deleted file mode 100644 index ec1e32db231..00000000000 --- a/src/i18n/content/es/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.53.mdx +++ /dev/null @@ -1,10 +0,0 @@ ---- -subject: Ping Runtime -releaseDate: '2025-07-29' -version: 1.53.0 -translationType: machine ---- - -### Mejoras - -* Se corrigieron vulnerabilidades relacionadas con `common-lang3` Java y Ubuntu para abordar problemas de seguridad en el tiempo de ejecución de Ping. \ No newline at end of file diff --git a/src/i18n/content/es/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.54.mdx b/src/i18n/content/es/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.54.mdx deleted file mode 100644 index 65d952ef7ac..00000000000 --- a/src/i18n/content/es/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.54.mdx +++ /dev/null @@ -1,10 +0,0 @@ ---- -subject: Ping Runtime -releaseDate: '2025-08-13' -version: 1.54.0 -translationType: machine ---- - -### Mejoras - -* Se corrigieron vulnerabilidades relacionadas con Ubuntu para abordar problemas de seguridad en el tiempo de ejecución de Ping. \ No newline at end of file diff --git a/src/i18n/content/fr/docs/accounts/accounts-billing/new-relic-one-pricing-billing/add-on-billing.mdx b/src/i18n/content/fr/docs/accounts/accounts-billing/new-relic-one-pricing-billing/add-on-billing.mdx deleted file mode 100644 index 6f47050af84..00000000000 --- a/src/i18n/content/fr/docs/accounts/accounts-billing/new-relic-one-pricing-billing/add-on-billing.mdx +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: Facturation complémentaire (en option) -tags: - - Accounts - - Accounts and billing - - New Relic pricing and billing -metaDescription: Add-ons are an optional billing factor -freshnessValidatedDate: '2024-10-23T00:00:00.000Z' -translationType: machine ---- - -En plus des principaux facteurs de facturation de GB Ingested et d'utilisateurs facturables, vous pouvez également utiliser des modules complémentaires facturables optionels pour étendre votre expérience avec New Relic. - -* **Calculateur avancé (anciennement calculateur complémentaire)**: ce module complémentaire s'applique à la facturation basée sur l'utilisation pour les actions que vous exécutez en relation avec CodeStream, Live Archives et d'autres fonctionnalités mises à disposition. Vous êtes mesuré et facturé en fonction de votre utilisation des [CCU avancés](/docs/licenses/license-information/product-definitions/new-relic-one-pricing-definitions/#compute-capacity-unit). - - - Votre utilisation de CodeStream sous calculateur avancé (Advanced Compute) entraînera des frais CCU, quel que soit le type d'utilisateur. Cela signifie que l'utilisateur de base gratuit peut accéder à la fonctionnalité de calcul avancée et encourir des frais pour les CCU avancés. - - -* **Centre de données de l'UE pour les données d'origine (Original Data) ou les données Plus (Data Plus)**: ce module complémentaire s'applique à votre option de données (données d'origine ou données Plus) lorsque vous sélectionnez l'Union européenne comme région de données, selon les disponibilités. - -* **Conservation prolongée des données d'origine ou des données plus** : ce module complémentaire s'applique si vous dépassez la durée par défaut pendant laquelle vos données sont conservées. Cela s'applique à toutes vos données, pas seulement aux logs, et constitue une bonne option si vous devez effectuer de nombreuses petites requêtes ou effectuer des requêtes sur de gros volumes de données. - -* **Live Archives** : Prolongez la durée de stockage de vos logs jusqu'à sept ans. Live Archives nécessite également Advanced Compute. - -* **New Relic Synthetics Checks** : Ce module complémentaire s'applique si vos contrôles dépassent le nombre par défaut de contrôles de monitoring synthétiques. - -* **Security RX**: cette fonctionnalité est incluse avec Data Plus, mais le module complémentaire s'applique si vous utilisez la fonctionnalité Security RX sans Data Plus. \ No newline at end of file diff --git a/src/i18n/content/fr/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing.mdx b/src/i18n/content/fr/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing.mdx deleted file mode 100644 index d92819d86c2..00000000000 --- a/src/i18n/content/fr/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing.mdx +++ /dev/null @@ -1,354 +0,0 @@ ---- -title: 'Données : Facturation et règles' -tags: - - Accounts - - Accounts and billing - - New Relic pricing and billing -metaDescription: 'For New Relic pricing, an explanation of how data ingest is calculated for billing purposes.' -freshnessValidatedDate: '2024-10-23T00:00:00.000Z' -translationType: machine ---- - -Pour la tarification New Relic, les données ingérées par votre organisation New Relic constituent un facteur de facturation. - -## Informez-vous sur les coûts [#costs] - -Si vous n'êtes pas encore client New Relic et que vous êtes curieux de connaître les coûts, consultez d'abord [notre page de tarification principale](https://newrelic.com/pricing). Si vous êtes déjà client, continuez à lire pour en savoir plus sur la facturation de l'ingestion de données. - -## Afficher l'ingestion de données dans l'UI [#ui] - -Pour savoir comment trouver les informations d'utilisation et de facturation dans l'UI, consultez [UI de facturation](/docs/accounts/accounts-billing/general-account-settings/introduction-account-settings). - -Pour savoir comment afficher et gérer votre ingestion de données, consultez [Gérer l'ingestion](/docs/data-apis/manage-data/manage-data-coming-new-relic). - -## Options de données : Données Plus et originales [#data-prices] - -Le prix de votre organisation par Go de données ingérées varie en fonction de l'option de données dont dispose votre organisation : **Data Plus** ou notre option **Original Data**. L'option Data Plus offre des fonctionnalités de données avancées pour des performances, une évolutivité, une sécurité et une gouvernance optimisées. Une organisation New Relic ne peut avoir qu'une seule option à la fois. - -Voici un tableau comparatif des deux options. Les prix et les limites sont mensuels et les prix sont en USD. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    - Fonctionnalité/aptitude - - **Original Data** option - - **Data Plus** option - - Plus de détails sur la fonctionnalité -
    - [Éditions](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing/#editions) - - Toutes les éditions - - Nécessite Standard, Pro ou Enterprise - - (Nous notons ci-dessous si une fonctionnalité est spécifique à une édition) - -
    - Limite de données gratuites - - 100 Go ingérés - - 100 Go ingérés - -
    - Prix des données
    (au-delà de la limite gratuite) -     		- 0,40 USD/Go ingéré - - 0,60 USD/Go ingéré - -
    - Limite gratuite de rétention des données
    ([varie selon le type de données](/docs/data-apis/manage-data/manage-data-retention)) -     		- Défaut d'au moins 8 jours - - 90 jours supplémentaires en cas de défaut - -
    - Prix pour chaque tranche de 30 jours de rétention supplémentaire
    (au-delà de la limite gratuite) -     		- +0,05$/Go - - +0,05$/Go - -
    - Prix supplémentaire pour stocker des données dans [data centerde l'UE](/docs/accounts/accounts-billing/account-setup/choose-your-data-center)
    -     		- +0,05$/Go - - +0,05$/Go - - Les données sont stockées par défaut dans le data center américain. -
    - [Limite de requêtes](/docs/query-your-data/nrql-new-relic-query-language/get-started/rate-limits-nrql-queries/#query-limits)maximale - - Jusqu'à 20 milliards de points de données par minute - - Jusqu'à 60 B de points de données par minute - -
    - [Durée maximale de la requête](/docs/query-your-data/nrql-new-relic-query-language/get-started/rate-limits-nrql-queries/#query-duration) - - 1 minute - - Jusqu'à 10 minutes - -
    - Choix du fournisseur de cloud - - Fournisseur de cloud unique - - Azure ou plusieurs fournisseurs de cloud - - Choisissez votre fournisseur cloud préféré pour votre charge de travail d'observabilité afin d'aligner votre stockage de télémétrie avec votre modèle de déploiement d'ingénierie et votre préférence cloud . -
    - [Obfuscation des logs](/docs/logs/ui-data/obfuscation-ui/) - - Masquer [automatiquement](/docs/logs/get-started/new-relics-log-management-security-privacy/#log-obfuscation) les modèles de carte de crédit et de numéro de sécurité sociale connus dans les logs. - - Créez et suivez des règles directement dans l'UI et [masquez ou hachez](/docs/logs/ui-data/obfuscation-ui/) les données log sensibles. - -
    - [New Relic gestion des vulnérabilités](/docs/vulnerability-management/overview)
    (plateforme utilisateur complète uniquement) -     		- +0,10 $/Go
    (au-delà de la limite gratuite) -     		- Standard, Pro et Entreprise - - Identifiez les vulnérabilités et traitez les risques à chaque étape du cycle de vie du logiciel. -
    - Admissibilité [au programme FedRAMP Modéré](/docs/security/security-privacy/compliance/fedramp-compliant-endpoints) et [à la loi HIPAA](/docs/security/security-privacy/compliance/hipaa-readiness-new-relic) - - - - Enterprise - - Atteignez la conformité en matière de sécurité grâce à une configuration qui vous aide à répondre à vos exigences FedRAMP et HIPAA. -
    - [données de streaming export](/docs/apis/nerdgraph/examples/nerdgraph-streaming-export) - - - - Standard, Pro et Entreprise - - Configurez des règles pour exporter simultanément des données télémétriques vers le stockage AWS ou Azure de votre choix. Des frais d’exportation supplémentaires vers le fournisseur de cloud s’appliqueront. -
    - [Exportation de données historiques](/docs/apis/nerdgraph/examples/nerdgraph-historical-data-export) - - - - Standard, Pro et Entreprise - - Exécutez des requêtes plus volumineuses sans délai d'expiration pour l'analyse historique et la modélisation, le stockage à long terme et l'intégration avec d'autres plateformes d'analyse de données. -
    - Service natif New Relic d'Azure - - - - Standard, Pro et Entreprise
    ([avec quelques limitations](#azure-native-data-plus)) -     		-
    - -Pour voir une comparaison côte à côte de Data Plus et de notre option de données originales, consultez [notre fiche technique Data Plus](https://newrelic.com/resources/datasheets/data-plus). - -Intéressé par Data Plus ? Voir [Mise à niveau vers Data Plus](#upgrade-data-plus). - -### Détails du service Azure Native New Relic [#azure-native-data-plus] - -Avec le [serviceAzure Native New Relic ](/docs/infrastructure/microsoft-azure-integrations/get-started/azure-native), vous pouvez collecter et stocker vos données télémétriques pour les applications et infrastructure directement dans Azure. Cette fonctionnalité est incluse avec Data Plus, mais avec les limitations suivantes : - -* Disponible uniquement dans la région data center des États-Unis -* L'éligibilité FedRAMP Modéré/HIPAA n'est pas disponible -* L'exportation des données historiques n'est pas disponible - -## Mise à niveau vers Data Plus [#upgrade-data-plus] - -Pour passer à Data Plus, accédez à l'[UI**Data retention** ](/docs/data-apis/manage-data/manage-data-retention/#adjust-retention)dans le hub de gestion des données et cliquez sur **Upgrade retention**. - -* Remarque : vous pouvez voir un bouton **Edit data retention** , mais il est différent du bouton **Upgrade retention**. -* Pour voir le bouton **Upgrade retention** , vous devez disposer [des autorisations de facturation](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts/#admin-settings). Si vous remplissez les conditions et que vous ne voyez toujours pas l'option **Upgrade retention** , contactez votre représentant de compte New Relic. - -## Qu'est-ce qui est considéré comme des Go ingérés facturables ? [#usage-calculation] - -Dans le contexte du [plan tarifaire New Relic](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing), les « données ingérées » font référence aux données enregistrées dans New Relic par votre organisation après l'application de diverses règles de découpage et de transformation des données. En d’autres termes, ce n’est pas la quantité de données brutes envoyées à New Relic qui compte, mais la taille des données qui finissent par être stockées. - -En général, les données que nous générons pour fournir notre fonctionnalité ne comptent pas dans vos Go ingérés. Voici quelques exemples de fonctionnalités et de données liées aux fonctionnalités qui ne sont pas comptabilisées dans les Go ingérés : - -* [Fonctionnalité d'alerte de base](/docs/alerts-applied-intelligence/new-relic-alerts/learn-alerts/alerts-concepts-workflow). Par exemple, `NrAiIncident`, un événement utilisé pour générer ces fonctionnalités, ne compte pas dans les Go ingérés. -* Données créées à partir de données brutes agrégées (par exemple, [données infrastructure agrégées](/docs/data-apis/manage-data/manage-data-retention/#infrastructure-data) ou [données métriques dimensionnelles](/data-apis/manage-data/manage-data-retention/#dimensional-metrics)). -* [métriques dorées](/docs/apis/nerdgraph/examples/golden-metrics-entities-nerdgraph-api-tutorial) (pour en savoir plus sur les métriques dorées, voir nos [définitions d'entités](https://github.com/newrelic/entity-definitions)). -* Contrôles de monitoring synthétiques. Pour plus de détails sur la facturation des produits synthétiques, consultez [Limites et tarifsSynthetics ](/docs/synthetics/synthetic-monitoring/using-monitors/monitor-limits). -* Données de suivi d’utilisation et de facturation (par exemple, `NrConsumption`). -* Données relatives à l’administration du compte (par exemple, `NrIntegrationError`, `NrAuditEvent`). - -Pour comprendre votre utilisation, consultez l'[ UI d'utilisation](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing#usage-ui). - -## Autres détails de calcul [#calculation-details] - -* Dans le contexte de notre modèle de tarification, un Go est défini comme 1 milliard d’octets. -* Le nombre mensuel de Go ingérés est arrondi à l'entier inférieur le plus proche. Par exemple, si votre organisation utilise 100,9 Go au cours d'un mois, cela est comptabilisé comme 100 Go. - -## Édition gratuite [#free-tier-limits] - -Pour plus de détails sur GB Ingested pour notre édition gratuite, voir [Édition gratuite](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing/#free). - -## En savoir plus [#related-docs] - -* Pour en savoir plus sur la gestion des Go ingérés, consultez [Gérer l'ingestion de données](/docs/data-apis/manage-data/manage-data-coming-new-relic). -* Pour savoir comment requêter l'utilisation, voir [requête et alerte sur l'utilisation](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts). \ No newline at end of file diff --git a/src/i18n/content/fr/docs/cci/getting-started/overview.mdx b/src/i18n/content/fr/docs/cci/getting-started/overview.mdx deleted file mode 100644 index 35f5280af9d..00000000000 --- a/src/i18n/content/fr/docs/cci/getting-started/overview.mdx +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: 'Intelligence Coûts du cloud : Prenez le contrôle de vos dépenses cloud' -metaDescription: 'Gain comprehensive visibility and control over AWS cloud costs with CCI, enhancing your FinOps strategy for holistic cost management.' -freshnessValidatedDate: never -translationType: machine ---- - - - Nous travaillons toujours sur cette fonctionnalité, mais nous aimerions que vous l'essayiez ! - - Cette fonctionnalité est actuellement fournie dans le cadre d'un programme d'aperçu conformément à nos [politiques de pré-sortie](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). - - -Intelligence Coûts du cloud est conçu pour offrir une visibilité et une gestion des coûts cloud. Intelligence Coûts du cloud monitoring de l'IA pour combler le fossé entre la visibilité des coûts et l'observabilité infrastructure, vous offrant une vue holistique de vos dépenses cloud. - -Par exemple, à mesure que votre grande entreprise adapte rapidement son utilisation des services cloud, le suivi et la gestion des dépenses cloud peuvent devenir de plus en plus complexes. Intelligence Coûts du cloud vous aide en fournissant des informations détaillées sur la destination de votre argent. Cela peut vous aider à identifier les domaines dans lesquels des économies potentielles peuvent être réalisées. En alignant les dépenses cloud sur l’utilisation réelle, vous pouvez optimiser vos budgets tout en continuant à soutenir les initiatives de croissance stratégique. Cette approche permet de garantir que chaque dollar que vous investissez contribue au succès global de votre entreprise. - - - Actuellement, seuls les coûts cloud d'AWS sont pris en charge. - - -Cloud Cost Intelligence summary page showing total costs, real-time cost estimates, average cost by day, and top 5 cost variance - -## Fonctionnalité clé - -### Visibilité complète des coûts - -* **Répartition par catégorie :** affichez les coûts du cloud segmentés par application, service, équipe propriétaire et région. -* **Analyse des tendances :** obtenez des informations détaillées sur les tendances des coûts d'un mois à l'autre, les coûts moyens et les principaux facteurs de coûts. - -### Répartition des coûts de Kubernetes - -Obtenez une visibilité sur les coûts liés à Kubernetes. Nous exploitons les données télémétriques de New Relic pour ventiler les coûts par nom d'application. - -### Estimation des coûts en temps réel - -Intelligence Coûts du cloud exploite les données télémétriques et les modèles de coûts historiques pour fournir des mises à jour horaires des coûts, reflétant les changements dans l'heure suivant l'approvisionnement des ressources. Cette intégration avec vos données de facturation permet des estimations de coûts basées sur le prix unitaire moyen de la semaine écoulée et les données télémétriques New Relic pour la période récente de 48 heures. Sans cette intégration, les estimations sont par défaut basées sur des taux de tarification unitaires standard potentiellement plus élevés. - -Pour des estimations plus précises, intégrez la télémétrie et conservez au moins 7 jours de données historiques. Ces données permettent de calculer les coûts pour la même instance. En l’absence de telles données, les estimations reviennent à la tarification à la demande, le modèle standard de paiement à l’utilisation utilisé par les fournisseurs de cloud. - - - **Collecte de données inter-comptes**
    Intelligence Coûts du cloud s'adresse à l'utilisateur et collecte les données télémétriques de tous les comptes associés à vos identifiants utilisateur New Relic. Cela signifie que même si vous utilisez un seul compte New Relic pour Intelligence Coûts du cloud, les données télémétriques de tous les comptes New Relic supplémentaires auxquels vous avez accès seront également collectées et visibles dans ce seul compte New Relic. Vérifiez que les autorisations de votre compte utilisateur sont conformes à vos politiques internes et autorisez l'accès aux données des comptes New Relic que vous souhaitez afficher. -     - -## Comment Intelligence Coûts du cloud récupère les coûts cloud via des solutions de stockage [#fetch-costs] - -Intelligence Coûts du cloud accède automatiquement à vos rapports de coûts et d'utilisation AWS (CUR) dans votre compartiment S3 désigné une fois la configuration et l'intégration terminées. Ce processus commence par votre autorisation et la fourniture des autorisations d’accès. Il est important de noter qu'Intelligence Coûts du cloud ne peut extraire des rapports qu'une fois les données exportées vers votre bucket S3 désigné. Assurez-vous que le préfixe du chemin S3 est défini sur cost-and-usage-reports comme spécifié dans les [prérequis](/docs/cci/getting-started/prerequisites). - -En règle générale, AWS met à jour le CUR trois fois par jour et Intelligence Coûts du cloud récupère le CUR de votre bucket S3 une fois par heure après la configuration. Votre dernier CUR sera visible dans Intelligence Coûts du cloud lorsque AWS fournira sa mise à jour et Intelligence Coûts du cloud le récupérera peu de temps après. - - - **Confidentialité de vos données**
    Les CUR sont des données sur votre utilisation des services cloud et leurs coûts, qui ne doivent pas inclure de données personnelles. Assurez-vous que les données que vous envoyez sont exemptes d'informations personnelles identifiables ou d'informations sensibles avant d'ajouter le CUR à votre compartiment S3 et avant de le télécharger sur New Relic. La suppression des données CUR n'est pas prise en charge pour le moment. Nous vous recommandons de ne pas générer le CUR avec des informations personnelles identifiables ou des informations sensibles. - - **Rétention des données :** Notre politique actuelle de rétention des données est de conserver les données jusqu'à 5 ans. Après 2 ans, les données sont déplacées vers AWS Glacier, une option de stockage moins coûteuse avec un temps de récupération plus long. - - **Accès de visualisation :** Sachez que toute personne ayant accès au compte New Relic que vous sélectionnez lors de l'installation pourra visualiser toutes les données dans Intelligence Coûts du cloud. Choisissez un compte avec des privilèges d’accès appropriés pour correspondre à vos exigences en matière de RBAC et de politique d’accès. -     - -### Analyse et reporting des données - -Après avoir récupéré les données CUR, Intelligence Coûts du cloud traite et analyse ces informations pour présenter des informations exploitables détaillées dans ses dashboards. Vous pouvez visualiser clairement les implications financières de votre utilisation du cloud, en identifiant les facteurs de coût et les domaines potentiels d’optimisation. \ No newline at end of file diff --git a/src/i18n/content/fr/docs/cci/getting-started/setup.mdx b/src/i18n/content/fr/docs/cci/getting-started/setup.mdx deleted file mode 100644 index 4e497e255cc..00000000000 --- a/src/i18n/content/fr/docs/cci/getting-started/setup.mdx +++ /dev/null @@ -1,83 +0,0 @@ ---- -title: Mettre en place CCI -metaDescription: Set up Cloud Cost Intelligence with AWS. Configure IAM roles and data paths for detailed cost analysis and streamlined access in New Relic. -freshnessValidatedDate: never -translationType: machine ---- - - - Nous travaillons toujours sur cette fonctionnalité, mais nous aimerions que vous l'essayiez ! - - Cette fonctionnalité est actuellement fournie dans le cadre d'un programme d'aperçu conformément à nos [politiques de pré-sortie](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). - - -Découvrez comment configurer Intelligence Coûts du cloud avec AWS en configurant les paramètres d'intégration essentiels, notamment les rôles IAM et les chemins d'exportation de données. Ce guide vous guide à travers les étapes nécessaires pour permettre une analyse et une gestion détaillées des coûts au sein de votre plateforme New Relic. - -Suivez ces étapes pour configurer Intelligence Coûts du cloud : - - - - ## Commencer à intégrer - - Cliquez sur **Cloud Cost Intelligence** dans le panneau de gauche, puis cliquez sur **Add the integration**. Vous pouvez également cliquer sur **Integrations & Agents** dans le panneau de gauche, rechercher Intelligence Coûts du cloud parmi toutes les fonctionnalités, puis cliquer sur **Cloud Cost Intelligence**. - - - - ## Sélectionnez un compte - - Sélectionnez le compte New Relic que vous souhaitez utiliser pour la configuration et cliquez sur **Continue**. - - - - ## Fournir les détails de connexion - - Saisissez les détails suivants requis pour récupérer les données de coût depuis AWS : - - * **Nom de la connexion :** renseigné par défaut. Modifiez si vous souhaitez un nom personnalisé. - * **ARN du rôle IAM inter-comptes :** le nom de ressource Amazon (ARN) pour le rôle IAM qu'Intelligence Coûts du cloud assumera pour accéder à votre compartiment S3. Un ARN est un identifiant unique pour diverses ressources AWS, y compris les rôles IAM. Il suit un format standard qui inclut le service, la région, l'ID de compte et les spécificités des ressources, telles que `arn:aws:iam:::role/`. - * **ID externe :** copiez l’ID externe de votre compte New Relic et ajoutez-le à votre configuration de rôle IAM dans le cadre des conditions préalables. Vous devez l’ajouter à la politique de confiance du rôle IAM dans votre compte AWS. - * **Nom d'exportation des données :** le nom du fichier d'exportation des données. Utilisé pour construire le chemin vers le fichier CUR correspondant. Pour un rapport nommé `cci-ingestion-test`, le chemin construit serait `cost-and-usage-reports/cci-ingestion-test/data`. C'est ici que les données CUR sont stockées dans le compartiment S3. - * **Nom du compartiment S3 :** le nom exact de votre compartiment S3. Assurez-vous qu'il inclut le préfixe `cost-and-usage-reports`. Utilisez un bucket S3 situé dans la région `us-east-2` pour des performances et une rentabilité optimales. - - - - ## Mettre en place une politique de confiance - - Ajoutez l’utilisateur global New Relic à la politique de confiance de votre rôle IAM et fournissez des autorisations de rôle. Cela permet à l'utilisateur global New Relic pour Intelligence Coûts du cloud d'assumer le rôle IAM. - - Pour permettre à Intelligence Coûts du cloud d'accéder à vos ressources AWS, configurez une politique de confiance dans votre console de gestion AWS qui permet à l'utilisateur global New Relic, `arn:aws:iam::207192125115:user/cci_global_user`, d'assumer un rôle IAM. Vous trouverez ci-dessous un exemple de document de politique de confiance : - - ```json - { - "Version": "2012-10-17", - "Statement": [ - { - "Effect": "Allow", - "Principal": { - "AWS": "arn:aws:iam::207192125115:user/cci_global_user" - }, - "Action": "sts:AssumeRole", - "Condition": { - "StringEquals": { - "sts:ExternalId": "" - } - } - } - ] - } - ``` - - - * Le `sts:ExternalId` est un composant essentiel pour la sécurité. Définissez-le sur l’ID externe que vous avez copié à l’étape précédente. Cet ID garantit que le rôle est assumé uniquement dans le contexte prévu par New Relic, améliorant ainsi la sécurité de votre intégration. - * Si vos ressources se trouvent dans des régions AWS où le service de jeton de sécurité (STS) n'est pas actif par défaut (par exemple, `ap-east-1`, `eu-south-1`), activez STS pour ces régions. - - - - - ## Tester la connexion - - Enfin, lancez un test pour vérifier que la connexion à votre environnement AWS est réussie. - - - -Après une configuration réussie, il peut falloir quelques heures pour que les données commencent à apparaître dans l'interface utilisateur de New Relic, en particulier lors de la première configuration. \ 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 deleted file mode 100644 index b4b4bbb9208..00000000000 --- a/src/i18n/content/fr/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation.mdx +++ /dev/null @@ -1,70 +0,0 @@ ---- -title: Intégration via CloudFormation et flux de métriques CloudWatch -tags: - - Integration via CloudFormation - - AWS metric integration - - Amazon integrations - - AWS integrations - - Integration with CloudWatch Metric Streams via CloudFormation -metaDescription: Integrate New Relic with AWS services using CloudFormation templates to automate the setup of CloudWatch Metric Streams for metrics ingestion. -freshnessValidatedDate: never -translationType: machine ---- - -Pour une intégration transparente de votre compte AWS avec New Relic, il s'agit du processus d'intégration le plus recommandé. Vous pouvez utiliser l'interrogation API pour les services non pris en charge par flux de métriques CloudWatch. - -## Prérequis [#prerequisites] - -Avant de commencer à intégrer votre compte AWS à New Relic, assurez-vous de remplir les conditions préalables suivantes : - -* **Une [clé de licence](https://one.newrelic.com/api-keys)New Relic**: vous aurez besoin d’une clé de licence pour connecter vos services AWS à votre compte New Relic. -* **[Autorisations](https://docs.aws.amazon.com/ARG/latest/userguide/gettingstarted-prereqs-permissions.html)** pour déployer de nouvelles ressources AWS et **[rôles IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html)**: vous aurez besoin de cette autorisation pour votre compte AWS. -* **[Autorisations](/docs/accounts/accounts-billing/new-relic-one-user-management/user-permissions/#infrastructure)** pour l'intégration cloud: vous aurez besoin de ces autorisations pour votre compte New Relic. - -## Étapes d'intégration [#integration-steps] - -Pour intégrer votre compte AWS à New Relic à l'aide de CloudFormation et de flux de métriques CloudWatch, suivez ces étapes : - -1. Accédez à [**Infrastructure > AWS**](https://one.newrelic.com/infra/infrastructure/cloud-aws). - -2. Sélectionnez le bon compte. - -3. Cliquez sur **Set up integration**. - -4. Suivez les instructions sur chaque écran et remplissez les champs qui vous concernent. Pour cette intégration, choisissez les options suivantes dans les écrans donnés : - - 1. **Choose Data type(s)**: Metrics - 2. **Choose a setup method**: Automate AWS with CloudFormation (Recommended) - 3. **Choose a metrics integration type**: CloudWatch Metric Stream (Recommended) - -5. Si vous utilisez l'un des services qui ne sont pas pris en charge dans flux de métriques CloudWatch, sur la page **Choose a metrics integration type**, sélectionnez **Yes** à la troisième étape pour l'interrogation de l'API et continuez. - - AWS Integration with CWMS and API Polling - -
    - Intégration CWMS des services AWS avec interrogation API sélectionnée pour les services non pris en charge. -
    - - Effectuez la configuration nécessaire comme indiqué sur la page **Enable API Polling (optional)** et continuez. - -6. Auto-discovery détecte et visualise automatiquement les relations entre vos entités AWS sur des cartes et exploite quelques autres flexibilités. Pour plus de détails, reportez-vous [à Découverte automatique de l'entité AWS](/docs/infrastructure/amazon-integrations/connect/set-up-auto-discovery-of-aws-entities/). Si vous souhaitez cette fonctionnalité, activez-la sur la page **Enable Auto Discovery (optional)** et continuez. - -7. Cliquez sur **Launch your CloudFormation in AWS**. Le modèle CloudFormation s'ouvre dans votre console AWS avec les paramètres configurés en fonction de vos sélections dans New Relic. Aucune modification supplémentaire n'est donc nécessaire, sauf si vous souhaitez apporter des modifications. - -8. Collez votre clé de licence dans votre console AWS. - -9. Pour déployer la stack Cloudformation, dans la console AWS, sélectionnez **Create stack**. La création des ressources stack peut prendre plusieurs minutes et peut générer plusieurs piles, selon la façon dont vous configurez le transfert des métriques. Si la création de la pile échoue, reportez-vous à la [procédure de dépannage](https://docs.newrelic.com/docs/logs/troubleshooting/aws-log-integration-issues/stack-creation-fails/). - -10. Après une création stack réussie, passez à la plateforme New Relic et continuez l'intégration guidée jusqu'à ce que vous voyiez vos données AWS dans New Relic. - -## Sujets connexes [#related-topics] - - - - Découvrez comment collecter des données à partir de plusieurs comptes AWS. - - - - Explorez et utilisez les métriques du flux de métriques CloudWatch. - - \ No newline at end of file diff --git a/src/i18n/content/fr/docs/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 deleted file mode 100644 index 2fb22d217d6..00000000000 --- a/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx +++ /dev/null @@ -1,267 +0,0 @@ ---- -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/) -* Added AWS integration via [CloudFormation and CloudWatch Metric Streams](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms/), supporting API Polling for unsupported services. -* 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/) -* Added seamless integration for [AWS with New Relic utilizing CloudFormation and CloudWatch Metric Streams](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms/), including support for API polling. - -### 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 deleted file mode 100644 index 1fcdfbdf228..00000000000 --- a/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-8-01-2025.mdx +++ /dev/null @@ -1,99 +0,0 @@ ---- -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 deleted file mode 100644 index d1b3ded6ad8..00000000000 --- a/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx +++ /dev/null @@ -1,60 +0,0 @@ ---- -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 deleted file mode 100644 index e751e90fd9c..00000000000 --- a/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-8-14-2025.mdx +++ /dev/null @@ -1,112 +0,0 @@ ---- -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 deleted file mode 100644 index 7cc6267277e..00000000000 --- a/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-8-21-2025.mdx +++ /dev/null @@ -1,56 +0,0 @@ ---- -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 deleted file mode 100644 index bb5a9bec1bb..00000000000 --- a/src/i18n/content/fr/docs/release-notes/docs-release-notes/docs-9-12-2025.mdx +++ /dev/null @@ -1,94 +0,0 @@ ---- -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/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 deleted file mode 100644 index e635be395dd..00000000000 --- a/src/i18n/content/fr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx +++ /dev/null @@ -1,39 +0,0 @@ ---- -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 deleted file mode 100644 index 1c13b3f0f23..00000000000 --- a/src/i18n/content/fr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.296.mdx +++ /dev/null @@ -1,34 +0,0 @@ ---- -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 deleted file mode 100644 index d923f60c65c..00000000000 --- a/src/i18n/content/fr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.297.mdx +++ /dev/null @@ -1,27 +0,0 @@ ---- -subject: Browser agent -releaseDate: '2025-09-17' -version: 1.297.1 -downloadLink: 'https://www.npmjs.com/package/@newrelic/browser-agent' -features: [] -bugs: - - Prevent double import of Session Replay aggregate class -security: [] -translationType: machine ---- - -## v1.297.1 - -### Débogage - -#### Empêcher la double importation de la classe d'agrégation Session Replay - -Corrige un problème qui a été détecté où la classe d'agrégation Session Replay pouvait être importée deux fois lors de l'utilisation de la méthode API newrelic.recordReplay lors du préchargement a été activée. - -## Déclaration de soutien - -New Relic vous recommande de mettre à niveau l'agent régulièrement pour vous assurer de bénéficier des dernières fonctionnalités et avantages en termes de performances. Les sorties plus anciennes ne seront plus prises en charge lorsqu'elles atteindront [la fin de leur vie](https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/browser-agent-eol-policy/). Les dates de sortie reflètent la date de publication originale de la version de l'agent. - -Les nouveaux agents de navigation sont déployés auprès des clients par petites étapes sur une période donnée. De ce fait, la date à laquelle la sortie devient accessible sur votre compte peut ne pas correspondre à la date de publication d'origine. Veuillez consulter ce [dashboard d'état](https://newrelic.github.io/newrelic-browser-agent-release/) pour plus d'informations. - -Conformément à notre [politique de prise en charge des navigateurs](https://docs.newrelic.com/docs/browser/new-relic-browser/getting-started/compatibility-requirements-browser-monitoring/#browser-types), la version 1.297.1 de l'agent du Browser a été conçue et testée sur ces navigateurs et plages de versions : Chrome 130-140, Edge 130-140, Safari 17-19 et Firefox 132-142. Pour les appareils mobiles, la version 1.297.1 a été créée et testée pour Android OS 16 et iOS Safari 17-18.5. \ No newline at end of file diff --git a/src/i18n/content/fr/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.mdx b/src/i18n/content/fr/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.mdx deleted file mode 100644 index 5605d8a3164..00000000000 --- a/src/i18n/content/fr/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.mdx +++ /dev/null @@ -1,10 +0,0 @@ ---- -subject: Node API runtime -releaseDate: '2025-08-13' -version: 1.2.124 -translationType: machine ---- - -### Corrections - -* 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. \ 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 deleted file mode 100644 index 85f982fb724..00000000000 --- a/src/i18n/content/fr/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.mdx +++ /dev/null @@ -1,10 +0,0 @@ ---- -subject: Node browser runtime -releaseDate: '2025-08-13' -version: 3.0.41 -translationType: machine ---- - -### Améliorations - -* 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 Node Browser. \ 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 deleted file mode 100644 index 40b68beae40..00000000000 --- a/src/i18n/content/fr/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.53.mdx +++ /dev/null @@ -1,10 +0,0 @@ ---- -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 deleted file mode 100644 index 9cf6842663a..00000000000 --- a/src/i18n/content/fr/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.54.mdx +++ /dev/null @@ -1,10 +0,0 @@ ---- -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/cci/getting-started/setup.mdx b/src/i18n/content/jp/docs/cci/getting-started/setup.mdx deleted file mode 100644 index b36b6b647e1..00000000000 --- a/src/i18n/content/jp/docs/cci/getting-started/setup.mdx +++ /dev/null @@ -1,83 +0,0 @@ ---- -title: CCIを設定する -metaDescription: Set up Cloud Cost Intelligence with AWS. Configure IAM roles and data paths for detailed cost analysis and streamlined access in New Relic. -freshnessValidatedDate: never -translationType: machine ---- - - - この機能はまだ開発中ですが、ぜひお試しください。 - - この機能は現在、弊社の[プレリリース ポリシー](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy)に従ってプレビュー プログラムの一部として提供されています。 - - -Cloud Cost IntelligenceAWSIAM ロールやデータ エクスポート パスなどの重要な統合設定を構成して、 で をセットアップする方法を学びます。このガイドでは、New Relic プラットフォーム内で詳細なコスト分析と管理を可能にするために必要な手順について説明します。 - -Cloud Cost Intelligence を構成するには、次の手順に従います。 - - - - ## 統合を開始する - - 左側のパネルで**Cloud Cost Intelligence**をクリックし、 **Add the integration** \[統合の追加]をクリックします。 または、左側のパネルで**Integrations & Agents** \[統合とエージェント]をクリックし、すべての機能の中からCloud Cost Intelligenceを探して、 **Cloud Cost Intelligence**をクリックします。 - - - - ## アカウントを選択 - - セットアップに使用する New Relic アカウントを選択し、 **Continue** \[続行]をクリックします。 - - - - ## 接続の詳細を入力する - - AWS からコストデータを取得するために必要な次の詳細を入力します。 - - * **接続名:**デフォルトで入力されます。カスタム名が必要な場合は編集します。 - * **クロスアカウント IAM ロール ARN:** Cloud Cost Intelligence が S3 バケットにアクセスするために引き受ける IAM ロールの Amazon リソース名 (ARN)。ARN は、IAM ロールを含むさまざまな AWS リソースの一意の識別子です。これは、サービス、リージョン、アカウント ID、リソースの詳細 ( `arn:aws:iam:::role/`など) を含む標準形式に従います。 - * **外部 ID:** New Relic アカウントの外部 ID をコピーし、前提条件の一部として IAM ロール設定に追加します。AWS アカウントの IAM ロールの信頼ポリシーに追加する必要があります。 - * **データ エクスポート名:**データ エクスポート ファイルの名前。対応する CUR ファイルへのパスを構築するために使用されます。`cci-ingestion-test`という名前のレポートの場合、構築されるパスは`cost-and-usage-reports/cci-ingestion-test/data`になります。これは、S3 バケット内で CUR データが保存される場所です。 - * **S3 バケット名:** S3 バケットの正確な名前。プレフィックス`cost-and-usage-reports`が含まれていることを確認してください。最適なパフォーマンスとコスト効率を得るには、 `us-east-2`リージョンにある S3 バケットを使用します。 - - - - ## 信頼ポリシーを設定する - - New Relic グローバル ユーザーを IAM ロールの信頼ポリシーに追加し、ロール権限を付与します。これにより、Cloud Cost Intelligence の New Relic グローバル ユーザーが IAM ロールを引き受けることができるようになります。 - - Cloud Cost Intelligence が AWS リソースにアクセスできるようにするには、AWS マネジメントコンソールで、New Relic グローバルユーザー`arn:aws:iam::207192125115:user/cci_global_user`が IAM ロールを引き受けることを許可する信頼ポリシーを設定します。以下は信頼ポリシー ドキュメントのサンプルです。 - - ```json - { - "Version": "2012-10-17", - "Statement": [ - { - "Effect": "Allow", - "Principal": { - "AWS": "arn:aws:iam::207192125115:user/cci_global_user" - }, - "Action": "sts:AssumeRole", - "Condition": { - "StringEquals": { - "sts:ExternalId": "" - } - } - } - ] - } - ``` - - - * `sts:ExternalId`セキュリティにとって重要なコンポーネントです。前の手順でコピーした外部 ID に設定します。この ID により、 New Relicが意図したコンテキスト内でのみ役割が引き受けられることが保証され、統合のセキュリティが強化されます。 - * リソースが、セキュリティ サービス (STS) がデフォルトでアクティブになっていないAWSリージョン ( `ap-east-1` 、 `eu-south-1` ) にある場合は、それらのリージョンに対して STS をアクティブ化します。 - - - - - ## テスト接続 - - 最後に、AWS 環境への接続が成功したことを確認するためのテストを開始します。 - - - -セットアップが成功した後、特に初回セットアップ時には、New Relic UI にデータが表示されるまでに数時間かかる場合があります。 \ No newline at end of file diff --git a/src/i18n/content/jp/docs/cci/getting-started/overview.mdx b/src/i18n/content/jp/docs/cci/overview.mdx similarity index 100% rename from src/i18n/content/jp/docs/cci/getting-started/overview.mdx rename to src/i18n/content/jp/docs/cci/overview.mdx 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 deleted file mode 100644 index 3d58ebbbfa1..00000000000 --- a/src/i18n/content/jp/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation.mdx +++ /dev/null @@ -1,70 +0,0 @@ ---- -title: CloudFormationとCloudWatchメトリックストリームを介して統合 -tags: - - Integration via CloudFormation - - AWS metric integration - - Amazon integrations - - AWS integrations - - Integration with CloudWatch Metric Streams via CloudFormation -metaDescription: Integrate New Relic with AWS services using CloudFormation templates to automate the setup of CloudWatch Metric Streams for metrics ingestion. -freshnessValidatedDate: never -translationType: machine ---- - -AWSアカウントとNew Relicをシームレスに統合するには、これが最も推奨される統合プロセスです。 CloudWatch メトリック ストリームでサポートされていないサービスに対してAPIポーリングを利用できます。 - -## 前提条件 [#prerequisites] - -AWS アカウントと New Relic の統合を開始する前に、次の前提条件を満たしていることを確認してください。 - -* **New Relic[ライセンスキー](https://one.newrelic.com/api-keys)**: AWSサービスをNew Relicアカウントに接続するには、ライセンスキーが必要です。 -* **[](https://docs.aws.amazon.com/ARG/latest/userguide/gettingstarted-prereqs-permissions.html)**新しい AWS リソースと**[ IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html)** ロール をデプロイするための 権限: AWS アカウントにはこの権限が必要です。 -* クラウド統合の**[権限](/docs/accounts/accounts-billing/new-relic-one-user-management/user-permissions/#infrastructure)**: New Relicアカウントにはこれらの権限が必要です。 - -## 統合手順 [#integration-steps] - -CloudFormation と CloudWatch Metric Streams を使用して AWS アカウントを New Relic と統合するには、次の手順に従います。 - -1. [**Infrastructure > AWS**](https://one.newrelic.com/infra/infrastructure/cloud-aws)に移動します。 - -2. 正しいアカウントを選択してください。 - -3. **Set up integration**をクリックします。 - -4. 各画面の指示に従って、該当するフィールドに入力します。この統合では、所定の画面で次のオプションを選択します。 - - 1. **Choose Data type(s)**： Metrics - 2. **Choose a setup method**： Automate AWS with CloudFormation (Recommended) - 3. **Choose a metrics integration type**： CloudWatch Metric Stream (Recommended) - -5. CloudWatch メトリックストリームでサポートされていないサービスを使用している場合は、 **Choose a metrics integration type**ページで、 APIポーリングの 3 番目のステップで**Yes**を選択して続行します。 - - AWS Integration with CWMS and API Polling - -
    - サポートされていないサービスに対して選択された ポーリングによる サービスの CWMS 統合。AWSAPI -
    - - **Enable API Polling (optional)**ページの指示に従って必要な設定を行い、続行します。 - -6. Auto-discovery マップ上の AWS エンティティ間の関係を自動的に検出して視覚化し、その他の柔軟性も活用します。詳細については、 [「AWS エンティティの自動検出」](/docs/infrastructure/amazon-integrations/connect/set-up-auto-discovery-of-aws-entities/)を参照してください。この機能が必要な場合は、 **Enable Auto Discovery (optional)**ページで有効にして続行してください。 - -7. **Launch your CloudFormation in AWS**をクリックします。CloudFormationAWS New Relicテンプレートは、 での選択に基づいて構成された とともに コンソールで開くため、変更を加えない限り追加の編集は必要ありません。 - -8. ライセンスキーを AWS コンソールに貼り付けます。 - -9. Cloudformation スタックをデプロイするには、AWS コンソールで**Create stack**選択します。スタック リソースの作成には数分かかる場合があり、メトリクス転送の構成によっては複数のスタックが生成される場合があります。 スタックの作成に失敗した場合は、 [トラブルシューティング手順](https://docs.newrelic.com/docs/logs/troubleshooting/aws-log-integration-issues/stack-creation-fails/)を参照してください。 - -10. スタックの作成が成功したら、New Relic プラットフォームに切り替えて、AWS にNew Relic データが表示されるまでガイド付き統合を続行します。 - -## 関連トピック [#related-topics] - - - - 複数の AWS アカウントからデータを収集する方法を学びます。 - - - - CloudWatch メトリック ストリームからメトリクスを探索して使用します。 - - \ No newline at end of file diff --git a/src/i18n/content/jp/docs/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 deleted file mode 100644 index ba8578a471f..00000000000 --- a/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx +++ /dev/null @@ -1,267 +0,0 @@ ---- -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/)を追加 -* Added AWS integration via [CloudFormation and CloudWatch Metric Streams](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms/), supporting API Polling for unsupported services. -* 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/)を更新しました。 -* Added seamless integration for [AWS with New Relic utilizing CloudFormation and CloudWatch Metric Streams](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms/), including support for API polling. - -### マイナーチェンジ - -* [境界トレース](/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 deleted file mode 100644 index 9e024f7adf7..00000000000 --- a/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx +++ /dev/null @@ -1,60 +0,0 @@ ---- -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 deleted file mode 100644 index a7591ff8b81..00000000000 --- a/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-8-14-2025.mdx +++ /dev/null @@ -1,112 +0,0 @@ ---- -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 deleted file mode 100644 index 5e0abc2d13d..00000000000 --- a/src/i18n/content/jp/docs/release-notes/docs-release-notes/docs-9-12-2025.mdx +++ /dev/null @@ -1,94 +0,0 @@ ---- -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/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 deleted file mode 100644 index 6e5b982a15b..00000000000 --- a/src/i18n/content/jp/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx +++ /dev/null @@ -1,39 +0,0 @@ ---- -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 deleted file mode 100644 index 9d3fed96462..00000000000 --- a/src/i18n/content/jp/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.297.mdx +++ /dev/null @@ -1,27 +0,0 @@ ---- -subject: Browser agent -releaseDate: '2025-09-17' -version: 1.297.1 -downloadLink: 'https://www.npmjs.com/package/@newrelic/browser-agent' -features: [] -bugs: - - Prevent double import of Session Replay aggregate class -security: [] -translationType: machine ---- - -## バージョン1.297.1 - -### バグ修正 - -#### セッションリプレイ集約クラスの二重インポートを防止する - -newrelic.recordReplay の使用時にセッションリプレイ集約クラスが二重にインポートされる可能性がある問題を修正しました。プリロード中の API メソッドが有効になりました。 - -## サポートステートメント - -New Relic では、最新の機能とパフォーマンス上のメリットを確実に得られるよう、エージェントを定期的にアップグレードすることをお勧めします。古いリリースは[サポート終了](https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/browser-agent-eol-policy/)になるとサポートされなくなります。リリース日は、エージェント バージョンの元の公開日を反映します。 - -新しいブラウザエージェントのリリースは、一定期間にわたって小さな段階で顧客に展開されます。 このため、リリースがアカウントでアクセス可能になる日付は、元の公開日と一致しない可能性があります。詳細については、この[ステータス ダッシュボード](https://newrelic.github.io/newrelic-browser-agent-release/)をご覧ください。 - -弊社の[ブラウザ サポート ポリシー](https://docs.newrelic.com/docs/browser/new-relic-browser/getting-started/compatibility-requirements-browser-monitoring/#browser-types)に従い、 Browserの v1.297.1 は、 Chrome 130 ～ 140、Edge 130 ～ 140、Safari 17 ～ 19、Firefox 132 ～ 142 のブラウザとバージョン範囲向けに構築され、テストされました。 モバイル デバイスの場合、v1.297.1 は Android OS 16 および iOS Safari 17-18.5 用に構築およびテストされました。 \ No newline at end of file diff --git a/src/i18n/content/jp/docs/release-notes/synthetics-release-notes/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 deleted file mode 100644 index 0c207aa8cb7..00000000000 --- a/src/i18n/content/jp/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.mdx +++ /dev/null @@ -1,10 +0,0 @@ ---- -subject: Node API runtime -releaseDate: '2025-08-13' -version: 1.2.124 -translationType: machine ---- - -### 修正 - -* Node API ランタイムのセキュリティ脆弱性に対処するために、根本的な Ubuntu の脆弱性を修正しました。 \ 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 deleted file mode 100644 index ccb18f70339..00000000000 --- a/src/i18n/content/jp/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.mdx +++ /dev/null @@ -1,10 +0,0 @@ ---- -subject: Node browser runtime -releaseDate: '2025-08-13' -version: 3.0.41 -translationType: machine ---- - -### 改良点 - -* ノードBrowserランタイムのセキュリティの脆弱性に対処するために、tmp CVE-2025-54798 の脆弱性と基盤となる Ubuntu の脆弱性を修正しました。 \ 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 deleted file mode 100644 index d3726ad0d76..00000000000 --- a/src/i18n/content/jp/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.54.mdx +++ /dev/null @@ -1,10 +0,0 @@ ---- -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 deleted file mode 100644 index 65be8f0b577..00000000000 --- a/src/i18n/content/kr/docs/accounts/accounts-billing/new-relic-one-pricing-billing/add-on-billing.mdx +++ /dev/null @@ -1,28 +0,0 @@ ---- -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 deleted file mode 100644 index 4e466ace0f4..00000000000 --- a/src/i18n/content/kr/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing.mdx +++ /dev/null @@ -1,354 +0,0 @@ ---- -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/cci/getting-started/overview.mdx b/src/i18n/content/kr/docs/cci/getting-started/overview.mdx deleted file mode 100644 index f74d6cf9df0..00000000000 --- a/src/i18n/content/kr/docs/cci/getting-started/overview.mdx +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: '클라우드 비용 인텔리전스: cloud 지출을 관리하세요' -metaDescription: 'Gain comprehensive visibility and control over AWS cloud costs with CCI, enhancing your FinOps strategy for holistic cost management.' -freshnessValidatedDate: never -translationType: machine ---- - - - 이 기능은 아직 개발 중이지만 꼭 사용해 보시기 바랍니다! - - 이 기능은 현재 [출시 전 정책](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy) 에 따라 미리보기 프로그램의 일부로 제공됩니다. - - -클라우드 컴퓨팅 인텔리전스는 cloud 비용에 대한 가시성과 관리를 제공하도록 설계되었습니다. 클라우드 컴퓨팅 인텔리전스 AI 모니터링은 비용 가시성과 어셈블리 옵저버빌리티 간의 격차를 해소하여 cloud 지출에 대한 전체적인 보기를 제공합니다. - -예를 들어, 대기업이 클라우드 서비스 사용을 빠르게 확장함에 따라 cloud 비용을 추적하고 관리하는 일이 점점 더 복잡해질 수 있습니다. 클라우드 비용 인텔리전스는 귀하의 자금이 어디에 할당되는지 인사이트를 제공하여 지원합니다. 이를 통해 잠재적으로 비용을 절감할 수 있는 분야를 파악하는 데 도움이 될 수 있습니다. cloud 지출을 실제 사용량에 맞게 조정하면 전략적 성장 이니셔티브를 계속 지원하는 동시에 예산을 최적화할 수 있습니다. 이러한 접근 방식은 귀하가 투자한 모든 달러가 회사의 전반적인 성공에 기여하도록 보장하는 데 도움이 됩니다. - - - 현재는 의 cloud 비용만 AWS 지원됩니다. - - -Cloud Cost Intelligence summary page showing total costs, real-time cost estimates, average cost by day, and top 5 cost variance - -## 주요 특징들 - -### 포괄적인 비용 가시성 - -* **범주별 분석:** 애플리케이션, 서비스, 소유 팀, 지역별로 세분화된 cloud 비용을 확인하세요. -* **추세 분석:** 월별 비용 추세, 평균 비용, 주요 비용 요인을 파악하세요. - -### Kubernetes 비용 할당 - -Kubernetes 관련 비용에 대한 가시성을 확보하세요. 우리는 뉴렐릭의 텔레메트리 데이터를 활용하여 제작 이름별로 비용을 분류합니다. - -### 실시간 비용 추정 - -클라우드 비용 인텔리전스는 텔레메트리 데이터와 과거 비용 패턴을 활용하여 리소스 프로비저닝 후 1시간 이내에 변경 사항을 반영하는 시간별 비용 업데이트를 제공합니다. 청구 데이터와 통합하면 지난주 평균 단가와 최근 48시간 동안의 뉴렐릭 텔레메트리 데이터를 기반으로 비용을 추정할 수 있습니다. 이러한 통합이 없으면 추정치는 잠재적으로 더 높은 표준 단위 가격으로 기본 설정됩니다. - -가장 정확한 추정을 위해서는 텔레메트리를 통합하고 최소 7일간의 이력 데이터를 유지하세요. 이 데이터는 동일한 인스턴스에 대한 비용을 계산하는 데 도움이 됩니다. 이러한 데이터가 없는 경우 추정치는 cloud 공급업체가 사용하는 표준적인 사용량 기반 지불 모델인 주문형 가격 책정으로 회귀합니다. - - - **교차 계정 데이터 수집**
    클라우드 비용 인텔리전스의 범위는 사용자이며 뉴렐릭 사용자 자격 증명과 관련된 모든 계정에서 스프레드시트 데이터를 수집합니다. 즉 클라우드 인텔 뉴리전스에 대해 단일 뉴렐릭 계정을 사용하더라도 귀하가 액세스할 수 있는 추가 뉴렐릭 계정의 텔레메트리 데이터도 해당 단일 뉴렐릭 계정 내에서 수집되고 표시됩니다. 사용자 계정 권한이 내부 정책에 부합하는지 확인하고, 보고 싶은 뉴렐릭 계정에 대한 데이터 액세스를 허용하세요. -     - -## 클라우드 솔루션 인텔리전스가 스토리지 솔루션을 통해 cloud 비용을 회수하는 방법 [#fetch-costs] - -클라우드 비용 인텔리전스는 설정 및 통합이 완료되면 지정된 S3 버킷에 있는 AWS 비용 및 사용 보고서(CUR)에 자동으로 액세스합니다. 이 과정은 귀하의 승인과 접근 권한 제공으로 시작됩니다. 클라우드 비용 인텔리전스는 데이터를 지정된 S3 버킷으로 내보낸 후에만 보고서를 가져올 수 있다는 점에 유의하는 것이 중요합니다. [필수 구성 요소](/docs/cci/getting-started/prerequisites) 에 지정된 대로 S3 경로 접두사가 cost-and-usage-reports로 설정되어 있는지 확인하세요. - -일반적으로 AWS CUR을 하루에 세 번 업데이트하고, 클라우드는 설정 후 1시간에 한 번씩 S3 버킷에서 CUR을 검색합니다. 클라우드 비용 인텔리전스는 AWS 업데이트를 제공하고 그 직후 클라우드 비용 인텔리전스가 이를 검색하면 귀하의 최신 CUR이 표시됩니다. - - - **귀하의 데이터 개인정보 보호**
    CUR은 클라우드 서비스 사용 및 비용에 대한 데이터로, 개인 데이터는 포함되어서는 안 됩니다. CUR을 S3 버킷에 추가하고 뉴렐릭에 업로드하기 전에 전송하는 데이터에 개인 식별 정보나 민감한 정보가 없는지 확인하세요. 현재 CUR 데이터 삭제는 지원되지 않습니다. 개인 식별 정보나 민감한 정보를 사용하여 CUR을 생성하지 않는 것이 좋습니다. - - **데이터 수집:** 당사의 현재 데이터 삭제 정책은 데이터를 최대 5년 동안 유지하는 것입니다. 2년 후, 데이터는 비용이 저렴하고 검색 시간이 긴 저장 옵션인 AWS Glacier로 이동됩니다. - - **액세스 보기:** 설치 중에 귀하가 선택한 뉴렐릭 계정에 액세스할 수 있는 사람은 누구나 해양 인텔리전스 내의 모든 데이터를 볼 수 있다는 점에 유의하십시오. RBAC 및 액세스 정책 요구 사항에 맞는 적절한 액세스 권한이 있는 계정을 선택하세요. -     - -### 데이터 분석 및 보고 - -클라우드 인텔리전스는 CUR 데이터를 검색한 후 이 정보를 처리 및 분석하여 대시보드에 실행 가능한 인사이트를 제시합니다. cloud 사용에 따른 재정적 영향을 명확하게 시각화하여 비용 요인과 최적화 가능한 영역을 파악할 수 있습니다. \ No newline at end of file diff --git a/src/i18n/content/kr/docs/cci/getting-started/setup.mdx b/src/i18n/content/kr/docs/cci/getting-started/setup.mdx deleted file mode 100644 index a1c71be18bb..00000000000 --- a/src/i18n/content/kr/docs/cci/getting-started/setup.mdx +++ /dev/null @@ -1,83 +0,0 @@ ---- -title: CCI 설정 -metaDescription: Set up Cloud Cost Intelligence with AWS. Configure IAM roles and data paths for detailed cost analysis and streamlined access in New Relic. -freshnessValidatedDate: never -translationType: machine ---- - - - 이 기능은 아직 개발 중이지만 꼭 사용해 보시기 바랍니다! - - 이 기능은 현재 [출시 전 정책](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy) 에 따라 미리보기 프로그램의 일부로 제공됩니다. - - -IAM 역할 및 데이터 내보내기 경로를 포함한 필수 통합 설정을 구성하여 AWS 에서 클라우드 솔루션 인텔리전스를 설정하는 방법을 알아보세요. 이 가이드에서는 뉴렐릭 플랫폼 내에서 자세한 비용 분석과 관리를 활성화하는 데 필요한 단계를 안내합니다. - -클라우드 비용 인텔리전스를 구성하려면 다음 단계를 따르십시오. - - - - ## 통합을 시작하세요 - - 왼쪽 패널에서 **Cloud Cost Intelligence** \[클라우드 매트리스 인텔리전스를] 클릭한 후 **Add the integration** \[통합 추가를] 클릭하세요. 또는 왼쪽 패널에서 **Integrations & Agents** \[통합 & 에이전트를] 클릭하고 모든 기능 중에서 클라우드 비용 인텔리전스를 찾은 다음 **Cloud Cost Intelligence** \[클라우드 비용 인텔리전스를] 클릭하세요. - - - - ## 계정 선택 - - 설정에 사용할 뉴렐릭 계정을 선택하고 **Continue** \[계속을] 클릭하세요. - - - - ## 연결 세부 정보 제공 - - AWS에서 비용 데이터를 가져오는 데 필요한 다음 세부 정보를 입력하세요. - - * **연결 이름:** 기본적으로 입력됩니다. 원하는 경우 사용자 정의 이름을 편집하세요. - * **교차 계정 IAM 역할 ARN:** 클라우드 인텔리전스가 S3 버킷에 액세스하기 위해 맡게 될 IAM 역할에 대한 Amazon 리소스 이름(ARN)입니다. ARN은 IAM 역할을 포함한 다양한 AWS 리소스에 대한 고유 식별자입니다. 여기에는 서비스, 지역, 계정 ID, 리소스 세부 정보(예: `arn:aws:iam:::role/` 를 포함하는 표준 형식이 따릅니다. - * **외부 ID:** 뉴렐릭 계정의 외부 ID를 복사하여 필수 구성 요소의 일부로 IAM 역할 설정에 추가합니다. AWS 계정의 IAM 역할에 대한 신뢰 정책에 이를 추가해야 합니다. - * **데이터 내보내기 이름:** 데이터 내보내기 파일의 이름입니다. 해당 CUR 파일에 대한 경로를 구성하는 데 사용됩니다. `cci-ingestion-test` 이라는 보고서의 경우 생성된 경로는 `cost-and-usage-reports/cci-ingestion-test/data` 입니다. CUR 데이터는 S3 버킷 내에 저장됩니다. - * **S3 버킷 이름:** S3 버킷의 정확한 이름입니다. `cost-and-usage-reports` 접두사가 포함되어 있는지 확인하세요. 최적의 성능과 비용 효율성을 위해 `us-east-2` 지역에 있는 S3 버킷을 사용하세요. - - - - ## 신뢰 정책 설정 - - IAM 역할의 신뢰 정책에 뉴렐릭 글로벌 사용자를 추가하고 역할 권한을 제공합니다. 이를 통해 클라우드 컴퓨팅 인텔리전스의 뉴켈릭 글로벌 사용자가 IAM 역할을 맡을 수 있습니다. - - 클라우드 분석 인텔리전스가 AWS 리소스에 액세스할 수 있도록 하려면 뉴렐릭 글로벌 사용자 `arn:aws:iam::207192125115:user/cci_global_user`) IAM 역할을 맡도록 허용하는 신뢰 정책을 AWS Management Console에서 구성하십시오. 아래는 신탁 정책 문서의 샘플입니다. - - ```json - { - "Version": "2012-10-17", - "Statement": [ - { - "Effect": "Allow", - "Principal": { - "AWS": "arn:aws:iam::207192125115:user/cci_global_user" - }, - "Action": "sts:AssumeRole", - "Condition": { - "StringEquals": { - "sts:ExternalId": "" - } - } - } - ] - } - ``` - - - * `sts:ExternalId` 은 보안에 중요한 구성 요소입니다. 이전 단계에서 복사한 외부 ID로 설정합니다. 이 ID는 뉴렐릭이 의도한 맥락에서만 역할을 수행하도록 보장하여 통합의 보안을 강화합니다. - * 리소스가 기본적으로 보안 토큰 서비스(STS)가 활성화되지 않은 AWS 지역(예: `ap-east-1`, `eu-south-1`)에 있는 경우 해당 지역에 대해 STS를 활성화합니다. - - - - - ## 연결 테스트 - - 마지막으로 AWS 환경에 대한 연결이 성공적인지 확인하기 위한 테스트를 시작합니다. - - - -성공적으로 설정한 후, 특히 처음 설정하는 경우 데이터가 뉴렐릭 UI 에 나타나기까지 몇 시간이 걸릴 수 있습니다. \ 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 deleted file mode 100644 index 301e808de43..00000000000 --- a/src/i18n/content/kr/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation.mdx +++ /dev/null @@ -1,70 +0,0 @@ ---- -title: CloudFormation 및 CloudWatch Metric Streams를 통해 통합 -tags: - - Integration via CloudFormation - - AWS metric integration - - Amazon integrations - - AWS integrations - - Integration with CloudWatch Metric Streams via CloudFormation -metaDescription: Integrate New Relic with AWS services using CloudFormation templates to automate the setup of CloudWatch Metric Streams for metrics ingestion. -freshnessValidatedDate: never -translationType: machine ---- - -AWS 계정을 뉴렐릭과 원활하게 통합하려면 이 통합 프로세스가 가장 권장됩니다. CloudWatch Metric Streams에서 지원하지 않는 서비스에도 API 폴링을 활용할 수 있습니다. - -## 전제 조건 [#prerequisites] - -AWS 계정을 뉴렐릭과 통합하기 전에 다음 필수 조건을 충족하는지 확인하세요. - -* **뉴렐릭 [클러스터 키](https://one.newrelic.com/api-keys)**: AWS 서비스를 뉴베리 계정에 연결하려면 클러스터 키가 필요합니다. -* **[새로운 리소스](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html)** 및 IAM 역할을 구현하고 배포하기 위한 **[권한](https://docs.aws.amazon.com/ARG/latest/userguide/gettingstarted-prereqs-permissions.html)** AWS :AWS 계정에 이 권한이 필요합니다. -* 클라우드 통합 **[권한](/docs/accounts/accounts-billing/new-relic-one-user-management/user-permissions/#infrastructure)** : 뉴렐릭 계정에 대해 다음 권한이 필요합니다. - -## 통합 단계 [#integration-steps] - -CloudFormation 및 사용하여 계정을 뉴렐릭과 통합하려면 AWS CloudWatch Metric Streams 다음 단계를 따르세요. - -1. [**Infrastructure > AWS**](https://one.newrelic.com/infra/infrastructure/cloud-aws) 로 이동합니다. - -2. 올바른 계정을 선택하세요. - -3. **Set up integration** 을(를) 클릭합니다. - -4. 각 화면의 지시를 따르고, 귀하에게 해당하는 필드를 작성하세요. 이 통합을 위해 주어진 화면에서 다음 옵션을 선택하세요. - - 1. **Choose Data type(s)**: Metrics - 2. **Choose a setup method**: Automate AWS with CloudFormation (Recommended) - 3. **Choose a metrics integration type**: CloudWatch Metric Stream (Recommended) - -5. CloudWatch Metric Streams에서 지원되지 않는 서비스를 사용하는 경우 **Choose a metrics integration type** 페이지에서 API 폴링을 위한 세 번째 단계에서 **Yes** 선택하고 계속 진행합니다. - - AWS Integration with CWMS and API Polling - -
    - 지원되지 않는 서비스에 대해 선택된 API 폴링을 통해 AWS 서비스와 CWMS가 통합되었습니다. -
    - - **Enable API Polling (optional)** 페이지에 안내된 대로 필요한 설정을 수행하고 계속 진행하세요. - -6. Auto-discovery AWS 와 관련된 관계를 지도에서 자동으로 감지하고 시각화하며, 다른 몇 가지 유연성을 활용합니다. 자세한 내용은 [AWS 자동 검색을](/docs/infrastructure/amazon-integrations/connect/set-up-auto-discovery-of-aws-entities/) 참조하세요. 이 기능을 원하시면 **Enable Auto Discovery (optional)** 페이지에서 해당 기능을 활성화하고 계속 진행하세요. - -7. **Launch your CloudFormation in AWS** 클릭하세요. CloudFormation 템플릿은 AWS 콘솔에서 구성된 파라미터와 함께 열립니다. 파라미터는 뉴렐릭에서 선택한 내용에 따라 달라지므로, 변경하려는 경우가 아니면 추가 편집이 필요하지 않습니다. - -8. AWS 콘솔에 라이선스 키를 붙여넣습니다. - -9. Cloudformation 그리드를 구현하거나 배포하려면 AWS 콘솔에서 **Create stack** 선택합니다. 택시 리소스를 만드는 데는 몇 분이 걸릴 수 있으며, 택시 전달을 구성하는 방법에 따라 여러 택시가 생성될 수 있습니다. 그리드 생성에 실패할 경우 [문제 해결, 해결 절차를](https://docs.newrelic.com/docs/logs/troubleshooting/aws-log-integration-issues/stack-creation-fails/) 참조하세요. - -10. 그리드 생성이 성공적으로 완료되면 뉴렐릭 플랫폼으로 전환하고 뉴렐릭에서 AWS 데이터가 표시될 때까지 통합 안내를 계속 진행하세요. - -## 관련 주제 [#related-topics] - - - - 여러 AWS 계정에서 데이터를 수집하는 방법을 알아보세요. - - - - CloudWatch Metric Streams의 지표를 탐색하고 사용하세요. - - \ No newline at end of file diff --git a/src/i18n/content/kr/docs/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 deleted file mode 100644 index 3d4cc02fcba..00000000000 --- a/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx +++ /dev/null @@ -1,267 +0,0 @@ ---- -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/)추가 -* Added AWS integration via [CloudFormation and CloudWatch Metric Streams](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms/), supporting API Polling for unsupported services. -* 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/) 업데이트했습니다. -* Added seamless integration for [AWS with New Relic utilizing CloudFormation and CloudWatch Metric Streams](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms/), including support for API polling. - -### 사소한 변경 사항 - -* [프로세서 트레이스](/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 deleted file mode 100644 index e6aff2f120f..00000000000 --- a/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-8-01-2025.mdx +++ /dev/null @@ -1,99 +0,0 @@ ---- -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 deleted file mode 100644 index 8223f140d0d..00000000000 --- a/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx +++ /dev/null @@ -1,60 +0,0 @@ ---- -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 deleted file mode 100644 index aa88f66f598..00000000000 --- a/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-8-14-2025.mdx +++ /dev/null @@ -1,112 +0,0 @@ ---- -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 deleted file mode 100644 index 690e192131c..00000000000 --- a/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-8-21-2025.mdx +++ /dev/null @@ -1,56 +0,0 @@ ---- -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 deleted file mode 100644 index b882f2ec86d..00000000000 --- a/src/i18n/content/kr/docs/release-notes/docs-release-notes/docs-9-12-2025.mdx +++ /dev/null @@ -1,94 +0,0 @@ ---- -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/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 deleted file mode 100644 index d2e754e3a25..00000000000 --- a/src/i18n/content/kr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx +++ /dev/null @@ -1,39 +0,0 @@ ---- -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 deleted file mode 100644 index 6325fc4941e..00000000000 --- a/src/i18n/content/kr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.296.mdx +++ /dev/null @@ -1,34 +0,0 @@ ---- -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 deleted file mode 100644 index 67041e6d551..00000000000 --- a/src/i18n/content/kr/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.297.mdx +++ /dev/null @@ -1,27 +0,0 @@ ---- -subject: Browser agent -releaseDate: '2025-09-17' -version: 1.297.1 -downloadLink: 'https://www.npmjs.com/package/@newrelic/browser-agent' -features: [] -bugs: - - Prevent double import of Session Replay aggregate class -security: [] -translationType: machine ---- - -## v1.297.1 - -### 버그 수정 - -#### 세션 리플레이 집계 클래스 이중 가져오기 방지 - -newrelic.recordReplay를 사용할 때 세션 재생 집계 클래스를 두 번 가져올 수 있는 문제가 발견되었습니다. 사전 로딩이 활성화된 동안 API 메서드가 활성화되었습니다. - -## 지지 성명 - -뉴렐릭은 에이전트를 정기적으로 업그레이드하여 최신 기능과 성능 이점을 얻을 것을 권장합니다. 이전 릴리스는 지원 [종료](https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/browser-agent-eol-policy/) 시점부터 더 이상 지원되지 않습니다. 출시일은 에이전트 버전의 원래 출판일을 반영합니다. - -새로운 브라우저 에이전트 릴리스는 일정 기간 동안 작은 단계로 고객에게 출시됩니다. 이로 인해, 귀하의 계정에서 해당 릴리스에 접근할 수 있는 날짜가 원래 게시 날짜와 일치하지 않을 수 있습니다. 자세한 내용은 이 [상태 대시보드를](https://newrelic.github.io/newrelic-browser-agent-release/) 참조하세요. - -[브라우저 지원 정책](https://docs.newrelic.com/docs/browser/new-relic-browser/getting-started/compatibility-requirements-browser-monitoring/#browser-types) 에 따라, 브라우저 에이전트 v1.297.1은 다음 브라우저 및 버전 범위에 맞춰 빌드되고 테스트되었습니다: Chrome 130-140, Edge 130-140, Safari 17-19, Firefox 132-142. 모바일 장치의 경우 v1.297.1은 Android OS 16 및 iOS Safari 17-18.5에 대해 구축 및 테스트되었습니다. \ No newline at end of file diff --git a/src/i18n/content/kr/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.mdx b/src/i18n/content/kr/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.mdx deleted file mode 100644 index d53ad8a17ec..00000000000 --- a/src/i18n/content/kr/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.mdx +++ /dev/null @@ -1,10 +0,0 @@ ---- -subject: Node API runtime -releaseDate: '2025-08-13' -version: 1.2.124 -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 deleted file mode 100644 index 5d74d8e0aff..00000000000 --- a/src/i18n/content/kr/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.mdx +++ /dev/null @@ -1,10 +0,0 @@ ---- -subject: Node browser runtime -releaseDate: '2025-08-13' -version: 3.0.41 -translationType: machine ---- - -### 개량 - -* 노드 브라우저 런타임의 보안 교육을 해결하기 위해 tmp CVE-2025-54798 돋보기 및 기본 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 deleted file mode 100644 index d0c4af0c3c3..00000000000 --- a/src/i18n/content/kr/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.53.mdx +++ /dev/null @@ -1,10 +0,0 @@ ---- -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 deleted file mode 100644 index 1e9b8e6103d..00000000000 --- a/src/i18n/content/kr/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.54.mdx +++ /dev/null @@ -1,10 +0,0 @@ ---- -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 deleted file mode 100644 index 518f9563586..00000000000 --- a/src/i18n/content/pt/docs/accounts/accounts-billing/new-relic-one-pricing-billing/add-on-billing.mdx +++ /dev/null @@ -1,28 +0,0 @@ ---- -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 deleted file mode 100644 index 6d724b3c3f9..00000000000 --- a/src/i18n/content/pt/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing.mdx +++ /dev/null @@ -1,354 +0,0 @@ ---- -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/cci/getting-started/overview.mdx b/src/i18n/content/pt/docs/cci/getting-started/overview.mdx deleted file mode 100644 index 8d94dc1e539..00000000000 --- a/src/i18n/content/pt/docs/cci/getting-started/overview.mdx +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: 'Inteligência de Custos na Nuvem: Assuma o controle dos seus gastos cloud' -metaDescription: 'Gain comprehensive visibility and control over AWS cloud costs with CCI, enhancing your FinOps strategy for holistic cost management.' -freshnessValidatedDate: never -translationType: machine ---- - - - Ainda estamos trabalhando nesse recurso, mas adoraríamos que você experimentasse! - - Atualmente, esse recurso é fornecido como parte de um programa de visualização de acordo com nossas [políticas de pré-lançamento](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). - - -A Inteligência de Custos na Nuvem foi projetada para fornecer visibilidade e gerenciamento dos custos cloud. Inteligência de Custos na Nuvem AI Monitoring para preencher a lacuna entre visibilidade de custos e observabilidade de infraestrutura, oferecendo uma visão holística de seus gastos cloud. - -Por exemplo, à medida que sua grande empresa expande rapidamente o uso de serviços na nuvem, rastrear e gerenciar despesas cloud pode se tornar cada vez mais complexo. A Inteligência de Custos na Nuvem auxilia fornecendo insights sobre onde seu dinheiro está sendo alocado. Isso pode ajudar você a identificar áreas com potencial de economia de custos. Ao alinhar os gastos cloud com o uso real, você pode otimizar seus orçamentos e continuar a dar suporte a iniciativas de crescimento estratégico. Essa abordagem ajuda a garantir que cada dólar investido contribua para o sucesso geral da sua empresa. - - - Atualmente, apenas os custos cloud da AWS são suportados. - - -Cloud Cost Intelligence summary page showing total costs, real-time cost estimates, average cost by day, and top 5 cost variance - -## Recurso chave - -### Visibilidade abrangente de custos - -* **Detalhamento por categoria:** visualize os custos cloud segmentados por aplicativo, serviço, equipe proprietária e região. -* **Análise de tendências:** obtenha insights sobre tendências de custos mês a mês, custos médios e principais impulsionadores de custos. - -### Alocação de custos do Kubernetes - -Obtenha visibilidade dos custos relacionados ao Kubernetes. Aproveitamos dados de telemetria do New Relic para detalhar custos por nome de aplicativo. - -### Estimativa de custos em tempo real - -A Inteligência de Custos na Nuvem aproveita dados de telemetria e padrões históricos de custos para fornecer atualizações de custos por hora, refletindo mudanças dentro de uma hora após o provisionamento de recursos. Essa integração com seus dados de cobrança permite estimativas de custos com base no preço unitário médio da semana anterior e nos dados de telemetria da New Relic do período recente de 48 horas. Sem essa integração, as estimativas tendem a taxas de preços unitários padrão potencialmente mais altas. - -Para estimativas mais precisas, integre a telemetria e mantenha pelo menos 7 dias de dados históricos. Esses dados ajudam a calcular custos para a mesma instância. Na ausência desses dados, as estimativas retornam ao preço sob demanda, o modelo padrão de pagamento conforme o uso usado por provedores cloud. - - - **Coleta de dados entre contas**
    A Inteligência de Custos na Nuvem tem como escopo o usuário e coleta dados de telemetria de todas as contas associadas às suas credenciais de usuário New Relic. Isso significa que, mesmo se você estiver usando uma única conta New Relic para Inteligência de Custos na Nuvem, os dados de telemetria de quaisquer contas New Relic adicionais às quais você tenha acesso também serão coletados e ficarão visíveis nessa única conta New Relic. Verifique se as permissões da sua conta de usuário estão de acordo com suas políticas internas e permita o acesso aos dados das contas do New Relic que você gostaria de visualizar. -     - -## Como a Inteligência de Custos na Nuvem recupera custos cloud por meio de soluções de armazenamento [#fetch-costs] - -A Inteligência de Custos na Nuvem acessa automaticamente seus Relatórios de Custo e Uso AWS (CUR) em seu bucket S3 designado assim que a configuração e a integração forem concluídas. Este processo começa com sua autorização e o fornecimento de permissões de acesso. É importante observar que a Inteligência de Custos na Nuvem só pode extrair relatórios depois que os dados forem exportados para o seu bucket S3 designado. Certifique-se de que o prefixo do caminho S3 esteja definido como cost-and-usage-reports, conforme especificado nos [pré-requisitos](/docs/cci/getting-started/prerequisites). - -Normalmente, AWS atualiza o CUR três vezes ao dia, e a Inteligência de Custos na Nuvem recupera o CUR do seu bucket S3 uma vez por hora após a configuração. Seu CUR mais recente ficará visível na Inteligência de Custos na Nuvem quando AWS fornecer sua atualização e a Inteligência de Custos na Nuvem a recuperar logo em seguida. - - - **A privacidade dos seus dados**
    CUR são dados sobre seu uso de serviços na Nuvem e seus custos, que não devem incluir dados pessoais. Certifique-se de que os dados enviados estejam livres de informações de identificação pessoal ou informações confidenciais antes de adicionar o CUR ao seu bucket S3 e antes de carregá-lo no New Relic. A exclusão de dados CUR não é suportada no momento. Recomendamos não gerar o CUR com informações de identificação pessoal ou informações confidenciais. - - **Retenção de dados:** Nossa política atual de retenção de dados é manter os dados por até 5 anos. Após 2 anos, os dados são movidos para o AWS Glacier, uma opção de armazenamento de menor custo com um tempo de recuperação maior. - - **Acesso de visualização:** Esteja ciente de que qualquer pessoa com acesso à conta New Relic que você selecionar durante a instalação poderá visualizar todos os dados dentro do Inteligência de Custos na Nuvem. Escolha uma conta com privilégios de acesso adequados para corresponder aos seus requisitos de RBAC e política de acesso. -     - -### Análise de dados e relatórios - -Após recuperar os dados do CUR, a Inteligência de Custos na Nuvem processa e analisa essas informações para apresentar insights acionáveis em seus dashboards. Você pode visualizar as implicações financeiras do uso cloud com clareza, identificando os geradores de custos e possíveis áreas de otimização. \ No newline at end of file diff --git a/src/i18n/content/pt/docs/cci/getting-started/setup.mdx b/src/i18n/content/pt/docs/cci/getting-started/setup.mdx deleted file mode 100644 index 3bdcc7b4192..00000000000 --- a/src/i18n/content/pt/docs/cci/getting-started/setup.mdx +++ /dev/null @@ -1,83 +0,0 @@ ---- -title: Configurar CCI -metaDescription: Set up Cloud Cost Intelligence with AWS. Configure IAM roles and data paths for detailed cost analysis and streamlined access in New Relic. -freshnessValidatedDate: never -translationType: machine ---- - - - Ainda estamos trabalhando nesse recurso, mas adoraríamos que você experimentasse! - - Atualmente, esse recurso é fornecido como parte de um programa de visualização de acordo com nossas [políticas de pré-lançamento](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). - - -Aprenda como configurar a Inteligência de Custos na Nuvem com AWS definindo configurações essenciais de integração, incluindo funções IAM e caminhos de exportação de dados. Este guia orienta você nas etapas necessárias para habilitar a análise e o gerenciamento detalhados de custos na sua plataforma New Relic. - -Siga estes passos para configurar a Inteligência de Custos na Nuvem: - - - - ## Comece a integrar - - Clique em **Cloud Cost Intelligence** no painel esquerdo e depois clique em **Add the integration**. Alternativamente, clique em **Integrations & Agents** no painel esquerdo, procure Inteligência de Custos na Nuvem entre todas as capacidades e depois clique em **Cloud Cost Intelligence**. - - - - ## Selecione a conta - - Selecione a conta New Relic que deseja usar para a configuração e clique em **Continue**. - - - - ## Forneça detalhes de conexão - - Insira os seguintes detalhes necessários para buscar dados de custo da AWS: - - * **Nome da conexão:** Preenchido por padrão. Edite se quiser um nome personalizado. - * **ARN da função do IAM entre contas:** o nome do recurso da Amazon (ARN) para a função do IAM que a Inteligência de Custos na Nuvem assumirá para acessar seu bucket do S3. Um ARN é um identificador exclusivo para vários recursos da AWS, incluindo funções do IAM. Ele segue um formato padrão que inclui o serviço, a região, a ID da conta e especificações do recurso, como `arn:aws:iam:::role/`. - * **ID externo:** copie o ID externo da sua conta do New Relic e adicione-o à configuração da sua função do IAM como parte dos pré-requisitos. Você precisa adicioná-lo à política de confiança da função do IAM na sua conta da AWS. - * **Nome da exportação de dados:** O nome do arquivo de exportação de dados. Usado para construir o caminho para o arquivo CUR correspondente. Para um relatório chamado `cci-ingestion-test`, o caminho construído seria `cost-and-usage-reports/cci-ingestion-test/data`. É aqui que os dados CUR são armazenados dentro do bucket S3. - * **Nome do bucket S3:** o nome exato do seu bucket S3. Certifique-se de que inclui o prefixo `cost-and-usage-reports`. Use um bucket S3 localizado na região `us-east-2` para obter desempenho ideal e eficiência de custos. - - - - ## Estabelecer uma política de confiança - - Adicione o usuário global do New Relic à política de confiança da sua função do IAM e forneça permissões de função. Isso permite que o usuário global de Inteligência de Custos na Nuvem New Relic assuma a função de IAM. - - Para permitir que a Inteligência de Custos na Nuvem acesse seus recursos AWS, configure uma política de confiança no seu AWS Management Console que permita que o usuário global New Relic, `arn:aws:iam::207192125115:user/cci_global_user`, assuma uma função do IAM. Abaixo está um exemplo de documento de política de confiança: - - ```json - { - "Version": "2012-10-17", - "Statement": [ - { - "Effect": "Allow", - "Principal": { - "AWS": "arn:aws:iam::207192125115:user/cci_global_user" - }, - "Action": "sts:AssumeRole", - "Condition": { - "StringEquals": { - "sts:ExternalId": "" - } - } - } - ] - } - ``` - - - * O `sts:ExternalId` é um componente crítico para segurança. Defina-o como o ID externo que você copiou na etapa anterior. Esse ID garante que a função seja assumida apenas no contexto pretendido pelo New Relic, aumentando a segurança da sua integração. - * Se seus recursos estiverem em regiões AWS onde o Security Token Service (STS) não estiver ativo por padrão (por exemplo, `ap-east-1`, `eu-south-1`), ative o STS para essas regiões. - - - - - ## Conexão de teste - - Por fim, inicie um teste para verificar se a conexão com seu ambiente AWS foi bem-sucedida. - - - -Após uma configuração bem-sucedida, pode levar algumas horas para que os dados comecem a aparecer na interface do usuário do New Relic, especialmente durante a primeira configuração. \ 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 deleted file mode 100644 index f6b4ed7fdbd..00000000000 --- a/src/i18n/content/pt/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation.mdx +++ /dev/null @@ -1,70 +0,0 @@ ---- -title: Integrar via CloudFormation e CloudWatch Metric Streams -tags: - - Integration via CloudFormation - - AWS metric integration - - Amazon integrations - - AWS integrations - - Integration with CloudWatch Metric Streams via CloudFormation -metaDescription: Integrate New Relic with AWS services using CloudFormation templates to automate the setup of CloudWatch Metric Streams for metrics ingestion. -freshnessValidatedDate: never -translationType: machine ---- - -Para uma integração perfeita da sua conta da AWS com o New Relic, este é o processo de integração mais recomendado. Você pode utilizar API Polling para serviços não suportados pelo CloudWatch Metric Streams. - -## Pré-requisitos [#prerequisites] - -Antes de começar a integrar sua conta da AWS com o New Relic, certifique-se de atender aos seguintes pré-requisitos: - -* **Uma [chave de licença](https://one.newrelic.com/api-keys)do New Relic**: você precisará de uma chave de licença para conectar seus serviços da AWS à sua conta do New Relic. -* **[Permissões](https://docs.aws.amazon.com/ARG/latest/userguide/gettingstarted-prereqs-permissions.html)** para implantar novos recursos da AWS e **[funções do IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html)**: você precisará dessa permissão para sua conta da AWS. -* **[Permissões](/docs/accounts/accounts-billing/new-relic-one-user-management/user-permissions/#infrastructure)** para integração na nuvem: Você precisará dessas permissões para sua conta New Relic. - -## Etapas de integração [#integration-steps] - -Para integrar sua conta da AWS com o New Relic usando o CloudFormation e o CloudWatch Metric Streams, siga estas etapas: - -1. Navegue até [**Infrastructure > AWS**](https://one.newrelic.com/infra/infrastructure/cloud-aws). - -2. Selecione a conta correta. - -3. Clique em **Set up integration**. - -4. Siga as instruções em cada tela e preencha os campos que se aplicam a você. Para esta integração, escolha as seguintes opções nas telas fornecidas: - - 1. **Choose Data type(s)**: Metrics - 2. **Choose a setup method**: Automate AWS with CloudFormation (Recommended) - 3. **Choose a metrics integration type**: CloudWatch Metric Stream (Recommended) - -5. Se você estiver usando algum dos serviços que não são suportados no CloudWatch Metric Streams, na página **Choose a metrics integration type**, selecione **Yes** na terceira etapa para pesquisa API e continue. - - AWS Integration with CWMS and API Polling - -
    - CWMS integração de serviços da AWS com sondagem API selecionada para serviços não suportados. -
    - - Faça a configuração necessária conforme orientado na página **Enable API Polling (optional)** e continue. - -6. Auto-discovery detecta e visualiza automaticamente os relacionamentos entre suas entidades AWS em mapas e aproveita algumas outras flexibilidades. Para mais detalhes, consulte [Descoberta automática de entidade AWS ](/docs/infrastructure/amazon-integrations/connect/set-up-auto-discovery-of-aws-entities/). Se você quiser esse recurso, ative-o na página **Enable Auto Discovery (optional)** e continue. - -7. Clique em **Launch your CloudFormation in AWS**. O modelo do CloudFormation é aberto no seu console AWS com o parâmetro configurado com base nas suas seleções no New Relic, portanto, nenhuma edição adicional é necessária, a menos que você queira fazer alterações. - -8. Cole sua chave de licença no console da AWS. - -9. Para implantar a stack Cloudformation, no console AWS, selecione **Create stack**. A criação dos recursos stack pode levar vários minutos e pode gerar múltiplas pilhas, dependendo de como você configura o encaminhamento métrico. Se a criação stack falhar, consulte o [procedimento de resolução de problemas](https://docs.newrelic.com/docs/logs/troubleshooting/aws-log-integration-issues/stack-creation-fails/). - -10. Após a criação bem-sucedida stack, mude para a plataforma New Relic e continue com a integração guiada até ver seus dados AWS no New Relic. - -## Tópicos relacionados [#related-topics] - - - - Aprenda a coletar dados de várias contas da AWS. - - - - Explore e use o métrica do CloudWatch Metric Streams. - - \ No newline at end of file diff --git a/src/i18n/content/pt/docs/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 deleted file mode 100644 index e9db937cdd3..00000000000 --- a/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-7-25-2025.mdx +++ /dev/null @@ -1,267 +0,0 @@ ---- -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/) -* Added AWS integration via [CloudFormation and CloudWatch Metric Streams](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms/), supporting API Polling for unsupported services. -* 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/) -* Added seamless integration for [AWS with New Relic utilizing CloudFormation and CloudWatch Metric Streams](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms/), including support for API polling. - -### 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 deleted file mode 100644 index 465d315090e..00000000000 --- a/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-8-01-2025.mdx +++ /dev/null @@ -1,99 +0,0 @@ ---- -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 deleted file mode 100644 index 56fc49bcdf6..00000000000 --- a/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-8-08-2025.mdx +++ /dev/null @@ -1,60 +0,0 @@ ---- -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 deleted file mode 100644 index 1ca88ca0ec1..00000000000 --- a/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-8-14-2025.mdx +++ /dev/null @@ -1,112 +0,0 @@ ---- -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 deleted file mode 100644 index bb5951d3f88..00000000000 --- a/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-8-21-2025.mdx +++ /dev/null @@ -1,56 +0,0 @@ ---- -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 deleted file mode 100644 index 9d88cfd440c..00000000000 --- a/src/i18n/content/pt/docs/release-notes/docs-release-notes/docs-9-12-2025.mdx +++ /dev/null @@ -1,94 +0,0 @@ ---- -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/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 deleted file mode 100644 index 3cf842161b5..00000000000 --- a/src/i18n/content/pt/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.mdx +++ /dev/null @@ -1,39 +0,0 @@ ---- -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 deleted file mode 100644 index 2f08aaa8206..00000000000 --- a/src/i18n/content/pt/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.296.mdx +++ /dev/null @@ -1,34 +0,0 @@ ---- -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 deleted file mode 100644 index c5167cc6355..00000000000 --- a/src/i18n/content/pt/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.297.mdx +++ /dev/null @@ -1,27 +0,0 @@ ---- -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/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 deleted file mode 100644 index bf664907c81..00000000000 --- a/src/i18n/content/pt/docs/release-notes/synthetics-release-notes/node-api-runtime-release-notes/node-api-runtime-1.2.mdx +++ /dev/null @@ -1,10 +0,0 @@ ---- -subject: Node API runtime -releaseDate: '2025-08-13' -version: 1.2.124 -translationType: machine ---- - -### Correções - -* Corrigidas as vulnerabilidades subjacentes do Ubuntu para lidar com vulnerabilidades de segurança nos tempos de execução da 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 deleted file mode 100644 index da289930725..00000000000 --- a/src/i18n/content/pt/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.mdx +++ /dev/null @@ -1,10 +0,0 @@ ---- -subject: Node browser runtime -releaseDate: '2025-08-13' -version: 3.0.41 -translationType: machine ---- - -### Melhorias - -* Corrigidas as vulnerabilidades tmp CVE-2025-54798 e as vulnerabilidades subjacentes do Ubuntu para resolver vulnerabilidades de segurança nos 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 deleted file mode 100644 index 4bb67078ec7..00000000000 --- a/src/i18n/content/pt/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.53.mdx +++ /dev/null @@ -1,10 +0,0 @@ ---- -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 deleted file mode 100644 index b7b8a18c47c..00000000000 --- a/src/i18n/content/pt/docs/release-notes/synthetics-release-notes/ping-runtime-release-notes/ping-runtime-1.54.mdx +++ /dev/null @@ -1,10 +0,0 @@ ---- -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 From c2dc6790a3d797390fb62f4798d6abe461db3391 Mon Sep 17 00:00:00 2001 From: Abhilash Dutta Date: Thu, 9 Oct 2025 20:22:30 +0530 Subject: [PATCH 10/21] Updated the google cloud platform --- src/content/docs/cci/google-cloud-platform-cci.mdx | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/src/content/docs/cci/google-cloud-platform-cci.mdx b/src/content/docs/cci/google-cloud-platform-cci.mdx index 26ac88f7f3f..c21db1593ad 100644 --- a/src/content/docs/cci/google-cloud-platform-cci.mdx +++ b/src/content/docs/cci/google-cloud-platform-cci.mdx @@ -4,4 +4,9 @@ metaDescription: Connect your Google Cloud Platform billing to New Relic Cloud C freshnessValidatedDate: never --- -This page needs to be updated \ No newline at end of file + + We're still working on this feature, but we'd love for you to try it out! + + This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). + + From ebc3b0d86719624b439bc41fc7654ebabe3cdb47 Mon Sep 17 00:00:00 2001 From: Abhilash Dutta Date: Thu, 9 Oct 2025 20:24:42 +0530 Subject: [PATCH 11/21] Updated the navigation --- src/nav/cci.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/nav/cci.yml b/src/nav/cci.yml index 5cbd93c1b54..e1a46c93fc8 100644 --- a/src/nav/cci.yml +++ b/src/nav/cci.yml @@ -10,7 +10,7 @@ pages: - title: Azure CCI path: /docs/cci/cci-azure - title: Google Cloud Platform CCI - path: /docs/cci/cci-gcp + path: /docs/cci/google-cloud-platform-cci - title: Configure Cloud Cost Intelligence pages: - title: General settings From 3aed87e536a0f65ed8229a98c196d04b6a3865ec Mon Sep 17 00:00:00 2001 From: Abhilash Dutta Date: Fri, 10 Oct 2025 18:32:34 +0530 Subject: [PATCH 12/21] Updatd the GCP document --- .../docs/cci/google-cloud-platform-cci.mdx | 31 ++++++++++++++++++- 1 file changed, 30 insertions(+), 1 deletion(-) diff --git a/src/content/docs/cci/google-cloud-platform-cci.mdx b/src/content/docs/cci/google-cloud-platform-cci.mdx index c21db1593ad..c66cc5f762b 100644 --- a/src/content/docs/cci/google-cloud-platform-cci.mdx +++ b/src/content/docs/cci/google-cloud-platform-cci.mdx @@ -1,5 +1,5 @@ --- -title: Google Cloud Platform CCI +title: Cloud Cost Intelligence - Google Cloud Platform metaDescription: Connect your Google Cloud Platform billing to New Relic Cloud Cost Intelligence to monitor, analyze, and optimize cloud spending across GCP services. freshnessValidatedDate: never --- @@ -10,3 +10,32 @@ freshnessValidatedDate: never This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy).     +The Google Cloud Platform (GCP) integration for Cloud Cost Insights enables you to monitor and analyze your GCP cloud spending directly within New Relic. This integration uses a service account-based authorization method to securely access your GCP BigQuery billing and pricing data. + +When you set up this integration, New Relic creates a dedicated service account in its GCP environment on your behalf. You grant this service account read-only access to your BigQuery datasets, allowing New Relic to retrieve and analyze your cost data without requiring broader access to your GCP resources. + +## Key features + - Automated service account generation per New Relic account + - Secure, read-only access to billing data via BigQuery + - Access to both billing export and cloud pricing export tables + - Connection validation and error reporting + +## Prerequisites + + Before setting up the GCP integration, ensure you have the following: + + New Relic requirements: + - Active New Relic account with Cloud Cost Insights access + - Account ID where you want to configure the GCP integration + + Google Cloud Platform requirements: + - Active GCP account with billing enabled + - Access to Google Cloud Console + - BigQuery dataset with the following tables configured: + - Billing Export table - Contains your GCP billing data + - Cloud Pricing Export table - Contains GCP pricing information + - Fully qualified table names for both tables in the format: project_id.dataset_name.table_name + + Permissions required: + - Ability to manage BigQuery dataset permissions in your GCP account + - Permission to grant the BigQuery Data Viewer role to external service accounts \ No newline at end of file From af2dba7087ccdf946a10591a97079097f7873e96 Mon Sep 17 00:00:00 2001 From: Abhilash Dutta Date: Fri, 10 Oct 2025 19:37:35 +0530 Subject: [PATCH 13/21] updated the GCP instructions --- .../docs/cci/google-cloud-platform-cci.mdx | 64 ++++++++++++++----- 1 file changed, 49 insertions(+), 15 deletions(-) diff --git a/src/content/docs/cci/google-cloud-platform-cci.mdx b/src/content/docs/cci/google-cloud-platform-cci.mdx index c66cc5f762b..1ca0113668c 100644 --- a/src/content/docs/cci/google-cloud-platform-cci.mdx +++ b/src/content/docs/cci/google-cloud-platform-cci.mdx @@ -23,19 +23,53 @@ When you set up this integration, New Relic creates a dedicated service account ## Prerequisites Before setting up the GCP integration, ensure you have the following: + - [Connect Google Cloud Platform services to New Relic](/docs/infrastructure/google-cloud-platform-integrations/get-started/connect-google-cloud-platform-services-new-relic/) + - Enabled billing on an active GCP account + - Configured a BigQuery dataset with these tables: + - Billing Export table (contains your GCP billing data) + - Cloud Pricing Export table (contains GCP pricing information) + - Obtained fully qualified table names in this format: `project_id.dataset_name.table_name` + - Verified access to Google Cloud Console - New Relic requirements: - - Active New Relic account with Cloud Cost Insights access - - Account ID where you want to configure the GCP integration - - Google Cloud Platform requirements: - - Active GCP account with billing enabled - - Access to Google Cloud Console - - BigQuery dataset with the following tables configured: - - Billing Export table - Contains your GCP billing data - - Cloud Pricing Export table - Contains GCP pricing information - - Fully qualified table names for both tables in the format: project_id.dataset_name.table_name - - Permissions required: - - Ability to manage BigQuery dataset permissions in your GCP account - - Permission to grant the BigQuery Data Viewer role to external service accounts \ No newline at end of file +## Connect Google Cloud Platform to Cloud Cost Intelligence + + + + ### Select your account + + Start the integration by choosing your New Relic account. + + 1. Go to [**one.newrelic.com**](https://one.newrelic.com) > **All Capabilities** > **Cloud Cost Intelligence - Google Cloud Platform**. + 2. Select your account from the dropdown and click **Continue**. + + + + ### Set up the GCP connection + + 1. Follow these steps to connect your GCP billing account to New Relic: + - **Connection name** - Enter a descriptive name (for example, "GCP Production Environment") + - **Project ID** - Enter your GCP project ID + - **Dataset name** - Enter your BigQuery dataset name + - **Billing table name** - Enter the fully qualified table name in this format: `project_id.dataset_name.table_name` + - **Pricing table name** - Enter the fully qualified table name in this format: `project_id.dataset_name.table_name` + 2. Click **Continue**. + + + + ### Grant New Relic access to GCP + + New Relic provides a service account ID specific to your organization to access your Cloud Billing data in BigQuery. + + 1. Copy the service account ID displayed. + 2. Open **Google Cloud Console** and grant the service account read-only access to your BigQuery billing tables. + 3. Return to this page and click **Continue**. + + + + + ### Test and create connection + + Click **Create connection** to verify the configuration and establish the integration. + + + \ No newline at end of file From eea7b026d27a05c347cb69a0a22bd15f2b6ba9cf Mon Sep 17 00:00:00 2001 From: Abhilash Dutta Date: Wed, 15 Oct 2025 16:12:46 +0530 Subject: [PATCH 14/21] Updates --- src/content/docs/cci/cci-azure.mdx | 8 ++++---- src/content/docs/cci/overview.mdx | 6 +----- 2 files changed, 5 insertions(+), 9 deletions(-) diff --git a/src/content/docs/cci/cci-azure.mdx b/src/content/docs/cci/cci-azure.mdx index ded001259c4..fa2ee570383 100644 --- a/src/content/docs/cci/cci-azure.mdx +++ b/src/content/docs/cci/cci-azure.mdx @@ -1,5 +1,5 @@ --- -title: Azure CCI +title: Cloud Cost Intelligence - Azure metaDescription: Connect your Azure billing to New Relic Cloud Cost Intelligence to monitor, analyze, and optimize cloud spending across Azure services. freshnessValidatedDate: never redirect: @@ -12,7 +12,7 @@ redirect: This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy).     -Connect your Azure billing to Cloud Cost Intelligence for complete cost monitoring and optimization of your Azure infrastructure. Get real-time visibility into spending patterns, resource use, and cost allocation across services and resource groups. With the Azure - CCI, you can: +Connect your Azure billing to Cloud Cost Intelligence for complete cost monitoring and optimization of your Azure infrastructure. Get real-time visibility into spending patterns, resource use, and cost allocation across services and resource groups. With the Cloud Cost Intelligence - Azure, you can: - **Optimize resource usage** - Find underutilized or costly Azure services and VMs to adjust allocations across subscriptions and resource groups - **Control expenses** - See specific cost drivers in your Azure environment, including compute, storage, networking, and database services for better financial decisions @@ -37,7 +37,7 @@ Before you connect Azure to Cloud Cost Intelligence, make sure you have: Start the integration by choosing your New Relic account. - 1. Go to [**one.newrelic.com**](https://one.newrelic.com) > **All Capabilities** > **Azure - CCI**. + 1. Go to [**one.newrelic.com**](https://one.newrelic.com) > **All Capabilities** > **Cloud Cost Intelligence - Azure**. 2. Select your account from the dropdown and click **Continue**.     @@ -45,7 +45,7 @@ Before you connect Azure to Cloud Cost Intelligence, make sure you have: ### Connect your Azure billing account Enter your Azure billing information to connect Azure with Cloud Cost Intelligence: - - **Connection name** - Enter a descriptive name, such as "Azure Production Environment. + - **Connection name** - Enter a descriptive name, such as "Azure Production Environment". - **Azure Agreement Type** - Select your agreement type. You must have **[Cost and usage details (FOCUS) access](https://learn.microsoft.com/en-us/azure/cost-management-billing/dataset-schema/schema-index#latest-dataset-schema-files)**. For more information, see [Billing accounts and scopes in the Azure portal](https://learn.microsoft.com/en-us/azure/cost-management-billing/manage/view-all-accounts). To locate your agreement type, navigate to **[Microsoft Entra Admin center](https://entra.microsoft.com/#home) > Billing > Properties**. diff --git a/src/content/docs/cci/overview.mdx b/src/content/docs/cci/overview.mdx index fe0807256ef..a36e062ec96 100644 --- a/src/content/docs/cci/overview.mdx +++ b/src/content/docs/cci/overview.mdx @@ -16,10 +16,6 @@ Cloud Cost Intelligence is designed to provide visibility and management of clou For example, as your large enterprise rapidly scales its use of cloud services, tracking and managing cloud expenses can become increasingly complex. Cloud Cost Intelligence assists by providing insights into where your money is being allocated. This can help you identify areas for potential cost savings. By aligning cloud expenditures with actual usage, you can optimize your budgets while continuing to support strategic growth initiatives. This approach helps ensure that every dollar you invest is contributing to your company's overall success. - -Currently, only cloud costs from AWS are supported. - - Cloud Cost Intelligence summary page showing total costs, real-time cost estimates, average cost by day, and top 5 cost variance ## Key features @@ -42,7 +38,7 @@ Cloud Cost Intelligence is scoped to the user and collects telemetry data from a ## How Cloud Cost Intelligence retrieves cloud costs via storage solutions [#fetch-costs] -Cloud Cost Intelligence automatically accesses your AWS Cost and Usage Reports (CUR) in your designated S3 bucket once setup and integration are complete. This process begins with your authorization and the provision of access permissions. It is important to note that Cloud Cost Intelligence can only pull reports after the data is exported to your designated S3 bucket. Ensure that the S3 path prefix is set to cost-and-usage-reports as specified in the [prerequisites](/docs/cci/getting-started/prerequisites). +Cloud Cost Intelligence automatically accesses your generic Cloud Provider and Billing reports in your designated S3 bucket once setup and integration are complete. This process begins with your authorization and the provision of access permissions. It is important to note that Cloud Cost Intelligence can only pull reports after the data is exported to your designated S3 bucket. Ensure that the S3 path prefix is set to **cost-and-usage-reports** as specified in the [prerequisites](/docs/cci/getting-started/prerequisites). Typically, AWS updates the CUR three times a day, and Cloud Cost Intelligence retrieves the CUR from your S3 bucket once an hour after setup. Your latest CUR will be visible within Cloud Cost Intelligence when AWS provides their update and Cloud Cost Intelligence retrieves it shortly thereafter. From ed4ca9c28b05d7b2ba6774441987642c3e6f5853 Mon Sep 17 00:00:00 2001 From: Abhilash Dutta Date: Wed, 15 Oct 2025 16:59:32 +0530 Subject: [PATCH 15/21] Update the numbering --- src/content/docs/cci/google-cloud-platform-cci.mdx | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/src/content/docs/cci/google-cloud-platform-cci.mdx b/src/content/docs/cci/google-cloud-platform-cci.mdx index 1ca0113668c..04a952f6f3c 100644 --- a/src/content/docs/cci/google-cloud-platform-cci.mdx +++ b/src/content/docs/cci/google-cloud-platform-cci.mdx @@ -47,11 +47,11 @@ When you set up this integration, New Relic creates a dedicated service account ### Set up the GCP connection 1. Follow these steps to connect your GCP billing account to New Relic: - - **Connection name** - Enter a descriptive name (for example, "GCP Production Environment") - - **Project ID** - Enter your GCP project ID - - **Dataset name** - Enter your BigQuery dataset name - - **Billing table name** - Enter the fully qualified table name in this format: `project_id.dataset_name.table_name` - - **Pricing table name** - Enter the fully qualified table name in this format: `project_id.dataset_name.table_name` + - **Connection name** - Enter a descriptive name (for example, "GCP Production Environment") + - **Project ID** - Enter your GCP project ID + - **Dataset name** - Enter your BigQuery dataset name + - **Billing table name** - Enter the fully qualified table name in this format: `project_id.dataset_name.table_name` + - **Pricing table name** - Enter the fully qualified table name in this format: `project_id.dataset_name.table_name` 2. Click **Continue**. From 2a5894240c7a5a7c3d45cd35d0c8f39d956dfe88 Mon Sep 17 00:00:00 2001 From: Abhilash Dutta Date: Wed, 15 Oct 2025 17:54:56 +0530 Subject: [PATCH 16/21] Minor updates --- src/content/docs/cci/cci-azure.mdx | 34 ++++++++++----- .../docs/cci/google-cloud-platform-cci.mdx | 42 +++++++++++++++---- 2 files changed, 57 insertions(+), 19 deletions(-) diff --git a/src/content/docs/cci/cci-azure.mdx b/src/content/docs/cci/cci-azure.mdx index fa2ee570383..2611d101e5e 100644 --- a/src/content/docs/cci/cci-azure.mdx +++ b/src/content/docs/cci/cci-azure.mdx @@ -1,7 +1,13 @@ --- title: Cloud Cost Intelligence - Azure +tags: + - cloud cost intelligence + - azure + - azure cost management + - cloud cost optimization + - cci azure metaDescription: Connect your Azure billing to New Relic Cloud Cost Intelligence to monitor, analyze, and optimize cloud spending across Azure services. -freshnessValidatedDate: never +freshnessValidatedDate: 2025-10-15 redirect: - /docs/cci/financial-intelligence/cci-azure --- @@ -12,7 +18,7 @@ redirect: This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). -Connect your Azure billing to Cloud Cost Intelligence for complete cost monitoring and optimization of your Azure infrastructure. Get real-time visibility into spending patterns, resource use, and cost allocation across services and resource groups. With the Cloud Cost Intelligence - Azure, you can: +Connect your Azure billing to Cloud Cost Intelligence for complete cost monitoring and optimization of your Azure infrastructure. Get real-time visibility into spending patterns, resource use, and cost allocation across services and resource groups. With the Cloud Cost Intelligence for Azure, you can: - **Optimize resource usage** - Find underutilized or costly Azure services and VMs to adjust allocations across subscriptions and resource groups - **Control expenses** - See specific cost drivers in your Azure environment, including compute, storage, networking, and database services for better financial decisions @@ -24,10 +30,10 @@ Connect your Azure billing to Cloud Cost Intelligence for complete cost monitori ## Prerequisites Before you connect Azure to Cloud Cost Intelligence, make sure you have: - - **Azure subscription** with active billing account - - **Contributor or Owner role** on the subscription you want to monitor - - **Access to Azure Cost Management** features - - **Billing reader permissions** for the subscription or management group + - An **Azure subscription** with active billing account. + - **Contributor or Owner role** on the subscription you want to monitor. + - **Access to Azure Cost Management** features. + - **Billing reader permissions** for the subscription or management group. ## Connect Azure to Cloud Cost Intelligence @@ -45,11 +51,12 @@ Before you connect Azure to Cloud Cost Intelligence, make sure you have: ### Connect your Azure billing account Enter your Azure billing information to connect Azure with Cloud Cost Intelligence: - - **Connection name** - Enter a descriptive name, such as "Azure Production Environment". - - **Azure Agreement Type** - Select your agreement type. You must have **[Cost and usage details (FOCUS) access](https://learn.microsoft.com/en-us/azure/cost-management-billing/dataset-schema/schema-index#latest-dataset-schema-files)**. For more information, see [Billing accounts and scopes in the Azure portal](https://learn.microsoft.com/en-us/azure/cost-management-billing/manage/view-all-accounts). + - **Connection name** - Enter a descriptive name, for example, "Azure Production Environment". + - **Azure Agreement Type** - Select your agreement type. For more information, see [Billing accounts and scopes in the Azure portal](https://learn.microsoft.com/en-us/azure/cost-management-billing/manage/view-all-accounts). To locate your agreement type, navigate to **[Microsoft Entra Admin center](https://entra.microsoft.com/#home) > Billing > Properties**. + - **Export Type** - Select your export type. You must have **[Cost and usage details (FOCUS)](https://learn.microsoft.com/en-us/azure/cost-management-billing/dataset-schema/schema-index#latest-dataset-schema-files)** access. - **Tenant ID** - Enter the unique identifier for your organization's Microsoft Entra ID instance in Azure. To locate your **Tenant ID**, go to **[Microsoft Entra Admin center](https://entra.microsoft.com/#home)**. @@ -60,7 +67,7 @@ Before you connect Azure to Cloud Cost Intelligence, make sure you have: To locate the Storage Container Name, go to **[Microsoft Azure](https://portal.azure.com/#home) > Subscription > Storage account > Container**. It is mandatory to add authentication for our service principal in your Azure container. - - **Base drop path** - Enter the base path where billing data is stored in monthly format (for example, 20251001-20251031 for October 2025). This field is empty by default. + - **Base drop path** - Enter the base path where billing data is stored in monthly format (for example, `20251001-20251031` for October 2025). This field is empty by default. @@ -89,4 +96,11 @@ Before you connect Azure to Cloud Cost Intelligence, make sure you have: Processing your data for the first time can take up to 12 hours. - \ No newline at end of file + + +## What's next? + +After connecting Azure to Cloud Cost Intelligence: +- [View your cost data](/docs/cci/financial-intelligence/cloud-cost-insights) +- [Set up cost budgets](/docs/cci/financial-intelligence/cci-budgets) +- [Configure general settings](/docs/cci/configure-cci/general-setting) \ No newline at end of file diff --git a/src/content/docs/cci/google-cloud-platform-cci.mdx b/src/content/docs/cci/google-cloud-platform-cci.mdx index 04a952f6f3c..d6a5e40cd70 100644 --- a/src/content/docs/cci/google-cloud-platform-cci.mdx +++ b/src/content/docs/cci/google-cloud-platform-cci.mdx @@ -1,7 +1,14 @@ --- title: Cloud Cost Intelligence - Google Cloud Platform +tags: + - cloud cost intelligence + - google cloud platform + - gcp + - gcp cost management + - cloud cost optimization + - cci gcp metaDescription: Connect your Google Cloud Platform billing to New Relic Cloud Cost Intelligence to monitor, analyze, and optimize cloud spending across GCP services. -freshnessValidatedDate: never +freshnessValidatedDate: 2025-10-15 --- @@ -10,7 +17,7 @@ freshnessValidatedDate: never This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). -The Google Cloud Platform (GCP) integration for Cloud Cost Insights enables you to monitor and analyze your GCP cloud spending directly within New Relic. This integration uses a service account-based authorization method to securely access your GCP BigQuery billing and pricing data. +The Google Cloud Platform (GCP) integration for Cloud Cost Intelligence enables you to monitor and analyze your GCP cloud spending directly within New Relic. This integration uses a service account-based authorization method to securely access your GCP BigQuery billing and pricing data. When you set up this integration, New Relic creates a dedicated service account in its GCP environment on your behalf. You grant this service account read-only access to your BigQuery datasets, allowing New Relic to retrieve and analyze your cost data without requiring broader access to your GCP resources. @@ -22,14 +29,14 @@ When you set up this integration, New Relic creates a dedicated service account ## Prerequisites - Before setting up the GCP integration, ensure you have the following: - - [Connect Google Cloud Platform services to New Relic](/docs/infrastructure/google-cloud-platform-integrations/get-started/connect-google-cloud-platform-services-new-relic/) - - Enabled billing on an active GCP account + Before setting up the GCP integration, ensure you have: + - Connection to New Relic infrastructure monitoring - a GCP project already connected. See [Connect Google Cloud Platform services to New Relic](/docs/infrastructure/google-cloud-platform-integrations/get-started/connect-google-cloud-platform-services-new-relic/) + - Enabled billing on an active GCP account. - Configured a BigQuery dataset with these tables: - Billing Export table (contains your GCP billing data) - Cloud Pricing Export table (contains GCP pricing information) - - Obtained fully qualified table names in this format: `project_id.dataset_name.table_name` - - Verified access to Google Cloud Console + - Obtained fully qualified table names in this format `project_id.dataset_name.table_name`. + - Verified access to Google Cloud Console. ## Connect Google Cloud Platform to Cloud Cost Intelligence @@ -46,7 +53,7 @@ When you set up this integration, New Relic creates a dedicated service account ### Set up the GCP connection - 1. Follow these steps to connect your GCP billing account to New Relic: + 1. Connect your GCP billing account to New Relic: - **Connection name** - Enter a descriptive name (for example, "GCP Production Environment") - **Project ID** - Enter your GCP project ID - **Dataset name** - Enter your BigQuery dataset name @@ -72,4 +79,21 @@ When you set up this integration, New Relic creates a dedicated service account Click **Create connection** to verify the configuration and establish the integration. - \ No newline at end of file + + ### Verify data collection + + Go to [**Cost Overview**](/docs/cci/financial-intelligence/cloud-cost-insights) to view your GCP cost data. + + + Processing your data for the first time can take up to 12 hours. + + + + + +## What's next? + +After connecting Google Cloud Platform to Cloud Cost Intelligence: +- [View your cost data](/docs/cci/financial-intelligence/cloud-cost-insights) +- [Set up cost budgets](/docs/cci/financial-intelligence/cci-budgets) +- [Configure general settings](/docs/cci/configure-cci/general-setting) \ No newline at end of file From 0db24edba7c4d2269d5899a33e7721427bf308ae Mon Sep 17 00:00:00 2001 From: Abhilash Dutta Date: Wed, 15 Oct 2025 18:23:12 +0530 Subject: [PATCH 17/21] Final updates' --- src/content/docs/cci/google-cloud-platform-cci.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/docs/cci/google-cloud-platform-cci.mdx b/src/content/docs/cci/google-cloud-platform-cci.mdx index d6a5e40cd70..a5672c8b99a 100644 --- a/src/content/docs/cci/google-cloud-platform-cci.mdx +++ b/src/content/docs/cci/google-cloud-platform-cci.mdx @@ -30,12 +30,12 @@ When you set up this integration, New Relic creates a dedicated service account ## Prerequisites Before setting up the GCP integration, ensure you have: - - Connection to New Relic infrastructure monitoring - a GCP project already connected. See [Connect Google Cloud Platform services to New Relic](/docs/infrastructure/google-cloud-platform-integrations/get-started/connect-google-cloud-platform-services-new-relic/) + - Connection to New Relic infrastructure monitoring - A GCP project already connected. See [Connect Google Cloud Platform services to New Relic](/docs/infrastructure/google-cloud-platform-integrations/get-started/connect-google-cloud-platform-services-new-relic/) - Enabled billing on an active GCP account. - Configured a BigQuery dataset with these tables: - Billing Export table (contains your GCP billing data) - Cloud Pricing Export table (contains GCP pricing information) - - Obtained fully qualified table names in this format `project_id.dataset_name.table_name`. + - Obtained fully qualified table names in this format: `project_id.dataset_name.table_name`. - Verified access to Google Cloud Console. ## Connect Google Cloud Platform to Cloud Cost Intelligence From 2ba535681bc0ee0bcfb7028e4ec5c6ec124d3ff1 Mon Sep 17 00:00:00 2001 From: Abhilash Dutta Date: Tue, 21 Oct 2025 12:28:14 +0530 Subject: [PATCH 18/21] Updated the structure --- src/content/docs/cci/cci-azure.mdx | 334 +++++++++++++++++++++++++---- 1 file changed, 292 insertions(+), 42 deletions(-) diff --git a/src/content/docs/cci/cci-azure.mdx b/src/content/docs/cci/cci-azure.mdx index 2611d101e5e..bcc53d1b73e 100644 --- a/src/content/docs/cci/cci-azure.mdx +++ b/src/content/docs/cci/cci-azure.mdx @@ -7,9 +7,9 @@ tags: - cloud cost optimization - cci azure metaDescription: Connect your Azure billing to New Relic Cloud Cost Intelligence to monitor, analyze, and optimize cloud spending across Azure services. -freshnessValidatedDate: 2025-10-15 -redirect: +redirects: - /docs/cci/financial-intelligence/cci-azure +freshnessValidatedDate: 2025-10-15 --- @@ -30,18 +30,148 @@ Connect your Azure billing to Cloud Cost Intelligence for complete cost monitori ## Prerequisites Before you connect Azure to Cloud Cost Intelligence, make sure you have: - - An **Azure subscription** with active billing account. + - **Completed Azure billing export configuration** - This is mandatory as the export creates the storage account, container, and directory path needed in the connection process. See the collapsible section below for detailed instructions. + - An **Azure subscription** with an active billing account. - **Contributor or Owner role** on the subscription you want to monitor. - **Access to Azure Cost Management** features. - **Billing reader permissions** for the subscription or management group. + + + + Determine whether a billing export already exists that matches the parameters specified below: + - **If a matching export exists**: Proceed with your setup process using the existing export. + - **If no matching export exists**: Follow the steps below to create a new billing export. + + ### Access Azure Cost Management + + 1. Navigate to the **Azure Console > Cost Management & Billing > Billing Scope**. + 2. Expand the **Settings** section and click **Exports**. + + ### Create new export + + 1. Click **Create**. + 2. Select **Cost and Usage (FOCUS)** as the export type. + 3. Provide an export prefix for identification purposes. + + ### Configure export parameters + + Configure the export with the following parameters: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterValueDescription
    Type of DataCost and Usage details (FOCUS) - PreviewProvides detailed cost and usage information in FOCUS format
    Export NameA descriptive name of your choiceMeaningful identifier for your export
    Dataset Version1.2-preview (Latest dataset schema files)Latest schema version available
    FrequencyDaily export of month-to-date costsDaily exports capture month-to-date cost information
    Export DescriptionA meaningful description of your choiceContext about the export purpose
    + + ### Configure storage settings + + After configuring the export parameters, click **Next** to proceed to storage configuration. + + Configure the storage settings with the following specifications: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    SettingValueDescription
    Storage TypeBlob StorageAzure Blob Storage for cost data
    Destination StorageUse existing storage account or create a new oneStorage location for billing data
    Container and DirectoryUse existing container/directory or create newOrganization structure for billing exports
    Compression TypeParquetProvides optimal storage efficiency and query performance
    Data OverwriteYesAllows updates to existing data
    File PartitioningYesEnables efficient data organization and retrieval
    + + + We recommend the storage account to be based in **(US) East US**. This helps save on outbound data transfer costs. The storage type should be **Azure Blob storage**. + + + ### Finalize configuration + + 1. Review all configured settings. + 2. Click **Create** or **Save** to finalize the billing export configuration. + 3. Verify that the export appears in your Exports list. + + + - The FOCUS (FinOps Open Cost and Usage Specification) format is currently in preview + - Dataset version 1.2-preview represents the latest schema version available + - Daily exports will capture month-to-date cost information + - Parquet compression provides optimal storage efficiency and query performance + +     +     + ## Connect Azure to Cloud Cost Intelligence ### Select your account - - Start the integration by choosing your New Relic account. + + Now that you've completed the Azure billing export setup, you're ready to connect your Azure billing to New Relic. Start by choosing your New Relic account. 1. Go to [**one.newrelic.com**](https://one.newrelic.com) > **All Capabilities** > **Cloud Cost Intelligence - Azure**. 2. Select your account from the dropdown and click **Continue**. @@ -50,57 +180,177 @@ Before you connect Azure to Cloud Cost Intelligence, make sure you have: ### Connect your Azure billing account - Enter your Azure billing information to connect Azure with Cloud Cost Intelligence: - - **Connection name** - Enter a descriptive name, for example, "Azure Production Environment". - - **Azure Agreement Type** - Select your agreement type. For more information, see [Billing accounts and scopes in the Azure portal](https://learn.microsoft.com/en-us/azure/cost-management-billing/manage/view-all-accounts). - - To locate your agreement type, navigate to **[Microsoft Entra Admin center](https://entra.microsoft.com/#home) > Billing > Properties**. - - - **Export Type** - Select your export type. You must have **[Cost and usage details (FOCUS)](https://learn.microsoft.com/en-us/azure/cost-management-billing/dataset-schema/schema-index#latest-dataset-schema-files)** access. - - **Tenant ID** - Enter the unique identifier for your organization's Microsoft Entra ID instance in Azure. - - To locate your **Tenant ID**, go to **[Microsoft Entra Admin center](https://entra.microsoft.com/#home)**. - - - **Billing account ID** - Enter your Azure billing account ID. For more information, see [Billing administration](https://learn.microsoft.com/en-us/azure/cost-management-billing/manage/direct-ea-administration#to-view-enrollment-properties). - - **Azure Storage account name** - Enter the name of your storage account, which provides a unique global address for all your Azure cloud storage data. - - **Storage Container Name** - Enter the name of the container within your storage account that organizes and groups your block blobs or files. - - To locate the Storage Container Name, go to **[Microsoft Azure](https://portal.azure.com/#home) > Subscription > Storage account > Container**. It is mandatory to add authentication for our service principal in your Azure container. - - - **Base drop path** - Enter the base path where billing data is stored in monthly format (for example, `20251001-20251031` for October 2025). This field is empty by default. + Now you'll provide the connection details that link your Azure billing data to New Relic. You'll need information from both your Azure billing account and the storage location where your billing exports are saved. + + Enter the following Azure billing information: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldDescriptionLocation
    **Azure Agreement Type** + Select your agreement type from the dropdown. + + Navigate to **Azure Console > Cost Management + Billing > Settings > Properties**. For more information, see [Billing accounts and scopes in the Azure portal](https://learn.microsoft.com/en-us/azure/cost-management-billing/manage/view-all-accounts). +
    **Tenant ID** + Enter the unique identifier for your organization's Microsoft Entra ID instance. + + Go to **[Microsoft Entra Admin center](https://entra.microsoft.com/#home)** +
    **Billing account ID** + Enter your Azure billing account ID. + + Navigate to **Azure Console > Cost Management + Billing > Settings > Properties**. For more information, see [Billing administration](https://learn.microsoft.com/en-us/azure/cost-management-billing/manage/direct-ea-administration#to-view-enrollment-properties). +
    **Azure Storage account name** + Enter the name of the storage account where your billing export is saved. This is the account you created or selected during the billing export configuration. It is recommended to use a storage account in **(US) East US** to minimize outbound data transfer costs. The storage type should be **Azure Blob storage**. + +
    **Storage Container Name** + Enter the container name within your storage account that holds the billing export files. + + Go to **[Microsoft Azure](https://portal.azure.com/#home) > Subscription > Storage account > Container** + **Note**: You must grant access to the New Relic service principal in the next step for this container. +
    **Directory Path** + Enter the base path where billing data is stored within the container (for example, `20251001-20251031` for October 2025). + **Note**: If your billing export publishes directly to the root of the container, leave this field empty. + +
    + + After entering all the required information, click **Continue** to proceed to the next step.     - ### Test and create connection - - Verify the connection works and create the integration with proper permissions. - - 1. Click **Initiate Connection** to start the request (admin approval required). - - Complete these Azure admin tasks: -
      -
    • Provide access to the service principal **msazurecostdata**. See [View enterprise applications](https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/view-applications-portal) for more information.
      • -
    • Provide [Access Control (IAM)](https://learn.microsoft.com/en-us/azure/role-based-access-control/quickstart-assign-role-user-portal#grant-access) access to the service principal for the necessary Azure resources.
      • -
    -     - 2. Click **Create Connection** to create the **msazurecostdata** entry. - 3. Click **See your data**. + ### Grant New Relic access to your billing data + + Now that you've provided your Azure connection details, New Relic needs permission to read the billing data from your storage container. This step authorizes the New Relic service principal (**msazurecostdata**) to access your billing exports securely. + + + Azure administrator approval is required for this step. + + + - **Initiate the connection request** + + 1. Click the **Initiate Connection** button in the New Relic interface. + 2. You'll be redirected to the Microsoft Authentication flow. + 3. Review and accept the authentication request. + 4. A small file (0 KB) will download to your system upon acceptance. You can safely delete this file. + + - **Verify the service principal was added** + + After accepting the authentication request, confirm that the New Relic service principal was successfully added to your Azure environment: + + 1. Navigate to **Enterprise Applications** in your Microsoft Entra Account. + 2. Verify that the service principal **msazurecostdata** appears in the list. + + + For help viewing enterprise applications, see the [Microsoft Entra documentation](https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/view-applications-portal). + + + - **Assign read permissions to the service principal** + + The final step grants the service principal permission to read your billing data. You'll assign the **Storage Blob Data Reader** role, which provides read-only access to the billing exports. + + **Prerequisites for this step**: + - Access to the storage account where the billing export is published + - Permissions to modify IAM role assignments + + **Follow these steps**: + + 1. **Navigate to Access Control**: + - Open the storage account container where your billing exports are published. + - Select **Access Control (IAM)** from the left navigation menu. + + 2. **Add role assignment**: + - Navigate to the **Role Assignments** tab. + - Click **Add** or **Add role assignment**. + + 3. **Select the role**: + - Choose **Storage Blob Data Reader** from the role list. + + 4. **Assign the service principal**: + - In the **Add Members** section, search for **msazurecostdata** (the service principal you verified in the previous step). + - Select it from the search results. + + 5. **Complete the assignment**: + - Review the role assignment configuration. + - Click **Review + Assign** to finalize. + - Verify that **msazurecostdata** now appears in the role assignments list. + + - **Verify the connection** + + After completing all the steps above, confirm that: + - Service principal **msazurecostdata** is visible in Enterprise Applications + - Service principal has the **Storage Blob Data Reader** role assigned + - Role assignment is applied to the correct storage account container + - Connection test completes successfully in the New Relic interface + + + **Security note**: The service principal only has read-only access to your billing data. It cannot write, modify, or delete any data. Access is limited exclusively to the billing export container you specified. + + + With permissions configured, New Relic can now begin collecting your Azure cost data.     ### Verify data collection - Go to [**Cost Overview**](/docs/cci/financial-intelligence/cloud-cost-insights) to view your Azure cost data. + You've successfully connected your Azure billing to Cloud Cost Intelligence! Your Azure cost data will begin flowing into New Relic. + + **What happens next**: + - New Relic will start processing your Azure billing exports + - Initial data processing can take up to 12 hours + - Once processing completes, you'll see your cost data in the Cost Overview dashboard Processing your data for the first time can take up to 12 hours. + + **View your data**: + + Once processing is complete, go to [**Cost Overview**](/docs/cci/financial-intelligence/cloud-cost-insights) to view your Azure cost data and start optimizing your cloud spending.     ## What's next? -After connecting Azure to Cloud Cost Intelligence: -- [View your cost data](/docs/cci/financial-intelligence/cloud-cost-insights) -- [Set up cost budgets](/docs/cci/financial-intelligence/cci-budgets) -- [Configure general settings](/docs/cci/configure-cci/general-setting) \ No newline at end of file +Now that your Azure billing is connected, you can take full advantage of Cloud Cost Intelligence features: + +- **[View your cost data](/docs/cci/financial-intelligence/cloud-cost-insights)** - Explore detailed cost breakdowns, trends, and insights across your Azure services and resource groups. +- **[Set up cost budgets](/docs/cci/financial-intelligence/cci-budgets)** - Create budgets and alerts to proactively manage spending and prevent cost overruns. +- **[Configure general settings](/docs/cci/configure-cci/general-setting)** - Customize your Cloud Cost Intelligence experience with additional configuration options. + +Start by exploring your cost data to identify optimization opportunities and establish baseline spending patterns. \ No newline at end of file From 16b57f0344918b7935b87af4465240a4b888c1c8 Mon Sep 17 00:00:00 2001 From: Abhilash Dutta Date: Tue, 21 Oct 2025 13:42:15 +0530 Subject: [PATCH 19/21] Updated --- src/content/docs/cci/cci-azure.mdx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/content/docs/cci/cci-azure.mdx b/src/content/docs/cci/cci-azure.mdx index bcc53d1b73e..65b4f693026 100644 --- a/src/content/docs/cci/cci-azure.mdx +++ b/src/content/docs/cci/cci-azure.mdx @@ -353,4 +353,5 @@ Now that your Azure billing is connected, you can take full advantage of Cloud C - **[Set up cost budgets](/docs/cci/financial-intelligence/cci-budgets)** - Create budgets and alerts to proactively manage spending and prevent cost overruns. - **[Configure general settings](/docs/cci/configure-cci/general-setting)** - Customize your Cloud Cost Intelligence experience with additional configuration options. -Start by exploring your cost data to identify optimization opportunities and establish baseline spending patterns. \ No newline at end of file +Start by exploring your cost data to identify optimization opportunities and establish baseline spending patterns. + From 17723ea5eaa445e0c078bb3eb4eb74db5cf8f053 Mon Sep 17 00:00:00 2001 From: Abhilash Dutta Date: Tue, 21 Oct 2025 13:54:38 +0530 Subject: [PATCH 20/21] Updated the indentation --- src/content/docs/cci/cci-azure.mdx | 210 ++++++++++++++--------------- 1 file changed, 105 insertions(+), 105 deletions(-) diff --git a/src/content/docs/cci/cci-azure.mdx b/src/content/docs/cci/cci-azure.mdx index 65b4f693026..4b0b238e45b 100644 --- a/src/content/docs/cci/cci-azure.mdx +++ b/src/content/docs/cci/cci-azure.mdx @@ -39,129 +39,129 @@ Before you connect Azure to Cloud Cost Intelligence, make sure you have: - Determine whether a billing export already exists that matches the parameters specified below: - - **If a matching export exists**: Proceed with your setup process using the existing export. - - **If no matching export exists**: Follow the steps below to create a new billing export. + - **If a matching export exists**: Proceed with your setup process using the existing export. + - **If no matching export exists**: Follow the steps below to create a new billing export. ### Access Azure Cost Management - 1. Navigate to the **Azure Console > Cost Management & Billing > Billing Scope**. - 2. Expand the **Settings** section and click **Exports**. + 1. Navigate to the **Azure Console > Cost Management & Billing > Billing Scope**. + 2. Expand the **Settings** section and click **Exports**. ### Create new export - 1. Click **Create**. - 2. Select **Cost and Usage (FOCUS)** as the export type. - 3. Provide an export prefix for identification purposes. + 1. Click **Create**. + 2. Select **Cost and Usage (FOCUS)** as the export type. + 3. Provide an export prefix for identification purposes. ### Configure export parameters - Configure the export with the following parameters: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    ParameterValueDescription
    Type of DataCost and Usage details (FOCUS) - PreviewProvides detailed cost and usage information in FOCUS format
    Export NameA descriptive name of your choiceMeaningful identifier for your export
    Dataset Version1.2-preview (Latest dataset schema files)Latest schema version available
    FrequencyDaily export of month-to-date costsDaily exports capture month-to-date cost information
    Export DescriptionA meaningful description of your choiceContext about the export purpose
    + Configure the export with the following parameters: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterValueDescription
    Type of DataCost and Usage details (FOCUS) - PreviewProvides detailed cost and usage information in FOCUS format
    Export NameA descriptive name of your choiceMeaningful identifier for your export
    Dataset Version1.2-preview (Latest dataset schema files)Latest schema version available
    FrequencyDaily export of month-to-date costsDaily exports capture month-to-date cost information
    Export DescriptionA meaningful description of your choiceContext about the export purpose
    ### Configure storage settings - After configuring the export parameters, click **Next** to proceed to storage configuration. - - Configure the storage settings with the following specifications: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    SettingValueDescription
    Storage TypeBlob StorageAzure Blob Storage for cost data
    Destination StorageUse existing storage account or create a new oneStorage location for billing data
    Container and DirectoryUse existing container/directory or create newOrganization structure for billing exports
    Compression TypeParquetProvides optimal storage efficiency and query performance
    Data OverwriteYesAllows updates to existing data
    File PartitioningYesEnables efficient data organization and retrieval
    - - - We recommend the storage account to be based in **(US) East US**. This helps save on outbound data transfer costs. The storage type should be **Azure Blob storage**. - + After configuring the export parameters, click **Next** to proceed to storage configuration. + + Configure the storage settings with the following specifications: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    SettingValueDescription
    Storage TypeBlob StorageAzure Blob Storage for cost data
    Destination StorageUse existing storage account or create a new oneStorage location for billing data
    Container and DirectoryUse existing container/directory or create newOrganization structure for billing exports
    Compression TypeParquetProvides optimal storage efficiency and query performance
    Data OverwriteYesAllows updates to existing data
    File PartitioningYesEnables efficient data organization and retrieval
    + + + We recommend the storage account to be based in **(US) East US**. This helps save on outbound data transfer costs. The storage type should be **Azure Blob storage**. + ### Finalize configuration - 1. Review all configured settings. - 2. Click **Create** or **Save** to finalize the billing export configuration. - 3. Verify that the export appears in your Exports list. + 1. Review all configured settings. + 2. Click **Create** to finalize the billing export configuration. + 3. Verify that the export appears in your **Exports** list. + + + - The FOCUS (FinOps Open Cost and Usage Specification) format is currently in preview + - Dataset version 1.2-preview represents the latest schema version available + - Daily exports are capturing month-to-date cost information + - Parquet compression provides optimal storage efficiency and query performance + - - - The FOCUS (FinOps Open Cost and Usage Specification) format is currently in preview - - Dataset version 1.2-preview represents the latest schema version available - - Daily exports will capture month-to-date cost information - - Parquet compression provides optimal storage efficiency and query performance -     From 29da2da7ba3e7d8791a2cd7b54b71e68a0c52f48 Mon Sep 17 00:00:00 2001 From: akashreddy Date: Tue, 21 Oct 2025 18:20:24 +0530 Subject: [PATCH 21/21] fix: build errors --- package.json | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/package.json b/package.json index 0d8903f9367..a29e1410d75 100644 --- a/package.json +++ b/package.json @@ -239,6 +239,5 @@ }, "bugs": { "url": "https://github.com/newrelic/docs-website/issues" - }, - "packageManager": "yarn@1.22.22+sha512.a6b2f7906b721bba3d67d4aff083df04dad64c399707841b7acf00f6b133b7ac24255f2652fa22ae3534329dc6180534e98d17432037ff6fd140556e2bb3137e" + } }