diff --git a/src/content/docs/accounts/install-new-relic/partner-based-installation/google-app-engine-environment.mdx b/src/content/docs/accounts/install-new-relic/partner-based-installation/google-app-engine-environment.mdx index be0f50ce04f..f502818af2c 100644 --- a/src/content/docs/accounts/install-new-relic/partner-based-installation/google-app-engine-environment.mdx +++ b/src/content/docs/accounts/install-new-relic/partner-based-installation/google-app-engine-environment.mdx @@ -119,4 +119,4 @@ To monitor your applications that reside in a Google App Engine flexible environ ## Infrastructure integration for Google App Engine [#gae-integration] -Our [infrastructure monitoring](/docs/infrastructure) offers an [integration](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) that reports data about your Google App Engine services. With the [Google App Engine integration](/docs/gcp-gcp_appengine-integration), you can view dashboards and alerts, query metric data, and explore inventory data. +Our [infrastructure monitoring](/docs/infrastructure) offers an [integration](/docs/infrastructure/introduction-infra-monitoring) that reports data about your Google App Engine services. With the [Google App Engine integration](/docs/gcp-gcp_appengine-integration), you can view dashboards and alerts, query metric data, and explore inventory data. 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 641aea5393b..a0a43b4205c 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 @@ -39,140 +39,140 @@ Microsoft is retiring Microsoft 365 webhook-based Connectors service in Teams by src="/images/alerts_workflow_payload.webp" /> 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": [ + ```json + { + "type": "message", + "attachments": [ { - "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": [ + "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": "ColumnSet", + "columns": [ + { - "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]}} - { - "type": "TextBlock", - "text": {{ json accumulations.conditionDescription.[0] }}, - "wrap": true - }, - {{/if}} - {{#eq "Not Available" violationChartUrl}} - {{else}} - { - "type": "Image", - "url": {{ json violationChartUrl }} - }, - {{/eq}} - { - "type": "FactSet", - "facts": [ - { - "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]}} - }, - {{/if}} - {{#if accumulations.conditionName }} - { - "title": "*Condition:*", - "value": {{ json accumulations.conditionName.[0]}} - }, - {{#eq impactedEntitiesCount 1}} - {{else}} - { - "title": "*Total Incidents:*", - "value": {{ json impactedEntitiesCount}} - }, - {{/eq}} - {{/if}} - { - "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": "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": "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]}} + { + "type": "TextBlock", + "text": {{ json accumulations.conditionDescription.[0] }}, + "wrap": true + }, + {{/if}} + {{#eq "Not Available" violationChartUrl}} + {{else}} + { + "type": "Image", + "url": {{ json violationChartUrl }} + }, + {{/eq}} + { + "type": "FactSet", + "facts": [ + { + "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]}} + }, + {{/if}} + {{#if accumulations.conditionName }} + { + "title": "*Condition:*", + "value": {{ json accumulations.conditionName.[0]}} + }, + {{#eq impactedEntitiesCount 1}} + {{else}} + { + "title": "*Total Incidents:*", + "value": {{ json impactedEntitiesCount}} + }, + {{/eq}} + {{/if}} + { + "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}} + ] + } ] + } } ] } - } - ] -} - ``` + ``` 4. Click **Save message**. diff --git a/src/content/docs/apis/nerdgraph/examples/export-import-dashboards-using-api.mdx b/src/content/docs/apis/nerdgraph/examples/export-import-dashboards-using-api.mdx index 26bd5335eb4..52a602f2cad 100644 --- a/src/content/docs/apis/nerdgraph/examples/export-import-dashboards-using-api.mdx +++ b/src/content/docs/apis/nerdgraph/examples/export-import-dashboards-using-api.mdx @@ -25,7 +25,7 @@ To do so: Use the following query to retrieve a list of your existing dashboards: -``` +```graphql { actor { entitySearch(queryBuilder: {type: DASHBOARD}) { @@ -47,10 +47,10 @@ Use the following query to retrieve a list of your existing dashboards: Use the following query to export, then extract the dashboard's entity information from the output: -``` +```graphql { actor { - entity(guid: "your_guid_xxxxxxx") { + entity(guid: "YOUR_DASHBOARD_GUID") { ... on DashboardEntity { name permissions @@ -81,9 +81,9 @@ Example entity information in GraphiQL output: Use the following mutation to import the dashboard into another account: -``` +```graphql mutation create($dashboard: DashboardInput!) { - dashboardCreate(accountId: your_new_AccountID, dashboard: $dashboard) { + dashboardCreate(accountId: YOUR_NEW_ACCOUNT_ID, dashboard: $dashboard) { entityResult { guid name diff --git a/src/content/docs/apis/nerdgraph/examples/manage-accounts-nerdgraph.mdx b/src/content/docs/apis/nerdgraph/examples/manage-accounts-nerdgraph.mdx index f14246b6686..6e4c9e9dcdc 100644 --- a/src/content/docs/apis/nerdgraph/examples/manage-accounts-nerdgraph.mdx +++ b/src/content/docs/apis/nerdgraph/examples/manage-accounts-nerdgraph.mdx @@ -61,7 +61,9 @@ Here's an example of how to create an account. Before creating an account, make ```graphql mutation { - accountManagementCreateAccount(managedAccount: {name: "NEW_ACCOUNT_NAME"}) { + accountManagementCreateAccount( + managedAccount: {name: "NEW_ACCOUNT_NAME"} + ) { managedAccount { id name @@ -75,7 +77,9 @@ If you have a complex account structure you may use the optional `regionCode` pa ```graphql mutation { - accountManagementCreateAccount(managedAccount: {name: "NEW_ACCOUNT_NAME", regionCode: "eu01"}) { + accountManagementCreateAccount( + managedAccount: { name: "NEW_ACCOUNT_NAME", regionCode: "eu01" } + ) { managedAccount { id name @@ -91,7 +95,9 @@ Here's an example of how to rename an account. ```graphql mutation { - accountManagementUpdateAccount(managedAccount: {name: "UPDATED_ACCOUNT_NAME", id: 101010101}) { + accountManagementUpdateAccount( + managedAccount: { name: "UPDATED_ACCOUNT_NAME", id: 101010101 } + ) { managedAccount { id name @@ -146,9 +152,10 @@ Here are some errors and what they mean: - ```"unauthorized", { - extensions: { nerdGraphExtensions: { errorClass: "ACCESS_DENIED" } } - } + ``` + "unauthorized", { + extensions: { nerdGraphExtensions: { errorClass: "ACCESS_DENIED" } } + } ``` @@ -160,9 +167,9 @@ Here are some errors and what they mean: ``` - cannot create subaccount -- multiple parent account ids found. Please use Partnership API.", { - extensions: { nerdGraphExtensions: { errorClass: "SERVER_ERROR" } } - } + "cannot create subaccount -- multiple parent account ids found. Please use Partnership API.", { + extensions: { nerdGraphExtensions: { errorClass: "SERVER_ERROR" } } + } ``` diff --git a/src/content/docs/apis/nerdgraph/examples/manage-live-chart-urls-via-api.mdx b/src/content/docs/apis/nerdgraph/examples/manage-live-chart-urls-via-api.mdx index 43d11b8072a..8ca54da0aa4 100644 --- a/src/content/docs/apis/nerdgraph/examples/manage-live-chart-urls-via-api.mdx +++ b/src/content/docs/apis/nerdgraph/examples/manage-live-chart-urls-via-api.mdx @@ -24,7 +24,7 @@ To do so: Use the following query to retrieve a list of existing live chart URLs: -``` +```graphql { actor { dashboard { @@ -48,9 +48,9 @@ Use the following query to retrieve a list of existing live chart URLs: Use the following query to revoke the live chart URL you specify: -``` +```graphql mutation { - dashboardWidgetRevokeLiveUrl(uuid: "") { + dashboardWidgetRevokeLiveUrl(uuid: "LIVE_CHART_UUID") { uuid errors { description diff --git a/src/content/docs/apis/nerdgraph/examples/mobile-monitoring-config-nerdgraph.mdx b/src/content/docs/apis/nerdgraph/examples/mobile-monitoring-config-nerdgraph.mdx index d0ae991c0c6..335f0c730e7 100644 --- a/src/content/docs/apis/nerdgraph/examples/mobile-monitoring-config-nerdgraph.mdx +++ b/src/content/docs/apis/nerdgraph/examples/mobile-monitoring-config-nerdgraph.mdx @@ -26,17 +26,15 @@ mutation CreateExampleMobileApplication($accountId: Int!, $name: String!) { name } } - ``` Variables: -```JSON +```json { "accountId": Int!, "name": String! } - ``` ## Retrieving the application token [#get-mobile-token] @@ -63,7 +61,7 @@ query FetchMobileApplicationToken($guid: EntityGuid!) { Variables: -```JSON +```json { "guid": EntityGuid! } @@ -76,7 +74,10 @@ Here's an example mutation that changes the name of your mobile app in New Relic Mutation: ```graphql -mutation UpdateMobileApplicationAlias($guid: EntityGuid!, $settings: $AgentApplicationSettingsUpdateInput) { +mutation UpdateMobileApplicationAlias( + $guid: EntityGuid!, + $settings: $AgentApplicationSettingsUpdateInput +) { agentApplicationSettingsUpdate(guid: $guid, settings: $settings) { alias guid @@ -91,7 +92,7 @@ mutation UpdateMobileApplicationAlias($guid: EntityGuid!, $settings: $AgentAppli Variables: -```JSON +```json { "guid": EntityGuid!, "settings": { @@ -107,7 +108,10 @@ Here's an example of how to configure settings vi Mutation: ```graphql -mutation UpdateMobileSettingsExample($guid: EntityGuid!, $settings: AgentApplicationSettingsUpdateInput!) { +mutation UpdateMobileSettingsExample( + $guid: EntityGuid! + $settings: AgentApplicationSettingsUpdateInput! +) { agentApplicationSettingsUpdate(guid: $guid, settings: $settings) { guid errors { @@ -138,7 +142,7 @@ mutation UpdateMobileSettingsExample($guid: EntityGuid!, $settings: AgentApplica Variables: -```JSON +```json { "guid": EntityGuid!, "settings": { diff --git a/src/content/docs/apis/nerdgraph/examples/nerdgraph-cloud-integrations-api-tutorial.mdx b/src/content/docs/apis/nerdgraph/examples/nerdgraph-cloud-integrations-api-tutorial.mdx index bf601a4e29d..d481448b258 100644 --- a/src/content/docs/apis/nerdgraph/examples/nerdgraph-cloud-integrations-api-tutorial.mdx +++ b/src/content/docs/apis/nerdgraph/examples/nerdgraph-cloud-integrations-api-tutorial.mdx @@ -52,10 +52,10 @@ Queries are requests that are intended to only fetch data (no side effects). Que **Anonymous:** - ``` + ```graphql { actor { - account(id: ) { + account(id: YOUR_ACCOUNT_ID) { cloud { providers { id @@ -75,10 +75,10 @@ Queries are requests that are intended to only fetch data (no side effects). Que **Named:** - ``` + ```graphql query cloudProviders { actor { - account(id: ) { + account(id: YOUR_ACCOUNT_ID) { cloud { providers { id @@ -98,10 +98,10 @@ Queries are requests that are intended to only fetch data (no side effects). Que > This query returns information about a specific provider account for your AWS integration. The properties `id`, `name`, `slug` are requested, along with a list of integrations available to be monitored. - ``` + ```graphql { actor { - account(id: ) { + account(id: YOUR_ACCOUNT_ID) { cloud { provider(slug: "aws") { id @@ -126,10 +126,10 @@ Queries are requests that are intended to only fetch data (no side effects). Que > This query returns information about a specific cloud service integration of a provider. In this example, the integration is the [AWS ALB monitoring integration](/docs/integrations/amazon-integrations/aws-integrations-list/aws-alb-monitoring-integration) and the provider is AWS. The properties `id`, `name`, `slug`, and `isAllowed` are requested with the available configuration parameters. - ``` + ```graphql { actor { - account(id: ) { + account(id: YOUR_ACCOUNT_ID) { cloud { provider(slug: "aws") { service(slug: "alb") { @@ -152,10 +152,10 @@ Queries are requests that are intended to only fetch data (no side effects). Que > This query returns the list of cloud accounts enabled with your New Relic account. (Your cloud account associates your New Relic account and a specific provider account with your integration.) You can enable multiple cloud provider accounts in the same New Relic account, even with the same cloud provider. - ``` + ```graphql { actor { - account(id: ) { + account(id: YOUR_ACCOUNT_ID) { cloud { linkedAccounts { id @@ -179,12 +179,12 @@ Queries are requests that are intended to only fetch data (no side effects). Que > This query returns information about a linked account, including the properties `name`, `providerId`, and a list of the cloud integrations enabled for monitoring. - ``` + ```graphql { actor { - account(id: ) { + account(id: YOUR_ACCOUNT_ID) { cloud { - linkedAccount(id: ) { + linkedAccount(id: LINKED_CLOUD_ACCOUNT_ID) { name provider { id @@ -210,10 +210,10 @@ Queries are requests that are intended to only fetch data (no side effects). Que > This query returns all monitored integrations for all the provider cloud accounts. - ``` + ```graphql { actor { - account(id: ) { + account(id: YOUR_ACCOUNT_ID) { cloud { linkedAccounts { name @@ -245,18 +245,18 @@ Queries are requests that are intended to only fetch data (no side effects). Que > This query returns information about a specific integration from a specific linked account. - ``` + ```graphql { actor { - account(id: ) { + account(id: YOUR_ACCOUNT_ID) { cloud { - linkedAccount(id: ) { + linkedAccount(id: LINKED_CLOUD_ACCOUNT_ID) { name provider { id name } - integration(id: ) { + integration(id: INTEGRATION_ID) { id name service { @@ -290,25 +290,25 @@ Mutations are requests that are intended to have side effects, such as creating **Required:** - * The parameter `` is required and cannot be empty. It must be unique in your New Relic account. + * The parameter `PROVIDER_ACCOUNT_NAME` is required and cannot be empty. It must be unique in your New Relic account. * Other parameters are specific to the provider (AWS, GCP, and Azure) and are also required. In the following sections, you can see which parameters are required for each provider account. After linking an account the `createdAt` and `updatedAt` values are equal. - ``` + ```graphql mutation { cloudLinkAccount( accounts: { - accountId: , + accountId: YOUR_ACCOUNT_ID, aws: [{ - name: , - + name: PROVIDER_ACCOUNT_NAME, + # other parameters }] azure: [{ - name: , - + name: PROVIDER_ACCOUNT_NAME, + # other parameters }] gcp: [{ - name: , - + name: PROVIDER_ACCOUNT_NAME, + # other parameters }] } ) { @@ -331,14 +331,14 @@ Mutations are requests that are intended to have side effects, such as creating > This mutation links an AWS provider account to your New Relic account. - ``` + ```graphql mutation { cloudLinkAccount( - accountId: , + accountId: YOUR_ACCOUNT_ID, accounts: { aws: [{ - name: , - arn: + name: PROVIDER_ACCOUNT_NAME, + arn: AWS_ROLE_ARN }] } ) { @@ -361,14 +361,14 @@ Mutations are requests that are intended to have side effects, such as creating > This mutation links an AWS account sending data through CloudWatch Metric Streams to your New Relic account. - ``` + ```graphql mutation { cloudLinkAccount( - accountId: , + accountId: YOUR_ACCOUNT_ID, accounts: { aws: [{ - name: , - arn: , + name: PROVIDER_ACCOUNT_NAME, + arn: AWS_ROLE_ARN, metricCollectionMode: PUSH }] } @@ -392,17 +392,17 @@ Mutations are requests that are intended to have side effects, such as creating > This mutation links a Microsoft Azure cloud subscription to the New Relic account. - ``` + ```graphql mutation { cloudLinkAccount( - accountId: , + accountId: YOUR_ACCOUNT_ID, accounts: { azure: [{ - name: , - applicationId: , - clientSecret: , - tenantId: , - subscriptionId: + name: PROVIDER_ACCOUNT_NAME, + applicationId: AZURE_APP_ID, + clientSecret: AZURE_APP_KEY, + tenantId: AZURE_TENANT_ID, + subscriptionId: AZURE_SUBSCRIPTION_ID }] } ) { @@ -424,14 +424,14 @@ Mutations are requests that are intended to have side effects, such as creating > This mutation rotates the client secret on an existing Microsoft Azure account. - ``` + ```graphql mutation { cloudUpdateAccount( - accountId: + accountId: YOUR_ACCOUNT_ID accounts: { azure: { - linkedAccountId: , - clientSecret: + linkedAccountId: NR_LINKED_ACCOUNT_ID, + clientSecret: AZURE_SECRET_TOKEN } } ) { @@ -453,14 +453,14 @@ Mutations are requests that are intended to have side effects, such as creating > This mutation links a GCP project to the New Relic account. - ``` + ```graphql mutation { cloudLinkAccount( - accountId: , + accountId: YOUR_ACCOUNT_ID, accounts: { gcp: [{ - name: , - projectId: + name: PROVIDER_ACCOUNT_NAME, + projectId: GCP_PROJECT_ID }] } ) { @@ -482,18 +482,18 @@ Mutations are requests that are intended to have side effects, such as creating > This mutation allows you to rename one or more linked provider accounts. The `name` parameter is required, cannot be empty, and must be unique within your New Relic account. - ``` + ```graphql mutation { cloudRenameAccount( - accountId: , + accountId: YOUR_ACCOUNT_ID, accounts: [ { - id: , - name: + id: LINKED_CLOUD_ACCOUNT_ID_1, + name: PROVIDER_ACCOUNT_NAME }, { - id: , - name: + id: LINKED_CLOUD_ACCOUNT_ID_2, + name: PROVIDER_ACCOUNT_NAME } ] ) { @@ -512,15 +512,15 @@ Mutations are requests that are intended to have side effects, such as creating > This mutation allows you to enable the monitoring of one or more specific cloud integrations in an existing cloud account. With this mutation, New Relic records data for the enabled integration from the provider account. For each provider account you have access to different input parameters, matching each available service. - ``` + ```graphql mutation { cloudConfigureIntegration ( - accountId: , + accountId: YOUR_ACCOUNT_ID, integrations: { - : { - : [{ - linkedAccountId: , - + PROVIDER_SLUG : { + INTEGRATION_SLUG: [{ + linkedAccountId: LINKED_CLOUD_ACCOUNT_ID, + # other parameters }] } } @@ -549,15 +549,15 @@ Mutations are requests that are intended to have side effects, such as creating For the output of the operation, you can use [GraphQL fragments](https://graphql.org/learn/queries/#fragments) for integration specific configuration parameters. - ``` + ```graphql mutation { cloudConfigureIntegration ( - accountId: , + accountId: YOUR_ACCOUNT_ID, integrations: { - : { - : [ - { linkedAccountId: }, - { linkedAccountId: } + PROVIDER_SLUG : { + INTEGRATION_SLUG : [ + { linkedAccountId: LINKED_CLOUD_ACCOUNT_ID_1 }, + { linkedAccountId: LINKED_CLOUD_ACCOUNT_ID_2 } ] } } @@ -586,23 +586,23 @@ Mutations are requests that are intended to have side effects, such as creating For the output of the operation, you can use [GraphQL fragments](https://graphql.org/learn/queries/#fragments) to ask for integration specific configuration parameters. - ``` + ```graphql mutation { cloudConfigureIntegration ( - accountId: , + accountId: YOUR_ACCOUNT_ID, integrations: { - : { - : [ - { linkedAccountId: } + PROVIDER_SLUG_1: { + INTEGRATION_SLUG_1: [ + { linkedAccountId: LINKED_CLOUD_ACCOUNT_ID_1 } ] - : [ - { linkedAccountId: } + INTEGRATION_SLUG_2: [ + { linkedAccountId: LINKED_CLOUD_ACCOUNT_ID_2 } ] }, - : { - : [ - { linkedAccountId: }, - { linkedAccountId: } + PROVIDER_SLUG_2: { + INTEGRATION_SLUG_3: [ + { linkedAccountId: LINKED_CLOUD_ACCOUNT_ID_3}, + { linkedAccountId: LINKED_CLOUD_ACCOUNT_ID_4} ] } } @@ -631,17 +631,17 @@ Mutations are requests that are intended to have side effects, such as creating For parameters of a type list (for example, `awsRegion`) supply the full list. For the output of the operation, you can use [GraphQL fragments](https://graphql.org/learn/queries/#fragments) to ask for integration specific configuration parameters. - ``` + ```graphql mutation { cloudConfigureIntegration ( - accountId: , + accountId: YOUR_ACCOUNT_ID, integrations: { - : { - : [{ - linkedAccountId: , - metricsPollingInterval: , - : , - : , + PROVIDER_SLUG: { + INTEGRATION_SLUG: [{ + linkedAccountId: LINKED_CLOUD_ACCOUNT_ID, + metricsPollingInterval: NEW_POLLING_INTERVAL, + PARAMETER_1: VALUE_1, + PARAMETER_N: VALUE_N, }] } } @@ -655,8 +655,8 @@ Mutations are requests that are intended to have side effects, such as creating } ... on SqsIntegration { metricsPollingInterval, - , - + PARAMETER_1, + PARAMETER_N } } errors { @@ -674,14 +674,14 @@ Mutations are requests that are intended to have side effects, such as creating > This mutation allows you to disable an integration and stop data collection for the specific cloud integration. - ``` + ```graphql mutation { cloudDisableIntegration ( - accountId: , + accountId: YOUR_ACCOUNT_ID, integrations: { : { : [ - { linkedAccountId: } + { linkedAccountId: LINKED_CLOUD_ACCOUNT_ID } ] } } @@ -713,12 +713,12 @@ Mutations are requests that are intended to have side effects, such as creating This action can not be undone. However, you can link the account again, but account history will still be lost. - ``` + ```graphql mutation { cloudUnlinkAccount ( - accountId: , + accountId: YOUR_ACCOUNT_ID, accounts: { - { linkedAccountId: } + { linkedAccountId: LINKED_CLOUD_ACCOUNT_ID } } ) { unlinkedAccounts { @@ -748,10 +748,10 @@ To enable an AWS integration: > Send a query to fetch data about the account, specifically available providers and already created provider accounts: - ``` + ```graphql { actor { - account(id: ) { + account(id: YOUR_ACCOUNT_ID) { cloud { providers { id @@ -778,18 +778,18 @@ To enable an AWS integration: > Link an AWS provider account, if there is not one already linked or if you want to link another AWS account: - 1. Use your New Relic account identifier in the `` parameter. - 2. Provide a name for the provider account in the ``. + 1. Use your New Relic account identifier in the `YOUR_ACCOUNT_ID` parameter. + 2. Provide a name for the provider account in the `PROVIDER_ACCOUNT_NAME`. 3. Include the ARN of the AWS role used to fetch data from your AWS account. - ``` + ```graphql mutation { cloudLinkAccount( - accountId: , + accountId: YOUR_ACCOUNT_ID, accounts: { aws: [{ - name: , - arn: }] + name: PROVIDER_ACCOUNT_NAME, + arn: AWS_ROLE_ARN }] } ) { linkedAccounts { @@ -812,16 +812,16 @@ To enable an AWS integration: id="enable-sqs-integration" title="Enable the AWS SQS integration" > - Use your New Relic account ID in the `` parameter and the ID of the provider account in the `` parameter value. + Use your New Relic account ID in the `YOUR_ACCOUNT_ID` parameter and the ID of the provider account in the `LINKED_CLOUD_ACCOUNT_ID` parameter value. - ``` + ```graphql mutation { cloudConfigureIntegration ( - accountId: , + accountId: YOUR_ACCOUNT_ID, integrations: { aws: { sqs: [ - { linkedAccountId: } + { linkedAccountId: LINKED_CLOUD_ACCOUNT_ID } ] } } @@ -847,17 +847,23 @@ To enable an AWS integration: id="enable-sqs-multiple-provider-accounts" title="Enable integration in multiple provider accounts" > - If you have multiple accounts with the same provider account, you can enable the same integration in multiple provider accounts at the same time. Use your New Relic account ID in the `` parameter and the ID of the provider accounts in the `` parameter value. + If you have multiple accounts with the same provider account, you can enable the same integration in multiple provider accounts at the same time. Use your New Relic account ID in the `YOUR_ACCOUNT_ID` parameter and the ID of the provider accounts in the `LINKED_CLOUD_ACCOUNT_ID_N` parameter value. - ``` + ```graphql mutation { cloudConfigureIntegration ( - accountId: , + accountId: YOUR_ACCOUNT_ID, integrations: { aws: { sqs: [ - { linkedAccountId: }, - { linkedAccountId: , configuration_param_1: value_1, configuration_param_2: value_2 } + { + linkedAccountId: LINKED_CLOUD_ACCOUNT_ID_1 + }, + { + linkedAccountId: LINKED_CLOUD_ACCOUNT_ID_2, + configuration_param_1: value_1, + configuration_param_2: value_2 + } ] } } @@ -889,16 +895,19 @@ This example uses an [AWS SQS](/docs/integrations/amazon-integrations/aws-integr id="update-sqs-polling" title="Update the polling interval" > - To update the polling interval for an AWS SQS integration, use your New Relic account ID in the `` parameter and the `id` of the linked provider account in the `` parameter value: + To update the polling interval for an AWS SQS integration, use your New Relic account ID in the `YOUR_ACCOUNT_ID` parameter and the `id` of the linked provider account in the `LINKED_ACCOUNT_ID` parameter value: - ``` + ```graphql mutation { cloudConfigureIntegration( - accountId: , + accountId: YOUR_ACCOUNT_ID, integrations: { aws : { sqs: [ - { linkedAccountId: , metricsPollingInterval: 300 } + { + linkedAccountId: LINKED_CLOUD_ACCOUNT_ID, + metricsPollingInterval: 300 + } ] } } @@ -933,24 +942,20 @@ This example uses an [AWS SQS](/docs/integrations/amazon-integrations/aws-integr id="disable-sqs-scenario" title="Disable the SQS integration" > - Use your New Relic account identifier in the `` parameter and the ID of the linked cloud account the `` parameter value. + Use your New Relic account identifier in the `YOUR_ACCOUNT_ID` parameter and the ID of the linked cloud account the `LINKED_ACCOUNT_ID` parameter value. - ``` + ```graphql mutation { - cloudDisableIntegration ( - accountId: , + cloudDisableIntegration( + accountId: YOUR_ACCOUNT_ID integrations: { - aws: { - sqs: [ - { linkedAccountId: } - ] - } + aws: { sqs: [{ linkedAccountId: LINKED_CLOUD_ACCOUNT_ID }] } } ) { - disabledIntegrations { - id + disabledIntegrations { + id accountId - name + name } errors { type diff --git a/src/content/docs/apis/nerdgraph/examples/nerdgraph-concurrency-tutorial.mdx b/src/content/docs/apis/nerdgraph/examples/nerdgraph-concurrency-tutorial.mdx index e6f7ca45f3b..40937729724 100644 --- a/src/content/docs/apis/nerdgraph/examples/nerdgraph-concurrency-tutorial.mdx +++ b/src/content/docs/apis/nerdgraph/examples/nerdgraph-concurrency-tutorial.mdx @@ -14,34 +14,36 @@ New Relic's NerdGraph API enforces a limit of **25 concurrent requests per One way to handle concurrency is to use a worker pool. The below example uses the [async module](https://caolan.github.io/async/v3/docs.html#queue) to do so. It creates a queue that has a set concurrency execution limit, pushes requests as tasks onto that queue, and empties the queue once completeing all tasks. -```node -import got from 'got'; -import async from 'async'; +```js +import got from "got"; +import async from "async"; -const API_KEY = '' //GraphQL User Key -const MAX_CONCURRENCY = 25; //Maximum amount of requests in queue at a given time - -const GRAPH_API = 'https://api.newrelic.com/graphql'; -const HEADERS = { 'Content-Type': 'application/json', 'Api-Key': API_KEY }; +const API_KEY = "YOUR_GRAPHQL_USER_KEY"; // GraphQL User Key +const MAX_CONCURRENCY = 25; // Maximum amount of requests in queue at a given time +const GRAPH_API = "https://api.newrelic.com/graphql"; +const HEADERS = { "Content-Type": "application/json", "Api-Key": API_KEY }; async function main() { - let accounts = await getAccounts(); //All accounts to run a query against + let accounts = await getAccounts(); // All accounts to run a query against var allResults = []; //Queue initialization const q = async.queue(async (task, cb) => { - let result = await makeRequest(task.acct) - allResults.push({'transactionCount': result[0].count, 'account': task.acct.id}); + let result = await makeRequest(task.acct); + allResults.push({ + transactionCount: result[0].count, + account: task.acct.id, + }); cb(); }, MAX_CONCURRENCY); - //Push requests on to the queue (one for each account) - accounts.forEach(acct => { - q.push({acct: acct}); + // Push requests on to the queue (one for each account) + accounts.forEach((acct) => { + q.push({ acct: acct }); }); - await q.drain(); //Drain event listener when all tasks are complete + await q.drain(); // Drain event listener when all tasks are complete console.log(allResults); } @@ -49,53 +51,51 @@ async function main() { async function makeRequest(acct) { let nrql = `SELECT count(*) FROM Transaction`; let gql = `{ - actor { - account(id: ${acct.id}) { - nrql(query: "${nrql}", timeout: 90) { - results - } - } - } - }`; + actor { + account(id: ${acct.id}) { + nrql(query: "${nrql}", timeout: 90) { + results + } + } + } + }`; let opts = { url: GRAPH_API, headers: HEADERS, - json: {'query': gql, 'variables': {}} + json: { query: gql, variables: {} }, }; let response = await got.post(opts).json(); if (!response.errors) { return response.data.actor.account.nrql.results; } else { - console.log('Query Error'); + console.log("Query Error"); console.log(response.errors); } } async function getAccounts() { var q = `{ - actor { - accounts { - id - name - } - } - }` + actor { + accounts { + id + name + } + } + }`; var opts = { url: GRAPH_API, headers: HEADERS, - json: {'query': q, 'variables': {}} - } + json: { query: q, variables: {} }, + }; let resp = await got.post(opts).json(); return resp.data.actor.accounts; } - main(); - ``` ## Python @@ -107,35 +107,33 @@ You can also use Python by leveraging the following packages to handle asynchron Below sets a [Semaphore](https://docs.python.org/3/library/asyncio-sync.html?highlight=semaphore#asyncio.Semaphore) that manages the amount of concurrent simultaneous requests. It then uses `asyncio.gather()` to execute multiple co-routines concurrently and waits for their completion. -``` +```py import aiohttp import asyncio -API_KEY = '' +API_KEY = "YOUR_GRAPHQL_USER_KEY" MAX_CONCURRENCY = 25 -GRAPHQL_API = 'https://api.newrelic.com/graphql' -HEADERS = {'Content-Type': 'application/json', 'Api-Key': API_KEY} - +GRAPHQL_API = "https://api.newrelic.com/graphql" +HEADERS = {"Content-Type": "application/json", "Api-Key": API_KEY} async def main(): - #All accounts to run a query against + # All accounts to run a query against accounts = await get_accounts() # Semaphore for controlling concurrency limit = asyncio.Semaphore(MAX_CONCURRENCY) - #Add all accounts to run a query against + # Add all accounts to run a query against tasks = [send_request(acct, limit) for acct in accounts] - #Schedule all tasks to run concurrently + # Schedule all tasks to run concurrently allResults = await asyncio.gather(*tasks) print(allResults) - async def send_request(acct, limit): nrql = "SELECT count(*) FROM Transaction" - gql = f''' + gql = f""" {{ actor {{ account(id: {acct['id']}) {{ @@ -145,19 +143,22 @@ async def send_request(acct, limit): }} }} }} - ''' + """ async with limit: try: async with aiohttp.ClientSession() as session: - async with session.post(GRAPHQL_API, json={"query": gql, "variables":{}}, headers=HEADERS) as response: + async with session.post( + GRAPHQL_API, json={"query": gql, "variables": {}}, headers=HEADERS + ) as response: result = await response.json() - return {'transactionCount': result['data']['actor']['account']['nrql']['results'][0]['count'], 'account': acct['id']} + return { + "transactionCount": result["data"]["actor"]["account"]["nrql"]["results"][0]["count"],"account": acct["id"], + } except Exception as error: print("Query Error") raise error - async def get_accounts(): gql = """ { @@ -166,19 +167,19 @@ async def get_accounts(): id name } - } - } + } + } """ async with aiohttp.ClientSession() as session: - async with session.post(GRAPHQL_API, json={"query": gql, "variables":{}}, headers=HEADERS) as response: + async with session.post( + GRAPHQL_API, json={"query": gql, "variables": {}}, headers=HEADERS + ) as response: result = await response.json() - return result['data']['actor']['accounts'] - - -if __name__ == '__main__': - asyncio.run(main()) #Run event loop + return result["data"]["actor"]["accounts"] +if __name__ == "__main__": + asyncio.run(main()) # Run event loop ``` For more detail on NerdGraph limits, see [NerdGraph usage limits](/docs/apis/nerdgraph/nerdgraph-usage-limits). diff --git a/src/content/docs/apis/nerdgraph/examples/nerdgraph-dashboards.mdx b/src/content/docs/apis/nerdgraph/examples/nerdgraph-dashboards.mdx index 0962d4e63cd..0ab704f0c28 100644 --- a/src/content/docs/apis/nerdgraph/examples/nerdgraph-dashboards.mdx +++ b/src/content/docs/apis/nerdgraph/examples/nerdgraph-dashboards.mdx @@ -262,7 +262,7 @@ Here's an example of creating a cross-account dashboard: id="cross-account-dashboard" title="Dashboard with cross-account query" > - ```graphql + ```graphql lineHighlight=21,37,53 mutation { dashboardCreate( accountId: 1 @@ -283,7 +283,7 @@ Here's an example of creating a cross-account dashboard: legend: { enabled: true } nrqlQueries: [ { - accountIds: [1, 1606862, 2212585] + accountIds: [1, 1606862, 2212585] query: "SELECT count(*) FROM Transaction" } ] @@ -299,7 +299,7 @@ Here's an example of creating a cross-account dashboard: legend: { enabled: true } nrqlQueries: [ { - accountIds: [1, 1606862, 2212585] + accountIds: [1, 1606862, 2212585] query: "SELECT count(*) FROM Transaction FACET accountId()" } ] @@ -315,7 +315,7 @@ Here's an example of creating a cross-account dashboard: legend: { enabled: true } nrqlQueries: [ { - accountIds: [1, 1606862, 2212585] + accountIds: [1, 1606862, 2212585] query: "SELECT count(*) FROM Transaction FACET accountId() TIMESERIES" } ] @@ -565,18 +565,18 @@ All dashboard mutations offer a way to ask for errors when being executed. This id="errors-first-class" title="Errors as part of every mutation response" > - ``` + ```graphql mutation { - dashboardMutation(guid: "MY_EXISTING_DASHBOARD_GUID") { - mutationResult { - result - } - errors { - description - type - } + dashboardMutation(guid: "MY_EXISTING_DASHBOARD_GUID") { + mutationResult { + result + } + errors { + description + type } } + } ``` diff --git a/src/content/docs/apis/nerdgraph/examples/nerdgraph-synthetics-tutorial.mdx b/src/content/docs/apis/nerdgraph/examples/nerdgraph-synthetics-tutorial.mdx index bc4e47802f2..d891d45485d 100644 --- a/src/content/docs/apis/nerdgraph/examples/nerdgraph-synthetics-tutorial.mdx +++ b/src/content/docs/apis/nerdgraph/examples/nerdgraph-synthetics-tutorial.mdx @@ -57,7 +57,7 @@ Configure simple browser, scripted browser, and step monitors to use one or more > To identify a [private location](/docs/synthetics/synthetic-monitoring/private-locations/private-locations-overview-monitor-internal-sites-add-new-locations) in your scripts, use the private location's entity GUID. If the private location is configured to use [verified script execution](/docs/synthetics/synthetic-monitoring/private-locations/verified-script-execution-private-locations/), also include the `vsePassword` attribute. For example: - ``` + ```graphql locations: { private: { guid: LOCATION_ENTITY_GUID, @@ -68,7 +68,7 @@ Configure simple browser, scripted browser, and step monitors to use one or more [Public locations](/docs/synthetics/synthetic-monitoring/administration/synthetic-public-minion-ips/#location) use the location identifier without the AWS\_ prefix, for example: - ``` + ```graphql locations: { public: ["US_EAST_2", "US_WEST_1"] } @@ -193,7 +193,7 @@ Queries make requests to fetch data. To learn additional query capabilities avai > You can query your synthetic monitors to get current status information about your data or details about the monitor configuration. Many monitor configurations are surfaced as tags. - ``` + ```graphql { actor { entitySearch(query: "domain = 'SYNTH' AND type = 'MONITOR'") { @@ -223,7 +223,7 @@ Queries make requests to fetch data. To learn additional query capabilities avai > You're able to query your private locations: - ``` + ```graphql { actor { entitySearch(query: "domain = 'SYNTH' AND type = 'PRIVATE_LOCATION'") { @@ -250,7 +250,7 @@ Queries make requests to fetch data. To learn additional query capabilities avai > Query existing monitor downtimes. Configuration details are stored in tags. - ``` + ```graphql { actor { entitySearch(query: "domain = 'SYNTH' AND type = 'MONITOR_DOWNTIME'") { @@ -277,7 +277,7 @@ Queries make requests to fetch data. To learn additional query capabilities avai > Querying secure credentials lets you retrieve metadata only, but not the credential values themselves: - ``` + ```graphql { actor { entitySearch(query: "domain = 'SYNTH' AND type = 'SECURE_CRED'") { @@ -307,10 +307,10 @@ Queries make requests to fetch data. To learn additional query capabilities avai > Retrieve the script used in a scripted API or scripted browser monitor. Other monitor types will return an error. - ``` + ```graphql { actor { - account(id: YOUR_ACCOUNT_ID) { + account(id: ACCOUNT_ID) { synthetics { script(monitorGuid: "ENTITY_GUID") { text @@ -328,10 +328,10 @@ Queries make requests to fetch data. To learn additional query capabilities avai > Retrieve the steps configured for a step monitor. Other monitor types will return an error. - ``` + ```graphql { actor { - account(id: YOUR_ACCOUNT_ID) { + account(id: ACCOUNT_ID) { synthetics { steps(monitorGuid: "ENTITY_GUID") { ordinal @@ -351,7 +351,7 @@ Queries make requests to fetch data. To learn additional query capabilities avai > Retrieve the entity GUID for a synthetic monitor using the monitor ID. - ``` + ```graphql { actor { entitySearch( @@ -378,7 +378,7 @@ Queries make requests to fetch data. To learn additional query capabilities avai > Retrieve the status of all runtime upgrade tests for legacy runtime monitors. These tests populate the [runtime upgrades UI](/docs/synthetics/synthetic-monitoring/using-monitors/runtime-upgrade-ui/). The test result is stored in the `validationStatus` tag. If the upgrade test failed, the error message is available in the `validationError` tag. - ``` + ```graphql { actor { entitySearch(query: "domain = 'SYNTH' AND type = 'RUNTIME_VALIDATION'") { @@ -405,10 +405,12 @@ Queries make requests to fetch data. To learn additional query capabilities avai > Retrieve the status of a runtime upgrade test for a single legacy runtime monitor. These test results populate the [runtime upgrades UI](/docs/synthetics/synthetic-monitoring/using-monitors/runtime-upgrade-ui/). The test result is stored in the `validationStatus` tag. If the upgrade test failed, the error message is available in the `validationError` tag. - ``` + ```graphql { actor { - entitySearch(query: "domain = 'SYNTH' AND type = 'RUNTIME_VALIDATION' and domainId = 'MONITOR_ID'") { + entitySearch( + query: "domain = 'SYNTH' AND type = 'RUNTIME_VALIDATION' AND domainId = 'MONITOR_ID'" + ) { results { entities { accountId @@ -449,31 +451,26 @@ Below are some sample requests to automate the creation of your synthetic monito > Ping monitors check that your application is running. Here's an example for creating one in NerdGraph: - ``` + ```graphql mutation { - syntheticsCreateSimpleMonitor ( - accountId: YOUR_ACCOUNT_ID + syntheticsCreateSimpleMonitor( + accountId: ACCOUNT_ID monitor: { - locations: { - public: ["LOCATION_1", "LOCATION_2"] - }, - name: "YOUR_MONITOR_NAME", - period: PERIOD, - status: STATUS, - uri: "MONITORED_URI", + locations: { public: ["LOCATION_1", "LOCATION_2"] } + name: "YOUR_MONITOR_NAME" + period: PERIOD + status: STATUS + uri: "MONITORED_URI" advancedOptions: { - customHeaders: { - name: "HEADER_NAME", - value: "HEADER_VALUE" - }, - redirectIsFailure: REDIRECT_IS_FAILURE, - responseValidationText: "VALIDATION_TEXT", - shouldBypassHeadRequest: BYPASS_HEAD_REQUEST, + customHeaders: { name: "HEADER_NAME", value: "HEADER_VALUE" } + redirectIsFailure: REDIRECT_IS_FAILURE + responseValidationText: "VALIDATION_TEXT" + shouldBypassHeadRequest: BYPASS_HEAD_REQUEST useTlsValidation: TLS_VALIDATION - }, + } apdexTarget: APDEX_TARGET } - ) { + ) { errors { description type @@ -489,43 +486,39 @@ Below are some sample requests to automate the creation of your synthetic monito > Simple browser monitors use Chrome instances to mimic customer visits. Here's an example for creating one in NerdGraph: - ``` + ```graphql mutation { - syntheticsCreateSimpleBrowserMonitor ( - accountId: YOUR_ACCOUNT_ID, + syntheticsCreateSimpleBrowserMonitor( + accountId: ACCOUNT_ID monitor: { - browsers: [BROWSERS], - devices: [DEVICES], - locations: { - public: ["LOCATION_1", "LOCATION_2"] - }, - name: "YOUR_MONITOR_NAME", - period: PERIOD, + browsers: [BROWSERS] + devices: [DEVICES] + locations: { public: ["LOCATION_1", "LOCATION_2"] } + name: "YOUR_MONITOR_NAME" + period: PERIOD runtime: { - runtimeType: "RUNTIME_TYPE", - runtimeTypeVersion: "RUNTIME_TYPE_VERSION", + runtimeType: "RUNTIME_TYPE" + runtimeTypeVersion: "RUNTIME_TYPE_VERSION" scriptLanguage: "SCRIPT_LANGUAGE" } - status: STATUS, - uri: "MONITORED_URI", + status: STATUS + uri: "MONITORED_URI" advancedOptions: { - customHeaders: { - name: "HEADER_NAME", - value: "HEADER_VALUE" - }, - enableScreenshotOnFailureAndScript: ENABLE_SCREENSHOT, - responseValidationText: "VALIDATION_TEXT", + customHeaders: { name: "HEADER_NAME", value: "HEADER_VALUE" } + enableScreenshotOnFailureAndScript: ENABLE_SCREENSHOT + responseValidationText: "VALIDATION_TEXT" useTlsValidation: TLS_VALIDATION - }, + } apdexTarget: APDEX_TARGET - ) { + } + ) { errors { description type } } } - ``` + ``` [Scripted browser monitors](/docs/synthetics/synthetic-monitoring/scripting-monitors/introduction-scripted-browser-monitors) are more complex interactions with your pages and applications. Here's an example for creating one in NerdGraph: - ``` - mutation { - syntheticsCreateScriptBrowserMonitor ( - accountId: YOUR_ACCOUNT_ID, - monitor: { - browsers: [BROWSERS], - devices: [DEVICES], - locations: { - public: ["LOCATION_1", "LOCATION_2"] - }, - name: "MONITOR_NAME", - period: PERIOD, - runtime: { - runtimeType: "RUNTIME_TYPE", - runtimeTypeVersion: "RUNTIME_TYPE_VERSION", - scriptLanguage: "SCRIPT_LANGUAGE" - } - script: "SCRIPT_CONTENT", - status: STATUS, - advancedOptions: { - enableScreenshotOnFailureAndScript: ENABLE_SCREENSHOT - }, - apdexTarget: APDEX_TARGET - } - ) { - errors { - description - type + ```graphql + mutation { + syntheticsCreateScriptBrowserMonitor( + accountId: ACCOUNT_ID + monitor: { + browsers: [BROWSERS] + devices: [DEVICES] + locations: { public: ["LOCATION_1", "LOCATION_2"] } + name: "MONITOR_NAME" + period: PERIOD + runtime: { + runtimeType: "RUNTIME_TYPE" + runtimeTypeVersion: "RUNTIME_TYPE_VERSION" + scriptLanguage: "SCRIPT_LANGUAGE" } + script: "SCRIPT_CONTENT" + status: STATUS + advancedOptions: { enableScreenshotOnFailureAndScript: ENABLE_SCREENSHOT } + apdexTarget: APDEX_TARGET + } + ) { + errors { + description + type } } + } ``` @@ -574,32 +563,30 @@ Below are some sample requests to automate the creation of your synthetic monito > [Scripted API monitors](/docs/synthetics/synthetic-monitoring/scripting-monitors/write-synthetic-api-tests) check your API endpoints. Here's an example for creating one in NerdGraph: - ``` - mutation { - syntheticsCreateScriptApiMonitor ( - accountId: YOUR_ACCOUNT_ID, - monitor: { - locations: { - public: ["LOCATION_1", "LOCATION_2"] - }, - name: "YOUR_MONITOR_NAME", - period: PERIOD, - runtime: { - runtimeType: "RUNTIME_TYPE", - runtimeTypeVersion: "RUNTIME_TYPE_VERSION", - scriptLanguage: "SCRIPT_LANGUAGE" - } - script: "SCRIPT_CONTENT", - status: STATUS, - apdexTarget: APDEX_TARGET - } - ) { - errors { - description - type + ```graphql + mutation { + syntheticsCreateScriptApiMonitor( + accountId: ACCOUNT_ID + monitor: { + locations: { public: ["LOCATION_1", "LOCATION_2"] } + name: "YOUR_MONITOR_NAME" + period: PERIOD + runtime: { + runtimeType: "RUNTIME_TYPE" + runtimeTypeVersion: "RUNTIME_TYPE_VERSION" + scriptLanguage: "SCRIPT_LANGUAGE" } + script: "SCRIPT_CONTENT" + status: STATUS + apdexTarget: APDEX_TARGET + } + ) { + errors { + description + type } } + } ``` @@ -609,44 +596,42 @@ Below are some sample requests to automate the creation of your synthetic monito > Step monitors provide codeless multi-step browser based monitors. Here's an example for creating one in NerdGraph: - ``` + ```graphql mutation { - syntheticsCreateStepMonitor ( - accountId: NR_ACCOUNT_ID, - monitor: { - browsers: [BROWSERS], - devices: [DEVICES], - locations: { - public: ["LOCATION_1", "LOCATION_2"] - }, - name: "MONITOR_NAME", - period: PERIOD, - runtime: { - runtimeType: "RUNTIME_TYPE", - runtimeTypeVersion: "RUNTIME_TYPE_VERSION", - scriptLanguage: "SCRIPT_LANGUAGE" + syntheticsCreateStepMonitor( + accountId: ACCOUNT_ID + monitor: { + browsers: [BROWSERS] + devices: [DEVICES] + locations: { public: ["LOCATION_1", "LOCATION_2"] } + name: "MONITOR_NAME" + period: PERIOD + runtime: { + runtimeType: "RUNTIME_TYPE" + runtimeTypeVersion: "RUNTIME_TYPE_VERSION" + scriptLanguage: "SCRIPT_LANGUAGE" } - status: STATUS, - steps: [{ - ordinal: 0, - type: NAVIGATE, - values: ["MONITORED_URI"],["USER_AGENT"] - },{ - ordinal: STEP_NUMBER, - type: STEP_TYPE, - values: ["CONDITIONAL_TYPE","VALUE"] - }] - advancedOptions: { - enableScreenshotOnFailureAndScript: ENABLE_SCREENSHOT - }, - apdexTarget: APDEX_TARGET - } - ) { + status: STATUS + steps: [ + { + ordinal: 0, + type: NAVIGATE, + values: ["MONITORED_URI", "USER_AGENT"] } + { + ordinal: STEP_NUMBER + type: STEP_TYPE + values: ["CONDITIONAL_TYPE", "VALUE"] + } + ] + advancedOptions: { enableScreenshotOnFailureAndScript: ENABLE_SCREENSHOT } + apdexTarget: APDEX_TARGET + } + ) { errors { description type } - } + } } ``` @@ -657,28 +642,26 @@ Below are some sample requests to automate the creation of your synthetic monito > Set up monitors to notify you when your SSL certificates are about to expire. Here's an example for creating one in NerdGraph: - ``` - mutation { - syntheticsCreateCertCheckMonitor ( - accountId: YOUR_ACCOUNT_ID, - monitor: { - domain: "DOMAIN", - locations: { - public: ["LOCATION_1", "LOCATION_2"] - }, - name: "YOUR_MONITOR_NAME", - numberDaysToFailBeforeCertExpires: DAYS_UNTIL_EXPIRATION, - period: PERIOD, - status: STATUS, - apdexTarget: APDEX_TARGET - } - ) { - errors { - description - type - } + ```graphql + mutation { + syntheticsCreateCertCheckMonitor( + accountId: ACCOUNT_ID + monitor: { + domain: "DOMAIN" + locations: { public: ["LOCATION_1", "LOCATION_2"] } + name: "YOUR_MONITOR_NAME" + numberDaysToFailBeforeCertExpires: DAYS_UNTIL_EXPIRATION + period: PERIOD + status: STATUS + apdexTarget: APDEX_TARGET + } + ) { + errors { + description + type } } + } ``` @@ -688,32 +671,26 @@ Below are some sample requests to automate the creation of your synthetic monito > Broken links monitors check the links on a webpage for failure. Here's an example for creating one in NerdGraph: - ``` + ```graphql mutation { - syntheticsCreateBrokenLinksMonitor ( - accountId: YOUR_ACCOUNT_ID, + syntheticsCreateBrokenLinksMonitor( + accountId: ACCOUNT_ID monitor: { - locations: { - public: ["LOCATION_1", "LOCATION_2"] - }, - name: "YOUR_MONITOR_NAME", - period: PERIOD, - status: STATUS, - apdexTarget: APDEX_TARGET, - uri: "MONITOR_URI", - tags: { - key: "YOUR_TAG_NAME", - values: "TAG_VALUE" - } - } - ) { - errors { - description - type - } + locations: { public: ["LOCATION_1", "LOCATION_2"] } + name: "YOUR_MONITOR_NAME" + period: PERIOD + status: STATUS + apdexTarget: APDEX_TARGET + uri: "MONITOR_URI" + tags: { key: "YOUR_TAG_NAME", values: "TAG_VALUE" } + } + ) { + errors { + description + type + } } } - ``` @@ -733,28 +710,23 @@ While you can't change the monitor type after creating it, you can update its se > Use this to update your ping monitors: - ``` + ```graphql mutation { - syntheticsUpdateSimpleMonitor ( - guid: "ENTITY_GUID", + syntheticsUpdateSimpleMonitor( + guid: "ENTITY_GUID" monitor: { - locations: { - public: ["LOCATION_1", "LOCATION_2"] - }, - name: "YOUR_MONITOR_NAME", - period: PERIOD, - status: STATUS, - uri: "MONITORED_URI", + locations: { public: ["LOCATION_1", "LOCATION_2"] } + name: "YOUR_MONITOR_NAME" + period: PERIOD + status: STATUS + uri: "MONITORED_URI" advancedOptions: { - customHeaders: { - name: "HEADER_NAME", - value: "HEADER_VALUE" - }, - redirectIsFailure: REDIRECT_IS_FAILURE, - responseValidationText: "VALIDATION_TEXT", - shouldBypassHeadRequest: BYPASS_HEAD_REQUEST, + customHeaders: { name: "HEADER_NAME", value: "HEADER_VALUE" } + redirectIsFailure: REDIRECT_IS_FAILURE + responseValidationText: "VALIDATION_TEXT" + shouldBypassHeadRequest: BYPASS_HEAD_REQUEST useTlsValidation: TLS_VALIDATION - }, + } apdexTarget: APDEX_TARGET } ) { @@ -773,42 +745,38 @@ While you can't change the monitor type after creating it, you can update its se > To update a simple browser monitor (including the ability to upgrade the runtime version), use this: - ``` - mutation { - syntheticsUpdateSimpleBrowserMonitor ( - guid: ENTITY_GUID, - monitor: { - browsers: [BROWSERS], - devices: [DEVICES], - locations: { - public: ["LOCATION_1", "LOCATION_2"] - }, - name: "YOUR_MONITOR_NAME", - period: PERIOD, - runtime: { - runtimeType: "RUNTIME_TYPE", - runtimeTypeVersion: "RUNTIME_TYPE_VERSION", - scriptLanguage: "SCRIPT_LANGUAGE" - } - status: STATUS, - uri: "MONITORED_URI", - advancedOptions: { - customHeaders: { - name: "HEADER_NAME", - value: "HEADER_VALUE" - }, - enableScreenshotOnFailureAndScript: ENABLE_SCREENSHOT, - responseValidationText: "VALIDATION_TEXT", - useTlsValidation: TLS_VALIDATION - }, - apdexTarget: APDEX_TARGET - ) { - errors { - description - type + ```graphql + mutation { + syntheticsUpdateSimpleBrowserMonitor( + guid: ENTITY_GUID + monitor: { + browsers: [BROWSERS] + devices: [DEVICES] + locations: { public: ["LOCATION_1", "LOCATION_2"] } + name: "YOUR_MONITOR_NAME" + period: PERIOD + runtime: { + runtimeType: "RUNTIME_TYPE" + runtimeTypeVersion: "RUNTIME_TYPE_VERSION" + scriptLanguage: "SCRIPT_LANGUAGE" + } + status: STATUS + uri: "MONITORED_URI" + advancedOptions: { + customHeaders: { name: "HEADER_NAME", value: "HEADER_VALUE" } + enableScreenshotOnFailureAndScript: ENABLE_SCREENSHOT + responseValidationText: "VALIDATION_TEXT" + useTlsValidation: TLS_VALIDATION } + apdexTarget: APDEX_TARGET + } + ) { + errors { + description + type } } + } ``` @@ -818,37 +786,33 @@ While you can't change the monitor type after creating it, you can update its se > To update a scripted browser monitor (including the ability to upgrade the runtime version), use this: - ``` - mutation { - syntheticsUpdateScriptBrowserMonitor ( - guid: ENTITY_GUID, - monitor: { - browsers: [BROWSERS], - devices: [DEVICES], - locations: { - public: ["LOCATION_1", "LOCATION_2"] - }, - name: "MONITOR_NAME", - period: PERIOD, - runtime: { - runtimeType: "RUNTIME_TYPE", - runtimeTypeVersion: "RUNTIME_TYPE_VERSION", - scriptLanguage: "SCRIPT_LANGUAGE" - } - script: "SCRIPT_CONTENT", - status: STATUS, - advancedOptions: { - enableScreenshotOnFailureAndScript: ENABLE_SCREENSHOT - }, - apdexTarget: APDEX_TARGET - } - ) { - errors { - description - type + ```graphql + mutation { + syntheticsUpdateScriptBrowserMonitor( + guid: ENTITY_GUID + monitor: { + browsers: [BROWSERS] + devices: [DEVICES] + locations: { public: ["LOCATION_1", "LOCATION_2"] } + name: "MONITOR_NAME" + period: PERIOD + runtime: { + runtimeType: "RUNTIME_TYPE" + runtimeTypeVersion: "RUNTIME_TYPE_VERSION" + scriptLanguage: "SCRIPT_LANGUAGE" } + script: "SCRIPT_CONTENT" + status: STATUS + advancedOptions: { enableScreenshotOnFailureAndScript: ENABLE_SCREENSHOT } + apdexTarget: APDEX_TARGET + } + ) { + errors { + description + type } } + } ``` @@ -858,33 +822,30 @@ While you can't change the monitor type after creating it, you can update its se > To update a scripted API monitor (including the ability to upgrade the runtime version), use this: - ``` - mutation { - syntheticsUpdateScriptApiMonitor ( - guid: ENTITY_GUID, - monitor: { - locations: { - public: ["LOCATION_1", "LOCATION_2"] - }, - name: "YOUR_MONITOR_NAME", - period: PERIOD, - runtime: { - runtimeType: "RUNTIME_TYPE", - runtimeTypeVersion: "RUNTIME_TYPE_VERSION", - scriptLanguage: "SCRIPT_LANGUAGE" - } - script: "SCRIPT_CONTENT", - status: STATUS, - apdexTarget: APDEX_TARGET - } - ) { - errors { - description - type + ```graphql + mutation { + syntheticsUpdateScriptApiMonitor( + guid: ENTITY_GUID + monitor: { + locations: { public: ["LOCATION_1", "LOCATION_2"] } + name: "YOUR_MONITOR_NAME" + period: PERIOD + runtime: { + runtimeType: "RUNTIME_TYPE" + runtimeTypeVersion: "RUNTIME_TYPE_VERSION" + scriptLanguage: "SCRIPT_LANGUAGE" } + script: "SCRIPT_CONTENT" + status: STATUS + apdexTarget: APDEX_TARGET + } + ) { + errors { + description + type } } - + } ``` @@ -894,43 +855,42 @@ While you can't change the monitor type after creating it, you can update its se > Use this to update a step monitor: - ``` + ```graphql mutation { - syntheticsUpdateStepMonitor ( - guid: ENTITY_GUID, + syntheticsUpdateStepMonitor( + guid: ENTITY_GUID monitor: { - browsers: [BROWSERS], - devices: [DEVICES], - locations: { - public: ["LOCATION_1", "LOCATION_2"] - }, - name: "MONITOR_NAME", - period: PERIOD, + browsers: [BROWSERS] + devices: [DEVICES] + locations: { public: ["LOCATION_1", "LOCATION_2"] } + name: "MONITOR_NAME" + period: PERIOD runtime: { - runtimeType: "RUNTIME_TYPE", - runtimeTypeVersion: "RUNTIME_TYPE_VERSION", + runtimeType: "RUNTIME_TYPE" + runtimeTypeVersion: "RUNTIME_TYPE_VERSION" scriptLanguage: "SCRIPT_LANGUAGE" + } + status: STATUS + steps: [ + { + ordinal: 0, + type: NAVIGATE, + values: ["MONITORED_URI", "USER_AGENT"] } - status: STATUS, - steps: [{ - ordinal: 0, - type: NAVIGATE, - values: ["MONITORED_URI"],["USER_AGENT"] - },{ - ordinal: STEP_NUMBER, - type: STEP_TYPE, - values: ["VALUE_1","VALUE_2"] - }] - advancedOptions: { - enableScreenshotOnFailureAndScript: ENABLE_SCREENSHOT - }, + { + ordinal: STEP_NUMBER, + type: STEP_TYPE, + values: ["VALUE_1", "VALUE_2"] + } + ] + advancedOptions: { enableScreenshotOnFailureAndScript: ENABLE_SCREENSHOT } apdexTarget: APDEX_TARGET } ) { - errors { - description - type - } + errors { + description + type + } } } ``` @@ -942,28 +902,26 @@ While you can't change the monitor type after creating it, you can update its se > Use this to update a certificate check monitor: - ``` - mutation { - syntheticsUpdateCertCheckMonitor ( - guid: ENTITY_GUID, - monitor: { - domain: "DOMAIN", - locations: { - public: ["LOCATION_1", "LOCATION_2"] - }, - name: "YOUR_MONITOR_NAME", - numberDaysToFailBeforeCertExpires: DAYS_UNTIL_EXPIRATION, - period: PERIOD, - status: STATUS, - apdexTarget: APDEX_TARGET - } - ) { - errors { - description - type - } + ```graphql + mutation { + syntheticsUpdateCertCheckMonitor( + guid: ENTITY_GUID + monitor: { + domain: "DOMAIN" + locations: { public: ["LOCATION_1", "LOCATION_2"] } + name: "YOUR_MONITOR_NAME" + numberDaysToFailBeforeCertExpires: DAYS_UNTIL_EXPIRATION + period: PERIOD + status: STATUS + apdexTarget: APDEX_TARGET + } + ) { + errors { + description + type } } + } ``` @@ -973,29 +931,27 @@ While you can't change the monitor type after creating it, you can update its se > Use this to update a broken links monitor: - ``` + ```graphql mutation { - syntheticsUpdateBrokenLinksMonitor ( - guid: ENTITY_GUID, + syntheticsUpdateBrokenLinksMonitor( + guid: ENTITY_GUID monitor: { - locations: { - public: ["LOCATION_1", "LOCATION_2"] - }, - name: "YOUR_MONITOR_NAME", - period: PERIOD, - status: STATUS, - apdexTarget: APDEX_TARGET, - uri: "MONITOR_URI", - tags: { + locations: { public: ["LOCATION_1", "LOCATION_2"] } + name: "YOUR_MONITOR_NAME" + period: PERIOD + status: STATUS + apdexTarget: APDEX_TARGET + uri: "MONITOR_URI" + tags: { key: "YOUR_TAG_NAME", - values: "TAG_VALUE" - } - } - ) { - errors { - description - type + values: "TAG_VALUE" } + } + ) { + errors { + description + type + } } } ``` @@ -1012,10 +968,10 @@ While you can't change the monitor type after creating it, you can update its se Check out [optional-fields](#optional-fields) for additional details on runtime settings. - ``` + ```graphql mutation { syntheticsUpdateScriptBrowserMonitor ( - guid: "", + guid: "ENTITY_GUID", monitor: { runtime: { runtimeType: "RUNTIME_TYPE", @@ -1044,10 +1000,10 @@ While you can't change the monitor type after creating it, you can update its se Check out [optional-fields](#optional-fields) for additional details on runtime settings. - ``` + ```graphql mutation { syntheticsUpdateScriptBrowserMonitor ( - guid: "", + guid: "ENTITY_GUID", monitor: { runtime: { runtimeType: "", @@ -1077,11 +1033,11 @@ Use these scripts to delete your monitors: > Delete a monitor using the monitor entity GUID. - ``` + ```graphql mutation { syntheticsDeleteMonitor ( guid: "ENTITY_GUID" - ) { + ) { deletedGuid } } @@ -1098,10 +1054,10 @@ A [private location](/docs/synthetics/synthetic-monitoring/private-locations/pri id="private-location" title="Create a private location" > - ``` - mutation{ + ```graphql + mutation { syntheticsCreatePrivateLocation ( - accountId: NR_ACCOUNT_ID, + accountId: ACCOUNT_ID, name: "PrivateLocationName", description: "Optional description", verifiedScriptExecution: false @@ -1120,18 +1076,18 @@ A [private location](/docs/synthetics/synthetic-monitoring/private-locations/pri id="private-location" title="Update a private location" > - ``` + ```graphql mutation { syntheticsUpdatePrivateLocation ( - guid: YOUR_ENTITY_GUID, + guid: ENTITY_GUID, description: "EnterYourDescription", verifiedScriptExecution: true ) { - description - verifiedScriptExecution - errors { description - type + verifiedScriptExecution + errors { + description + type } } } @@ -1142,11 +1098,11 @@ A [private location](/docs/synthetics/synthetic-monitoring/private-locations/pri id="delete-private locations" title="Delete a private location" > - ``` + ```graphql mutation { syntheticsDeletePrivateLocation ( - guid: YOUR_ENTITY_GUID - ) { + guid: ENTITY_GUID + ) { errors { description type @@ -1162,11 +1118,11 @@ A [private location](/docs/synthetics/synthetic-monitoring/private-locations/pri > If you need to clear an unwieldy backlog, use this: - ``` + ```graphql mutation { syntheticsPurgePrivateLocationQueue ( - guid: YOUR_ENTITY_GUID - ) { + guid: ENTITY_GUID + ) { errors { description type @@ -1186,14 +1142,14 @@ You use [secure credentials](/docs/synthetics/synthetic-monitoring/using-monitor id="secure-credential" title="Create a secure credential" > - ``` + ```graphql mutation { syntheticsCreateSecureCredential ( - accountId: YOUR_ENTITY_GUID, + accountId: ACCOUNT_ID, description: "YourOptionalDescription", key: SECURE_CREDENTIAL_NAME, value: SECURE_CREDENTIAL_VALUE - ) { + ) { errors { description } @@ -1206,13 +1162,14 @@ You use [secure credentials](/docs/synthetics/synthetic-monitoring/using-monitor id="update-secure" title="Update a secure credential" > - ``` + ```graphql mutation { - syntheticsUpdateSecureCredential ( - accountId: YOUR_ACCOUNT_ID, - description: "YourOptionalDescription", - key: SECURE_CREDENTIAL_NAME, - value: SECURE_CREDENTIAL_VALUE) { + syntheticsUpdateSecureCredential( + accountId: ACCOUNT_ID + description: "YourOptionalDescription" + key: SECURE_CREDENTIAL_NAME + value: SECURE_CREDENTIAL_VALUE + ) { createdAt lastUpdate errors { @@ -1227,12 +1184,12 @@ You use [secure credentials](/docs/synthetics/synthetic-monitoring/using-monitor id="secure-credential" title="Delete a secure credential" > - ``` + ```graphql mutation { syntheticsDeleteSecureCredential ( - accountId: YOUR_ACCOUNT_ID, + accountId: ACCOUNT_ID, key: SECURE_CREDENTIAL_NAME - ) { + ) { errors { description } @@ -1251,13 +1208,13 @@ Monitor downtimes let you specify times that your synthetics should stop running id="create-once-downtime" title="Create a monitor downtime that runs once" > - ``` + ```graphql mutation { syntheticsCreateOnceMonitorDowntime ( - accountId: NR_ACCOUNT_ID, + accountId: ACCOUNT_ID, name: "MonitorDowntimeName", monitorGuids: ["OptionalMonitorEntityGuid", "OptionalMonitorEntityGuid"], - timezone: "Timezone", + timezone: "TIMEZONE", startTime: "yyyy-MM-ddTHH:mm:ss", endTime: "yyyy-MM-ddTHH:mm:ss" ) { @@ -1277,13 +1234,13 @@ Monitor downtimes let you specify times that your synthetics should stop running id="create-daily-downtime" title="Create a monitor downtime that runs daily" > - ``` + ```graphql mutation { syntheticsCreateDailyMonitorDowntime ( - accountId: NR_ACCOUNT_ID, + accountId: ACCOUNT_ID, name: "MonitorDowntimeName", monitorGuids: ["OptionalMonitorEntityGuid", "AnotherOptionalMonitorEntityGuid"], - timezone: "Timezone", + timezone: "TIMEZONE", startTime: "yyyy-MM-ddTHH:mm:ss", endTime: "yyyy-MM-ddTHH:mm:ss", endRepeat: { @@ -1311,13 +1268,13 @@ Monitor downtimes let you specify times that your synthetics should stop running id="create-weekly-downtime" title="Create a monitor downtime that runs weekly" > - ``` + ```graphql mutation { syntheticsCreateWeeklyMonitorDowntime ( - accountId: NR_ACCOUNT_ID, + accountId: ACCOUNT_ID, name: "MonitorDowntimeName", monitorGuids: ["OptionalMonitorEntityGuid", "AnotherOptionalMonitorEntityGuid"], - timezone: "Timezone", + timezone: "TIMEZONE", startTime: "yyyy-MM-ddTHH:mm:ss", endTime: "yyyy-MM-ddTHH:mm:ss", endRepeat: { @@ -1347,13 +1304,13 @@ Monitor downtimes let you specify times that your synthetics should stop running id="create-monthly-downtime" title="Create a monitor downtime that runs monthly" > - ``` + ```graphql mutation { syntheticsCreateMonthlyMonitorDowntime ( - accountId: NR_ACCOUNT_ID, + accountId: ACCOUNT_ID, name: "MonitorDowntimeName", monitorGuids: ["OptionalMonitorEntityGuid", "AnotherOptionalMonitorEntityGuid"], - timezone: "Timezone", + timezone: "TIMEZONE", startTime: "yyyy-MM-ddTHH:mm:ss", endTime: "yyyy-MM-ddTHH:mm:ss", endRepeat: { @@ -1395,19 +1352,19 @@ Monitor downtimes let you specify times that your synthetics should stop running id="update-downtime" title="Update a monitor downtime" > - ``` + ```graphql mutation { syntheticsEditMonitorDowntime ( guid: "MonitorDowntimeEntityGuid", name: "MONITOR_DOWNTIME_NAME", monitorGuids: ["OptionalMonitorEntityGuid", "AnotherOptionalMonitorEntityGuid"], once: { - timezone: "Timezone", + timezone: "TIMEZONE", startTime: "yyyy-MM-ddTHH:mm:ss", endTime: "yyyy-MM-ddTHH:mm:ss" }, daily: { - timezone: "Timezone", + timezone: "TIMEZONE", startTime: "yyyy-MM-ddTHH:mm:ss", endTime: "yyyy-MM-ddTHH:mm:ss", endRepeat: { @@ -1416,7 +1373,7 @@ Monitor downtimes let you specify times that your synthetics should stop running } }, weekly: { - timezone: "Timezone", + timezone: "TIMEZONE", startTime: "yyyy-MM-ddTHH:mm:ss", endTime: "yyyy-MM-ddTHH:mm:ss", endRepeat: { @@ -1426,7 +1383,7 @@ Monitor downtimes let you specify times that your synthetics should stop running maintenanceDays: [WeekDaysEnums] }, monthly: { - timezone: "Timezone", + timezone: "TIMEZONE", startTime: "yyyy-MM-ddTHH:mm:ss", endTime: "yyyy-MM-ddTHH:mm:ss", endRepeat: { @@ -1469,7 +1426,7 @@ Monitor downtimes let you specify times that your synthetics should stop running id="delete-downtime" title="Delete a monitor downtime" > - ``` + ```graphql mutation { syntheticsDeleteMonitorDowntime ( guid: DOWNTIME_ENTITY_GUID 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 7c6f1425847..8469ab8b972 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 @@ -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.405.0 + * Latest verified compatible version: 3.7.405.5 * 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 - 3.7.411.17 + 3.7.411.20 @@ -803,7 +803,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co 10.0.0 - 9.0.0 + 9.0.1 @@ -860,7 +860,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co * Minimum supported version: 5.0 - * Latest verified compatible version: 9.2.3 + * Latest verified compatible version: 9.2.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.76 + * Latest verified compatible version: 3.7.400.79 @@ -1604,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.405.2 + * Latest verified compatible version: 3.7.405.5 * Minimum agent version required: 10.33.0 @@ -1765,7 +1765,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co 10.23.0 - 3.7.411.17 + 3.7.411.20 @@ -1858,7 +1858,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co 9.7.0 - 9.0.0 + 9.0.1 @@ -1978,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.76 + * Latest verified compatible version: 3.7.400.79 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 db83a3af978..a8fe343f9cf 100644 --- a/src/content/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx +++ b/src/content/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx @@ -276,11 +276,12 @@ version. | --- | --- | --- | --- | | `@apollo/gateway` | 2.3.0 | 2.9.3 | `@newrelic/apollo-server-plugin@1.0.0` | | `@apollo/server` | 4.0.0 | 4.11.3 | `@newrelic/apollo-server-plugin@2.1.0` | -| `@aws-sdk/client-bedrock-runtime` | 3.474.0 | 3.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/client-bedrock-runtime` | 3.474.0 | 3.730.0 | 11.13.0 | +| `@aws-sdk/client-dynamodb` | 3.0.0 | 3.730.0 | 8.7.1 | +| `@aws-sdk/client-redshift-data` | 3.474.0 | 3.730.0 | 12.12.0 | +| `@aws-sdk/client-sns` | 3.0.0 | 3.730.0 | 8.7.1 | +| `@aws-sdk/client-sqs` | 3.0.0 | 3.730.0 | 8.7.1 | +| `@aws-sdk/lib-dynamodb` | 3.377.0 | 3.730.0 | 8.7.1 | | `@aws-sdk/smithy-client` | 3.47.0 | 3.374.0 | 8.7.1 | | `@elastic/elasticsearch` | 7.16.0 | 8.17.0 | 11.9.0 | | `@grpc/grpc-js` | 1.4.0 | 1.12.5 | 8.17.0 | diff --git a/src/content/docs/change-tracking/change-tracking-view-analyze.mdx b/src/content/docs/change-tracking/change-tracking-view-analyze.mdx index 5928a88d96f..23624d7c527 100644 --- a/src/content/docs/change-tracking/change-tracking-view-analyze.mdx +++ b/src/content/docs/change-tracking/change-tracking-view-analyze.mdx @@ -33,6 +33,11 @@ Before you jump into the details here about how to view and analyze the impact o If you land on a dashboard or entity summary page and don't see the tracked change you're expecting, check your time picker selection. It might be outside the window you are looking at. + + + If you are still not seeing the markers that you're expecting, please review the ["How markers are selected for inclusion on a chart"](#nrql-markers-inclusion) section for more details on how change tracking events are selected for inclusion based on the chart's query. + + * **Entity sidebar:** To see a table of changes, click on **Change tracking** for any entity that has recorded changes. It features a time range selector and table filtering and sorting options. Use these to narrow the field of changes or to find a specific change. Note that you may need to adjust the selected time range on this page to see tracked changes. Also, by default the table will only lazy load up to 2,000 changes. Keep this in mind as you're filtering, searching, and adjusting your time range. * **New Relic & Detection:** If your change is related to an issue, you'll see it listed in the **Root Cause Analysis** section of the **Issues** page. @@ -242,6 +247,57 @@ Try these examples or create your own queries: +#### How markers are selected for inclusion on a chart [#nrql-markers-inclusion] + +Most charts are driven by a NRQL query, which you can view by clicking the three dots in the tile's top-right corner. When working with a query, follow these steps to determine which markers to include on the resulting chart: + +1. Derive the set of relevant entities that includes both entities mentioned directly in the query and related entities. Refer to the section below for more details. +2. Paint a marker for each change-tracking event recorded for this set of entities, plot a marker, with a limit of up to 5,000 events. + +The entities relevant to the chart are derived from the NRQL query based on the following logic: + * Entities that are directly specified in the query for the chart using either an `IN` or `=` operator (e.g. queries with an `WHERE entity.guid IN ('MTE2NjAxMzJ8QVBNfEFQUExJQ0FUSU9OfDEyMDk1MjY5')` clause). While we use `entity.guid` as an example, other properties may also be used to explicitly designate entities for the query. They are: + * `entity.guid` + * `entityGuid` + * `entity.name` + * `entityName` + * `appName` + * `service.name` + * Entities that are [related](https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/core-concepts/what-entity-new-relic/#related-entities) to entities specified via the method above. Only the following relationship-types are considered: + * `CALLS` + * `SERVES` + * `IS` + * `CONTAINS` + * `HOSTS` + +Please be advised that __NRQL queries for charts are currently scoped to a single account__. This means that if you specify entity-GUIDs belonging to multiple accounts, only markers from a single account will be visualized. + +For example, let's consider that the query for your chart looks like the following: +``` +FROM Transaction SELECT count(*) WHERE entityGuid IN ('MTE2NjAxMzJ8QVBNfEFQUExJQ0FUSU9OfDg0MTY1OTI','MTEwNjI2OTl8QVBNfEFQUExJQ0FUSU9OfDg5ODEwMDk5') TIMESERIES MAX SINCE 2 weeks AGO +``` +Markers from both entities will show up on the chart. Additionally, markers from related-entities will also be included on the chart. To determine the list of related-entities, you can run a GraphQL query similar to the example below: +``` +{ + actor { + entity(guid: "MTEwNjI2OTl8QVBNfEFQUExJQ0FUSU9OfDg5ODEwMDk5") { + relatedEntities( + filter: {relationshipTypes: {include: [CALLS, SERVES, IS, CONTAINS, HOSTS]}} + ) { + results { + type + source { + guid + } + target { + guid + } + } + } + } + } +} +``` + ### NerdGraph (GraphQL) [#graphql-markers] Try these NerdGraph queries in our [NerdGraph explorer](/docs/apis/nerdgraph/get-started/nerdgraph-explorer#find): diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-albnlb-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-albnlb-monitoring-integration.mdx index b789b69c83a..fa39474d1ad 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-albnlb-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-albnlb-monitoring-integration.mdx @@ -20,7 +20,7 @@ freshnessValidatedDate: never [Amazon Application Load Balancing](http://docs.aws.amazon.com/elasticloadbalancing/latest/application/introduction.html) (ALB) distributes incoming application traffic across multiple targets, such as EC2 instances, in multiple availability zones. [Amazon Network Load Balancer](http://docs.aws.amazon.com/elasticloadbalancing/latest/network/introduction.html) (NLB) distributes incoming traffic across multiple targets, such as Amazon EC2 instances. -[New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your AWS ALB/NLB data to New Relic products. This document explains how to activate this integration and describes the data that can be captured. +[New Relic infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your AWS ALB/NLB data to New Relic products. This document explains how to activate this integration and describes the data that can be captured. New Relic also offers an [integration for Amazon's Elastic Load Balancing (ELB) service](/docs/infrastructure/amazon-integrations/amazon-integrations/aws-elb-monitoring-integration). diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-api-gateway-v1-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-api-gateway-v1-monitoring-integration.mdx index 234991efbaf..3651d9bd411 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-api-gateway-v1-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-api-gateway-v1-monitoring-integration.mdx @@ -16,7 +16,7 @@ freshnessValidatedDate: never Enable the [AWS CloudWatch Metric Streams integration](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-metric-stream/) to monitor all CloudWatch metrics from your AWS services, including custom namespaces. Individual integrations are no longer our recommended option. -[New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your Amazon API Gateway data to New Relic. This document explains how to activate this integration and describes the data that can be reported. +[New Relic infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your Amazon API Gateway data to New Relic. This document explains how to activate this integration and describes the data that can be reported. API Gateway v1 metrics are available exclusively through the API polling integration for Amazon API Gateway. [API Gateway v2 metrics](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-api-gateway-v2-monitoring-integration) are streamed through CloudWatch Metric Streams. diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-api-gateway-v2-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-api-gateway-v2-monitoring-integration.mdx index 07e26199c95..2a213b3160d 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-api-gateway-v2-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-api-gateway-v2-monitoring-integration.mdx @@ -8,7 +8,7 @@ metaDescription: "New Relic's AWS API Gateway v2 monitoring integration: what da freshnessValidatedDate: 2024-02-01 --- -[New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) now include an integration for AWS API Gateway v2, sending its metrics data to New Relic. +[New Relic infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) now include an integration for AWS API Gateway v2, sending its metrics data to New Relic. This document explains the integration's features, how to activate it, and what data you can report. @@ -34,7 +34,7 @@ This New Relic infrastructure integration collects the following Amazon API Gate - Metric + Metric diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-apprunner.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-apprunner.mdx index b5585c22cba..0d9d0d211ac 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-apprunner.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-apprunner.mdx @@ -8,7 +8,7 @@ metaDescription: "New Relic's Amazon App Runner monitoring integration: what dat freshnessValidatedDate: never --- -[New Relic's infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your Amazon App Runner data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your Amazon App Runner data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features [#features] @@ -40,12 +40,12 @@ To find your integration data: - Metric (min, max, average) + Metric (min, max, average) - Unit + Unit @@ -62,7 +62,7 @@ To find your integration data: - count + count @@ -73,12 +73,12 @@ To find your integration data: - `4xxStatusResponses` + `4xxStatusResponses` - count + count @@ -93,7 +93,7 @@ To find your integration data: - count + count @@ -108,7 +108,7 @@ To find your integration data: - percentage + percentage @@ -123,7 +123,7 @@ To find your integration data: - percentage + percentage @@ -138,7 +138,7 @@ To find your integration data: - ms + ms @@ -153,7 +153,7 @@ To find your integration data: - count + count diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-auto-scaling-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-auto-scaling-monitoring-integration.mdx index 92931c59dab..26dd32663bf 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-auto-scaling-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-auto-scaling-monitoring-integration.mdx @@ -17,7 +17,7 @@ freshnessValidatedDate: never The [AWS Auto Scaling](https://aws.amazon.com/autoscaling/) service allows launching or terminating Amazon EC2 instances automatically. It helps dynamically adapt Amazon EC2 capacity based on user-defined policies, schedules, and health checks. -[New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an AWS Auto Scaling integration that reports data about groups from your Auto Scaling service to New Relic products. This document explains how to activate this integration and describes the data that can be reported. +[New Relic infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) include an AWS Auto Scaling integration that reports data about groups from your Auto Scaling service to New Relic products. This document explains how to activate this integration and describes the data that can be reported. ## Activate integration [#activate] diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-billing-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-billing-monitoring-integration.mdx index 2c7f4501ed0..8150d6b1947 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-billing-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-billing-monitoring-integration.mdx @@ -15,7 +15,7 @@ redirects: freshnessValidatedDate: never --- -[New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your AWS Billing data to New Relic. This document explains how to activate this integration and describes the data that can be reported. +[New Relic infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your AWS Billing data to New Relic. This document explains how to activate this integration and describes the data that can be reported. ## Features [#features] @@ -111,11 +111,11 @@ Details for these types of billing data and how to query them are below: SELECT latest(`provider.budgetType`) as 'Budget Type', max(`provider.actualAmount`) as 'Actual Amount', max(`provider.limitAmount`) as 'Budget Limit', - latest(`provider.forecastedAmount`) as 'Forecast' - FROM FinanceSample - WHERE provider='BillingBudget' - AND providerAccountId = 'NEW_RELIC_ID_FOR_YOUR_CLOUD_ACCOUNT' - FACET `provider.budgetName` + latest(`provider.forecastedAmount`) as 'Forecast' + FROM FinanceSample + WHERE provider='BillingBudget' + AND providerAccountId = 'NEW_RELIC_ID_FOR_YOUR_CLOUD_ACCOUNT' + FACET `provider.budgetName` SINCE 1 day ago ``` @@ -137,12 +137,12 @@ Details for these types of billing data and how to query them are below: **NRQL example**: To group providers by service names, run the following NRQL query: ``` - SELECT latest(`provider.estimatedCharges.Maximum`) - FROM FinanceSample - WHERE provider='BillingServiceCost' - AND providerAccountId = 'NEW_RELIC_ID_FOR_YOUR_CLOUD_ACCOUNT' - SINCE 1 day ago - FACET `provider.serviceName` + SELECT latest(`provider.estimatedCharges.Maximum`) + FROM FinanceSample + WHERE provider='BillingServiceCost' + AND providerAccountId = 'NEW_RELIC_ID_FOR_YOUR_CLOUD_ACCOUNT' + SINCE 1 day ago + FACET `provider.serviceName` LIMIT 20 ``` @@ -160,12 +160,12 @@ Details for these types of billing data and how to query them are below: **NRQL example**: To group providers by account names, run the following NRQL query: ``` - SELECT latest(`provider.estimatedCharges.Maximum`) - FROM FinanceSample - WHERE provider='BillingAccountCost' - AND providerAccountId = 'NEW_RELIC_ID_FOR_YOUR_CLOUD_ACCOUNT' - SINCE 1 day ago - FACET `provider.accountId` + SELECT latest(`provider.estimatedCharges.Maximum`) + FROM FinanceSample + WHERE provider='BillingAccountCost' + AND providerAccountId = 'NEW_RELIC_ID_FOR_YOUR_CLOUD_ACCOUNT' + SINCE 1 day ago + FACET `provider.accountId` LIMIT 20 ``` @@ -183,11 +183,11 @@ Details for these types of billing data and how to query them are below: **NRQL example**: To understand the cost split of AWS services for a particular AWS account ID, run the following NRQL query: ``` - SELECT latest(`provider.estimatedCharges.Maximum`) - FROM FinanceSample - WHERE provider='BillingAccountServiceCost' - AND providerAccountId = 'NEW_RELIC_ID_FOR_YOUR_CLOUD_ACCOUNT' - SINCE 1 day ago + SELECT latest(`provider.estimatedCharges.Maximum`) + FROM FinanceSample + WHERE provider='BillingAccountServiceCost' + AND providerAccountId = 'NEW_RELIC_ID_FOR_YOUR_CLOUD_ACCOUNT' + SINCE 1 day ago FACET `provider.serviceName` LIMIT 100 ``` @@ -195,13 +195,13 @@ Details for these types of billing data and how to query them are below: **NRQL example**: To understand the cost split of AWS accounts for your AWS EC2 service, run the following NRQL query: ``` - SELECT latest(`provider.estimatedCharges.Maximum`) - FROM FinanceSample - WHERE provider='BillingAccountServiceCost' - AND providerAccountId = 'NEW_RELIC_ID_FOR_YOUR_CLOUD_ACCOUNT' - AND `provider.serviceName`='AmazonEC2' - FACET `provider.accountId` - SINCE 1 day ago + SELECT latest(`provider.estimatedCharges.Maximum`) + FROM FinanceSample + WHERE provider='BillingAccountServiceCost' + AND providerAccountId = 'NEW_RELIC_ID_FOR_YOUR_CLOUD_ACCOUNT' + AND `provider.serviceName`='AmazonEC2' + FACET `provider.accountId` + SINCE 1 day ago LIMIT 100 ``` diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-chatbot-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-chatbot-monitoring-integration.mdx index 052ed829a23..973e5b0108c 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-chatbot-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-chatbot-monitoring-integration.mdx @@ -8,7 +8,7 @@ metaDescription: "New Relic's Amazon Chatbot integration: what data it reports, freshnessValidatedDate: never --- -[New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) now include an integration for AWS Chatbot, sending its metrics data to New Relic. +[New Relic infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) now include an integration for AWS Chatbot, sending its metrics data to New Relic. This document explains the integration's features, how to activate it, and what data can be reported. @@ -36,12 +36,12 @@ This New Relic infrastructure integration collects the following Amazon Chatbot - Metric (min, max, average, count, sum) + Metric (min, max, average, count, sum) - Unit + Unit @@ -68,7 +68,7 @@ This New Relic infrastructure integration collects the following Amazon Chatbot - `EventsProcessed` + `EventsProcessed` @@ -83,7 +83,7 @@ This New Relic infrastructure integration collects the following Amazon Chatbot - `UnsupportedEvents` + `UnsupportedEvents` @@ -98,7 +98,7 @@ This New Relic infrastructure integration collects the following Amazon Chatbot - `MessageDeliverySuccess` + `MessageDeliverySuccess` @@ -113,7 +113,7 @@ This New Relic infrastructure integration collects the following Amazon Chatbot - `MessageDeliveryFailure` + `MessageDeliveryFailure` diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-cloudfront-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-cloudfront-monitoring-integration.mdx index b8e89c4d854..580395bc25b 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-cloudfront-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-cloudfront-monitoring-integration.mdx @@ -17,7 +17,7 @@ freshnessValidatedDate: never Enable the [AWS CloudWatch Metric Streams integration](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-metric-stream/) to monitor all CloudWatch metrics from your AWS services, including custom namespaces. Individual integrations are no longer our recommended option. -[New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting Amazon CloudFront service data to New Relic. This document explains how to activate this integration and describes the data that can be reported. +[New Relic infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting Amazon CloudFront service data to New Relic. This document explains how to activate this integration and describes the data that can be reported. ## Features [#features] diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-cloudtrail-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-cloudtrail-monitoring-integration.mdx index 826e33e70f0..f07a242ecae 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-cloudtrail-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-cloudtrail-monitoring-integration.mdx @@ -11,7 +11,7 @@ redirects: freshnessValidatedDate: never --- -[New Relic integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your AWS CloudTrail events to New Relic. This document explains how to activate this integration and describes the data that can be reported. +[New Relic integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your AWS CloudTrail events to New Relic. This document explains how to activate this integration and describes the data that can be reported. ## Features @@ -179,8 +179,8 @@ You can use New Relic to run queries of AWS CloudTrail data, and optionally use Query for a count of failed API calls, aggregated by the AWS service that the request was made to: ``` - SELECT count(*) from InfrastructureEvent WHERE provider = 'CloudTrail' - AND cloudTrailEventType = 'AwsApiCall' + SELECT count(*) from InfrastructureEvent WHERE provider = 'CloudTrail' + AND cloudTrailEventType = 'AwsApiCall' FACET eventSource ``` @@ -192,8 +192,8 @@ You can use New Relic to run queries of AWS CloudTrail data, and optionally use Query to find all console login errors: ``` - SELECT * from InfrastructureEvent WHERE provider = 'CloudTrail' - AND cloudTrailEventType = 'AwsConsoleSignIn' + SELECT * from InfrastructureEvent WHERE provider = 'CloudTrail' + AND cloudTrailEventType = 'AwsConsoleSignIn' AND errorMessage IS NOT NULL ``` diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-connect-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-connect-monitoring-integration.mdx index b7783c614d5..70b0d279534 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-connect-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-connect-monitoring-integration.mdx @@ -14,7 +14,7 @@ freshnessValidatedDate: never Enable the [AWS CloudWatch Metric Streams integration](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-metric-stream/) to monitor all CloudWatch metrics from your AWS services, including custom namespaces. Individual integrations are no longer our recommended option. -[New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your AWS Connect data to New Relic. Here we explain how to activate the integration and what data it collects. +[New Relic infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your AWS Connect data to New Relic. Here we explain how to activate the integration and what data it collects. ## Activate integration [#activate] diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-dynamodb-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-dynamodb-monitoring-integration.mdx index e3dc0037f2e..ea6742f0e8b 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-dynamodb-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-dynamodb-monitoring-integration.mdx @@ -17,7 +17,7 @@ freshnessValidatedDate: never Enable the [AWS CloudWatch Metric Streams integration](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-metric-stream/) to monitor all CloudWatch metrics from your AWS services, including custom namespaces. Individual integrations are no longer our recommended option. -[New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting Amazon DynamoDB data to New Relic. This document explains how to activate this integration and describes the data that can be reported. +[New Relic infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting Amazon DynamoDB data to New Relic. This document explains how to activate this integration and describes the data that can be reported. ## Features diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-ebs-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-ebs-monitoring-integration.mdx index 22f65acf6c1..b1658fddb07 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-ebs-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-ebs-monitoring-integration.mdx @@ -17,7 +17,7 @@ freshnessValidatedDate: never Enable the [AWS CloudWatch Metric Streams integration](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-metric-stream/) to monitor all CloudWatch metrics from your AWS services, including custom namespaces. Individual integrations are no longer our recommended option. -[New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an Amazon EBS integration for reporting your EBS data to New Relic. Here we explain how to activate our integration and what data can be reported. +[New Relic infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) include an Amazon EBS integration for reporting your EBS data to New Relic. Here we explain how to activate our integration and what data can be reported. ## Features diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-ec2-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-ec2-monitoring-integration.mdx index 698d61e9a4a..38e9a4dc420 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-ec2-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-ec2-monitoring-integration.mdx @@ -19,7 +19,7 @@ freshnessValidatedDate: never Enable the [AWS CloudWatch Metric Streams integration](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-metric-stream/) to monitor all CloudWatch metrics from your AWS services, including custom namespaces. Individual integrations are no longer our recommended option. -[New Relic infrastructure monitoring integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an Amazon Elastic Compute Cloud (EC2) integration for reporting your EC2 metadata to New Relic. This document explains the integration's features, how to activate it, and what data can be reported. +[New Relic infrastructure monitoring integrations](/docs/infrastructure/introduction-infra-monitoring) include an Amazon Elastic Compute Cloud (EC2) integration for reporting your EC2 metadata to New Relic. This document explains the integration's features, how to activate it, and what data can be reported. ## Features [#about] diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-efs-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-efs-monitoring-integration.mdx index b6bb579f1a7..9a774747bb3 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-efs-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-efs-monitoring-integration.mdx @@ -16,7 +16,7 @@ freshnessValidatedDate: never Enable the [AWS CloudWatch Metric Streams integration](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-metric-stream/) to monitor all CloudWatch metrics from your AWS services, including custom namespaces. Individual integrations are no longer our recommended option. -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an Amazon EFS integration for reporting your EFS data to New Relic. This document explains the integration's features, how to activate it, and what data can be reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an Amazon EFS integration for reporting your EFS data to New Relic. This document explains the integration's features, how to activate it, and what data can be reported. ## Features [#features] diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-elastic-beanstalk-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-elastic-beanstalk-monitoring-integration.mdx index b3e9b480be8..671171189d6 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-elastic-beanstalk-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-elastic-beanstalk-monitoring-integration.mdx @@ -19,7 +19,7 @@ freshnessValidatedDate: never Enable the [AWS CloudWatch Metric Streams integration](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-metric-stream/) to monitor all CloudWatch metrics from your AWS services, including custom namespaces. Individual integrations are no longer our recommended option. -[New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an AWS [Elastic Beanstalk](https://aws.amazon.com/elasticbeanstalk) integration for reporting your Beanstalk data to New Relic. This document explains the integration's features, how to activate it, and what data can be reported. +[New Relic infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) include an AWS [Elastic Beanstalk](https://aws.amazon.com/elasticbeanstalk) integration for reporting your Beanstalk data to New Relic. This document explains the integration's features, how to activate it, and what data can be reported. AWS Elastic Beanstalk is a dynamic service that allows easy deployment and scalability for your applications. The "application" in AWS Beanstalk is the environment. An "application" can have several environments associated with it. diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-elasticache-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-elasticache-monitoring-integration.mdx index abfa572c241..cd56ecb3f80 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-elasticache-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-elasticache-monitoring-integration.mdx @@ -18,7 +18,7 @@ freshnessValidatedDate: never Enable the [AWS CloudWatch Metric Streams integration](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-metric-stream/) to monitor all CloudWatch metrics from your AWS services, including custom namespaces. Individual integrations are no longer our recommended option. -[New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your Amazon ElastiCache data to New Relic. This document explains how the integration works and what data can be reported. +[New Relic infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your Amazon ElastiCache data to New Relic. This document explains how the integration works and what data can be reported. ## Features [#features] diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-elasticsearch-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-elasticsearch-monitoring-integration.mdx index 96bdd45bfd5..1d07b61eb59 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-elasticsearch-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-elasticsearch-monitoring-integration.mdx @@ -17,7 +17,7 @@ freshnessValidatedDate: never Enable the [AWS CloudWatch Metric Streams integration](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-metric-stream/) to monitor all CloudWatch metrics from your AWS services, including custom namespaces. Individual integrations are no longer our recommended option. -[New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting Amazon Elasticsearch data to New Relic. This document explains the integration's features, how to activate it, and what data can be reported. +[New Relic infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting Amazon Elasticsearch data to New Relic. This document explains the integration's features, how to activate it, and what data can be reported. ## Features [#features] diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-elb-classic-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-elb-classic-monitoring-integration.mdx index 567cc914c62..e7e51ed8590 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-elb-classic-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-elb-classic-monitoring-integration.mdx @@ -18,7 +18,7 @@ freshnessValidatedDate: never Enable the [AWS CloudWatch Metric Streams integration](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-metric-stream/) to monitor all CloudWatch metrics from your AWS services, including custom namespaces. Individual integrations are no longer our recommended option. -[New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an Amazon Elastic Classic Load Balancing (ELB) integration for reporting Classic ELB data to New Relic. This document explains the integration's features, how to activate it, and what data can be reported. +[New Relic infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) include an Amazon Elastic Classic Load Balancing (ELB) integration for reporting Classic ELB data to New Relic. This document explains the integration's features, how to activate it, and what data can be reported. ## Features [#features] diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-elemental-mediaconvert-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-elemental-mediaconvert-monitoring-integration.mdx index e764c99cf01..845563087c8 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-elemental-mediaconvert-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-elemental-mediaconvert-monitoring-integration.mdx @@ -15,7 +15,7 @@ freshnessValidatedDate: never Enable the [AWS CloudWatch Metric Streams integration](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-metric-stream/) to monitor all CloudWatch metrics from your AWS services, including custom namespaces. Individual integrations are no longer our recommended option. -[New Relic includes an integration](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) for reporting your AWS Elemental MediaConvert data to our platform. Here we explain how to activate the integration and what data it collects. +[New Relic includes an integration](/docs/infrastructure/introduction-infra-monitoring) for reporting your AWS Elemental MediaConvert data to our platform. Here we explain how to activate the integration and what data it collects. ## Activate the integration [#activate] diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-elemental-mediatailor-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-elemental-mediatailor-monitoring-integration.mdx index 2db7310f3bb..4c744749bda 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-elemental-mediatailor-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-elemental-mediatailor-monitoring-integration.mdx @@ -8,7 +8,7 @@ metaDescription: "New Relic's AWS Elemental MediaTailor integration: what data i freshnessValidatedDate: 2023-10-04 --- -[New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) now include an integration for AWS Elemental MediaTailor, sending its metric data to New Relic. +[New Relic infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) now include an integration for AWS Elemental MediaTailor, sending its metric data to New Relic. This document explains the integration's features, how to activate it, and what data can be reported. @@ -36,12 +36,12 @@ All imported data has one dimension: `ConfigurationName` - Metric (min, max, average, count, sum) + Metric (min, max, average, count, sum) - Unit + Unit diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-emr-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-emr-monitoring-integration.mdx index 1be7353f2f8..8f6a4758efb 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-emr-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-emr-monitoring-integration.mdx @@ -16,7 +16,7 @@ freshnessValidatedDate: never Enable the [AWS CloudWatch Metric Streams integration](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-metric-stream/) to monitor all CloudWatch metrics from your AWS services, including custom namespaces. Individual integrations are no longer our recommended option. -[New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Amazon EMR (Elastic MapReduce)](https://aws.amazon.com/emr/) data to New Relic. This document explains how to activate this integration and describes the data that can be reported. +[New Relic infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Amazon EMR (Elastic MapReduce)](https://aws.amazon.com/emr/) data to New Relic. This document explains how to activate this integration and describes the data that can be reported. ## Features [#features] diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-health-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-health-monitoring-integration.mdx index 26870caa70c..eaae4a58761 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-health-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-health-monitoring-integration.mdx @@ -12,7 +12,7 @@ redirects: freshnessValidatedDate: never --- -[New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your AWS Health data to New Relic. This document explains how to activate this integration and describes the data that can be reported. +[New Relic infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your AWS Health data to New Relic. This document explains how to activate this integration and describes the data that can be reported. ## Features [#features] diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-iam-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-iam-monitoring-integration.mdx index 92d24ca237b..ec77f1dc8f9 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-iam-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-iam-monitoring-integration.mdx @@ -17,7 +17,7 @@ freshnessValidatedDate: never Enable the [AWS CloudWatch Metric Streams integration](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-metric-stream/) to monitor all CloudWatch metrics from your AWS services, including custom namespaces. Individual integrations are no longer our recommended option. -[New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an AWS Identity and Access Management (IAM) integration for reporting your IAM data to New Relic. This document explains the integration's features, how to activate it, and what data can be reported. +[New Relic infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) include an AWS Identity and Access Management (IAM) integration for reporting your IAM data to New Relic. This document explains the integration's features, how to activate it, and what data can be reported. ## Features [#features] diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-iot-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-iot-monitoring-integration.mdx index e2b65fcf4be..3e3f0f6a44e 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-iot-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-iot-monitoring-integration.mdx @@ -16,7 +16,7 @@ freshnessValidatedDate: never Enable the [AWS CloudWatch Metric Streams integration](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-metric-stream/) to monitor all CloudWatch metrics from your AWS services, including custom namespaces. Individual integrations are no longer our recommended option. -New Relic offers an [integration](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) for reporting your AWS IoT [metric data](/docs/telemetry-data-platform/understand-data/new-relic-data-types/#metrics-new-relic). +New Relic offers an [integration](/docs/infrastructure/introduction-infra-monitoring) for reporting your AWS IoT [metric data](/docs/telemetry-data-platform/understand-data/new-relic-data-types/#metrics-new-relic). [AWS IoT](https://docs.aws.amazon.com/iot/latest/developerguide/what-is-aws-iot.html) is a service that provides communication between Internet-connected devices and the AWS Cloud. It also collects and stores telemetry data. With the AWS IoT Infrastructure integration, you can access these features: diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-iot-twinmaker-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-iot-twinmaker-integration.mdx index ce0981b89ec..a16a6acc93a 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-iot-twinmaker-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-iot-twinmaker-integration.mdx @@ -8,7 +8,7 @@ metaDescription: "New Relic's Amazon IoT Twinmaker integration: what data it rep freshnessValidatedDate: never --- -[New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) now include an integration for AWS IoT Twinmaker that sends its metrics data to New Relic. This document explains the integration's features, how to activate it, and what data it can reported. +[New Relic infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) now include an integration for AWS IoT Twinmaker that sends its metrics data to New Relic. This document explains the integration's features, how to activate it, and what data it can reported. ## Features @@ -26,12 +26,12 @@ This New Relic infrastructure integration collects the following Amazon WorkMail - Metric (min, max, average, count, sum) + Metric (min, max, average, count, sum) - Unit + Unit diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-kinesis-data-analytics-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-kinesis-data-analytics-monitoring-integration.mdx index fca8afc8597..a671b24c716 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-kinesis-data-analytics-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-kinesis-data-analytics-monitoring-integration.mdx @@ -16,7 +16,7 @@ freshnessValidatedDate: never Enable the [AWS CloudWatch Metric Streams integration](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-metric-stream/) to monitor all CloudWatch metrics from your AWS services, including custom namespaces. Individual integrations are no longer our recommended option. -Our [infrastructure monitoring integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your AWS Kinesis Data Analytics data to our products. Read on to learn more about how to activate the integration and what data it collects. +Our [infrastructure monitoring integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your AWS Kinesis Data Analytics data to our products. Read on to learn more about how to activate the integration and what data it collects. ## Activate integration [#activate] diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-kinesis-data-firehose-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-kinesis-data-firehose-monitoring-integration.mdx index 679f4ae1d2c..f67cfbe5745 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-kinesis-data-firehose-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-kinesis-data-firehose-monitoring-integration.mdx @@ -20,7 +20,7 @@ freshnessValidatedDate: never Enable the [AWS CloudWatch Metric Streams integration](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-metric-stream/) to monitor all CloudWatch metrics from your AWS services, including custom namespaces. Individual integrations are no longer our recommended option. -[New Relic](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) includes an integration for collecting your Amazon Kinesis Data Firehose data. This document explains how to activate this integration and describes the data that can be reported. +[New Relic](/docs/infrastructure/introduction-infra-monitoring) includes an integration for collecting your Amazon Kinesis Data Firehose data. This document explains how to activate this integration and describes the data that can be reported. ## Features [#features] diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-kinesis-data-streams-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-kinesis-data-streams-monitoring-integration.mdx index b7e9f22bf82..7408c808d3a 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-kinesis-data-streams-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-kinesis-data-streams-monitoring-integration.mdx @@ -19,7 +19,7 @@ freshnessValidatedDate: never Enable the [AWS CloudWatch Metric Streams integration](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-metric-stream/) to monitor all CloudWatch metrics from your AWS services, including custom namespaces. Individual integrations are no longer our recommended option. -[New Relic](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) includes an integration for monitoring Amazon Kinesis Data Streams. This document explains how to activate the integration and describes the data that can be reported. +[New Relic](/docs/infrastructure/introduction-infra-monitoring) includes an integration for monitoring Amazon Kinesis Data Streams. This document explains how to activate the integration and describes the data that can be reported. ## Features [#features] diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-lex-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-lex-monitoring-integration.mdx index 96c5f957c84..6e08507bfc3 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-lex-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-lex-monitoring-integration.mdx @@ -13,7 +13,7 @@ redirects: freshnessValidatedDate: never --- -[New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an Amazon Lex integration for reporting your Lex data to New Relic. Here we explain how to activate our integration and what data can be reported. +[New Relic infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) include an Amazon Lex integration for reporting your Lex data to New Relic. Here we explain how to activate our integration and what data can be reported. Enable the [AWS CloudWatch Metric Streams integration](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-metric-stream/) to monitor all CloudWatch metrics from your AWS services, including custom namespaces. Individual integrations are no longer our recommended option. diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-neptune-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-neptune-monitoring-integration.mdx index a48391f544e..d1bd1b6327d 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-neptune-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-neptune-monitoring-integration.mdx @@ -15,7 +15,7 @@ freshnessValidatedDate: never Enable the [AWS CloudWatch Metric Streams integration](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-metric-stream/) to monitor all CloudWatch metrics from your AWS services, including custom namespaces. Individual integrations are no longer our recommended option. -[New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your Amazon Neptune data to New Relic. This document explains how to activate this integration and describes the data that can be reported. +[New Relic infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your Amazon Neptune data to New Relic. This document explains how to activate this integration and describes the data that can be reported. ## Activate integration [#activate] diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-polly-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-polly-monitoring-integration.mdx index 1fbb32ab71e..22e1c78320c 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-polly-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-polly-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "The New Relic Amazon Polly integration: what data it reports, freshnessValidatedDate: never --- -[New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for Amazon Polly that reports your Polly metrics to New Relic. +[New Relic infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for Amazon Polly that reports your Polly metrics to New Relic. ## Features [#features] @@ -24,12 +24,12 @@ Data from this integration is attached to the `Metric` data type. To find this d - Metric (min, max, average, count, sum) + Metric (min, max, average, count, sum) - Unit + Unit @@ -56,7 +56,7 @@ Data from this integration is attached to the `Metric` data type. To find this d - `ResponseLattency` + `ResponseLattency` @@ -71,7 +71,7 @@ Data from this integration is attached to the `Metric` data type. To find this d - `5XXCount` + `5XXCount` @@ -86,7 +86,7 @@ Data from this integration is attached to the `Metric` data type. To find this d - `2XXCount` + `2XXCount` @@ -101,7 +101,7 @@ Data from this integration is attached to the `Metric` data type. To find this d - `4XXCount` + `4XXCount` diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-rds-enhanced-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-rds-enhanced-monitoring-integration.mdx index 33f1c09cf99..4deef4973c5 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-rds-enhanced-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-rds-enhanced-monitoring-integration.mdx @@ -12,7 +12,7 @@ redirects: freshnessValidatedDate: never --- -[New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for collecting [enhanced Amazon RDS data](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_Monitoring.OS.html); this supplements the basic [New Relic RDS integration](/docs/infrastructure/amazon-integrations/amazon-integrations/aws-rds-monitoring-integration) with real-time metrics about the operating system the database instance runs on. +[New Relic infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for collecting [enhanced Amazon RDS data](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_Monitoring.OS.html); this supplements the basic [New Relic RDS integration](/docs/infrastructure/amazon-integrations/amazon-integrations/aws-rds-monitoring-integration) with real-time metrics about the operating system the database instance runs on. ## Features [#features] diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-rds-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-rds-monitoring-integration.mdx index 405ee5bad56..5ae513dfb04 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-rds-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-rds-monitoring-integration.mdx @@ -17,7 +17,7 @@ freshnessValidatedDate: never Enable the [AWS CloudWatch Metric Streams integration](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-metric-stream/) to monitor all CloudWatch metrics from your AWS services, including custom namespaces. Individual integrations are no longer our recommended option. -[New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your Amazon Web Services RDS data to New Relic. This document explains how to activate this integration and describes the data that can be reported. +[New Relic infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your Amazon Web Services RDS data to New Relic. This document explains how to activate this integration and describes the data that can be reported. New Relic also offers an [integration for enhanced RDS monitoring](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-rds-enhanced-monitoring-integration). diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-redshift-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-redshift-integration.mdx index 4990d35483d..0fc1979e240 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-redshift-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-redshift-integration.mdx @@ -16,7 +16,7 @@ freshnessValidatedDate: never Enable the [AWS CloudWatch Metric Streams integration](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-metric-stream/) to monitor all CloudWatch metrics from your AWS services, including custom namespaces. Individual integrations are no longer our recommended option. -[New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your Amazon Redshift data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your Amazon Redshift data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features [#features] diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-rekognition-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-rekognition-monitoring-integration.mdx index 792fac2ac50..ea9f2c0d669 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-rekognition-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-rekognition-monitoring-integration.mdx @@ -13,7 +13,7 @@ redirects: freshnessValidatedDate: 2023-06-12 --- -[New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an Amazon Rekognition integration for reporting your Rekognition data to New Relic. Here, we explain how to activate our integration and what data can be reported. +[New Relic infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) include an Amazon Rekognition integration for reporting your Rekognition data to New Relic. Here, we explain how to activate our integration and what data can be reported. Enable the [AWS CloudWatch Metric Streams integration](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-metric-stream/) to monitor all CloudWatch metrics from your AWS services, including custom namespaces. Individual integrations are no longer our recommended option. diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-route-53-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-route-53-monitoring-integration.mdx index 26e8c409284..c9204b316df 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-route-53-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-route-53-monitoring-integration.mdx @@ -19,7 +19,7 @@ freshnessValidatedDate: never Enable the [AWS CloudWatch Metric Streams integration](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-metric-stream/) to monitor all CloudWatch metrics from your AWS services, including custom namespaces. Individual integrations are no longer our recommended option. -[New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your Amazon Route 53 data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your Amazon Route 53 data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features [#features] diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-route53-resolver-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-route53-resolver-monitoring-integration.mdx index b4020882911..93cefafbfe1 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-route53-resolver-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-route53-resolver-monitoring-integration.mdx @@ -15,7 +15,7 @@ freshnessValidatedDate: never Enable the [AWS CloudWatch Metric Streams integration](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-metric-stream/) to monitor all CloudWatch metrics from your AWS services, including custom namespaces. Individual integrations are no longer our recommended option. -[New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your AWS Route53 Resolver data to our. Here we explain how to activate the integration and what data it collects. +[New Relic infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your AWS Route53 Resolver data to our. Here we explain how to activate the integration and what data it collects. ## Activate integration [#activate] diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-s3-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-s3-monitoring-integration.mdx index 4140d50b677..1a49a3d55f3 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-s3-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-s3-monitoring-integration.mdx @@ -17,7 +17,7 @@ freshnessValidatedDate: never Enable the [AWS CloudWatch Metric Streams integration](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-metric-stream/) to monitor all CloudWatch metrics from your AWS services, including custom namespaces. Individual integrations are no longer our recommended option. -[New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your Amazon S3 data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your Amazon S3 data to New Relic. This document explains how to activate the integration and describes the data reported. AWS states that [S3 CloudWatch metrics are provided on a best-effort](https://docs.aws.amazon.com/AmazonS3/latest/userguide/metrics-dimensions.html) basis and may not always be current. If the CloudWatch metrics are delayed over 48 hours at collection, [New Relic cannot ingest them](https://docs.newrelic.com/docs/data-apis/ingest-apis/metric-api/metric-api-limits-restricted-attributes/). diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-s3-storagelens-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-s3-storagelens-monitoring-integration.mdx index b7e33fe3393..81cbf261d1d 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-s3-storagelens-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-s3-storagelens-monitoring-integration.mdx @@ -18,7 +18,7 @@ freshnessValidatedDate: never Enable the [AWS CloudWatch Metric Streams integration](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-metric-stream/) to monitor all CloudWatch metrics from your AWS services, including custom namespaces. Individual integrations are no longer our recommended option. -[New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your Amazon S3 data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your Amazon S3 data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features [#features] diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-security-lake-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-security-lake-monitoring-integration.mdx index ae3b18245b1..b1a22a1c6f6 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-security-lake-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-security-lake-monitoring-integration.mdx @@ -8,7 +8,7 @@ metaDescription: "The New Relic Amazon Security Lake integration: what data it r freshnessValidatedDate: never --- -[New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for AWS Security Lake, allowing you to send your security log data to New Relic. +[New Relic infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for AWS Security Lake, allowing you to send your security log data to New Relic. Collect and send telemetry data to New Relic from [Security Lake](https://aws.amazon.com/security-lake/) using our integration. You can use this integration to monitor your services, query incoming data, and build dashboards to observe everything at a glance. @@ -56,7 +56,7 @@ Here's an overview of the steps you'll be doing: - Value + Value @@ -69,14 +69,14 @@ Here's an overview of the steps you'll be doing: - S3 + S3 - `Account ID` + `Account ID` @@ -101,7 +101,7 @@ Here's an overview of the steps you'll be doing: - SQS queue + SQS queue diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-sns-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-sns-monitoring-integration.mdx index 780fc9f46c4..5bf842d56e2 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-sns-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-sns-monitoring-integration.mdx @@ -17,7 +17,7 @@ freshnessValidatedDate: never Enable the [AWS CloudWatch Metric Streams integration](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-metric-stream/) to monitor all CloudWatch metrics from your AWS services, including custom namespaces. Individual integrations are no longer our recommended option. -[Our infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your Amazon Web Services Simple Notification Service (SNS) data to New Relic. This document explains how to activate the integration and describes the data reported. +[Our infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your Amazon Web Services Simple Notification Service (SNS) data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features [#features] diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-textract-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-textract-monitoring-integration.mdx index 0342a3bb46d..681c478242e 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-textract-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-textract-monitoring-integration.mdx @@ -8,7 +8,7 @@ metaDescription: "New Relic's Amazon Textract integration: what data it reports, freshnessValidatedDate: never --- -[New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) now include an integration for AWS Textract, sending its metrics data to New Relic. +[New Relic infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) now include an integration for AWS Textract, sending its metrics data to New Relic. This document explains the integration's features, how to activate it, and what data can be reported. @@ -30,12 +30,12 @@ Data from this integration is attached to the `Metric` data type. To find your i - Metric (min, max, average, count, sum) + Metric (min, max, average, count, sum) - Unit + Unit @@ -48,7 +48,7 @@ Data from this integration is attached to the `Metric` data type. To find your i - `ResponseTime` + `ResponseTime` @@ -63,7 +63,7 @@ Data from this integration is attached to the `Metric` data type. To find your i - `ServerErrorCount` + `ServerErrorCount` @@ -78,7 +78,7 @@ Data from this integration is attached to the `Metric` data type. To find your i - `SuccessfulRequestCount` + `SuccessfulRequestCount` @@ -93,7 +93,7 @@ Data from this integration is attached to the `Metric` data type. To find your i - `ThrottledCount` + `ThrottledCount` @@ -108,7 +108,7 @@ Data from this integration is attached to the `Metric` data type. To find your i - `UserErrorCount` + `UserErrorCount` diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-transcribe-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-transcribe-monitoring-integration.mdx index d6af68a120b..c7fa9186c9f 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-transcribe-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-transcribe-monitoring-integration.mdx @@ -8,7 +8,7 @@ metaDescription: "The New Relic Amazon Transcribe integration: what data it repo freshnessValidatedDate: never --- -[New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for [Amazon Transcribe](https://aws.amazon.com/transcribe) that reports your Transcribe metrics to New Relic. +[New Relic infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for [Amazon Transcribe](https://aws.amazon.com/transcribe) that reports your Transcribe metrics to New Relic. ## Features [#features] @@ -30,12 +30,12 @@ This New Relic infrastructure integration collects the following Amazon Transcri - Metric (min, max, average, count, sum) + Metric (min, max, average, count, sum) - Unit + Unit @@ -62,7 +62,7 @@ This New Relic infrastructure integration collects the following Amazon Transcri - `SuccessfulRequestCount` + `SuccessfulRequestCount` @@ -77,7 +77,7 @@ This New Relic infrastructure integration collects the following Amazon Transcri - `SyncServerErrorCount` + `SyncServerErrorCount` @@ -92,7 +92,7 @@ This New Relic infrastructure integration collects the following Amazon Transcri - `SyncUserErrorCount` + `SyncUserErrorCount` @@ -107,7 +107,7 @@ This New Relic infrastructure integration collects the following Amazon Transcri - `ThrottledCount` + `ThrottledCount` @@ -122,7 +122,7 @@ This New Relic infrastructure integration collects the following Amazon Transcri - `LimitExceededCount` + `LimitExceededCount` @@ -137,7 +137,7 @@ This New Relic infrastructure integration collects the following Amazon Transcri - `AsyncUserErrorCount` + `AsyncUserErrorCount` @@ -152,7 +152,7 @@ This New Relic infrastructure integration collects the following Amazon Transcri - `AsyncServerErrorCount` + `AsyncServerErrorCount` @@ -167,7 +167,7 @@ This New Relic infrastructure integration collects the following Amazon Transcri - `AudioDurationTime` + `AudioDurationTime` diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-translate-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-translate-monitoring-integration.mdx index e59c02bb884..414da538773 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-translate-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-translate-monitoring-integration.mdx @@ -8,7 +8,7 @@ metaDescription: "New Relic's Amazon Translate integration: what data it reports freshnessValidatedDate: never --- -[New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) now include an integration for AWS Translate, sending its metrics data to New Relic. +[New Relic infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) now include an integration for AWS Translate, sending its metrics data to New Relic. This document explains the integration's features, how to activate it, and what data can be reported. @@ -33,12 +33,12 @@ To find your integration's metrics, go to **[one.newrelic.com > All capabil - Metric (min, max, average, count, sum) + Metric (min, max, average, count, sum) - Unit + Unit @@ -65,7 +65,7 @@ To find your integration's metrics, go to **[one.newrelic.com > All capabil - `ResponseTime` + `ResponseTime` @@ -80,7 +80,7 @@ To find your integration's metrics, go to **[one.newrelic.com > All capabil - `ServerErrorCount` + `ServerErrorCount` @@ -95,7 +95,7 @@ To find your integration's metrics, go to **[one.newrelic.com > All capabil - `SuccessfulRequestCount` + `SuccessfulRequestCount` @@ -110,7 +110,7 @@ To find your integration's metrics, go to **[one.newrelic.com > All capabil - `ThrottledCount` + `ThrottledCount` @@ -125,7 +125,7 @@ To find your integration's metrics, go to **[one.newrelic.com > All capabil - `UserErrorCount` + `UserErrorCount` diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-trusted-advisor-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-trusted-advisor-integration.mdx index 7fb65665576..8354bdd8d99 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-trusted-advisor-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-trusted-advisor-integration.mdx @@ -19,7 +19,7 @@ freshnessValidatedDate: never The AWS [Trusted Advisor](https://aws.amazon.com/premiumsupport/technology/trusted-advisor/) is an online tool that provides real-time guidance to help you follow AWS best practices for provisioning your resources. -[New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your service limits data to New Relic products. This document explains how to activate this integration and describes the data that can be captured. +[New Relic infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your service limits data to New Relic products. This document explains how to activate this integration and describes the data that can be captured. ## Activate integration [#activate] diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-vpc-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-vpc-monitoring-integration.mdx index 341a9cb737e..9036f9eccd8 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-vpc-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-vpc-monitoring-integration.mdx @@ -17,7 +17,7 @@ freshnessValidatedDate: never Enable the [AWS CloudWatch Metric Streams integration](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-metric-stream/) to monitor all CloudWatch metrics from your AWS services, including custom namespaces. Individual integrations are no longer our recommended option. -[New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your Amazon VPC data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your Amazon VPC data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features [#features] diff --git a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-x-ray-monitoring-integration.mdx b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-x-ray-monitoring-integration.mdx index 4be76c68a0d..34c08cff176 100644 --- a/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-x-ray-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-x-ray-monitoring-integration.mdx @@ -56,7 +56,7 @@ Here's an example NRQL query to correlate X-Ray data with specific API performan ```sql SELECT average(duration.ms) FROM Span WHERE newRelic.ingestPoint = 'xray.polling' -AND http.url LIKE 'https://yourdomanin.com/api/v1/endpoint%' since 1 month ago +AND http.url LIKE 'https://yourdomanin.com/api/v1/endpoint%' SINCE 1 month ago LIMIT MAX TIMESERIES 1 day ``` diff --git a/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-app-engine-monitoring-integration.mdx b/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-app-engine-monitoring-integration.mdx index 37c3fe4c4a8..1979ad9acfa 100644 --- a/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-app-engine-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-app-engine-monitoring-integration.mdx @@ -13,7 +13,7 @@ redirects: freshnessValidatedDate: never --- -New Relic offers an [integration](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) that fetches data about your [Google App Engine](https://cloud.google.com/appengine/) services so that you can view the data in the New Relic UI. +New Relic offers an [integration](/docs/infrastructure/introduction-infra-monitoring) that fetches data about your [Google App Engine](https://cloud.google.com/appengine/) services so that you can view the data in the New Relic UI. For more information about monitoring applications that **reside in** a Google App Engine environment with (instead of how to monitor your Google App Engine services), see [Google App Engine environment](/docs/accounts/install-new-relic/partner-based-installation/google-app-engine-environment). diff --git a/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-dataflow-monitoring-integration.mdx b/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-dataflow-monitoring-integration.mdx index 67616f37bff..7987f5e0316 100644 --- a/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-dataflow-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-dataflow-monitoring-integration.mdx @@ -11,7 +11,7 @@ redirects: freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your GCP Dataflow data to our products. Here we explain how to activate the integration and what data it collects. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your GCP Dataflow data to our products. Here we explain how to activate the integration and what data it collects. ## Activate integration [#activate] diff --git a/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-dataproc-monitoring-integration.mdx b/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-dataproc-monitoring-integration.mdx index b9ba4447278..5a7346154c6 100644 --- a/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-dataproc-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-dataproc-monitoring-integration.mdx @@ -11,7 +11,7 @@ redirects: freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your GCP Dataproc data to our products. Here we explain how to activate the integration and what data it collects. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your GCP Dataproc data to our products. Here we explain how to activate the integration and what data it collects. ## Activate integration [#activate] diff --git a/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-firebase-database-monitoring-integration.mdx b/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-firebase-database-monitoring-integration.mdx index 2b17d1180a1..a9e87cc71c0 100644 --- a/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-firebase-database-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-firebase-database-monitoring-integration.mdx @@ -11,7 +11,7 @@ redirects: freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your GCP Firebase Database data to our products. Here we explain how to activate the integration and what data it collects. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your GCP Firebase Database data to our products. Here we explain how to activate the integration and what data it collects. ## Activate integration [#activate] diff --git a/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-firebase-hosting-monitoring-integration.mdx b/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-firebase-hosting-monitoring-integration.mdx index 91f0e8aaf3f..ab492720913 100644 --- a/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-firebase-hosting-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-firebase-hosting-monitoring-integration.mdx @@ -11,7 +11,7 @@ redirects: freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your GCP Firebase Hosting data to our products. Here we explain how to activate the integration and what data it collects. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your GCP Firebase Hosting data to our products. Here we explain how to activate the integration and what data it collects. ## Activate integration [#activate] diff --git a/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-firebase-storage-monitoring-integration.mdx b/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-firebase-storage-monitoring-integration.mdx index fd56ef6fe53..862e07976b6 100644 --- a/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-firebase-storage-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-firebase-storage-monitoring-integration.mdx @@ -11,7 +11,7 @@ redirects: freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your GCP Firebase Storage data to our products. Here we explain how to activate the integration and what data it collects. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your GCP Firebase Storage data to our products. Here we explain how to activate the integration and what data it collects. ## Activate integration [#activate] diff --git a/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-firestore-monitoring-integration.mdx b/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-firestore-monitoring-integration.mdx index c378bc65c51..36d8a8a0fd3 100644 --- a/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-firestore-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-firestore-monitoring-integration.mdx @@ -11,7 +11,7 @@ redirects: freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your GCP Firestore data to our products. Here we explain how to activate the integration and what data it collects. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your GCP Firestore data to our products. Here we explain how to activate the integration and what data it collects. ## Activate integration [#activate] diff --git a/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-functions-monitoring-integration.mdx b/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-functions-monitoring-integration.mdx index 993b56c9163..006f8d68c39 100644 --- a/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-functions-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-functions-monitoring-integration.mdx @@ -13,7 +13,7 @@ redirects: freshnessValidatedDate: never --- -Our [infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) with the [Google Cloud Platform (GCP)](https://cloud.google.com/) includes one that reports [Google Cloud Functions](https://cloud.google.com/functions/) data to our products. This document explains how to activate the GCP Cloud Functions integration and describes the data that can be reported. +Our [infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) with the [Google Cloud Platform (GCP)](https://cloud.google.com/) includes one that reports [Google Cloud Functions](https://cloud.google.com/functions/) data to our products. This document explains how to activate the GCP Cloud Functions integration and describes the data that can be reported. ## Features @@ -36,7 +36,7 @@ After activating the integration and then waiting a few minutes (based on the [p ## Metric data [#metrics] -[Metric data](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations#data-types) we receive from your GCP Cloud Functions integration includes: +[Metric data](/docs/infrastructure/introduction-infra-monitoring#data-types) we receive from your GCP Cloud Functions integration includes: diff --git a/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-load-balancing-monitoring-integration.mdx b/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-load-balancing-monitoring-integration.mdx index 4dabcaa8c52..e3c1bb2c145 100644 --- a/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-load-balancing-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-load-balancing-monitoring-integration.mdx @@ -12,7 +12,7 @@ redirects: freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) with the [Google Cloud Platform (GCP)](https://cloud.google.com) include an integration to report [Google Cloud Load Balancing](https://cloud.google.com/load-balancing/) data to New Relic. This document explains how to activate the GCP Cloud Load Balancing integration and describes the data that can be reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) with the [Google Cloud Platform (GCP)](https://cloud.google.com) include an integration to report [Google Cloud Load Balancing](https://cloud.google.com/load-balancing/) data to New Relic. This document explains how to activate the GCP Cloud Load Balancing integration and describes the data that can be reported. ## Features diff --git a/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-pubsub-monitoring-integration.mdx b/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-pubsub-monitoring-integration.mdx index be4b20554f9..ed47bdfdc59 100644 --- a/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-pubsub-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-pubsub-monitoring-integration.mdx @@ -11,7 +11,7 @@ redirects: freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) with the [Google Cloud Platform (GCP)](https://cloud.google.com/) include an integration to report [Google Cloud Pub/Sub](https://cloud.google.com/pubsub/) data to New Relic. This document explains how to activate the GCP Pub/Sub integration and describes the data that will be reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) with the [Google Cloud Platform (GCP)](https://cloud.google.com/) include an integration to report [Google Cloud Pub/Sub](https://cloud.google.com/pubsub/) data to New Relic. This document explains how to activate the GCP Pub/Sub integration and describes the data that will be reported. ## Features diff --git a/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-router-monitoring-integration.mdx b/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-router-monitoring-integration.mdx index b20bfabbb61..cc17c3e6d53 100644 --- a/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-router-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-router-monitoring-integration.mdx @@ -12,7 +12,7 @@ redirects: freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your GCP Router data to our products. Here we explain how to activate the integration and what data it collects. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your GCP Router data to our products. Here we explain how to activate the integration and what data it collects. ## Activate integration [#activate] diff --git a/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-run-monitoring-integration.mdx b/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-run-monitoring-integration.mdx index a5d97851832..16ad1d6bd6f 100644 --- a/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-run-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-run-monitoring-integration.mdx @@ -11,7 +11,7 @@ redirects: freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your GCP Run data to our products. Here we explain how to activate the integration and what data it collects. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your GCP Run data to our products. Here we explain how to activate the integration and what data it collects. ## Activate integration [#activate] diff --git a/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-spanner-monitoring-integration.mdx b/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-spanner-monitoring-integration.mdx index 50c4888c7c4..e1f5298395d 100644 --- a/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-spanner-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-spanner-monitoring-integration.mdx @@ -11,7 +11,7 @@ redirects: freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) with the [Google Cloud Platform (GCP)](https://cloud.google.com) include an integration to report [Google Cloud Spanner](https://cloud.google.com/spanner/) data to New Relic. This document explains how to activate the GCP Cloud Spanner integration and describes the data that can be reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) with the [Google Cloud Platform (GCP)](https://cloud.google.com) include an integration to report [Google Cloud Spanner](https://cloud.google.com/spanner/) data to New Relic. This document explains how to activate the GCP Cloud Spanner integration and describes the data that can be reported. ## Features [#features] diff --git a/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-sql-monitoring-integration.mdx b/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-sql-monitoring-integration.mdx index 96babffe893..18f08b8d27a 100644 --- a/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-sql-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-sql-monitoring-integration.mdx @@ -12,7 +12,7 @@ redirects: freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) with the [Google Cloud Platform (GCP)](https://cloud.google.com/) include an integration to report [Google Cloud SQL](https://cloud.google.com/sql/docs/) data to New Relic. This document explains how to activate the GCP SQL integration and describes the data that can be reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) with the [Google Cloud Platform (GCP)](https://cloud.google.com/) include an integration to report [Google Cloud SQL](https://cloud.google.com/sql/docs/) data to New Relic. This document explains how to activate the GCP SQL integration and describes the data that can be reported. ## Features diff --git a/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-storage-monitoring-integration.mdx b/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-storage-monitoring-integration.mdx index 72e50f424a1..16a90307bd8 100644 --- a/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-storage-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-storage-monitoring-integration.mdx @@ -12,7 +12,7 @@ redirects: freshnessValidatedDate: never --- -New Relic offers an [integration](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) for reporting your Google Cloud Storage data to New Relic. Learn how to [connect this integration to infrastructure monitoring](#connect) and about the [metric data](#metrics) that New Relic reports for this integration. +New Relic offers an [integration](/docs/infrastructure/introduction-infra-monitoring) for reporting your Google Cloud Storage data to New Relic. Learn how to [connect this integration to infrastructure monitoring](#connect) and about the [metric data](#metrics) that New Relic reports for this integration. ## Features diff --git a/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-compute-engine-monitoring-integration.mdx b/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-compute-engine-monitoring-integration.mdx index c51c16052a5..260e3d64a8e 100644 --- a/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-compute-engine-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-compute-engine-monitoring-integration.mdx @@ -33,7 +33,7 @@ After activating the integration and waiting a few minutes (based on the [pollin ## Metric data [#metrics] -[Metric data](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations#data-types) that New Relic receives from your GCP Compute Engine integration include: +[Metric data](/docs/infrastructure/introduction-infra-monitoring#data-types) that New Relic receives from your GCP Compute Engine integration include: ### GcpVirtualMachineSample [#GcpVirtualMachineSample] diff --git a/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-datastore-monitoring-integration.mdx b/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-datastore-monitoring-integration.mdx index d799a525ce2..0c8d69dc681 100644 --- a/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-datastore-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-datastore-monitoring-integration.mdx @@ -11,7 +11,7 @@ redirects: freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your GCP Datastore data to our products. Here we explain how to activate the integration and what data it collects. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your GCP Datastore data to our products. Here we explain how to activate the integration and what data it collects. ## Activate integration [#activate] diff --git a/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-direct-interconnect-monitoring-integration.mdx b/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-direct-interconnect-monitoring-integration.mdx index aef3d1c72db..09014399fc6 100644 --- a/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-direct-interconnect-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-direct-interconnect-monitoring-integration.mdx @@ -11,7 +11,7 @@ redirects: freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your GCP Interconnect data to our products. Here we explain how to activate the integration and what data it collects. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your GCP Interconnect data to our products. Here we explain how to activate the integration and what data it collects. ## Activate integration [#activate] diff --git a/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-kubernetes-engine-monitoring-integration.mdx b/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-kubernetes-engine-monitoring-integration.mdx index 25faa845f62..f8566d33d26 100644 --- a/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-kubernetes-engine-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-kubernetes-engine-monitoring-integration.mdx @@ -12,7 +12,7 @@ redirects: freshnessValidatedDate: never --- -[New Relic's integration](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) with [Google Kubernetes Engine](https://cloud.google.com/kubernetes-engine/) (GKE) reports data about clusters hosted on Google's infrastructure. You can monitor and alert on your GKE instances data from our [infrastructure UI](/docs/infrastructure), and you can create [custom queries and chart dashboards](/docs/insights). +[New Relic's integration](/docs/infrastructure/introduction-infra-monitoring) with [Google Kubernetes Engine](https://cloud.google.com/kubernetes-engine/) (GKE) reports data about clusters hosted on Google's infrastructure. You can monitor and alert on your GKE instances data from our [infrastructure UI](/docs/infrastructure), and you can create [custom queries and chart dashboards](/docs/insights). ## Activate integration [#activate] diff --git a/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-serverless-vpc-access-monitoring-integration.mdx b/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-serverless-vpc-access-monitoring-integration.mdx index 5f203610b92..e190c11087e 100644 --- a/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-serverless-vpc-access-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-serverless-vpc-access-monitoring-integration.mdx @@ -11,7 +11,7 @@ redirects: freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your GCP VPC Access data to our products. Here we explain how to activate the integration and what data it collects. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your GCP VPC Access data to our products. Here we explain how to activate the integration and what data it collects. ## Activate integration [#activate] diff --git a/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-vertexai-monitoring-integration.mdx b/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-vertexai-monitoring-integration.mdx index 2db88efeebf..2a59c5d6510 100644 --- a/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-vertexai-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-vertexai-monitoring-integration.mdx @@ -10,7 +10,7 @@ redirects: freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your GCP Run data to our products. Here, we explain how to activate the integration and what data it collects. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your GCP Run data to our products. Here, we explain how to activate the integration and what data it collects. ## Activate integration [#activate] diff --git a/src/content/docs/infrastructure/infrastructure-agent/linux-installation/package-manager-install.mdx b/src/content/docs/infrastructure/infrastructure-agent/linux-installation/package-manager-install.mdx index 5927d7747a1..b8d7feb1857 100644 --- a/src/content/docs/infrastructure/infrastructure-agent/linux-installation/package-manager-install.mdx +++ b/src/content/docs/infrastructure/infrastructure-agent/linux-installation/package-manager-install.mdx @@ -587,6 +587,6 @@ The only required [configuration option](/docs/infrastructure/install-configure- * [Add custom attributes](/docs/Infrastructure-configure-your-agent#conf-custom_attributes) to annotate your infrastructure data. * [Connect your AWS account](/docs/infrastructure-amazon-aws-ec2-integration#connect) if your servers are hosted on Amazon EC2. * Enable [log forwarding](/docs/logs/enable-new-relic-logs/1-enable-logs/forward-your-logs-using-new-relic-infrastructure-agent). -* Add other [New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) to collect data from external services. +* Add other [New Relic infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) to collect data from external services. diff --git a/src/content/docs/infrastructure/infrastructure-agent/linux-installation/tarball-assisted-linux.mdx b/src/content/docs/infrastructure/infrastructure-agent/linux-installation/tarball-assisted-linux.mdx index b188037bf62..5a0d35c8e7f 100644 --- a/src/content/docs/infrastructure/infrastructure-agent/linux-installation/tarball-assisted-linux.mdx +++ b/src/content/docs/infrastructure/infrastructure-agent/linux-installation/tarball-assisted-linux.mdx @@ -258,5 +258,5 @@ You may also want to: * [Add custom attributes](/docs/Infrastructure-configure-your-agent#conf-custom_attributes) to annotate your infrastructure data. * [Connect your AWS account](/docs/infrastructure-amazon-aws-ec2-integration#connect) if your servers are hosted on Amazon EC2. * Enable [log forwarding](/docs/logs/forward-logs/forward-your-logs-using-infrastructure-agent#tarball-install). -* Add other [infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) to collect data from external services. +* Add other [infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) to collect data from external services. * Manually [start, stop, restart, or check the agent status](/docs/infrastructure-start-stop-restart-check-agent-status#linux). diff --git a/src/content/docs/infrastructure/infrastructure-agent/linux-installation/tarball-manual-linux.mdx b/src/content/docs/infrastructure/infrastructure-agent/linux-installation/tarball-manual-linux.mdx index fb5ba7a3203..601f61401c1 100644 --- a/src/content/docs/infrastructure/infrastructure-agent/linux-installation/tarball-manual-linux.mdx +++ b/src/content/docs/infrastructure/infrastructure-agent/linux-installation/tarball-manual-linux.mdx @@ -453,5 +453,5 @@ You may also want to: * [Connect your AWS account](/docs/infrastructure-amazon-aws-ec2-integration#connect) if your servers are hosted on Amazon EC2. * Enable [log forwarding](/docs/logs/forward-logs/forward-your-logs-using-infrastructure-agent#tarball-install). * Enable our Flex integration by [manually adding the Flex executable](https://github.com/newrelic/nri-flex/releases). -* Add other [infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) to collect data from external services. +* Add other [infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) to collect data from external services. * Manually [start, stop, restart, or check the agent status](/docs/infrastructure-start-stop-restart-check-agent-status#linux). diff --git a/src/content/docs/infrastructure/infrastructure-agent/macos-installation/install-infrastructure-monitoring-agent-macos.mdx b/src/content/docs/infrastructure/infrastructure-agent/macos-installation/install-infrastructure-monitoring-agent-macos.mdx index 183bfd3ab8e..a3ea52b88bf 100644 --- a/src/content/docs/infrastructure/infrastructure-agent/macos-installation/install-infrastructure-monitoring-agent-macos.mdx +++ b/src/content/docs/infrastructure/infrastructure-agent/macos-installation/install-infrastructure-monitoring-agent-macos.mdx @@ -83,7 +83,7 @@ The only required [configuration option](/docs/infrastructure/install-configure- * [Add custom attributes](/docs/Infrastructure-configure-your-agent#conf-custom_attributes) to annotate your infrastructure data. * [Connect your AWS account](/docs/infrastructure-amazon-aws-ec2-integration#connect) if your servers are hosted on Amazon EC2. -* Add other [New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) to collect data from external services. +* Add other [New Relic infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) to collect data from external services. ## Update the agent [#update] diff --git a/src/content/docs/infrastructure/infrastructure-agent/windows-installation/windows-msi-installer.mdx b/src/content/docs/infrastructure/infrastructure-agent/windows-installation/windows-msi-installer.mdx index f372b857ba0..d90edb78d4f 100644 --- a/src/content/docs/infrastructure/infrastructure-agent/windows-installation/windows-msi-installer.mdx +++ b/src/content/docs/infrastructure/infrastructure-agent/windows-installation/windows-msi-installer.mdx @@ -138,7 +138,7 @@ The only required [configuration option](/docs/infrastructure/install-configure- * [Add custom attributes](/docs/Infrastructure-configure-your-agent#conf-custom_attributes) to annotate your infrastructure data. * [Connect your AWS account](/docs/infrastructure-amazon-aws-ec2-integration#connect) if your servers are hosted on Amazon EC2. * Enable [log forwarding](/docs/logs/enable-new-relic-logs/1-enable-logs/forward-your-logs-using-new-relic-infrastructure-agent). -* Add other [New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) to collect data from external services. +* Add other [New Relic infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) to collect data from external services. ## Update the agent [#update] diff --git a/src/content/docs/infrastructure/infrastructure-agent/windows-installation/windows-zip-assisted.mdx b/src/content/docs/infrastructure/infrastructure-agent/windows-installation/windows-zip-assisted.mdx index e8715953098..c949df5c981 100644 --- a/src/content/docs/infrastructure/infrastructure-agent/windows-installation/windows-zip-assisted.mdx +++ b/src/content/docs/infrastructure/infrastructure-agent/windows-installation/windows-zip-assisted.mdx @@ -195,5 +195,5 @@ You may also want to: * [Add custom attributes](/docs/Infrastructure-configure-your-agent#conf-custom_attributes) to annotate your infrastructure data. * [Connect your AWS account](/docs/infrastructure-amazon-aws-ec2-integration#connect) if your servers are hosted on Amazon EC2. -* Add other [New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) to collect data from external services. +* Add other [New Relic infrastructure integrations](/docs/infrastructure/introduction-infra-monitoring) to collect data from external services. * Manually [start, stop, restart, or check the agent status](/docs/infrastructure-start-stop-restart-check-agent-status#linux). diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-app-configuration-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-app-configuration-monitoring-integration.mdx index eb865b7f5d5..6317a929302 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-app-configuration-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-app-configuration-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure App Configuration integration: wha freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure App Configuration](https://learn.microsoft.com/en-us/azure/azure-app-configuration/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure App Configuration](https://learn.microsoft.com/en-us/azure/azure-app-configuration/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-app-service-environment-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-app-service-environment-monitoring-integration.mdx index 10ce694d9ec..7cbce56aa77 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-app-service-environment-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-app-service-environment-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure App Service Environment integratio freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure App Service Environment](https://learn.microsoft.com/en-in/azure/app-service/environment) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure App Service Environment](https://learn.microsoft.com/en-in/azure/app-service/environment) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-app-service-plan.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-app-service-plan.mdx index 1841c9e64f3..dc538f54fb1 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-app-service-plan.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-app-service-plan.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure App Service Plan integration: what freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure App Service Plan](https://learn.microsoft.com/en-us/azure/app-service/overview-hosting-plans) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure App Service Plan](https://learn.microsoft.com/en-us/azure/app-service/overview-hosting-plans) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-application-gateway-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-application-gateway-monitoring-integration.mdx index 7284b3f80c2..f1e8140cef5 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-application-gateway-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-application-gateway-monitoring-integration.mdx @@ -12,7 +12,7 @@ redirects: freshnessValidatedDate: never --- -[New Relic includes an integration](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) for reporting your Azure App Gateway data to our platform. Here we explain how to activate the integration and what data it collects. +[New Relic includes an integration](/docs/infrastructure/introduction-infra-monitoring) for reporting your Azure App Gateway data to our platform. Here we explain how to activate the integration and what data it collects. ## Activate the integration [#activate] diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-application-insights-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-application-insights-monitoring-integration.mdx index f64b5d5478b..de1da652981 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-application-insights-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-application-insights-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure Application Insights integration: freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Application Insights](https://learn.microsoft.com/en-us/azure/azure-monitor/app/app-insights-overview) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Application Insights](https://learn.microsoft.com/en-us/azure/azure-monitor/app/app-insights-overview) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-automation-account-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-automation-account-monitoring-integration.mdx index 9e943657a34..ec1f87d23df 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-automation-account-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-automation-account-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure Automation Account integration: wh freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Automation Account](https://learn.microsoft.com/en-us/azure/automation/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Automation Account](https://learn.microsoft.com/en-us/azure/automation/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-batchaccount-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-batchaccount-monitoring-integration.mdx index c4b6f011837..ffe92fac57b 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-batchaccount-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-batchaccount-monitoring-integration.mdx @@ -6,7 +6,7 @@ redirects: freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Batch Account](https://azure.microsoft.com/en-us/services/batch/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Batch Account](https://azure.microsoft.com/en-us/services/batch/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-bing-search-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-bing-search-monitoring-integration.mdx index 67910cb9dc5..16b7e37dd99 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-bing-search-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-bing-search-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure Bing Search integration: what data freshnessValidatedDate: 2023-06-06 --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Bing Search](https://learn.microsoft.com/en-us/bing/search-apis/bing-web-search/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Bing Search](https://learn.microsoft.com/en-us/bing/search-apis/bing-web-search/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cdn-profile-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cdn-profile-monitoring-integration.mdx index 4833dd1b8ec..977654efaaa 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cdn-profile-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cdn-profile-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure CDN profile integration: what data freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure CDN profile](https://azure.microsoft.com/en-us/services/cdn/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure CDN profile](https://azure.microsoft.com/en-us/services/cdn/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cloud-services-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cloud-services-monitoring-integration.mdx index 9b8e1f25086..6efbd4990fe 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cloud-services-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cloud-services-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure Cloud Services integration: what d freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Cloud Services](https://learn.microsoft.com/en-us/azure/cloud-services) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Cloud Services](https://learn.microsoft.com/en-us/azure/cloud-services) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cognitive-search-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cognitive-search-monitoring-integration.mdx index 28954d830f5..12173f48588 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cognitive-search-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cognitive-search-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure Cognitive Search integration: what freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Cognitive Search](https://azure.microsoft.com/en-in/products/search/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Cognitive Search](https://azure.microsoft.com/en-in/products/search/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cognitive-services-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cognitive-services-monitoring-integration.mdx index b4c63910944..b8059fbd1b7 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cognitive-services-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cognitive-services-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure Cognitive Services integration: wh freshnessValidatedDate: 2023-06-06 --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Cognitive Services](https://azure.microsoft.com/en-in/products/cognitive-services/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Cognitive Services](https://azure.microsoft.com/en-in/products/cognitive-services/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-containers-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-containers-monitoring-integration.mdx index 098823a8754..a97e04b2a4b 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-containers-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-containers-monitoring-integration.mdx @@ -11,7 +11,7 @@ redirects: freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your Azure Containers data to our products. Here we explain how to activate the integration and what data it collects. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your Azure Containers data to our products. Here we explain how to activate the integration and what data it collects. ## Activate integration [#activate] diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cost-management-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cost-management-monitoring-integration.mdx index 4a05ace82b0..9d422acffcb 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cost-management-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cost-management-monitoring-integration.mdx @@ -11,7 +11,7 @@ redirects: freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Cost Management](https://docs.microsoft.com/en-us/azure/cost-management/) data to New Relic. Here we explain how to activate the integration and what data it collects. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Cost Management](https://docs.microsoft.com/en-us/azure/cost-management/) data to New Relic. Here we explain how to activate the integration and what data it collects. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-data-box-edge-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-data-box-edge-monitoring-integration.mdx index 2664d65b98b..5c985389fb7 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-data-box-edge-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-data-box-edge-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure Data Box Edge integration: what da freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Data Box Edge](https://azure.microsoft.com/en-us/updates/announcing-azure-data-box-edge/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Data Box Edge](https://azure.microsoft.com/en-us/updates/announcing-azure-data-box-edge/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-data-explorer-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-data-explorer-monitoring-integration.mdx index 5cc8ce26c7f..248d8b44d4a 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-data-explorer-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-data-explorer-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure Data Explorer integration: what da freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Data Explorer](https://azure.microsoft.com/en-us/products/data-explorer/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Data Explorer](https://azure.microsoft.com/en-us/products/data-explorer/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features @@ -66,7 +66,7 @@ This integration collects the following [metric data](/docs/infrastructure/integ diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-data-factory-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-data-factory-integration.mdx index 0efda2ed8a1..eaabc56ab03 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-data-factory-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-data-factory-integration.mdx @@ -12,7 +12,7 @@ redirects: freshnessValidatedDate: never --- -[New Relic infrastructure monitoring](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) provides an integration for reporting your [Microsoft Azure Data Factory](https://azure.microsoft.com/en-us/services/data-factory/) data to New Relic. Here we explain how to activate the integration and what data can be reported. +[New Relic infrastructure monitoring](/docs/infrastructure/introduction-infra-monitoring) provides an integration for reporting your [Microsoft Azure Data Factory](https://azure.microsoft.com/en-us/services/data-factory/) data to New Relic. Here we explain how to activate the integration and what data can be reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-data-lake-analytic-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-data-lake-analytic-monitoring-integration.mdx index be9974f990e..46d9b5d072d 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-data-lake-analytic-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-data-lake-analytic-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure Data Lake Analytics integration: w freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Data Lake Analytics](https://azure.microsoft.com/en-us/products/data-lake-analytics) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Data Lake Analytics](https://azure.microsoft.com/en-us/products/data-lake-analytics) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-data-lake-storage-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-data-lake-storage-monitoring-integration.mdx index 126857c6a5a..0f6eda90da1 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-data-lake-storage-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-data-lake-storage-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure Data Lake Storage integration: wha freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Data Lake Storage](https://learn.microsoft.com/en-us/azure/data-lake-store) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Data Lake Storage](https://learn.microsoft.com/en-us/azure/data-lake-store) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-data-share-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-data-share-monitoring-integration.mdx index 8ab2e05a3cb..26ce922743a 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-data-share-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-data-share-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure Data Share integration: what data freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Data Share](https://azure.microsoft.com/en-us/products/data-share/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Data Share](https://azure.microsoft.com/en-us/products/data-share/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-database-mariadb-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-database-mariadb-monitoring-integration.mdx index b9db8aa6c59..b4cb0c47e09 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-database-mariadb-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-database-mariadb-monitoring-integration.mdx @@ -11,7 +11,7 @@ redirects: freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Database for MariaDB](https://docs.microsoft.com/en-gb/azure/mariadb/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Database for MariaDB](https://docs.microsoft.com/en-gb/azure/mariadb/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-database-mysql-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-database-mysql-monitoring-integration.mdx index a402a16f890..fd0acc12992 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-database-mysql-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-database-mysql-monitoring-integration.mdx @@ -11,7 +11,7 @@ redirects: freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Database for MySQL](https://azure.microsoft.com/en-us/services/mysql/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Database for MySQL](https://azure.microsoft.com/en-us/services/mysql/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-database-postgresql-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-database-postgresql-monitoring-integration.mdx index ba9da566c85..4360b3cdcdb 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-database-postgresql-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-database-postgresql-monitoring-integration.mdx @@ -11,7 +11,7 @@ redirects: freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Database for PostgreSQL](https://docs.microsoft.com/en-gb/azure/postgresql/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Database for PostgreSQL](https://docs.microsoft.com/en-gb/azure/postgresql/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-device-provisioning-service-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-device-provisioning-service-integration.mdx index b7caf2e3cf9..42f9e188804 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-device-provisioning-service-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-device-provisioning-service-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure Device Provisioning Service integr freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Device Provisioning Service](https://learn.microsoft.com/en-us/azure/iot-dps/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Device Provisioning Service](https://learn.microsoft.com/en-us/azure/iot-dps/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-disk-storage-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-disk-storage-monitoring-integration.mdx index 5a96a6ce1a4..14fd47a60df 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-disk-storage-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-disk-storage-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure Disk Storage integration: what dat freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Disk Storage](https://azure.microsoft.com/en-us/products/storage/disks/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Disk Storage](https://azure.microsoft.com/en-us/products/storage/disks/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-dns-zones-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-dns-zones-monitoring-integration.mdx index 43ebb3a024d..aab9036e10f 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-dns-zones-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-dns-zones-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure DNS Zones integration: what data i freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure DNS Zones](https://azure.microsoft.com/en-us/products/dns/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure DNS Zones](https://azure.microsoft.com/en-us/products/dns/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-event-grid-domains-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-event-grid-domains-monitoring-integration.mdx index 2bfa130190d..6d1227056b8 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-event-grid-domains-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-event-grid-domains-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure Event Grid Domains integration: wh freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Event Grid Domains](https://learn.microsoft.com/en-us/azure/event-grid/event-domains) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Event Grid Domains](https://learn.microsoft.com/en-us/azure/event-grid/event-domains) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-event-grid-partner-namespaces-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-event-grid-partner-namespaces-monitoring-integration.mdx index 04ec6577428..b713b398473 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-event-grid-partner-namespaces-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-event-grid-partner-namespaces-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure Event Grid Partner Namespaces inte freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Event Grid partner Namespaces ](https://learn.microsoft.com/en-us/azure/event-grid/partner-events-overview-for-partners) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Event Grid partner Namespaces ](https://learn.microsoft.com/en-us/azure/event-grid/partner-events-overview-for-partners) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-event-grid-partner-topics-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-event-grid-partner-topics-monitoring-integration.mdx index 8c97d699623..1d6f9d31de4 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-event-grid-partner-topics-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-event-grid-partner-topics-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure Event Grid Partner Topics integrat freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Event Grid Partner Topics ](https://azure.microsoft.com/en-us/products/event-grid/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Event Grid Partner Topics ](https://azure.microsoft.com/en-us/products/event-grid/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-event-grid-subscriptions-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-event-grid-subscriptions-monitoring-integration.mdx index ab848ea5307..12477b3531e 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-event-grid-subscriptions-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-event-grid-subscriptions-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure Event Grid Subscriptions integrati freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Event Grid Subscriptions](https://learn.microsoft.com/en-us/azure/event-grid/subscribe-through-portal) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Event Grid Subscriptions](https://learn.microsoft.com/en-us/azure/event-grid/subscribe-through-portal) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-event-grid-system-topics-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-event-grid-system-topics-monitoring-integration.mdx index 05feb212137..98454715a9c 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-event-grid-system-topics-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-event-grid-system-topics-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure Event Grid System Topics integrati freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Event Grid System Topics ](https://azure.microsoft.com/en-us/products/event-grid/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Event Grid System Topics ](https://azure.microsoft.com/en-us/products/event-grid/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-event-grid-topics-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-event-grid-topics-monitoring-integration.mdx index e36b91e2653..a5874053186 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-event-grid-topics-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-event-grid-topics-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure Event Grid Topics integration: wha freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Event Grid Topics ](https://azure.microsoft.com/en-us/products/event-grid/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Event Grid Topics ](https://azure.microsoft.com/en-us/products/event-grid/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-event-hub-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-event-hub-monitoring-integration.mdx index 4bc7c2a0da9..bd4d15c41ee 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-event-hub-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-event-hub-monitoring-integration.mdx @@ -11,7 +11,7 @@ redirects: freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your Azure Event Hub data to our products. Here we explain how to activate the integration and what data it collects. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your Azure Event Hub data to our products. Here we explain how to activate the integration and what data it collects. ## Activate integration [#activate] diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-express-route-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-express-route-monitoring-integration.mdx index 32a98025e0f..aa2b716e657 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-express-route-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-express-route-monitoring-integration.mdx @@ -11,7 +11,7 @@ redirects: freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your Azure Express Route data to our products. Here we explain how to activate the integration and what data it collects. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your Azure Express Route data to our products. Here we explain how to activate the integration and what data it collects. ## Activate integration [#activate] diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-firewalls-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-firewalls-monitoring-integration.mdx index 15d41879bce..1dcc3a1b846 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-firewalls-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-firewalls-monitoring-integration.mdx @@ -11,7 +11,7 @@ redirects: freshnessValidatedDate: never --- -[New Relic includes an integration](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) for reporting your Azure Firewalls data to our platform. Here we explain how to activate the integration and what data it collects. +[New Relic includes an integration](/docs/infrastructure/introduction-infra-monitoring) for reporting your Azure Firewalls data to our platform. Here we explain how to activate the integration and what data it collects. ## Activate the integration [#activate] diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-front-door-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-front-door-monitoring-integration.mdx index f0c19395284..e6bcec16f0a 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-front-door-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-front-door-monitoring-integration.mdx @@ -11,7 +11,7 @@ redirects: freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your Azure Front Door data to our products. Here we explain how to activate the integration and what data it collects. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your Azure Front Door data to our products. Here we explain how to activate the integration and what data it collects. ## Activate integration [#activate] diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-functions-workflow-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-functions-workflow-monitoring-integration.mdx index 4ca5638b742..2fa58f6d16b 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-functions-workflow-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-functions-workflow-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure Functions Workflow integration: wh freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Functions Workflow](https://azure.microsoft.com/en-us/products/logic-apps/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Functions Workflow](https://azure.microsoft.com/en-us/products/logic-apps/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-hdinsight-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-hdinsight-monitoring-integration.mdx index e99eef5200c..d2f554c9227 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-hdinsight-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-hdinsight-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure HDInsight integration: what data i freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure HDInsight](https://azure.microsoft.com/en-us/products/hdinsight/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure HDInsight](https://azure.microsoft.com/en-us/products/hdinsight/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-integration-service-environment-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-integration-service-environment-monitoring-integration.mdx index 3eaa84b4f79..d3f9cf80f77 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-integration-service-environment-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-integration-service-environment-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure Integration Service Environment in freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Integration Service Environment](https://learn.microsoft.com/en-us/azure/logic-apps/ise-manage-integration-service-environment/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Integration Service Environment](https://learn.microsoft.com/en-us/azure/logic-apps/ise-manage-integration-service-environment/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-iot-central-application-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-iot-central-application-monitoring-integration.mdx index 8575b3a9ef7..7a099784b59 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-iot-central-application-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-iot-central-application-monitoring-integration.mdx @@ -6,7 +6,7 @@ redirects: freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure IoT Central Applications](https://azure.microsoft.com/en-us/products/iot-central/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure IoT Central Applications](https://azure.microsoft.com/en-us/products/iot-central/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-iot-hub-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-iot-hub-monitoring-integration.mdx index 45a4d8d7939..d093cc3e2ff 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-iot-hub-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-iot-hub-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure IoT Hub integration: what data it freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure IoT Hub](https://learn.microsoft.com/en-us/azure/iot-hub) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure IoT Hub](https://learn.microsoft.com/en-us/azure/iot-hub) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-key-vault-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-key-vault-monitoring-integration.mdx index f29d39a8733..0f6f6dbc225 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-key-vault-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-key-vault-monitoring-integration.mdx @@ -11,7 +11,7 @@ redirects: freshnessValidatedDate: never --- -[New Relic includes an integration](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) for reporting your Azure Key Vault data to our platform. Here we explain how to activate the integration and what data it collects. +[New Relic includes an integration](/docs/infrastructure/introduction-infra-monitoring) for reporting your Azure Key Vault data to our platform. Here we explain how to activate the integration and what data it collects. ## Activate the integration [#activate] diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-logic-apps-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-logic-apps-monitoring-integration.mdx index b8c0804e699..c6d28f7b1aa 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-logic-apps-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-logic-apps-monitoring-integration.mdx @@ -11,7 +11,7 @@ redirects: freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your Azure Logic Apps data to our products. Here we explain how to activate the integration and what data it collects. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your Azure Logic Apps data to our products. Here we explain how to activate the integration and what data it collects. ## Activate integration [#activate] diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-machine-learning-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-machine-learning-integration.mdx index 083283b1eba..c024cab2102 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-machine-learning-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-machine-learning-integration.mdx @@ -11,7 +11,7 @@ redirects: freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your Azure Machine Learning data to New Relic. This document explains how to activate this integration and describes the data that can be reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your Azure Machine Learning data to New Relic. This document explains how to activate this integration and describes the data that can be reported. ## Activate integration [#activate] diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-machine-learning-monitor-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-machine-learning-monitor-integration.mdx index 27d39a2588e..e224e00ed18 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-machine-learning-monitor-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-machine-learning-monitor-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure Machine Learning integration: what freshnessValidatedDate: 2023-09-12 --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Machine Learning](https://azure.microsoft.com/en-in/products/machine-learning/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Machine Learning](https://azure.microsoft.com/en-in/products/machine-learning/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-maps-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-maps-monitoring-integration.mdx index aca86dbd57b..be4159b9166 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-maps-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-maps-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure Maps integration: what data it rep freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Maps](https://azure.microsoft.com/en-in/products/azure-maps/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Maps](https://azure.microsoft.com/en-in/products/azure-maps/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-media-services-live-events-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-media-services-live-events-monitoring-integration.mdx index 7a1fa99a42a..923fac0a69d 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-media-services-live-events-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-media-services-live-events-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure Media Services Live Events integra freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Media Services Live Events](https://learn.microsoft.com/en-us/azure/media-services/latest/live-event-streaming-best-practices-guide) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Media Services Live Events](https://learn.microsoft.com/en-us/azure/media-services/latest/live-event-streaming-best-practices-guide) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-media-services-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-media-services-monitoring-integration.mdx index 2c53ec0ab5f..40bfb91ebd8 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-media-services-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-media-services-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure Media Services integration: what d freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Media Services](https://learn.microsoft.com/en-us/azure/media-services) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Media Services](https://learn.microsoft.com/en-us/azure/media-services) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-media-services-streaming-endpoints-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-media-services-streaming-endpoints-monitoring-integration.mdx index 24e90f583a2..30ed7bf07c3 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-media-services-streaming-endpoints-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-media-services-streaming-endpoints-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure Media Services Streaming Endpoints freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Media Services Streaming Endpoints](https://learn.microsoft.com/en-us/azure/media-services/latest/stream-streaming-endpoint-concept) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Media Services Streaming Endpoints](https://learn.microsoft.com/en-us/azure/media-services/latest/stream-streaming-endpoint-concept) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-media-services-video-analyzer-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-media-services-video-analyzer-monitoring-integration.mdx index 604c733be98..a5c51a09fb2 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-media-services-video-analyzer-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-media-services-video-analyzer-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure Media Services Video Analyzer inte freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Media Services Video Analyzer](https://learn.microsoft.com/en-us/azure/azure-video-analyzer) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Media Services Video Analyzer](https://learn.microsoft.com/en-us/azure/azure-video-analyzer) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-netapp-capacity-pools-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-netapp-capacity-pools-monitoring-integration.mdx index f8f47cb7c17..74340849816 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-netapp-capacity-pools-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-netapp-capacity-pools-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure NetApp Capacity Pools integration: freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure NetApp Capacity Pools](https://learn.microsoft.com/en-us/azure/azure-netapp-files/azure-netapp-files-set-up-capacity-pool) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure NetApp Capacity Pools](https://learn.microsoft.com/en-us/azure/azure-netapp-files/azure-netapp-files-set-up-capacity-pool) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-netapp-files-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-netapp-files-monitoring-integration.mdx index 4ec4891f1a9..7c9d73c2d7d 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-netapp-files-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-netapp-files-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure NetApp Files integration: what dat freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure NetApp Files](https://azure.microsoft.com/en-us/products/netapp/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure NetApp Files](https://azure.microsoft.com/en-us/products/netapp/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-network-interface-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-network-interface-monitoring-integration.mdx index b82b9525d08..dae60f45b5a 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-network-interface-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-network-interface-monitoring-integration.mdx @@ -11,7 +11,7 @@ redirects: freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Network Interface](https://learn.microsoft.com/en-us/azure/virtual-network/virtual-network-network-interface) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Network Interface](https://learn.microsoft.com/en-us/azure/virtual-network/virtual-network-network-interface) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-network-watcher-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-network-watcher-monitoring-integration.mdx index ae001633267..92fa8fa2c60 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-network-watcher-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-network-watcher-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure Network Watcher integration: what freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Network Watcher](https://azure.microsoft.com/en-us/products/network-watcher/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Network Watcher](https://azure.microsoft.com/en-us/products/network-watcher/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-notification-hubs-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-notification-hubs-monitoring-integration.mdx index a173a1ad8b8..185c51978ef 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-notification-hubs-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-notification-hubs-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure Notification Hubs integration: wha freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Notification Hubs](https://azure.microsoft.com/en-us/products/notification-hubs/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Notification Hubs](https://azure.microsoft.com/en-us/products/notification-hubs/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features @@ -396,7 +396,7 @@ This integration collects the following [metric data](/docs/infrastructure/integ diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-peering-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-peering-monitoring-integration.mdx index bb2055c0b1d..b9e7baef059 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-peering-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-peering-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure Peering integration: what data it freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Peering](https://learn.microsoft.com/en-in/azure/internet-peering/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Peering](https://learn.microsoft.com/en-in/azure/internet-peering/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-peering-service-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-peering-service-monitoring-integration.mdx index 8a3b1d2846e..bf427f9ab2a 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-peering-service-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-peering-service-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure Peering Service integration: what freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Peering Service ](https://learn.microsoft.com/en-us/azure/peering-service/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Peering Service ](https://learn.microsoft.com/en-us/azure/peering-service/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-private-dns-zones-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-private-dns-zones-monitoring-integration.mdx index b00fd539820..9ab680fb6e0 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-private-dns-zones-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-private-dns-zones-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure Private DNS Zones integration: wha freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Private DNS Zones](https://learn.microsoft.com/en-us/azure/dns/private-dns-privatednszone/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Private DNS Zones](https://learn.microsoft.com/en-us/azure/dns/private-dns-privatednszone/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-purview-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-purview-monitoring-integration.mdx index e2666a4fc75..b7047984f8b 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-purview-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-purview-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Purview integration: what data it report freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Purview](https://azure.microsoft.com/en-us/products/purview/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Purview](https://azure.microsoft.com/en-us/products/purview/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-recovery-services-vaults-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-recovery-services-vaults-monitoring-integration.mdx index c7ac083a8a4..01f8ca822a8 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-recovery-services-vaults-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-recovery-services-vaults-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure Recovery Services Vaults integrati freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Recovery Services Vaults](https://learn.microsoft.com/en-us/azure/backup/backup-azure-recovery-services-vault-overview/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Recovery Services Vaults](https://learn.microsoft.com/en-us/azure/backup/backup-azure-recovery-services-vault-overview/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-relay-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-relay-monitoring-integration.mdx index b4ea5942358..7f44b51084b 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-relay-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-relay-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure Relay integration: what data it re freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Relay](https://learn.microsoft.com/en-us/azure/azure-relay/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Relay](https://learn.microsoft.com/en-us/azure/azure-relay/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-signalr-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-signalr-monitoring-integration.mdx index 43b3349fa7f..f1a14d02b4e 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-signalr-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-signalr-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure SignalR integration: what data it freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure SignalR ](https://learn.microsoft.com/en-us/azure/azure-signalr/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure SignalR ](https://learn.microsoft.com/en-us/azure/azure-signalr/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-spring-apps-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-spring-apps-monitoring-integration.mdx index 8ae509fe1cb..5d39001ed02 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-spring-apps-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-spring-apps-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure Spring Apps integration: what data freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Spring Apps](https://azure.microsoft.com/en-us/services/spring-apps/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Spring Apps](https://azure.microsoft.com/en-us/services/spring-apps/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-sql-database-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-sql-database-monitoring-integration.mdx index 9dc4b8d1681..7e4c645d6a1 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-sql-database-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-sql-database-monitoring-integration.mdx @@ -12,7 +12,7 @@ redirects: freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure SQL Database](https://azure.microsoft.com/en-us/services/sql-database/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure SQL Database](https://azure.microsoft.com/en-us/services/sql-database/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-storage-sync-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-storage-sync-monitoring-integration.mdx index ca904bc7f54..ffc859b4651 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-storage-sync-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-storage-sync-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure Storage Sync integration: what dat freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Storage Sync ](https://azure.microsoft.com/en-us/services/storagesync/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Storage Sync ](https://azure.microsoft.com/en-us/services/storagesync/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-stream-analytics-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-stream-analytics-monitoring-integration.mdx index 2d8cc175586..85a699f8f04 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-stream-analytics-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-stream-analytics-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure Stream Analytics integration: what freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Stream Analytics](https://azure.microsoft.com/en-us/products/stream-Analytics) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Stream Analytics](https://azure.microsoft.com/en-us/products/stream-Analytics) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-synapse-analytics-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-synapse-analytics-monitoring-integration.mdx index cfc5f4456ce..4175e9eeec1 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-synapse-analytics-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-synapse-analytics-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure Synapse Analytics integration: wha freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Synapse Analytics](https://azure.microsoft.com/en-in/products/synapse-analytics/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Synapse Analytics](https://azure.microsoft.com/en-in/products/synapse-analytics/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features @@ -276,7 +276,7 @@ This integration collects the following [metric data](/docs/infrastructure/integ diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-time-series-insights-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-time-series-insights-monitoring-integration.mdx index 5d06a665fea..028fe2ddb59 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-time-series-insights-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-time-series-insights-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure Time Series Insights integration: freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Time Series Insights](https://azure.microsoft.com/en-us/products/time-series-insights/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Time Series Insights](https://azure.microsoft.com/en-us/products/time-series-insights/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-traffic-manager-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-traffic-manager-monitoring-integration.mdx index d6e140aed2d..86c2af6f5e3 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-traffic-manager-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-traffic-manager-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure Traffic Manager integration: what freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Traffic Manager](https://learn.microsoft.com/en-us/azure/traffic-manager) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Traffic Manager](https://learn.microsoft.com/en-us/azure/traffic-manager) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-vpn-gateway-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-vpn-gateway-integration.mdx index d75841ebb06..fcdaa83d53b 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-vpn-gateway-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-vpn-gateway-integration.mdx @@ -12,7 +12,7 @@ redirects: freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Azure VPN Gateway](https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-about-vpngateways) data to our products. This document explains how to activate this integration and describes the data that can be reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Azure VPN Gateway](https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-about-vpngateways) data to our products. This document explains how to activate this integration and describes the data that can be reported. ## Features diff --git a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-web-apps-monitoring-integration.mdx b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-web-apps-monitoring-integration.mdx index 583b6c1cf90..fb259f1ce28 100644 --- a/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-web-apps-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-web-apps-monitoring-integration.mdx @@ -4,7 +4,7 @@ metaDescription: "New Relic's Microsoft Azure Web Apps integration: what data it freshnessValidatedDate: never --- -[New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Web Apps](https://azure.microsoft.com/en-us/products/app-service/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. +[New Relic's integrations](/docs/infrastructure/introduction-infra-monitoring) include an integration for reporting your [Microsoft Azure Web Apps](https://azure.microsoft.com/en-us/products/app-service/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. ## Features diff --git a/src/content/docs/logs/get-started/live-archives.mdx b/src/content/docs/logs/get-started/live-archives.mdx index 1f50fcd7800..8fdf63877ec 100644 --- a/src/content/docs/logs/get-started/live-archives.mdx +++ b/src/content/docs/logs/get-started/live-archives.mdx @@ -97,6 +97,10 @@ The live archives feature offers long-term log data storage that you intend to q ## Query your logs + + Users can query logs in live archives if they have the Live archives query [permission](/docs/accounts/accounts-billing/new-relic-one-user-management/user-permissions/). Refer to [user management concepts](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts/) for more information about using groups, roles, and permissions to control access to certain features. + + There are a few ways to query live archives: Lucene, NRQL, or NRQL in the NerdGraph API. For all three methods, you'll need the **Live archives query** capability to query live archives. ### Query live archives with Lucene query syntax [#query] diff --git a/src/content/docs/logs/ui-data/parsing.mdx b/src/content/docs/logs/ui-data/parsing.mdx index d6879442dcb..88f9f3bff3a 100644 --- a/src/content/docs/logs/ui-data/parsing.mdx +++ b/src/content/docs/logs/ui-data/parsing.mdx @@ -544,7 +544,7 @@ Note that variable names must be explicitly set and be lowercase like `%{URI:uri > The New Relic logs pipeline parses your log messages by default, but sometimes you have log messages that are formatted as key-value pairs. In this situation, you may want to be able to parse them and then be able to filter using the key-value attributes. - If that is the case, you can use the `key value pairs` [grok type](#grok-syntax), which will parse the key-value pairs captured by the grok pattern. This format relies on 3 main parts: the grok syntax, the prefix you would like to assign to the parsed key-value attributes, and the `key value pairs` [grok type](#grok-syntax). Using the `key value pairs` [grok type](#grok-syntax), you can extract and parse key-value pairs from logs that are not properly formatted; for example, if your logs are prefixed with a date/time string: + If that is the case, you can use the `keyvalue` [grok type](#grok-syntax), which will parse the key-value pairs captured by the grok pattern. This format relies on 3 main parts: the grok syntax, the prefix you would like to assign to the parsed key-value attributes, and the `keyvalue` [grok type](#grok-syntax). Using the `keyvalue` [grok type](#grok-syntax), you can extract and parse key-value pairs from logs that are not properly formatted; for example, if your logs are prefixed with a date/time string: ```json 2015-05-13T23:39:43.945958Z key1=value1,key2=value2,key3=value3 @@ -623,9 +623,9 @@ Note that variable names must be explicitly set and be lowercase like `%{URI:uri You can customize the parsing behavior with the following options to suit your log formats: * **delimiter** - * **Description:** String separating each key-value pair. - * **Default Value:** `,` (comma) - * **Override:** Set the field `delimiter` to change this behavior. + * **Description:** String separating each key-value pair. + * **Default Value:** `,` (comma) + * **Override:** Set the field `delimiter` to change this behavior. * **keyValueSeparator** * **Description:** String used to assign values to keys. diff --git a/src/content/docs/network-performance-monitoring/setup-performance-monitoring/snmp-performance-monitoring.mdx b/src/content/docs/network-performance-monitoring/setup-performance-monitoring/snmp-performance-monitoring.mdx index aac1d99fd6f..92fdf3c4682 100755 --- a/src/content/docs/network-performance-monitoring/setup-performance-monitoring/snmp-performance-monitoring.mdx +++ b/src/content/docs/network-performance-monitoring/setup-performance-monitoring/snmp-performance-monitoring.mdx @@ -62,7 +62,7 @@ It's recommended to deploy the SNMP monitoring agent as a container for either D * Debian 12 (Bookworm) * Debian 11 (Bullseye) * Debian 10 (Buster) - * RedHat Enterprise Linux 9 + * RedHat Enterprise Linux 9 up to 9.5 * Ubuntu 20.04 (Focal LTS) * Ubuntu 22.04 (Jammy LTS) * Ubuntu 23.04 (Lunar) diff --git a/src/content/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1560.mdx b/src/content/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1560.mdx new file mode 100644 index 00000000000..ae77c4922db --- /dev/null +++ b/src/content/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1560.mdx @@ -0,0 +1,12 @@ +--- +subject: Infrastructure agent +releaseDate: '2024-08-13' +version: 1.56.0 +--- + +We've released a new version of the agent. Follow standard procedures to [update the Infrastructure agent](https://docs.newrelic.com/docs/infrastructure/install-configure-manage-infrastructure/update-or-uninstall/update-infrastructure-agent). +New Relic recommends that you upgrade the agent regularly, every 3 months at a minimum. As of this release, the oldest supported version is [Infrastructure agent 1.46.0](https://docs.newrelic.com/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1460/). + +## Added + +* Add support to Fluent Bit 3 on Windows [#1909](https://github.com/newrelic/infrastructure-agent/pull/1909) diff --git a/src/content/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1600.mdx b/src/content/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1600.mdx index ae77c4922db..96c5a8db8ee 100644 --- a/src/content/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1600.mdx +++ b/src/content/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1600.mdx @@ -1,12 +1,13 @@ --- subject: Infrastructure agent -releaseDate: '2024-08-13' -version: 1.56.0 +releaseDate: '2024-01-20' +version: 1.60.0 --- -We've released a new version of the agent. Follow standard procedures to [update the Infrastructure agent](https://docs.newrelic.com/docs/infrastructure/install-configure-manage-infrastructure/update-or-uninstall/update-infrastructure-agent). -New Relic recommends that you upgrade the agent regularly, every 3 months at a minimum. As of this release, the oldest supported version is [Infrastructure agent 1.46.0](https://docs.newrelic.com/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1460/). +A new version of the agent has been released. Follow standard procedures to [update the Infrastructure agent](https://docs.newrelic.com/docs/infrastructure/install-configure-manage-infrastructure/update-or-uninstall/update-infrastructure-agent). +New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is [Infrastructure agent 1.49.0](https://docs.newrelic.com/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1490/). ## Added -* Add support to Fluent Bit 3 on Windows [#1909](https://github.com/newrelic/infrastructure-agent/pull/1909) +* Add labels from nri-winservices config as tags on UI in [#1989](https://github.com/newrelic/infrastructure-agent/pull/1989). +* FIPS compatible packages for Linux. diff --git a/src/content/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-33-0.mdx b/src/content/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-33-0.mdx new file mode 100644 index 00000000000..62375ecfe1a --- /dev/null +++ b/src/content/docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-33-0.mdx @@ -0,0 +1,11 @@ +--- +subject: Kubernetes integration +releaseDate: '2025-01-21' +version: 3.33.0 +--- + +For a detailed description of changes, see the [release notes](https://github.com/newrelic/nri-kubernetes/releases/tag/v3.33.0). + +This integration is included in the following chart versions: +* [newrelic-infrastructure-3.38.0](https://github.com/newrelic/nri-kubernetes/releases/tag/newrelic-infrastructure-3.38.0) +* [nri-bundle-5.0.107](https://github.com/newrelic/helm-charts/releases/tag/nri-bundle-5.0.107) diff --git a/src/content/docs/security/security-privacy/compliance/certificates-standards-regulations/DORA Subcontractors.mdx b/src/content/docs/security/security-privacy/compliance/certificates-standards-regulations/DORA Subcontractors.mdx new file mode 100644 index 00000000000..7c822659193 --- /dev/null +++ b/src/content/docs/security/security-privacy/compliance/certificates-standards-regulations/DORA Subcontractors.mdx @@ -0,0 +1,83 @@ +--- +title: New Relic Digital Operational Resilience Act (DORA) Subcontractor +tags: + - Security + - Security and Privacy + - Compliance + - DORA Subcontractors +metaDescription: List of New Relic subcontracors for DORA purposes. +freshnessValidatedDate: never +--- + +
- The duration of the aggregation phase in the ingestion flow. + The duration of the aggregation phase in the ingestion flow.
- The count of pushes that failed because the ChannelURI in the registration was disconnected (MPNS status: 412 not found). + The count of pushes that failed because the ChannelURI in the registration was disconnected (MPNS status: 412 not found).
- Resource utilization expressed as a percentage. High utilization indicates that the job is using close to the maximum allocated resources. + Resource utilization expressed as a percentage. High utilization indicates that the job is using close to the maximum allocated resources.
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Subcontractor + + Service Location + + Service Provided +
+ Amazon Web Services (AWS) + + Data storage & diagnostics + + Multiple Worldwide +
+ Google Cloud Platform (GCP) + + Data storage & diagnostics + + For more information on GCP and its subcontractors, including locations see [Google Cloud Platform Subprocessors](https://cloud.google.com/terms/subprocessors) +
+ Microsoft Azure + + Cloud computing, storage & related features + + United States +
+ Cloudflare + + Traffic routing, TLS Termination & security services + + Global. See [Cloudflare](https://cloudflare.com/network/) for more information. +
+ Fastly + + Traffic routing, TLS Termination + + Global. See [Fastly](https://www.fastly.com/network-map/) for more information. +
diff --git a/src/content/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx b/src/content/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx index ee89fcf7e80..3c1c940ba24 100644 --- a/src/content/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx +++ b/src/content/docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring.mdx @@ -144,8 +144,6 @@ Ensure that you add a comma at the end of the last existing line and update your "value": "info", "slotSetting": false }, - - ``` diff --git a/src/content/whats-new/2025/01/whats-new-01-17-cross-account-alerts.md b/src/content/whats-new/2025/01/whats-new-01-17-cross-account-alerts.md new file mode 100644 index 00000000000..1d4f76c0f50 --- /dev/null +++ b/src/content/whats-new/2025/01/whats-new-01-17-cross-account-alerts.md @@ -0,0 +1,32 @@ +--- +title: 'Configure cross account alerts for improved organization and manageability' +summary: 'Alert conditions can now target data in another account' +releaseDate: '2025-01-16' +learnMoreLink: 'https://docs.newrelic.com/docs/alerts/create-alert/create-alert-condition/cross-account-alert/' +--- + +In many organizations, different teams or departments may use separate New Relic accounts to organize their data. The new cross-account alert condition feature now enables users to create and manage an alert condition in one account that targets data residing in another account. + +## Key benefits + +* **Consolidated alerts management**: Manage alerts across multiple accounts you have access to, enabling a unified view of all relevant incidents and issues. +* **Enhanced security**: Limit write and edit access to sensitive accounts, minimizing the need for multiple users to have permissions on accounts they do not directly manage. +* **Efficient alert organization**: Reduce unnecessary alerts on accounts that serve as data sources for others. +* **Delegated governance**: Delegate alert threshold management and governance to the appropriate teams, easing the burden on account owners. +* **Timely Notifications**: Ensure timely alerts for critical dependencies, even if they reside in different New Relic accounts. + +## Example + +Consider an application team dependent on the host their application runs on, with the application team鈥檚 data in a separate account from the host data. + +Once data sharing is enabled on the host data鈥檚 account, the application team can create an alert condition within their own account targeting the host鈥檚 data. This allows the application team to manage their own alert conditions and notifications, ensuring they are informed of any host issues. The team managing the host data鈥檚 account does not need to manage these alert conditions on behalf of the application team. + +## Get started + +To use cross-account conditions, an organization manager must decide which accounts can share data for cross-account alerts. They need to opt-in those accounts via the **Alerts > Settings** page or the [cross account enablement API](https://docs.newrelic.com/docs/apis/nerdgraph/examples/nerdgraph-api-cross-account-alerting-elections/) + +!["Screenshot showing account opt in for data sharing for cross account alerts"](/images/cross_account_alerts_opt_in.webp "Screenshot showing account opt in for data sharing for cross account alerts") + +This feature is available only on the new NRQL alert conditions through the **Query Mode** form. This field is located in the **Tell us where to look** section of the form above the query box. It can also be edited using the alert condition APIs and in our latest Terraform provider. For more details, refer to [Cross-account alert](https://docs.newrelic.com/docs/alerts/create-alert/create-alert-condition/cross-account-alert/). + +!["Screenshot showing cross account alert configuration"](/images/cross_account_alert_config.webp "Screenshot showing cross account alert configuration") 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 index 8bfad14b50a..abaa06274e2 100644 --- 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 @@ -1,7 +1,7 @@ --- title: "REST API Keys End-of-life" summary: "Retiring the REST API key to improve security and reliability." -releaseDate: "2025-03-01" +releaseDate: "2025-01-17" learnMoreLink: "https://docs.newrelic.com/docs/apis/intro-apis/new-relic-api-keys/" --- diff --git a/src/data/whats-new-ids.json b/src/data/whats-new-ids.json index 8f51c1b7c93..9761f991ed3 100644 --- a/src/data/whats-new-ids.json +++ b/src/data/whats-new-ids.json @@ -357,5 +357,6 @@ "/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" + "/whats-new/2025/01/whats-new-01-17-cross-account-alerts": "43017", + "/whats-new/2025/01/whats-new-03-01-rest-api-keys-eol": "43018" } \ No newline at end of file diff --git a/src/i18n/content/es/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx b/src/i18n/content/es/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx index 39878a267fc..f1b3de37262 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 @@ -538,8 +538,10 @@ Para el marco y la biblioteca que no se [instrumentan autom谩ticamente](#instrum * Versi贸n m铆nima compatible: 3.5.0 + * 脷ltima versi贸n compatible verificada: 3.7.405.0 + * Versi贸n m铆nima del agente requerida: 10.33.0 @@ -632,6 +634,7 @@ Para el marco y la biblioteca que no se [instrumentan autom谩ticamente](#instrum 3.7.411.17 + @@ -731,7 +734,7 @@ Para el marco y la biblioteca que no se [instrumentan autom谩ticamente](#instrum - 9.0.0 + 9.0.1 @@ -787,7 +790,7 @@ Para el marco y la biblioteca que no se [instrumentan autom谩ticamente](#instrum * Versi贸n m铆nima soportada: 5.0 - * 脷ltima versi贸n compatible verificada: 9.2.3 + * Latest verified compatible version: 9.2.4 @@ -842,6 +845,7 @@ Para el marco y la biblioteca que no se [instrumentan autom谩ticamente](#instrum * Versi贸n m铆nima compatible: 3.7.0 * 脷ltima versi贸n compatible verificada: 3.7.400.76 + @@ -1452,6 +1456,7 @@ Para el marco y la biblioteca que no se [instrumentan autom谩ticamente](#instrum * 脷ltima versi贸n compatible verificada: 3.7.405.2 + * Versi贸n m铆nima del agente requerida: 10.33.0 @@ -1602,6 +1607,7 @@ Para el marco y la biblioteca que no se [instrumentan autom谩ticamente](#instrum 3.7.411.17 + @@ -1701,7 +1707,7 @@ Para el marco y la biblioteca que no se [instrumentan autom谩ticamente](#instrum - 9.0.0 + 9.0.1 @@ -1820,6 +1826,7 @@ Para el marco y la biblioteca que no se [instrumentan autom谩ticamente](#instrum * Versi贸n m铆nima compatible: 3.7.0 * 脷ltima versi贸n compatible verificada: 3.7.400.76 + 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 fc569879bcb..72566b0a7af 100644 --- a/src/i18n/content/es/docs/logs/ui-data/parsing.mdx +++ b/src/i18n/content/es/docs/logs/ui-data/parsing.mdx @@ -504,7 +504,7 @@ Tenga en cuenta que los nombres de las variables deben establecerse expl铆citame La canalizaci贸n de logs de New Relic analiza su mensaje de log de manera predeterminada, pero a veces tiene mensajes de log que est谩n formateados como pares principales de valores. En esta situaci贸n, es posible que desees poder analizarlos y luego filtrarlos empleando el atributo valor principal. - Si ese es el caso, puedes usar el [tipo grok](#grok-syntax) `key value pairs` , que analizar谩 los pares principales de valor capturados por el patr贸n grok. Este formato se basa en tres partes principales: la sintaxis de grok, el prefijo que desea asignar al atributo valor principal analizado y el [tipo de grok](#grok-syntax) `key value pairs` . Al emplear el [tipo grok](#grok-syntax) `key value pairs` , puede extraer y analizar pares principales de valor de logs que no tienen el formato correcto; por ejemplo, si sus logs tienen como prefijo una cadena de fecha y hora: + Si ese es el caso, puedes usar el [tipo grok](#grok-syntax) `keyvalue` , que analizar谩 los pares principales de valor capturados por el patr贸n grok. Este formato se basa en tres partes principales: la sintaxis de grok, el prefijo que desea asignar al atributo valor principal analizado y el [tipo de grok](#grok-syntax) `keyvalue` . Al emplear el [tipo grok](#grok-syntax) `keyvalue` , puede extraer y analizar pares principales de valor de logs que no tienen el formato correcto; por ejemplo, si sus logs tienen como prefijo una cadena de fecha y hora: ```json 2015-05-13T23:39:43.945958Z key1=value1,key2=value2,key3=value3 @@ -583,11 +583,9 @@ Tenga en cuenta que los nombres de las variables deben establecerse expl铆citame * **delimitador** - * **Descripci贸n:** Cadena que separa cada par principal de valores. - - * **Valor predeterminado:** `,` (coma) - - * **Anular:** establezca el campo `delimiter` para cambiar este comportamiento. + * **Descripci贸n:** Cadena que separa cada par principal de valores. + * **Valor predeterminado:** `,` (coma) + * **Anular:** establezca el campo `delimiter` para cambiar este comportamiento. * **separador de valor-clave** diff --git a/src/nav/browser.yml b/src/nav/browser.yml index 3e2aa8b932b..3bbdc7a9151 100644 --- a/src/nav/browser.yml +++ b/src/nav/browser.yml @@ -137,6 +137,8 @@ pages: path: /docs/browser/new-relic-browser/browser-apis/noticeerror - title: pauseReplay path: /docs/browser/new-relic-browser/browser-apis/pauseReplay + - title: recordCustomEvent + path: /docs/browser/new-relic-browser/browser-apis/recordCustomEvent - title: recordReplay path: /docs/browser/new-relic-browser/browser-apis/recordReplay - title: setApplicationVersion diff --git a/static/images/cross_account_alert_config.webp b/static/images/cross_account_alert_config.webp new file mode 100644 index 00000000000..190c3f64f38 Binary files /dev/null and b/static/images/cross_account_alert_config.webp differ diff --git a/static/images/cross_account_alerts_opt_in.webp b/static/images/cross_account_alerts_opt_in.webp new file mode 100644 index 00000000000..5de377a3a8c Binary files /dev/null and b/static/images/cross_account_alerts_opt_in.webp differ