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.
Validation failed with the following errors: (step[0].constraint[0]) value: attribute is missing

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

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:
operator: ">"
value: "80"
❌ Incorrect (causes validation error):
">" : "80"
✅ Correct:


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:
“At least one request per step must be defined”


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.