The log data for your Java app shows failures to connect to New Relic. You want to verify if the
INFO messages are due to traffic connectivity or firewall rules, or if they are due to more serious issues.
Occasional failures to connect to the New Relic collector should not be a cause for concern. These failures should not affect the performance metrics available in your app's New Relic user interface.
New Relic's Java agent attempts to connect about once a minute. To troubleshoot the problem:
- Search your log files for
INFOmessages about connection failures.
- Check how frequently the messages appear.
For example, look for messages such as:
Jul 31, 2017 21:37:14 +0000 NewRelic 10 INFO: Failed to connect to collector.newrelic.com.:443 for My Application:java.net. ConnectException: Connection refused:connect
Jul 31, 2017 21:37:14 +0000 NewRelic 40 INFO: The data collector is temporarily unavailable. This can happen periodically. In the event that availability of our servers is not restored after a period of time, then please report this to New Relic. java.net.SocketException: Connection reset
Depending on how frequently the message appears, do the following to troubleshoot the problem:
|Frequency of INFO message||Comments|
|A few minutes||
New Relic's Java agent can cache a significant amount of metric data when it cannot connect. Even if the outage lasts a few minutes, in general, this will not result in any loss of information in the APM UI. You can safely ignore these messages.
|Intermittently over a few days||
Intermittent connection issues can occasionally cause many of these messages in a short time. If this occurs only once every few days, and all your app data appears in the New Relic UI, you can safely ignore these messages.
|Every minute for several minutes||
If failures occur every minute for more than a few minutes, then the Java agent is not able to receive data from your app, and no data can be reported. In this situation:
Despite the log text, this error generally is caused by a failure of connectivity or firewalled traffic rather than the New Relic collector actually being unavailable. For more information, see the lists of IP ranges used by all of New Relic's services.