---
schema_version: "1"
id: da857a33bcb33dc0795ed38b0dd200aae5d313bcbd028f81c6c589841183e832
title: Creating Monitors That Use a Specific Location
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/api-functional-monitoring/bat-schedule-for-particular-location.md
canonical_url: https://docs.mulesoft.com/api-functional-monitoring/bat-schedule-for-particular-location
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 439efc9c61258c90129cbd7dc32743959a92a9d359f05a5dc9a87b19b372d178
description: MuleSoft Documentation Site
latest: true
---
---
product: API Functional Monitoring
---

# Creating Monitors That Use a Specific Location

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

To create a monitor that uses a specific location:

1.  Run the following command to list the locations that are in your default profile:

    ```none
    bat location ls
    ```

    > [!NOTE] To use a non-default profile, add `--profile=<name-of-profile>` to the commands in
    > these steps.

2.  Find the entry for the location that you want to use.

    For public locations, the value of the `organizationId` field is `public`. For private
    locations, the value is your organization ID.

    Here is example output from this command:

    ```none
    organizationId: 612dbc11-a043-4b8b-b76e-7d51f84723c7
    targets:
    -
      id: 75c403a6-8054-43ec-b611-63b9efff820d
      name: us-east-1
      transport: LAMBDA
      organizationId: public
    -
      id: 799baaeb-3c86-4798-b5b4-6d6954254229
      name: us-east-2
      transport: LAMBDA
      organizationId: public
    -
      id: b4b4db50-bcbb-4b9a-93e1-50259fd100f7
      name: myLocation
      transport: MULE
      organizationId: 612dbc11-a043-4b8b-b76e-7d51f84723c7
    ```

3.  Copy to your clipboard the value of the `id` field for the location that you want to use.

    For example, to use the private location in the example output, copy the value of the `id` field
    for the third location listed.

4.  Create the schedule, using the `--target` parameter and pasting in the value of the `id` field,
    as in this example:

    ```none
    bat schedule create --target=b4b4db50-bcbb-4b9a-93e1-50259fd100f7
    ```

    > [!NOTE] This schedule uses the default interval of 15 minutes.

    The output of the `bat schedule create` command looks like this:

    ```none
    #Creating artifact...
      + exchange.json
      + .DS_Store
      + config/default.dwl
      + config/qax.dwl
      + config/devx.dwl
      + config/stgx.dwl
      + tests/HelloWorld.dwl
      + bat.yaml
    # Creating artifact...OK
    # Uploading 612dbc11-a043-4b8b-b76e-7d51f84723c7:HelloWorldSuite:0.0.1
    # Version 0.0.1 published
    scheduleId: 345305b4-0244-4a75-a304-220495e2e34a
    ```

5.  If you run the `bat schedule ls` command, you see an entry like this one:

```none
# HelloWorldSuite
# every 15 minutes
id: 345305b4-0244-4a75-a304-220495e2e34a
test: 612dbc11-a043-4b8b-b76e-7d51f84723c7:HelloWorldSuite
version: 0.0.1
organizationId: 612dbc11-a043-4b8b-b76e-7d51f84723c7
config: default
target:
  id: b4b4db50-bcbb-4b9a-93e1-50259fd100f7
  name: myLocation
  transport: MULE
nextExecution: 2019-09-27T02:15:00Z
cron: 0 */15 * * * ? *
active: true
```