Follow the appropriate procedure to rename your Browser app depending on the deployment option you used to add it to Browser.
If you added an app to Browser already being monitored by APM, the app name that appears in Browser is the same as the app name in the 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 our user interface with the new name, and data will stop reporting to the app(s) with the old name.
- App monitored by APM that was deployed via the copy/paste method
- Single page app (SPA)
- Any standalone Browser app that is not also monitored by 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.
If you need more help, check out these support and learning resources:
- Browse the Explorers Hub to get help from the community and join in discussions.
- Find answers on our sites and learn how to use our support portal.
- Run New Relic Diagnostics, our troubleshooting tool for Linux, Windows, and macOS.
- Review New Relic's data security and licenses documentation.