Not seeing data

Data should start appearing in your New Relic dashboard within a few minutes after successful installation. If you do not see data after installing the New Relic agent, here are some things you can do to troubleshoot:

  1. Check your agent log files for errors.
  2. Make sure you restarted your app after updating or installing New Relic.

Deleted or renamed applications

If you delete an application from the dashboard, the app needs to stop reporting data for at least an hour before you can reuse that name. It also needs to reconnect with our servers (be restarted) before new data will be accepted.

Essentially, the app remains in our server'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 server

Your app will not be affected if the New Relic agent cannot connect to the server. Data continues to be collected, and New Relic uploads it as soon as the connection is restored. While the network is down or the server unavailable, you will see on your New Relic dashboards (at rpm.newrelic.com) that your applications are not reporting data. This is most evident in the CPU and memory charts, where there will be gaps where data is missing. 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 server, 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 server.

Java agent troubleshooting

  1. Verify the jar is installed correctly.
  2. Verify that your newrelic.jar and newrelic.yml files are in the same directory. See the Java agent installation instructions.

.NET agent troubleshooting

  1. Make sure you restarted IIS by running IISRESET from a command line.
  2. Run the Windows Event Viewer and look for Application events from the New Relic .NET Profiler.
  3. If there are no application events from the .NET agent, look for error messages from the .NET runtime.

If the .NET agent installer did not complete successfully, uninstall the agent (do not run a repair), and re-run the installer from the command line with these arguments: /log nr_install.txt. This will create a log file containing detailed information about the installer failure. Use the logfile to troubleshoot the issue. If you need further assistance, get support at support.newrelic.com.

PHP agent troubleshooting

  1. Use phpinfo() to verify that the agent was installed into the correct directories
  2. Make sure you have restarted both the local daemon and your app server
  3. Look for errors in the local daemon and agent log files
  4. For more information, see New Relic for PHP

Python agent troubleshooting

  1. Make sure your agent is up to date. If you opted to download it from the New Relic site rather than use pip or easy_install, check your version against the current release.
  2. Make sure data can get to the New Relic UI by running the python agent test.
  3. Review the configuration file that was generated with the newrelic-admin generate-config command. Does it contain the correct license key?
  4. Check for error messages in the log file. If the log file is missing not there, make sure you have logging turned on in your configuration file, and that you have permissions to write to that location.

Ruby agent troubleshooting

  1. If you are using something other than Rails, make sure you set RACK_ENV to an environment appearing in the newrelic.yml file, such as development or production.
  2. If your problem is with the Developer mode, make sure you have developer_mode: true and monitor_mode: false.
  3. Make sure newrelic.yml is installed in the working directory or config sub-directory. See the Ruby agent installation instructions
  4. Make sure monitor_mode is set to true in the newrelic.yml file.
  5. Make sure your agent is up to date. (As the different frameworks and dispatchers evolve, their APIs change, so older agents can get out of sync with newer versions of Rails, Passenger, etc.)
  6. When using the gem, verify the gem is installed correctly and is being required after the framework loads.
  7. If you are using Unicorn, make sure you have configured it to use preload_app true. The agent may not start in other modes. For more information, see No data with Unicorn.

No Ruby newrelic_agent.log file found

If you do not see a newrelic_agent log file at all, often that means the agent did not detect your dispatcher (Sinatra, Unicorn, etc). To find out immediately if this is the problem, try manually forcing the agent to start.

If that does not fix the problem, try these steps:

  1. Make sure you have write permissions on the RAILS_ROOT/log directory. (There have been cases where the Rails app setup sym-linked this directory to a /var directory but the admin neglected to change the permissions on the target directory so new log files could be created.)
  2. Make sure the log_level is at least :warn.
  3. For older verisons of Rails, make sure you do not have the plugins “locked” with the config.plugins override in environment.rb. Otherwise add newrelic_rpm to the list.
  4. Look in the application log for errors loading the gem or newrelic init.rb file.
  5. Put the following line at the end of your environment.rb file or equivalent initialization script, and verify that your application server is being detected.

    STDOUT.puts "RPM detected environment: #{NewRelic::LocalEnvironment.new}, RAILS_ENV: #{RAILS_ENV}"

Note: You can also change "STDOUT.puts" to ::RAILS_DEFAULT_LOGGER.warn and then get the output from your production logfile.

Upgrading the agent

New Relic recommends copying your existing license key and customized settings (such as app_name) into a fresh, up-to-date version of newrelic.yml. For example, Ruby users will find the newrelic.yml template in the base directory of the newrelic_rpm plugin or gem; Java users will find the newrelic.yml template in their downloaded zip file.

For more help

If you need additional help, get support at support.newrelic.com.