# Validation errors while creating NAM monitors via UI on Managed

**URL:** <https://community.dynatrace.com/t/validation-errors-while-creating-nam-monitors-via-ui-on-managed/49731>\
**Category:** Troubleshooting\
**Tags:** nam, network-monitoring, synthetic-monitoring\
**Created:** [January 15, 2025, 2:00pm UTC](https://community.dynatrace.com/t/validation-errors-while-creating-nam-monitors-via-ui-on-managed/49731 "2025-01-15T14:00:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![slawomir\_justa](https://avatars.discourse-cdn.com/v4/letter/s/a87d85/32.png) [@slawomir\_justa](https://community.dynatrace.com/u/slawomir_justa)\
**Post date:** [January 15, 2025, 2:00pm UTC](https://community.dynatrace.com/t/validation-errors-while-creating-nam-monitors-via-ui-on-managed/49731/1 "2025-01-15T14:00:00Z")

</div>

## **Summary**

This article explains how to fix validation errors when creating **Network Availability Monitors (NAM)** in the Dynatrace Managed UI.These errors are commonly caused by:

- Incorrect constraint configuration
- Missing request definitions

Fixing these configuration issues allows successful creation of NAM monitors and ensures proper network monitoring.

## **Problem**

When [creating a NAM monitor](https://docs.dynatrace.com/managed/observe/digital-experience/synthetic-monitoring/network-availability-monitors/configure-nam-managed#manage-nam-monitors-using-web-ui) via the Managed UI, validation may fail with errors such as:

_Validation failed with the following errors: (step[0].constraint[0]) value: attribute is missing_

 ![slawomir_justa_0-1736939922918.png](https://global.discourse-cdn.com/dynatrace/original/2X/8/8a9fea1ff54b959d5b0e8ac546b3897ba0028d5d.png)

_Validation failed with the following errors: (step[0]) At least one request per step must be defined_

 ![slawomir_justa_1-1736939933019.png](https://global.discourse-cdn.com/dynatrace/original/2X/5/55812bb65d5ec04713120ae2bec9a14d62a7f932.png)

As a result:

- The monitor cannot be saved
- Configuration is blocked at validation stage

## **Cause**

These validation errors occur when required fields are either:

- Missing
- Incorrectly configured

Typical root causes include:

### 1. Incorrect constraint configuration

- Misconfigured `SUCCESS_RATE_PERCENT` settings
- Using a single property instead of required key-value pairs

### 2. Missing request definition

- No request configured in the step
- NAM requires at least one request-level configuration per step
- 

## **Resolution**

### **Fix 1 – Correct constraint configuration (SUCCESS\_RATE\_PERCENT)**

Ensure the constraint contains **two properties** :

```auto
operator: ">"
value: "80"

```

❌ Incorrect (causes validation error):

```auto
">" : "80"

```

✅ Correct:

- Separate fields for:
  - `operator`
  - `value`

### 

\*\*

 ![slawomir_justa_3-1736940062211.png](https://global.discourse-cdn.com/dynatrace/original/3X/9/a/9a853e716b31f8ee07ec7cbd47f935a1a1c185af.png)

 ![slawomir_justa_2-1736940053668.png](https://global.discourse-cdn.com/dynatrace/original/3X/d/e/deb407373144abafb81516e7b119d6022b167290.png)\*\*

### **Fix 2 – Add request configuration to each step**

Each NAM step must include:

- At least one request definition

Even if minimal:

- Add an empty or basic request configuration using the UI button

Without this:

- Validation fails with:

## 

 ![slawomir_justa_5-1736940084048.png](https://global.discourse-cdn.com/dynatrace/original/2X/8/8c937a6d838cd29e10c01880ad1a52b0a0ab26a3.png)

 ![slawomir_justa_4-1736940076164.png](https://global.discourse-cdn.com/dynatrace/original/3X/6/9/69642a0892f18ed908809ba56130b93bfeeacc65.png)

## **Example**

A working NAM step should:

- Include:
  - ✅ At least one request
  - ✅ Proper constraint structure

If either is missing:

- The UI validation fails immediately

## What’s next

If the issue persists:Provide the following to Dynatrace Support:

- Screenshot of configuration
- Settings used in each step
- Exact validation error text

Then open a support ticket and reference this article for faster resolution.

### Related reading

📖&nbsp;&nbsp;[Script Configuration Constraints](https://docs.dynatrace.com/managed/observe/digital-experience/synthetic-monitoring/network-availability-monitors/configure-nam-managed#big-steps--Configuration--2#script-configuration-constraints)

📖&nbsp;&nbsp;[Synthetic Troubleshooting Map](https://community.dynatrace.com/topic/250426)

📖&nbsp;&nbsp;[NAM overview and usage articles](https://community.dynatrace.com/post/267342)