You can proactively monitor your website or API endpoints with synthetic monitors. Depending on the type of monitor, you can:
- Add and edit monitors.
- Use the Synthetics REST API to manage monitors.
- Set up monitors from specific locations or for private servers.
You can also use the host not reporting feature in infrastructure monitoring. This allows you to take advantage of enhanced monitoring options and be notified when New Relic has stopped receiving data from your hosts.
To use synthetic monitoring and the rest of our observability platform, join the New Relic family! Sign up to create your free account in only a few seconds. Then ingest up to 100GB of data for free each month. Forever.
Types of monitors
These are the four types of synthetic monitors:
| Type of synthetic monitor | Description |
|---|---|
|
Ping monitor API name: |
Ping monitors are the simplest type of monitor. They simply check to see if an application is online. The synthetic ping monitor uses a simple Java HTTP client to make requests to your site. For consistency with other synthetic monitor types, the user agent is identified as |
|
Simple browser monitors API name: |
Simple browser monitors essentially are simple, pre-built scripted browser monitors. They make a request to your site using an instance of Google Chrome. Compared to a simple ping monitor, this is a more accurate emulation of an actual customer visit. The user agent is identified as |
|
Scripted browser monitors API name: |
Scripted browser monitors are used for more sophisticated, customized monitoring. You can create a custom script that navigates your website, takes specific actions, and ensures specific resources are present. The monitor uses Google Chrome browser. You can also use a variety of third-party modules to build your custom monitor. |
|
API tests API name: |
API tests are used to monitor your API endpoints. This can ensure that your app server works in addition to your website. New Relic uses the |