diff --git a/src/content/docs/accounts/accounts-billing/account-structure/new-relic-account-structure.mdx b/src/content/docs/accounts/accounts-billing/account-structure/new-relic-account-structure.mdx index a7cfb253896..240190747eb 100644 --- a/src/content/docs/accounts/accounts-billing/account-structure/new-relic-account-structure.mdx +++ b/src/content/docs/accounts/accounts-billing/account-structure/new-relic-account-structure.mdx @@ -20,6 +20,8 @@ When you sign up for New Relic, this creates an organization containing a single An account can have many sources of data reporting to it. For example, a single account could have data reporting from our infrastructure agent, an agent, and other integrations. All data reported to New Relic requires an [account ID](/docs/accounts/accounts-billing/account-structure/account-id), which tells New Relic which account that data belongs in. That ID is also used for some account-specific tasks, like making API calls. +You may notice a special account in your list of accounts under the Organization header. This account stores data for organization-scoped features, and you will use this account for any queries using data from organization-scoped features. You cannot cancel or ingest data into this account. This will also be in your list of accounts when querying NerdGraph. It will be returned as ` Storage Account`. + When you [set up user access](#account-access), you grant users access to specific accounts. ## Cross-account access [#cross-account-access] diff --git a/src/content/docs/accounts/accounts-billing/new-relic-one-pricing-billing/add-on-billing.mdx b/src/content/docs/accounts/accounts-billing/new-relic-one-pricing-billing/add-on-billing.mdx index 52405f6f578..119c71309d1 100644 --- a/src/content/docs/accounts/accounts-billing/new-relic-one-pricing-billing/add-on-billing.mdx +++ b/src/content/docs/accounts/accounts-billing/new-relic-one-pricing-billing/add-on-billing.mdx @@ -15,7 +15,7 @@ In addition to the primary billing factors of GB Ingested and billable users, yo Your use of CodeStream under Advanced Compute will incur CCU charges, regardless of user type. This means that free basic users can access Advanced Compute features and incur charges for Advanced CCUs. - + * **EU Data Center for Original Data or Data Plus**: This add-on applies to your data option (original Data or Data Plus) when you select the European Union as your data region, as available. * **Extended Retention for Original Data or Data Plus**: This add-on applies if you exceed the default length of time your data is retained. This applies to all your data—not just logs—and is a good option if you need to make a lot of small queries or make queries on large volumes of data. * **Live Archives**: Extend your log storage duration up to seven years. Live Archives also requires Advanced Compute. diff --git a/src/content/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts.mdx b/src/content/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts.mdx index c2eee377851..4f703f84048 100644 --- a/src/content/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts.mdx +++ b/src/content/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts.mdx @@ -217,7 +217,7 @@ To learn how to add users, assign them to groups, and create custom groups and r ## Use the API [#api] -For how to manage your users and groups via API, see [our NerdGraph docs](/docs/apis/nerdgraph/examples/nerdgraph-manage-users). +For how to manage your users, groups, and roles via API, see [our NerdGraph docs](/docs/apis/nerdgraph/examples/nerdgraph-manage-users). ## User management terms and definitions [#definitions] diff --git a/src/content/docs/apis/nerdgraph/examples/nerdgraph-manage-groups.mdx b/src/content/docs/apis/nerdgraph/examples/nerdgraph-manage-groups.mdx index 9f5f637f67f..a47716c1fe7 100644 --- a/src/content/docs/apis/nerdgraph/examples/nerdgraph-manage-groups.mdx +++ b/src/content/docs/apis/nerdgraph/examples/nerdgraph-manage-groups.mdx @@ -274,6 +274,129 @@ Here's an example response: }, ``` +## Create a role [#create-role] + +Here's an example of creating a [role](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts/#roles): + +```graphql +mutation { + customRoleCreate( + container: { + id: "$YOUR_ORGANIZATION_ID" + type: "ORGANIZATION" + } + name: "MY CUSTOM ROLE" + permissionIds: [1,2,3] + scope: "ACCOUNT" + ) { + id + } +} +``` +### Parameters +- `container`: + - `id`: (String) The unique identifier of your organization. Replace $YOUR_ORGANIZATION_ID with your actual organization ID. + - `type`: (String) The type of container. Currently, the only supported type is "ORGANIZATION". + - `name`: (String) The name assigned to the custom role. Example: "MY CUSTOM ROLE". +- `permissionIds`: (Array) A list of permission IDs representing the capabilities assigned to the custom role. Ensure these IDs correspond to valid permissions in your system. +- `scope`: (String) The level at which the role's permissions apply. In this instance, the scope is "ACCOUNT". + +### Response +- `id`: Returns the unique ID of the newly created custom role. + + + - Replace `$YOUR_ORGANIZATION_ID` with your specific organization ID before executing the mutation. + - Ensure that the `permissionIds` provided are valid and align with the permissions you want to grant. + + +Before you create a custom role, you have to identify the permissions you want to assign to it. + +Use the following query to retrieve the list of permissions: + +```graphql +mutation { + customerAdministration { + permissions { + items { + category + feature + id + product + subsetIds + } + nextCursor + } + } +} +``` +This returns account-scoped permissions. For permissions scoped to an org, run the following query instead: + +```graphql +{ + customerAdministration { + permissions(filter: {scope: {eq: "organization"}}) { + items { + category + feature + id + product + subsetIds + } + nextCursor + } + } +} +``` + +Note the following fields: +- `items`: An array of permission objects, each containing the following attributes: + - `category`: (String) The category or grouping the permission belongs to. + - `feature`: (String) The specific feature the permission is associated with. + - `id`: (String) A unique identifier for each permission. + - `product`: (String) The product that the permission applies to. + - `subsetIds`: (Array) A list of IDs representing subsets or related permissions. + +After you have the unique identifier for each permission you want to assign to the new role, create that role. + +## Update role [#update-role] + +Here's an example of updating a [role](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts/#roles). + +```graphql +mutation { + customRoleUpdate( + id: $ROLE_ID + name: "MY NEW CUSTOM ROLE NAME" + permissionIds: [4,5,6] + ) { + id + } +} +``` + +### Parameters +- `id`: The unique identifier of the custom role you wish to modify. Replace `$ROLE_ID` with the actual ID of the role. +- `name`: The new name you want to assign to the custom role. In this example, it's `MY NEW CUSTOM ROLE NAME`. +- `permissionIds`: An array of permission IDs you want to assign to this role. Ensure these IDs are valid and correspond to the permissions you intend to implement. + +## Delete a role [#delete-role] +Here's an example of deleting a [role](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts/#roles): + +```graphql +mutation { + customRoleDelete( + id: $ROLE_ID + ) { + id + } +} +``` + +### Parameters +- `id`: The unique identifier of the role you wish to delete. Replace `$ROLE_ID` with the actual ID of the role you want to remove. +### Response +- `id`: Returns the ID of the role that has been deleted, confirming the successful execution of the mutation. + ## Create a group [#create-group] Here's an example of creating a [group](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts/#groups): diff --git a/src/content/docs/apis/nerdgraph/examples/use-nerdgraph-manage-license-keys-user-keys.mdx b/src/content/docs/apis/nerdgraph/examples/use-nerdgraph-manage-license-keys-user-keys.mdx index 2c7fb7bc799..93005d33afb 100644 --- a/src/content/docs/apis/nerdgraph/examples/use-nerdgraph-manage-license-keys-user-keys.mdx +++ b/src/content/docs/apis/nerdgraph/examples/use-nerdgraph-manage-license-keys-user-keys.mdx @@ -30,26 +30,25 @@ Notes about this functionality: * All mutations can accept multiple keys as arguments, and will return details about successful changes and errors. See examples below for details. * All mutations (create, update and delete) will result in an `NrAuditEvent` that can be queried for auditing purposes. For details, see [Audit events](/docs/insights/use-insights-ui/manage-account-data/query-account-audit-logs-nrauditevent). -* Regarding license keys: - * License keys are categorized by NerdGraph as **ingest keys**. This is because their main use is to allow data ingest. - * You can create up to 1,000 keys of each license key type, which allows for key rotation. - * You can't manage or delete original license keys; you can only create additional license keys and manage keys you've created. +* Regarding ingest keys: + * License and Browser keys are categorized by NerdGraph as **ingest keys**. This is because their main use is to allow data ingest. + * You can create up to 1,000 keys of each ingest key type, which allows for key rotation. + * You can't manage or delete original account ingest keys but you can contact New Relic support to rotate these; you can only create additional ingest or user keys and manage keys you've created. ## Before using examples [#before-examples] Things to note before using these example queries: -* The examples below use license keys (aka ingest keys), but you can query [user keys](/docs/apis/get-started/intro-apis/types-new-relic-api-keys#user-api-key) in similar ways, replacing the ingest-key-specific fields with user-key-specific fields. * To understand the data structure, we recommend experimenting with queries using the [GraphiQL explorer](https://api.newrelic.com/graphiql). * You can also [create, view, and delete user keys using the UI.](/docs/apis/get-started/intro-apis/types-new-relic-api-keys#personal-api-key) ## Create keys - You can find and generate user keys using the [NerdGraph GraphiQL explorer](/docs/apis/nerdgraph/get-started/introduction-new-relic-nerdgraph/#explorer), at the top of that interface. + You can find and generate user keys using the [NerdGraph GraphQL explorer](/docs/apis/nerdgraph/get-started/introduction-new-relic-nerdgraph/#explorer), at the top of that interface. -To create multiple keys (user key or license key) in a single mutation, for multiple accounts and key types. Note that the mutation can return successfully created keys as well as any errors encountered trying to create keys. +To create multiple keys (user key or ingest key) in a single mutation, for multiple accounts and key types. Note that the mutation can return successfully created keys as well as any errors encountered trying to create keys. Example of creating a key: diff --git a/src/content/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx b/src/content/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx index 84445942ecc..b6208121b3d 100644 --- a/src/content/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx +++ b/src/content/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx @@ -616,6 +616,32 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co + + + System.Data.ODBC + + + + + + + + Use [System.Data.Odbc](https://www.nuget.org/packages/System.Data.Odbc/). + * Minimum supported version: 8.0.0 + * Latest verified compatible version: 9.0.1 + * Minimum agent version required: 10.35.0 + + + The following features supported for ODBC datastore calls in .NET Framework (using the built-in System.Data namespace) are not supported for .NET 8+: + * Connection `Open/OpenAsync` calls + * SqlDataReader `Read/NextResult` calls + * Slow SQL traces + + + @@ -1388,6 +1414,23 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co + + + System.Data.ODBC + + + + + + Use the built-in `System.Data.ODBC` namespace from the .NET Framework. + * Available in all currently supported .NET Framework agent versions. + * All versions of the .NET Framework currently supported by Microsoft are verified to be compatible. + + + MongoDB (legacy driver) diff --git a/src/content/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx b/src/content/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx index bb8c5757d95..59b61456e90 100644 --- a/src/content/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx +++ b/src/content/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx @@ -276,19 +276,19 @@ version. | --- | --- | --- | --- | | `@apollo/gateway` | 2.3.0 | 2.9.3 | `@newrelic/apollo-server-plugin@1.0.0` | | `@apollo/server` | 4.0.0 | 4.11.3 | `@newrelic/apollo-server-plugin@2.1.0` | -| `@aws-sdk/client-bedrock-runtime` | 3.474.0 | 3.741.0 | 11.13.0 | -| `@aws-sdk/client-dynamodb` | 3.0.0 | 3.741.0 | 8.7.1 | -| `@aws-sdk/client-sns` | 3.0.0 | 3.741.0 | 8.7.1 | -| `@aws-sdk/client-sqs` | 3.0.0 | 3.741.0 | 8.7.1 | -| `@aws-sdk/lib-dynamodb` | 3.377.0 | 3.741.0 | 8.7.1 | +| `@aws-sdk/client-bedrock-runtime` | 3.474.0 | 3.744.0 | 11.13.0 | +| `@aws-sdk/client-dynamodb` | 3.0.0 | 3.744.0 | 8.7.1 | +| `@aws-sdk/client-sns` | 3.0.0 | 3.744.0 | 8.7.1 | +| `@aws-sdk/client-sqs` | 3.0.0 | 3.744.0 | 8.7.1 | +| `@aws-sdk/lib-dynamodb` | 3.377.0 | 3.744.0 | 8.7.1 | | `@aws-sdk/smithy-client` | 3.47.0 | 3.374.0 | 8.7.1 | | `@elastic/elasticsearch` | 7.16.0 | 8.17.0 | 11.9.0 | | `@grpc/grpc-js` | 1.4.0 | 1.12.6 | 8.17.0 | | `@hapi/hapi` | 20.1.2 | 21.3.12 | 9.0.0 | | `@koa/router` | 11.0.2 | 13.1.0 | 3.2.0 | -| `@langchain/core` | 0.1.17 | 0.3.37 | 11.13.0 | +| `@langchain/core` | 0.1.17 | 0.3.40 | 11.13.0 | | `@nestjs/cli` | 9.0.0 | 11.0.2 | 10.1.0 | -| `@opensearch-project/opensearch` | 2.1.0 | 3.2.0 | 12.10.0 | +| `@opensearch-project/opensearch` | 2.1.0 | 3.3.0 | 12.10.0 | | `@prisma/client` | 5.0.0 | 6.3.1 | 11.0.0 | | `@smithy/smithy-client` | 2.0.0 | 4.1.3 | 11.0.0 | | `amqplib` | 0.5.0 | 0.10.5 | 2.0.0 | @@ -302,19 +302,19 @@ version. | `express` | 4.6.0 | 4.21.2 | 2.6.0 | | `fastify` | 2.0.0 | 5.2.1 | 8.5.0 | | `generic-pool` | 3.0.0 | 3.9.0 | 0.9.0 | -| `ioredis` | 4.0.0 | 5.4.2 | 1.26.2 | +| `ioredis` | 4.0.0 | 5.5.0 | 1.26.2 | | `kafkajs` | 2.0.0 | 2.2.4 | 11.19.0 | -| `koa` | 2.0.0 | 2.15.3 | 3.2.0 | +| `koa` | 2.0.0 | 2.15.4 | 3.2.0 | | `koa-route` | 3.0.0 | 4.0.1 | 3.2.0 | | `koa-router` | 11.0.2 | 13.0.1 | 3.2.0 | | `memcached` | 2.2.0 | 2.2.2 | 1.26.2 | | `mongodb` | 4.1.4 | 6.13.0 | 1.32.0 | | `mysql` | 2.2.0 | 2.18.1 | 1.32.0 | | `mysql2` | 2.0.0 | 3.12.0 | 1.32.0 | -| `next` | 13.4.19 | 15.1.6 | 12.0.0 | -| `openai` | 4.0.0 | 4.82.0 | 11.13.0 | -| `pg` | 8.2.0 | 8.13.1 | 9.0.0 | -| `pg-native` | 3.0.0 | 3.2.0 | 9.0.0 | +| `next` | 13.4.19 | 15.1.7 | 12.0.0 | +| `openai` | 4.0.0 | 4.84.0 | 11.13.0 | +| `pg` | 8.2.0 | 8.13.2 | 9.0.0 | +| `pg-native` | 3.0.0 | 3.2.1 | 9.0.0 | | `pino` | 7.0.0 | 9.6.0 | 8.11.0 | | `q` | 1.3.0 | 1.5.1 | 1.26.2 | | `redis` | 3.1.0 | 4.7.0 | 1.31.0 | diff --git a/src/content/docs/browser/browser-monitoring/browser-pro-features/auto-logging.mdx b/src/content/docs/browser/browser-monitoring/browser-pro-features/auto-logging.mdx deleted file mode 100644 index 3d872b4531f..00000000000 --- a/src/content/docs/browser/browser-monitoring/browser-pro-features/auto-logging.mdx +++ /dev/null @@ -1,144 +0,0 @@ ---- -title: "Automatically detect browser logs" -metaDescription: "Get a more complete picture of your front-end application" -freshnessValidatedDate: 2024-11-18 ---- - -Auto logging collects log messages issued from the browser `console` to help you maximize observability of your front-end applications. - -Browser logs are tracked by default at the `WARN` level for Pro and Pro+SPA agents, but unavailable for the Lite browser agent. We recommend that you first confirm you're using the Pro or Pro+SPA agent. See [Getting Started](#get-started). - -## How browser auto-logging works [#how-it-works] - -Based on logging levels and sampling rates set in the configuration, auto-instrumentation of browser logs will attempt to collect messages from the following methods: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Method - - Level -
- `console.log` - - `'INFO'` -
- `console.error` - - `'ERROR'` -
- `console.warn` - - `'WARN'` -
- `console.info` - - `'INFO'` -
- `console.debug` - - `'DEBUG'` -
- `console.trace` - - `'TRACE'` -
- - -Data passed through the console methods may go through serialization and [obfuscation](/docs/browser/new-relic-browser/configuration/obfuscate-browser-agent-data/). Depending on the size and frequency, this may negatively impact application performance as well as data costs. In general, it is NOT recommended to pass in large objects or large amounts of data into console methods. - - -By default, logging data is stored for 30 days, but actual data retention depends on your account. - -## Get started [#get-started] - - - - ### Enable automatic log collection [#enable-configure-settings] - - 1. Go to **[one.newrelic.com](https://one.newrelic.com/all-capabilities) > All Capabilities > Browser**. - 2. Select your browser app. - 3. In the left-hand menu, click **Application settings**. - 4. On the Application settings page, make sure **Pro** or **Pro + SPA** browser agent is selected. Automatic log detection is not available for the Lite browser agent. - 5. Toggle ON **Browser logs** setting. - - - - ### Configure sampling rates [#configure-sampling-rates] - - Set a sampling rate (0%-100%) for the following samples: - - * **User sessions** records a random sample of all user sessions. - - For example, if you set the session sampling rate to 50%, it means that: - - * Half of all user sessions will automatically collect log events. - - - - ### View log events [#view-events] - - You can find logging data in two places: - - * On the **Logs** page: - - 1. Go to: **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Logs**. For details on what you can do in the UI, see [Logs UI](/docs/logs/ui-data/use-logs-ui). - - You can also query the `Log` data type. Here's a simple example NRQL query: - - ```sql - SELECT * FROM Log - ``` - - You can also use NerdGraph, our GraphQL-format API to [query data](/docs/apis/nerdgraph/examples/nerdgraph-nrql-tutorial), or to [configure log management](/docs/apis/nerdgraph/examples/nerdgraph-log-parsing-rules-tutorial). - - * On the **Errors inbox** page: - - 1. In the left-hand browser menu, click **Errors**. - 2. Click on the **Triage** and **Group errors** pages to see logs attached to errors. - - - -## Data consumption [#data-consumption] - -Logs follow the same consumption pricing as your other browser bytes. The amount of bytes produced depends on the count and length of messages. - -The auto logging feature eliminates the need to call the `newrelic.log` or `newrelic.wrapLogger` browser APIs, except when adding custom attributes to logging events. diff --git a/src/content/docs/browser/browser-monitoring/browser-pro-features/session-replay.mdx b/src/content/docs/browser/browser-monitoring/browser-pro-features/session-replay.mdx index 3bf841c654c..d92a6ee802f 100644 --- a/src/content/docs/browser/browser-monitoring/browser-pro-features/session-replay.mdx +++ b/src/content/docs/browser/browser-monitoring/browser-pro-features/session-replay.mdx @@ -43,7 +43,7 @@ For more details on session replay, see the following sections: 2. Select your browser app. 3. In the left-hand menu, click **Application settings**. 4. On the Application settings page, make sure **Pro** or **Pro + SPA** browser agent is selected. Session replay is not available for the Lite browser agent. - 5. Toggle ON **Session traces** and **Session replay** settings. + 5. Toggle ON **Session tracking** and **Session replay** settings. diff --git a/src/content/docs/browser/new-relic-browser/browser-apis/recordReplay.mdx b/src/content/docs/browser/new-relic-browser/browser-apis/recordReplay.mdx index 1c5dab2f3d6..5322bd9e04a 100644 --- a/src/content/docs/browser/new-relic-browser/browser-apis/recordReplay.mdx +++ b/src/content/docs/browser/new-relic-browser/browser-apis/recordReplay.mdx @@ -28,6 +28,7 @@ Browser API used to force a replay to start recording. `newrelic.recordReplay()` can be called to manually force a replay to begin recording. You must meet the following requirements: * Account is entitled to record replays +* Session Tracking is Enabled * Session Trace is Enabled * Browser mutation observer global is present in the current version of the browser being used * The Session Replay feature is either normally imported, or set to `autoStart: false` and has already been "started" diff --git a/src/content/docs/infrastructure/other-infrastructure-integrations/confluent-cloud-integration.mdx b/src/content/docs/infrastructure/other-infrastructure-integrations/confluent-cloud-integration.mdx new file mode 100644 index 00000000000..c287cd9b694 --- /dev/null +++ b/src/content/docs/infrastructure/other-infrastructure-integrations/confluent-cloud-integration.mdx @@ -0,0 +1,299 @@ +--- +title: Confluent cloud integration +tags: + - Integrations + - Confluent cloud integrations + - Apache Kafka + +metaDescription: " New Relic's Confluent cloud integration for Kafka: what data it reports, and how to enable it." +freshnessValidatedDate: never +--- + +New Relic offers an integration for collecting your [Confluent Cloud managed streaming for Apache Kafka](https://www.confluent.io/confluent-cloud/) data. This document explains how to activate this integration and describes the data that can be reported. + +## Prerequisites + +* A New Relic account +* An active Confluent Cloud account +* A Confluent Cloud API key and secret +* `MetricsViewer` access on the Confluent Cloud account + +## Activate integration [#activate] + +To enable this integration, go to **Integrations & Agents**, select **Confluent Cloud -> API Polling** and follow the instructions. + + +If you have IP Filtering set up, add the following IP addresses to your filter. +* `162.247.240.0/22` +* `152.38.128.0/19` + +For more information about New Relic IP ranges for cloud integration, refer [this document](/docs/new-relic-solutions/get-started/networks/#webhooks). +For instructions to perform this task, refer [this document](https://docs.confluent.io/cloud/current/security/access-control/ip-filtering/manage-ip-filters.html). + + + + +## Configuration and polling [#polling] + + +Default polling information for the Confluent Cloud Kafka integration: + +* New Relic polling interval: 5 minutes +* Confluent Cloud data interval: 1 minute + +You can change the polling frequency only during the initial configuration. + +## View and use data [#find-data] + +To view your integration data, go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Infrastructure > AWS** and select an integration. + +You can [query and explore your data](/docs/using-new-relic/data/understand-data/query-new-relic-data) using the following [event type](/docs/data-apis/understand-data/new-relic-data-types/#metrics-in-service-levels): + + + + + + + + + + + + + + + + + + + + + +
+ Entity + + Data type + + Provider +
+ Cluster + + `Metric` + + `Confluent` +
+ +For more on how to use your data, see [Understand and use integration data](/docs/infrastructure/integrations/find-use-infrastructure-integration-data). + +## Metric data [#metrics] + +This integration records Amazon Managed Kafka data for cluster, partition, and topic entities. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Metric + + Unit + + Description +
+ `cluster_load_percent` + + Percent + + A measure of the utilization of the cluster. The value is between 0.0 and 1.0. + Only dedicated tier clusters has this metric data. + +
+ `hot_partition_ingress` + + Percent + + An indicator of the presence of a hot partition caused by ingress throughput. The value is 1.0 when a hot partition is detected, and empty when there is no hot partition detected. +
+ `hot_partition_egress` + + Percent + + An indicator of the presence of a hot partition caused by egress throughput. The value is 1.0 when a hot partition is detected, and empty when there is no hot partition detected. +
+ `request_bytes` + + Bytes + + The delta count of total request bytes from the specified request types sent over the network. Each sample is the number of bytes sent since the previous data point. The count is sampled every 60 seconds. +
+ `response_bytes` + + Bytes + + The delta count of total response bytes from the specified response types sent over the network. Each sample is the number of bytes sent since the previous data point. The count is sampled every 60 seconds. +
+ `received_bytes` + + Bytes + + The delta count of bytes of the customer's data received from the network. Each sample is the number of bytes received since the previous data sample. The count is sampled every 60 seconds. +
+ `sent_bytes` + + Bytes + + The delta count of bytes of the customer's data sent over the network. Each sample is the number of bytes sent since the previous data point. The count is sampled every 60 seconds. +
+ `received_records` + + Count + + The delta count of records received. Each sample is the number of records received since the previous data sample. The count is sampled every 60 seconds. +
+ `sent_records` + + Count + + The delta count of records sent. Each sample is the number of records sent since the previous data point. The count is sampled every 60 seconds. +
+ `partition_count` + + Count + + The number of partitions. +
+ `consumer_lag_offsets` + + Milliseconds + + The lag between a group member's committed offset and the partition's high watermark. +
+ `successful_authentication_count` + + Count + + The delta count of successful authentications. Each sample is the number of successful authentications since the previous data point. The count sampled every 60 seconds. +
+ `active_connection_count` + + Count + + The count of active authenticated connections. +
+ diff --git a/src/content/docs/infrastructure/prometheus-integrations/install-configure/prometheus-high-availability-ha.mdx b/src/content/docs/infrastructure/prometheus-integrations/install-configure/prometheus-high-availability-ha.mdx index f8d5d888395..2b99861c837 100644 --- a/src/content/docs/infrastructure/prometheus-integrations/install-configure/prometheus-high-availability-ha.mdx +++ b/src/content/docs/infrastructure/prometheus-integrations/install-configure/prometheus-high-availability-ha.mdx @@ -68,7 +68,9 @@ New Relic requires two external labels to deduplicate data from replicas in a hi -The remaining sections explain how labels work with Prometheus Operator and standalone Prometheus. + + An account can have up to 1,500 unique Prometheus HA clusters. If this limit is exceeded, data from additional HA clusters will be dropped. In such cases, New Relic generates `PrometheusHAClusterLimit` [`NrIntegrationError`](https://docs.newrelic.com/docs/data-apis/ingest-apis/metric-api/troubleshoot-nrintegrationerror-events/) events. + ## Prometheus Operator [#kubernetes-operator] diff --git a/src/content/docs/mobile-crash-rest-api-v1.mdx b/src/content/docs/mobile-crash-rest-api-v1.mdx index 0d070fed24b..ca9d328e98e 100644 --- a/src/content/docs/mobile-crash-rest-api-v1.mdx +++ b/src/content/docs/mobile-crash-rest-api-v1.mdx @@ -19,7 +19,7 @@ You can use the API to: To use the Crash API in these examples, you need: -* Your New Relic Crash API Key. Pass this key as the value of the X-API-KEY header. +* Your New Relic Crash API Key. Pass this key as the value of the `X-API-KEY` header. * Your New Relic [account ID](/docs/accounts-partnerships/accounts/account-setup/account-id) * Your mobile monitoring [application ID](/docs/apis/rest-api-v2/requirements/finding-product-id#mobile) @@ -30,7 +30,7 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} ``` - **Note**: X-API-KEYs are rate limited to 600 requests per minute. + **Note**: `X-API-KEY`s are rate limited to 600 requests per minute. ## GET mobile-crashes/ @@ -98,15 +98,15 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} `sort` - Optional: The order of the results sorted on a particular property: recent, occurrence-count, users-affected. + Optional: The order of the results sorted on a particular property: `recent`, `occurrence-count`, `users-affected`. - recent + `recent` - occurrence-count + `occurrence-count` @@ -149,7 +149,7 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} id="get-crashes-response" title="Response" > - ``` + ```json { data: [ { @@ -185,11 +185,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - crashFingerprint + `crashFingerprint` - string + _string_ @@ -199,11 +199,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - crashLocation + `crashLocation` - string + _string_ @@ -213,11 +213,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - firstSeen + `firstSeen` - long + _long_ @@ -227,11 +227,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - lastSeen + `lastSeen` - long + _long_ @@ -241,11 +241,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - usersAffected + `usersAffected` - long + _long_ @@ -255,11 +255,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - occurrenceCount + `occurrenceCount` - long + _long_ @@ -269,11 +269,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - crashLocationFile + `crashLocationFile` - string + _string_ @@ -287,11 +287,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - crashLocationLineNumber + `crashLocationLineNumber` - long + _long_ @@ -305,11 +305,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - crashLocationMethod + `crashLocationMethod` - string + _string_ @@ -323,11 +323,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - crashLocationClass + `crashLocationClass` - string + _string_ @@ -359,11 +359,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - count + `count` - long + _long_ @@ -373,11 +373,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - startTime + `startTime` - long + _long_ @@ -387,11 +387,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - endTime + `endTime` - long + _long_ @@ -401,11 +401,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - maxSize + `maxSize` - long + _long_ @@ -415,11 +415,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - sort + `sort` - string + _string_ @@ -532,11 +532,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - 20 + `20` - 100 + `100` @@ -548,11 +548,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - recent + `recent` - recent + `recent` @@ -564,11 +564,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - false + `false` - true + `true` @@ -579,7 +579,7 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} id="get-fingerprints-response" title="Response" > - ``` + ```json { data: [ :occurrence, @@ -613,11 +613,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - id + `id` - string + _string_ @@ -627,11 +627,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - timestamp + `timestamp` - long + _long_ @@ -663,11 +663,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - count + `count` - long + _long_ @@ -677,11 +677,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - startTime + `startTime` - long + _long_ @@ -691,11 +691,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - endTime + `endTime` - long + _long_ @@ -705,11 +705,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - maxSize + `maxSize` - long + _long_ @@ -719,11 +719,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - sort + `sort` - string + _string_ @@ -839,7 +839,7 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} id="get-details-response" title="Response" > - ``` + ```json { data: [ threads: [ @@ -885,11 +885,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - threadNumber + `threadNumber` - long + _long_ @@ -899,11 +899,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - threadName + `threadName` - string + _string_ @@ -913,11 +913,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - crashed + `crashed` - bool + _bool_ @@ -927,11 +927,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - registers + `registers` - Dictionary + _Dictionary_ @@ -941,11 +941,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - frames + `frames` - Array<Frame> + _Array<Frame>_ @@ -977,11 +977,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - library + `library` - string + _string_ @@ -991,11 +991,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - libraryAddress + `libraryAddress` - hex + _hex_ @@ -1005,11 +1005,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - file + `file` - string + _string_ @@ -1019,11 +1019,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - class + `class` - string + _string_ @@ -1033,11 +1033,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - method + `method` - string + _string_ @@ -1047,11 +1047,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - line + `line` - long + _long_ @@ -1061,11 +1061,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - instructionAddress + `instructionAddress` - hex + _hex_ @@ -1075,11 +1075,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - symbolAddress + `symbolAddress` - hex + _hex_ @@ -1089,11 +1089,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - symbolName + `symbolName` - string + _string_ @@ -1173,7 +1173,7 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} id="get-thread-data-response" title="Response" > - ``` + ```json { data: [ threads: [ @@ -1216,11 +1216,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - threadNumber + `threadNumber` - long + _long_ @@ -1230,11 +1230,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - threadName + `threadName` - string + _string_ @@ -1244,11 +1244,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - crashed + `crashed` - bool + _bool_ @@ -1258,11 +1258,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - registers + `registers` - Dictionary + _Dictionary_ @@ -1272,11 +1272,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - frames + `frames` - Array<Frame> + _Array<Frame>_ @@ -1308,11 +1308,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - library + `library` - string + _string_ @@ -1322,11 +1322,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - libraryAddress + `libraryAddress` - hex + _hex_ @@ -1336,11 +1336,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - file + `file` - string + _string_ @@ -1350,11 +1350,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - class + `class` - string + _string_ @@ -1364,11 +1364,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - method + `method` - string + _string_ @@ -1378,11 +1378,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - line + `line` - long + _long_ @@ -1392,11 +1392,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - instructionAddress + `instructionAddress` - hex + _hex_ @@ -1406,11 +1406,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - symbolAddress + `symbolAddress` - hex + _hex_ @@ -1420,11 +1420,11 @@ https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID} - symbolName + `symbolName` - string + _string_ diff --git a/src/content/docs/mobile-monitoring/new-relic-mobile-maui-dotnet/monitor-your-net-maui-application.mdx b/src/content/docs/mobile-monitoring/new-relic-mobile-maui-dotnet/monitor-your-net-maui-application.mdx index 3b461807243..dc8a0c8e009 100644 --- a/src/content/docs/mobile-monitoring/new-relic-mobile-maui-dotnet/monitor-your-net-maui-application.mdx +++ b/src/content/docs/mobile-monitoring/new-relic-mobile-maui-dotnet/monitor-your-net-maui-application.mdx @@ -308,3 +308,21 @@ The following customizations are available for the .NET MAUI agent. Missing HTTP data in the UI? After installing the .NET MAUI agent, wait at least 5 minutes. If no HTTP data appears on the HTTP errors and HTTP requests UI pages, make sure you used `HttpMessageHandler` in `HttpClient`. + + +### Missing Distributed Tracing Data in the UI + +Distributed Tracing does not work when you use static methods to report HTTP data. To enable Distributed Tracing, you must use `HttpMessageHandler` with `HttpClient`. + +```csharp +HttpClient myClient = new HttpClient(CrossNewRelic.Current.GetHttpMessageHandler()); + + var response = await myClient.GetAsync(new Uri("https://jsonplaceholder.typicode.com/todos/1")); + if (response.IsSuccessStatusCode) + { + var content = await response.Content.ReadAsStringAsync(); + } else + { + Console.WriteLine("Http request failed"); + } +``` diff --git a/src/content/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-13-0.mdx b/src/content/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-13-0.mdx new file mode 100644 index 00000000000..450297d7ffb --- /dev/null +++ b/src/content/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-13-0.mdx @@ -0,0 +1,40 @@ +--- +subject: Node.js agent +releaseDate: '2025-02-12' +version: 12.13.0 +downloadLink: 'https://www.npmjs.com/package/newrelic' +security: [] +bugs: ["Fixed `api.getTraceMetadata` to handle when there is an active transaction but not active segment"] +features: ["Propagate agent root context when opentelemetry `ROOT_CONTEXT` is passed in to trace propagator.","Added timeslice metrics for synthesized producer segments","Added timeslice metrics for synthesized server segments","Added timeslice metrics for synthesized database segments","Provided ability to disable instrumentation for core Node.js libraries"] +--- + +## Notes + +#### Features + +* Added timeslice metrics for synthesized server segments ([#2924](https://github.com/newrelic/node-newrelic/pull/2924)) ([f404585](https://github.com/newrelic/node-newrelic/commit/f4045855a1cdbfb74e3217daf8bfa125aa6fe2e4)) +* Added timeslice metrics for synthesized producer segments ([#2939](https://github.com/newrelic/node-newrelic/pull/2939)) ([6832637](https://github.com/newrelic/node-newrelic/commit/68326377dcd23b574abae7c323ff93bc05c525ed)) +* Added timeslice metrics for synthesized database segments ([#2922](https://github.com/newrelic/node-newrelic/pull/2922)) ([8606f78](https://github.com/newrelic/node-newrelic/commit/8606f789772b7651d0c46ad50dad3a1da74e5e9c)) +* Propagate agent root context when opentelemetry `ROOT_CONTEXT` is passed in to trace propagator.([#2940](https://github.com/newrelic/node-newrelic/pull/2940)) ([b85111c](https://github.com/newrelic/node-newrelic/commit/b85111c46797dfbf399faf973e7a3e0ea6bbdc28)) + * Added logic to handle properly naming and ending transactions for server spans. +* Provided ability to disable instrumentation for core Node.js libraries ([#2927](https://github.com/newrelic/node-newrelic/pull/2927)) ([2d232f1](https://github.com/newrelic/node-newrelic/commit/2d232f16c167e5f84b7b7898a6c5410d9cece55e)) + +#### Bug fixes + +* Fixed `api.getTraceMetadata` to handle when there is an active transaction but not active segment ([#2944](https://github.com/newrelic/node-newrelic/pull/2944)) ([6db3b4d](https://github.com/newrelic/node-newrelic/commit/6db3b4d53a077a9738dd72d46e1ba1cee0d6af3f)) + +#### Documentation + +* Updated compatibility report ([#2920](https://github.com/newrelic/node-newrelic/pull/2920)) ([c7ae8be](https://github.com/newrelic/node-newrelic/commit/c7ae8befafa4c91fab6804cd95e20f5a93546ea4)) + +#### Miscellaneous chores + +* Localized OTEL attribute constants ([#2928](https://github.com/newrelic/node-newrelic/pull/2928)) ([965c41b](https://github.com/newrelic/node-newrelic/commit/965c41b3e64805ac14ae4dd36120b018ec5899f4)) +* Updated import-in-the-middle version ([#2923](https://github.com/newrelic/node-newrelic/pull/2923)) ([aa2781f](https://github.com/newrelic/node-newrelic/commit/aa2781fd9c7bed08d590e33682729a92f21f43a5)) + + +### Support statement: + +We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) + +See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/) \ No newline at end of file diff --git a/src/content/docs/serverless-function-monitoring/azure-function-monitoring/compatibility-requirement-azure-monitoring.mdx b/src/content/docs/serverless-function-monitoring/azure-function-monitoring/compatibility-requirement-azure-monitoring.mdx index ecbc20135b5..3d15aba9539 100644 --- a/src/content/docs/serverless-function-monitoring/azure-function-monitoring/compatibility-requirement-azure-monitoring.mdx +++ b/src/content/docs/serverless-function-monitoring/azure-function-monitoring/compatibility-requirement-azure-monitoring.mdx @@ -31,7 +31,7 @@ End-to-end distributed tracing is supported only for HTTP requests. Additionally ## Supported runtimes -Based on your hosting environment, the following runtimes are supported. +Based on your hosting environment, the following Azure Function runtime stacks are supported. @@ -45,20 +45,20 @@ Based on your hosting environment, the following runtimes are supported. -* .NET: `dotnet6.0`, `dotnet8.0` +* .NET: version 6 - 9, Isolated model only -* .NET: `dotnet6.0`, `dotnet8.0` +* .NET: version 6 - 9 -* .NET: `dotnet6.0`, `dotnet8.0` +* .NET: version 6 - 9, Isolated model only diff --git a/src/content/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx b/src/content/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx index 2d1a1ae32fd..5ef6eef32f3 100644 --- a/src/content/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx +++ b/src/content/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx @@ -37,7 +37,7 @@ Based on your requirement, select one of the following options to instrument you 1. Add the `NewRelic.Agent` NuGet package to your application project. * In Visual Studio code editor, use NuGet Package Manager to search for and add the latest version of `NewRelic.Agent` to your application. - * If you're using other development environments, you can add the package with `dotnet add packages NewRelic.Agent`. + * If you're using other development environments, you can add the package with `dotnet add package NewRelic.Agent`. 2. Use your preferred publishing mechanism to deploy your updated application to Azure. This includes the New Relic agent, which is installed to the `/home/site/www/newrelic` folder. diff --git a/src/content/docs/service-level-management/create-slm.mdx b/src/content/docs/service-level-management/create-slm.mdx index 39955deaac4..d4ba264ae70 100644 --- a/src/content/docs/service-level-management/create-slm.mdx +++ b/src/content/docs/service-level-management/create-slm.mdx @@ -648,6 +648,9 @@ To create service levels, follow these steps: alt="wildcards" src="/images/slm-wildcard.webp" /> + + +When writing your SLI queries, you can add [comments](https://docs.newrelic.com/docs/nrql/nrql-syntax-clauses-functions/#comments) to help your team members better understand the query. - ```SQL - SELECT count(*), average(threadCount), average(cpuPercent), average(cpuSystemPercent) FROM ProcessSample FACET commandName SINCE 1 hour ago + ```sql + SELECT count(*), average(threadCount), average(cpuPercent), average(cpuSystemPercent) + FROM ProcessSample FACET commandName SINCE 1 hour ago ``` @@ -86,8 +87,9 @@ This tutorial shows you different ways to add data to dashboards. You will: - ```SQL - SELECT average(transmitBytesPerSecond) from NetworkSample FACET hostname LIMIT 5 timeseries + ```sql + SELECT average(transmitBytesPerSecond) + FROM NetworkSample FACET hostname LIMIT 5 TIMESERIES ``` diff --git a/src/content/whats-new/2024/12/whats-new-03-12-confluent-cloud-integration.md b/src/content/whats-new/2024/12/whats-new-03-12-confluent-cloud-integration.md new file mode 100644 index 00000000000..2ef360444df --- /dev/null +++ b/src/content/whats-new/2024/12/whats-new-03-12-confluent-cloud-integration.md @@ -0,0 +1,17 @@ +--- +title: 'Monitor your Kafka Metrics with API Polling for Confluent Cloud Integration' +summary: 'Seamlessly integrate your Kafka Confluent Cloud Metrics into New Relic. You can now monitor your Clusters and Topics with ease via API Polling' +releaseDate: '2024-12-03' +learnMoreLink: 'https://docs.newrelic.com/docs/infrastructure/other-infrastructure-integrations/confluent-cloud-integration +' +--- + +We're excited to announce that you can now monitor the health of your Confluent Cloud Kafka Clusters. This can be done through the new Confluent Cloud integration via API Polling. + +Confluent Cloud lets developers to focus on building applications, microservices and data pipelines, rather than on managing the underlying infrastructure. With this integration, you can now monitor your clusters, topics, and brokers with ease. + +New Relic lets you create dashboards using this data. In February, we will release a public preview of a new feature called Messages Queues and Streaming, which provides out-of-the-box reports. This feature facilitates a seamless flow from clusters to topics and allow for a deep dive into any APM service utilizing Confluent Cloud for Kafka. Until then, all data are available for use, and custom dashboards can be created and saved. For more information on creating custom dashboards, see the documentation here. + + + + diff --git a/src/content/whats-new/2025/02/whats-new-02-12-one-click-log-forwarding-for-java-applications.md b/src/content/whats-new/2025/02/whats-new-02-12-one-click-log-forwarding-for-java-applications.md new file mode 100644 index 00000000000..507c33677c2 --- /dev/null +++ b/src/content/whats-new/2025/02/whats-new-02-12-one-click-log-forwarding-for-java-applications.md @@ -0,0 +1,34 @@ +--- +title: "1-Click Log Forwarding for Java Applications" +summary: "Quickly enable or disable Java application logs directly in the UI" +releaseDate: "2025-02-12" +--- + +In software, time is of the essence, especially when an issue may arise that may leave your customers without access to your service. These are the scenarios when you need logs the most. Traditionally, enabling or disabling logs in Java applications required coordinating with DevOps teams, manual configuration, and prolonged downtime. New Relic is excited to introduce a new feature that simplifies this process, adding ease and efficiency to your workflow. + +![Java application logs](/images/one-click-java-app-logs.webp "Java application logs table") + +## Why is this important: + +Engineers often face friction when needing to adjust Java application logging settings for tasks like debugging. This commonly includes rooting through configuration files or waiting for a DevOps team to implement changes, which can disrupt the development cycle. + +This new feature allows users to turn Java application logs on and off directly within the curated application UI, through our Server-Side Configuration. This gives users immediate control over logging in their service, streamlining the debugging process and enhancing agility. + +## How to Get Started: + +1. Ensure your application is running on New Relic version 7.6.0 or higher. +1. Access the Server-Side Configuration in the UI by locating Application underneath the Settings section of the secondary navigation or simply click enable logs in the banner at the top of the APM UI. +1. Turn on the Server Side Configuration toggle next to “Server-side agent configuration” +1. Opt in to Application log forwarding in the secondary radio option +1. Turn on application log forwarding in the main Application log forwarding section of the Server Side Configuration UI. + +![Java application settings](/images/one-click-java-app-settings.webp "Java application settings with arrows highlighting where to toggle on the server-side agent configuration and application log forwarding") + +## Things to Keep in Mind: + +- Only available on Java applications 7.6.0 and higher. +- If you turn on Server Side Configuration and opt-in to each individual section then you will override existing client-side settings for those values in the `.yml` files, or Java properties. +- Will not work if you are managing configurations via environment variables. +- Beyond logging, users can manage other configurations such as application transaction tracing and error handling, providing more control and granularity over their application's operation. + +By integrating this feature, New Relic continues to empower teams by reducing friction, accelerating development cycles, and providing deeper insight into their systems, all through a user-friendly interface. Transform your approach to application management and make cumbersome configuration changes a thing of the past—experience the freedom of Server-Side Configuration today! diff --git a/src/data/whats-new-ids.json b/src/data/whats-new-ids.json index 0b352607965..a442cd1548a 100644 --- a/src/data/whats-new-ids.json +++ b/src/data/whats-new-ids.json @@ -361,5 +361,8 @@ "/whats-new/2025/01/whats-new-03-01-rest-api-keys-eol": "43018", "/whats-new/2025/01/whats-new-01-22-React18-upgrade": "43019", "/whats-new/2025/01/whats-new-01-23-msconnector-eol": "43020", - "/whats-new/2025/02/what-new-10-02-sessions-replay": "43021" + "/whats-new/2025/02/what-new-10-02-sessions-replay": "43021", + "/whats-new/2025/02/whats-new-01-31-synthetics-ip": "43022", + "/whats-new/2024/12/whats-new-03-12-confluent-cloud-integration": "43023", + "/whats-new/2025/02/whats-new-02-12-one-click-log-forwarding-for-java-applications": "43024" } \ No newline at end of file diff --git a/src/i18n/content/es/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx b/src/i18n/content/es/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx index 11cc702484b..a9164e43b01 100644 --- a/src/i18n/content/es/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx +++ b/src/i18n/content/es/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx @@ -543,6 +543,30 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum * Versión mínima del agente requerida: 10.33.0 + + + + System.Data.ODBC + + + + + + + + Use [System.Data.Odbc](https://www.nuget.org/packages/System.Data.Odbc/). + + * Versión mínima admitida: 8.0.0 + * Latest verified compatible version: 9.0.1 + * Minimum agent version required: 10.35.0 + + The following features supported for ODBC datastore calls in .NET Framework (using the built-in System.Data namespace) are not supported for .NET 8+: + + * Connection `Open/OpenAsync` calls + * SqlDataReader `Read/NextResult` calls + * Slow SQL traces + + @@ -1153,6 +1177,10 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum Para instrumentar automáticamente el rendimiento de las llamadas de la aplicación .NET framework a estos almacenes de datos, asegúrese de tener la [versión 8.14 o superior del agente .NET](/docs/release-notes/agent-release-notes/net-release-notes): + Use the built-in `System.Data.ODBC` namespace from the .NET Framework. + + * Available in all currently supported .NET Framework agent versions. + * All versions of the .NET Framework currently supported by Microsoft are verified to be compatible. * Última versión compatible verificada: 4.0.40 * Versiones incompatibles conocidas: 4.0.44 o superior @@ -1257,6 +1285,18 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum + + + System.Data.ODBC + + + + + + + + + MongoDB (controlador legacy ) diff --git a/src/i18n/content/es/docs/browser/browser-monitoring/browser-pro-features/auto-logging.mdx b/src/i18n/content/es/docs/browser/browser-monitoring/browser-pro-features/auto-logging.mdx deleted file mode 100644 index fab00556fd8..00000000000 --- a/src/i18n/content/es/docs/browser/browser-monitoring/browser-pro-features/auto-logging.mdx +++ /dev/null @@ -1,151 +0,0 @@ ---- -title: Detectar automáticamente los logs de browser -metaDescription: Get a more complete picture of your front-end application -freshnessValidatedDate: '2024-11-18T00:00:00.000Z' -translationType: machine ---- - -El logging automático recopila mensajes de log emitidos desde el browser `console` para ayudarlo a maximizar la observabilidad de su aplicación frontend. - -Los logs del Browser se rastrean de forma predeterminada en el `WARN` nivel para el agente Pro y Pro+SPA, pero no están disponibles para el Lite agente del browser. Le recomendamos que primero confirme que está empleando el agente Pro o Pro+SPA. Consulte [Primeros pasos](#get-started). - -## Cómo funciona el logging automático del browser [#how-it-works] - -En función de los niveles de logging y las frecuencias de ejemplificación establecido en la configuración, la instrumentación automática de logs browser intentará recopilar mensajes de los siguientes métodos: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Método - - Nivel -
- `console.log` - - `'INFO'` -
- `console.error` - - `'ERROR'` -
- `console.warn` - - `'WARN'` -
- `console.info` - - `'INFO'` -
- `console.debug` - - `'DEBUG'` -
- `console.trace` - - `'TRACE'` -
- - - Los datos que pasan a través de los métodos de consola pueden pasar por serialización y [ofuscación](/docs/browser/new-relic-browser/configuration/obfuscate-browser-agent-data/). Dependiendo del tamaño y la frecuencia, esto puede afectar negativamente el rendimiento de la aplicación, así como los costos de datos. En general, NO se recomienda pasar objetos grandes o grandes cantidades de datos a los métodos de consola. - - -De forma predeterminada, los datos de logging se almacenan durante 30 días, pero la retención real de los datos depende de su cuenta. - -## Empezar [#get-started] - - - - ### Habilitar la recopilación automática de logs [#enable-configure-settings] - - 1. Vaya a **[one.newrelic.com](https://one.newrelic.com/all-capabilities) &gt; All Capabilities &gt; Browser**. - 2. Seleccione la aplicación de su browser . - 3. En el menú de la izquierda, haga clic en **Application settings**. - 4. En la página de configuración de la aplicación, cerciorar de que el agente del browser **Pro** o **Pro + SPA** esté seleccionado. La detección automática de logs no está disponible para el Lite agente del browser. - 5. Activar la configuración **Browser logs** . - - - - ### Configurar tasas de muestreo [#configure-sampling-rates] - - Establezca una frecuencia de muestreo (0%-100%) para las siguientes muestras: - - * **User sessions** registra una muestra aleatoria de todas las sesiones de usuario. - - Por ejemplo, si establece la frecuencia de ejemplificación de la sesión al 50%, significa que: - - * La mitad de todas las sesiones de usuario recopilarán automáticamente el log de eventos. - - - - ### Ver log de eventos [#view-events] - - Puede encontrar datos de logging en dos lugares: - - * En la página **Logs** : - - 1. Vaya a: **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) &gt; Logs**. Para obtener detalles sobre lo que puede hacer en la UI, consulte [Logs UI](/docs/logs/ui-data/use-logs-ui). - - También puedes consultar el tipo de datos `Log` . Aquí hay un ejemplo simple de consulta NRQL: - - ```sql - SELECT * FROM Log - ``` - - También puede utilizar NerdGraph, nuestra API en formato GraphQL para [consultar datos](/docs/apis/nerdgraph/examples/nerdgraph-nrql-tutorial) o [configurar la administración de logs](/docs/apis/nerdgraph/examples/nerdgraph-log-parsing-rules-tutorial). - - * En la página **Errors inbox** : - - 1. En el menú browser de la izquierda, haga clic en **Errors**. - 2. Haga clic en las páginas **Triage** y **Group errors** para ver los logs adjuntos a los errores. - - - -## Consumo de datos [#data-consumption] - -Los logs siguen el mismo precio de consumo que los demás bytes de su browser . La cantidad de bytes producidos depende del número y la longitud de los mensajes. - -La función de logging automático elimina la necesidad de llamar a `newrelic.log` la `newrelic.wrapLogger` browser API o, excepto cuando se agrega un atributo personalizado al evento de registro. \ No newline at end of file diff --git a/src/i18n/content/es/docs/browser/browser-monitoring/browser-pro-features/session-replay/manage-session-replay-modify-capabilities.mdx b/src/i18n/content/es/docs/browser/browser-monitoring/browser-pro-features/session-replay/manage-session-replay-modify-capabilities.mdx index 0da96d818e8..c765611149a 100644 --- a/src/i18n/content/es/docs/browser/browser-monitoring/browser-pro-features/session-replay/manage-session-replay-modify-capabilities.mdx +++ b/src/i18n/content/es/docs/browser/browser-monitoring/browser-pro-features/session-replay/manage-session-replay-modify-capabilities.mdx @@ -108,5 +108,6 @@ Gestione las capacidades de reproducción y modificación de sesiones empleando - Es posible que pasen entre 5 y 10 minutos hasta que las configuraciones actualizadas aparezcan en la UI de las cuentas y los usuarios. + * La configuración **Session Replay** solo será accesible para [todos los administradores de productos](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts/#standard-roles) y el usuario **SR Modify** . Los usuarios con capacidad de lectura existente no podrán ver la configuración\*. + * Es posible que pasen entre 5 y 10 minutos hasta que las configuraciones actualizadas aparezcan en la UI de las cuentas y los usuarios. \ No newline at end of file diff --git a/src/i18n/content/es/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx b/src/i18n/content/es/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx index e32074ada39..cfa244139ce 100644 --- a/src/i18n/content/es/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx +++ b/src/i18n/content/es/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx @@ -31,7 +31,7 @@ Cerciorar de que sus Azure Functions cumplan con nuestros [requisitos y compatib 1. Agregue el paquete NuGet `NewRelic.Agent` a su proyecto de aplicación. * En el editor de código de Visual Studio, use el administrador de paquetes de NuGet para buscar y agregar la última versión de `NewRelic.Agent` a su aplicación. - * Si está empleando otros entornos de desarrollo, puede agregar el paquete con `dotnet add packages NewRelic.Agent`. + * Si está empleando otros entornos de desarrollo, puede agregar el paquete con `dotnet add package NewRelic.Agent`. 2. Emplee su mecanismo de publicación preferido para implementar su aplicación actualizada en Azure. Esto incluye el agente New Relic, que está instalado en la carpeta `/home/site/www/newrelic` . diff --git a/src/i18n/content/es/docs/synthetics/synthetic-monitoring/administration/synthetic-public-minion-ips.mdx b/src/i18n/content/es/docs/synthetics/synthetic-monitoring/administration/synthetic-public-minion-ips.mdx index 266aaa573f3..d50edcf45a1 100644 --- a/src/i18n/content/es/docs/synthetics/synthetic-monitoring/administration/synthetic-public-minion-ips.mdx +++ b/src/i18n/content/es/docs/synthetics/synthetic-monitoring/administration/synthetic-public-minion-ips.mdx @@ -30,6 +30,18 @@ Los minion se implementan en los servidores y los agentes se activan utilizando Las direcciones IP de las ubicaciones publicadas están sujetas a cambios. Si es necesario un cambio, intentaremos notificar proactivamente a los clientes antes de cualquier cambio por correo electrónico. También puede consultar el [Foro de soporte](https://discuss.newrelic.com/) para obtener actualizaciones. Los rangos de IP enumerados están reservados para uso de New Relic y nadie más puede utilizarlos. + + Si está agregando tráfico sintético a la lista blanca desde cualquier ubicación pública usando direcciones IP, debe actualizar sus listas blancas con los nuevos rangos de IP. Nuevos rangos de IP para incluir en la lista de permitidos: + + * 152.38.128.0/19 + * 212.32.0.0/20 + * 64.251.192.0/20 + + **If no action is taken** + + Si no actualiza sus listas de permitidos antes del **14 de abril de 2025**, es posible que sus controles Sintéticos no puedan conectarse a su aplicación, lo que puede generar conexiones fallidas y activar alertas. + + @@ -46,6 +58,10 @@ Las direcciones IP de las ubicaciones publicadas están sujetas a cambios. Si es
+ + La lista de rangos de IP en formato JSON cambiará después **del 14 de abril de 2025,** ya que algunas IP más antiguas serán reemplazadas por los nuevos rangos especificados anteriormente. Cerciorar de incluir en la lista blanca los rangos recién mencionados. + + ## Ubicaciones de Minion Público y etiquetas de ubicación. [#location] La siguiente tabla hace referencias cruzadas de las ubicaciones minion público de Sintético con sus etiquetas de ubicación. Puedes [consultar](/docs/query-your-data) el atributo `location` y `locationLabel` desde el evento [SyntheticCheck](/docs/insights/explore-data/attributes/synthetics-default-attributes-insights#syntheticcheck-table) y [SyntheticRequest](/docs/insights/explore-data/attributes/synthetics-default-attributes-insights#syntheticrequest-table) . diff --git a/src/i18n/content/fr/docs/accounts/accounts-billing/account-setup/choose-your-data-center.mdx b/src/i18n/content/fr/docs/accounts/accounts-billing/account-setup/choose-your-data-center.mdx new file mode 100644 index 00000000000..370cca470a6 --- /dev/null +++ b/src/i18n/content/fr/docs/accounts/accounts-billing/account-setup/choose-your-data-center.mdx @@ -0,0 +1,255 @@ +--- +title: Choisissez votre data center (US ou EU) +tags: + - Using New Relic + - Welcome to New Relic + - Get started +metaDescription: 'The New Relic global data hosting structure consists of two regions: the EU region and the US region.' +freshnessValidatedDate: never +translationType: machine +--- + +La structure d'hébergement de données mondiale de New Relic se compose de deux régions : la région de l'Union européenne (UE) et la région des États-Unis (US). + +## Requirements + +L'accès à la région New Relic EU nécessite les dernières versions de notre agent. + +* Pour les nouveaux clients : [installez la version la plus récente de l'agent](/docs/agents/manage-apm-agents/installation/install-agent). +* Pour les clients existants : [mettre à jour vers la version la plus récente de l'agent](/docs/agents/manage-apm-agents/installation/update-new-relic-agent). + +Version minimale de l'agent requise : + +* [Passez à la version 2.0.0](/docs/release-notes/agent-release-notes/go-release-notes) ou supérieure +* [Java 4.0.0](/docs/release-notes/agent-release-notes/java-release-notes) ou supérieur +* [.NET 8.0.0](/docs/release-notes/agent-release-notes/net-release-notes) ou supérieur +* [Node.js 3.0.0](/docs/release-notes/agent-release-notes/nodejs-release-notes) ou supérieur +* [PHP 8.0.0.204](/docs/release-notes/agent-release-notes/php-release-notes) ou supérieur +* [Python 3.0.0.89](/docs/release-notes/agent-release-notes/python-release-notes) ou supérieur +* [Ruby 5.0.0.342](/docs/release-notes/agent-release-notes/ruby-release-notes) ou supérieur + +## Régions et disponibilité [#regions-availability] + +Votre choix de data center n’est pas limité par votre situation géographique. Vous pouvez choisir de créer une organisation avec des données hébergées dans la région de l'UE ou des États-Unis, quel que soit l'endroit où vous ou votre système résidez. Vous êtes seul responsable du choix de la région de traitement et de stockage appropriée en fonction des lois, réglementations et autres exigences légales de tiers relatives à la localisation ou à la souveraineté des données qui vous sont applicables. + +New Relic propose presque tous les mêmes produits actifs, fonctionnalités, offres de support et niveaux de performances dans la région de l'UE que ce qui est proposé dans la région des États-Unis. + +**Exceptions:** Voici les **not supported** disposant d&apos;un compte dans la région UE : + +* Les [rapports de performances hebdomadaires](/docs/apm/reports/other-performance-analysis/weekly-performance-report) d&apos;APM ne sont pas disponibles. +* Les produits et fonctionnalités obsolètes ne sont pas disponibles. + +## Coûts des données [#data-costs] + +Les coûts d’ingestion de données dépendent de la région de votre data center. Pour plus de détails, consultez [le tableau des prix catalogue](/docs/licenses/license-information/usage-plans/new-relic-one-usage-plan-descriptions/#list-price). + +## Comptes interrégionaux [#account-structure] + +Lorsque vous vous inscrivez à New Relic, une [organisation New Relic](/docs/accounts/accounts-billing/account-structure/new-relic-account-structure/#organization-accounts) est créée. C&apos;est ce qui contient tous vos comptes et données. Lors de la création d&apos;une organisation, vous devez spécifier la région data center. Par défaut, une organisation New Relic et ses comptes ne peuvent se trouver que dans une seule région data center. + +## Créer une organisation régionale de l'UE [#create-eu-account] + +Pour créer une organisation New Relic dans la région UE : + +1. Accédez à la [page d'inscription](https://newrelic.com/signup/) de New Relic. + + OU + + Si vous avez une offre spécifique d'un partenaire New Relic, suivez directement ce lien. + +2. Suivez les étapes en ligne pour créer votre compte. + +3. Dans la liste déroulante **Select your region** , sélectionnez **European Union**. + +4. Accepter les [conditions d'utilisation](https://newrelic.com/terms "Le lien s'ouvre dans une nouvelle fenêtre"). + +5. Lorsque vous recevez un message de confirmation par e-mail, sélectionnez le lien pour confirmer votre compte et connectez-vous à New Relic. Ensuite, [installez](/docs/agents/manage-apm-agents/installation/install-agent) ou [mettez à jour vers](/docs/agents/manage-apm-agents/installation/update-new-relic-agent) la version la plus récente de l’agent. + +## points de terminaison d'API pour les comptes de la région UE [#endpoints] + +Si vous avez un compte de région UE, utilisez le point de terminaison approprié pour accéder à l'New Relic API suivante : + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ API + + Point de terminaison de l'UE +
+ [API de cartes sources du navigateur](/docs/browser/new-relic-browser/browser-pro-features/push-source-maps-api) + + ``` + sourcemaps.service.eu.newrelic.com + ``` +
+ [API d'alerte d'infrastructure](/docs/infrastructure/new-relic-infrastructure/infrastructure-alert-conditions/rest-api-calls-new-relic-infrastructure-alerts) + + ``` + infrastructure-alert.service.eu.newrelic.com + ``` +
+ [Applications mobiles](/docs/mobile-monitoring/new-relic-mobile/maintenance/viewing-your-application-token) + + ``` + rpm.eu.newrelic.com/mobile + ``` +
+ [API GraphQL de NerdGraph](/docs/apis/graphql-api/getting-started/introduction-new-relic-graphql-api) + + ``` + api.eu.newrelic.com/graphql + ``` +
+ [API partenaire](/docs/new-relic-partnerships/partnerships/partner-api) + + L'API partenaire est une API globale sans différences de données régionales. Utilisez ce point de terminaison pour les comptes de l’UE et des États-Unis : + + ``` + rpm.newrelic.com/api/v2/partners/ + ``` +
+ [REST API](/docs/apis/rest-api-v2/getting-started/introduction-new-relic-rest-api-v2) + + ``` + api.eu.newrelic.com + ``` +
+ [REST synthétique monitoring API](/docs/apis/synthetics-rest-api) + + ``` + synthetics.eu.newrelic.com/synthetics/api + ``` +
+ [API de trace](/docs/apm/distributed-tracing/trace-api/introduction-new-relic-trace-api) + + ``` + trace-api.eu.newrelic.com/trace/v1 + ``` +
+ [API métrique](/docs/introduction-new-relic-metric-api) + + ``` + metric-api.eu.newrelic.com/metric/v1 + ``` +
+ [API de log](/docs/introduction-new-relic-logs-api) + + ``` + log-api.eu.newrelic.com/log/v1 + ``` +
+ [Evénement API](/docs/data-apis/ingest-apis/introduction-event-api) + + ``` + insights-collector.eu01.nr-data.net + ``` +
+ [API de requête Insights](/docs/insights/insights-api/get-data/query-insights-event-data-api) + + ``` + insights-api.eu.newrelic.com + ``` +
+ +## Accéder à New Relic [#access] + +Si votre organisation New Relic transmet des données au [data centerde l'UE](/docs/using-new-relic/welcome-new-relic/getting-started/introduction-eu-region-data-center), utilisez le lien suivant pour accéder à New Relic: **[one.eu.newrelic.com](https://one.eu.newrelic.com)**. + +## Facturation et tarification [#billing-pricing] + +Le [processus de facturation des comptes et les tarifs des options](/docs/accounts/accounts/subscription-pricing/account-pricing-billing-options) de New Relic sont les mêmes pour les régions de l&apos;UE et des États-Unis. + +## Accès et traitement opérationnels [#data-retention] + +[Les données des clients](/docs/licenses/license-information/product-definitions/new-relic-one-pricing-definitions#customer-data) sont hébergées dans la région sélectionnée lors de [la création du compte](#create-eu-account). [Les données d'exploitation du système](https://newrelic.com/termsandconditions/services-notices) sont stockées dans la région des États-Unis. Toutes les autres informations, y compris les informations de compte (telles que les informations d&apos;abonnement de licence, la facturation et monitoring interne) sont hébergées dans la région des États-Unis et répliquées dans la région de l&apos;UE. + +New Relic peut accéder aux données des clients et les traiter aux États-Unis et dans d'autres juridictions où New Relic possède des sociétés affiliées et des filiales, y compris si cela peut être nécessaire pour maintenir, sécuriser ou exécuter les services, pour fournir un support technique ou si nécessaire pour se conformer à la loi ou à une ordonnance contraignante d'un organisme gouvernemental. + +Les données des comptes New Relic existants ne peuvent pas être transférées ou partagées entre les régions, et les nouvelles données générées ne peuvent pas être partagées avec les comptes existants. + +## Vérifiez que votre compte est basé dans la région de l'UE [#verifying-account] + +Utilisez l'une de ces options pour vérifier si les données de votre compte sont hébergées dans le data center de la région de l'UE : + +* Dans APM, passez la souris sur le nom de l'application pour afficher l'URL. Si le nom commence par `rpm.eu.newrelic.com/`, il s&apos;agit d&apos;un compte basé dans l&apos;UE. +* Vérifiez votre . Si le nom commence par `EU`, il s&apos;agit d&apos;un compte basé dans l&apos;UE. \ No newline at end of file diff --git a/src/i18n/content/fr/docs/accounts/accounts-billing/account-setup/create-your-new-relic-account.mdx b/src/i18n/content/fr/docs/accounts/accounts-billing/account-setup/create-your-new-relic-account.mdx new file mode 100644 index 00000000000..deb4c885c65 --- /dev/null +++ b/src/i18n/content/fr/docs/accounts/accounts-billing/account-setup/create-your-new-relic-account.mdx @@ -0,0 +1,49 @@ +--- +title: "S'inscrire à New\_Relic" +metaDescription: Sign up for a free forever New Relic account. +freshnessValidatedDate: never +translationType: machine +--- + +Chez New Relic, notre mission est de vous aider à créer des logiciels plus parfaits. Nous vous proposons donc **free access** notre plateforme d&apos;observabilité, **forever**. Vous pouvez ingérer [gratuitement](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing/#free) jusqu&apos;à 100 Go par mois et disposer d&apos;un [utilisateur de plateforme complet](/docs/accounts/accounts-billing/new-relic-one-user-management/user-type) et de **unlimited** utilisateurs de base. + +Prêt à commencer ? + + + + S'inscrire à New Relic + + + +Vous souhaitez en savoir plus en premier ? + +À titre d’exemple de ce que vous pouvez faire avec New Relic, imaginez que vous êtes un administrateur Kubernetes supervisant de nombreux clusters et pods de conteneurs logiciels. Par où commencer le dépannage ? Cette courte vidéo montre comment localiser un cluster de problèmes et utiliser le traçage distribué pour trouver les logs pertinents : + +