# How to TAG Synthetic Monitors with the location name

**URL:** <https://community.dynatrace.com/t/how-to-tag-synthetic-monitors-with-the-location-name/48718>\
**Category:** Troubleshooting\
**Tags:** maintenance-window, synthetic-monitoring\
**Created:** [February 25, 2025, 2:00pm UTC](https://community.dynatrace.com/t/how-to-tag-synthetic-monitors-with-the-location-name/48718 "2025-02-25T14:00:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ShahbazKhan](https://avatars.discourse-cdn.com/v4/letter/s/c68b51/32.png) [@ShahbazKhan](https://community.dynatrace.com/u/ShahbazKhan)\
**Post date:** [February 25, 2025, 2:00pm UTC](https://community.dynatrace.com/t/how-to-tag-synthetic-monitors-with-the-location-name/48718/1 "2025-02-25T14:00:00Z")

</div>

## **Summary**

Learn how to automatically tag Dynatrace Synthetic monitors based on their execution location (for example, London or Frankfurt) so you can use those tags in Maintenance Windows, filtering, and alerting workflows.This approach enables location-based control for Synthetic Browser and HTTP monitors, which is not available out of the box.

## **Problem**

Dynatrace Maintenance Windows allow filtering using:

- Tags
- Synthetic entities

However, they **do not support direct filtering by Synthetic location name** (public or private locations).This makes it difficult to:

- Silence alerts for monitors running from specific regions
- Handle maintenance for location-specific outages
- Apply environment-specific monitoring rules

## **Cause**

Synthetic locations are not exposed as a **native filter dimension** in Maintenance Windows.As a result, you cannot directly select:

> “All monitors running from London”

without introducing an intermediate layer (such as tagging).

## **Resolution**

Use **[automatic tagging](https://docs.dynatrace.com/docs/manage/tags-and-metadata/setup/how-to-define-tags#automatic) with entity selectors** to assign tags to Synthetic monitors based on the location they run on.

### **Step 1 – Create an automatic tagging rule**

Create a tag that represents the location (for example: `location:London`).Use the following **entity selector logic** :

- For Browser Monitors

```markup
type("SYNTHETIC_TEST"),fromRelationships.runsOn(type("SYNTHETIC_LOCATION"),customizedName("London"))

```

- For HTTP Monitors

```markup
type("HTTP_CHECK"),fromRelationships.runsOn(type("SYNTHETIC_LOCATION"),customizedName("London"))

```

These selectors tag monitors based on the location they execute from.

For example,

 ![ShahbazKhan_1-1730814570520.png](https://global.discourse-cdn.com/dynatrace/original/3X/1/d/1ddb5cfadf070d56f7a4a01612d58fc152663e97.png)

 ![ShahbazKhan_0-1730814945984.png](https://global.discourse-cdn.com/dynatrace/original/2X/d/df7fb4e2ea2bd348940ccb35db6e66180b1a1354.png)

### **Step 2 – Use the tag in Maintenance Windows**

Once applied, you can:

- Filter Maintenance Windows by the tag (for example: `location:London`)
- Scope maintenance to specific Synthetic locations
- Avoid unnecessary alert noise during regional outages or maintenance

## &nbsp; **Example Use Cases**

This tagging approach is especially useful for:

- 🌍 Region-specific maintenance windows (e.g., Europe vs US)
- 🧪 Testing Synthetic performance by location
- 🚫 Silencing alerts when a single Synthetic location is degraded
- 🔐 Managing private Synthetic locations independently

## **Best Practices**

- Use a **consistent naming convention** such as:
  - `location:London`
  - `location:Frankfurt`

- Avoid free-text tags; standardize across teams
- Combine with:
  - Management Zones
  - Alerting profiles  
for more granular control

## What’s next

If the setup doesn’t work as expected, collect the following before contacting support:

- Link to the automatic tagging rule
- Maintenance Window configuration
- Affected Synthetic monitor(s)

Then: 👉 Open an in-product chat via Dynatrace for further assistance.

### Related reading

📖&nbsp; [Automatic tagging](https://docs.dynatrace.com/docs/manage/tags-and-metadata/setup/how-to-define-tags#automatic)

📖&nbsp; [How to define a maintenance window](https://docs.dynatrace.com/docs/analyze-explore-automate/notifications-and-alerting/maintenance-windows/define-maintenance-window)
