When APM and infrastructure agents are installed on the same hosts and use the same New Relic license key, APM data should appear in Infrastructure, and vice versa. If you do not see this APM-Infrastructure linkage, follow these troubleshooting tips.
If you completed the APM/Infrastructure integration but do not see New Relic APM data in Infrastructure, try these troubleshooting procedures.
- Restart the app server.
If you have not restarted your APM-monitored application in a few weeks or months, the data streams from Infrastructure and APM may not be linked.
- Restart your app server.
- Generate some traffic for your app.
- Wait a few minutes, and then check for APM data in infrastructure monitoring.
- Make sure the hostnames are the same in APM and Infrastructure.
If the hostnames are different in APM and infrastructure monitoring, New Relic cannot integrate the data. One common cause for this issue is that the default hostnames are different. For example, infrastructure monitoring uses a host's FQDN (such as
myhost1.example.com), while APM uses the host's name (such as
- Go to one.newrelic.com > APM > (select an app).
- From the app's APM Overview page, look at the app's associated host name. Compare that name with the same host's name in infrastructure monitoring.
- If the names are different, either set the APM agent host's
display_nameto match its FQDN, or set the host's
display_namein Infrastructure to match the one set in APM.
- Check for replacement host FQDN recognition problems.
If the APM-Infrastructure integration previously worked but has stopped, the server may have been replaced by another server that has the same FQDN. If both servers existed simultaneously for a period of time, New Relic cannot automatically recognize the new server. That will break the connection between APM and infrastructure data.
- To solve this problem, get help at support.newrelic.com.
- To prevent this problem, make sure there is a time gap between taking down an old server going down and creating a new server.