Merged main into main-jp

newrelic · Oct 22, 2024 · ae323ec · ae323ec
2 parents 9b62419 + a9f8d4f
commit ae323ec
Show file tree

Hide file tree

Showing 152 changed files with 3,980 additions and 3,783 deletions.
diff --git a/package.json b/package.json
@@ -10,7 +10,7 @@
     "@emotion/styled": "^11.3.0",
     "@mdx-js/mdx": "2.0.0-next.8",
     "@mdx-js/react": "2.0.0-next.8",
-    "@newrelic/gatsby-theme-newrelic": "9.8.1",
+    "@newrelic/gatsby-theme-newrelic": "9.10.3",
     "@splitsoftware/splitio-react": "^1.2.4",
     "ansi-colors": "^4.1.3",
     "cockatiel": "^3.0.0-beta.0",

diff --git a/scripts/actions/webdriver-desktop.mjs b/scripts/actions/webdriver-desktop.mjs
@@ -98,7 +98,9 @@ const navTest = async () => {
 };
 
 const searchTest = async () => {
-  const [searchInput] = await waitForXPath('//aside//input');
+  const [searchInput] = await waitForXPath(
+    './/input[@placeholder="Search docs"]'
+  );
   console.log('\nClicking search input');
   await searchInput.click();
   const activeEl = await driver.executeScript('return document.activeElement');

diff --git a/scripts/actions/webdriver-mobile.mjs b/scripts/actions/webdriver-mobile.mjs
@@ -47,7 +47,8 @@ const main = async () => {
   await driver.get(testUrl + 'docs/mdx-test-page/');
   await navTest();
   await collapserTest();
-  await searchTest();
+  // TODO: reenable after fixing mobile search focus behavior
+  // await searchTest();
 
   // this step isn't necessary in synthetics
   await driver.quit();
@@ -106,7 +107,7 @@ const navTest = async () => {
 };
 
 const searchTest = async () => {
-  const [searchButton] = await waitForXPath('//a[contains(@href, "?q=")]');
+  const [searchButton] = await waitForXPath('.//*[@id="mobile-search-expand"]');
   console.log('\nClicking search input');
   await searchButton.click();
   // sleep is required here on mobile to account for the click delay

diff --git a/src/components/HomepageBanner.js b/src/components/HomepageBanner.js
@@ -78,7 +78,9 @@ const HomepageBanner = () => {
             searchTerm,
             searchLocation: 'homepage',
           });
-          navigate(`?q=${searchTerm || ''}`);
+          if (searchTerm !== '') {
+            navigate(`search-results/?query=${searchTerm}&page=1`);
+          }
         }}
         css={css`
           max-width: 880px;
@@ -116,19 +118,19 @@ const HomepageBanner = () => {
         `}
       >
         <p>{t('strings.home.search.popularSearches.title')}: </p>
-        <Link to="?q=nrql">
+        <Link to="/search-results/?query=nrql&page=1">
           {t('strings.home.search.popularSearches.options.0')},
         </Link>
-        <Link to="?q=logs">
+        <Link to="/search-results/?query=logs&page=1">
           {t('strings.home.search.popularSearches.options.1')},
         </Link>
-        <Link to="?q=alert">
+        <Link to="/search-results/?query=alert&page=1">
           {t('strings.home.search.popularSearches.options.2')},
         </Link>
-        <Link to="?q=best practices">
+        <Link to="/search-results/?query=best practices&page=1">
           {t('strings.home.search.popularSearches.options.3')},
         </Link>
-        <Link to="?q=kubernetes">
+        <Link to="/search-results/?query=kubernetes&page=1">
           {t('strings.home.search.popularSearches.options.4')}
         </Link>
       </div>

