Merge branch 'develop' into pr/17742

newrelic · Jun 24, 2024 · fe2a136 · fe2a136
2 parents c0a0da6 + 4736296
commit fe2a136
Show file tree

Hide file tree

Showing 228 changed files with 1,542 additions and 28,855 deletions.
diff --git a/...tegrations/best-practices-integration.mdx → ...management/best-practices-integration.mdx b/...tegrations/best-practices-integration.mdx → ...management/best-practices-integration.mdx
@@ -1,10 +1,12 @@
 ---
 title: Best practices for integration users
 tags:
-    - Best practices
-    - Integrations
-metaDescription: "Here are some best practices for controlling how you expose your New Relic data when you're using an integration."
-freshnessValidatedDate: 2024-04-24
+  - Best practices
+  - Integrations
+metaDescription: Here are some best practices for controlling how you expose your New Relic data when you're using an integration.
+freshnessValidatedDate: 2024-04-24T00:00:00.000Z
+redirects:
+  - /docs/more-integrations/best-practices-integration
 ---
 
 As a New Relic administrator, you must operate your New Relic organization with the principle of least privilege. This principle is a security concept in which a user should only have access to the specific data, systems, and resources needed to complete a necessary task for the organization. By following this principle, you can reduce the risk of unauthorized access to sensitive data. This includes assigning permissions based on job roles and responsibilities. In a [New Relic organization](/docs/accounts/accounts-billing/account-structure/new-relic-account-structure/), account-based access allows you to control what information is available to the users in your organization. This ensures that sensitive data remains secure and only authorized personnel can view it. 

diff --git a/...ocs/alerts/create-alert/create-alert-condition/create-nrql-alert-conditions.mdx b/...ocs/alerts/create-alert/create-alert-condition/create-nrql-alert-conditions.mdx
@@ -14,6 +14,7 @@ redirects:
   - /docs/alerts/new-relic-alerts/configuring-alert-policies/create-alert-conditions-nrql-queries
   - /docs/alerts/new-relic-alerts/defining-conditions/create-alert-conditions-nrql-queries
   - /docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/create-nrql-alert-conditions
+  - /docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/queries-nrql_screenshot-full_nrql-alert-conditions/
 freshnessValidatedDate: never
 ---
 

diff --git a/...ations/dropwizard/dropwizard-reporter.mdx → ...ations/dropwizard/dropwizard-reporter.mdx b/...ations/dropwizard/dropwizard-reporter.mdx → ...ations/dropwizard/dropwizard-reporter.mdx
@@ -9,6 +9,7 @@ redirects:
   - /docs/integrations/open-source-telemetry-integrations/dropwizard/dropwizard-reporter
   - /docs/integrations/exporters/exporter-list/new-relics-dropwizard-integration
   - /docs/integrations/open-source-telemetry-integrations/open-source-telemetry-integration-list/new-relics-dropwizard-integration
+  - /docs/more-integrations/open-source-telemetry-integrations/dropwizard/dropwizard-reporter
 freshnessValidatedDate: never
 ---
 

diff --git a/...try-integrations/kamon/kamon-reporter.mdx → ...rty-integrations/kamon/kamon-reporter.mdx b/...try-integrations/kamon/kamon-reporter.mdx → ...rty-integrations/kamon/kamon-reporter.mdx
@@ -8,6 +8,7 @@ metaDescription: New Relic's Kamon reporter can send telemetry data from your Ka
 redirects:
   - /docs/integrations/open-source-telemetry-integrations/kamon/kamon-reporter
   - /docs/integrations/open-source-telemetry-integrations/open-source-telemetry-integration-list/kamon-reporter
+  - /docs/more-integrations/open-source-telemetry-integrations/kamon/kamon-reporter
 freshnessValidatedDate: never
 ---
 

diff --git a/...icrometer/micrometer-metrics-registry.mdx → ...icrometer/micrometer-metrics-registry.mdx b/...icrometer/micrometer-metrics-registry.mdx → ...icrometer/micrometer-metrics-registry.mdx
@@ -2,8 +2,9 @@
 title: Forward Micrometer data to New Relic with OpenTelemetry
 metaDescription: New Relic offers an integration that sends your Micrometer telemetry data to your New Relic account.
 redirects:
