daily-release/Dec-8-2023-11_09

src/content/docs/accounts/accounts-billing/new-relic-one-user-management/authentication-domains-saml-sso-scim-more.mdx

@@ -117,7 +117,7 @@ More on these two options:
 
     To enable this setting, your authentication domain **Source of users** must have [SCIM enabled](#source-users).
 
-    Currently, we only have instructions for [Okta](/docs/accounts/accounts/automated-user-management/okta-scimsso-application-configuration). For other identity provider services, you can configure your identity provider to send us user type information using our [SCIM API user type specifications](/docs/accounts/accounts/automated-user-management/tutorial-manage-users-groups-scim/#manage-user-type).
+    Currently, we have instructions for [Okta](/docs/accounts/accounts/automated-user-management/okta-scimsso-application-configuration) and [Azure](https://forum.newrelic.com/s/hubtopic/aAX8W0000008d6MWAQ/relic-solution-make-full-core-basic-users-in-azure-active-directory-w-scim). For other identity provider services, you can configure your identity provider to send us user type information using our [SCIM API user type specifications](/docs/accounts/accounts/automated-user-management/tutorial-manage-users-groups-scim/#manage-user-type).
 
     How users upgrade requests are handled:
 

src/content/docs/accounts/accounts/automated-user-management/azure-ad-scimsso-application-configuration.mdx

@@ -1,5 +1,5 @@
 ---
-title: Azure AD SCIM/SSO application configuration
+title: Microsoft Entra ID SCIM /SSO application configuration
 tags:
   - Accounts
   - Accounts and billing
@@ -31,14 +31,14 @@ For that authentication domain, under **Source of users**, select **SCIM**. Copy
 
 ## Step 2. Set up Azure's New Relic app [#azure-app]
 
-Next, you'll set up Azure's New Relic SAML/SCIM app. Azure AD provides an application gallery, which includes various integrations for Azure AD, including the ones that New Relic offers. To set this up:
+Next, you'll set up Azure's New Relic SAML/SCIM app. Microsoft Entra ID, formerly know as Azure AD, provides an application gallery, which includes various integrations for Microsoft Entra ID, including the ones that New Relic offers. To set this up:
 
-1. Go to the Azure Active Directory admin center, and sign in if necessary. [aad.portal.azure.com/](https://aad.portal.azure.com/)
-2. Click on **All services** in the left hand menu.
-3. In the main pane, click on **Enterprise applications**.
+1. Go to the Microsoft Entra ID admin center, and sign in if necessary. [aad.portal.azure.com/](https://aad.portal.azure.com/)
+2. Click on **Applications** in the left hand menu.
+3. In the drop down, click on **Enterprise applications**.
 4. Click on **+New Application**.
 5. Find our SCIM/SSO application by entering **New Relic** in the name search box, and click on the application **New Relic by organization** (not **New Relic by account**).
-6. Click on **Add**.
+6. Click on **Create**.
 
 ## Step 3. Configure connection [#configure]
 
@@ -56,14 +56,15 @@ The New Relic SCIM/SSO application can now connect with New Relic. Continue with
 
 ## Step 4. Configure provisioning rules [#configure-rules]
 
-Initially, nothing is configured to be sent to New Relic. You must configure Azure AD to send changes for user creation, updates, and deactivation.
+Initially, nothing is configured to be sent to New Relic. You must configure Microsoft Entra ID to send changes for user creation, updates, and deactivation.
 
 Go to the **Provisioning** page and complete the following:
 
-1. Expand the **Mappings** section.
-2. Click **Provision Azure Active Directory Users**.
-3. Verify the **Target Object Actions**, **Create**, **Update**, and **Delete** checkboxes are all checked.
-4. Verify the **Attribute Mappings** look correct for your environment. Each of the New Relic attributes shown in the list must receive a value.
+1. In the overview page click on **Edit attribute mappings**.
+2. Expand the **Mappings** section.
+3. Click **Provision Azure Active Directory Users**.
+4. Verify the **Target Object Actions**, **Create**, **Update**, and **Delete** checkboxes are all checked.
+5. Verify the **Attribute Mappings** look correct for your environment. Each of the New Relic attributes shown in the list must receive a value.
 
    <Callout variant="tip">
      Ensure that the Azure Active Directory attributes shown in the list on the left are good sources for the information to send to New Relic. In particular, not all environments set the **mail** attribute. If your environment does not set the **mail** attribute, **userPrincipalName** could be a good alternative.

src/content/docs/alerts-applied-intelligence/applied-intelligence/incident-intelligence/Issues-and-Incident-management-and-response.mdx

@@ -231,16 +231,6 @@ To view the issues in a text format, in the right hand corner, click **Switch to
   src={accountsIssueSummary}
 />
 
-**Golden signals**
-
-Here you will find an indication about which of the 4 golden signals is related to issue, it means that there is a problem affecting the performance or availability of your distributed system in one or more of the key areas.
-
-**Related components**
-
-We're analyzing the title and based on that we get value from the list components.
-
-We also present a list of tags that are derived from the stack trace, based on Stack Overflow tags analysis.
-
 ## Use decisions [#decisions]
 
 To further reduce noise or get improved incident correlation, you can change or customize your decisions. Decisions determine how incidents are grouped together.

src/content/docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/rest-api-alerts/alerts-conditions-api-field-names.mdx

@@ -438,7 +438,7 @@ Not every field listed in this glossary is required for every condition type. Th
 
     In the UI, under **Advanced signal settings**, this is the **Aggregation window** field.
 
-    Default is **60 seconds**. Maximum is 120 minutes.
+    Default is **60 seconds**. Maximum is 6 hours.
 
     Used for:
 

src/content/docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/understand-technical-concepts/incident-event-attributes.mdx

@@ -253,7 +253,7 @@ All attributes are available for use in a [description](/docs/alerts/new-relic-a
 
     <tr>
       <td>
-        `incidentID`
+        `incidentId`
       </td>
 
       <td>
@@ -273,7 +273,7 @@ All attributes are available for use in a [description](/docs/alerts/new-relic-a
 
     <tr>
       <td>
-        `mutingRuleID`
+        `mutingRuleId`
       </td>
 
       <td>

src/content/docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/understand-technical-concepts/streaming-alerts-key-terms-concepts.mdx

@@ -258,7 +258,7 @@ In order to make loss of signal detection more effective and to reduce unnecessa
 
 An [aggregation window](/docs/using-new-relic/welcome-new-relic/get-started/glossary#aggregation-window) is a specific block of time. We gather data points together in an aggregation window, before evaluating the data. A longer aggregation window can smooth out the data, since an outlier data point will have more data points to be aggregated with, giving it less of an influence on the aggregated data point that is sent for evaluation. When a data point arrives, its timestamp is used to put it in the proper aggregation window.
 
-You can set your aggregation window to anything between **30 seconds** and **2 hours**. The default is **1 minute**.
+You can set your aggregation window to anything between **30 seconds** and **6 hours**. The default is **1 minute**.
 
 ### Delay/timer [#delay-timer]
 

src/content/docs/apm/agents/java-agent/configuration/java-agent-configuration-config-file.mdx

@@ -513,7 +513,7 @@ Set these options in the `common` stanza. To [override](#System_Properties) any
 
     Event ingest URI used by some agent features. Defaults to the US production ingest endpoint. Can be manually configured to send events to other ingest endpoints (for example, EU production: [`https://insights-collector.eu01.nr-data.net/v1/accounts/events`](https://insights-collector.eu01.nr-data.net/v1/accounts/events)).
 
-    FedRAMP compliant customers should use the [FedRAMP compliant endpoint](https://docs.newrelic.com/docs/security/security-privacy/compliance/fedramp-compliant-endpoints/#event-api): `https://gov-insights-collector.newrelic.com/v1/accounts/events`
+    FedRAMP compliant customers should use the [FedRAMP compliant endpoint](docs/security/security-privacy/compliance/fedramp-compliant-endpoints/#event-api): `https://gov-insights-collector.newrelic.com/v1/accounts/events`
   </Collapser>
 
   <Collapser
@@ -741,7 +741,7 @@ Set these options in the `common` stanza. To [override](#System_Properties) any
 
     Metric ingest URI used by some agent features. Defaults to the US production ingest endpoint. Can be manually configured to send metrics to other ingest endpoints (example EU production URI: [`https://metric-api.eu.newrelic.com/metric/v1`](https://metric-api.eu.newrelic.com/metric/v1)).
 
-    FedRAMP compliant customers should use the [FedRAMP compliant endpoint](https://docs.newrelic.com/docs/security/security-privacy/compliance/fedramp-compliant-endpoints/#metric-api): `https://gov-metric-api.newrelic.com/metric/v1`
+    FedRAMP compliant customers should use the [FedRAMP compliant endpoint](docs/security/security-privacy/compliance/fedramp-compliant-endpoints/#metric-api): `https://gov-metric-api.newrelic.com/metric/v1`
   </Collapser>
 
   <Collapser
@@ -3403,6 +3403,17 @@ The Java agent uses JMX to collect JVM data. Additionally the agent can expose l
   </Collapser>
 </CollapserGroup>
 
+## Kafka message queues [#kafka-message-queues]
+
+Detailed information on Kafka instrumentation configuration and can be found on the [Instrument Kafka message queues](docs/apm/agents/java-agent/instrumentation/java-agent-instrument-kafka-message-queues/) page.
+- [Kafka event collection(/docs/apm/agents/java-agent/instrumentation/java-agent-instrument-kafka-message-queues/#collect-kafka-events)
+- [Kafka node metrics](/docs/apm/agents/java-agent/instrumentation/java-agent-instrument-kafka-message-queues/#kafka-node-metrics)
+- [Kafka config events](/docs/apm/agents/java-agent/instrumentation/java-agent-instrument-kafka-message-queues/#kafka-config)
+- [Kafka streams transactions](/docs/apm/agents/java-agent/instrumentation/java-agent-instrument-kafka-message-queues/#collect-kafka-streams-transactions)
+- [Kafka connect transactions](/docs/apm/agents/java-agent/instrumentation/java-agent-instrument-kafka-message-queues/#collect-kafka-connect-transactions)
+- [Kafka distributed traces](/docs/apm/agents/java-agent/instrumentation/java-agent-instrument-kafka-message-queues/#collect-kafka-distributed-traces)
+
+
 ## Logs in context [#logs-in-context]
 
 Starting with Java agent version `7.6.0`, support for [logs in context](/docs/logs/logs-context/java-configure-logs-context-all) has been added to the agent, making it easy to use for supported logging frameworks. For tips on using the Java agent for logs in context, see [Java logs in context](/docs/logs/logs-context/java-configure-logs-context-all).
@@ -4017,7 +4028,7 @@ These options are set in the `message_tracer` stanza and can be [overridden](#Sy
 
 ## Security Agent [#sec-agent]
 
-[New Relic Security agent interactive applications security testing](https://docs.newrelic.com/docs/iast/use-iast/) (IAST) tests your applications for any exploitable vulnerability by replaying the generated HTTP request with vulnerable payloads. 
+[New Relic Security agent interactive applications security testing](docs/iast/use-iast/) (IAST) tests your applications for any exploitable vulnerability by replaying the generated HTTP request with vulnerable payloads. 
 
 <Callout variant="important">
   Run IAST with non-production deployments only to avoid exposing vulnerabilities on your production software.

src/content/docs/apm/agents/java-agent/troubleshooting/java-agent-identified-with-security-vulnerabilities.mdx

@@ -17,15 +17,17 @@ When a security scan is performed, it reports back vulnerabilities for the New R
 
 ## Cause
 
-While any software product has the potential to have security vulnerabilities, the New Relic Java agent may be erroneously identified by security products that scan for certain string patterns in files due to instrumentation jar files that are a part of the agent.
+While any software product can potentially have security vulnerabilities, the New Relic Java agent may be erroneously identified by security products. Security products that scan for certain string patterns in files may mistakenly flag instrumentation modules that are a part of the agent as vulnerable libraries. 
 
-The modules in the `instrumentation` package are named after the software frameworks they are designed to instrument. They are packaged as JAR files inside the agent jar file, `newrelic.jar`. Some security scanning tools detect these names and interpret them as being the actual software framework itself, when it's just an instrumentation module.
+These instrumentation modules are JAR files named after the software frameworks designed to instrument and their versions. They don't contain code from the frameworks but may contain classes with the same name. Some security scanning tools detect these names/versions and interpret them as being the actual software framework itself, when it's just an instrumentation module.
 
-Warnings for all jar files within the `newrelic.jar` file are false positives, and should be suppressed.
+They're found inside `newrelic.jar` under the `instrumentation` package, or inside `newrelic-security-agent.jar` under the `instrumentation-security` package.
+
+Warnings for any jar files within `newrelic.jar` or `newrelic-security-agent.jar` are false positives, and should be suppressed.
 
 ## Solution
 
-Suppress the false positive warnings coming from the `instrumentation` package in the `newrelic.jar` file with your scanning tool, including all JAR files whose names match the modules listed in the [New Relic Java agent repository](https://github.com/newrelic/newrelic-java-agent/tree/main/instrumentation).
+Suppress the false positive warnings coming from the `instrumentation` package in `newrelic.jar` and the `instrumentation-security` package in `newrelic-security-agent.jar` with your scanning tool, including all JAR files whose names match the modules listed in the [New Relic Java agent repository](https://github.com/newrelic/newrelic-java-agent/tree/main/instrumentation) or in the [New Relic SecurityAgent for Java](https://github.com/newrelic/csec-java-agent/tree/main/instrumentation-security).
 
 For example, false positives discovered by the `DependencyCheck` project at [github.com/jeremylong/DependencyCheck](https://github.com/jeremylong/DependencyCheck) can be suppressed with:
 

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

@@ -1040,7 +1040,8 @@ The `proxy` element supports the following attributes:
 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 level="info"
+<log enabled="true"
+  level="info"
   auditLog="false"
   console="false"
   directory="<var>PATH\TO\LOG\DIRECTORY</var>"
@@ -1154,7 +1155,38 @@ The `log` element supports the following attributes:
       </tbody>
     </table>
 
-    Send log messages to the console, in addition to the log file.
+    Send log messages to the console, in addition to the log file. Alternatively, set the `NEWRELIC_LOG_CONSOLE` environment variable in the application's environment.
+  </Collapser>
+
+  <Collapser
+    id="log-enabled"
+    title="enabled"
+  >
+    <table>
+      <tbody>
+        <tr>
+          <th>
+            Type
+          </th>
+
+          <td>
+            Boolean
+          </td>
+        </tr>
+
+        <tr>
+          <th>
+            Default
+          </th>
+
+          <td>
+            `true`
+          </td>
+        </tr>
+      </tbody>
+    </table>
+
+    If disabled, no logging is attempted. Intended for read-only file systems. Alternatively, set the `NEWRELIC_LOG_ENABLED` environment variable in the application's environment.
   </Collapser>
 
   <Collapser

src/content/docs/apm/agents/php-agent/features/browser-monitoring-php-agent.mdx

@@ -14,13 +14,13 @@ redirects:
 freshnessValidatedDate: never
 ---
 
-With the PHP agent, you can add [browser monitoring](/docs/browser/new-relic-browser/getting-started/introduction-new-relic-browser) to your pages either automatically or manually. To enable browser monitoring in the user interface, follow the procedures to [install the browser agent.](/docs/browser/new-relic-browser/installation/install-new-relic-browser-agent) Then follow the procedures in this section to set up the PHP agent.
+By default, the PHP agent automatically adds [browser monitoring](/docs/browser/new-relic-browser/getting-started/introduction-new-relic-browser) to your application's web pages. In this automated process, the PHP agent injects the browser agent JavaScript snippet into your webpages. This means you get front-end browser performance monitoring without needing to manually insert the JavaScript snippet into your page's head element. 
 
-To use browser monitoring with your PHP agent, ensure you have the latest release. For more information, see the [agent installation instructions](/docs/agents/php-agent/installation/php-agent-installation-overview).
+You can enable or disable auto-instrumentation in your PHP agent config file, or you can use the PHP agent API to manually configure browser monitoring.
 
-## Use auto-instrumentation [#auto_instrumentation]
+## Use or disable auto-instrumentation [#auto_instrumentation]
 
-To configure the agent to automatically instrument pages with the browser monitoring script, add or edit the [auto-instrumentation flag](/docs/agents/php-agent/configuration/php-agent-configuration#inivar-autorum) in your INI file. The PHP agent will automatically inject the browser monitoring's JS snippet into your pages.
+By default, the PHP agent automatically injects the browser monitoring's JavaScript snippet into your pages. To change this setting,  edit the [`newrelic.browser_monitoring.auto_instrument`](/docs/apm/agents/php-agent/configuration/php-agent-configuration/#inivar-autorum) setting in your INI file. 
 
 ```ini
 newrelic.browser_monitoring.auto_instrument=1

src/content/docs/apm/agents/php-agent/other-integrations/magento-business-insights.mdx

@@ -80,7 +80,7 @@ If you need to install the integration in a different way, see [Apache monitorin
 
         To install the integration:
 
-        1. Go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Add data**.
+        1. Go to **[one.newrelic.com](https://one.newrelic.com) > Add data**.
         2. Search for and click on **Elasticsearch**.
         3. Select an account and follow the guided install steps.
 
@@ -110,7 +110,7 @@ If you need to install the integration in a different way, see [Elasticsearch mo
             * Path to the configuration file: `/etc/newrelic-infra/integrations.d/`
             * Configuration file name: `mysql-database-config.yml`
 
-        2. Add this code snippet to the configuration file:
+        2. Add the following code snippet to the configuration file. Be sure to change replace `USERNAME`, `PASSWORD`, AND `DATABASE_NAME`:
 
             ```
             # NOTE: 'database' is an experimental API at this time
@@ -124,7 +124,7 @@ If you need to install the integration in a different way, see [Elasticsearch mo
                   apis:
                     - database: mysql
                   # connection string for an rds mysql instance. Be sure to use the writer endpoint here.  /sys is the default database. newrelic:Password is the user:pass.
-                      db_conn: magento2:password@tcp(localhost:3306)/magento2
+                      db_conn:<USERNAME>:<PASSWORD>@tcp(localhost:3306)/<DATABASE_NAME>
                       logging:
                         open: true
                   # custom_attributes: # applies to all queries
@@ -213,7 +213,7 @@ If you need to install the integration in a different way, see [Elasticsearch mo
 
     ## Install the Magento business insights dashboard [#install-dashboard]
 
-        1. Go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Dashboards**.
+        1. Go to **[one.newrelic.com > Add Data](https://one.newrelic.com) > Dashboards**.
         2. In the search bar, type "Magento business insights". The dashboard should appear. 
         3. Click on it to install.
 
@@ -227,7 +227,7 @@ Your Magento dashboard is considered a custom dashboard and can be found in the
 Interested in querying your Magento app data? Here's an example NRQL query checking the total registered customers on your Magento platform:
 
 ```sql
-SELECT LATEST(`Registered Accounts`) AS ‘Registered Accounts’ FROM MYSQLCustomerEntityRegisteredUsers
+SELECT LATEST(`Registered Accounts`) AS 'Registered Accounts' FROM MYSQLCustomerEntityRegisteredUsers
 ```
 
 ## What's next? [#whats-next]