Merge pull request #19591 from newrelic/daily-release/12-20-24-morning

Daily release/12 20 24 morning

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

@@ -420,6 +420,18 @@ common: &default_settings
     # Default is false.
     audit_logging: false
 
+    # The time interval, in seconds, of how often JFR data is sent to New Relic.
+    # The default is 10 seconds.
+    harvest_interval: 10
+
+    # The size of the queue used to store JFR events. Increasing this can reduce gaps in JFR reported data
+    # but can also cause resource issues in the agent or cause data to be dropped if backend pipeline
+    # limits are exceeded.
+    # See: https://docs.newrelic.com/docs/data-apis/ingest-apis/event-api/introduction-event-api/#limits
+    #      https://docs.newrelic.com/docs/data-apis/ingest-apis/metric-api/metric-api-limits-restricted-attributes/
+    # Default is 250000
+    queue_size: 250000
+
   # User-configurable custom labels for this agent.  Labels are name-value pairs.
   # There is a maximum of 64 labels per agent.  Names and values are limited to 255 characters.
   # Names and values may not contain colons (:) or semicolons (;).

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

@@ -162,6 +162,7 @@ The agent automatically instruments these frameworks and libraries:
     The agent automatically instruments the following frameworks. To install the Java agent on supported frameworks, see [Install the Java agent](/docs/agents/java-agent/installation/java-agent-manual-installation).
 
     * Akka 2.2.0-RC1 to latest
+    * Amazon Firehose SDK 2.1.0 to latest
     * Amazon Kinesis v1 and v2 SDKs
     * Amazon Lambda SDK 1.11.280 to latest
     * AmazonS3 client 1.2.13 to latest
@@ -197,6 +198,7 @@ The agent automatically instruments these frameworks and libraries:
     * Pekko 1.0.0 to latest
     * Pekko-Http 1.0.0 to latest
       * Scala 2.13
+      * Scala 3
     * Play Server 2.3.0 to latest {/* Play support will extend to latest once we support Pekko-Http */}
     * Quartz Job Scheduler 1.8.3 to 2.2.x
     * RESTEasy 2.2-RC-1 to latest
@@ -292,7 +294,7 @@ The agent automatically instruments these frameworks and libraries:
     * Oracle ojdbc5, ojdbc6, ojdbc7, ojdbc8, ojdbc10, ojdbc14
     * Postgres 8.0-312.jdbc3 to latest
     * R2DBC H2 0.8.x to 0.9.x
-    * R2DBC MariaDB 1.0.2 to 1.1.1
+    * R2DBC MariaDB 1.0.2 to latest
     * R2DBC MySQL 0.8.x to latest
     * R2DBC MSSQL 0.8.0 to latest
     * R2DBC Oracle 0.x to latest

src/content/docs/codestream/troubleshooting/proxy-support.mdx

@@ -12,6 +12,8 @@ If you're experiencing connectivity issues with the New Relic CodeStream extensi
 
 Look for the <DNT>**Proxy Support**</DNT> setting and make sure it is set to <DNT>**on**</DNT>. You will also need to disable Strict SSL checking since your CodeStream extension won’t see the SSL/TLS certificates as coming from a legitimate certificate authority.
 
+If you want to limit the allowed certificates to specific certificates used by your company, you can place those certificates in a file, and add the path to that file in the **Extra certs** field.
+
 Here's what these settings look like in VS Code.
 
 <img

src/content/docs/data-apis/ingest-apis/metric-api/cardinality-management.mdx

@@ -10,19 +10,19 @@ freshnessValidatedDate: 2024-09-24
   This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy).
 </Callout>
 
