Daily release/nov 20 2023 5 35

src/@newrelic/gatsby-theme-newrelic/icons/newrelic.js

@@ -11,6 +11,8 @@ import InfrastructureIcon from './newrelic/infrastructure';
 import BrowserIcon from './newrelic/browser';
 import AlertsAiIcon from './newrelic/alerts-ai';
 import ApmIcon from './newrelic/apm';
+import StackTraceIcon from './newrelic/stack-trace';
+import LatencyIcon from './newrelic/latency';
 
 export default {
   ...defaultIcons,
@@ -26,4 +28,6 @@ export default {
   browser: BrowserIcon,
   'alerts-ai': AlertsAiIcon,
   apm: ApmIcon,
+  'stack-trace': StackTraceIcon,
+  latency: LatencyIcon,
 };

src/@newrelic/gatsby-theme-newrelic/icons/newrelic/latency.js

@@ -0,0 +1,28 @@
+import React from 'react';
+import PropTypes from 'prop-types';
+import { css } from '@emotion/react';
+import SVG from '@newrelic/gatsby-theme-newrelic/src/components/SVG';
+
+const LatencyIcon = (props) => (
+  <SVG
+    {...props}
+    viewBox="0 0 16 16"
+    css={css`
+      fill: currentColor;
+      stroke: currentColor;
+      stroke-width: 0.25;
+    `}
+  >
+    <path
+      fillRule="evenodd"
+      clipRule="evenodd"
+      d="M1 7.5C1 3.9 3.9 1 7.5 1S14 3.9 14 7.5c0 .5-.1 1-.2 1.5h1c.1-.5.2-1 .2-1.5C15 3.4 11.6 0 7.5 0S0 3.4 0 7.5 3.4 15 7.5 15c.5 0 1-.1 1.5-.2v-1c-.5.1-1 .2-1.5.2C3.9 14 1 11.1 1 7.5zM7 3v6h4V8H8V3H7zm6 9.3l1.6-1.7.8.8-1.7 1.6 1.7 1.6-.8.8-1.6-1.7-1.6 1.7-.8-.8 1.7-1.6-1.7-1.6.8-.8 1.6 1.7z"
+    />
+  </SVG>
+);
+
+LatencyIcon.propTypes = {
+  size: PropTypes.string,
+};
+
+export default LatencyIcon;

src/@newrelic/gatsby-theme-newrelic/icons/newrelic/stack-trace.js

@@ -0,0 +1,28 @@
+import React from 'react';
+import PropTypes from 'prop-types';
+import { css } from '@emotion/react';
+import SVG from '@newrelic/gatsby-theme-newrelic/src/components/SVG';
+
+const StackTraceIcon = (props) => (
+  <SVG
+    {...props}
+    viewBox="0 0 16 16"
+    css={css`
+      fill: currentColor;
+      stroke: currentColor;
+      stroke-width: 0.25;
+    `}
+  >
+    <path
+      fillRule="evenodd"
+      clipRule="evenodd"
+      d="M12 1H4v1h8V1zM4 4h8v1H4V4zm10 9H2V7H1v7h14V7h-1v6zM4 10h8v1H4v-1zm8-3H4v1h8V7z"
+    />
+  </SVG>
+);
+
+StackTraceIcon.propTypes = {
+  size: PropTypes.string,
+};
+
+export default StackTraceIcon;

src/content/docs/apm/agents/java-agent/getting-started/compatibility-requirements-java-agent.mdx

@@ -326,7 +326,7 @@ The agent automatically instruments these frameworks and libraries:
     * JBoss 7.0 to latest
     * JBoss EAP 6.0 to latest
     * Jetty 9.3.0.M1 to latest
-    * Mule ESB 3.4 to 3.8.x
+    * Mule ESB 3.4 to 3.9.x
     * Netty 3.3.0.Alpha1 to 5.0.0.Alpha1
     * Resin 3.1.9 to 4.0.x
     * Spray-can 1.3.1 to latest

src/content/docs/apm/transactions/transaction-traces/transaction-traces-trace-details-page.mdx

@@ -19,7 +19,9 @@ import apmTransactionTraceDetails from 'images/apm_screenshot-crop_transaction-t
 
 import apmIconDb from 'images/apm_icon_icon-db.webp'
 
-import apmIconParameters from 'images/apm_icon_icon-parameters.webp'
+import apmIconStackTrace from 'images/stack-trace-icon.webp'
+
+import apmIconLatency from 'images/latency-icon.webp'
 
 import apmIcoWebTransactions from 'images/apm_icon_ico-web-transactions.webp'
 
@@ -41,7 +43,8 @@ In [APM](/docs/apm/new-relic-apm/getting-started/welcome-new-relic-apm), the **T
   Go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > APM & services > (select an app) > Monitor > Transactions > (select a transaction trace) > Trace details.**
 </figcaption>
 
-The **Trace details** page displays a table with the timing data for the segments in a transaction, plus additional features and functions:
+The **Trace details** page displays a table and waterfall with the timing data for the segments in a transaction, plus additional features and functions.
+Additional tabs are available to view all segment attributes and database queries recorded during the trace.
 
 <table>
   <thead>
@@ -64,21 +67,7 @@ The **Trace details** page displays a table with the timing data for the segment
 
       <td>
         The top of each transaction trace UI page shows several primary pieces of data, including the trace time, response time, and, if available, CPU info. Also, sometimes the UI may indicate a [partial trace](#partial).
-
-        Available functions include:
-
-        * Delete this trace: When you delete a trace, it cannot be retrieved.
-        * Track as [key transaction](/docs/apm/transactions/key-transactions/key-transactions-tracking-important-transactions-or-events).
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        Duration column
-      </td>
-
-      <td>
-        The duration of each segment and subsegment is shown as both the number of milliseconds and a percentage of the total transaction time. Especially slow segments are [color-coded](#colors).
+        When the trace is derived from Distribtued tracing, it also contains a link to view the full distributed that includes this transaction trace.
       </td>
     </tr>
 
@@ -90,38 +79,36 @@ The **Trace details** page displays a table with the timing data for the segment
       <td>
         The **Segment** column displays segment names and counts. Fast and repeat calls may be [automatically grouped together](#rollup). Sometimes you may see [**Application code**](#application-code) as the name of a segment or subsegment.
 
-        To expand segments, use either of the following:
-
-        * The **Expand performance problems** button at the top of the page
-        * The expand and collapse dropdown arrows next to the segments
+        Use the expand and collapse dropdown arrows to expand segments.
       </td>
     </tr>
 
     <tr>
       <td>
-        Drilldown column
+        Segment icons
       </td>
 
       <td>
-        The [**Drilldown** column](#drilldown) may contain icons that link to additional transaction data, if available.
+        [Icons](#icons) represent significant characteristics of the segments.
       </td>
     </tr>
 
     <tr>
       <td>
-        Timestamp column
+        Duration column
       </td>
 
       <td>
-        The **Timestamp** column displays the start time of a segment or subsegment, relative to the start of the transaction. For example, a value of `3.150 s` indicates that that segment started 3.15 seconds into the transaction.
+        The duration of each segment and subsegment is shown as both the number of milliseconds and a percentage of the total transaction time. Especially slow segments are [color-coded](#colors).
       </td>
     </tr>
+
   </tbody>
 </table>
 
-## Drilldown options [#drilldown]
+## Segment icons [#icons]
 
-In the **Drilldown** column, icons indicate that additional data is available:
+Icons indicate significant characteristics of a segment:
 
 <table>
   <thead>
@@ -144,43 +131,34 @@ In the **Drilldown** column, icons indicate that additional data is available:
 
       <td>
         The database <Icon name="fe-database"/>
-        icon links to the raw database query for that query segment. Depending on your [transaction trace settings](/docs/features/configuring-transaction-traces), this query can either show as raw data or obfuscated data. If the total time for the segment exceeds the query plan threshold in your settings, the query analysis also will appear, along with a stack trace showing the exact location of the call in your code.
+        icon identifies a database call segment. Click on the segment to view the raw database query. Depending on your [transaction trace settings](/docs/features/configuring-transaction-traces), this query can either show as raw data or obfuscated data.
       </td>
     </tr>
 
     <tr>
       <td>
-        <img title="icon-search" alt="icon-search" src={apmIconParameters}/> Stack traces
+        <img title="icon-stack-trace" alt="icon-stack-trace" src={apmIconStackTrace} width="35px" height="35px" /> Stack traces
       </td>
 
       <td>
-        The magnifying glass <Icon name="fe-search"/>
-        links to stack trace details.
+        The stack trace icon <Icon name="nr-stack-trace"/>
+        icon indicates that a stack trace is available for this segment.
       </td>
     </tr>
 
     <tr>
       <td>
-        <img title="icon-web-transaction-app" alt="icon-web-transaction-app" src={apmIcoWebTransactions}/> Aggregate transaction details
+        <img title="icon-latency" alt="icon-latency" src={apmIconLatency} width="35px" height="35px" /> Latency
       </td>
 
       <td>
-        This icon indicates that cross application tracing details are not available. However, you can select this icon to view [aggregated transaction information](/docs/apm/applications-menu/monitoring/transactions-page) across multiple invocations of the transaction.
+        The latency <Icon name="nr-latency"/>
+        icon indicates that this segment accounts for a significant portion of latency in the trace. See [latency color codes](#colors).
       </td>
     </tr>
   </tbody>
 </table>
 
-## Examine logs for trace details [#logs-context]
-
-You can bring your logs and application's data together to make troubleshooting easier and faster. With [logs in context](/docs/logs/logs-context/configure-logs-context-apm-agents/), you can see log messages related to your errors and traces directly in your app's UI.
-
-1. From the **Transactions** page, click on a trace to go to the [**Trace details** page](/docs/apm/transactions/transaction-traces/transaction-traces-trace-details-page).
-2. From the trace details page, click **See logs**.
-3. To view details related to an individual log message, click directly on the message.
-
-You can also see logs in context of your [infrastructure data](/docs/logs/forward-logs/forward-your-logs-using-infrastructure-agent/), such as Kubernetes clusters. No need to switch to another UI page.
-
 ## Color coding of segment duration data [#colors]
 
 The **Duration** column of the **Trace details** table is color-coded:
@@ -283,8 +261,20 @@ Rules underlying segment grouping include:
 
 ## Distributed traces [#distributed-traces]
 
+When a transaction trace is based on distributed trace data, you can view the full distributed trace by clicking on the distributed trace link in the page header.
+
 The trace details page will display slightly different information when looking at a distributed trace instead of a transaction trace. 
 
 * All attributes are grouped into a single `Attributes` section rather than being split out into the three default attribute types
 * Segment metric names may differ slightly between distributed traces and transaction traces
-* Stack traces are not displayed in segment attributes
+* Stack traces are not displayed in segment attributes
+
+## Examine logs for trace details [#logs-context]
+
+You can bring your logs and application's data together to make troubleshooting easier and faster. With [logs in context](/docs/logs/logs-context/configure-logs-context-apm-agents/), you can see log messages related to your errors and traces directly in your app's UI.
+
+1. From the **Transactions** page, click on a trace to go to the [**Trace details** page](/docs/apm/transactions/transaction-traces/transaction-traces-trace-details-page).
+2. From the trace details page, click **See logs**.
+3. To view details related to an individual log message, click directly on the message.
+
+You can also see logs in context of your [infrastructure data](/docs/logs/forward-logs/forward-your-logs-using-infrastructure-agent/), such as Kubernetes clusters. No need to switch to another UI page.

src/content/docs/query-your-data/nrql-new-relic-query-language/get-started/introduction-nrql-tutorial.mdx

@@ -425,6 +425,8 @@ Grouping or "faceting" allows you to get dimensional with your data. When applyi
 
 Congratulations: you've completed the first NRQL tutorial! If you've made it this far, you now know the basics of querying event data using NRQL.
 
-Have you read the tutorial but don't have an account yet? If you haven't already, create your free New Relic account below to start monitoring your data today.
+### What's next?
+
+We have even more NRQL for you to explore with three more tutorials that cover more advanced concepts and use cases! We recommend proceeding to the tutorial on [processing your data](/docs/query-your-data/nrql-new-relic-query-language/get-started/nrql-tutorial-process-your-data/) first, then moving on to the tutorial on [advancing your dashboarding](/docs/query-your-data/nrql-new-relic-query-language/get-started/nrql-tutorial-advanced-dashboarding/), and finally finish the series with our tutorial on the most [advanced NRQL functions](/docs/query-your-data/nrql-new-relic-query-language/get-started/nrql-tutorial-advanced-functions/).
+
 
-<InlineSignup/>