You do not see data in New Relic UI after installing a New Relic agent.
You should start seeing data within a few minutes after installing the agent. If you do not see data, see the agent-specific troubleshooting resources:
- New Relic APM
- Java: No data appears (Java)
- .NET: No data appears (.NET)
- Node.js: Node.js agent installations
- PHP: No data appears (PHP)
- Python: No data appears (Python)
- Ruby: No data appears (Ruby)
You may also encounter the following issues in APM:
- Deleted or renamed applications
If you delete an application from the New Relic APM index, the app needs to stop reporting data for at least an hour before you can reuse that name. It also needs to reconnect with the New Relic collector (be restarted) before new data will be accepted.
The app remains in the New Relic collector's cache for an hour before it is flushed. During that time it is marked as "deleted," so no new data is accepted. Also, the data is associated with an executing app that has been deleted until the agent is restarted.
For more information, see:
- No connection to collector
Your app will not be affected if the New Relic agent cannot connect to the collector. Data continues to be collected, and New Relic uploads it as soon as the connection is restored.
While the network is down or the collector unavailable, you may see gaps where data is missing in New Relic APM's CPU and memory charts. The agent will continue attempting to reconnect, and when it succeeds, you will again see data appearing in the UI.
During the time the agent is unable to communicate with the collector, it is still collecting data. Once it is able to connect again, it will upload the data and fill in the missing segment so there will not be any confusion about whether your application was down or just not reporting data. To save memory, the data will be aggregated and averaged over the period, so you will see flat bars and charts over the period when it was unable to communicate with the collector.
- New Relic Infrastructure
- New Relic Mobile