---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Create synthetic monitoring locations

# Create synthetic monitoring locations {#ariaid-title1}

* Release version: Yokohama
* 
* Updated July 31, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Create a synthetic monitoring location to run a synthetic monitor. If you plan to run monitors from a ServiceNow hosted location, you can skip this procedure.

## Before you begin

You need at least one of the following:

* A MID Server
* One or more Agent Client Collector (ACC) agent that monitors the health and performance of the HTTP endpoints to be monitored using synthetic monitoring. If you plan to run tests only from the ServiceNow hosted location, you don't need to set up a location.  
  Note:  
  * If your synthetic monitor is testing a private HTTP endpoint, your location must only include ACC agents that are within the same network boundaries as the HTTP endpoint.
  * If your monitor is testing an HTTP endpoint from different datacenters, cloud providers, or geographic regions, a different location must be used for each.
  {#create-synthetic-monitoring-locations__ul_f4w_l12_tdc}
{#create-synthetic-monitoring-locations__ul_vsk_jjr_qfc}

Role required: sn_sow_synthetics.synthetics_admin

## About this task

Synthetic monitors can be hosted from:

* A MID Server
* A cluster of Agent Client Collector agents
* A ServiceNow hosted location, as long as all monitored endpoints are publicly available. You don't need to configure a local instance as a location. It's available by default.
{#create-synthetic-monitoring-locations__ul_pml_k3r_qfc}

You can create as many locations as needed, but you must have at least one location to create a synthetic monitor.

## Procedure

1. Navigate to AllService Operations WorkspaceConfigurations.
2. Navigate to Synthetic monitoring setupManage Locations.
3. Select Create a new location.
4. Expand the Location details card and enter a unique name and an optional description for this location.  
   The description should clearly state where the servers or agents in this location are running. For example, <kbd class="ph userinput">US-1-east-cluster</kbd>.
5. In the Location type field, select either MID Server or Agent Client Collector, depending on where you want the monitor to be hosted.
6. Expand the Select card and select one or more MID Servers or ACC agents.
7. Select Save.  
   Note:  
   You can delete locations from the Synthetic Locations menu, which you can navigate to by selecting AllSynthetic MonitoringSynthetic Locations. However, you must first remove any monitors running on that location, either by editing the monitors to use a different location or deleting the monitors. See [Create and edit a synthetic monitor](https://servicenow-prod.fluidtopics.net/~wI6L7Q0fqCnQ3z3XZDp3Q "Create or edit a synthetic monitor to test the availability and performance of your HTTP endpoints before your users discover issues.") for more information.

## What to do next

[Create and edit a synthetic monitor](https://servicenow-prod.fluidtopics.net/~wI6L7Q0fqCnQ3z3XZDp3Q "Create or edit a synthetic monitor to test the availability and performance of your HTTP endpoints before your users discover issues.")

*[\>]: and then