If you don’t want to name the application using the app.config file, you should be able to use a combination of both the global and local newrelic.config files to configure the agent to monitor your applications.
First, in order to tell the profiler to pay attention to your application, edit the global newrelic.config file at C:\ProgramData\New Relic\.NET Agent to include the following, as a child of the
<configuration> element (replacing “MyService.exe” as needed):
<application name="MyService1.exe" />
Next, make a copy of the
newrelic.config file located at C:\ProgramData\New Relic\.NET Agent and place it in the root folder of the application you want to monitor. This makes the config file application-specific.
Inside the application-specific config file, change the name of your application in the line that looks like this:
Note that this name will be ignored if the application is also named inside the app.config file. If you don’t want to name the application in the app.config file, remove the app.config file line that looks like this
<add key = "NewRelic.AppName" value="Unique Name" />
Once this is all done, restart your application’s host process in order to allow the agent to pick up the changes. Exercise the application in order to get some data collected and the application should show up in your account a few minutes later.
One last thing to note. This process tells the agent to pay attention to your application and what to name it in the UI. It does not, however, tell the agent which parts of your application to monitor. Database and external calls will likely be collected in the APM UI, but without custom instrumentation, you will not see any transactions reported for non-IIS applications.
A good place to get an overview of creating custom instrumentation for non-IIS applications is in this forum post.
Let us know if you have any questions. I hope this helped.