Name your application

New Relic connects metrics to individual applications using your license key and the primary application name. Both the license key and the associated app names are defined in your configuration file. By giving your app multiple names, you can aggregate metrics for multiple agents across an entire app or service. If you do not specify the app name in your New Relic configuration file, most New Relic agents provide a default application name, such as My Application or PHP Application.

When you first deploy your app, edit your config file and change the default name. For detailed information and tips about how to decide what to name your app, refer to this blog post and your agent's configuration file documentation.

Name vs. alias

You can set the app name in two places: In the agent's configuration file and in New Relic's user interface. These have two different effects:

Location Effect
Config file

Changing the app name in the agent's configuration file will cause the application to report to a new heading in the New Relic user interface, with a total discontinuity of data.

This is useful, for example, if you want to start over and report new data. If no other agents are reporting to the old app name, the old app name will appear gray and can be deleted.

User interface Creating an alias for the app name only changes how the app name appears in the New Relic UI. Changing the alias does not affect how data is reported. It simply helps you keep track of your data with a useful alias.

Give each app a descriptive name

Each new app name creates a new application record in your New Relic UI. Collecting data by app name allows you to run an application on more than one server and have all the data aggregated (collected) under the same name. This is why you should change the default name to a more descriptive name before deploying your app.

Example: Multiple names for apps

The primary app name is an identifier the data collector uses to distinguish one application from another. If two applications share a name, then their data will be aggregated in the UI. This can be useful if you are using multiple names for your apps. For example, if two of your applications are named AppA;AggregateApps and one app is named AppB;AggregateApps, the UI will display three applications: AppA, AppB, and AggregateApps.

Assign the name in your config file

Set the app name value in the agent's configuration file. If you have deployed an app via one APM agent, and then deploy another app with the same name via a different APM agent, New Relic will automatically append the agent language name to the end of the second app's name. For example, if you deploy a Node.js app named New-App, and then deploy a .NET app named New-App, New Relic will automatically append the second app name as New-App (DOTNET).

Agent Configuration file value
Go Set AppName to a maximum of three names separated by a semicolon.
Java Set app_name to a maximum of three names separated by a semicolon.
.NET Use any of the available options to name your .NET app.
Node.js Set app_name to a maximum of three names separated by a comma. Enclose the names with single or double quotes. (Or, change the environment variable NEW_RELIC_APP_NAME.)
PHP Set newrelic.appname to a maximum of three names separated by a semicolon OR set app name by using the agent API method newrelic_set_appname.
Python Set app_name to a maximum of three names separated by a semicolon. Do not add a space after the semicolon, or the next name will be interpreted as a comment.
Ruby Set app_name to a maximum of three names separated by a semicolon.

Rename an app later

To change the app's alias in the New Relic user interface, or to change the app's name in the config file, see:

For more help

Additional documentation resources include:

Join the discussion about New Relic APM in the New Relic Online Technical Community! The Technical Community is a public platform to discuss and troubleshoot your New Relic toolset.

If you need additional help, get support at