diff --git a/scripts/releaseNotes.mjs b/scripts/releaseNotes.mjs index 1fab40a280e..b0e956d5926 100755 --- a/scripts/releaseNotes.mjs +++ b/scripts/releaseNotes.mjs @@ -70,7 +70,9 @@ const INCLUDE_AGENTS = new Set([ 'python', 'ruby', 'sdk', - 'fluentbit' + 'fluentbit', + 'nrdot', + 'prometheus' ]); const generateReleaseNoteObject = async (filePath) => { diff --git a/src/content/docs/accounts/accounts-billing/new-relic-one-user-management/user-permissions.mdx b/src/content/docs/accounts/accounts-billing/new-relic-one-user-management/user-permissions.mdx index 808c65be3eb..51d4cb7ce8e 100644 --- a/src/content/docs/accounts/accounts-billing/new-relic-one-user-management/user-permissions.mdx +++ b/src/content/docs/accounts/accounts-billing/new-relic-one-user-management/user-permissions.mdx @@ -65,6 +65,7 @@ To learn more about specific permissions, select a category below, or try search * **Incidents**: relates to [alert incidents](/docs/alerts-applied-intelligence/new-relic-alerts/alert-policies/specify-when-alerts-create-incidents) and [view incidents from our products](/docs/alerts-applied-intelligence/new-relic-alerts/alert-incidents/view-alert-incidents-our-products). * **Lifecycle overrides**: relates to [muting rules](/docs/alerts-applied-intelligence/new-relic-alerts/alert-notifications/muting-rules-suppress-notifications). * **Policies**: relates to [alert policies](/docs/alerts-applied-intelligence/new-relic-alerts/alert-policies/create-edit-or-find-alert-policy). + * **Cross-account alerts**: relates to [cross-account alerts](/docs/alerts-applied-intelligence/new-relic-alerts/alert-policies/create-edit-or-find-alert-policy). - You should not enable AI monitoring if you're a [FedRAMP customer](/docs/security/security-privacy/compliance/certificates-standards-regulations/fedramp-moderate), because AI and AI-based technologies are not currently FedRAMP authorized. - - ## Compatible AI libraries [#compatibility] AI monitoring is compatible with these agent versions and AI libraries: diff --git a/src/content/docs/alerts/admin/user-settings.mdx b/src/content/docs/alerts/admin/user-settings.mdx index 37cfb27a82b..b2d901303de 100644 --- a/src/content/docs/alerts/admin/user-settings.mdx +++ b/src/content/docs/alerts/admin/user-settings.mdx @@ -48,3 +48,7 @@ When an issue is inactive, it won't be aggregated or correlated by our system. F An issue is considered inactive when it has collected 5,000 incidents. After 30 days, an inactive issue will be automatically closed. + +## Cross-account alerts [#cross-account-alerts] + +The cross-account alerts settings allow you to configure an alert condition to target data reported to an account other than the one that owns the condition. diff --git a/src/content/docs/alerts/create-alert/create-alert-condition/alert-conditions.mdx b/src/content/docs/alerts/create-alert/create-alert-condition/alert-conditions.mdx index b1534c75723..ac4357d1ab4 100644 --- a/src/content/docs/alerts/create-alert/create-alert-condition/alert-conditions.mdx +++ b/src/content/docs/alerts/create-alert/create-alert-condition/alert-conditions.mdx @@ -53,13 +53,6 @@ For all methods except for our guided mode, the process for creating an alert co In this example, imagine that your team manages the `WebPortal` application for an ecommerce site. You want to be alerted of any latency issues. - To create a new alert condition: - - * Go to [one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > **Alerts**. - * Select **Alert Conditions** in the left navigation. - * Then select **New alert condition**. - * Select **Write your own query**. - **Run**. A chart will appear and display the parameters that you've set. + + + To set up cross-account alerts, select a **data account** from the drop-down list. And you can only query a data from one account for cross-account alerts at a time. + - For this example, the chart will show the average latency for your `WebPortal` application. Click **Next** and begin configuring your alert condition. + For this example, the chart will show the average duration of a transaction. Click **Next** and begin configuring your alert condition. For this example, you will customize these advanced signal settings for the condition you created to monitor latency in your `WebPortal` application. @@ -177,6 +174,17 @@ For all methods except for our guided mode, the process for creating an alert co Learn more about gap-filling strategies in our [lost signal docs](/docs/apis/nerdgraph/examples/nerdgraph-api-loss-signal-gap-filling/). + + + Cross-account alerts in New Relic enable you to set up alert conditions that monitor data from a different account than the one where the alert is configured. This feature allows for greater flexibility in monitoring and managing dependencies across multiple accounts within New Relic. + + For more information, refer to [Cross-account alert](/docs/alerts/create-alert/create-alert-condition/cross-account-alert/). + + + @@ -344,6 +352,8 @@ For all methods except for our guided mode, the process for creating an alert co +To know more about the cross-account alerts, refer to our [Cross account alerts.](/docs/alerts/create-alert/create-alert-condition/cross-account-alert) + ## Edit an existing alert condition [#edit-existing-alert-condition] If you want to edit an alert condition you've already created, you can: diff --git a/src/content/docs/alerts/create-alert/create-alert-condition/cross-account-alert.mdx b/src/content/docs/alerts/create-alert/create-alert-condition/cross-account-alert.mdx new file mode 100644 index 00000000000..16f14233b6d --- /dev/null +++ b/src/content/docs/alerts/create-alert/create-alert-condition/cross-account-alert.mdx @@ -0,0 +1,95 @@ +--- +title: Cross-account alert +tags: + - Alerts + - Alert conditions +translate: + - jp +metaDescription: "Use the conditions page to identify what triggers an alert policy's notification, starting with the product and type of metric or service." +redirects: + - /docs/alerts-applied-intelligence/new-relic-alerts/get-started/your-first-nrql-condition + - /docs/alerts/alert-policies/configuring-alerts/managing-your-alerts + - /docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/alert-conditions + - /docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/advanced-techniques/select-product-targets-alert-condition + - /docs/alerts/create-alert/create-alert-condition/create-alert-conditions + - /docs/alerts/create-alert/create-alert-condition/update-or-disable-policies-conditions + - /docs/alerts/new-relic-alerts-beta/configuring-alert-policies/define-alert-conditions + - /docs/alerts/new-relic-alerts/configuring-alert-policies/define-alert-conditions + - /docs/alerts/new-relic-alerts-beta/configuring-alert-policies/select-product-targets-alert-condition +freshnessValidatedDate: never +--- + +New Relic's cross-account alert option enables you to set up alert conditions that monitor data from a different account than the one where the alert is configured. This feature allows for greater flexibility in monitoring and managing dependencies across multiple accounts within New Relic. + +In many organizations, different teams or departments may use separate New Relic accounts for their applications and infrastructure. Even if you are not directly responsible for an entity or data in another account, it may still be critical to your operations. For example, an application team might need to set up alerts for the hosts that run their application but are managed under a different account. + +This offers several benefits to: + +* **Manage** alerts across multiple accounts that you have access to, enabling a consolidated view of all relevant incidents and issues. +* **Limit** write and edit access to sensitive accounts, minimizing the need for multiple users to have permissions on accounts they do not directly manage. +* **Organize** alert configurations by reducing unnecessary alerts on accounts that serve as data sources for others. +* **Delegate** alert threshold management and governance to the appropriate teams, easing the burden on account owners. +* **Ensure** timely alerts for critical dependencies, even if they reside in different New Relic accounts. + +## Get started [#get-started] + +Before you start using cross-account alerts: + +* You must first enable the data sharing between accounts. This is currently being done only on a per-account basis in New Relic UI. +* Organization managers will have the ability to turn the data-sharing toggle **on**. +* Alternatively, you can create a custom role with the **Cross-account conditions: Data-sharing access control** permission and assign it to the users to whom you want to grant this capability. For more information, refer to [Create custom roles](/docs/accounts/accounts-billing/new-relic-one-user-management/account-user-mgmt-tutorial/#roles/). + +Once you've ensured your user has the proper role and permission, you can allow other accounts to query data from the selected account by following the below steps: + + + + + Go to [one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > **Alerts**. + + + + On the left navigation menu, select **General** + + + + Go to **Cross-accounts**, and enable **Let other accounts query data from this account**. + + + + Click **Save**. + + + + +There is also an API that enables users with the appropriate roles and permissions to opt multiple accounts in or out simultaneously. For more information, refer to [Add API examples for cross-accogit unt alert elections.](/docs/apis/nerdgraph/examples/nerdgraph-api-cross-account-alerting-elections) + +As long as you have at least read-only access to the data account, you can create alert conditions and query data from any account within your organization. + +## Create a cross-account alert condition + +You can create cross-account alerts in the following ways: + +* **API**: Enter the account number you'd like your condition to target in the `dataAccountId` field in the condition builder API. For more information, refer to [NRQL condition](/docs/apis/nerdgraph/examples/nerdgraph-api-nrql-condition-alerts/#create-cross-account-alert). + + -OR- + +* **UI**: In the query mode of the condition builder UI, you'll see a drop-down as part of the first step. This menu lists the accounts that you can access for querying in your new alert. For more information, refer to [Create alert condition using query mode.](/docs/alerts/create-alert/create-alert-condition/alert-conditions/#advanced-signal-settings) + + + At this time, the entity health status is not affected by any cross-account alert conditions. + + +## Restrict data sharing for cross account alerts + +When an account stops sharing data (the **Let other accounts query data from this account** option is disabled), then: + +* The account does not appear in the drop-down, when choosing where to query for your new alert conditions. +* Any previously created alert conditions targeting that account's data will be deleted, and evaluation will stop. All history pertaining to that condition will be deleted. + +## Data visibility + +Currently, when using this feature, any user with at least read access to the account that owns the alert condition can view cross-account alert condition information. This access is granted regardless of whether the user has `read` access to the originating account. Users can see: + +* Condition names and details, including condition signals, facet names, etc. +* Issues and incidents pertaining to the cross account condition, including signals, facet names in the incident titles, etc. +* Workflows to set up notifications on cross account alert conditions. diff --git a/src/content/docs/alerts/get-notified/new-relic-webhook-for-microsoft-teams-workflow.mdx b/src/content/docs/alerts/get-notified/new-relic-webhook-for-microsoft-teams-workflow.mdx index f5562de54e9..641aea5393b 100644 --- a/src/content/docs/alerts/get-notified/new-relic-webhook-for-microsoft-teams-workflow.mdx +++ b/src/content/docs/alerts/get-notified/new-relic-webhook-for-microsoft-teams-workflow.mdx @@ -40,137 +40,139 @@ Microsoft is retiring Microsoft 365 webhook-based Connectors service in Teams by /> 3. On the Edit notification message screen, in the **Template** field, copy and paste the following payload: ```json +{ + "type": "message", + "attachments": [ + { + "contentType": "application/vnd.microsoft.card.adaptive", + "contentUrl": null, + "content": { + "$schema": "http://adaptivecards.io/schemas/adaptive-card.json", + "type": "AdaptiveCard", + "version": "1.2", + "msteams": { "width": "full" }, + "body": [ { - "type": "message", - "attachments": [ - { - "contentType": "application/vnd.microsoft.card.adaptive", - "contentUrl": null, - "content": { - "$schema": "https://adaptivecards.io/schemas/adaptive-card.json", - "type": "AdaptiveCard", - "version": "1.2", - "body": [ - { "type": "ColumnSet", "columns": [ + + { + "type": "Column", + "items": [ + { + "type": "Image", + "style": "Person", + "url": "https://avatars.slack-edge.com/2022-06-02/3611814361970_f6a28959c2e7258660ea_512.png", + "size": "Small" + } + ], + "width": "auto" + }, + { - "type": "Column", - "items": [ - { - "type": "Image", - "style": "Person", - "url": "https://avatars.slack-edge.com/2022-06-02/3611814361970_f6a28959c2e7258660ea_512.png", - "size": "medium" - } - ], - "width": "auto" - }, - { - "type": "Column", - "items": [ - { - "type": "TextBlock", - "size": "large", - "weight": "bolder", - "text": "{{ priorityText }} priority issue is {{#if issueClosedAt}}CLOSED{{else}}{{#if issueAcknowledgedAt}}ACKNOWLEDGED{{else}}ACTIVATED{{/if}}{{/if}}" - }, - { - "type": "TextBlock", - "size": "large", - "wrap": "true", - "maxLines": "2", - "weight": "bolder", - "text": "[{{ issueTitle }}]({{ issuePageUrl }})" - } - ], - "width": "stretch" + "type": "Column", + "items": [ + { + "type": "TextBlock", + "size": "large", + "weight": "bolder", + "text": "{{ priorityText }} priority issue is {{#if issueClosedAt}}CLOSED{{else}}{{#if issueAcknowledgedAt}}ACKNOWLEDGED{{else}}ACTIVATED{{/if}}{{/if}}" + }, + { + "type": "TextBlock", + "size": "large", + "wrap": "true", + "maxLines": "2", + "weight": "bolder", + "text": "[{{ issueTitle }}]({{ issuePageUrl }})" + } + ], + "width": "stretch" } ] - }, - {{#if accumulations.conditionDescription.[0]}} - { + }, + {{#if accumulations.conditionDescription.[0]}} + { "type": "TextBlock", "text": {{ json accumulations.conditionDescription.[0] }}, "wrap": true - }, - {{/if}} - {{#eq "Not Available" violationChartUrl}} - {{else}} - { + }, + {{/if}} + {{#eq "Not Available" violationChartUrl}} + {{else}} + { "type": "Image", "url": {{ json violationChartUrl }} - }, - {{/eq}} - { + }, + {{/eq}} + { "type": "FactSet", "facts": [ { - "title": "*Impacted entities:*", - "value": "{{#each entitiesData.names}}{{#lt @index 5}}{{this}}{{#unless @last}},{{/unless}}{{/lt}}{{/each}}" + "title": "*Impacted entities:*", + "value": "{{#each entitiesData.names}}{{#lt @index 5}}{{this}}{{#unless @last}},{{/unless}}{{/lt}}{{/each}}" }, {{#if accumulations.policyName }} { - "title": "*Policy:*", - "value": {{ json accumulations.policyName.[0]}} + "title": "*Policy:*", + "value": {{ json accumulations.policyName.[0]}} }, {{/if}} {{#if accumulations.conditionName }} { - "title": "*Condition:*", - "value": {{ json accumulations.conditionName.[0]}} + "title": "*Condition:*", + "value": {{ json accumulations.conditionName.[0]}} }, {{#eq impactedEntitiesCount 1}} {{else}} { - "title": "*Total Incidents:*", - "value": {{ json impactedEntitiesCount}} + "title": "*Total Incidents:*", + "value": {{ json impactedEntitiesCount}} }, {{/eq}} {{/if}} { - "title": "Workflow Name:", - "value": {{ json workflowName }} + "title": "Workflow Name:", + "value": {{ json workflowName }} } ] - }, - { + }, + { "type": "ActionSet", "actions": [ - { - "type": "Action.OpenUrl", - "title": "📥 Acknowledge", - "url": {{ json issueAckUrl }} - }, - { - "type": "Action.OpenUrl", - "title": "✔️ Close", - "url": {{ json issueCloseUrl }} - }, - {{#if accumulations.deepLinkUrl}} - { - "type": "Action.OpenUrl", - "title": "🔎 View Query", - "url": {{ json accumulations.deepLinkUrl.[0] }}, - "mode": "secondary" - }, - {{/if}} - {{#if accumulations.runbookUrl}} - { - "type": "Action.OpenUrl", - "title": "📕 View Runbook", - "url": {{ json accumulations.runbookUrl.[0] }}, - "mode": "secondary" - } - {{/if}} - ] - } - ] - } - } - ] + { + "type": "Action.OpenUrl", + "title": "📥 Acknowledge", + "url": {{ json issueAckUrl }} + }, + { + "type": "Action.OpenUrl", + "title": "✔️ Close", + "url": {{ json issueCloseUrl }} + } + {{#if accumulations.deepLinkUrl}} + ,{ + "type": "Action.OpenUrl", + "title": "🔎 View Query", + "url": {{ json accumulations.deepLinkUrl.[0] }}, + "mode": "secondary" + } + {{/if}} + {{#if accumulations.runbookUrl}} + ,{ + "type": "Action.OpenUrl", + "title": "📕 View Runbook", + "url": {{ json accumulations.runbookUrl.[0] }}, + "mode": "secondary" + } + {{/if}} + ] } - } + ] + } + } + ] +} ``` 4. Click **Save message**. diff --git a/src/content/docs/alerts/get-notified/notification-integrations.mdx b/src/content/docs/alerts/get-notified/notification-integrations.mdx index 47677ebc26d..6c2bfdf95bf 100644 --- a/src/content/docs/alerts/get-notified/notification-integrations.mdx +++ b/src/content/docs/alerts/get-notified/notification-integrations.mdx @@ -601,7 +601,7 @@ Read more about each of our specific notification integrations. To create a ServiceNow destination, follow these steps: - 1. [Download and install the New Relic application](https://store.servicenow.com/sn_appstore_store.do#!/store/application/d117597d1b9b9d9078faddf7b04bcba7/1.0.0?referer=%2Fstore%2Fsearch%3Flistingtype%3Dallintegrations%25253Bancillary_app%25253Bcertified_apps%25253Bcontent%25253Bindustry_solution%25253Boem%25253Butility%25253Btemplate%26q%3Dnew%2520relic&sl=sh) in the ServiceNow store. + 1. [Download and install the New Relic application](https://store.servicenow.com/sn_appstore_store.do#!/store/application/d117597d1b9b9d9078faddf7b04bcba7/1.1.1?referer=%2Fstore%2Fsearch%3Flistingtype%3Dallintegrations%25253Bancillary_app%25253Bcertified_apps%25253Bcontent%25253Bindustry_solution%25253Boem%25253Butility%25253Btemplate%26q%3Dnew%2520relic&sl=sh) in the ServiceNow store. 2. Create a user inside ServiceNow. Make sure you enable the **Web service access only** option and grant the `x_newre_core.inbound_api` role to the created user. Copy and save the generated password. diff --git a/src/content/docs/apis/nerdgraph/examples/nerdgraph-api-cross-account-alerting-elections.mdx b/src/content/docs/apis/nerdgraph/examples/nerdgraph-api-cross-account-alerting-elections.mdx new file mode 100644 index 00000000000..e76eaba72ac --- /dev/null +++ b/src/content/docs/apis/nerdgraph/examples/nerdgraph-api-cross-account-alerting-elections.mdx @@ -0,0 +1,45 @@ +--- +title: "NerdGraph tutorial: Elections for cross-account alerting" +tags: + - Alerts + - Alerts and NerdGraph +metaDescription: 'Examples of how to use the NerdGraph API explorer to update account elections for cross-account alerting.' +freshnessValidatedDate: never +--- + +To allow data sharing between accounts within an organization, an account must opt in to the 'cross-account alerting' feature. Follow these instructions on how to use the NerdGraph API Explorer to update account settings by enabling cross-account alerting. + + + Only users with the "Data-sharing access control" permission can update cross-account elections for data sharing. By default, this permission is granted only to users with the "Organization Manager" role. + + +## Steps to update a cross-account alerting election + + + + + Collect the list of account IDs to update. The API accepts up to **20 account IDs**. + + + + Indicate whether you want to enable `true` or disable `false` the election. + + + + Use the NerdGraph API explorer to update the account elections. + + + + +Here's an example of the mutation: + +```graphql +mutation { + alertsUpdateCrossAccountElections( + accountIds: [YOUR_1ST_ACCOUNT_ID, YOUR_2ND_ACCOUNT_ID, YOUR_3RD_ACCOUNT_ID], + electionStatus: true + ) { + electionStatus + } +} +``` diff --git a/src/content/docs/apis/nerdgraph/examples/nerdgraph-api-nrql-condition-alerts.mdx b/src/content/docs/apis/nerdgraph/examples/nerdgraph-api-nrql-condition-alerts.mdx index 86c7669b3bb..ae4feb5d5fd 100644 --- a/src/content/docs/apis/nerdgraph/examples/nerdgraph-api-nrql-condition-alerts.mdx +++ b/src/content/docs/apis/nerdgraph/examples/nerdgraph-api-nrql-condition-alerts.mdx @@ -105,6 +105,43 @@ mutation { } ``` +## Create cross-account alert [#create-cross-account-alert] + +Here's an example of creating a static condition: + +```graphql + mutation { + alertsNrqlConditionStaticCreate( + accountId: YOUR_ACCOUNT_ID + policyId: YOUR_POLICY_ID + condition: { + name: "Low Host Count - Catastrophic" + enabled: true + nrql: { + query: "SELECT uniqueCount(host) FROM Transaction WHERE appName='my-app-name'" + dataAccountId: YOUR_DATA_ACCOUNT_ID + } + signal: { + aggregationWindow: 60 + aggregationMethod: EVENT_FLOW + aggregationDelay: 120 + } + terms: { + threshold: 2 + thresholdOccurrences: AT_LEAST_ONCE + thresholdDuration: 600 + operator: BELOW + priority: CRITICAL + } + violationTimeLimitSeconds: 86400 + } + ) { + id + name + } +} +``` + ## Update a condition [#update-condition] Complete the following: diff --git a/src/content/docs/apm/agents/go-agent/configuration/go-agent-configuration.mdx b/src/content/docs/apm/agents/go-agent/configuration/go-agent-configuration.mdx index 7650a17ff5d..c7148b6c6f2 100644 --- a/src/content/docs/apm/agents/go-agent/configuration/go-agent-configuration.mdx +++ b/src/content/docs/apm/agents/go-agent/configuration/go-agent-configuration.mdx @@ -1765,6 +1765,11 @@ This section includes Go agent configurations for setting up AI monitoring. If distributed tracing is disabled or high security mode is enabled, AI monitoring will not collect AI data. + + When enabled, AI monitoring records a streaming copy of inputs and outputs sent to and from the models you choose to monitor, including any personal information contained therein. + You're responsible for obtaining consent from your model users that their interactions may be recorded by a third party (New Relic) for the purpose of providing the AI monitoring feature. + + [Java agent](/docs/agents/java-agent/getting-started/new-relic-java). This API consists of: * Static methods on the `com.newrelic.api.agent.NewRelic` class -* A [@Trace annotation](/docs/agents/java-agent/custom-instrumentation/java-instrumentation-annotation) for implementing custom instrumentation +* A [`@Trace` annotation](/docs/agents/java-agent/custom-instrumentation/java-instrumentation-annotation) for implementing custom instrumentation * A hierarchy of API objects providing additional functionality Use this API to set up [custom instrumentation](/docs/agents/java-agent/custom-instrumentation/java-custom-instrumentation) of your Java app and collect more in-depth data. For detailed information about this API, see the complete [Javadoc on GitHub](http://newrelic.github.io/java-agent-api/javadoc/index.html?com/newrelic/api/agent/NewRelic.html). @@ -49,7 +49,7 @@ You can call the API even without the agent running, but the methods will be a n ## Transactions -To instrument [`Transactions`](/docs/apm/applications-menu/monitoring/transactions-page) in your application, use the following APIs. +To instrument [transactions](/docs/apm/applications-menu/monitoring/transactions-page) in your application, use the following APIs. @@ -650,9 +650,11 @@ The following APIs provide additional functionality, such as setting app server diff --git a/src/content/docs/apm/agents/java-agent/configuration/java-agent-configuration-config-file.mdx b/src/content/docs/apm/agents/java-agent/configuration/java-agent-configuration-config-file.mdx index 21b99836e36..f2f50d961a0 100644 --- a/src/content/docs/apm/agents/java-agent/configuration/java-agent-configuration-config-file.mdx +++ b/src/content/docs/apm/agents/java-agent/configuration/java-agent-configuration-config-file.mdx @@ -1541,6 +1541,11 @@ This section details the Java agent configuration options for [AI monitoring](/d If distributed tracing is disabled or high security mode is enabled, AI monitoring will not collect AI data. + + When enabled, AI monitoring records a streaming copy of inputs and outputs sent to and from the models you choose to monitor, including any personal information contained therein. + You're responsible for obtaining consent from your model users that their interactions may be recorded by a third party (New Relic) for the purpose of providing the AI monitoring feature. + + + When enabled, AI Monitoring will record a streaming copy of inputs and outputs sent to and from the models you choose to monitor, including any personal information contained therein. When using AI Monitoring, you are responsible for obtaining consent from your model users that their interactions may be recorded by a third party (New Relic) for the purpose of providing the AI Monitoring feature. + + ```xml ``` 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 02dac862763..7c6f1425847 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 @@ -398,7 +398,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co The .NET agent `v9.2.0` or higher automatically instruments the [Microsoft.Azure.Cosmos](https://www.nuget.org/packages/Microsoft.Azure.Cosmos) library. * Minimum supported version: 3.17.0 - * Latest verified compatible version: 3.44.0 + * Latest verified compatible version: 3.46.1 * Versions 3.35.0 and higher are supported beginning with .NET agent v10.32.0 @@ -444,7 +444,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co Use [Oracle.ManagedDataAccess.Core](https://www.nuget.org/packages/Oracle.ManagedDataAccess.Core/) * Minimum supported version: 23.4.0 - * Latest verified compatible version: 23.6.0 + * Latest verified compatible version: 23.7.0 Older versions of `Oracle.ManagedDataAccess.Core` may be instrumented, but have not been tested and are not supported. @@ -517,7 +517,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co **MySql.Data** * Minimum supported version: 6.10.7 - * Latest verified compatible version: 8.4.0 + * Latest verified compatible version: 9.1.0 **MySqlConnector** * Minimum supported version: 1.0.1 @@ -539,7 +539,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co @@ -560,7 +560,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co **Elastic.Clients.Elasticsearch** * Minimum supported version: 8.0.0 - * Latest verified compatible version: 8.15.8 + * Latest verified compatible version: 8.15.10 * Versions 8.10.0 and higher are supported beginning with .NET agent v10.20.1 * Versions 8.12.1 and higher are supported beginning with .NET agent v10.23.0 @@ -610,7 +610,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co Use [AWSSDK.DynamoDBv2](https://www.nuget.org/packages/AWSSDK.DynamoDBv2). * Minimum supported version: 3.5.0 - * Latest verified compatible version: 3.7.404.5 + * Latest verified compatible version: 3.7.405.0 * Minimum agent version required: 10.33.0 @@ -709,7 +709,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co 10.23.0 @@ -788,7 +788,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co 9.7.0 @@ -846,7 +846,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co * Minimum supported version: 1.4.0 - * Latest verified compatible version: 2.5.3 + * Latest verified compatible version: 2.8.0 @@ -900,7 +900,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co * Minimum supported version: 7.1.0 - * Latest verified compatible version: 8.2.5 + * Latest verified compatible version: 8.3.4 @@ -914,7 +914,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co * Minimum supported version: 3.7.0 - * Latest verified compatible version: 3.7.400.33 + * Latest verified compatible version: 3.7.400.76 @@ -1315,7 +1315,8 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co The .NET agent `v9.2.0` or higher automatically instruments [Microsoft.Azure.Cosmos](https://www.nuget.org/packages/Microsoft.Azure.Cosmos) library. * Minimum supported version: 3.17.0 - * Latest verified compatible version: 3.23.0 + * Latest verified compatible version: 3.46.1 + * Versions 3.35.0 and higher are supported beginning with .NET agent v10.32.0 @@ -1452,7 +1453,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co **MySql.Data** * Minimum supported version: 6.10.7 - * Latest verified compatible version: 8.4.0 + * Latest verified compatible version: 9.1.0 **MySqlConnector** * Minimum supported version: 1.0.1 @@ -1476,7 +1477,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co Use [Oracle.ManagedDataAccess](https://www.nuget.org/packages/Oracle.ManagedDataAccess/) * Minimum supported version: 12.1.2400 - * Latest verified compatible version: 23.5.1 + * Latest verified compatible version: 23.7.0 @@ -1531,7 +1532,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co @@ -1552,7 +1553,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co **Elastic.Clients.Elasticsearch** * Minimum supported version: 8.0.0 - * Latest verified compatible version: 8.14.6 + * Latest verified compatible version: 8.15.10 * Versions 8.10.0 and higher are supported beginning with .NET agent v10.20.1 * Versions 8.12.1 and higher are supported beginning with .NET agent v10.23.0 @@ -1603,7 +1604,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co Use [AWSSDK.DynamoDBv2](https://www.nuget.org/packages/AWSSDK.DynamoDBv2). * Minimum supported version: 3.5.0 - * Latest verified compatible version: 3.7.404.5 + * Latest verified compatible version: 3.7.405.2 * Minimum agent version required: 10.33.0 @@ -1764,7 +1765,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co 10.23.0 @@ -1842,7 +1843,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co 9.7.0 @@ -1900,7 +1901,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co * Minimum supported version: 1.4.0 - * Latest verified compatible version: 2.5.3 + * Latest verified compatible version: 2.8.0 @@ -1963,7 +1964,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co * Minimum supported version: 7.1.0 - * Latest verified compatible version: 8.2.5 + * Latest verified compatible version: 8.3.4 @@ -1977,7 +1978,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co * Minimum supported version: 3.7.0 - * Latest verified compatible version: 3.7.400.33 + * Latest verified compatible version: 3.7.400.76 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 ddde99f0856..db83a3af978 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 @@ -259,6 +259,8 @@ Before [installing the agent](/docs/apm/agents/nodejs-agent/installation-configu +{/* The content between begin: compat-table and end: compat-table is automatically updated by the Node.js agent team bot. Don't change the contents and don't change the formatting of the data between the comments.*/} +{/* begin: compat-table */} ## Instrumented modules After installation, the agent automatically instruments with our catalog of @@ -270,306 +272,57 @@ frameworks or libraries, you'll need to instrument the agent yourself using the **Note**: The latest supported version may not reflect the most recent supported version. -
- [`public interface ErrorGroupCallback { - String generateGroupingString(ErrorData errorData); - }`](https://newrelic.github.io/java-agent-api/javadoc/index.html?com/newrelic/api/agent/NewRelic.html) + ``` + public interface ErrorGroupCallback { + String generateGroupingString(ErrorData errorData); + }() + ```
Minimum supported version: 1.0.488 - Latest verified compatible version: 2.8.16 + Latest verified compatible version: 2.8.24
- 3.7.404.5 + 3.7.411.17
- 5.3.14 + 5.3.15
* Minimum supported version: 1.0.488 - * Latest verified compatible version: 2.8.16 + * Latest verified compatible version: 2.8.24
- 3.7.404.5 + 3.7.411.17
- 5.3.14 + 5.3.15
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Package nameMinimum supported versionLatest supported versionIntroduced in*
`@apollo/gateway`2.3.02.8.4`@newrelic/apollo-server-plugin@1.0.0`
`@apollo/server`4.0.04.11.0`@newrelic/apollo-server-plugin@2.1.0`
`@aws-sdk/client-bedrock-runtime`3.474.03.629.011.13.0
`@aws-sdk/client-dynamodb`3.0.03.629.08.7.1
`@aws-sdk/client-sns`3.0.03.624.08.7.1
`@aws-sdk/client-sqs`3.0.03.624.08.7.1
`@aws-sdk/lib-dynamodb`3.377.03.624.08.7.1
`@aws-sdk/smithy-client`3.47.03.374.08.7.1
`@elastic/elasticsearch`7.16.08.15.011.9.0
`@grpc/grpc-js`1.4.01.11.18.17.0
`@hapi/hapi`20.1.221.3.109.0.0
`@koa/router`11.0.212.0.13.2.0
`@langchain/core`0.1.170.2.2311.13.0
`@nestjs/cli`9.0.010.4.410.1.0
`@prisma/client`5.0.05.18.011.0.0
`@smithy/smithy-client`2.0.03.1.1211.0.0
`amqplib`0.5.00.10.42.0.0
`apollo-server`3.0.03.13.0`@newrelic/apollo-server-plugin@1.0.0`
`apollo-server-express`3.0.03.13.0`@newrelic/apollo-server-plugin@1.0.0`
`aws-sdk`2.2.482.1673.06.2.0
`bluebird`2.0.03.7.21.27.0
`bunyan`1.8.121.8.159.3.0
`cassandra-driver`3.4.04.7.21.7.1
`connect`3.0.03.7.02.6.0
`express`4.6.04.19.22.6.0
`fastify`2.0.04.28.18.5.0
`generic-pool`3.0.03.9.00.9.0
`ioredis`4.0.05.4.11.26.2
`kafkajs`2.0.02.2.411.19.0
`koa`2.0.02.15.33.2.0
`koa-route`3.0.04.0.13.2.0
`koa-router`11.0.212.0.13.2.0
`memcached`2.2.02.2.21.26.2
`mongodb`4.1.46.8.01.32.0
`mysql`2.2.02.18.11.32.0
`mysql2`2.0.03.11.01.32.0
`next`13.4.1914.2.512.0.0
`openai`4.0.04.55.411.13.0
`pg`8.2.08.12.09.0.0
`pg-native`2.0.03.1.09.0.0
`pino`7.0.09.3.28.11.0
`q`1.3.01.5.11.26.2
`redis`3.1.04.7.01.31.0
`restify`11.0.011.1.02.6.0
`superagent`3.0.010.0.04.9.0
`undici`5.0.06.19.711.1.0
`when`3.7.03.7.81.26.2
`winston`3.0.03.14.18.11.0
+| Package name | Minimum supported version | Latest supported version | Introduced in* | +| --- | --- | --- | --- | +| `@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.726.1 | 11.13.0 | +| `@aws-sdk/client-dynamodb` | 3.0.0 | 3.726.1 | 8.7.1 | +| `@aws-sdk/client-sns` | 3.0.0 | 3.726.1 | 8.7.1 | +| `@aws-sdk/client-sqs` | 3.0.0 | 3.726.1 | 8.7.1 | +| `@aws-sdk/lib-dynamodb` | 3.377.0 | 3.726.1 | 8.7.1 | +| `@aws-sdk/smithy-client` | 3.47.0 | 3.374.0 | 8.7.1 | +| `@elastic/elasticsearch` | 7.16.0 | 8.17.0 | 11.9.0 | +| `@grpc/grpc-js` | 1.4.0 | 1.12.5 | 8.17.0 | +| `@hapi/hapi` | 20.1.2 | 21.3.12 | 9.0.0 | +| `@koa/router` | 11.0.2 | 13.1.0 | 3.2.0 | +| `@langchain/core` | 0.1.17 | 0.3.30 | 11.13.0 | +| `@nestjs/cli` | 9.0.0 | 10.4.9 | 10.1.0 | +| `@opensearch-project/opensearch` | 2.1.0 | 3.1.0 | 12.10.0 | +| `@prisma/client` | 5.0.0 | 6.2.1 | 11.0.0 | +| `@smithy/smithy-client` | 2.0.0 | 4.1.2 | 11.0.0 | +| `amqplib` | 0.5.0 | 0.10.5 | 2.0.0 | +| `apollo-server` | 3.0.0 | 3.13.0 | `@newrelic/apollo-server-plugin@1.0.0` | +| `apollo-server-express` | 3.0.0 | 3.13.0 | `@newrelic/apollo-server-plugin@1.0.0` | +| `aws-sdk` | 2.2.48 | 2.1692.0 | 6.2.0 | +| `bluebird` | 2.0.0 | 3.7.2 | 1.27.0 | +| `bunyan` | 1.8.12 | 1.8.15 | 9.3.0 | +| `cassandra-driver` | 3.4.0 | 4.7.2 | 1.7.1 | +| `connect` | 3.0.0 | 3.7.0 | 2.6.0 | +| `express` | 4.6.0 | 4.21.2 | 2.6.0 | +| `fastify` | 2.0.0 | 5.2.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 | +| `kafkajs` | 2.0.0 | 2.2.4 | 11.19.0 | +| `koa` | 2.0.0 | 2.15.3 | 3.2.0 | +| `koa-route` | 3.0.0 | 4.0.1 | 3.2.0 | +| `koa-router` | 11.0.2 | 13.0.1 | 3.2.0 | +| `memcached` | 2.2.0 | 2.2.2 | 1.26.2 | +| `mongodb` | 4.1.4 | 6.12.0 | 1.32.0 | +| `mysql` | 2.2.0 | 2.18.1 | 1.32.0 | +| `mysql2` | 2.0.0 | 3.12.0 | 1.32.0 | +| `next` | 13.4.19 | 15.1.4 | 12.0.0 | +| `openai` | 4.0.0 | 4.78.1 | 11.13.0 | +| `pg` | 8.2.0 | 8.13.1 | 9.0.0 | +| `pg-native` | 3.0.0 | 3.2.0 | 9.0.0 | +| `pino` | 7.0.0 | 9.6.0 | 8.11.0 | +| `q` | 1.3.0 | 1.5.1 | 1.26.2 | +| `redis` | 3.1.0 | 4.7.0 | 1.31.0 | +| `restify` | 11.0.0 | 11.1.0 | 2.6.0 | +| `superagent` | 3.0.0 | 10.1.1 | 4.9.0 | +| `undici` | 5.0.0 | 7.2.3 | 11.1.0 | +| `when` | 3.7.0 | 3.7.8 | 1.26.2 | +| `winston` | 3.0.0 | 3.17.0 | 8.11.0 | *When package is not specified, support is within the `newrelic` package. @@ -581,54 +334,14 @@ The Node.js agent supports the following AI platforms and integrations. Through the `@aws-sdk/client-bedrock-runtime` module, we support: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ModelImageTextVision
AI21 Labs Jurassic-2❌✅-
Amazon Titan❌✅-
Anthropic Claude❌✅❌
Cohere❌✅-
Meta Llama2❌✅-
Meta Llama3❌✅-
+| Model | Image | Text | Vision | +| --- | --- | --- | --- | +| AI21 Labs Jurassic-2 | ❌ | ✅ | - | +| Amazon Titan | ❌ | ✅ | - | +| Anthropic Claude | ❌ | ✅ | ❌ | +| Cohere | ❌ | ✅ | - | +| Meta Llama2 | ❌ | ✅ | - | +| Meta Llama3 | ❌ | ✅ | - | Note: if a model supports streaming, we also instrument the streaming variant. @@ -637,81 +350,26 @@ Note: if a model supports streaming, we also instrument the streaming variant. The following general features of Langchain are supported: - - - - - - - - - - - - - - - - - -
AgentsChainsToolsVectorstores
✅✅✅✅
+| Agents | Chains | Tools | Vectorstores | +| --- | --- | --- | --- | +| ✅ | ✅ | ✅ | ✅ | Models/providers are generally supported transitively by our instrumentation of the provider's module. - - - - - - - - - - - - - - - - - - - - - - - - - -
ProviderSupportedTransitively
Azure OpenAI❌❌
Amazon Bedrock❌❌
OpenAI✅✅
+| Provider | Supported | Transitively | +| --- | --- | --- | +| Azure OpenAI | ❌ | ❌ | +| Amazon Bedrock | ❌ | ❌ | +| OpenAI | ✅ | ✅ | ### OpenAI Through the `openai` module, we support: - - - - - - - - - - - - - - - - - - - - - -
AudioChatCompletionsEmbeddingsFilesImages
❌✅✅✅❌❌
+| Audio | Chat | Completions | Embeddings | Files | Images | +| --- | --- | --- | --- | --- | --- | +| ❌ | ✅ | ✅ | ✅ | ❌ | ❌ | {/* end: compat-table */} diff --git a/src/content/docs/apm/agents/nodejs-agent/installation-configuration/nodejs-agent-configuration.mdx b/src/content/docs/apm/agents/nodejs-agent/installation-configuration/nodejs-agent-configuration.mdx index b0eca063cbd..ea8c9cd5e96 100644 --- a/src/content/docs/apm/agents/nodejs-agent/installation-configuration/nodejs-agent-configuration.mdx +++ b/src/content/docs/apm/agents/nodejs-agent/installation-configuration/nodejs-agent-configuration.mdx @@ -927,6 +927,10 @@ This section includes Node.js agent configurations for setting up AI monitoring. You must enable [distributed tracing](/docs/apm/agents/nodejs-agent/installation-configuration/nodejs-agent-configuration/#dt-main) to capture AI data. It's turned on by default in Node.js agents 8.3.0 and higher. If you've enabled high security mode, AI monitoring will not work. + + When enabled, AI Monitoring will record a streaming copy of inputs and outputs sent to and from the models you choose to monitor, including any personal information contained therein. When using AI Monitoring, you are responsible for obtaining consent from your model users that their interactions may be recorded by a third party (New Relic) for the purpose of providing the AI Monitoring feature. + + - Prefix of attributes to include from all destinations. Allows `*` as wildcard at end. + Prefix of attributes to include from all destinations. Allows `*` as wildcard at end. For example, in the `config` file, this would include all parameters: ```js - attributes: { + attributes: { include: [ 'request.parameters.*' ] } ``` Using this example Express route definition and request URL: - + ```js app.get('/api/users/:id', myMiddleware, myController) ``` - + ```sh curl http://localhost:3000/api/users/abc123?id=true ``` - + The _route parameter_ is `id`, and has a value of `abc123`. This becomes the attribute `request.parameters.route.id: abc123` on the Transaction, root Segment, and Span. This example also has a _query parameter_ of `id`, which has a value of `true`. This would become the attribute `request.parameters.id: true` on the Transaction, root Segment, and Span. - + - Prefix of attributes to exclude from transaction events. Allows `*` as wildcard at end. + Prefix of attributes to exclude from transaction events. Allows `*` as wildcard at end. - Prefix of attributes to include in transaction events. Allows `*` as wildcard at end. + Prefix of attributes to include in transaction events. Allows `*` as wildcard at end. diff --git a/src/content/docs/apm/agents/python-agent/configuration/python-agent-configuration.mdx b/src/content/docs/apm/agents/python-agent/configuration/python-agent-configuration.mdx index 8689b3952fb..3debff6b9d8 100644 --- a/src/content/docs/apm/agents/python-agent/configuration/python-agent-configuration.mdx +++ b/src/content/docs/apm/agents/python-agent/configuration/python-agent-configuration.mdx @@ -76,9 +76,9 @@ Here are detailed descriptions of each configuration method: Starting with Python 3.11 the newer `.toml` syntax for configuration was added to the [standard library](https://docs.python.org/3/library/tomllib.html). Agent version `10.3.0` added support for using this newer format. The configuration file uses Tom's Obvious Minimal Language `.toml` files. For more information, see the [official file format documentation](https://toml.io/en/). - + To use the `.toml` syntax, the configuration file's name must end with `.toml` to indicate the syntax type. The standard `pyproject.toml` may be used alongside configuration for other libraries, or you may use a more specific file like `newrelic.toml`. - + The basic structure should look like the following: ```ini @@ -1448,6 +1448,11 @@ This section includes Python agent configurations for setting up AI monitoring. You must enable [distributed tracing](/docs/apm/agents/nodejs-agent/installation-configuration/nodejs-agent-configuration/#dt-main) to capture AI data. It's turned on by default in Python agent versions 7.0.0.166 and higher. + + When enabled, AI monitoring records a streaming copy of inputs and outputs sent to and from the models you choose to monitor, including any personal information contained therein. + You're responsible for obtaining consent from your model users that their interactions may be recorded by a third party (New Relic) for the purpose of providing the AI monitoring feature. + + - + A case-insensitive list of label names to exclude when you enable including labels in logs. This attribute does not support wildcards or regex. When adding labels as attributes, the agent prefixes the keys with `tags.`. This prefix is NOT included when matching against the exclude filtering rules. @@ -5849,4 +5854,4 @@ To disable default instrumentation, provide a special `import-hook` section corr enabled = false ``` - \ No newline at end of file + diff --git a/src/content/docs/new-relic-solutions/new-relic-one/core-concepts/new-relic-lookout-monitor-your-estate-glance.mdx b/src/content/docs/new-relic-solutions/new-relic-one/core-concepts/new-relic-lookout-monitor-your-estate-glance.mdx index 1b0e2b7e142..ea2b325bf6b 100644 --- a/src/content/docs/new-relic-solutions/new-relic-one/core-concepts/new-relic-lookout-monitor-your-estate-glance.mdx +++ b/src/content/docs/new-relic-solutions/new-relic-one/core-concepts/new-relic-lookout-monitor-your-estate-glance.mdx @@ -155,9 +155,9 @@ You can also create your own query. To do that: id="compare-one" title="Query: Compare the last 15 minutes to the same time 1 day ago" > - Please note that the UNTIL NOW portion is required here unlike in standard NRQL. Without the UNTIL NOW added, the system will query a 5 minute slice of data starting 15 minutes ago + Note that the `UNTIL NOW` portion is required here unlike in standard NRQL. Without the `UNTIL NOW` added, the system will query a 5 minute slice of data starting 15 minutes ago. - ``` + ```sql SINCE 15 minutes AGO UNTIL NOW COMPARE WITH 1 day ago ``` @@ -166,13 +166,13 @@ You can also create your own query. To do that: id="compare-one" title="Query: Compare a specific time range to the same range a month ago" > - ``` + ```sql SINCE '2021-03-07 07:00:00-0500' UNTIL '2021-03-08 07:00:00-0500' COMPARE WITH 1 month ago ``` Or: - ``` + ```sql SINCE 'today at midnight' UNTIL 'now' COMPARE WITH 1 MONTH AGO ``` diff --git a/src/content/docs/new-relic-solutions/new-relic-one/core-concepts/search-filter-entities.mdx b/src/content/docs/new-relic-solutions/new-relic-one/core-concepts/search-filter-entities.mdx index 0da8ffd55f1..0ba350159f4 100644 --- a/src/content/docs/new-relic-solutions/new-relic-one/core-concepts/search-filter-entities.mdx +++ b/src/content/docs/new-relic-solutions/new-relic-one/core-concepts/search-filter-entities.mdx @@ -27,12 +27,12 @@ Some tips for using the filter bar: * Type in a **string** of characters and/or numbers (for example, an environment) to find any entity that has this string in their name or ID. When typing, the UI suggests items that coincide with the string you're entering, so you can select one of those from the dropdown. You can also filter by the name of the **entity**, the **entity type**, **account ID**, **environment**, or a [**tag**](/docs/new-relic-one/use-new-relic-one/core-concepts/tagging-use-tags-organize-group-what-you-monitor). Selection parameters, once created, have a blue background. * If you filter using a string, the filter will have the `=` operator. -* If you filter using the dropdown menu, once the first element of the searched item (tag key or attribute) is entered, you need to select an operator (`=`, `!=`, `LIKE`, `NOT_LIKE`, `IN`, `NOT IN`) for your filter. +* If you filter using the dropdown menu, once the first element of the searched item (tag key or attribute) is entered, you need to select an operator (`=`, `!=`, `LIKE`, `NOT LIKE`, `IN`, `NOT IN`) for your filter. * Once the operator is selected, complete the filter by selecting the value to complete the search item. -To add more filters, first you have to select an operator, `AND` or `OR.` Tips on using these: +To add more filters, first you have to select an operator, `AND` or `OR`. Tips on using these: -* Use `AND` to indicate you want to restrict the selection removing entities from the list of results. You can also use the AND operator to add conditions that need to be met in the list of results, for example, **entityType = Services `AND` location = APAC**. +* Use `AND` to indicate you want to restrict the selection removing entities from the list of results. You can also use the `AND` operator to add conditions that need to be met in the list of results, for example, **entityType = Services `AND` location = APAC**. * Note that **entityType = Services `AND` entityType = Hosts** doesn’t return any results, as entities can only have one type and no entity would match this condition. * Use `OR` to add more entities to the selection. For example, the filter **entityType = Services `OR` entityType = Hosts** returns every entity you have access to that is of type `Services` or `Hosts`. diff --git a/src/content/docs/new-relic-solutions/new-relic-one/core-concepts/use-tags-help-organize-find-your-data.mdx b/src/content/docs/new-relic-solutions/new-relic-one/core-concepts/use-tags-help-organize-find-your-data.mdx index 71fec86c4f3..b642c33e30b 100644 --- a/src/content/docs/new-relic-solutions/new-relic-one/core-concepts/use-tags-help-organize-find-your-data.mdx +++ b/src/content/docs/new-relic-solutions/new-relic-one/core-concepts/use-tags-help-organize-find-your-data.mdx @@ -343,8 +343,8 @@ If you want to turn off infrastructure tag propagation, which means that you won ```sql SELECT rate(count(apm.service.transaction.duration), 1 minute) - FROM Metric WHERE appName LIKE 'MyApp (%' AND transactionType = 'Other' - FACET tags.Environment TIMESERIES + FROM Metric WHERE appName LIKE 'MyApp (%' AND transactionType = 'Other' + FACET tags.Environment TIMESERIES ``` @@ -356,8 +356,8 @@ If you want to turn off infrastructure tag propagation, which means that you won ```sql FROM Transaction SELECT count(*) - WHERE tags.Team = 'team-a' - FACET tags.Project TIMESERIES + WHERE tags.Team = 'team-a' + FACET tags.Project TIMESERIES ``` @@ -369,14 +369,14 @@ If you want to turn off infrastructure tag propagation, which means that you won ```sql FROM Metric SELECT count(apm.service.error.count) / count(apm.service.transaction.duration) - WHERE tags.Team = 'team-b' FACET appName + WHERE tags.Team = 'team-b' FACET appName ``` Related to this, you might create a general rule for a specific service deployed across several environments, so that we have an alarm for a single service monitoring each environment individually: ```sql - From Metric SELECT count(apm.service.error.count) / count(apm.service.transaction.duration) - WHERE tags.Project = 'MyProject' FACET tags.Environment + FROM Metric SELECT count(apm.service.error.count) / count(apm.service.transaction.duration) + WHERE tags.Project = 'MyProject' FACET tags.Environment ``` @@ -402,7 +402,14 @@ If you want to turn off infrastructure tag propagation, which means that you won Here's the NRQL query to select `cpuPercent`, broken down by the different experimental groups using a `FACET CASES (...)` clause: ```sql - FROM SystemSample SELECT cpuPercent FACET CASES (WHERE tags.experimentGroup = 'control' AS 'control group', WHERE tags.experimentGroup = 'A' AS 'given treatment A', WHERE tags.experimentGroup = 'B' AS 'given treatment B') SINCE 1 DAY AGO + FROM SystemSample SELECT cpuPercent + FACET CASES + ( + WHERE tags.experimentGroup = 'control' AS 'control group', + WHERE tags.experimentGroup = 'A' AS 'given treatment A', + WHERE tags.experimentGroup = 'B' AS 'given treatment B' + ) + SINCE 1 DAY AGO ``` @@ -414,13 +421,19 @@ If you want to turn off infrastructure tag propagation, which means that you won ```graphql mutation { - dataManagementUpdateFeatureSettings(accountId: YOUR_ACCOUNT_ID, setting: {enabled: false, featureSetting: {key: "infra_tag_propagation"}, locked: false}) - { - enabled - key - locked - name + dataManagementUpdateFeatureSettings( + accountId: YOUR_ACCOUNT_ID + setting: { + enabled: false + featureSetting: { key: "infra_tag_propagation" } + locked: false } + ) { + enabled + key + locked + name + } } ``` diff --git a/src/content/docs/new-relic-solutions/new-relic-one/workloads/workload-status-views-notifications.mdx b/src/content/docs/new-relic-solutions/new-relic-one/workloads/workload-status-views-notifications.mdx index ac00191c815..3cbfcb14c74 100644 --- a/src/content/docs/new-relic-solutions/new-relic-one/workloads/workload-status-views-notifications.mdx +++ b/src/content/docs/new-relic-solutions/new-relic-one/workloads/workload-status-views-notifications.mdx @@ -52,8 +52,10 @@ To set up the alert condition: 2. Where prompted to **Select a product**, click **NRQL**. 3. Add the following NRQL query: - ``` - SELECT latest(statusValueCode) FROM WorkloadStatus WHERE workloadGuid = 'YOUR_WORKLOAD_GUID' FACET workloadGuid as 'entity.guid', entity.name + ```sql + SELECT latest(statusValueCode) FROM WorkloadStatus + WHERE workloadGuid = 'YOUR_WORKLOAD_GUID' + FACET workloadGuid AS 'entity.guid', entity.name ``` 4. Some tips for writing your query: * Get the workload GUID by clicking on the **See metadata and manage tags** in the workloads UI. @@ -68,7 +70,7 @@ To set up the alert condition: * Choose to fill data gaps with **last known value**. 7. Optionally, you can also add a custom incident description that includes the workload name and permanent link to the UI in the alert notification: - ``` + ```handlebars Workload: {{tag.entity.name}} Direct link: https://one.newrelic.com/redirect/entity/{{tag.entity.guid}} ``` diff --git a/src/content/docs/nrql/get-started/introduction-nrql-new-relics-query-language.mdx b/src/content/docs/nrql/get-started/introduction-nrql-new-relics-query-language.mdx index deb33b4154a..5d225ecbb63 100644 --- a/src/content/docs/nrql/get-started/introduction-nrql-new-relics-query-language.mdx +++ b/src/content/docs/nrql/get-started/introduction-nrql-new-relics-query-language.mdx @@ -279,7 +279,7 @@ Here are the rules that NRQL follows: NRQL uses single quotes to designate strings. For example: ```sql - ... where traceId = '030a573f0df02c57' + ... WHERE traceId = '030a573f0df02c57' ``` diff --git a/src/content/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-11-1.mdx b/src/content/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-11-1.mdx new file mode 100644 index 00000000000..2b729d00bd6 --- /dev/null +++ b/src/content/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-11-1.mdx @@ -0,0 +1,34 @@ +--- +subject: Node.js agent +releaseDate: '2025-01-16' +version: 12.11.1 +downloadLink: 'https://www.npmjs.com/package/newrelic' +security: [] +bugs: ["Updated undici instrumentation to fix crash with trying to calculate exclusive duration on a segment that no longer exists"] +features: [] +--- + +## Notes + +#### Bug fixes + +* Updated undici instrumentation to fix crash with trying to calculate exclusive duration on a segment that no longer exists ([#2884](https://github.com/newrelic/node-newrelic/pull/2884)) ([3b7e4bf](https://github.com/newrelic/node-newrelic/commit/3b7e4bf0a40b21f16b11e7761809cbaa83c02515)) + +#### Documentation + +* Updated compatibility report ([#2878](https://github.com/newrelic/node-newrelic/pull/2878)) ([e784f84](https://github.com/newrelic/node-newrelic/commit/e784f8427bd49852f0ed7a15d6025ea8dfc73c72)) + +#### Miscellaneous chores + +* Fixed dns integration tests ([#2883](https://github.com/newrelic/node-newrelic/pull/2883)) ([dd30ad7](https://github.com/newrelic/node-newrelic/commit/dd30ad71f07233682da39ca41f452a55c6798a15)) + +#### Tests + +* Restored the branch to test apollo-server-plugin to main ([#2879](https://github.com/newrelic/node-newrelic/pull/2879)) ([978faab](https://github.com/newrelic/node-newrelic/commit/978faab59f5378e26cb8f5e584a3c9e684e7bbb1)) + + +### 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/release-notes/agent-release-notes/php-release-notes/php-agent-11-5-0-18.mdx b/src/content/docs/release-notes/agent-release-notes/php-release-notes/php-agent-11-5-0-18.mdx new file mode 100644 index 00000000000..ed6356478f8 --- /dev/null +++ b/src/content/docs/release-notes/agent-release-notes/php-release-notes/php-agent-11-5-0-18.mdx @@ -0,0 +1,41 @@ +--- +subject: PHP agent +releaseDate: '2025-01-13' +version: 11.5.0.18 +downloadLink: 'https://download.newrelic.com/php_agent/archive/11.5.0.18' +features: ['Adds support for PHP 8.4'] +bugs: ['Fix Drupal error and exception handling', 'externalCallCount should be added to transaction', 'Address aws-sdk-php versioning change'] +security: ['Daemon golang.org/x/net module upgraded to v0.33.0'] +--- + +## New Relic PHP agent v11.5.0.18 + +### New feature + +* Adds support for PHP 8.4 + +### Bug Fixes + +* Fix Drupal error and exception handling + * This fix may conflict with the error and exception handling of the Drupal [new_relic_rpm](https://www.drupal.org/project/new_relic_rpm) module. If you have this module installed and you aren't seeing your errors reported natively by the agent, try disabling the new_relic_rpm module. If you still experience issues after disabling this module, please reach out to New Relic Support. +* Fix error where externalCallCount should be added to the transaction and not just the error event. +* Address aws-sdk-php versioning change. + +### Security + +* Daemon golang.org/x/net module upgraded to v0.33.0 + +### Support statement + +* New Relic recommends that you upgrade the agent regularly and at a minimum every three months. For more information on supported agent versions and EOL timelines, check out our [New Relic PHP Agent EOL policy](https://docs.newrelic.com/docs/apm/agents/php-agent/getting-started/php-agent-eol-policy/). +* The [PHP agent compatibility and requirements](https://docs.newrelic.com/docs/apm/agents/php-agent/getting-started/php-agent-compatibility-requirements/) page should be consulted for the latest information on supported PHP versions and platforms. + + + **For installations using an unsupported PHP version or platform, it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages.** This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and the removal of support for the required, unsupported features. This would disrupt APM data collection. + + The PHP agent packages that are affected are: + + * newrelic-php5 + * newrelic-php5-common + * newrelic-daemon + diff --git a/src/content/docs/release-notes/index.mdx b/src/content/docs/release-notes/index.mdx index 823c56b76e6..81c027eebe5 100644 --- a/src/content/docs/release-notes/index.mdx +++ b/src/content/docs/release-notes/index.mdx @@ -184,5 +184,10 @@ To take full advantage of New Relic's latest features, enhancements, and importa icon="logo-newrelic" to="/docs/release-notes/fluentbit-release-notes" /> + diff --git a/src/content/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-32-4.mdx b/src/content/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-32-4.mdx new file mode 100644 index 00000000000..6128e85f914 --- /dev/null +++ b/src/content/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-32-4.mdx @@ -0,0 +1,11 @@ +--- +subject: Kubernetes integration +releaseDate: '2025-01-15' +version: 3.32.4 +--- + +For a detailed description of changes, see the [release notes](https://github.com/newrelic/nri-kubernetes/releases/tag/v3.32.4). + +This integration is included in the following chart versions: +* [newrelic-infrastructure-3.37.4](https://github.com/newrelic/nri-kubernetes/releases/tag/newrelic-infrastructure-3.37.4) +* [nri-bundle-5.0.106](https://github.com/newrelic/helm-charts/releases/tag/nri-bundle-5.0.106) diff --git a/src/content/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5272.mdx b/src/content/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5272.mdx new file mode 100644 index 00000000000..a851a88e157 --- /dev/null +++ b/src/content/docs/release-notes/mobile-apps-release-notes/new-relic-android-release-notes/new-relic-android-5272.mdx @@ -0,0 +1,14 @@ +--- +subject: Mobile app for Android +releaseDate: '2025-01-13' +version: 5.27.2 +downloadLink: 'https://play.google.com/store/apps/details?id=com.newrelic.rpm' +--- + + +### Enhancements +* Added events for enhanced app performance + +### Fixes +* Bug fixes +* Note: This is a Hotfix Release diff --git a/src/content/docs/release-notes/nrdot-release-notes/index.mdx b/src/content/docs/release-notes/nrdot-release-notes/index.mdx new file mode 100644 index 00000000000..99551ed0376 --- /dev/null +++ b/src/content/docs/release-notes/nrdot-release-notes/index.mdx @@ -0,0 +1,3 @@ +--- +subject: NRDOT +--- diff --git a/src/content/docs/release-notes/nrdot-release-notes/nrdot-24-10-25.mdx b/src/content/docs/release-notes/nrdot-release-notes/nrdot-24-10-25.mdx new file mode 100644 index 00000000000..ba0780becf7 --- /dev/null +++ b/src/content/docs/release-notes/nrdot-release-notes/nrdot-24-10-25.mdx @@ -0,0 +1,13 @@ +--- +subject: NRDOT +releaseDate: '2024-10-25' +version: 0.8.5 +metaDescription: Release notes for NRDOT version 0.8.5 +--- + +## Changes + +For a detailed description of changes, see [full release notes](https://github.com/newrelic/opentelemetry-collector-releases/releases/tag/nr-otel-collector-0.8.5) + +### Fixes +- force `docker@27.3.1` to fix [CVE-2024-41110](https://github.com/advisories/GHSA-v23v-6jw2-98fq) diff --git a/src/content/docs/security/security-privacy/compliance/certificates-standards-regulations/DORA Data Locations.mdx b/src/content/docs/security/security-privacy/compliance/certificates-standards-regulations/DORA Data Locations.mdx new file mode 100644 index 00000000000..50cf1f0387d --- /dev/null +++ b/src/content/docs/security/security-privacy/compliance/certificates-standards-regulations/DORA Data Locations.mdx @@ -0,0 +1,162 @@ +--- +title: Digital Operations Resilience Act (DORA) Locations of Processing +tags: + - Security + - Security and Privacy + - Compliance + - DORA Locations of Processing +metaDescription: Breakdown of locations of processing for DORA purposes. +freshnessValidatedDate: never +--- + +## Processing locations [#DORA_processing] + +New Relic processes data in the following locations*: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ North America + + South America + + EMEA + + APAC +
+ Canada + + Argentina + + European Union Member States + + Australia +
+ United States + + Brazil + + Israel + + India +
+ + + United Kingdom + + India +
+ + + + Japan +
+ + + + New Zealand +
+ + + + Philippines +
+ + + + Singapore +
+ + + + South Korea +
+ +*Note that this also encompasses the locations from which the regulated services are provided. + +## Data storage [#DORA_storage] + +New Relic stores data in the following regions**: + + + + + + + + + + + + + +
+ North America + + EMEA +
+ United States + + European Union +
+ +**New Relic’s global data hosting structure consists of two regions. You can select your preferred hosting region when setting up their account. + +For more information please see [Choose Your Data Center](/docs/accounts/accounts-billing/account-setup/choose-your-data-center/). diff --git a/src/content/eol/2025/01/deprecation-notice-rest-api-keys.md b/src/content/eol/2025/01/deprecation-notice-rest-api-keys.md deleted file mode 100644 index a18b9c739aa..00000000000 --- a/src/content/eol/2025/01/deprecation-notice-rest-api-keys.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: 'End of life for REST API Keys' -summary: "On March 1, 2025, REST API Keys End-of-life." -publishDate: '2025-01-16' -eolEffectiveDate: '2025-03-01' ---- - -Effective March 01, 2025, our REST API v2 will no longer accept REST API Keys. - -## Background [#bg] - -REST API keys are account-level keys and are not directly linked to an individual user, which limits auditing capabilities. This poses a security risk for both New Relic and our customers. User API keys are a well-tested alternative and serve as a replacement to REST API keys. These newer keys can be used across New Relic features such as NerdGraph, among others. - -## What's happening [#whats-happening] - -* Customers using deprecated REST API keys will be impacted by this end-of-life. -* If you have integrations or custom scripts which make calls to **(api.newrelic.com/v2 or api.eu.newrelic.com/v2)** you must check your API keys. -* If your API key starts with `NRAK`, no update is required. - -## What do you need to do [#what-to-do] - -* Generate a new User API key and configure your systems to use it. -* If you use a third-party integration, follow the instructions provided by the vendor to update the key. - -## What happens if you don't make any changes to your account [#account] - -* Failure to update the key will cause API calls to fail against the REST v2 API. -* The impact on your operations depends on which REST v2 API endpoints you use and your reliance on them. \ No newline at end of file diff --git a/src/content/whats-new/2025/01/whats-new-01-13-otelmetrics.md b/src/content/whats-new/2025/01/whats-new-01-13-otelmetrics.md new file mode 100644 index 00000000000..4d9157f813d --- /dev/null +++ b/src/content/whats-new/2025/01/whats-new-01-13-otelmetrics.md @@ -0,0 +1,20 @@ +--- +title: 'Enhanced APM golden metrics accuracy for services instrumented with OpenTelemetry' +summary: 'APM golden metrics are now calculated directly from OpenTelemetry metrics' +releaseDate: '2025-01-13' +learnMoreLink: 'https://docs.newrelic.com/docs/opentelemetry/get-started/apm-monitoring/opentelemetry-apm-ui/#golden-metrics' +getStartedLink: '' +--- + +Starting today, we're improving the accuracy of APM golden metrics for services instrumented with OpenTelemetry. "Golden metrics" or "golden signals" refer to high-value metrics such as latency, error rate, and throughput, which are visible in the entity explorer, workloads activity page, and change tracking details page. Previously, these metrics were derived from sampled span data. Now that OpenTelemetry metrics have matured, we are calculating them using unsampled metrics data, providing a more precise and comprehensive view of your service's performance. **To maintain visibility of golden metrics for your OpenTelemetry services, please ensure you are reporting both traces and metrics.** + +**Key Benefits:** +* **Improved accuracy:** If you're already reporting metrics for your OpenTelemetry-instrumented services, you will now receive more accurate and reliable data for latency, error rate, and throughput. This enhancement will be reflected in key areas such as the **Entity Explorer**, **Workloads Activity** page, and **Change Tracking Details** page. + +* **Faster troubleshooting:** With more accurate metrics, you can gain a clearer understanding of your application's performance. This precision allows you to pinpoint issues faster, identify root causes more efficiently, and resolve them swiftly. Detailed and accurate metrics help you trace anomalies to their sources, enabling quicker fixes and reducing downtime. + +**Next Steps:** + +* **Review instrumentation:** If you're using OpenTelemetry, verify that you are reporting both traces and metrics for your services. + +* ![OTelmetrics image](/images/otelmetrics.webp "OTel metrics screenshot") diff --git a/src/content/whats-new/2025/01/whats-new-01-16-azureserverless.md b/src/content/whats-new/2025/01/whats-new-01-16-azureserverless.md new file mode 100644 index 00000000000..f6447db79e0 --- /dev/null +++ b/src/content/whats-new/2025/01/whats-new-01-16-azureserverless.md @@ -0,0 +1,17 @@ +--- +title: 'Gain comprehensive visibility into your azure serverless functions' +summary: 'Troubleshoot faster and optimize resource utilization with deep insights into performance of Azure serverless functions' +releaseDate: '2024-01-16' +learnMoreLink: 'https://newrelic.com/blog/how-to-relic/new-relic-serverless-monitoring-for-azure-functions' +getStartedLink: 'https://docs.newrelic.com/docs/serverless-function-monitoring/overview/' +--- + +New Relic now offers comprehensive serverless monitoring for Azure Functions, including **exclusive support for both dedicated and consumption hosting plans**. Get a unified view of all your functions, regardless of deployment method, and gain deep insights into their performance and behavior. Troubleshoot issues faster and optimize resource utilization with: + +* **Deeper invocations insights:** Gain granular visibility into every function invocation (transaction), including detailed information on execution time, resource consumption, and success/failure rates. +* **Distributed tracing for HTTP:** Trace the flow of HTTP requests across your entire serverless application, identifying performance bottlenecks and quickly diagnosing issues within complex distributed systems. +* **Cross-platform support:** Our enhancements support .NET function apps hosted on both Windows and Linux, providing consistent visibility and troubleshooting capabilities across your diverse environments. +* **Containerized function support:** Gain deep insights into the behavior of your Azure Functions deployed as containers, even when running within Kubernetes environments. +* **Comprehensive metrics:** Access a rich set of metrics related to compute, garbage collection, and HTTP status codes, empowering you to proactively identify and address performance issues. + +![Azure serverless image](../../../../../static/images/azureserverless.webp "Azure serverless") diff --git a/src/content/whats-new/2025/01/whats-new-03-01-rest-api-keys-eol.md b/src/content/whats-new/2025/01/whats-new-03-01-rest-api-keys-eol.md deleted file mode 100644 index 75c82eaa00f..00000000000 --- a/src/content/whats-new/2025/01/whats-new-03-01-rest-api-keys-eol.md +++ /dev/null @@ -1,51 +0,0 @@ ---- -title: "REST API Keys End-of-life" -summary: "Retiring the REST API key to improve security and reliability." -releaseDate: "2025-03-01" -learnMoreLink: "https://docs.newrelic.com/docs/apis/intro-apis/new-relic-api-keys/" ---- - -New Relic is now retiring the REST API keys to improve security and reliability. You must update your systems with the new User keys to avoid service disruptions. - -The current REST API keys used to access REST API v2 **(api.newrelic.com/v2 or api.eu.newrelic.com/v2)** will be retired. This change addresses the limitations of the existing account-level keys and aligns with industry best practices. - -If your systems or integrations call these specified API end-points using the REST API keys, you must replace them with new User API keys by **March 1, 2025**, to avoid service disruptions. Failure to update may result in API call failures and errors, also potentially disrupting workflows. - -You must complete replacement of the REST API keys by March 1, 2025. - -## To get started - -This change requires you to [rotate your API key](https://docs.newrelic.com/docs/apis/intro-apis/new-relic-api-keys/#rotate-user-key). - -You must do the following: - -* **Generate new keys:** Use the [New Relic UI](https://docs.newrelic.com/docs/apis/intro-apis/new-relic-api-keys/) or [NerdGraph API.](https://docs.newrelic.com/docs/apis/nerdgraph/examples/use-nerdgraph-manage-license-keys-user-keys/) -* **Update systems:** Replace old keys with new User API keys in your systems. -* **Validate:** Ensure all API integrations work with the new User keys. -* **Remove old keys:** Delete old keys once validated. - -## Rotate API key - -**To rotate API keys in UI:** - -1. Go to [New Relic UI](https://docs.newrelic.com/docs/apis/intro-apis/new-relic-api-keys/) and determine which account you need a key for. -2. Create new User API keys associated to that account. -3. Update your systems to use the new User API keys. - - Go to [one.newrelic.com/api-keys](http://one.newrelic.com/api-keys) or [one.eu.newrelic.com/api-keys](http://one.eu.newrelic.com/api-keys) for EU data center and refer to the create and update instructions [here](https://docs.newrelic.com/docs/apis/intro-apis/new-relic-api-keys/#rotate-user-key). - -4. Ensure your API integrations function/work correctly with the new keys. This requires updating any scripts or code that reference the old key to use the new key value. -5. Once validated, remove the old REST API keys. After the old key is deleted, it cannot be restored. - -You can also manage User keys via our NerdGraph API. For instructions, refer to NerdGraph tutorial [Manage API keys.](https://docs.newrelic.com/docs/apis/nerdgraph/examples/use-nerdgraph-manage-license-keys-user-keys/) - -## Additional key points - -* If you’re using multiple New Relic accounts, each one will have its own REST API key. Each REST API key must be replaced individually with a User API key which is generated in the corresponding account. -* If your API key starts with `NRAK`, no update is required. - -## Contact support - -Our support team is here to assist you during this transition. If you have any questions about these changes, please contact [Support.](https://docs.newrelic.com/docs/new-relic-solutions/solve-common-issues/find-help-get-support/) - -For more information on how to view and manage API Keys in New Relic, click [here.](https://docs.newrelic.com/docs/apis/intro-apis/new-relic-api-keys/#keys-ui) diff --git a/src/data/whats-new-ids.json b/src/data/whats-new-ids.json index 1e5f7026121..8f51c1b7c93 100644 --- a/src/data/whats-new-ids.json +++ b/src/data/whats-new-ids.json @@ -354,5 +354,8 @@ "/whats-new/2024/11/whats-new-11-12-browser-apm-summary": "43011", "/whats-new/2024/12/whats-new-12-03-fossa": "43012", "/whats-new/2024/11/whats-new-11-20-k8s-apm-auto-attach": "43013", - "/whats-new/2024/12/whats-new-12-06-aws-logs": "43014" + "/whats-new/2024/12/whats-new-12-06-aws-logs": "43014", + "/whats-new/2025/01/whats-new-01-13-otelmetrics": "43015", + "/whats-new/2025/01/whats-new-01-16-azureserverless": "43016", + "/whats-new/2025/01/whats-new-03-01-rest-api-keys-eol": "43017" } \ No newline at end of file diff --git a/src/i18n/content/es/docs/alerts/get-notified/notification-integrations.mdx b/src/i18n/content/es/docs/alerts/get-notified/notification-integrations.mdx index 86a9279b2b2..1864264e19d 100644 --- a/src/i18n/content/es/docs/alerts/get-notified/notification-integrations.mdx +++ b/src/i18n/content/es/docs/alerts/get-notified/notification-integrations.mdx @@ -616,7 +616,7 @@ Lea más sobre cada una de nuestras notificaciones específicas de integración. Para crear un destino de ServiceNow, siga estos pasos: - 1. [Descargue e instale la aplicación New Relic](https://store.servicenow.com/sn_appstore_store.do#!/store/application/d117597d1b9b9d9078faddf7b04bcba7/1.0.0?referer=%2Fstore%2Fsearch%3Flistingtype%3Dallintegrations%25253Bancillary_app%25253Bcertified_apps%25253Bcontent%25253Bindustry_solution%25253Boem%25253Butility%25253Btemplate%26q%3Dnew%2520relic&sl=sh) en la tienda ServiceNow. + 1. [Descargue e instale la aplicación New Relic](https://store.servicenow.com/sn_appstore_store.do#!/store/application/d117597d1b9b9d9078faddf7b04bcba7/1.1.1?referer=%2Fstore%2Fsearch%3Flistingtype%3Dallintegrations%25253Bancillary_app%25253Bcertified_apps%25253Bcontent%25253Bindustry_solution%25253Boem%25253Butility%25253Btemplate%26q%3Dnew%2520relic&sl=sh) en la tienda ServiceNow. 2. Cree un usuario dentro de ServiceNow. Asegúrese de habilitar la opción **Web service access only** y otorgar el rol `x_newre_core.inbound_api` al usuario creado. Copie y guarde la contraseña generada. 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 68157a72040..bda75deaf18 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 @@ -901,7 +901,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum - [Panel](/docs/query-your-data/explore-query-data/dashboards/introduction-new-relic-one-dashboards) + [Dashboards](/docs/query-your-data/explore-query-data/dashboards/introduction-new-relic-one-dashboards) @@ -1825,8 +1825,8 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum - - Los lenguajes y tecnologías .NET enumerados son compatibles con nuestro panel [de observabilidad instantánea](https://newrelic.com/instant-observability/) . Si utiliza alguno de estos lenguajes o tecnologías, puede ver sus datos en un dashboard de New Relic, listo para usar: + + Los lenguajes y tecnologías .NET enumerados son compatibles con nuestro dashboard [de observabilidad instantánea](https://newrelic.com/instant-observability/) . Si utiliza alguno de estos lenguajes o tecnologías, puede ver sus datos en un dashboard de New Relic, listo para usar: @@ -1848,7 +1848,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum @@ -1863,7 +1863,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum 1. Instale el agente New Relic APM .NET y el agente de infraestructura siguiendo los pasos de nuestra [instalación guiada](https://one.newrelic.com/marketplace?state=bf68ca4b-b7cc-3227-fcc3-3349f5aa92f6). 2. Instale la integración en el host de Microsoft Windows Perfmon/WMI para New Relic Infrastructure [siguiendo las instrucciones de nri-perfmon](https://github.com/newrelic/nri-perfmon#nri-perfmon---windows-perfmonwmi-on-host-integration-for-new-relic-infrastructure). 3. Si instaló Perfmon manualmente, [reinicie su agente de infraestructura](/docs/infrastructure/install-infrastructure-agent/manage-your-agent/start-stop-restart-infrastructure-agent). - 4. Vaya a nuestra página de inicio rápido de ADO.NET para [instalar el panel de ADO.NET](https://newrelic.com/instant-observability/ado-dotnet). + 4. Vaya a nuestra página de inicio rápido de ADO.NET para [instalar el dashboard de ADO.NET](https://newrelic.com/instant-observability/ado-dotnet). @@ -1948,7 +1948,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum diff --git a/src/i18n/content/es/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx b/src/i18n/content/es/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx index e5ce009e9bc..e0c3781e333 100644 --- a/src/i18n/content/es/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx +++ b/src/i18n/content/es/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx @@ -50,15 +50,15 @@ Consulta original: ```sql FROM PageAction SELECT count(*) AS 'views' -WHERE countryCode IN ({{countryCode}}) and appName = 'Test App' FACET countryCode +WHERE countryCode IN ({{countryCode}}) AND appName = 'Test App' FACET countryCode ``` Consulta con una variable excluida: ```sql - FROM PageAction - SELECT count(*) AS 'views' - WHERE true and appName = 'Test App' FACET countryCode +FROM PageAction +SELECT count(*) AS 'views' +WHERE true AND appName = 'Test App' FACET countryCode ``` Esta característica es particularmente útil cuando: @@ -71,7 +71,7 @@ Limitaciones en la variable de inclusión: * Cuando se emplea en casos FACET, la condición se reemplaza con verdadero y la convierte en una condición siempre verdadera. -* Cuando se emplea en otros contextos, como funciones o con la declaración SELECT, obtendrá el siguiente error: `"Unknown function Disable_variable()"`. Esto se debe a que la función de deshabilitar variable aún no está implementada para estos casos específicos. +* Cuando se emplea en otros contextos, como funciones o con la declaración `SELECT` , obtendrá el siguiente error: `"Unknown function Disable_variable()"`. Esto se debe a que la función de deshabilitar variable aún no está implementada para estos casos específicos. ## Requisitos y limitaciones [#requirements] @@ -87,7 +87,7 @@ Puntos importantes a tener en cuenta al agregar una consulta: * Para ayudarte cuando estás creando una consulta, hay un código de color: - * Las cláusulas `from`, `select`, `facet` y `where` están en rosa. + * Las cláusulas `FROM`, `SELECT`, `FACET` y `WHERE` están en rosa. * Identificador están en negro. * Las funciones están en azul. * Las cadenas están en verde. @@ -193,7 +193,7 @@ La creación de una variable de plantilla consta de dos pasos. @@ -288,7 +288,7 @@ La creación de una variable de plantilla consta de dos pasos. Tenga en cuenta que estas son las cláusulas NRQL que aceptarán variables de plantilla como valores: `SELECT`, `FROM`, `FACET`, `ORDER BY` y `WHERE`. - En cambio, la siguiente lista de cláusulas NRQL no aceptará variables de plantilla como argumentos: `AS`, `COMPARE WITH`, `LIMIT`, `OFFSET`, `SINCE`, `SLIDE BY`, `TIMESERIES`, `UNTIL` y `WITH...`. + En cambio, la siguiente lista de cláusulas NRQL no aceptará variables de plantilla como argumentos: `AS`, `COMPARE WITH`, `LIMIT`, `OFFSET`, `SINCE`, `SLIDE BY`, `TIMESERIES`, `UNTIL` y `WITH`.... 5. Hacer clic **Save** @@ -313,7 +313,7 @@ Puede emplear casi cualquier consulta NRQL siempre que devuelva una lista de val Con [`uniques`](/docs/nrql/nrql-syntax-clauses-functions/#func-uniques): ```sql - From PageAction select uniques(countryCode) +FROM PageAction SELECT uniques(countryCode) ``` ```sql @@ -324,8 +324,8 @@ Con [`uniques`](/docs/nrql/nrql-syntax-clauses-functions/#func-uniques): Con [`keyset`](/docs/nrql/nrql-syntax-clauses-functions/#keyset): ```sql - -- with `keyset`, you'll get a list with all of the attributes from the table you're querying from - From PageAction select keyset() SINCE 1 day ago +-- with `keyset`, you'll get a list with all of the attributes from the table you're querying from +FROM PageAction SELECT keyset() SINCE 1 day ago ``` Tenga en cuenta que no se admiten variables anidadas ya que no puede haber variables dentro de variables. @@ -361,7 +361,8 @@ A continuación se muestran algunos tipos diferentes de implementaciones de vari A continuación se muestra un ejemplo de una consulta que utiliza dos variables de plantilla. Tenga en cuenta que esto supone que las variables de plantilla `countryCode` y `city` ya se habrán creado y que tienen un valor único. ```sql - SELECT countryCode, city FROM PageAction WHERE countryCode = {{countryCode}} and city = {{city}} + SELECT countryCode, city FROM PageAction + WHERE countryCode = {{countryCode}} AND city = {{city}} ``` Creating a widget using multiple variables @@ -369,21 +370,22 @@ A continuación se muestran algunos tipos diferentes de implementaciones de vari Si tiene varios valores para sus variables, como `Chicago`, `New York`, `Paris` para su variable `city` , debe usar `IN`: ```sql - SELECT countryCode, city FROM PageAction WHERE countryCode IN ({{countryCode}}) and city IN ({{city}}) + SELECT countryCode, city FROM PageAction + WHERE countryCode IN ({{countryCode}}) AND city IN ({{city}}) ``` Usando variables y [expresiones regulares](/docs/query-your-data/nrql-new-relic-query-language/get-started/nrql-syntax-clauses-functions/#func-capture), puede crear un filtro, siempre que esté seguro de que una parte del filtro es fija. - Debe utilizar esta coincidencia parcial si desea utilizar `like`. + Debe utilizar esta coincidencia parcial si desea utilizar `LIKE`. Supongamos que desea filtrar por versión de lanzamiento. La consulta devuelve algo como: `release-1234`. Puede crear una variable usando [`aparse`](/docs/query-your-data/nrql-new-relic-query-language/get-started/nrql-syntax-clauses-functions/#func-aparse) para analizar el número de versión: ```sql - SELECT uniques(aparse(platformVersion , 'release-*')) FROM PageView + SELECT uniques(aparse(platformVersion, 'release-*')) FROM PageView ``` Creating the release version variable @@ -391,7 +393,8 @@ A continuación se muestran algunos tipos diferentes de implementaciones de vari Luego cree un widget con la siguiente consulta: ```sql - SELECT count(*) FROM PageAction WHERE aparse(platformVersion, 'release-*') IN ({{releaseversion}}) facet platformVersion + SELECT count(*) FROM PageAction + WHERE aparse(platformVersion, 'release-*') IN ({{releaseversion}}) FACET platformVersion ``` Creating the widget @@ -399,7 +402,8 @@ A continuación se muestran algunos tipos diferentes de implementaciones de vari O si lo prefieres, puedes usar el comando [`capture`](/docs/query-your-data/nrql-new-relic-query-language/get-started/nrql-syntax-clauses-functions/#func-capture) : ```sql - SELECT count(*) FROM PageAction WHERE capture(platformVersion, r'release-(?P\d+)') IN ({{releaseversion}}) Facet platformVersion + SELECT count(*) FROM PageAction + WHERE capture(platformVersion, r'release-(?P\d+)') IN ({{releaseversion}}) FACET platformVersion ``` Creating the widget @@ -434,7 +438,7 @@ A continuación se muestran algunos tipos diferentes de implementaciones de vari con una consulta NRQL } > - Puede crear una variable de tipo NRQL con un formato de salida de cadena y usarla después de una cláusula `facet` para agrupar por diferentes valores. + Puede crear una variable de tipo NRQL con un formato de salida de cadena y usarla después de una cláusula `FACET` para agrupar por diferentes valores. Por ejemplo, podrías crear una variable denominada `{{userAgentName}}` que tendría este aspecto: @@ -447,7 +451,8 @@ A continuación se muestran algunos tipos diferentes de implementaciones de vari Luego crearías un widget con la siguiente consulta: ```sql - SELECT count(*) FROM PageAction WHERE userAgentName={{userAgentName}} FACET userAgentName + SELECT count(*) FROM PageAction + WHERE userAgentName={{userAgentName}} FACET userAgentName ``` Creating widget using facet @@ -496,7 +501,7 @@ A continuación se muestran algunos tipos diferentes de implementaciones de vari - De forma predeterminada, la opción "ignorar el selector de tiempo" está habilitada, lo que significa que la consulta siempre se ejecuta utilizando el valor de rango de tiempo predeterminado 1 `HOUR`, incluso si el selector de tiempo en el dashboard tiene un valor diferente seleccionado (por ejemplo, 5 minutos, 3 horas, etc.). La excepción para ese caso es cuando la consulta tiene un rango de tiempo explícito establecido con una cláusula `SINCE` , como por ejemplo: + De forma predeterminada, la opción “ignorar selector de tiempo” está habilitada, lo que significa que la consulta siempre se ejecuta empleando el valor de rango de tiempo predeterminado `1 hour`, incluso si el selector de tiempo en el dashboard tiene un valor diferente seleccionado (por ejemplo, `5 minutes`, `3 hours`, etc.). La excepción para ese caso es cuando la consulta tiene un rango de tiempo explícito establecido con una cláusula `SINCE` , como por ejemplo: ```sql SELECT uniques(eventId) @@ -506,7 +511,7 @@ A continuación se muestran algunos tipos diferentes de implementaciones de vari Los resultados estarán en el rango de los últimos 5 minutos. - Cuando la opción “ignorar selector de tiempo” está desactivada, la consulta se ejecutará con el valor seleccionado en el selector de tiempo. Por ejemplo, si configura el selector de tiempo en 30 minutos, como en la captura de pantalla siguiente, en el formulario para editar las variables, el campo "ignorar selector de tiempo" se desactivará. + Cuando la opción "ignorar selector de tiempo" está desactivada, la consulta se ejecutará con el valor seleccionado en el selector de tiempo. Por ejemplo, si configura el selector de tiempo en 30 minutos, como en la captura de pantalla a continuación, en el formulario para editar las variables, el campo "ignorar selector de tiempo" se desactivará. A screenshot showing the time picker diff --git a/src/i18n/content/jp/docs/alerts/get-notified/notification-integrations.mdx b/src/i18n/content/jp/docs/alerts/get-notified/notification-integrations.mdx index a5c5852f96a..5a7187d1882 100644 --- a/src/i18n/content/jp/docs/alerts/get-notified/notification-integrations.mdx +++ b/src/i18n/content/jp/docs/alerts/get-notified/notification-integrations.mdx @@ -616,7 +616,7 @@ translationType: machine ServiceNow 宛先を作成するには、次の手順に従います。 - 1. ServiceNow ストアで[New Relic アプリケーションをダウンロードしてインストールします](https://store.servicenow.com/sn_appstore_store.do#!/store/application/d117597d1b9b9d9078faddf7b04bcba7/1.0.0?referer=%2Fstore%2Fsearch%3Flistingtype%3Dallintegrations%25253Bancillary_app%25253Bcertified_apps%25253Bcontent%25253Bindustry_solution%25253Boem%25253Butility%25253Btemplate%26q%3Dnew%2520relic&sl=sh)。 + 1. ServiceNow ストアで[New Relic アプリケーションをダウンロードしてインストールします](https://store.servicenow.com/sn_appstore_store.do#!/store/application/d117597d1b9b9d9078faddf7b04bcba7/1.1.1?referer=%2Fstore%2Fsearch%3Flistingtype%3Dallintegrations%25253Bancillary_app%25253Bcertified_apps%25253Bcontent%25253Bindustry_solution%25253Boem%25253Butility%25253Btemplate%26q%3Dnew%2520relic&sl=sh)。 2. ServiceNow 内でユーザーを作成します。 必ず**Web service access only**オプションを有効にし、作成したユーザーに`x_newre_core.inbound_api`ロールを付与してください。 生成されたパスワードをコピーして保存します。 diff --git a/src/i18n/content/jp/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx b/src/i18n/content/jp/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx index 6f6ff738738..a577c04952b 100644 --- a/src/i18n/content/jp/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx +++ b/src/i18n/content/jp/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx @@ -50,15 +50,15 @@ translationType: machine ```sql FROM PageAction SELECT count(*) AS 'views' -WHERE countryCode IN ({{countryCode}}) and appName = 'Test App' FACET countryCode +WHERE countryCode IN ({{countryCode}}) AND appName = 'Test App' FACET countryCode ``` 除外変数を使用したクエリ: ```sql - FROM PageAction - SELECT count(*) AS 'views' - WHERE true and appName = 'Test App' FACET countryCode +FROM PageAction +SELECT count(*) AS 'views' +WHERE true AND appName = 'Test App' FACET countryCode ``` この機能は、特に次の場合に便利です。 @@ -71,7 +71,7 @@ include 変数の制限: * FACET の場合に使用すると、条件は true に置き換えられ、常に true の条件に変換されます。 -* 関数などの他のコンテキストや SELECT ステートメントで使用すると、次のエラーが発生します: `"Unknown function Disable_variable()"` 。 これは、これらの特定のケースに対して変数を無効にする機能がまだ実装されていないためです。 +* 関数などの他のコンテキストや`SELECT`ステートメントで使用すると、次のエラーが発生します: `"Unknown function Disable_variable()"` 。 これは、これらの特定のケースに対して変数を無効にする機能がまだ実装されていないためです。 ## 要件と制限 [#requirements] @@ -87,7 +87,7 @@ include 変数の制限: * クエリを作成するときに役立つように、次のカラー コードがあります。 - * 句 `from`、 `select`、 `facet`、および `where`はピンク色です。 + * 句 `FROM`、 `SELECT`、 `FACET`、および `WHERE`はピンク色です。 * 識別子は黒です。 * 関数は青色です。 * 弦は緑色です。 @@ -193,7 +193,7 @@ include 変数の制限: @@ -288,7 +288,7 @@ include 変数の制限: これらは、テンプレート変数を値として受け入れる NRQL 句であることに注意してください: `SELECT` 、 `FROM` 、 `FACET` 、 `ORDER BY` 、および`WHERE` 。 - 代わりに、次の NRQL 句のリストはテンプレート変数を引数として受け入れません: `AS` 、 `COMPARE WITH` 、 `LIMIT` 、 `OFFSET` 、 `SINCE` 、 `SLIDE BY` 、 `TIMESERIES` 、 `UNTIL`および`WITH...` . + 代わりに、次の NRQL 句のリストは、テンプレート変数を引数として受け入れません: `AS` 、 `COMPARE WITH` 、 `LIMIT` 、 `OFFSET` `WITH` `SINCE` 、`SLIDE BY`、 、 `TIMESERIES` 、 `UNTIL` ...。 5. クリック **Save** @@ -313,7 +313,7 @@ include 変数の制限: [`uniques`](/docs/nrql/nrql-syntax-clauses-functions/#func-uniques)の場合: ```sql - From PageAction select uniques(countryCode) +FROM PageAction SELECT uniques(countryCode) ``` ```sql @@ -324,8 +324,8 @@ include 変数の制限: [`keyset`](/docs/nrql/nrql-syntax-clauses-functions/#keyset)の場合: ```sql - -- with `keyset`, you'll get a list with all of the attributes from the table you're querying from - From PageAction select keyset() SINCE 1 day ago +-- with `keyset`, you'll get a list with all of the attributes from the table you're querying from +FROM PageAction SELECT keyset() SINCE 1 day ago ``` 変数内に変数が存在することはできないため、ネストされた変数はサポートされていないことに注意してください。 @@ -361,7 +361,8 @@ include 変数の制限: 次に、2 つのテンプレート変数を使用するクエリの例を示します。これは、 `countryCode` および `city` テンプレート変数がすでに作成されており、それらの値が 1 つであることを前提としていることに注意してください。 ```sql - SELECT countryCode, city FROM PageAction WHERE countryCode = {{countryCode}} and city = {{city}} + SELECT countryCode, city FROM PageAction + WHERE countryCode = {{countryCode}} AND city = {{city}} ``` Creating a widget using multiple variables @@ -369,21 +370,22 @@ include 変数の制限: `city` 変数の `Chicago` 、 `New York` 、 `Paris` など、変数に複数の値がある場合は、 `IN`を使用する必要があります。 ```sql - SELECT countryCode, city FROM PageAction WHERE countryCode IN ({{countryCode}}) and city IN ({{city}}) + SELECT countryCode, city FROM PageAction + WHERE countryCode IN ({{countryCode}}) AND city IN ({{city}}) ``` 変数と[regex](/docs/query-your-data/nrql-new-relic-query-language/get-started/nrql-syntax-clauses-functions/#func-capture)を使用して、フィルターの一部が修正されていることが確実であれば、フィルターを作成できます。 - `like`を使用する場合は、この部分一致を使用する必要があります。 + `LIKE`を使用する場合は、この部分一致を使用する必要があります。 リリース バージョンでフィルター処理するとします。クエリは`release-1234`のようなものを返します。 [`aparse`](/docs/query-your-data/nrql-new-relic-query-language/get-started/nrql-syntax-clauses-functions/#func-aparse)を使用して変数を作成し、バージョン番号を解析できます。 ```sql - SELECT uniques(aparse(platformVersion , 'release-*')) FROM PageView + SELECT uniques(aparse(platformVersion, 'release-*')) FROM PageView ``` Creating the release version variable @@ -391,7 +393,8 @@ include 変数の制限: 次に、次のクエリでウィジェットを作成します。 ```sql - SELECT count(*) FROM PageAction WHERE aparse(platformVersion, 'release-*') IN ({{releaseversion}}) facet platformVersion + SELECT count(*) FROM PageAction + WHERE aparse(platformVersion, 'release-*') IN ({{releaseversion}}) FACET platformVersion ``` Creating the widget @@ -399,7 +402,8 @@ include 変数の制限: または、 [`capture`](/docs/query-your-data/nrql-new-relic-query-language/get-started/nrql-syntax-clauses-functions/#func-capture) コマンドを使用することもできます。 ```sql - SELECT count(*) FROM PageAction WHERE capture(platformVersion, r'release-(?P\d+)') IN ({{releaseversion}}) Facet platformVersion + SELECT count(*) FROM PageAction + WHERE capture(platformVersion, r'release-(?P\d+)') IN ({{releaseversion}}) FACET platformVersion ``` Creating the widget @@ -434,7 +438,7 @@ include 変数の制限: を使用します } > - 文字列出力形式で NRQL 型の変数を作成し、それを `facet` 句の後に使用して、異なる値でグループ化できます。 + 文字列出力形式で NRQL 型の変数を作成し、それを `FACET` 句の後に使用して、異なる値でグループ化できます。 たとえば、次のような `{{userAgentName}}` という名前の変数を作成できます。 @@ -447,7 +451,8 @@ include 変数の制限: 次に、次のクエリを使用してウィジェットを作成します。 ```sql - SELECT count(*) FROM PageAction WHERE userAgentName={{userAgentName}} FACET userAgentName + SELECT count(*) FROM PageAction + WHERE userAgentName={{userAgentName}} FACET userAgentName ``` Creating widget using facet @@ -496,7 +501,7 @@ include 変数の制限: - デフォルトでは、「タイムピッカーを無視する」オプションが有効になっています。つまり、ダッシュボードのタイムピッカーに別の値が選択されている場合でも、クエリは常にデフォルトの 1 `HOUR`時間範囲値を使用して実行されます (例: 5 分、3)時間など）。 この場合の例外は、次のようなクエリに`SINCE`句を使用して明示的な時間範囲が設定されている場合です。 + デフォルトでは、「タイムピッカーを無視」オプションが有効になっています。つまり、ダッシュボードのタイムピッカーに別の値が選択されている場合でも、書き込みは常にデフォルトの`1 hour`時間範囲値を使用して実行されます。 `5 minutes` 、 `3 hours`など)。 この場合の例外は、クエリに`SINCE`句で明示的に時間範囲が設定されている場合です。次に例を示します。 ```sql SELECT uniques(eventId) @@ -506,7 +511,7 @@ include 変数の制限: 結果は過去 5 分間の範囲になります。 - 「タイムピッカーを無視」オプションがオフの場合、クエリはタイムピッカーで選択された値で実行されます。 たとえば、以下のスクリーンショットのようにタイムピッカーを 30 分に設定すると、変数編集フォームで「タイムピッカーを無視する」フィールドがオフに設定されます。 + 「タイムピッカーを無視する」オプションをオフにすると、タイムピッカーで選択した値で書き込みが実行されます。 たとえば、以下のスクリーンショットのように、変数編集フォームでタイムピッカーを 30 分に設定すると、「タイムピッカーを無視する」フィールドがオフに設定されます。 A screenshot showing the time picker diff --git a/src/i18n/content/kr/docs/alerts/get-notified/notification-integrations.mdx b/src/i18n/content/kr/docs/alerts/get-notified/notification-integrations.mdx index d8b7db236af..1ac65e37738 100644 --- a/src/i18n/content/kr/docs/alerts/get-notified/notification-integrations.mdx +++ b/src/i18n/content/kr/docs/alerts/get-notified/notification-integrations.mdx @@ -616,7 +616,7 @@ translationType: machine ServiceNow 대상을 생성하려면 다음 단계를 따르십시오. - 1. ServiceNow 스토어에서 [뉴킹릭 피규어를 다운로드하여 설치하세요](https://store.servicenow.com/sn_appstore_store.do#!/store/application/d117597d1b9b9d9078faddf7b04bcba7/1.0.0?referer=%2Fstore%2Fsearch%3Flistingtype%3Dallintegrations%25253Bancillary_app%25253Bcertified_apps%25253Bcontent%25253Bindustry_solution%25253Boem%25253Butility%25253Btemplate%26q%3Dnew%2520relic&sl=sh) . + 1. ServiceNow 스토어에서 [뉴킹릭 피규어를 다운로드하여 설치하세요](https://store.servicenow.com/sn_appstore_store.do#!/store/application/d117597d1b9b9d9078faddf7b04bcba7/1.1.1?referer=%2Fstore%2Fsearch%3Flistingtype%3Dallintegrations%25253Bancillary_app%25253Bcertified_apps%25253Bcontent%25253Bindustry_solution%25253Boem%25253Butility%25253Btemplate%26q%3Dnew%2520relic&sl=sh) . 2. ServiceNow 내부에서 사용자를 생성합니다. **Web service access only** 옵션을 활성화하고 생성된 사용자에게 `x_newre_core.inbound_api` 역할을 부여했는지 확인하세요. 생성된 비밀번호를 복사하여 저장하세요. diff --git a/src/i18n/content/kr/docs/apm/agents/net-agent/installation/update-net-agent.mdx b/src/i18n/content/kr/docs/apm/agents/net-agent/installation/update-net-agent.mdx index 32bfb153282..517d8c7c7b4 100644 --- a/src/i18n/content/kr/docs/apm/agents/net-agent/installation/update-net-agent.mdx +++ b/src/i18n/content/kr/docs/apm/agents/net-agent/installation/update-net-agent.mdx @@ -22,7 +22,6 @@ APM .NET 에이전트를 업데이트하는 방법. 다른 설치가 있는 경우 자세한 내용은 해당 설정에 대한 다음 설치 문서를 참조하십시오. -* [Azure 웹 앱](/docs/apm/agents/net-agent/azure-installation/install-net-agent-azure-web-apps/#site-extention-update) * 도커: [Windows용](/install/dotnet/?deployment=windowsInstall&docker=yesDocker) | [리눅스](/install/dotnet/?deployment=linux&docker=yesDocker)용 * [너겟](/docs/apm/agents/net-agent/install-guides/install-net-agent-using-nuget) @@ -60,7 +59,8 @@ APM .NET 에이전트를 업데이트하는 방법. 뉴렐릭 Azure 사이트 확장을 사용하여 Azure 웹앱용 .NET 에이전트를 업데이트하려면 설치 지침을 따르세요. - * 에이전트 파일을 최신 버전으로 업데이트하는 Azure 사이트 확장의 최신 버전을 설치합니다. + * 뉴렐릭 Azure 사이트 확장을 제거하면 에이전트가 제거됩니다. + * [이러한 설치 지침](/install/dotnet/?deployment=azure&azure=azuresiteextension) 에 따라 최신 버전의 Azure 사이트 확장 프로그램을 다시 설치하면 에이전트의 최신 버전이 설치됩니다. * 업데이트된 에이전트를 시작하려면 웹 앱을 다시 시작하십시오. diff --git a/src/i18n/content/kr/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx b/src/i18n/content/kr/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx index 673f201ff31..8d5331c08c9 100644 --- a/src/i18n/content/kr/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx +++ b/src/i18n/content/kr/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx @@ -50,15 +50,15 @@ translationType: machine ```sql FROM PageAction SELECT count(*) AS 'views' -WHERE countryCode IN ({{countryCode}}) and appName = 'Test App' FACET countryCode +WHERE countryCode IN ({{countryCode}}) AND appName = 'Test App' FACET countryCode ``` 제외된 변수가 있는 쿼리: ```sql - FROM PageAction - SELECT count(*) AS 'views' - WHERE true and appName = 'Test App' FACET countryCode +FROM PageAction +SELECT count(*) AS 'views' +WHERE true AND appName = 'Test App' FACET countryCode ``` 이 기능은 다음과 같은 경우에 특히 유용합니다. @@ -71,7 +71,7 @@ WHERE countryCode IN ({{countryCode}}) and appName = 'Test App' FACET countryCod * FACET 케이스에서 사용될 경우, 조건이 참으로 바뀌고 항상 참인 조건으로 변환됩니다. -* 함수나 SELECT 문 등 다른 컨텍스트에서 사용하는 경우 다음 오류가 발생합니다. `"Unknown function Disable_variable()"`. 이는 비활성화 변수 기능이 아직 이러한 특정한 경우에 구현되지 않았기 때문입니다. +* 함수나 `SELECT` 문 등 다른 맥락에서 사용하면 다음 오류가 발생합니다. `"Unknown function Disable_variable()"`. 이는 비활성화 변수 기능이 아직 이러한 특정한 경우에 구현되지 않았기 때문입니다. ## 요구 사항 및 제한 사항 [#requirements] @@ -87,7 +87,7 @@ WHERE countryCode IN ({{countryCode}}) and appName = 'Test App' FACET countryCod * 검색어를 만들 때 도움이 되도록 색상 코드가 있습니다. - * 절 `from`, `select`, `facet`및 `where`은 분홍색입니다. + * 절 `FROM`, `SELECT`, `FACET`및 `WHERE`은 분홍색입니다. * 식별자는 검은색입니다. * 기능은 파란색입니다. * 문자열은 녹색입니다. @@ -193,7 +193,7 @@ WHERE countryCode IN ({{countryCode}}) and appName = 'Test App' FACET countryCod @@ -288,7 +288,7 @@ WHERE countryCode IN ({{countryCode}}) and appName = 'Test App' FACET countryCod 이는 템플릿 변수를 값으로 허용하는 NRQL 절입니다: `SELECT`, `FROM`, `FACET`, `ORDER BY` 및 `WHERE`. - 대신 다음 NRQL 절 목록은 템플릿 변수를 인수로 허용하지 않습니다: `AS`, `COMPARE WITH`, `LIMIT`, `OFFSET`, `SINCE`, `SLIDE BY`, `TIMESERIES`, `UNTIL` 및 `WITH...`. + 대신, 다음 NRQL 절 목록은 템플릿 변수를 인수로 허용하지 않습니다: `AS`, `COMPARE WITH`, `LIMIT`, `OFFSET`, `SINCE`, `SLIDE BY`, `TIMESERIES`, `UNTIL` 및 `WITH`.... 5. 딸깍 하는 소리 **Save** @@ -313,7 +313,7 @@ WHERE countryCode IN ({{countryCode}}) and appName = 'Test App' FACET countryCod [`uniques`](/docs/nrql/nrql-syntax-clauses-functions/#func-uniques) 사용: ```sql - From PageAction select uniques(countryCode) +FROM PageAction SELECT uniques(countryCode) ``` ```sql @@ -324,8 +324,8 @@ WHERE countryCode IN ({{countryCode}}) and appName = 'Test App' FACET countryCod [`keyset`](/docs/nrql/nrql-syntax-clauses-functions/#keyset) 사용: ```sql - -- with `keyset`, you'll get a list with all of the attributes from the table you're querying from - From PageAction select keyset() SINCE 1 day ago +-- with `keyset`, you'll get a list with all of the attributes from the table you're querying from +FROM PageAction SELECT keyset() SINCE 1 day ago ``` 변수 내에 변수가 있을 수 없으므로 중첩 변수는 지원되지 않습니다. @@ -361,7 +361,8 @@ WHERE countryCode IN ({{countryCode}}) and appName = 'Test App' FACET countryCod 다음은 두 개의 템플릿 변수를 사용하는 쿼리의 예입니다. 이는 `countryCode` 및 `city` 템플릿 변수가 이미 생성되었으며 단일 값을 가지고 있다고 가정합니다. ```sql - SELECT countryCode, city FROM PageAction WHERE countryCode = {{countryCode}} and city = {{city}} + SELECT countryCode, city FROM PageAction + WHERE countryCode = {{countryCode}} AND city = {{city}} ``` Creating a widget using multiple variables @@ -369,21 +370,22 @@ WHERE countryCode IN ({{countryCode}}) and appName = 'Test App' FACET countryCod 변수에 여러 값이 있는 경우(예: `city` 변수에 대한 `Chicago`, `New York`, `Paris` , `IN` 사용해야 합니다. ```sql - SELECT countryCode, city FROM PageAction WHERE countryCode IN ({{countryCode}}) and city IN ({{city}}) + SELECT countryCode, city FROM PageAction + WHERE countryCode IN ({{countryCode}}) AND city IN ({{city}}) ``` 변수와 [regex를](/docs/query-your-data/nrql-new-relic-query-language/get-started/nrql-syntax-clauses-functions/#func-capture) 사용하여 필터의 일부가 고정된 것이 확실한 경우 필터를 만들 수 있습니다. - `like`사용하려면 이 부분 일치를 사용해야 합니다. + `LIKE`사용하려면 이 부분 일치를 사용해야 합니다. 릴리스 버전별로 필터링한다고 가정해 보겠습니다. 쿼리는 다음과 같은 것을 반환합니다. `release-1234` . [`aparse`](/docs/query-your-data/nrql-new-relic-query-language/get-started/nrql-syntax-clauses-functions/#func-aparse) 사용하여 변수를 생성하여 버전 번호를 구문 분석할 수 있습니다. ```sql - SELECT uniques(aparse(platformVersion , 'release-*')) FROM PageView + SELECT uniques(aparse(platformVersion, 'release-*')) FROM PageView ``` Creating the release version variable @@ -391,7 +393,8 @@ WHERE countryCode IN ({{countryCode}}) and appName = 'Test App' FACET countryCod 그런 다음 다음 쿼리를 사용하여 위젯을 만듭니다. ```sql - SELECT count(*) FROM PageAction WHERE aparse(platformVersion, 'release-*') IN ({{releaseversion}}) facet platformVersion + SELECT count(*) FROM PageAction + WHERE aparse(platformVersion, 'release-*') IN ({{releaseversion}}) FACET platformVersion ``` Creating the widget @@ -399,7 +402,8 @@ WHERE countryCode IN ({{countryCode}}) and appName = 'Test App' FACET countryCod 또는 원하는 경우 [`capture`](/docs/query-your-data/nrql-new-relic-query-language/get-started/nrql-syntax-clauses-functions/#func-capture) 명령을 사용할 수 있습니다. ```sql - SELECT count(*) FROM PageAction WHERE capture(platformVersion, r'release-(?P\d+)') IN ({{releaseversion}}) Facet platformVersion + SELECT count(*) FROM PageAction + WHERE capture(platformVersion, r'release-(?P\d+)') IN ({{releaseversion}}) FACET platformVersion ``` Creating the widget @@ -434,7 +438,7 @@ WHERE countryCode IN ({{countryCode}}) and appName = 'Test App' FACET countryCod 사용 } > - 문자열 출력 형식으로 NRQL 유형의 변수를 생성하고 `facet` 절 뒤에 사용하여 다른 값으로 그룹화할 수 있습니다. + 문자열 출력 형식으로 NRQL 유형의 변수를 생성하고 `FACET` 절 뒤에 사용하여 다른 값으로 그룹화할 수 있습니다. 예를 들어 다음과 같은 `{{userAgentName}}` 라는 변수를 만들 수 있습니다. @@ -447,7 +451,8 @@ WHERE countryCode IN ({{countryCode}}) and appName = 'Test App' FACET countryCod 그런 다음 다음 쿼리를 사용하여 위젯을 만듭니다. ```sql - SELECT count(*) FROM PageAction WHERE userAgentName={{userAgentName}} FACET userAgentName + SELECT count(*) FROM PageAction + WHERE userAgentName={{userAgentName}} FACET userAgentName ``` Creating widget using facet @@ -496,7 +501,7 @@ WHERE countryCode IN ({{countryCode}}) and appName = 'Test App' FACET countryCod - 기본적으로 "타임 피커 무시" 옵션이 활성화되어 있습니다. 즉, 대시보드의 타임 피커에 다른 값이 선택되어 있어도 쿼리는 항상 기본 1 `HOUR` 시간 범위 값을 사용하여 실행됩니다(예: 5분, 3분). 시간 등). 해당 경우의 예외는 쿼리에 `SINCE` 절을 사용하여 명시적인 시간 범위가 설정된 경우입니다. 예를 들면 다음과 같습니다. + 기본적으로 "타임 피커 무시" 옵션이 활성화되어 있어 대시보드의 타임 `1 hour` 에 다른 값이 선택된 경우에도(예: `5 minutes`, `3 hours`, 등). 이 경우의 예외는 쿼리에 `SINCE` 절로 설정된 명시적 시간 범위가 있는 경우입니다. 예를 들어 다음과 같습니다. ```sql SELECT uniques(eventId) @@ -506,7 +511,7 @@ WHERE countryCode IN ({{countryCode}}) and appName = 'Test App' FACET countryCod 결과는 지난 5분 동안의 범위에 있습니다. - 타임피커 무시 옵션을 끄면 타임피커에서 선택한 값으로 쿼리가 실행됩니다. 예를 들어, 아래 스크린샷처럼 변수 편집 폼에서 타임 피커를 30분으로 설정하면 '타임 피커 무시' 필드가 꺼짐으로 설정됩니다. + "타임 피커 무시" 옵션이 꺼지면 쿼리는 타임 피커에서 선택한 값으로 실행됩니다. 예를 들어, 아래 스크린샷과 같이 '라벨 피커'를 30분으로 설정하면, 변수 편집 폼에서 '라벨 피커 무시' 필드가 꺼짐으로 설정됩니다. A screenshot showing the time picker diff --git a/src/i18n/content/pt/docs/alerts/get-notified/notification-integrations.mdx b/src/i18n/content/pt/docs/alerts/get-notified/notification-integrations.mdx index 1e62b81ccd4..76f0c9917c5 100644 --- a/src/i18n/content/pt/docs/alerts/get-notified/notification-integrations.mdx +++ b/src/i18n/content/pt/docs/alerts/get-notified/notification-integrations.mdx @@ -616,7 +616,7 @@ Leia mais sobre cada uma de nossas integração de notificação específica. Para criar um destino ServiceNow, siga estas etapas: - 1. [Baixe e instale o aplicativo New Relic](https://store.servicenow.com/sn_appstore_store.do#!/store/application/d117597d1b9b9d9078faddf7b04bcba7/1.0.0?referer=%2Fstore%2Fsearch%3Flistingtype%3Dallintegrations%25253Bancillary_app%25253Bcertified_apps%25253Bcontent%25253Bindustry_solution%25253Boem%25253Butility%25253Btemplate%26q%3Dnew%2520relic&sl=sh) na loja ServiceNow. + 1. [Baixe e instale o aplicativo New Relic](https://store.servicenow.com/sn_appstore_store.do#!/store/application/d117597d1b9b9d9078faddf7b04bcba7/1.1.1?referer=%2Fstore%2Fsearch%3Flistingtype%3Dallintegrations%25253Bancillary_app%25253Bcertified_apps%25253Bcontent%25253Bindustry_solution%25253Boem%25253Butility%25253Btemplate%26q%3Dnew%2520relic&sl=sh) na loja ServiceNow. 2. Crie um usuário dentro do ServiceNow. Certifique-se de ativar a opção **Web service access only** e conceder a função `x_newre_core.inbound_api` ao usuário criado. Copie e salve a senha gerada. diff --git a/src/i18n/content/pt/docs/apm/agents/net-agent/installation/update-net-agent.mdx b/src/i18n/content/pt/docs/apm/agents/net-agent/installation/update-net-agent.mdx index 9f49e0151b8..17cdb15a7d8 100644 --- a/src/i18n/content/pt/docs/apm/agents/net-agent/installation/update-net-agent.mdx +++ b/src/i18n/content/pt/docs/apm/agents/net-agent/installation/update-net-agent.mdx @@ -22,7 +22,6 @@ Existem várias maneiras de instalar o agente .NET, o que significa que existem Se você tiver outras instalações, consulte estes documentos de instalação dessas configurações para obter mais contexto: -* [Aplicativos Web do Azure](/docs/apm/agents/net-agent/azure-installation/install-net-agent-azure-web-apps/#site-extention-update) * Docker: [para Windows](/install/dotnet/?deployment=windowsInstall&docker=yesDocker) | para [Linux](/install/dotnet/?deployment=linux&docker=yesDocker) * [Nuget](/docs/apm/agents/net-agent/install-guides/install-net-agent-using-nuget) @@ -60,7 +59,8 @@ Siga as instruções de atualização para seu agente: Para atualizar o agente .NET para um aplicativo Web do Azure usando a extensão do site do Azure do New Relic, siga as instruções de instalação para: - * Instale a versão mais recente da extensão do site New Relic Azure, que atualiza os arquivos do agente para a versão mais recente. + * Remova a extensão do site New Relic Azure, isso desinstala o agente + * Reinstale a versão mais recente da extensão do site do New Relic Azure usando [estas instruções de instalação](/install/dotnet/?deployment=azure&azure=azuresiteextension), que instalam a versão mais recente do agente. * Reinicie o aplicativo Web para iniciar o agente atualizado. diff --git a/src/i18n/content/pt/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx b/src/i18n/content/pt/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx index ce98f5e1461..0d942862da2 100644 --- a/src/i18n/content/pt/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx +++ b/src/i18n/content/pt/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx @@ -50,15 +50,15 @@ Consulta original: ```sql FROM PageAction SELECT count(*) AS 'views' -WHERE countryCode IN ({{countryCode}}) and appName = 'Test App' FACET countryCode +WHERE countryCode IN ({{countryCode}}) AND appName = 'Test App' FACET countryCode ``` Consulta com uma variável excluída: ```sql - FROM PageAction - SELECT count(*) AS 'views' - WHERE true and appName = 'Test App' FACET countryCode +FROM PageAction +SELECT count(*) AS 'views' +WHERE true AND appName = 'Test App' FACET countryCode ``` Esse recurso é particularmente útil quando: @@ -71,7 +71,7 @@ Limitações na variável include: * Quando usada em casos FACET, a condição é substituída por verdadeira e a converte em uma condição sempre verdadeira. -* Quando usado em outros contextos, como funções ou com a instrução SELECT, você obterá o seguinte erro: `"Unknown function Disable_variable()"`. Isso ocorre porque a função de desabilitar variável ainda não foi implementada para esses casos específicos. +* Quando usado em outros contextos, como funções ou com a instrução `SELECT` , você obterá o seguinte erro: `"Unknown function Disable_variable()"`. Isso ocorre porque a função de desabilitar variável ainda não foi implementada para esses casos específicos. ## Requisitos e limitações [#requirements] @@ -87,7 +87,7 @@ Pontos importantes a serem observados sobre a adição de uma consulta: * Para ajudá-lo ao criar uma consulta, há um código de cores: - * As cláusulas `from`, `select`, `facet` e `where` estão em rosa. + * As cláusulas `FROM`, `SELECT`, `FACET` e `WHERE` estão em rosa. * Identificador estão em preto. * As funções estão em azul. * As cordas estão em verde. @@ -193,7 +193,7 @@ A criação de uma variável de modelo consiste em duas etapas. @@ -288,7 +288,7 @@ A criação de uma variável de modelo consiste em duas etapas. Observe que estas são as cláusulas NRQL que aceitarão variáveis de modelo como valores: `SELECT`, `FROM`, `FACET`, `ORDER BY` e `WHERE`. - Em vez disso, a seguinte lista de cláusulas NRQL não aceitará variáveis de modelo como argumentos: `AS`, `COMPARE WITH`, `LIMIT`, `OFFSET`, `SINCE`, `SLIDE BY`, `TIMESERIES`, `UNTIL` e `WITH...`. + Em vez disso, a seguinte lista de cláusulas NRQL não aceitará variáveis de modelo como argumentos: `AS`, `COMPARE WITH`, `LIMIT`, `OFFSET`, `SINCE`, `SLIDE BY`, `TIMESERIES`, `UNTIL` e `WITH`.... 5. Clique **Save** @@ -313,7 +313,7 @@ Você pode usar praticamente qualquer consulta NRQL, desde que retorne uma lista Com [`uniques`](/docs/nrql/nrql-syntax-clauses-functions/#func-uniques): ```sql - From PageAction select uniques(countryCode) +FROM PageAction SELECT uniques(countryCode) ``` ```sql @@ -324,8 +324,8 @@ Com [`uniques`](/docs/nrql/nrql-syntax-clauses-functions/#func-uniques): Com [`keyset`](/docs/nrql/nrql-syntax-clauses-functions/#keyset): ```sql - -- with `keyset`, you'll get a list with all of the attributes from the table you're querying from - From PageAction select keyset() SINCE 1 day ago +-- with `keyset`, you'll get a list with all of the attributes from the table you're querying from +FROM PageAction SELECT keyset() SINCE 1 day ago ``` Lembre-se de que variáveis aninhadas não são suportadas, pois não pode haver variáveis dentro de variáveis. @@ -361,7 +361,8 @@ Aqui estão alguns tipos diferentes de implementações de variáveis de modelo. Aqui está um exemplo de consulta que usa duas variáveis de modelo. Observe que isso pressupõe que as variáveis de modelo `countryCode` e `city` já tenham sido criadas e que tenham um único valor. ```sql - SELECT countryCode, city FROM PageAction WHERE countryCode = {{countryCode}} and city = {{city}} + SELECT countryCode, city FROM PageAction + WHERE countryCode = {{countryCode}} AND city = {{city}} ``` Creating a widget using multiple variables @@ -369,21 +370,22 @@ Aqui estão alguns tipos diferentes de implementações de variáveis de modelo. Se você tiver vários valores para suas variáveis, como `Chicago`, `New York`, `Paris` para sua variável `city` , será necessário usar `IN`: ```sql - SELECT countryCode, city FROM PageAction WHERE countryCode IN ({{countryCode}}) and city IN ({{city}}) + SELECT countryCode, city FROM PageAction + WHERE countryCode IN ({{countryCode}}) AND city IN ({{city}}) ``` Usando variáveis e [regex](/docs/query-your-data/nrql-new-relic-query-language/get-started/nrql-syntax-clauses-functions/#func-capture), você pode criar um filtro, desde que tenha certeza de que uma parte do filtro foi corrigida. - Você precisa usar esta correspondência parcial se quiser usar `like`. + Você precisa usar esta correspondência parcial se quiser usar `LIKE`. Digamos que você queira filtrar por versão de lançamento. A consulta retorna algo como: `release-1234`. Você pode criar uma variável usando [`aparse`](/docs/query-your-data/nrql-new-relic-query-language/get-started/nrql-syntax-clauses-functions/#func-aparse) para analisar o número da versão: ```sql - SELECT uniques(aparse(platformVersion , 'release-*')) FROM PageView + SELECT uniques(aparse(platformVersion, 'release-*')) FROM PageView ``` Creating the release version variable @@ -391,7 +393,8 @@ Aqui estão alguns tipos diferentes de implementações de variáveis de modelo. Em seguida, crie um widget com a seguinte consulta: ```sql - SELECT count(*) FROM PageAction WHERE aparse(platformVersion, 'release-*') IN ({{releaseversion}}) facet platformVersion + SELECT count(*) FROM PageAction + WHERE aparse(platformVersion, 'release-*') IN ({{releaseversion}}) FACET platformVersion ``` Creating the widget @@ -399,7 +402,8 @@ Aqui estão alguns tipos diferentes de implementações de variáveis de modelo. Ou se preferir, você pode usar o comando [`capture`](/docs/query-your-data/nrql-new-relic-query-language/get-started/nrql-syntax-clauses-functions/#func-capture) : ```sql - SELECT count(*) FROM PageAction WHERE capture(platformVersion, r'release-(?P\d+)') IN ({{releaseversion}}) Facet platformVersion + SELECT count(*) FROM PageAction + WHERE capture(platformVersion, r'release-(?P\d+)') IN ({{releaseversion}}) FACET platformVersion ``` Creating the widget @@ -434,7 +438,7 @@ Aqui estão alguns tipos diferentes de implementações de variáveis de modelo. com uma consulta NRQL } > - Você pode criar uma variável do tipo NRQL com um formato de saída de string e usá-la após uma cláusula `facet` para agrupar por valores diferentes. + Você pode criar uma variável do tipo NRQL com um formato de saída de string e usá-la após uma cláusula `FACET` para agrupar por valores diferentes. Por exemplo, você pode criar uma variável chamada `{{userAgentName}}` com a seguinte aparência: @@ -447,7 +451,8 @@ Aqui estão alguns tipos diferentes de implementações de variáveis de modelo. Então você criaria um widget com a seguinte consulta: ```sql - SELECT count(*) FROM PageAction WHERE userAgentName={{userAgentName}} FACET userAgentName + SELECT count(*) FROM PageAction + WHERE userAgentName={{userAgentName}} FACET userAgentName ``` Creating widget using facet @@ -496,7 +501,7 @@ Aqui estão alguns tipos diferentes de implementações de variáveis de modelo. - Por padrão, a opção “ignorar seletor de hora” está habilitada, o que significa que a consulta é sempre executada usando o valor padrão do intervalo de tempo 1 `HOUR`, mesmo que o seletor de hora no dashboard tenha um valor diferente selecionado (ex. 5 minutos). , 3 horas, etc.). A exceção para esse caso é quando a consulta possui um intervalo de tempo explícito definido com uma cláusula `SINCE` , como por exemplo: + Por padrão, a opção “ignorar seletor de hora” está habilitada, o que significa que a consulta é sempre executada usando o valor de intervalo de tempo padrão `1 hour`, mesmo que o seletor de hora no dashboard tenha um valor diferente selecionado (ex. `5 minutes`, `3 hours`, etc.). A exceção para esse caso é quando a consulta tem um intervalo de tempo explícito definido com uma cláusula `SINCE` , como por exemplo: ```sql SELECT uniques(eventId) @@ -506,7 +511,7 @@ Aqui estão alguns tipos diferentes de implementações de variáveis de modelo. Os resultados estarão no intervalo dos últimos 5 minutos. - Quando a opção “ignorar seletor de hora” estiver desligada, a consulta será executada com o valor selecionado no seletor de hora. Por exemplo, se você definir o seletor de hora para 30 minutos, como na captura de tela abaixo, no formulário de edição de variáveis, o campo "ignorar seletor de hora" ficará desativado. + Quando a opção "ignorar seletor de hora" estiver desativada, a consulta será executada com o valor selecionado no seletor de hora. Por exemplo, se você definir o seletor de horas para 30 minutos, como na captura de tela abaixo, no formulário de edição das variáveis, o campo "ignorar seletor de horas" será definido como desativado. A screenshot showing the time picker diff --git a/src/install/ai-monitoring/intro.mdx b/src/install/ai-monitoring/intro.mdx index 47adb5b8181..76d312fa689 100644 --- a/src/install/ai-monitoring/intro.mdx +++ b/src/install/ai-monitoring/intro.mdx @@ -14,3 +14,8 @@ When you [install AI monitoring](/docs/ai-monitoring/intro-to-ai-monitoring), yo
Go to **[one.newrelic.com](https://one.newrelic.com) > All Capabilities > AI Monitoring > AI Responses**
+ + + When enabled, AI monitoring records a streaming copy of inputs and outputs sent to and from the models you choose to monitor, including any personal information contained therein. + You're responsible for obtaining consent from your model users that their interactions may be recorded by a third party (New Relic) for the purpose of providing the AI monitoring feature. + diff --git a/src/nav/alerts.yml b/src/nav/alerts.yml index d2e391c51c0..318140451e1 100644 --- a/src/nav/alerts.yml +++ b/src/nav/alerts.yml @@ -9,6 +9,9 @@ pages: pages: - title: Alert conditions path: /docs/alerts/create-alert/create-alert-condition/alert-conditions + pages: + - title: Cross-account alert + path: /docs/alerts/create-alert/create-alert-condition/cross-account-alert - title: Create NRQL conditions path: /docs/alerts/create-alert/create-alert-condition/create-nrql-alert-conditions - title: Create (HNR) NRQL conditions diff --git a/src/nav/telemetry-data-platform.yml b/src/nav/telemetry-data-platform.yml index 304f9e7c731..e43ebe4fdd6 100644 --- a/src/nav/telemetry-data-platform.yml +++ b/src/nav/telemetry-data-platform.yml @@ -139,6 +139,8 @@ pages: pages: - title: 'Channels' path: /docs/apis/nerdgraph/examples/nerdgraph-api-notifications-channels + - title: 'Cross-account alerting elections' + path: /docs/apis/nerdgraph/examples/nerdgraph-api-cross-account-alerting-elections - title: 'Destinations' path: /docs/apis/nerdgraph/examples/nerdgraph-api-notifications-destinations - title: Incident correlation topology diff --git a/src/utils/getAgentName.js b/src/utils/getAgentName.js index 33d5ab596c3..39fa09efd0d 100644 --- a/src/utils/getAgentName.js +++ b/src/utils/getAgentName.js @@ -38,6 +38,7 @@ const AGENTS = { 'service-levels-release-notes': 'service levels', 'serverless-release-notes': 'serverless', 'xamarin-release-notes': 'xamarin', + 'nrdot-release-notes': 'nrdot', }; // keeping the naming streamlined and in matching with previous data diff --git a/static/images/alerts_screenshot-crop_set-a-query.webp b/static/images/alerts_screenshot-crop_set-a-query.webp index 1e7b10362d9..4e9e50ea54b 100644 Binary files a/static/images/alerts_screenshot-crop_set-a-query.webp and b/static/images/alerts_screenshot-crop_set-a-query.webp differ diff --git a/static/images/azureserverless.webp b/static/images/azureserverless.webp new file mode 100644 index 00000000000..245240a2315 Binary files /dev/null and b/static/images/azureserverless.webp differ diff --git a/static/images/otelmetrics.webp b/static/images/otelmetrics.webp new file mode 100644 index 00000000000..a1273a2dc6f Binary files /dev/null and b/static/images/otelmetrics.webp differ
- New Relic puede instrumentar automáticamente servicios escritos en C#. Vaya a nuestra página de inicio rápido de C# para [instalar el panel de C#](https://newrelic.com/instant-observability/c-sharp). + New Relic puede instrumentar automáticamente servicios escritos en C#. Vaya a nuestra página de inicio rápido de C# para [instalar el dashboard de C#](https://newrelic.com/instant-observability/c-sharp).
- [Panel](/docs/query-your-data/explore-query-data/dashboards/introduction-dashboards/) + [Dashboards](/docs/query-your-data/explore-query-data/dashboards/introduction-dashboards/) diff --git a/src/i18n/content/es/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-monitor.mdx b/src/i18n/content/es/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-monitor.mdx index 37252958882..c72cba1dc22 100644 --- a/src/i18n/content/es/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-monitor.mdx +++ b/src/i18n/content/es/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-monitor.mdx @@ -246,7 +246,7 @@ La siguiente tabla muestra las diferencias entre ambas soluciones: Al migrar de nuestra integración tradicional de Azure al monitoreo de integración de Azure, aquí hay un par de cosas a tener en cuenta: -* Cuando habilita un monitoreo de integración de Azure, se creará una nueva entidad separada para todos sus recursos. La entidad creada por la integración Azure Polling se queda como está. Esto significa que debe actualizar el panel, las alertas y cualquier otra capacidad que haga referencia a esas entidades. +* Cuando habilita un monitoreo de integración de Azure, se creará una nueva entidad separada para todos sus recursos. La entidad creada por la integración Azure Polling se queda como está. Esto significa que debe actualizar el dashboard, las alertas y cualquier otra capacidad que haga referencia a esas entidades. * Las entidades antiguas están disponibles durante 24 horas. * Un nombre de métrica puede aparecer dos veces cuando la métrica tiene diferentes combinaciones de dimensiones. Puede evitar nombres de métricas duplicados [creando una consulta que filtre las agregaciones de sus datos](/docs/infrastructure/microsoft-azure-integrations/get-started/azure-integration-metrics/#metrics-with-many-dimension-combinations). diff --git a/src/i18n/content/es/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-nginx-buildpack-integration.mdx b/src/i18n/content/es/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-nginx-buildpack-integration.mdx index 61ef124cdbe..19a36457763 100644 --- a/src/i18n/content/es/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-nginx-buildpack-integration.mdx +++ b/src/i18n/content/es/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-nginx-buildpack-integration.mdx @@ -140,7 +140,7 @@ Puede instalar los paquetes de compilación como un mosaico en Ops Manager o ind - Navegue hasta el panel de instalación de Ops Manager y haga clic en **Import a Product** para cargar el archivo del producto. + Navegue hasta el dashboard de instalación de Ops Manager y haga clic en **Import a Product** para cargar el archivo del producto. diff --git a/src/i18n/content/es/docs/logs/get-started/get-started-log-management.mdx b/src/i18n/content/es/docs/logs/get-started/get-started-log-management.mdx index d2d9f3f1338..76c4b4e9707 100644 --- a/src/i18n/content/es/docs/logs/get-started/get-started-log-management.mdx +++ b/src/i18n/content/es/docs/logs/get-started/get-started-log-management.mdx @@ -24,7 +24,7 @@ Nuestra solución proporciona una visibilidad más La administración de logs proporciona una manera de conectar sus datos log con el resto de los datos de su aplicación e infraestructura. Puede llegar a la causa raíz de los problemas rápidamente, sin perder el contexto al cambiar entre herramientas. Por ejemplo, puedes: * Obtenga datos relevantes a través de la UI de New Relic que proporciona un logs en el contexto de problemas en sus aplicaciones y hosts. -* Profundice en los datos log utilizando nuestra UI de log y cree gráficos, paneles y alertas personalizados. +* Profundice en los datos log utilizando nuestra UI de log y cree gráficos, dashboards y alertas personalizados. * Busque instantáneamente en su log. * Solucione problemas de rendimiento sin cambiar entre otras herramientas. * Visualiza todo en un solo lugar. @@ -76,7 +76,7 @@ Para obtener información sobre los permisos relacionados con log , consulte [Pe 1. Si aún no tiene una, [cree una cuenta New Relic](https://newrelic.com/signup). Es gratis, para siempre. 2. Configure una de [nuestras opciones para el log de informes](#integrate-logs). 3. Explore [datoslog relevantes en su plataforma](/docs/apm/new-relic-apm/getting-started/get-started-logs-context#response-time-example), incluidos errores, rastreo distribuido, hosts y más. -4. Utilice nuestra [UI de logs](/docs/logs/ui-data/use-logs-ui) como un flujo de trabajo sencillo a través de todos los logs, atributos, patrones, logging de cola en vivo y consultas. Añade alerta, consulta tus datos y crea un panel. +4. Utilice nuestra [UI de logs](/docs/logs/ui-data/use-logs-ui) como un flujo de trabajo sencillo a través de todos los logs, atributos, patrones, logging de cola en vivo y consultas. Añade alerta, consulta tus datos y crea un dashboard. ¿Utiliza Datadog para monitor su log pero quiere probar las capacidades de monitoreo de New Relic de forma gratuita? Consulte nuestra [guía sobre cómo migrar desde Datadog](/docs/journey-migration/migrating-from-dd/) para saber cómo hacerlo. diff --git a/src/i18n/content/es/docs/logs/ui-data/parsing.mdx b/src/i18n/content/es/docs/logs/ui-data/parsing.mdx index ac604b4360e..fc569879bcb 100644 --- a/src/i18n/content/es/docs/logs/ui-data/parsing.mdx +++ b/src/i18n/content/es/docs/logs/ui-data/parsing.mdx @@ -179,7 +179,7 @@ Tenga en cuenta que los nombres de las variables deben establecerse explícitame 6. Habilite y guarde la regla de análisis. - Pronto verá que su registro del Servicio de inventario se enriquece con dos campos nuevos: `error_message` y `product_id`. Desde aquí, puedes consultar estos campos, crear gráficos y paneles, establecer alertas, etc. + Pronto verá que su registro del Servicio de inventario se enriquece con dos campos nuevos: `error_message` y `product_id`. Desde aquí, puedes consultar estos campos, crear gráficos y dashboards, establecer alertas, etc. Para obtener detalles completos, consulte [nuestros documentos para agregar reglas de análisis personalizadas en la UI](#custom-parsing). diff --git a/src/i18n/content/es/docs/network-performance-monitoring/advanced/advanced-config.mdx b/src/i18n/content/es/docs/network-performance-monitoring/advanced/advanced-config.mdx index 26f35f27238..9a858c1160a 100644 --- a/src/i18n/content/es/docs/network-performance-monitoring/advanced/advanced-config.mdx +++ b/src/i18n/content/es/docs/network-performance-monitoring/advanced/advanced-config.mdx @@ -1903,7 +1903,7 @@ El Monitoreo de red agente tiene soporte integrado para recuperar claves de [AWS - [Clave API del panel de control de Meraki](https://documentation.meraki.com/General_Administration/Other_Topics/Cisco_Meraki_Dashboard_API#Generate_API_Key) para autenticación. + [Clave API del dashboard de Meraki](https://documentation.meraki.com/General_Administration/Other_Topics/Cisco_Meraki_Dashboard_API#Generate_API_Key) para autenticación.
- Escribe aquí tu consulta usando `uniques (attribute)`. + Escribe aquí tu consulta usando `uniques(attribute)`.
- `uniques (attribute)`を使用してここにクエリを記述します。 + `uniques(attribute)`を使用してここにクエリを記述します。
- `uniques (attribute)`사용하여 여기에 쿼리를 작성하십시오. + `uniques(attribute)`사용하여 여기에 쿼리를 작성하십시오.
- Escreva aqui sua consulta usando `uniques (attribute)`. + Escreva aqui sua consulta usando `uniques(attribute)`.