Merge branch 'develop' into NR-343902-ccus-for-alert-conditions

src/content/docs/apm/agents/net-agent/configuration/net-agent-configuration.mdx

@@ -274,6 +274,7 @@ NEW_RELIC_FORCE_NEW_TRANSACTION_ON_NEW_THREAD=true
 NEW_RELIC_CODE_LEVEL_METRICS_ENABLED=true
 NEW_RELIC_AI_MONITORING_ENABLED=true
 NEW_RELIC_AI_MONITORING_RECORD_CONTENT_ENABLED=true
+NEW_RELIC_CLOUD_AWS_ACCOUNT_ID=123456789012
 ```
 
 <CollapserGroup>
@@ -1056,7 +1057,7 @@ The `proxy` element supports the following attributes:
 
 ### Log element [#log]
 
-The `log` element is a child of the `configuration` element. The `log` element configures New Relic's logging . The agent generates its own log file to keep its logging information separate from your application's logs.
+The `log` element is a child of the `configuration` element. The `log` element configures New Relic's logging. The agent generates its own log file to keep its logging information separate from your application's logs.
 
 ```xml
 <log enabled="true"
@@ -1071,8 +1072,8 @@ The `log` element supports the following attributes:
 
 <CollapserGroup>
   <Collapser
-    id="log-level"
-    title="level"
+    id="log-enabled"
+    title="enabled"
   >
     <table>
       <tbody>
@@ -1082,7 +1083,7 @@ The `log` element supports the following attributes:
           </th>
 
           <td>
-            String
+            Boolean
           </td>
         </tr>
 
@@ -1092,32 +1093,18 @@ The `log` element supports the following attributes:
           </th>
 
           <td>
-            `info`
+            `true`
           </td>
         </tr>
       </tbody>
     </table>
 
-    Defines the level of detail recorded in the log file. Possible values, in increasing order of detail, are:
-
-    * `off`
-    * `error`
-    * `warn`
-    * `info`
-    * `debug`
-    * `finest`
-    * `all`
-
-      Alternatively, set the `NEWRELIC_LOG_LEVEL` environment variable in the application's environment.
-
-      <Callout variant="important">
-        Increasing the log level will increase New Relic's performance impact.
-      </Callout>
+    When set to `false`, all logging is disabled. Alternatively, set the `NEW_RELIC_LOG_ENABLED` environment variable in the application's environment.
   </Collapser>
 
   <Collapser
-    id="log-auditLog"
-    title="auditLog"
+    id="log-level"
+    title="level"
   >
     <table>
       <tbody>
@@ -1127,7 +1114,7 @@ The `log` element supports the following attributes:
           </th>
 
           <td>
-            Boolean
+            String
           </td>
         </tr>
 
@@ -1137,18 +1124,32 @@ The `log` element supports the following attributes:
           </th>
 
           <td>
-            `false`
+            `info`
           </td>
         </tr>
       </tbody>
     </table>
 
-    Records all data sent to and received from New Relic in both an auditlog log file and the standard log file.
+    Defines the level of detail recorded in the log file. Possible values, in increasing order of detail, are:
+
+    * `off`
+    * `error`
+    * `warn`
+    * `info`
+    * `debug`
+    * `finest`
+    * `all`
+
+      Alternatively, set the `NEWRELIC_LOG_LEVEL` environment variable in the application's environment.
+
+      <Callout variant="important">
+        Increasing the log level will increase New Relic's performance impact.
+      </Callout>
   </Collapser>
 
   <Collapser
-    id="log-console"
-    title="console"
+    id="log-auditLog"
+    title="auditLog"
   >
     <table>
       <tbody>
@@ -1174,12 +1175,12 @@ The `log` element supports the following attributes:
       </tbody>
     </table>
 
-    Send log messages to the console, in addition to the log file. Alternatively, set the `NEW_RELIC_LOG_CONSOLE` environment variable in the application's environment.
+    Records all data sent to and received from New Relic in both an auditlog log file and the standard log file. Ignored if `enabled` is set to `false` or `console` is set to `true`.
   </Collapser>
 
   <Collapser
-    id="log-enabled"
-    title="enabled"
+    id="log-console"
+    title="console"
   >
     <table>
       <tbody>
