---
title: Add and edit monitors
source: https://docs.newrelic.com/docs/synthetics/synthetic-monitoring/using-monitors/add-edit-monitors
---

Synthetic monitors are API checks or virtual browser instances that monitor your website, recording each check in detail. Monitors can:

-   Capture aggregate numbers, including an overview or summary.
-   Provide detailed statistics about downtime alert events and page resources.
-   Collect custom response codes that detail your monitor performance.

You can create synthetic monitors without installation. To get started:

1.  Create a [New Relic account](https://newrelic.com/signup).
2.  Go to **[one.newrelic.com > Synthetic monitoring](https://one.newrelic.com/synthetics-nerdlets/monitor-create)** and click **Create a monitor**.
3.  Select the monitor you'd like to create. If it's your first time, we recommend creating a ping or step monitor to start.

## Create a monitor [#adding-monitors]

Ready to monitor your web apps with one (or several!) of our [synthetic monitors](https://docs.newrelic.com/docs/synthetics/synthetic-monitoring/using-monitors/intro-synthetic-monitoring/#types-of-synthetic-monitors)? The steps below walk you through the process for all our monitors.

![A screenshot that displays the menu options when you go to create synthetic monitors](https://docs.newrelic.com/images/synthetic_screenshot-crop_create-monitor.webp "Create your first synthetic monitor")

Go to **[one.newrelic.com > Synthetic monitoring](https://one.newrelic.com/synthetics-nerdlets/monitor-create)** and click **Create a monitor**.

**Add a ping or simple browser monitor**

1.  Go to **[one.newrelic.com > Synthetic monitoring > Create monitor](https://one.newrelic.com/synthetics-nerdlets/monitor-create)**
2.  Click the **Availability** tile for ping monitors or **Page load performance** for simple browser monitors.
3.  Optional: Set up [alert notifications](https://docs.newrelic.com/docs/synthetics/new-relic-synthetics/using-monitors/alerting-synthetics).

    Wait a few minutes, then check your monitor from the [**Monitors** index](https://docs.newrelic.com/docs/synthetics/synthetic-monitoring/pages/synthetic-monitoring-summary).

    You have some additional configuration options for your ping or simple browser monitor. For both monitor types, you can set up:

-   A **validation string** that enables substring monitoring for [response validation](#response-validation).

-   **Custom Headers** that will accompany requests submitted by your monitors.

-   **Verify SSL** to validate the SSL certificate chain. It can be duplicated by running the following syntax:

    ```sh
    openssl s_client -servername YOUR_HOSTNAME -connect YOUR_HOSTNAME:443 -CApath /etc/ssl/certs -verify_hostname YOUR_HOSTNAME > /dev/null
    ```

    If a non-zero exit code is returned, the monitor will fail.

    With only ping monitors, you can choose to set up:

-   The **Bypass HEAD request** option to skip the default `HEAD` request and use the `GET` verb instead.

-   **Redirect is Failure**, which will categorize the redirect as a failure, rather than following the redirect to the new URL.

-   **Custom Headers** can be added to ping and simple browser monitors. These headers will be added to requests submitted by the monitor.

    With only simple browser monitors, you can select from Chrome or Firefox and enable [device emulation](https://docs.newrelic.com/docs/synthetics/synthetic-monitoring/using-monitors/device-emulation) settings, including device type and screen orientation.

**Add a scripted browser or API test monitor**

1.  Go to **[one.newrelic.com > Synthetic monitoring > Create monitor](https://one.newrelic.com/synthetics-nerdlets/monitor-create)**.
2.  Specify a [monitor type](#setting-type) and [name](#setting-name).
3.  Choose a [period](#setting-frequency) to determine how often each location will run your monitor.
4.  Optional: Select one or more browser types and enable [device emulation](https://docs.newrelic.com/docs/synthetics/synthetic-monitoring/using-monitors/device-emulation) settings, browser types and including device type and screen orientation are available for scripted browser monitors.
5.  Select the [locations](#setting-location) from which you want your monitor to run.
6.  Optional: Set up [alert notifications](https://docs.newrelic.com/docs/synthetics/new-relic-synthetics/using-monitors/alerting-synthetics).
7.  Select **Next: Write your script** to create a script for your [**scripted browser**](https://docs.newrelic.com/docs/synthetics/new-relic-synthetics/scripting-monitors/writing-synthetic-scripts) or [**API test**](https://docs.newrelic.com/docs/synthetics/new-relic-synthetics/scripting-monitors/writing-api-tests), then select **Validate** to verify your syntax.

    > #### 💡 TIP
    >
    > For complex scripts, validation may take up to one minute.
8.  Select **Create my monitor** to confirm.

    Wait a few minutes, then check your monitor from the [**Monitors** index](https://docs.newrelic.com/docs/synthetics/new-relic-synthetics/dashboards/synthetics-monitors-dashboard-access-your-monitors).

**Add a step monitor**

1.  Go to **[one.newrelic.com > Synthetic monitoring > Create monitor](https://one.newrelic.com/synthetics-nerdlets/monitor-create)**.
2.  Select step monitor as the [monitor type](#setting-type).
3.  Specify a [name](#setting-name) and choose a [period](#setting-frequency) to determine how often each location will run your monitor.
4.  Optional: Select one or more browser types and enable [device emulation](https://docs.newrelic.com/docs/synthetics/synthetic-monitoring/using-monitors/device-emulation) settings, browser types and including device type and screen orientation are available for scripted browser monitors.
5.  Select the [locations](#setting-location) from which you want your monitor to run.
6.  Build your monitor by selecting from the preconfigured steps at the bottom of the UI:

    -   Navigate to a URL
    -   Type text
    -   Click an element
    -   Assert text
    -   Assert an element
    -   Secure a credential

    Use the instructions on the right side of the UI to help locate elements by CSS class, HTML ID, link text, or XPath.
7.  Select **Save monitor** to confirm.

    Generate some traffic and wait a few minutes, then check your monitor from the [**Monitors** index](https://docs.newrelic.com/docs/synthetics/new-relic-synthetics/dashboards/synthetics-monitors-dashboard-access-your-monitors).

**Add a certificate check monitor**

1.  Go to **[one.newrelic.com > Synthetic monitoring > Create monitor](https://one.newrelic.com/synthetics-nerdlets/monitor-create)**.
2.  Select the certificate check monitor type.
3.  Specify a [name](#setting-name) and enter the domain you'd like to monitor.
4.  Enter the number of days it takes for your certificate to expire.
5.  Select the period to determine your monitor's [frequency](#setting-frequency).
6.  Optional: Add tags to help you find this monitor later.
7.  Select the [locations](#setting-location) from which you want your monitor to run, and then click **Save monitor** to confirm.

    Generate some traffic and wait a few minutes, then check your monitor from the [**Monitors** index](https://docs.newrelic.com/docs/synthetics/new-relic-synthetics/dashboards/synthetics-monitors-dashboard-access-your-monitors).

**Add a broken links monitor**

1.  Go to **[one.newrelic.com > Synthetic monitoring > Create monitor](https://one.newrelic.com/synthetics-nerdlets/monitor-create)**.
2.  Select the broken links check monitor type.
3.  Specify a [name](#setting-name) and enter the URL you'd like to monitor (may be any valid HTTP or HTTPS URL).
4.  Select the period to determine your monitor's [frequency](#setting-frequency).
5.  Optional: Add tags to help you find this monitor later.
6.  Select the [locations](#setting-location) from which you want your monitor to run, and then click **Save monitor** to confirm.

    Generate some traffic and wait a few minutes, then check your monitor from the [**Monitors** index](https://docs.newrelic.com/docs/synthetics/new-relic-synthetics/dashboards/synthetics-monitors-dashboard-access-your-monitors).

Wanting to deploy more than a single monitor at a time? We recommend checking out the [NerdGraph API synthetic monitoring tutorial](https://docs.newrelic.com/docs/apis/nerdgraph/examples/nerdgraph-synthetics-tutorial). You can automate monitor creation with API calls.

You can also create monitors with our [synthetic monitoring REST API](https://docs.newrelic.com/docs/apis/synthetics-rest-api/monitor-examples/manage-synthetics-monitors-via-rest-api). For REST APIs, make a `GET` request to retrieve the configuration details of your chosen synthetic monitor. Once you've retrieved that data, use `POST` to create a "copy" of your chosen monitor.

## Edit a monitor [#editing-monitors]

![A screenshot that shows the New Relic UI when you're editing your monitor.](https://docs.newrelic.com/images/synthetic_screenshot-full_edit-monitor-from-general.webp "Edit a monitor page")

**[one.newrelic.com > Synthetic monitoring](https://one.newrelic.com/synthetics-nerdlets) > General**: Keep your monitors up to date so New Relic is always receiving the most pertinent data.

You cannot change a monitor's [type](#setting-type) after the monitor is created, but you can edit other monitor settings.

1.  Go to **[one.newrelic.com > Synthetic monitoring](https://one.newrelic.com/synthetics-nerdlets)**, then select the monitor you want to edit.
2.  In the side menu, select a link to change the following [settings](#settings):

    -   Select **Settings > General** to edit [name](#setting-name), URL, [locations](#setting-location), [frequency](#setting-frequency), and advanced options.
    -   For **Scripted browser** and **API test** monitors, select **Settings > Script** to edit your monitor script.
    -   For synthetic monitoring alerts, click **Manage alerts**.
3.  Select **Save changes** to confirm.

> #### ⚠️ IMPORTANT
>
> Convert to the [new synthetics runtime](https://docs.newrelic.com/docs/synthetics/synthetic-monitoring/getting-started/new-runtime) when you edit your monitors. Make sure to update your allow lists to accept network requests from [new public IP ranges](https://docs.newrelic.com/docs/synthetics/synthetic-monitoring/administration/new-synthetic-public-minion-ips).

## Delete a monitor [#deleting-monitors]

![A screenshot of the Edit a monitor page with a red arrow that shows where someone should look to delete a monitor.](https://docs.newrelic.com/images/synthetic_screenshot-crop_delete-monitor.webp "Edit a monitor page to delete monitor")

**[one.newrelic.com > Synthetic monitoring](https://one.newrelic.com/synthetics-nerdlets) > General**: Delete your synthetic monitors from the Edit monitor page.

You must have [Admin privileges](https://docs.newrelic.com/docs/synthetics/synthetic-monitoring/administration/user-roles-synthetic-monitoring/) in order to delete a monitor.

To delete a monitor:

1.  Go to **[one.newrelic.com > Synthetic monitoring](https://one.newrelic.com/synthetics-nerdlets)**, then select the monitor you want to edit.
2.  Click **General**, then click the delete monitor button.

You can also delete a monitor with our [NerdGraph API](https://docs.newrelic.com/docs/apis/nerdgraph/examples/nerdgraph-synthetics-tutorial) or the [synthetic monitoring REST API](https://docs.newrelic.com/docs/apis/synthetics-rest-api/monitor-examples/manage-synthetics-monitors-via-rest-api#delete-monitor).

## Monitor settings [#settings]

When configuring monitors, the following settings are available:

**Type**

Select the type of monitor you want to create. A monitor's [type](https://docs.newrelic.com/docs/synthetics/new-relic-synthetics/getting-started/types-synthetics-monitors#types-monitors) can't be changed after the monitor is created.

-   **Ping**: Specify a single URL to monitor for availability. New Relic will check this URL via HEAD or GET requests. The non-configurable [timeout](https://docs.newrelic.com/docs/synthetics/new-relic-synthetics/scripting-monitors/write-scripted-browsers#waiting-elements) for this monitor is 60 seconds.
-   **Simple browser**: Specify a single URL to monitor via real browser. Once each [frequency interval](#setting-frequency), New Relic will check this URL via a Selenium-powered Chrome or Firefox browser. The non-configurable [timeout](https://docs.newrelic.com/docs/synthetics/new-relic-synthetics/scripting-monitors/write-scripted-browsers/#waiting-elements) for this monitor is 60 seconds.
-   **Scripted browser**: [Create a script](https://docs.newrelic.com/docs/synthetics/new-relic-synthetics/scripting-monitors/writing-synthetic-scripts) to drive a Selenium-powered Chrome or Firefox browser. The browser follows each step in the script to verify that complex behavior is working as expected (for example, searching a website, then clicking one of the search results). The non-configurable [timeout](https://docs.newrelic.com/docs/synthetics/new-relic-synthetics/scripting-monitors/write-scripted-browsers#waiting-elements) for this monitor is 180 seconds.
-   **API test**: Create an API script to ensure your API endpoint is working correctly. For more information, see [Write API tests](https://docs.newrelic.com/docs/synthetics/new-relic-synthetics/scripting-monitors/writing-api-tests). The non-configurable timeout for this monitor is 180 seconds.
-   **Step monitor**: A codeless option to configure one or more steps to to drive a Selenium-powered Chrome or Firefox browser. The browser follows each step to verify that complex behavior is working as expected (for example, searching a website, then clicking one of the search results). The non-configurable [timeout](https://docs.newrelic.com/docs/synthetics/new-relic-synthetics/scripting-monitors/write-scripted-browsers#waiting-elements) for this monitor is 180 seconds.
-   **Certificate check**: Check if an SSL certificate will expire in a configurable number of days or less.
-   **Broken links**: Test all links found on a URL to ensure they respond with successful HTTP response codes.

**Monitor name**

Defines a name for the monitor. Monitor names cannot contain unencoded angle brackets (`<` and `>`). To include angle brackets in a monitor name, encode them as HTML bracket entities (`&lt;` for `<` and `&gt;` for `>`) in the UI or API.

**Location**

Select the locations where you want your monitor to run. Select more locations to ensure that your application is available to users around the world. If you have any [private locations](https://docs.newrelic.com/docs/synthetics/new-relic-synthetics/private-locations/private-locations-overview-monitor-internal-sites-add-new-locations), they will be listed here too. You can use the [Synthetics API `location` endpoint](https://docs.newrelic.com/docs/apis/synthetics-rest-api/monitor-examples/manage-synthetics-monitors-via-rest-api#list-locations) to retrieve a list of valid locations for your account.

Your monitor will run one check from each selected location during each [frequency interval](#setting-frequency). For example, if you select three locations and define a frequency of 15 minutes, your monitor will run three checks in each 15 minute period (or 8,640 checks per month).

**Frequency**

Select how often the monitor runs, in increments of minutes, hours, or 1 day. This frequency applies to each [location](#setting-location). For example, if you select three locations and a Frequency of **15 minutes**, your monitor will run three checks, on average every 5 minutes, in each 15 minute period (or 8,640 checks per month).

**Response Validation (optional)**

Specify text to search for on the page DOM. When using simple browser or ping [monitor types](https://docs.newrelic.com/docs/synthetics/synthetic-monitoring/getting-started/types-synthetic-monitors/#types-monitors), there is a 1MB (10^6 bytes) limit on the page load.

**Apdex T (optional)**

Specify the threshold for the **tolerable** response times for your monitor. The default value is 7 seconds (7000ms). For more information, see [Understand SLA report metrics](https://docs.newrelic.com/docs/synthetics/synthetic-monitoring/pages/synthetic-monitoring-aggregate-monitor-metrics/#understanding).

## See a history of monitor changes [#track-changes]

You can use the New Relic UI to see a [history of recent changes to synthetic monitors](https://docs.newrelic.com/docs/synthetics/new-relic-synthetics/administration/audit-synthetics-account-changes) and what users changed them.