Owner, Admins, or add-on managers
Follow the appropriate procedure to rename your Browser app depending on the deployment option you used to add it to New Relic Browser.
Rename app monitored by New Relic APM
If you added an app to New Relic Browser already being monitored by New Relic APM, the app name that appears in New Relic Browser is the same as the app name in the New Relic APM UI. To rename the app, use any of these options as applicable.
|Rename and continue collecting data||
This option is useful when you simply want to give an app a different display name (alias).
|Stop reporting under the old name||
To stop reporting data under the old name and begin collecting data with a new name (app identifer), use the APM agent's configuration file. This changes the identifier that New Relic's data collector uses to distinguish one app from another. Based on the data retention schedule, New Relic will retain historical data collected under the old name, and will collect and aggregate data under the new name. If one or more apps share the same name, then their data will be aggregated in the UI.
If you change the app identifier, a new application will appear in the New Relic user interface with the new name, and data will stop reporting to the app(s) with the old name.
- App monitored by New Relic APM that was deployed via the copy/paste method
- Single page app (SPA)
- Any standalone Browser app that is not also monitored by New Relic APM
- If your standalone app has multiple names, copy the custom app IDs in your configuration script to your new app.
Based on the data retention schedule, New Relic will retain historical data collected under the old name, and will collect and aggregate data under the new name.
Rename app via New Relic REST API (v2)
Follow standard procedures to change the APM app alias via REST API or API Explorer. New Relic automatically changes the display name for the app everywhere in the New Relic UI, including New Relic Browser.