I have a simple question: I’m using the
<instrumentation><applications><application>-element (see: https://docs.newrelic.com/docs/agents/net-agent/configuration/net-agent-configuration#application-instrumentation) in the global
newrelic.config-file to target multiple .NET Framework-based Windows Services hosted on the same machine but I want to expose them with custom names.
Something along these lines:
<instrumentation> <applications> <application name="MyAppA.exe" applicationName="IniTech.MyAppA" /> <application name="MyAppB.exe" applicationName="IniTech.MyAppB" /> </applications> </instrumentation>
In the example above, the
name-attribute is valid and is used to target an executable for monitoring. The
applicationName-attribute is a hypothetical one in which I would like to control the application its name as it would appear in the APM dashboard.
I know that it’s possible to name an application into its own configuration file but I really would like to keep the introduction of NR-specific configuration parameters to my applications to an absolute minimum…
New Relic edit
- I want this, too
- I have more info to share (reply below)
- I have a solution for this
We take feature ideas seriously and our product managers review every one when plotting their roadmaps. However, there is no guarantee this feature will be implemented. This post ensures the idea is put on the table and discussed though. So please vote and share your extra details with our team.