Your data. Anywhere you go.

New Relic for iOS or Android


Download on the App Store    Android App on Google play


New Relic Insights App for iOS


Download on the App Store


Learn more

Close icon

Feature Idea: Custom hostname configuration in newrelic.config

feature-idea

#1

For elastic-scaling instances (eg. AWS Elastic Beanstalk), the hostnames can be (is) mangled and required reboot to take into effect. You are able to modify the Infrastructure client to send a different hostname, can the same be brought into the .NET (and .NET Core) agent so that we can match a proper, friendly name in the APM?

There is a previous thread that others have talked about the same issue:


New Relic edit

  • I want this, too
  • I have more info to share (reply below)
  • I have a solution for this

0 voters

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.


#2

Thanks for sharing a bit about your use case, @Alan.Lok! I have added a poll so that others can vote for this feature! Please be sure to vote! :blush:


#3

@Linds - this was released on Oct 3: https://docs.newrelic.com/docs/release-notes/agent-release-notes/net-release-notes/net-agent-8775