@@ -1199,13 +1200,15 @@ The `log` element supports the following attributes:
           </th>
 
           <td>
-            `true`
+            `false`
           </td>
         </tr>
       </tbody>
     </table>
 
-    If disabled, no logging is attempted. Intended for read-only file systems. Alternatively, set the `NEW_RELIC_LOG_ENABLED` environment variable in the application's environment.
+    Send log messages to the console instead of the log file (in agent versions prior to 10.35.0, logs are sent to both the console and the log file). Ignored if `enabled` is set to `false`. Alternatively, set the `NEW_RELIC_LOG_CONSOLE` environment variable in the application's environment.
+
+    Console logging in the profiler is limited to `info` level and higher due to performance considerations. 
   </Collapser>
 
   <Collapser
@@ -2030,6 +2033,7 @@ Use these options to enable, disable, and configure New Relic features. New Reli
 * [Capture HTTP Request Headers](#capture_http_request_headers)
 * [Application logging](#application_logging)
 * [Code level metrics](#code_level_metrics)
+* [Cloud provider metadata](#cloud)
 * [AI monitoring](#ai_monitoring)
 
 ### App pools [#include_exclude_apps]
@@ -3700,6 +3704,37 @@ This can also be configured via environment variable:
 NEW_RELIC_CODE_LEVEL_METRICS_ENABLED=true
 ```
 
+### Cloud provider metadata [#cloud]
+
+The `cloud` element is a child of the `configuration` element. Use `cloud` to configure cloud provider metadata for your application.
+
+The `cloud` element supports the following sub-elements:
+
+<CollapserGroup>
+  <Collapser
+    id="cloud-aws"
+    title="aws"
+  >
+    Use this sub-element to configure AWS account ID for your application. 
+
+    <Callout variant="important">
+      Note that this configuration is not normally required, as the agent will automatically detect the AWS account ID at runtime. If automatic detetction is not working, the agent will fall back to the value configured here.
+    </Callout>
+
+    ```xml
+    <cloud>
+      <aws accountId="123456789012" />
+    </cloud>
+    ```
+
+    This can also be configured via environment variable:
+
+    ```ini
+    NEW_RELIC_CLOUD_AWS_ACCOUNT_ID=123456789012
+    ```
+  </Collapser>
+</CollapserGroup>
+
 ### AI monitoring [#ai_monitoring]
 
 By default, AI monitoring is disabled. To enable AI monitoring, set the `enabled` attribute to `true` in the `aiMonitoring` element. The `aiMonitoring` element is a child of the `configuration` element.

src/content/docs/infrastructure/google-cloud-platform-integrations/get-started/connect-google-cloud-platform-services-new-relic.mdx

@@ -64,6 +64,8 @@ These are the requirements for the authorization:
 
         You need a user with <DNT>**Project IAM Admin**</DNT> role to add the service account ID as a member in your GCP project.
 
+        Before adding the service account, ensure you click "Fetch data" of the onboarding wizard to verify authorization for data retrieval from Google.
+
         In the GCP project <DNT>**IAM & admin**</DNT>, the service account must have the <DNT>**Viewer**</DNT> role and the <DNT>**Service Usage Consumer**</DNT> role or, alternatively, a [custom role](/docs/integrations/google-cloud-platform-integrations/get-started/integrations-custom-roles).
       </td>
     </tr>

src/content/docs/nrql/nrql-syntax-clauses-functions.mdx

@@ -67,6 +67,45 @@ As noted in our [basic NRQL syntax doc](/docs/query-your-data/nrql-new-relic-que
         ```
       </Collapser>
     </CollapserGroup>
+
+    You can include both the `*` wildcard and individual attributes, [functions](#non-aggregator-functions), math expressions, and [NRQL variables](#with-as-nrql-var) in the same `SELECT` statement. `*` may appear at the beginning or end of the `SELECT` list, and the additional columns selected will appear at the beginning or end of the results table, respectively:
+
+    ```sql
+    SELECT *, attribute, function(attribute), attribute1 + attribute2 FROM ...
+    ```
+
+    ```sql
+    WITH attribute1 + attribute2 AS attrSum SELECT attrSum, attribute, function(attribute), * FROM ...
+    ```
+
+    <CollapserGroup>
+      <Collapser
+        id="select-star-with-columns-query"
+        title={<><InlineCode>SELECT *</InlineCode> with additional columns</>}
+      >
+        This query returns all available PageView attributes with additional columns at the beginning.
+
+        ```sql
+        WITH concat('(', asnLatitude, ', ', asnLongitude, ')') AS coordinates
+        SELECT coordinates, city, connectionSetupDuration + pageRenderingDuration AS partialDuration, *
+        FROM PageView
+        ```
+
+        <img
+          title="select star with additional columns"
+          alt="select star with additional columns"
+          src="/images/nrql_screenshot-select-star-with-additional-columns.webp"
+        />
+
+        <figcaption>
+          <InlineCode>SELECT *</InlineCode> with additional columns example
+        </figcaption>
+      </Collapser>
+    </CollapserGroup>
+
+    <Callout variant="tip">
+      Only [non-aggregator functions](#non-aggregator-functions) are supported in the `SELECT` list along with `*`.
+    </Callout>
   </Collapser>
 
   <Collapser

src/content/whats-new/2025/01/whats-new-01-16-azureserverless.md

@@ -14,4 +14,4 @@ New Relic now offers comprehensive serverless monitoring for Azure Functions, in
 * **Containerized function support:** Gain deep insights into the behavior of your Azure Functions deployed as containers, even when running within Kubernetes environments.
 * **Comprehensive metrics:** Access a rich set of metrics related to compute, garbage collection, and HTTP status codes, empowering you to proactively identify and address performance issues.
 
-![Azure serverless image](../../../../../static/images/azureserverless.webp "Azure serverless")
+![Azure serverless image](/images/azureserverless.webp "Azure serverless")

src/content/whats-new/2025/01/whats-new-01-23-msconnector-eol.md

@@ -0,0 +1,23 @@
+---
+title: 'Office 365 connectors for Microsoft Teams End-of-life'
+summary: 'Microsoft is retiring Office 365 connectors within Microsoft Teams '
+releaseDate: '2025-01-23'
+learnMoreLink: 'https://forum.newrelic.com/s/hubtopic/aAXPh0000008Rz7OAE/upcoming-endoflife-microsoft-teams-connectors-integration'
+---
+
+Microsoft has announced the [retirement of the Office 365 connectors feature for Microsoft Teams](https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/). This change could impact the New Relic accounts that use these connectors for outbound notifications. The transition to a new URL structure is required as part of [Microsoft's service hardening updates](https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/). 
+
+As a result, the webhook URLs of all existing Office 365 connectors with New Relic must either (1) be updated following the instructions below or (2) deleted and replaced with new connectors by January 31, 2025 to continue posting messages into Microsoft Teams. [Microsoft recommends](https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/) deleting existing connectors and creating new connectors to avoid having to do another round of updates at a later date. 
+
+## What you need to do
+
+1. **To update your existing connectors:** Follow the steps [recommended by Microsoft](https://learn.microsoft.com/en-us/microsoftteams/m365-custom-connectors#update-connectors-url) to update the webhook URLs of your Office 365 connectors. Edit the corresponding webhook destinations in New Relic UI by updating the new URLs in the **Endpoint URL** field.
+
+    **NOTE:** [Microsoft recommends](https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/) deleting existing connectors and creating new connectors to prevent further updates. See additional instructions below to create new connectors.
+
+    OR
+
+2. **To create new connectors:** Microsoft recommends designing a workflow within Microsoft Teams using the Workflows app. We have provided the step-by-step instructions along with a [sample payload template](/docs/alerts/get-notified/new-relic-webhook-for-microsoft-teams-workflow/) to help you get started.
+
+
+Our support team is here to assist you during this transition. Additional solutions may be available from New Relic in the future. If you have questions about these changes, please [contact Support](https://docs.newrelic.com/docs/new-relic-solutions/solve-common-issues/find-help-get-support/).

src/data/whats-new-ids.json

@@ -358,5 +358,7 @@
   "/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-01-17-cross-account-alerts": "43017",
-  "/whats-new/2025/01/whats-new-03-01-rest-api-keys-eol": "43018"
+  "/whats-new/2025/01/whats-new-03-01-rest-api-keys-eol": "43018",
+  "/whats-new/2025/01/whats-new-01-22-React18-upgrade": "43019",
+  "/whats-new/2025/01/whats-new-01-23-msconnector-eol": "43020"
 }

src/install/mysql/whatsNext.mdx

@@ -238,7 +238,7 @@ The MySQL integration collects the following metrics:
           </td>
 
           <td>
-            Amount of free memory in bytes for the query cache.
+            Amount of free memory in bytes for the query cache. Not supported from [MySQL 8.0](https://dev.mysql.com/doc/refman/5.7/en/query-cache-status-and-maintenance.html)
           </td>
         </tr>
 
@@ -252,7 +252,7 @@ The MySQL integration collects the following metrics:
           </td>
 
           <td>
-            Percentage of queries that are retrieved from the cache.
+            Percentage of queries that are retrieved from the cache. Not supported from [MySQL 8.0](https://dev.mysql.com/doc/refman/5.7/en/query-cache-status-and-maintenance.html)
           </td>
         </tr>
 
@@ -266,7 +266,7 @@ The MySQL integration collects the following metrics:
           </td>
 
           <td>
-            Number of noncached queries (not cacheable, or not cached due to the `query_cache_type setting`) per second.
+            Number of noncached queries (not cacheable, or not cached due to the `query_cache_type setting`) per second. Not supported from [MySQL 8.0](https://dev.mysql.com/doc/refman/5.7/en/query-cache-status-and-maintenance.html)
           </td>
         </tr>
 
@@ -280,7 +280,7 @@ The MySQL integration collects the following metrics:
           </td>
 
           <td>
-            Percentage of query cache memory that is being used.
+            Percentage of query cache memory that is being used. Not supported from [MySQL 8.0](https://dev.mysql.com/doc/refman/5.7/en/query-cache-status-and-maintenance.html)
           </td>
         </tr>
 
@@ -811,7 +811,7 @@ The MySQL integration collects the following metrics:
           </td>
 
           <td>
-            Number of free memory blocks in the query cache.
+            Number of free memory blocks in the query cache. Not supported from [MySQL 8.0](https://dev.mysql.com/doc/refman/5.7/en/query-cache-status-and-maintenance.html)
           </td>
         </tr>
 
@@ -825,7 +825,7 @@ The MySQL integration collects the following metrics:
           </td>
 
           <td>
-            Number of query cache hits per second.
+            Number of query cache hits per second. Not supported from [MySQL 8.0](https://dev.mysql.com/doc/refman/5.7/en/query-cache-status-and-maintenance.html)
           </td>
         </tr>
 
@@ -839,7 +839,7 @@ The MySQL integration collects the following metrics:
           </td>
 
           <td>
-            Number of queries added to the query cache.
+            Number of queries added to the query cache. Not supported from [MySQL 8.0](https://dev.mysql.com/doc/refman/5.7/en/query-cache-status-and-maintenance.html)
           </td>
         </tr>
 
@@ -853,7 +853,7 @@ The MySQL integration collects the following metrics:
           </td>
 
           <td>
-            Number of queries per second that were deleted from the query cache because of low memory.
+            Number of queries per second that were deleted from the query cache because of low memory. Not supported from [MySQL 8.0](https://dev.mysql.com/doc/refman/5.7/en/query-cache-status-and-maintenance.html)
           </td>
         </tr>
 
@@ -867,7 +867,7 @@ The MySQL integration collects the following metrics:
           </td>
 
           <td>
-            Number of queries per second registered in the query cache.
+            Number of queries per second registered in the query cache. Not supported from [MySQL 8.0](https://dev.mysql.com/doc/refman/5.7/en/query-cache-status-and-maintenance.html)
           </td>
         </tr>
 
@@ -881,7 +881,7 @@ The MySQL integration collects the following metrics:
           </td>
 
           <td>
-            Total number of blocks in the query cache.
+            Total number of blocks in the query cache. Not supported from [MySQL 8.0](https://dev.mysql.com/doc/refman/5.7/en/query-cache-status-and-maintenance.html)
           </td>
         </tr>