Merge pull request #20741 from newrelic/daily-release/05-21-25-night

Daily release/05 21 25 night

Author: cbehera-newrelic

src/content/docs/apm/agents/net-agent/troubleshooting/app-hangs-on-startup.mdx

@@ -0,0 +1,31 @@
+---
+title: Application hangs on startup
+type: troubleshooting
+tags:
+  - Agents
+  - NET agent
+  - Troubleshooting
+metaDescription: Learn how to resolve startup hangs in .NET 8 applications caused by a known runtime issue. 
+redirects:
+freshnessValidatedDate: never
+---
+
+## Problem
+
+When using the .NET agent, your .NET 8.x application may hang during startup due to a known runtime issue.
+
+## Solution
+
+This issue is caused by a [bug](https://github.com/dotnet/runtime/issues/93175) in the .NET runtime. While the bug is fixed in .NET 9, a backported fix is available for .NET 8. However, the fix introduces a breaking change and is not enabled by default.
+
+To enable the fix, apply the following AppConfig to your application:
+
+```
+"configProperties": {
+ "System.Diagnostics.Tracing.CounterCallbackOnTimerThread": true
+} 
+```
+
+You can also apply this setting by modifying your MSBuild project file or using an environment variable. For more details, refer to Microsoft's documentation on [.NET runtime configuration settings](https://learn.microsoft.com/en-us/dotnet/core/runtime-config/).
+
+

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

@@ -175,7 +175,7 @@ Based on the information above the PHP agent, can be installed on operating syst
       </td>
 
       <td>
-        3.15, 3.16, 3.17, 3.18, 3.19, 3.20
+        3.17, 3.18, 3.19, 3.20
       </td>
 
       <td>
@@ -241,49 +241,13 @@ Based on the information above the PHP agent, can be installed on operating syst
       </td>
     </tr>
 
-    <tr>
-      <td>
-        CentOS Linux
-      </td>
-
-      <td>
-        7
-      </td>
-
-      <td>
-        x86_64
-      </td>
-
-      <td>
-        [tar file](/docs/apm/agents/php-agent/installation/php-agent-installation-tar-file), [RPM](/docs/apm/agents/php-agent/installation/php-agent-installation-aws-linux-redhat-centos)
-      </td>
-    </tr>
-
-    <tr>
-      <td>
-        CentOS Linux
-      </td>
-
-      <td>
-        7
-      </td>
-
-      <td>
-        aarch64
-      </td>
-
-      <td>
-        [tar file](/docs/apm/agents/php-agent/installation/php-agent-installation-tar-file)
-      </td>
-    </tr>
-
     <tr>
       <td>
         CentOS Stream
       </td>
 
       <td>
-        8, 9
+        9
       </td>
 
       <td>
@@ -301,7 +265,7 @@ Based on the information above the PHP agent, can be installed on operating syst
       </td>
 
       <td>
-        8, 9
+        9
       </td>
 
       <td>
@@ -355,7 +319,7 @@ Based on the information above the PHP agent, can be installed on operating syst
       </td>
 
       <td>
-        10, 11, 12
+        11, 12
       </td>
 
       <td>
@@ -373,7 +337,7 @@ Based on the information above the PHP agent, can be installed on operating syst
       </td>
 
       <td>
-        10, 11, 12
+        11, 12
       </td>
 
       <td>

src/content/docs/apm/new-relic-apm/maintenance/remove-applications-new-relic.mdx

@@ -83,7 +83,7 @@ Before you can remove an application monitored by New Relic APM, browser monitor
     id="remove-otel-apps"
     title="OpenTelemetry"
   >
-    After 93 days the app will be removed from the UI. If you want to remove it sooner than that, use [NerdGraph to delete the relevant entities](/docs/apis/nerdgraph/examples/nerdgraph-entities-api-tutorial/#delete-entities). To find entity IDs, see [Entities](/docs/new-relic-one/use-new-relic-one/core-concepts/what-entity-new-relic/#find).
+    After 8 days the app will be removed from the UI. If you want to remove it sooner than that, use [NerdGraph to delete the relevant entities](/docs/apis/nerdgraph/examples/nerdgraph-entities-api-tutorial/#delete-entities). To find entity IDs, see [Entities](/docs/new-relic-one/use-new-relic-one/core-concepts/what-entity-new-relic/#find).
   </Collapser>
 </CollapserGroup>
 

src/content/docs/browser/new-relic-browser/browser-apis/start.mdx

@@ -45,6 +45,7 @@ See [Feature names](#feature-names) for a list of feature names which can be sta
 * session_replay
 * session_trace
 * spa
+* logging
 
   <Callout variant="important">
     The response body of the `page_view_event` harvest contains critical information for running the other features. Deferring the start of `page_view_event` will cause all other features to wait until `.start()` is called.
@@ -72,6 +73,7 @@ NREUM.init = {
   session_replay: {autoStart: false},
   session_trace: {autoStart: false},
   spa: {autoStart: false},
+  logging: {autoStart: false},
   // other configurations
   // ...
 }

src/content/docs/data-apis/manage-data/drop-data-using-nerdgraph.mdx

@@ -14,6 +14,12 @@ redirects:
 freshnessValidatedDate: never
 ---
 
+<Callout variant="important">
+  As of May 21, 2025, new customers can no longer use NRQL drop rules. Leverage [New Relic Pipeline Control](/docs/new-relic-control/pipeline-control/overview/). Pipeline cloud rules are the direct replacement of NRQL drop rules, and pipeline gateway can also help manage data. 
+
+  [NRQL drop rules will be end of life](/eol/2025/06/drop-rule-filter) January 7, 2026.
+</Callout>
+
 One way to [manage your data ingest](/docs/data-apis/manage-data/manage-data-coming-new-relic) is to set up data dropping rules. With data dropping you can:
 
 * Filter out unimportant low-value data

src/content/docs/logs/ui-data/drop-data-drop-filter-rules.mdx

@@ -13,6 +13,12 @@ redirects:
 freshnessValidatedDate: never
 ---
 
+<Callout variant="important">
+  As of May 21, 2025, new customers can no longer use NRQL drop rules via the logs management UI. Leverage [New Relic Pipeline Control](/docs/new-relic-control/pipeline-control/overview). Pipeline cloud rules are the direct replacement of NRQL drop rules, and pipeline gateway can also help manage data. 
+
+  [NRQL drop rules will be end of life](/eol/2025/06/drop-rule-filter) January 7, 2026.
+</Callout>
+
 After log event data has been sent to New Relic, it can either be stored in our NRDB database or dropped (discarded). To drop log data, you can use the logs management UI, as explained in this document. You can also use [NerdGraph to drop data](/docs/accounts/accounts/data-management/drop-data-using-nerdgraph). NerdGraph is our GraphQL Explorer.
 
 ## Savings, security, speed [#why-it-matters]

src/content/eol/2025/05/drop-rule-filter.md

@@ -0,0 +1,42 @@
+---
+title: 'End of Life Announcement: Drop Filter Rules API'
+subject: EOL for Drop Filter Rules API
+publishDate: '2025-05-21'
+eolEffectiveDate: '2026-01-07'
+---
+
+Effective January 7, 2026, the NRQL Drop Filter Rules API will be discontinued and fully replaced by the [Pipeline cloud rules API](/docs/new-relic-control/pipeline-control/cloud-rules-api/). Your existing NRQL drop filter rules will be automatically migrated. However, you'll need to take action to ensure a smooth transition to the new cloud rules API.
+
+## Background [#bg]
+
+This update is part of our ongoing work to improve our platform and streamline our APIs. This helps us ensure continued innovation and a more sustainable system. The new [Pipeline cloud rules API](/docs/new-relic-control/pipeline-control/cloud-rules-api/), integrated with Pipeline Control, offers the same functionality as the old API. It also works with the next-generation New Relic Control system, providing a more robust, consistent, and unified experience.
+
+## What's changing [#whats-changing]
+* The NRQL Drop Filter Rules API will be deprecated and shut off on January 7, 2026.
+* After January 7, 2026, you must use the [Pipeline cloud rules API](/docs/new-relic-control/pipeline-control/cloud-rules-api/), or the Pipeline Control UI, for all drop rule creation and management.
+* Renewals after January 7, 2026 will require the use of [Pipeline cloud rules API](/docs/new-relic-control/pipeline-control/cloud-rules-api/), which is available with the [Advanced Compute add-on](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/add-on-billing/).
+
+## What do you need to do [#what-to-do]
+
+* Update your integrations and references to the new Pipeline Cloud Rules API by January 7, 2026.
+* Do not migrate your drop rules. New Relic will handle the move from the old NRQL Drop Filter Rules API to the [Pipeline cloud rules API](/docs/new-relic-control/pipeline-control/cloud-rules-api/).
+* Access a unified rules list in June 2025 for migration assistance and visibility across both APIs.
+* Add Advanced Compute by January 7, 2026 (if you are on [Pay As You Go](/docs/licenses/license-information/usage-plans/new-relic-usage-plan/#pay-as-you-go)) to maintain uninterrupted use of drop rules.
+* Upgrade to a paid plan (if you are on the free tier) to continue using drop rules after the effective date.
+
+## If no action is taken [#no-action]
+* After January 7th, 2026, calls to NRQL Ddrop Filter Rrules API will fail. Migrate to [Pipeline cloud rules API](/docs/new-relic-control/pipeline-control/cloud-rules-api/) by then. 
+* If you are on [Pay As You Go](/docs/licenses/license-information/usage-plans/new-relic-usage-plan/#pay-as-you-go) or free tier, drop rules will be disabled if your account is not on Advanced Compute at the next renewal after January 7th, 2026.
+* If you have a commitment contract, work with your account team to add Advanced Compute before your next renewal to ensure continuous rule processing and authoring. Otherwise, rule creation will be disabled, and existing rules will be turned off at your renewal.
+
+## Next steps
+* Review your current use of NRQL Drop Filter Rules API.
+* Begin planning your migration to the [Pipeline cloud rules API](/docs/new-relic-control/pipeline-control/cloud-rules-api/).
+* Watch for communications regarding the unified rules list and migration tools, coming June 2025.
+* Contact your New Relic representative or support for assistance with migration or to discuss your options.
+
+We understand that changes to capabilities can be disruptive, and we are committed to supporting you through this transition. Our goal is to provide ample time and resources to ensure a smooth migration with minimal impact to your workflows.
+
+Our support team is here to assist you during this transition. If you have any questions about these changes, please [contact Support](/docs/new-relic-solutions/solve-common-issues/find-help-get-support/) or reach out to your account team. To learn more about the advantages of Pipeline Control UI, check out [New Relic Pipeline Control](https://newrelic.com/platform/pipeline-control).
+
+Thank you for your partnership and understanding as we continue to improve our platform and services.

src/nav/apm.yml

@@ -388,6 +388,8 @@ pages:
           - title: Troubleshooting
             path: /docs/apm/agents/net-agent/troubleshooting
             pages:
+              - title: Application hangs on startup
+                path: /docs/apm/agents/net-agent/troubleshooting/app-hangs-on-startup
               - title: No data appears
                 path: /docs/apm/agents/net-agent/troubleshooting/no-data-appears-net
               - title: Generate logs for troubleshooting