---
title: Private locations overview: Monitor internal sites and add new locations
source: https://docs.newrelic.com/docs/synthetics/synthetic-monitoring/private-locations/private-locations-overview-monitor-internal-sites-add-new-locations
---

In synthetic monitoring, a private location is a collection of synthetics job managers. Synthetics job managers are containerized application that receive and manage jobs set up through the synthetics UI.

A private location can contain any number of synthetics job managers. Private locations allow you to extend your synthetic monitoring coverage to new geographical locations, and to monitor websites behind your firewall (like an intranet site).

## What you need [#requirements]

To use private locations, first review these requirements and other factors:

| Compatibility for...           | Requirements                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
| ------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Check budget                   | Checks from a private location count against [your budget](https://docs.newrelic.com/docs/accounts/accounts-billing/new-relic-one-pricing-users/pricing-billing).                                                                                                                                                                                                                                                                                                                                                 |
| Synthetics horde endpoint      | For US-based accounts (default): `https://synthetics-horde.nr-data.net/` For [EU-based](https://docs.newrelic.com/docs/using-new-relic/welcome-new-relic/get-started/introduction-eu-region-data-center#partner-hierarchy) accounts: `https://synthetics-horde.eu01.nr-data.net/` For JP-based accounts: `https://synthetics-horde.jp.nr-data.net/`                                                                                                                                                               |
| Outbound network access        | The synthetics job manager needs to connect to the synthetic monitoring's horde endpoint to receive and process jobs. If your firewall rules don't permit direct access, you must [configure proxy access](https://docs.newrelic.com/docs/synthetics/synthetic-monitoring/private-locations/install-job-manager/#FAQ). Test your connection to the horde endpoint with a successful response from the following command: ````sh curl -X GET https://synthetics-horde.nr-data.net/synthetics/api/v1/ping ```  ```` |
| Account access and permissions | If a private location is set up by an account with [child accounts](https://docs.newrelic.com/docs/accounts/original-accounts-billing/original-users-roles/parent-child-account-structure), it can be used by users with access to those child accounts. But if it's set up on a child account, it can only be used by users in that account.                                                                                                                                                                     |

## Create a private location [#create-location]

Before [installing synthetics job managers](https://docs.newrelic.com/docs/synthetics/synthetic-monitoring/private-locations/install-job-manager), you need to create a private location.

To create a new private location:

![screenshot-manage-private-locations.png](https://docs.newrelic.com/images/synthetic_screenshot-full_find-private-location-button.webp "Click the Create private location button")

**[one.newrelic.com > Synthetic monitoring > Private locations](https://one.newrelic.com/synthetics-nerdlets/private-location-list)**: Use the **Private Locations** page to create, edit, and delete private locations.

1.  Ensure you meet the [requirements](#requirements), including [account access requirements](#account-access).

2.  Go to **[one.newrelic.com > Synthetic monitoring > Private locations](https://one.newrelic.com/synthetics-nerdlets/private-location-list)**. Then select 
    **Create private location**.

    > #### 💡 TIP
    >
    > The private locations sub menu becomes available after you create your first monitor.

3.  Type a location name.

4.  Optional: Configure these additional settings:

    -   **Description**: Describe your private location for other account users.

    -   **Share this location:** Select this option to share the location with other accounts in your organization.
        > #### 💡 TIP
        >
        > Sharing this location makes it visible to all accounts in your organization, allowing them to use it for running their synthetic monitors.

    -   **[Verified script execution](https://docs.newrelic.com/docs/synthetics/new-relic-synthetics/private-locations/verified-script-execution-private-locations)**: Require a passphrase when assigning scripts to this location, or when adding job managers to the location.

5.  Select **Create**.

After creating the location, synthetic monitoring lists your **Private location key** in the My location tab so you can [install a job manager](https://docs.newrelic.com/docs/synthetics/synthetic-monitoring/private-locations/install-job-manager).

![screenshot-manage-private-locations.png](https://docs.newrelic.com/images/synthetic_screenshot-full_private-location-page.webp "Add private location to a synthetic monitor")

## Ping monitor checks [#checks]

Each synthetics job manager can run about 75 ping monitor checks per minute. If the job queue for a particular location is growing, [add additional job managers](https://docs.newrelic.com/docs/synthetics/synthetic-monitoring/private-locations/install-job-manager). The capacity of a job manager can vary depending on network performance and hardware resources.

## Add jobs to the location queue [#add-jobs]

To add jobs to the queue for your location, follow standard procedures to [add or edit a monitor](https://docs.newrelic.com/docs/synthetics/new-relic-synthetics/using-monitors/add-edit-monitors#adding-monitors), and select your location from the **Private locations** list. To assign an existing monitor, edit that [monitor's settings](https://docs.newrelic.com/docs/synthetics/new-relic-synthetics/using-monitors/add-edit-monitors#editing-monitors).

## Manage private locations [#manage-location]

> #### 💡 TIP
>
> If you can't access this feature, check the [Factors affecting access to features and data](https://docs.newrelic.com/docs/accounts/accounts-billing/general-account-settings/factors-affecting-access-features-data).

Synthetic monitoring includes tools to manage locations and synthetics job managers. You can also [install synthetics job managers](https://docs.newrelic.com/docs/synthetics/synthetic-monitoring/private-locations/install-job-manager), and clear the job queue if it backs up.

To access these tools, go to **[one.newrelic.com > Synthetic monitoring > Private locations](https://one.newrelic.com/synthetics-nerdlets/private-location-list)**. Then follow the steps:

**Clear the job queue**

Click the  icon, and select **Clear queue**.

This is useful when the number of scheduled jobs has increased faster than the job managers can process them, such as when the job manager is offline.

**Change location**

Click the  icon, and select **Edit**.

**View status**

To view the status of an individual synthetics job manager, select the parent location's name from the list.

The green [health status indicator](https://docs.newrelic.com/docs/accounts-partnerships/education/getting-started-new-relic/glossary#health-status) identifies active synthetics job managers.

**View private location key**

Click the  icon, and select **Edit**.

**Unshare a private location**

If a location is shared and used by other accounts in your organization to run synthetic monitors, you cannot unshare the private location until you remove the private location from the monitors.

To unshare a private location, follow these steps:

1.  Click the  icon, and select **Edit**.
2.  Uncheck the **Share this location** box.
3.  Click **Save**.

**Delete a location**

Click the  icon for the location, and select **Delete**.

This does not shut down any job managers assigned to that location. The job managers must be shut down manually or reassigned.

**Enable or disable verified script execution**

To enable or disable [verified script execution](https://docs.newrelic.com/docs/synthetics/synthetic-monitoring/private-locations/verified-script-execution-private-locations/):

-   You need to pass the [VSE_PASSPHRASE](https://docs.newrelic.com/docs/synthetics/synthetic-monitoring/private-locations/job-manager-configuration/#environment-variables) environment variable to the job manager. Then, at the **Private locations** tab, click on **Edit** and, in the menu, enable the **Verified script execution** option.

**Rotate private location keys**

Private locations use a private location key. This token allows the private location job manager to pull jobs to be run and report the result back to New Relic platform.

If these keys are compromised they can't be rotated, so if they're compromised you should disable that key and deploy a new private location:

1.  Create a new private location:
    1.  Go to **[one.newrelic.com > Synthetic monitoring > Private locations](https://one.newrelic.com/synthetics/private-location-list)**. Then click **Create private location**.

    2.  Enter the private location name.

    3.  (Optional) Provide a description, check the **Share this location** box, and check **Enable verified script execution**.

    4.  Click **Generate key** to create the new private location.

        ![Screenshot of the screen for generating private locations](https://docs.newrelic.com/images/synthetic_screenshot-crop_generate-private-location-key.webp "Screenshot of the screen for generating private locations")

    5.  Update your job managers with the new private location. The **Configure and deploy** section includes sample code:

        ![Screenshot of the configure/deploy instructions for private locations](https://docs.newrelic.com/images/synthetic_screenshot-crop_configure-deploy-private-locations.webp "Screenshot of the configure/deploy instructions for private locations")
2.  Migrate monitors to the new private location. Follow these steps for each monitor you want to migrate:
    1.  Go to **[one.newrelic.com > Synthetic monitoring](https://one.newrelic.com/synthetics)**. Click the ellipsis icon **...** to the right of your monitor and select **Monitor settings**.

        ![How to find and edit monitor settings in synthetic](https://docs.newrelic.com/images/synthetic_screenshot-crop-monitor-settings.webp "How to find and edit monitor settings in synthetic")

    2.  In the **Select locations** tab, disable the old location and enable the new location. Then save the monitor.

        ![Screenshot demonstrating how to swap private locations when rotating private location keys](https://docs.newrelic.com/images/synthetic_screenshot-crop_edit-monitor-settings-rotate-private-location.webp "Screenshot demonstrating how to swap private locations when rotating private location   keys")
3.  Once you've migrated all the monitors running on the old location, delete the old location:
    1.  Go to **[one.newrelic.com > Synthetic monitoring > Private locations](https://one.newrelic.com/synthetics/private-location-list)**.

    2.  Find the old location. You can filter by location name or ID in the filter box.

    3.  Click the ellipsis icon **...** to the right, then select **Edit**.

        ![Screenshot of how to edit the key for a private location when rotating keys](https://docs.newrelic.com/images/synthetic_screenshot-crop_edit-private-location-rotate.webp "Screenshot of how to edit the key for a private location when rotating keys")

    4.  Click the trash icon and confirm to delete the private location.

        ![Screenshot of delete confirmation key for private location](https://docs.newrelic.com/images/synthetic_screenshot-crop_delete-private-location.webp "Screenshot of delete confirmation key for private location")

If you used secure credentials in any of the monitors you migrated, you should also [rotate those credentials](https://docs.newrelic.com/docs/synthetics/synthetic-monitoring/using-monitors/store-secure-credentials-scripted-browsers-api-tests/#rotate-secure-credentials).

## Set proxy configuration [#proxy]

You can set proxy server configuration for synthetic scripted monitors that run from local private locations. For more information, see [Synthetic's proxy settings](https://docs.newrelic.com/docs/synthetics/synthetic-monitoring/scripting-monitors/set-proxy-settings-properties-scripted-monitors).