diff --git a/src/components/Navigation.js b/src/components/Navigation.js
@@ -32,7 +32,7 @@ const Navigation = ({ nav, className }) => {
       css={css`
         height: 100%;
         overflow: auto;
-        margin: 16px 0;
+        margin: 0 0 16px;
         -ms-overflow-style: none;
         scrollbar-width: none;
         &::-webkit-scrollbar {

diff --git a/src/content/docs/apis/nerdgraph/examples/nerdgraph-synthetics-tutorial.mdx b/src/content/docs/apis/nerdgraph/examples/nerdgraph-synthetics-tutorial.mdx
@@ -436,9 +436,10 @@ Below are some sample requests to automate the creation of your synthetic monito
 </Callout>
 
 <Callout variant="important">
-  As of August 26, 2024, you can no longer create new monitors using legacy runtimes on public or private locations.
+  As of August 26, 2024, you can no longer create new monitors using legacy runtimes on public or private locations. On October 22, 2024, we will [end of life](/whats-new/2024/04/whats-new-04-09-eol-synthetics-runtime-cpm) the containerized private minion (CPM) and legacy synthetics runtime versions. 
 
-  On October 22, 2024, we will [end of life](/whats-new/2024/04/whats-new-04-09-eol-synthetics-runtime-cpm) the containerized private minion (CPM) and legacy synthetics runtime versions. For public locations, use [the runtime upgrade UI](/docs/synthetics/synthetic-monitoring/using-monitors/runtime-upgrade-ui/) to update your monitors to the newest runtimes. For private locations, please review our [recommended migration steps](/docs/synthetics/synthetic-monitoring/private-locations/job-manager-transition-guide/#monitorMigration) to avoid monitor degradation.
+  * For public locations, use [the runtime upgrade UI](/docs/synthetics/synthetic-monitoring/using-monitors/runtime-upgrade-ui/) to update your monitors to the newest runtimes. 
+  * For private locations, please review our [recommended migration steps](/docs/synthetics/synthetic-monitoring/private-locations/job-manager-transition-guide/#monitorMigration) to avoid monitor degradation.
 </Callout>
 
 <CollapserGroup>

diff --git a/src/content/docs/apm/agents/php-agent/configuration/php-agent-configuration.mdx b/src/content/docs/apm/agents/php-agent/configuration/php-agent-configuration.mdx
@@ -1553,7 +1553,7 @@ Keep in mind that changing your settings in your local agent configuration file
 
 If you're using a [supported logging framework](/docs/logs/logs-context/configure-logs-context-php), you can direct the agent to forward your app logs to New Relic.
 
-* `newrelic.application_logging.forward.enabled` enables or disables log forwarding
+* `newrelic.application_logging.forwarding.enabled` enables or disables log forwarding
 * `newrelic.application_logging.forwarding.max_samples_stored` limits how many logs your app forwards to New Relic
 * `newrelic.application_logging.forwarding.log_level` lets you choose what kinds of logs your app forwards to New Relic
 

diff --git a/...ent/docs/apm/agents/php-agent/troubleshooting/agent-overhead-reduction-tips.mdx b/...ent/docs/apm/agents/php-agent/troubleshooting/agent-overhead-reduction-tips.mdx
@@ -0,0 +1,44 @@
+---
+title: PHP Agent overhead reduction tips
+type: troubleshooting
+tags:
+  - Agents
+  - PHP agent
+  - Troubleshooting
+metaDescription: Agent settings to decrease overhead.
+freshnessValidatedDate: 2024-10-21
+---
+
+## Problem
+
+Using the New Relic PHP agent results in overhead.
+
+## Cause
+
+Overhead is an expected side effect of monitoring and reporting on software. Our engineers aim to minimize this, but your experience may differ quite a lot, depending on how you're using the agent. If you find that you're experiencing unexpected overhead, there are are various settings in the `INI` that can help reduce it.
+
+## Solution
+Performance INI settings that can reduce overhead depending on your agent usage.
+
+1. Reduce [`newrelic.span_events.max_samples_stored`](/docs/apm/agents/php-agent/configuration/php-agent-configuration/#inivar-span-events-max-samples-stored).
+
+2. Disable [code level metrics](/docs/apm/agents/php-agent/configuration/php-agent-configuration/#inivar-code-level-metrics).
+
+3. Disable [logging](/docs/apm/agents/php-agent/configuration/php-agent-configuration/#log-forwarding).
+
+4. Set [`newrelic.transaction_tracer.max_segments_web`](/docs/apm/agents/php-agent/configuration/php-agent-configuration/#inivar-tt-maxsegweb) and [`newrelic.transaction_tracer.max_segments_cli`](/docs/apm/agents/php-agent/configuration/php-agent-configuration/#inivar-tt-maxsegcli) >= 1.
+
+5. Set [`newrelic.transaction_tracer.detail`](/docs/apm/agents/php-agent/configuration/php-agent-configuration/#inivar-tt-detail) = 0.
+
+6. Set [`newrelic.transaction_tracer.enabled`](/docs/agents/php-agent/configuration/php-agent-configuration#inivar-tt-enabled) = false.
+
+7. Increase the [transaction tracer threshold](/docs/agents/php-agent/configuration/php-agent-configuration#inivar-tt-threshold) by setting `newrelic.transaction_tracer.threshold` = higher value.
+
+8. Set [`newrelic.transaction_tracer.explain_enabled`](/docs/agents/php-agent/configuration/php-agent-configuration#inivar-tt-explain-enabled) = false.
+
+9. Don't trace slow SQL statements by setting [`newrelic.transaction_tracer.slow_sql`](/docs/agents/php-agent/configuration/php-agent-configuration#inivar-tt-slowsql) = false.
+
+
+## Other overhead considerations
+A non-performant clocksource can affect the agent which checks the time for every span. Please ensure you're using an appropriate [clocksource](https://forum.newrelic.com/s/hubtopic/aAX8W0000008a7rWAA/relic-solution-php-agent-cpu-overhead-tips).
+Fargate is affected by clocksource and is known to cause additional [overhead](/docs/apm/agents/php-agent/troubleshooting/fargate-nitro-clock-performance-impact/).
diff --git a/src/content/docs/apm/agents/python-agent/troubleshooting/testing-python-agent.mdx b/src/content/docs/apm/agents/python-agent/troubleshooting/testing-python-agent.mdx
@@ -138,7 +138,7 @@ dig collector.newrelic.com
 [output] ;collector.newrelic.com.                IN      A
 [output] 
 [output] ;; ANSWER SECTION:
-[output] collector.newrelic.com. 2453    IN      A       50.31.164.140
+[output] collector.newrelic.com. 2453    IN      A       162.247.243.32
 [output] 
 [output] ;; AUTHORITY SECTION:
 [output] newrelic.com.           1163    IN      NS      ns2.p21.dynect.net.
@@ -178,9 +178,9 @@ If you cannot contact the data collector host, configure the agent to use any fi
   >
     ```sh
     ping collector.newrelic.com
-    [output] PING collector.newrelic.com (50.31.164.140): 56 data bytes
-    [output] 64 bytes from 50.31.164.140: icmp_seq=0 ttl=239 time=234.204 ms
-    [output] 64 bytes from 50.31.164.140: icmp_seq=1 ttl=239 time=230.095 ms
+    [output] PING collector.newrelic.com (162.247.243.32): 56 data bytes
+    [output] 64 bytes from 162.247.243.32: icmp_seq=0 ttl=239 time=234.204 ms
+    [output] 64 bytes from 162.247.243.32: icmp_seq=1 ttl=239 time=230.095 ms
     [output] ...
     ```
   </Collapser>
@@ -193,20 +193,20 @@ If you cannot contact the data collector host, configure the agent to use any fi
 
     ```sh
     traceroute -p 80 collector.newrelic.com
-    [output] traceroute to collector.newrelic.com (50.31.164.140), 64 hops max, 52 byte packets
+    [output] traceroute to collector.newrelic.com (162.247.243.32), 64 hops max, 52 byte packets
     [output]  1  ...
     [output]  2  ...
     [output]  3  ...
     [output]  4  * * *
-    [output]  5  collector.newrelic.com (50.31.164.140)  232.590 ms  231.000 ms  232.041 ms
+    [output]  5  collector.newrelic.com (162.247.243.32)  232.590 ms  231.000 ms  232.041 ms
 
     traceroute -p 443 collector.newrelic.com
-    [output] traceroute to collector.newrelic.com (50.31.164.140), 64 hops max, 52 byte packets
+    [output] traceroute to collector.newrelic.com (162.247.243.32), 64 hops max, 52 byte packets
     [output]  1  ...
     [output]  2  ...
     [output]  3  ...
     [output]  4  * * *
-    [output]  5  collector.newrelic.com (50.31.164.140)  253.513 ms  231.134 ms  232.511 ms
+    [output]  5  collector.newrelic.com (162.247.243.32)  253.513 ms  231.134 ms  232.511 ms
     ```
   </Collapser>
 </CollapserGroup>
diff --git a/...ntent/docs/data-apis/convert-to-metrics/analyze-monitor-data-trends-metrics.mdx b/...ntent/docs/data-apis/convert-to-metrics/analyze-monitor-data-trends-metrics.mdx
@@ -229,7 +229,7 @@ Mutation operations for events to metrics, logs to metrics, or spans to metrics
             {
               "id": "12",
               "name": "Test Rule",
-              "nrql": "select summary(duration) as 'server.responseTime' from Transaction where appName = 'Data Points Staging' facet name, appName, host"
+              "nrql": "SELECT summary(duration) AS 'server.responseTime' FROM Transaction WHERE appName = 'Data Points Staging' FACET name, appName, host"
             }
           ]
         }
@@ -484,14 +484,14 @@ Query operations include:
                     "enabled": true,
                     "id": "1",
                     "name": "Total Time Tx",
-                    "nrql": "select summary(totalTime) as 'server.totalTime' from Transaction where appName = 'Data Points Staging' facet name, appName, host"
+                    "nrql": "SELECT summary(totalTime) AS 'server.totalTime' FROM Transaction WHERE appName = 'Data Points Staging' FACET name, appName, host"
                   },
                   {
                     "description": "Metric for duration",
                     "enabled": true,
                     "id": "2",
                     "name": "Duration Rule",
-                    "nrql": "select summary(duration) as 'server.responseTime' from Transaction where appName = 'Data Points Staging' facet name, appName, host"
+                    "nrql": "SELECT summary(duration) AS 'server.responseTime' FROM Transaction WHERE appName = 'Data Points Staging' FACET name, appName, host"
                   }
                 ]
               }
@@ -554,7 +554,7 @@ Query operations include:
                     "enabled": true,
                     "id": "36",
                     "name": "Total Time Tx",
-                    "nrql": "select summary(totalTime) as 'server.totalTime' from Transaction where appName = 'Data Points Staging' facet name, appName, host"
+                    "nrql": "SELECT summary(totalTime) AS 'server.totalTime' FROM Transaction WHERE appName = 'Data Points Staging' FACET name, appName, host"
                   }
                 ]
               }

diff --git a/src/content/docs/data-apis/convert-to-metrics/create-metrics-other-data-types.mdx b/src/content/docs/data-apis/convert-to-metrics/create-metrics-other-data-types.mdx
@@ -282,8 +282,13 @@ The available [NRQL aggregator functions](/docs/insights/nrql-new-relic-query-la
   >
     If you created a summary metric type, you can use the `count`, `sum`, `max`, `min`, and `average` aggregator functions, as shown in the following query:
 
-    ```
-    SELECT count(appStartResponseTime), sum(appStartResponseTime), max(appStartResponseTime), min(appStartResponseTime),  average(appStartResponseTime) FROM Metric
+    ```sql
+    SELECT count(appStartResponseTime), 
+      sum(appStartResponseTime), 
+      max(appStartResponseTime), 
+      min(appStartResponseTime), 
+      average(appStartResponseTime) 
+    FROM Metric
     ```
   </Collapser>
 

diff --git a/src/content/docs/data-apis/custom-data/aws-privatelink.mdx b/src/content/docs/data-apis/custom-data/aws-privatelink.mdx
@@ -776,11 +776,11 @@ These are the New Relic endpoint services available via AWS PrivateLink:
             </td>
 
             <td>
-              `infra-api.eu01.nr-data.net`
+              `infra-api.eu01.nr-data.net` and `infra-api.eu.newrelic.com`
             </td>
 
             <td>
-              `com.amazonaws.vpce.eu-central-1.vpce-svc-06d5b2d7e79ddd78e`
+              `com.amazonaws.vpce.eu-central-1.vpce-svc-06d5b2d7e79ddd78e` and `com.amazonaws.vpce.eu-central-1.vpce-svc-02fc7dd8d7be95a32`, respectively
             </td>
           </tr>