Remove applications from New Relic

1. Disable the APM agent:

   • C SDK: Do a quick recompile and deploy. For example, surround your instrumentation in #ifdef, and set the value of YOURNAMESPACE_NEWRELIC_ENABLED with your build system.
   • Go: Set Enabled to false.
   • Java: Set agent_enabled to false.
   • .NET: Set Newrelic.AgentEnabled to false.
   • Node.js: Set agent_enabled to false.
   • PHP: Remove or disable both the newrelic.so and newrelic-daemon components. Set newrelic.enabled to false.
   • Python: Set monitor_mode to false.
   • Ruby: Set agent_enabled to false.

2. Restart the application server and wait up to ten minutes. Verify the color-coded health status for the app has turned to gray and is no longer reporting data.

3. To remove the APM application and its browser applications, call the /applications/delete endpoint of the New Relic REST API. For example:

   curl -X DELETE 'https://api.newrelic.com/v2/applications/YOUR_APP_ID.json' \
        -H 'X-Api-Key:YOUR_API_KEY' -i

   Copy

• If you've used the copy/paste method to install the browser agent, remove the JavaScript snippet from your application's pages. After 93 days, the application will be removed from New Relic.

  Tip

  If browser data continues to be reported, see our suggestions below.

• If your browser application is linked to an APM application, deleting the APM application also removes the browser application. Call the /applications/delete endpoint like this:

  curl -X DELETE 'https://api.newrelic.com/v2/applications/YOUR_APP_ID.json' \
       -H 'X-Api-Key:YOUR_API_KEY' -i

  Copy

Remove all references/dependencies to the New Relic's mobile SDK/frameworks, then rebuild the application. For more information, see the iOS and Android install docs.

After 93 days, the application will be removed from New Relic.

If you don't have proper permissions, you won't be able to remove an application.

All app data must stop reporting to New Relic before you can remove that entity from New Relic. In most cases, this takes between 10-15 minutes. In rare cases, it can take a few minutes longer.

If you have multiple agents reporting data under the same UI name, then you must make sure you disable or uninstall all of the agents associated with that entity.

If you have a PHP app and aren't able to remove it from the UI, possible causes include:

• You have not disabled both components of the PHP agent. You must stop or uninstall both newrelic.so and newrelic-daemon in order to be able to remove a PHP app. For more information, see New Relic daemon processes.
• You have set up per-directory monitoring of your PHP app, and unexpected PHP data is reporting as the default PHP application in the New Relic UI. To fix this, change the default app name in the PHP agent config.

If you don't know where an app's data is coming from, it may be because the app's name has been changed. When an app name is changed in the UI, it does not change the underlying app name being reported; it only changes how the app name appears in the UI.

To see if there is a difference between the reported name and the displayed name:

1. From one.newrelic.com, select APM, then select an application.

2. Scroll down to Settings and select Application.

3. Compare the name in the Application alias field to the name in the Your application still reports as message directly beneath it.

   To get host information about an app you are not familiar with:

4. From one.newrelic.com, select APM, then select an application.

5. From the summary view, review the Servers list.

   Once you have identified where app data is coming from, you can remove the app from New Relic.

To remove an app from New Relic, all data must have stopped reporting, including browser monitoring data. To verify that you have disabled or uninstalled the APM agent associated with the app:

1. Ensure that browser monitoring is disabled.

   • If your browser monitoring script is inserted by the APM agent, turn it off from inside the UI, in the agent's config file, or in both.
   • If you copied and pasted the monitoring JavaScript snippet in certain pages, remove that JavaScript snippet manually.

2. Ensure all caches have been cleared that the application uses, such as host caches, CDNs, or anything else that caches built pages.

3. Optional: To see a count of how many page views report from each domain, use this NRQL query:

   SELECT count(*) FROM PageView WHERE appName = 'YOUR_BROWSER_APP_NAME' FACET domain

   Copy

   If these steps don't resolve the issue, it is likely due to an end-user's browser cache that hasn't yet cleared. Wait until those caches clear. If your app has internal users, you may be able to identify the users and clear those caches.