Merge pull request #19107 from newrelic/daily-release/10-28-24-midday

Daily release/10 28 24 midday

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.10.5",
+    "@newrelic/gatsby-theme-newrelic": "9.10.6",
     "@splitsoftware/splitio-react": "^1.2.4",
     "ansi-colors": "^4.1.3",
     "cockatiel": "^3.0.0-beta.0",

src/content/docs/alerts/create-alert/condition-details/incident-event-attributes.mdx

@@ -167,7 +167,7 @@ All attributes are available for use in a [description](/docs/alerts/new-relic-a
       <td>
         The contents of the active condition's `Violation Description` field.
 
-        NRQL or infrastructure conditions only.
+        NRQL or infrastructure conditions only. Not available for use with alert condition [title](docs/alerts/create-alert/condition-details/title-template) or [description templates](/docs/alerts/create-alert/condition-details/alert-custom-incident-descriptions).
       </td>
     </tr>
 
@@ -256,7 +256,7 @@ All attributes are available for use in a [description](/docs/alerts/new-relic-a
       </td>
 
       <td>
-        The unique identifier of the incident.
+        The unique identifier of the incident. Not available for use with alert condition [title](docs/alerts/create-alert/condition-details/title-template) or [description templates](/docs/alerts/create-alert/condition-details/alert-custom-incident-descriptions).
       </td>
     </tr>
 

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

@@ -590,6 +590,8 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co
             The .NET agent does not directly monitor datastore processes. Also, the .NET SQL parameter capture in a query trace does not list parameters for a parameterized query or a stored procedure.
 
             Collecting [instance details](/docs/apm/applications-menu/features/analyze-database-instance-level-performance-issues) for supported datastores is enabled by default. To request instance-level information from datastores not currently listed, get support at [support.newrelic.com](https://support.newrelic.com).
+
+            If your datastore isn't listed here, you can add custom instrumentation using the `RecordDatastoreSegment` method in the [.NET agent API](/docs/apm/agents/net-agent/net-agent-api/net-agent-api/#ITransaction).
         </Collapser>
 
         <Collapser
@@ -1553,6 +1555,8 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co
 
                 </tbody>
                 </table>
+
+                If your datastore isn't listed here, you can add custom instrumentation using the `RecordDatastoreSegment` method in the [.NET agent API](/docs/apm/agents/net-agent/net-agent-api/net-agent-api/#ITransaction).
             </Collapser>
 
             <Collapser

src/content/docs/codestream/observability/code-level-metrics.mdx

@@ -50,6 +50,6 @@ To see in-editor performance data, your service must meet the requirements liste
 * <DNT>**Node.js:**</DNT> Requires Node.js agent version 10.5.0 or higher. If your codebase include anonymous functions you'll need to either use [change tracking](/docs/change-tracking/change-tracking-introduction/) to send deployment information to New Relic, or you'll need to [send your build SHA via an environment variable](/docs/codestream/observability/error-investigation/#buildsha) in your build pipeline.
 * <DNT>**PHP:**</DNT> Requires PHP agent version 10.6.0 or higher. If you're using VS Code, you must also have the [PHP Intelephense](https://marketplace.visualstudio.com/items?itemName=bmewburn.vscode-intelephense-client) extension installed.
 * <DNT>**Python:**</DNT> Requires Python agent version 7.10.0.175 or higher. Code-level metrics are only available for projects implemented with a [supported Python framework](/docs/apm/agents/python-agent/getting-started/instrumented-python-packages) and for PHP version 7.0 or higher. If you're using VS Code, you must also have the [Python](https://marketplace.visualstudio.com/items?itemName=ms-python.python) extension installed with the language server enabled.
-* <DNT>**Ruby:**</DNT> Requires Ruby agent version 8.10.0 or higher. Code-level metrics are only available for Rails applications and Ruby methods with manual traces ([learn more about Ruby methods and CodeStream](/docs/apm/agents/ruby-agent/features/ruby-codestream-integration)). If you're using VS Code, you must also have either the [Ruby](https://marketplace.visualstudio.com/items?itemName=rebornix.Ruby) or [Ruby Solargraph](https://marketplace.visualstudio.com/items?itemName=castwide.solargraph) extension installed with the language server enabled.
+* <DNT>**Ruby:**</DNT> Requires Ruby agent version 8.10.0 or higher. Code-level metrics are only available for Rails applications and Ruby methods with manual traces ([learn more about Ruby methods and CodeStream](/docs/apm/agents/ruby-agent/features/ruby-codestream-integration)). If you're using VS Code, you must also have the [Ruby LSP](https://marketplace.visualstudio.com/items?itemName=Shopify.ruby-lsp) extension installed.
 
 You can turn CodeLenses off by going to the CodeStream section of your IDE's settings and unchecking the <DNT>**CodeStream: Show Golden Signals In Editor**</DNT> setting.

src/content/docs/infrastructure/prometheus-integrations/view-query-data/translate-promql-queries-nrql.mdx

@@ -325,10 +325,10 @@ This table shows the mapping between NRQL and our PromQL-style queries when expl
       **5. Add the selected ID to the query.**
     </DNT>
 
-    Next you can select an `id` value and put it in the NRQL `where` clause.
+    Next you can select an `id` value and put it in the NRQL `WHERE` clause.
 
     ```sql
-    FROM Metric SELECT latest(container_memory_usage_bytes) WHERE id = "/" timeseries
+    FROM Metric SELECT latest(container_memory_usage_bytes) WHERE id = "/" TIMESERIES
     ```
 
     <img
@@ -337,7 +337,7 @@ This table shows the mapping between NRQL and our PromQL-style queries when expl
     />
 
     <figcaption>
-      <DNT>**[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Query your data**</DNT>: This example shows the data displayed after running `From Metric select latest(container_memory_usage_bytes) where id = "/" timeseries`.
+      <DNT>**[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Query your data**</DNT>: This example shows the data displayed after running `From Metric select latest(container_memory_usage_bytes) where id = "/" TIMESERIES`.
     </figcaption>
   </Collapser>
 </CollapserGroup>
@@ -425,7 +425,7 @@ Here are some example queries:
           In NRQL use the `LIKE` clause to match part of a string value. In this example, all data will be returned where the job attributes start with `api`.
 
           ```sql
-          FROM Metric SELECT latest(go_memstats_heap_alloc_bytes) WHEREe job LIKE 'api%' TIMESERIES
+          FROM Metric SELECT latest(go_memstats_heap_alloc_bytes) WHERE job LIKE 'api%' TIMESERIES
           ```
       </td>
     </tr>

src/content/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/monitor-services/monitor-services-running-kubernetes.mdx

@@ -32,7 +32,7 @@ To monitor services running on Kubernetes, you need:
   * [Cassandra](/docs/integrations/host-integrations/host-integrations-list/cassandra-monitoring-integration)
   * [Couchbase](/docs/integrations/host-integrations/host-integrations-list/couchbase-monitoring-integration)
   * [Elasticsearch](/docs/integrations/host-integrations/host-integrations-list/elasticsearch-monitoring-integration)
-  * [HAProxy](/docs/integrations/host-integrations/host-integrations-list/haproxy-monitoring-integration)
+  * [HAProxy](/install/haproxy/)
   * [HashiCorp Consul](/docs/integrations/host-integrations/host-integrations-list/hashicorp-consul-monitoring-integration)
   * [JMX](/docs/integrations/host-integrations/host-integrations-list/jmx-monitoring-integration)
   * [Kafka](/docs/integrations/host-integrations/host-integrations-list/kafka-monitoring-integration)

src/content/docs/new-relic-solutions/solve-common-issues/diagnostics-cli-nrdiag/diagnostics-cli-nrdiag.mdx

@@ -47,7 +47,7 @@ The Diagnostics CLI does not require `superuser` or `admin` permissions to run,
 To use the Diagnostics CLI:
 
 1. Run the Diagnostics CLI, including [task suites](/docs/new-relic-solutions/solve-common-issues/diagnostics-cli-nrdiag/run-diagnostics-cli-nrdiag) and [command line options](/docs/using-new-relic/cross-product-functions/diagnostics-cli-nrdiag/pass-command-line-options-nrdiag) as needed.
-2. Supply the [-attach or -api-key](/docs/using-new-relic/cross-product-functions/diagnostics-cli-nrdiag/pass-command-line-options-nrdiag) flag for uploading results to your New Relic account.
+2. Supply the [`-attach` or `-api-key`](/docs/using-new-relic/cross-product-functions/diagnostics-cli-nrdiag/pass-command-line-options-nrdiag) flag for uploading results to your New Relic account.
 3. Optional: Validate your [config file settings](/docs/using-new-relic/cross-product-functions/diagnostics-cli-nrdiag/validate-config-file-settings-nrdiag).
 4. Interpret the [output](/docs/using-new-relic/cross-product-functions/diagnostics-cli-nrdiag/interpret-nrdiag-output).
 

src/content/docs/new-relic-solutions/solve-common-issues/diagnostics-cli-nrdiag/interpret-nrdiag-output.mdx

@@ -10,7 +10,7 @@ redirects:
 freshnessValidatedDate: never
 ---
 
-After executing the Diagnostics CLI from your terminal, you will see the results for each task as they are completed. Tasks that result in a `Warning` or `Failure` status code will log additional details regarding possible issues found during execution, along with troubleshooting suggestions and relevant links to documentation. If you use the [-attach or -api-key](/docs/new-relic-solutions/solve-common-issues/diagnostics-cli-nrdiag/pass-command-line-options-nrdiag) flag, you can view your results in [the UI](/docs/using-new-relic/cross-product-functions/diagnostics-cli-nrdiag/interpret-nrdiag-output/#diag-in-nr1)
+After executing the Diagnostics CLI from your terminal, you will see the results for each task as they are completed. Tasks that result in a `Warning` or `Failure` status code will log additional details regarding possible issues found during execution, along with troubleshooting suggestions and relevant links to documentation. If you use the [`-attach` or `-api-key`](/docs/new-relic-solutions/solve-common-issues/diagnostics-cli-nrdiag/pass-command-line-options-nrdiag) flag, you can view your results in [the UI](/docs/using-new-relic/cross-product-functions/diagnostics-cli-nrdiag/interpret-nrdiag-output/#diag-in-nr1)
 
 <img
   title="screen-nrdiag-output.png"