Note: This document only applies to some of our larger existing customers whose accounts were too large to use the automated update scripts when Alert Policies were rolled out.
New Relic's Availability Monitoring feature uses an external "pinger" to verify your customers can reach your site. The pinger service verifies application availability by making requests to them regularly, recording errors, and notifying you when an application is down.
Note: This is not the same as a Linux "ping" command, which checks to see if the interface to your system is live. New Relic's Availability Monitor is a more extensive test; it verifies your web server is functioning correctly by accessing a webpage on your site.
|Product levels||New Relic supports Availability Monitoring at no extra charge on all product levels. However, some reports that include Availability data (for example, the Service Level Agreement report) may not be available for all products.|
We check your site every 30 seconds. When we detect a failure, New Relic increases the rate to once every 15 seconds until the site recovers. This gives you much more fine-grained information about when your site recovered as well as more accurate estimates for a rate of failure when there is a partial failure.
Often customers have problems only intermittently. Other services may miss these or mis-categorize them as one-off events. Because of our frequent re-checking, we have greater success surfacing situations where you have a fraction of your page requests failing.
|Star (*) indicator||You can easily tell whether availability monitoring is enabled for your application. If the app's "traffic light" bar includes a star (*), this indicates it uses the pinger service.|
|Types of targets||You can specify webpage targets with http and https URLs. The pinger uses HEAD requests when possible, and GET requests otherwise. The URLs may include query strings.|
|User-Agent header||The User-Agent header sent with the ping request contains the value
|IP addresses||New Relic has several pinger servers distributed around the globe. If a downtime event does occur, you can see which region it was reported from and the number of failed checks from each region. If you want to configure your firewall to restrict access to your monitoring URL, see Networks.|
|Downtime notifications||You can have downtime alert notifications sent to an email address. You can also have downtime alerts sent to your pager (for example, using PagerDuty): In the Pinger URL settings you can specify an SMS gateway email address for notification to receive an SMS alert. The email alerts sent by the pinger include a detailed styled description of the event displayed in mail readers, as well as a short text attachment with a link to the details that is displayed in your SMS device.|
Here is a summary of some features that Availability Monitoring currently does not support.
|Form submission, redirects, multiple URLs||New Relic does not support multiple URLs or form submission, and we do not follow redirects. The purpose of Availability Monitoring is to verify that your application server is reachable and responding, not to verify that your application itself is working properly. (That falls under the scope of the New Relic agent.) Availability Monitoring detects the types of outages that are outside the scope of the application and would not otherwise be visible in New Relic.|
|Authentication||Authentication schemes such as OAuth or Basic Authentication are not currently supported but are under consideration as a future enhancement.|
Additional documentation resources include:
If you still have problems, submit a support ticket (for fastest service) or email support @ New Relic. Also, you may be able to find support from the community at Stack Overflow. Tag your post with