For the latest, most advanced host monitoring, check out New Relic Infrastructure.
New Relic Servers for Linux detects the hostname configured on your server and uses that name when creating the Servers index. If necessary, you can change this name by updating your server's hostname.
However, a better solution is to associate arbitrary metadata with your servers by using labels and categories. Labels and categories can help prevent problems typically addressed by renaming your servers.
The New Relic UI uses the hostname to link APM-monitored applications to their parent server. The
hostname= setting may cause a different name to be reported for the server than what is reported by any monitored applications. This difference may cause the linkage between the APM app and the server in the New Relic user interface to break.
Change the OS-level hostname
If you do not want to use the New Relic user interface to label your Linux server, you can change your server's OS-level hostname settings. After you restart nrsysmond, this will automatically change the default name that appears in the New Relic user interface.
Change the New Relic configuration
If you do not want to label your Linux server or change the hostname at the OS-level, you can modify the nrsysmond.cfg file to contain a new
hostname= configuration setting. However, if you manually override the
hostname= setting, Servers for Linux will not pick up later changes to the OS-level hostname.
To change the hostname in nrsysmond.cfg (typically located at /etc/newrelic/nrsysmond.cfg):
hostname=setting to your nrsysmond.cfg file:
- Restart nrsysmond.