-As an administrator at New Relic, one of your tasks is to make sure you don't go beyond your limit of [GB Ingested](/docs/licenses/license-information/product-definitions/new-relic-one-pricing-definitions/#gb-ingested). One tool for tracking your ingest is the Cardinality Management UI. You'll find helpful graphs and tables explaining your ingest so you can take action if you're approaching limits.
+Cardinality refers to the number of unique elements in a set, specifically the unique attribute combinations observed for a given metric within a one-day period. This data resets daily at UTC midnight. As cardinality increases with more unique combinations, it can impact data limits. Understanding and managing cardinality is crucial to optimize data usage and preventing limit issues.
 
-## Where can you manage cardinality? [#where-manage]
+As a New Relic administrator, you oversee data ingestion to ensure it stays within the specified limit. <DNT>**Cardinality Management**</DNT> offers graphs and tables to detail your data usage, allowing you to take action if you're approaching your limits.
 
-In the New Relic UI, you can find this with other administration tools. Click your name in the lower left and go to **Administration > Cardinality Management**.
+To view the **<DNT>Cardinality Management</DNT>** UI, go to **<DNT>[one.newrelic.com](https://one.newrelic.com)</DNT> > (click your user name) > <DNT>Administration > Cardinality Management</DNT>**.
 
-## Account Cardinality Breakdown [#account-breakdown]
+## Account cardinality breakdown [#account-breakdown]
 
-If you're in an organization with multiple accounts, you can see a breakdown of cardinality by each account. As with most capabilities within New Relic, you can change the account you are currently viewing by selecting the account picker in the top right corner. The UI will display information about the selected account, as long as you have access to that account. 
+If your organization has multiple accounts, you can view a breakdown of cardinality for each account. To switch accounts, use the account picker in the top right corner. If you have access to the account, you can see the account cardinality information on the UI.
 
 ### Usage over time [#usage-over-time]
 
-On the opening page of **Cardinality Management**, you can view the **Usage over time** chart:
+On the landing page of <DNT>**Cardinality Managemen**t</DNT>, you can view the <DNT>**Usage over time**</DNT> chart. The chart displays the account cardinality usage compared the limit of that account.
 
 <img
     style={{ align: 'left',maxWidth: '90%' }}
@@ -31,19 +31,14 @@ On the opening page of **Cardinality Management**, you can view the **Usage over
     src="/images/apis-and-data_screenshot-crop_usage-over-time.webp"
 />
 
-This shows following:
-
-* The limit that is currently at 5 million account cardinality.
-* The current cardinality usage for the account, which is in the 2 to 4 million range. If there's no change in the value, then a new data point isn't reported. This can appear as an empty data point, but it's not data loss. This behavior may change as the feature is finalized.
-
-
 <Callout variant="tip">
-  You can modify this timeseries by changing the time-picker in the top right corner. Also, the time-picker only affects the timeseries and does not affect the **Metrics** table under the timeseries.
+  If the cardinality usage value remains unchanged, then a new data point isn't reported. So, you may see an empty data point. This isn't data loss.
 </Callout>
 
+To adjust the timeseries, use the time picker in the top right corner. This change only affects the timeseries in the chart and does't impact the Metrics table following it.
 ### Metrics table [#metrics-table]
+Check the top 20 metrics with the highest cardinality in the selected account for the day. View the breakdown of account cardinality in the <DNT>**Metrics**</DNT> table, organized by metric name.
 
-In the **Metrics** table, you can see the breakdown of account cardinality by metric name:
 
 <img
     style={{ align: 'left',maxWidth: '90%' }}
@@ -52,19 +47,11 @@ In the **Metrics** table, you can see the breakdown of account cardinality by me
     src="/images/apis-and-data_screenshot-crop_metrics-table.webp"
 />
 
-This table shows the top 20 highest cardinality metrics in an account. The table provides the following details:
-* The name of the metric
-* The current overall usage of the metric (the ratio of current usage to current limit)
-* The actual values of the current cardinality
-* The current limit of that metric name 
-
-<Callout variant="tip">
-  All metrics have a default metric limit of 100,000.
-</Callout>
+All metrics have a default cardinality limit of 100,000. Based on your requirement, you can [adjust the per-metric limits](#per-metric-limit-adjustment).
 
 ## Metric cardinality breakdown [#metric-cardinality-breakdown]
 
-You can view a deeper layer of granularity in your metrics by clicking on any metric name. You can view a breakdown of the specific metric's cardinality details. 
+Select any metric in the <DNT>**Metrics**</DNT> table to view its detailed cardinality information in a dedicated <DNT>**Cardinality Management**</DNT> page.
 
 <img
     style={{ align: 'left',maxWidth: '90%' }}
@@ -73,81 +60,89 @@ You can view a deeper layer of granularity in your metrics by clicking on any me
     src="/images/apis-and-data_screenshot-crop_metric-cardinality-breakdown.webp"
 />
 
-### Metric and account cardinality bar charts [#bar-charts]
+### Bar charts
+In the metric-specific view, you can check current cardinality usage with two bar charts:
+* <DNT>**Metric cardinality budget**</DNT> (limit): Cardinality usage specific to the metric
+* <DNT>**Account cardinality budget**</DNT> (limit): Overall cardinality usage for the account
 
-In this metric-specific view, you can see the current cardinality usage as two bar charts, one for **Metric cardinality budget** and one for **Account cardinality budget** (the overall account usage). 
+### Usage over time (for metrics) [#usage-over-time-metrics]
 
-## Usage over time (for metrics) [#usage-over-time-metrics]
-
-Below the bar charts is a chart of a timeseries query showing the metric cardinality usage versus the limit of that metric. Again, you can change the time-picker to view different time periods of this individual metric's cardinality data. 
+The <DNT>**Usage over time**</DNT> chart displays the metric cardinality usage compared the limit of that metric. You can adjust the time picker to view different time periods of this individual metric's cardinality data.
 
 <Callout variant="tip">
-  For any metric that has exceeded its cardinality limit (usually 100,000) New Relic will still attempt to populate information on the metric, but it will be slightly slower since it uses RAW data instead of using aggregated data. 
+    If a metric exceeds its cardinality limit, New Relic still populates information for the metric, but it may be slightly slower as it uses raw data instead of aggregated data.
 </Callout>
 
 ### Attributes table [#attributes-table]
 
-Under the timeseries, a table shows the attributes that are powering the metric cardinality. Note that the numbers usually don’t add up to 100% because cardinality is calculated as a combination of several attributes. However, it is a good indicator of what your highest contributing attributes are. 
-
-<img
-    style={{ align: 'left',maxWidth: '90%' }}
-    title="Screenshot showing attributes behind metrics"
-    alt="Screenshot showing attributes behind metrics"
-    src="/images/apis-and-data_screenshot-crop_metric-attributes.webp"
-/>
-
-This information is only for the last day (since UTC midnight), which is when cardinality resets (both account and metric). 
-
-You can also view specific information about an attribute, which can help you make decisions about whether or not that attribute is useful. You can see a sample of the attribute values by clicking the menu on the right side of the attribute row.
-
+The <DNT>**Attributes**</DNT> table has the list of top 20 attributes that majorly contribute to the metric's cardinality. To view the values of a specific attribute, click the options menu on the right side of the attribute row and select <DNT>**View attribute values**</DNT>.
 
 ## Account pruning rules [#account-pruning-rules]
 
-A common way to keep account cardinality under its limit is to implement pruning rules for metrics and attributes you don't consider important. 
+A common method to maintain account cardinality within its limit is to implement pruning rules for non-critical attributes, which removes unnecessary data.
 
 ### View account pruning rules [#view-pruning-rules]
 
-You can view pruning rules by clicking into a metric and then clicking **View Pruning Rules**. This will bring up a scrollable list of all pruning rules associated with an account. You can also delete pruning rules associated with an account in this view:
-
-<img
-    style={{ align: 'left',maxWidth: '90%' }}
-    title="Screenshot showing the link to pruning rules on the Attributes page"
-    alt="Screenshot showing the link to pruning rules on the Attributes page"
-    src="/images/apis-and-data_screenshot-crop_view-pruning-rules.webp"
-/>
-
+To view account pruning rules:
+1. Go to the **Cardinality Management** page of the account.
+2. From the **Metrics** table, click <DNT>**View Pruning Rules**</DNT>. A scrollable list of all pruning rules associated with the account appears.
+  <Callout variant="tip">
+If no pruning rules exist in the account, the <DNT>**View Pruning Rules**</DNT> button doesn't appear.
+</Callout>
 
 ### Create a pruning rule [#create-pruning-rule]
 
-You can create a pruning rule based on attributes within the UI. To create a pruning rule:
+To create a pruning rule:
 
-1. Select the checkboxes next to the attributes you want to prune. 
+1. Go to the **Cardinality Management** page of the account.
+2. From the **Metrics** table, select the metric in which you want to create a pruning rule. The **Cardinality Management** page of the metric opens.
+3. Go to the **Attributes** table and select the attributes you want to prune. 
   <img
     style={{ align: 'left', maxWidth: '90%' }}
     title="Screenshot showing how to select attributes for pruning rule"
     alt="Screenshot showing how to select attributes for pruning rule"
     src="/images/apis-and-data_screenshot-crop_select-attributes-for-pruning-rule.webp"/>
 
-2. Click **Create pruning rule**.
-3. In the pop-up with information about how the pruning rule affects the metric's cardinality, enter a rule name or description.
+3. Click <DNT>**Create pruning rule**</DNT>. A pop-up appears, providing details on how the pruning rule impacts the metric's cardinality.
+  
   <img
     style={{ align: 'left' }}
     title="Screenshot of page to name the pruning rule"
     alt="Screenshot of page to name the pruning rule"
     src="/images/apis-and-data_screenshot-crop_name-pruning-rule.webp"/>
-
-4. Click **Submit** to generate the pruning rule. 
 
-It's important to note that pruning rules are instantaneous. The information will be pruned instantly after creating the rule, so make sure you really want to prune the data. 
+3. Enter a rule name or description.
+
+4. To create the pruning rule, click <DNT>**Submit**</DNT>.
 
-If you create a pruning rule, you can still delete the pruning rule after it's made, but before it's deleted, the rule may prune a little bit of data. 
+<Callout variant="important">
+Pruning rules take effect immediately. Ensure you want to prune the data before creating a rule. You can delete a pruning rule after creating it, but the rule may prune some data before you remove it.
+</Callout>
 
 ### Delete a pruning rule [#delete-pruning-rule]
 
 To delete a pruning rule:
 
-1. Click **View All Pruning Rules**.
-2. Scroll to the relevant pruning rule, and then click **Delete**. 
+1. Go to the **Cardinality Management** page of the account.
+2. From the **Metrics** table, select <DNT>**View Pruning Rules**</DNT>.
+3. Scroll to the relevant pruning rule and delete it. 
+
+## Per-metric limit adjustment [#per-metric-limit-adjustment]
+
+When all attributes of a specific metric are crucial and you approach your cardinality limit, you can adjust the per-metric limit to meet your needs. Typically, metrics have a default maximum cardinality of 100,000, but you can increase this up to 1 million per metric.
+
+<Callout variant="tip">
+  Your account's overall cardinality limit remains unchanged. Therefore, setting all metric limits to 1 million without careful consideration could quickly exhaust your account's cardinality capacity.
+</Callout>
+
+### Edit per-metric limit [#edit-per-metric-limit]
+
+1. Go to the specific metric's <DNT>**Cardinality Management**</DNT> page.
+2. Select <DNT>**Adjust metric budget**</DNT>.
+3. Update the limit value to meet your needs. Make sure, it is less than or equal to 1 million.
+
+The updated limit appears in the <DNT>**Cardinality Management**</DNT> page within a few minutes.
+
 
 ## What's next [#whats-next]