-    - /docs/integrations/open-source-telemetry-integrations/micrometer/micrometer-metrics-registry
-    - /docs/integrations/open-source-telemetry-integrations/open-source-telemetry-integration-list/new-relics-micrometer-integration
+  - /docs/integrations/open-source-telemetry-integrations/micrometer/micrometer-metrics-registry
+  - /docs/integrations/open-source-telemetry-integrations/open-source-telemetry-integration-list/new-relics-micrometer-integration
+  - /docs/more-integrations/open-source-telemetry-integrations/micrometer/micrometer-metrics-registry
 freshnessValidatedDate: never
 ---
 

diff --git a/...tegrations/vertx-eventbus-integration.mdx → ...ions/vertx/vertx-eventbus-integration.mdx b/...tegrations/vertx-eventbus-integration.mdx → ...ions/vertx/vertx-eventbus-integration.mdx
@@ -11,6 +11,8 @@ tags:
   - expert services
 metaDescription: Provides instrumentation for monitoring the Vert.x Event Bus.
 freshnessValidatedDate: never
+redirects:
+  - /docs/more-integrations/java-integrations/vertx-eventbus-integration
 ---
 
 [Java Vert.x Event Bus Integration](https://github.com/newrelic/newrelic-java-vertx/tree/main) provides instrumentation for monitoring the (Vert.x)[https://vertx.io/] Event Bus, enabling the tracking of event flow across the bus. Specifically designed for Vert.x Verticles that extend` AbstractVerticle`, this extension instruments each deployed class to monitor all methods except those specifically defined by `AbstractVerticle`.
@@ -150,4 +152,4 @@ From [Java Vert.x Event Bus Integration Releases](https://github.com/newrelic/ne
 After configuring the Java Vert.x Event Bus Integration, you can visualize your application's Vert.x Event Bus transactions and traces directly within New Relic APM and Services.
 
 ## Reporting Integration Issues
-If you encounter any issues with the Java Vert.x Event Bus Integration, please report them on the [GitHub repository](https://github.com/newrelic/newrelic-java-vertx/issues). Your feedback helps us identify and address issues promptly, ensuring a smooth and reliable monitoring experience for Vert.x applications. Thank you for contributing to the improvement of our integration.
+If you encounter any issues with the Java Vert.x Event Bus Integration, please report them on the [GitHub repository](https://github.com/newrelic/newrelic-java-vertx/issues). Your feedback helps us identify and address issues promptly, ensuring a smooth and reliable monitoring experience for Vert.x applications. Thank you for contributing to the improvement of our integration.
diff --git a/...grations/vertx-extensions-integration.mdx → ...ns/vertx/vertx-extensions-integration.mdx b/...grations/vertx-extensions-integration.mdx → ...ns/vertx/vertx-extensions-integration.mdx
@@ -22,9 +22,10 @@ tags:
   - reactive
   - coroutines
   - expert services
-metaDescription: provides instrumentation for monitoring the Vert.x Cassandra, JDBCClient, Coroutines, Kafka, 
-      RxJava, SQL Clients, Redis, MongoDB, Reactive and Service Proxy.
+metaDescription: provides instrumentation for monitoring the Vert.x Cassandra, JDBCClient, Coroutines, Kafka, RxJava, SQL Clients, Redis, MongoDB, Reactive and Service Proxy.
 freshnessValidatedDate: never
+redirects:
+  - /docs/more-integrations/java-integrations/vertx-extensions-integration
 ---
 
 [Java Instrumentation for Vert.x Extensions](https://github.com/newrelic/newrelic-java-vertx-extensions/tree/main) provides instrumentation for monitoring Vert.x Cassandra, JDBCClient, Coroutines, Kafka, RxJava, SQL Clients, Redis, MongoDB, Reactive and Service Proxy.
@@ -153,4 +154,4 @@ Remove-Item -Path $tempExtractPath -Recurse -Force
 After configuring the Java Instrumentation for Vert.x Extensions, you can visualize your application's Vert.x extensions transactions and traces directly within New Relic APM and Services.
 
 ## Reporting Integration Issues
-If you encounter any issues with the Java Instrumentation for Vert.x Extensions, please report them on the [GitHub repository](https://github.com/newrelic/newrelic-java-vertx-extensions/issues). Your feedback helps us identify and address issues promptly, ensuring a smooth and reliable monitoring experience for Vert.x applications. Thank you for contributing to the improvement of our integration!
+If you encounter any issues with the Java Instrumentation for Vert.x Extensions, please report them on the [GitHub repository](https://github.com/newrelic/newrelic-java-vertx-extensions/issues). Your feedback helps us identify and address issues promptly, ensuring a smooth and reliable monitoring experience for Vert.x applications. Thank you for contributing to the improvement of our integration!
diff --git a/...agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx b/...agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx
@@ -190,7 +190,7 @@ The following are proposed time ranges for EOL on older Node.js versions. The ac
 
 
 {/* begin: compat-table */}
-## Instrumented modules
+## Instrumented modules [#instrumented-modules]
 
 After installation, the agent automatically instruments with our catalog of
 supported Node.js libraries and frameworks. This gives you immediate access to

diff --git a/...press/wordpress-fullstack-integration.mdx → ...aries/wordpress-fullstack-integration.mdx b/...press/wordpress-fullstack-integration.mdx → ...aries/wordpress-fullstack-integration.mdx
@@ -1,12 +1,13 @@
 ---
-title: WordPress Full Stack integration
+title: WordPress full stack integration
 tags:
-    - New Relic integrations
-    - WordPress Full Stack integration
+  - New Relic integrations
+  - WordPress full stack integration
 metaDescription: Use New Relic browser monitoring to get a dashboard with metrics from your Wordpress.
-redirects: 
+redirects:
   - /docs/infrastructure/host-integrations/host-integrations-list/wordpress-fullstack-integration
-freshnessValidatedDate: 2023-06-28
+  - /docs/more-integrations/open-source-telemetry-integrations/wordpress/wordpress-fullstack-integration
+freshnessValidatedDate: 2023-06-28T00:00:00.000Z
 ---
 
 import infrastructureWordPressIntegrationDashboard from 'images/infrastructure_screenshot-full_wordpress-dashboard.webp'

diff --git a/...tions/elixir/elixir-open-source-agent.mdx → ...gents/elixir/elixir-open-source-agent.mdx b/...tions/elixir/elixir-open-source-agent.mdx → ...gents/elixir/elixir-open-source-agent.mdx
@@ -10,10 +10,11 @@ redirects:
   - /docs/introduction-new-relic-elixir
   - /docs/elixir-open-source-agent
   - /docs/agents/open-source-licensed-agents/elixir-open-source-agent/
+  - /docs/more-integrations/open-source-telemetry-integrations/elixir/elixir-open-source-agent
 freshnessValidatedDate: never
 ---
 
-Monitor [Elixir](https://github.com/newrelic/elixir_agent) behavior with New Relic using the Elixir open-source agent. The agent:
+Monitor [Elixir](https://github.com/newrelic/elixir_agent) behavior with New Relic using the Elixir open-source agent. This experimental agent:
 
 * Helps you track transactions, distributed traces, and other parts of your application’s behavior
 * Provides an overview of underlying [BEAM](http://erlang.org/faq/implementations.html#idp32950544) activity

diff --git a/...integrations/dojo/dojo-io-integration.mdx → ...wser-integrations/dojo-io-integration.mdx b/...integrations/dojo/dojo-io-integration.mdx → ...wser-integrations/dojo-io-integration.mdx
@@ -1,12 +1,13 @@
 ---
 title: Dojo.io integration
 tags:
-    - dojo.io integration
-    - dojo integration
-    - new relic integrations
-metaDescription: "The New Relic Dojo.io integration sends performance metrics and inventory data from your Dojo.io framework to the New Relic platform."
-redirects: 
+  - dojo.io integration
+  - dojo integration
+  - new relic integrations
+metaDescription: The New Relic Dojo.io integration sends performance metrics and inventory data from your Dojo.io framework to the New Relic platform.
+redirects:
   - /docs/infrastructure/host-integrations/host-integrations-list/dojo-io-integration
+  - /docs/more-integrations/open-source-telemetry-integrations/dojo/dojo-io-integration
 freshnessValidatedDate: never
 ---
 import dojodashboard from 'images/infrastructure_screenshot-crop_dojo-dashboard.webp'

diff --git a/src/content/docs/iast/troubleshooting.mdx b/src/content/docs/iast/troubleshooting.mdx
@@ -17,7 +17,7 @@ If you don't find your problem listed here, you can always reach out to [New Rel
     id="iast-results"
     title="Where do I find IAST results?"
     >
-    Go to <DoNotTranslate>**[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > Tests & Applications**</DoNotTranslate>. Click on an application to check the application testing efficiency, vulnerabilities, APIs covered, and methods calls, amongst other data.
+    Go to <DoNotTranslate>**[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > Tests**</DoNotTranslate>. Click on an application to check the application testing efficiency, vulnerabilities, APIs covered, and methods calls, amongst other data.
 
     </Collapser>
 
@@ -38,9 +38,9 @@ If you don't find your problem listed here, you can always reach out to [New Rel
 
     If you can see your application in the New Relic UI and the security agent successfully started IAST, but you don't see vulnerabilities in the UI, check the following:
 
-    - The level of efficiency for your application: Go to <DoNotTranslate>**[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > Tests & Applications**</DoNotTranslate>. Search for your application and check the summary section. If IAST coverage is low for your application, add additional test cases to your application to get a higher level of testing efficiency.
+    - The level of efficiency for your application: Go to <DoNotTranslate>**[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > Tests**</DoNotTranslate>. Search for your application and check the summary section. If IAST coverage is low for your application, add additional test cases to your application to get a higher level of testing efficiency.
 
-    - The IAST coverage: Go to <DoNotTranslate>**[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > Tests & Applications**</DoNotTranslate>. Search for your application and click on it. Under the summary section, check if IAST analysis coverage is high and no vulnerabilities are detected, that means your application is secure.
+    - The IAST coverage: Go to <DoNotTranslate>**[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > Tests**</DoNotTranslate>. Search for your application and click on it. Under the summary section, check if IAST analysis coverage is high and no vulnerabilities are detected, that means your application is secure.
 
     - Your application's framework or vulnerability category is not supported. 
 
@@ -52,15 +52,16 @@ If you don't find your problem listed here, you can always reach out to [New Rel
     id="see-my-application"
     title="I don't see my application in IAST"
     >
-    If you don't see your application in <DoNotTranslate>**[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > Tests & Applications**</DoNotTranslate>, check the following:
+    If you don't see your application in <DoNotTranslate>**[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > Tests**</DoNotTranslate>, check the following:
 
     - Your application is up and running: Check the application process or the [APM & Services page](/docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/advanced-techniques/view-events-their-products#products). 
     - The application's logs to find out if there's a problem.
     - The version of your APM agent and udpate it if needed.
     - The `newrelic.yml` config file includes the modification of the parameters as indicated on the [install page](/docs/iast/install).
     - Go to the `nr-security-home/logs` directory and find the `[SETP-8]` line in the `LANGUAGE-security-collector-init.log` file. Check if there is an unexpected error and know what failed.
     - The application has traffic. Generate some traffic to allow IAST to test your application.
-    - The TLS Certificate is correct.
+    - Proxy or Firewall blocking access. Whitelist the following IPs `3.134.136.130, 18.219.177.104, 18.117.21.106` for the domain <DoNotTranslate>**csec.nr-data.net**</DoNotTranslate>, the following IPs `3.130.22.102, 3.138.243.136, 3.139.218.150` for the domain <DoNotTranslate>**csec-gov.nr-data.net**</DoNotTranslate> and the following IPs `18.185.235.118, 3.125.193.113, 3.75.166.122` for the domain <DoNotTranslate>**csec.eu01.nr-data.net**</DoNotTranslate>. But our recommendation is to add domains in the whitelist instead of the IPs as these IPs are bound to change anytime.
+    - The TLS Certificate is correct. Add Let's Encrypt CA certificate (download from [Let's Encrypt Certificates](https://letsencrypt.org/certificates/#root-certificates)) to your local trust store. Include both the root certificates and the intermediate ones (ISRG Root X1 & Let's Encrypt R3) to establish the complete chain of trust.
     - Your application's framework or vulnerability category is supported.
 
     </Collapser>
@@ -78,7 +79,7 @@ If you don't find your problem listed here, you can always reach out to [New Rel
 
     When the security agent is working correctly:
 
-    - You see your application in <DoNotTranslate>**[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > Tests & Applications**</DoNotTranslate>. The application is started and there is traffic generated.
+    - You see your application in <DoNotTranslate>**[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > Tests**</DoNotTranslate>. The application is started and there is traffic generated.
     - In the `nr-security-home/logs` directory, search for the `LANGUAGE-security-collector-init.log` file. Replace `LANGUAGE` in the filename with the one you are using. Search for these steps to see where the problem is:
         - [STEP-1]: The security agent is starting.
         - [STEP-2]: The security agent generates a unique identifier. For web socket connection, you'll see Node auth headers.
@@ -107,7 +108,7 @@ If you don't find your problem listed here, you can always reach out to [New Rel
 
     You can check if IAST is working, even if you're seeing your application in the IAST UI and the security agent started successfully. Follow these steps for checking it:
 
-    1. Go to <DoNotTranslate>**[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > Tests & Applications**</DoNotTranslate>.
+    1. Go to <DoNotTranslate>**[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > Tests**</DoNotTranslate>.
 
     2. Search for your application in the <DoNotTranslate>**Application tests**</DoNotTranslate> tab and click on it.
 
@@ -187,7 +188,7 @@ If you don't find your problem listed here, you can always reach out to [New Rel
 
     Update the status of your vulnerability if you think IAST has reported a false positive. Follow these steps:
 
-    - Search your application: Go to <DoNotTranslate>**[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > Tests & Applications**</DoNotTranslate>.
+    - Search your application: Go to <DoNotTranslate>**[one.newrelic.com](https://one.newrelic.com) > All capabilities > IAST > Tests**</DoNotTranslate>.
 
     - Click on the all applications tab and select the vulnerability that is not an actual vulnerability.
 
@@ -229,7 +230,7 @@ If you don't find your problem listed here, you can always reach out to [New Rel
     ```
 
     <Callout variant="important">
-        You can skip this step if you're on a linux environment.
+        You can skip this step if you're on a Linux environment.
     </Callout>
 
     - For a specific case of <DoNotTranslate>**Outbound HTTP Request**</DoNotTranslate> or calls to external services, you need to [update your application method](/docs/apm/agents/go-agent/instrumentation/instrument-go-segments/#go-external-segments).

diff --git a/...ntegrations/terraform/terraform-intro.mdx → ...ure-as-code/terraform/terraform-intro.mdx b/...ntegrations/terraform/terraform-intro.mdx → ...ure-as-code/terraform/terraform-intro.mdx
@@ -1,7 +1,9 @@
 ---
-title: 'Getting started with New Relic and Terraform'
-metaDescription: 'Learn how to provision New Relic resources using [Terraform](https://www.terraform.io/).'
+title: Getting started with New Relic and Terraform
+metaDescription: Learn how to provision New Relic resources using [Terraform](https://www.terraform.io/).
 freshnessValidatedDate: never
+redirects:
+  - /docs/more-integrations/terraform/terraform-intro
 ---
 
 [Terraform](https://www.terraform.io/) is a popular infrastructure-as-code software tool built by HashiCorp. You use it to provision all kinds of infrastructure and services, including New Relic <InlinePopover type="dashboards" /> and alerts.

diff --git a/...egrations/terraform/terraform-modules.mdx → ...e-as-code/terraform/terraform-modules.mdx b/...egrations/terraform/terraform-modules.mdx → ...e-as-code/terraform/terraform-modules.mdx
@@ -1,8 +1,10 @@
 ---
-title: 'Using Terraform Modules and Remote Storage'
-template: 'GuideTemplate'
-metaDescription: 'Learn how to use [Terraform](https://www.terraform.io/) modules in your configurations and store them remotely.'
+title: Using Terraform Modules and Remote Storage
+template: GuideTemplate
+metaDescription: Learn how to use [Terraform](https://www.terraform.io/) modules in your configurations and store them remotely.
 freshnessValidatedDate: never
+redirects:
+  - /docs/more-integrations/terraform/terraform-modules
 ---
 
 [Terraform](https://www.terraform.io/) is a popular infrastructure-as-code software tool built by HashiCorp. You use it to provision all kinds of infrastructure and services, including New Relic dashboards and alerts.

diff --git a/...ore-integrations/terraform/terragrunt.mdx → ...tructure-as-code/terraform/terragrunt.mdx b/...ore-integrations/terraform/terragrunt.mdx → ...tructure-as-code/terraform/terragrunt.mdx
@@ -1,9 +1,11 @@
 ---
-title: 'Using Terragrunt to Manage Multiple Environments'
-metaDescription: 'Learn how to use [Terragrunt](https://www.terraform.io/) to manage configurations in multiple environments'
+title: Using Terragrunt to Manage Multiple Environments
+metaDescription: Learn how to use [Terragrunt](https://www.terraform.io/) to manage configurations in multiple environments
 translate:
   - kr
 freshnessValidatedDate: never
+redirects:
+  - /docs/more-integrations/terraform/terragrunt
 ---
 
 [Terraform](https://www.terraform.io/) is a popular infrastructure-as-code software tool built by HashiCorp. You use it to provision all kinds of infrastructure and services, including New Relic <InlinePopover type="dashboards" /> and alerts.