When APM and infrastructure agents are installed on the same hosts and use the same New Relic or license keys from accounts in the same organization, APM data should appear in infrastructure, and vice versa. If you do not see this APM-infrastructure linkage, follow these troubleshooting tips.
Please note if license keys from separate accounts within an organization are used a user must have access to both accounts to see the linked data.
Solution
If you completed the APM/Infrastructure integration but do not see APM data in infrastructure, try these troubleshooting procedures.
If you have not restarted your APM-monitored application in a few weeks or months, the data streams from infrastructure monitoring and APM may not be linked.
If the hostnames are different in APM and the infrastructure UI, we 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 myhost1).
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.